When we started building Linguix, one of the first questions we had to settle was: what does "writing assistance" actually mean? You have text, the text has problems, a tool finds those problems and suggests fixes. Simple enough on the surface. But once you get into the mechanics, grammar and style turn out to be two fundamentally different categories of problem, and most browser extensions only solve one of them.
What grammar tools are actually checking
Grammar checkers operate on rules. Subject must agree with verb. Articles precede nouns in specific patterns. Prepositions pair with verbs in ways that can be catalogued and enumerated. A sentence either violates subject-verb agreement or it does not. This predictability is exactly why grammar tools work as well as they do. Catching "the team have submitted their report" (where singular subject "team" conflicts with plural "have") requires knowing one rule and scanning a sentence for violations of it. Tools have done this reliably for decades.
Where grammar tools run into trouble is at the edges: sentences that are technically correct but in the wrong register, constructions that are legal in American English but odd in British business writing, phrasing that is correct on its own but clashes with the surrounding paragraph's tone. These cases fall outside the rules grammar tools were built to check. No rule is broken, so nothing gets flagged. The problem stays in the text.
Where style begins
Style is a different category entirely. It is not about whether a sentence follows the rules. It is about whether the sentence does what the writer intends. A few examples from professional email writing illustrate the difference clearly.
Passive voice in the wrong place: "Mistakes were made in the initial review" passes every grammar check. It also obscures agency in a context where readers typically expect directness. No rule is broken. The style choice is doing real work here, and possibly not the work the writer intended.
Nominalization: "We need to make a decision about the timeline" is perfectly correct. "We need to decide on the timeline" is shorter, more direct, and easier to read quickly. Both pass grammar tools. Only one of them sounds like a person rather than a policy document.
Register mismatch: "I am in receipt of your communication" is technically correct but reads as overly formal in most contemporary workplace email. A grammar tool has no way to flag this without knowing the context and the likely relationship between sender and recipient.
These are style problems. They are also the problems that professional writers most often want help with. When we talked to early Linguix users, grammar flagging was appreciated but rarely the headline benefit. What people actually wanted was help with the second category: does this email read the way I meant it to?
Why browser extensions are mostly grammar tools
Grammar tools are easier to build, and the reasons for this are worth understanding. The rules are documented. The evaluation criteria are objective. You can test a grammar model against a tagged corpus and measure precision and recall with reasonable confidence. Style suggestions are harder to evaluate because the correct answer depends on context, audience, and the writer's intent, none of which is captured in the text alone.
This is not a criticism of tools that focus on grammar. For many use cases, grammar checking is exactly what the writer needs. For non-native speakers especially, grammatically correct text is a prerequisite for professional credibility in English-language contexts. Getting grammar right before worrying about style is the right order of operations for many writers.
But most professional writers, including non-native speakers who have reached a solid level of English fluency, run into style problems more often than grammar problems at this stage of their writing development. They know the rules. They sometimes make grammar mistakes under time pressure. But more often, the issue is that their writing is technically correct and yet somehow reads as flat, evasive, or oddly formal.
What style means in practice for Linguix
When we built the style layer in Linguix, we focused on three categories that came up repeatedly in our analysis of professional email and document writing.
The first is structural clarity: passive constructions where active phrasing is expected, nominalized verbs that bury the action of a sentence, and clauses whose subject does not appear until late in the sentence structure. These are not errors. They are patterns that slow down a reader or create ambiguity about who is doing what and why.
The second is redundancy: qualifiers that add no information ("in order to" instead of "to"), verbal padding ("as per our previous discussion" instead of "as we discussed"), and hedging phrases that signal uncertainty where none is needed or where the writer does not actually feel uncertain.
The third is register: vocabulary and phrasing choices that fit one level of formality when the context calls for another. This is particularly relevant for non-native speakers who adopted formal English as a default because it was what their instruction materials modeled. English professional writing has moved considerably toward conversational directness over the past two decades, and tools built on older corpora may reflect older norms that no longer serve the writer well.
What Linguix does not do
We want to be clear about the limits of style suggestions. Style is not grammar. There is no single correct answer for most style questions. A suggestion to convert passive voice to active is a useful signal, not a command. A professional writer may have good reasons for using passive voice in a specific context, and Linguix is not in a position to know those reasons. The suggestion exists so that the writer can ask the question, not to prescribe the answer.
We also do not model persuasion or deep emotional register. We can flag that a sentence is unusually blunt relative to typical professional email patterns in similar contexts. We cannot tell you whether blunt is the right choice in a particular exchange with a particular recipient. That judgment belongs to the writer. It always will.
The next generation of writing tools
The browser extensions most people have used were built when grammar was the tractable problem and style was not. That is changing. Language models can now pick up on stylistic patterns at a level of granularity that rule-based systems could not approach. The question is how to surface those signals usefully: not as corrections that override the writer's choices, but as observations that help the writer make their own choices more deliberately.
That is the design space Linguix works in. Grammar checking is part of what we do, because it is genuinely valuable and because non-native speakers in professional contexts need it. But if you ask where the real gap is, where writers most often fail to say what they were trying to say, the answer is style. That is where we spend most of our time.