From 40655597a11b61fd803cacc84d518a82b4775c33 Mon Sep 17 00:00:00 2001
From: Srijan Saurav <68371686+srijan-deepsource@users.noreply.github.com>
Date: Mon, 30 May 2022 16:19:26 +0530
Subject: [PATCH] Revert "docs: update docs directory in working-with-rules
 (#15830)"

This reverts commit 327ca9f855ceb0a053c38c3098e2ff76c626452a.
---
 docs/src/developer-guide/working-with-rules.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/src/developer-guide/working-with-rules.md b/docs/src/developer-guide/working-with-rules.md
index 0a2d202cf98..f1330ac1296 100644
--- a/docs/src/developer-guide/working-with-rules.md
+++ b/docs/src/developer-guide/working-with-rules.md
@@ -11,7 +11,7 @@ Each rule in ESLint has three files named with its identifier (for example, `no-
 
 * in the `lib/rules` directory: a source file (for example, `no-extra-semi.js`)
 * in the `tests/lib/rules` directory: a test file (for example, `no-extra-semi.js`)
-* in the `docs/src/rules` directory: a Markdown documentation file (for example, `no-extra-semi.md`)
+* in the `docs/rules` directory: a Markdown documentation file (for example, `no-extra-semi`)
 
 **Important:** If you submit a **core** rule to the ESLint repository, you **must** follow some conventions explained below.