textlint-rule-terminology

Textlint rule to check and fix terms, brands and technologies spelling in your tech writing in English.

For example:

• Javascript → JavaScript
• NPM → npm
• front-end → frontend
• website → site
• Internet → internet

(You can customize the rules as you wish.)

Installation

1npm install textlint-rule-terminology

Usage

1textlint --fix --rule terminology Readme.md

Configuration

You can configure the rule in your .textlintrc:

1{
2  "rules": {
3    "terminology": {
4      // Your options here
5    }
6  }
7}

Read more about configuring textlint.

defaultTerms (default: true)

Whether to load the default replacements (terms). Example:

1{
2  "rules": {
3    "terminology": {
4      // Don't load default replacements
5      "defaultTerms": false,
6    }
7  }
8}

skip (default ['BlockQuote'])

Syntax elements to skip. By default skips blockquotes. Example:

1{
2  "rules": {
3    "terminology": {
4      // Don't check terms inside links
5      "skip": ["Link"],
6    }
7  }
8}

See all available element types.

terms

Additional replacements.

Could be an array of replacements:

1{
2  "rules": {
3    "terminology": {
4      // List of terms
5      "terms": [
6        // Exact spelling including the case
7        "JavaScript",
8        "ESLint",
9        "Sass",
10        "Less",
11        "npm",
12        // RegExp (case-insensitive) → replacement
13        ["front[- ]end(\\w*)", "frontend$1"],
14        ["back[- ]end(\\w*)", "backend$1"],
15        ["web[- ]?site(s?)", "site$1"],
16        ["hot[- ]key", "hotkey"],
17        ["repo\\b", "repository"],
18        ["CLI tool(s?)", "command line tool$1"],
19        ["build system(s?)", "build tool$1"],
20        ["id['’]?s", "IDs"],
21        ["(\\w+[^.?!]\\)? )webpack", "$1webpack"],
22        ["(\\w+[^.?!]\\)? )internet", "$internet"]
23      ],
24    }
25  }
26}

A path to a JSON file:

1{
2  "rules": {
3    "terminology": {
4      // Load terms from a file
5      "terms": "~/terms.jsonc",
6    }
7  }
8}

Or an npm module:

1{
2  "rules": {
3    "terminology": {
4      // Load terms from npm
5      "terms": "@chucknorris/terms",
6    }
7  }
8}

Check out the default replacements.

exclude

If you don’t like any of the default replacements, you can exclude them. For example, to exclude these entries:

1// terms.jsonc
2[
3  'JavaScript',
4  'API',
5  ['V[ -]?S[ -]?Code', 'Visual Studio Code'],
6  ['walk-through', 'walkthrough'],
7  ['(?<![\\.-])css\\b', 'CSS']
8];

You need to copy the exact entry (for array, just the first element) to the exclude option of the terminology rule in your Textlint config:

1{
2  "rules": {
3    "terminology": {
4      // Excludes terms
5      "exclude": [
6        // Simple replacements, the casing should match terms.jsonc entry
7        "JavaScript",
8        "API",
9        // Complex replacements, put only the first array element exactly as
10        // in terms.jsonc
11        "V[ -]?S[ -]?Code",
12        "walk-through",
13        "(?<![\\.-])css\\b"
14      ]
15    }
16  }
17}

Tips & tricks

Use textlint-filter-rule-comments to disable terminology check for particular paragraphs:

1<!-- textlint-disable terminology -->
2
3Oh my javascript!
4
5<!-- textlint-enable -->

Other textlint rules

• textlint-rule-apostrophe — correct apostrophe usage
• textlint-rule-diacritics — words with diacritics
• textlint-rule-quotes — correct quotes usage
• textlint-rule-stop-words — filler words, buzzwords and clichés

Change log

The change log can be found on the Releases page.

Contributing

Bug fixes are welcome, but not new features. Please take a moment to review the contributing guidelines.

Sponsoring

This software has been developed with lots of coffee, buy me one more cup to keep it going.

Authors and license

Artem Sapegin and contributors.

MIT License, see the included License.md file. Also see the project status.