From 9ecd42f36462331a0d697e74323a4d24f0cf02fc Mon Sep 17 00:00:00 2001 From: Addison G Date: Wed, 27 Apr 2022 15:22:05 +1000 Subject: [PATCH] docs: Fixed typo in code comment (#15812) --- docs/src/rules/no-constant-binary-expression.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/rules/no-constant-binary-expression.md b/docs/src/rules/no-constant-binary-expression.md index 36f67fd4370..7efd4fcf4c6 100644 --- a/docs/src/rules/no-constant-binary-expression.md +++ b/docs/src/rules/no-constant-binary-expression.md @@ -12,7 +12,7 @@ Comparisons which will always evaluate to true or false and logical expressions These errors are especially common in complex expressions where operator precedence is easy to misjudge. For example: ```js -// One might think this would evaluate as `x + (b ?? c)`: +// One might think this would evaluate as `a + (b ?? c)`: const x = a + b ?? c; // But it actually evaluates as `(a + b) ?? c`. Since `a + b` can never be null,