From bf7bd885a92046a6b6bcbcaaa1e78e9f2c4b482f Mon Sep 17 00:00:00 2001 From: Nitin Kumar Date: Sat, 17 Sep 2022 18:03:10 +0530 Subject: [PATCH] docs: fix warn severity description for new config files (#16324) --- docs/src/user-guide/configuring/configuration-files-new.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/user-guide/configuring/configuration-files-new.md b/docs/src/user-guide/configuring/configuration-files-new.md index e515acfa6e7..c5175c420a9 100644 --- a/docs/src/user-guide/configuring/configuration-files-new.md +++ b/docs/src/user-guide/configuring/configuration-files-new.md @@ -473,7 +473,7 @@ Each rule specifies its own options and can be any valid JSON data type. Please There are three possible severities you can specify for a rule * `"error"` (or `2`) - the reported problem should be treated as an error. When using the ESLint CLI, errors cause the CLI to exit with a nonzero code. -* `"warn"` (or `1`) - the reported problem should be treated as a warning. When using the ESLint CLI, warnings are reported but do not change the exit code. If only errors are reported, the exit code will be 0. +* `"warn"` (or `1`) - the reported problem should be treated as a warning. When using the ESLint CLI, warnings are reported but do not change the exit code. If only warnings are reported, the exit code will be 0. * `"off"` (or `0`) - the rule should be turned off completely. #### Rule configuration cascade