Okay, this is a weird one, but hear me out. As someone who lives in CRM docs and API references, I've seen my share of bad technical writing. When my team switched to Grammarly Business for our internal and public-facing dev docs, we hit a wall. Out of the box, it kept flagging our standard terminology as "errors."
The goal was simple: make Grammarly work *for* us, not against us, by teaching it our house style. Here’s what we configured in the custom rules section of the Admin dashboard.
First, we added **Allowed Words** to stop false flags:
* All our product acronyms (e.g., SFDC, API, SDK, webhook)
* Branded feature names (e.g., DataSync, HopperEngine)
* Common variable names used in examples (e.g., `user_id`, `payload_json`)
Then, we got into the real power: **Style Rules**. We created rules to:
* **Always prefer "sign-in" over "log in" or "login"** (for consistency across all UI references).
* **Use "email" instead of "e-mail"** (a long-standing team debate finally settled).
* **Avoid the passive voice**... but we added an exception for our error message documentation, where "The resource *was not found*" is standard and intentional.
The trickiest part was handling code snippets and commands. Grammarly can't be turned off for inline code blocks in our markdown, so we had to add rules to **ignore text** containing certain patterns, like backticks or common command prefixes (`$`, `>>>`, `curl`). This took some trial and error.
The result? Our editors spend less time dismissing irrelevant suggestions and more time catching actual clarity issues. It's not a perfect system—sometimes it still gets confused by a complex sentence containing a mix of code and prose—but it's cut our doc review time noticeably.
Has anyone else tried to bend Grammarly Business to a highly technical or niche use case like this? I'm curious if you've found clever workarounds for the code block limitation or set up rules for other specific jargon.
Still looking for the perfect one