From bb85a4d496ddaf2f760603c0a5dae04ca89c2cdc Mon Sep 17 00:00:00 2001
From: CK <69121180+TfTHacker@users.noreply.github.com>
Date: Sat, 30 Oct 2021 11:42:48 +0200
Subject: [PATCH] Adding eslint for code analysis

---
 README.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/README.md b/README.md
index 4d05fdf..a815286 100644
--- a/README.md
+++ b/README.md
@@ -56,10 +56,10 @@ Quick starting guide for new plugin devs:
 - [ESLint](https://eslint.org/) is a tool that analyzes your code to quickly find problems. You can run ESLint against your plugin to find common bugs and ways to improve your code. 
 - To use eslint with this project, make sure to install eslint from terminal:
   - `npm install -g eslint`
-- To use eslint analyze this project use this command:
+- To use eslint to analyze this project use this command:
   - `eslint main.ts`
-  - eslint will then createe a report with suggestions for code improvement by file and line number.
-- If your source code is a folder, such as `src`, you can use eslint with this command to analyze all files in that folder:
+  - eslint will then create a report with suggestions for code improvement by file and line number.
+- If your source code is in a folder, such as `src`, you can use eslint with this command to analyze all files in that folder:
   - `eslint .\src\`