From 2c6bf8ea9c8a8f94746f980bd5bea0a8c5c4d6b7 Mon Sep 17 00:00:00 2001 From: Daniel Nixon Date: Wed, 25 Sep 2019 11:12:14 +1000 Subject: [PATCH] Docs: English fix (#12306) --- docs/developer-guide/working-with-rules.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-guide/working-with-rules.md b/docs/developer-guide/working-with-rules.md index 2a9f1b9d342..35f224b3229 100644 --- a/docs/developer-guide/working-with-rules.md +++ b/docs/developer-guide/working-with-rules.md @@ -616,6 +616,6 @@ The thing that makes ESLint different from other linters is the ability to defin Runtime rules are written in the same format as all other rules. Create your rule as you would any other and then follow these steps: -1. Place all of your runtime rules in the same directory (i.e., `eslint_rules`). +1. Place all of your runtime rules in the same directory (e.g., `eslint_rules`). 2. Create a [configuration file](../user-guide/configuring.md) and specify your rule ID error level under the `rules` key. Your rule will not run unless it has a value of `1` or `2` in the configuration file. 3. Run the [command line interface](../user-guide/command-line-interface.md) using the `--rulesdir` option to specify the location of your runtime rules.