From ffa3c30560a5b260b1a3711c6072dd42f4e04fa3 Mon Sep 17 00:00:00 2001 From: Ben Perlmutter <57849986+bpmutter@users.noreply.github.com> Date: Thu, 17 Nov 2022 20:21:17 -0500 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Milos Djermanovic --- docs/src/user-guide/configuring/plugins.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/src/user-guide/configuring/plugins.md b/docs/src/user-guide/configuring/plugins.md index c70743dd8ed..79a5a378f39 100644 --- a/docs/src/user-guide/configuring/plugins.md +++ b/docs/src/user-guide/configuring/plugins.md @@ -13,7 +13,7 @@ You can extend ESLint with plugins in a variety of different ways. Plugins can i * Custom processors to extract JavaScript code from other kinds of files or preprocess code before linting. * Custom rules to validate if your code meets a certain expectation, and what to do if it does not meet that expectation. -* Other custom configurations using ESLint's built-in features. +* Custom configurations. You can also use custom parsers to convert JavaScript code into an abstract syntax tree for ESLint to evaluate. You might want to add a custom parser if the code you're writing isn't compatible with the ESLint default parser, Espree.