From 18f7e2812bd268dae42bd79d1e9c174130da95f3 Mon Sep 17 00:00:00 2001
From: Zwyx <29386932+Zwyx@users.noreply.github.com>
Date: Fri, 1 Dec 2023 20:33:38 +0800
Subject: [PATCH] readme: remove mention about ESLint stylistic rules

In the section "Does Prettier replace ESLint", it was mentioned that ESLint has stylistic rules, however these rules have been [deprecated recently](https://eslint.org/blog/2023/10/deprecating-formatting-rules/).
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 5379c319491..4e1c850ae87 100644
--- a/README.md
+++ b/README.md
@@ -103,7 +103,7 @@ We are now at or near 100% compatibility with JSCS. If you try ESLint and believ
 
 ### Does Prettier replace ESLint?
 
-No, ESLint does both traditional linting (looking for problematic patterns) and style checking (enforcement of conventions). You can use ESLint for everything, or you can combine both using Prettier to format your code and ESLint to catch possible errors.
+No, ESLint and Prettier have diffent jobs: ESLint is a linter (looking for problematic patterns) and Prettier is a code formatter. Using both tools is common, refer to [Prettier's documentation](https://prettier.io/docs/en/install#eslint-and-other-linters) to learn how to configure them to work well with each other.
 
 ### Why can't ESLint find my plugins?