From 300f6b110aa35e362bbc54d461be26432e3e411f Mon Sep 17 00:00:00 2001
From: NotWearingPants <26556598+NotWearingPants@users.noreply.github.com>
Date: Wed, 7 May 2025 21:15:53 +0300
Subject: [PATCH] fix grammar in verbatimModuleSyntax: "an ES modules"

---
 .../tsconfig-reference/copy/en/options/verbatimModuleSyntax.md  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/packages/tsconfig-reference/copy/en/options/verbatimModuleSyntax.md b/packages/tsconfig-reference/copy/en/options/verbatimModuleSyntax.md
index be3cf3590517..b5bf19b0fc53 100644
--- a/packages/tsconfig-reference/copy/en/options/verbatimModuleSyntax.md
+++ b/packages/tsconfig-reference/copy/en/options/verbatimModuleSyntax.md
@@ -140,7 +140,7 @@ module.exports = {
 
 While this is a limitation, it does help make some issues more obvious.
 For example, it's very common to forget to set the [`type` field in `package.json`](https://nodejs.org/api/packages.html#type) under `--module node16`.
-As a result, developers would start writing CommonJS modules instead of an ES modules without realizing it, giving surprising lookup rules and JavaScript output.
+As a result, developers would start writing CommonJS modules instead of ES modules without realizing it, giving surprising lookup rules and JavaScript output.
 This new flag ensures that you're intentional about the file type you're using because the syntax is intentionally different.
 
 Because `--verbatimModuleSyntax` provides a more consistent story than `--importsNotUsedAsValues` and `--preserveValueImports`, those two existing flags are being deprecated in its favor.