From 3ef40fb8b622b24f45fb7becb9a0a8184e1e44e5 Mon Sep 17 00:00:00 2001
From: Ben Perlmutter <57849986+bpmutter@users.noreply.github.com>
Date: Sun, 20 Nov 2022 13:21:09 -0500
Subject: [PATCH] Update docs/src/user-guide/configuring/plugins.md

---
 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 79a5a378f39..2b28fb4b6f9 100644
--- a/docs/src/user-guide/configuring/plugins.md
+++ b/docs/src/user-guide/configuring/plugins.md
@@ -15,7 +15,7 @@ You can extend ESLint with plugins in a variety of different ways. Plugins can i
 * Custom rules to validate if your code meets a certain expectation, and what to do if it does not meet that expectation.
 * 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.
+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 your code isn't compatible with ESLint's default parser, Espree.
 
 ## Configuring Plugins