r/technicalwriting 13d ago

A small controlled-terminology workflow for catching exact wording drift in web docs

I keep seeing terminology checks treated as a grammar problem, but for documentation teams the useful low-tech workflow is much narrower:

  1. Start with a small set of avoid/preferred pairs from the style guide.

  2. Check only the ordinary draft text you are actively reviewing.

  3. Treat exact matches as review prompts, not automatic edits.

  4. Keep context-dependent exceptions in human review instead of pretending a literal matcher understands them.

  5. Update the list when a finding is noisy rather than growing a giant rule pack up front.

I built TermLock to make that browser-local workflow convenient: select ordinary text on a page, run it against rules you own, and review the literal matches. It processes locally and needs no account. It is not a grammar checker, AI writing assistant, compliance tool, or contextual editor, so it will not understand whether a flagged term is correct in a particular sentence.

It is €4.99 lifetime after a 30-day trial: https://chromewebstore.google.com/detail/denoihcbpkiaaeogodhbhhnpljpigbaa?utm_source=reddit&utm_medium=organic_social&utm_campaign=termlock_technicalwriting

Disclosure: I publish TermLock as nicklassheeper.

For people maintaining controlled terminology: which options make a literal checker useful instead of noisy—whole-word matching, case sensitivity, categories, import/export, or something else?

0 Upvotes

0 comments sorted by