(add suggested format changes) why and how use Prettier and ESLint

README.md

@@ -94,15 +94,15 @@ make code more consistent in itself and across team members and detect problemat
 
 eslint commands:
 
-- to see errors: npx eslint (file-name)
+- to see errors: `npx eslint (file-name)`
   Warning: you can make this command, to target just files into src folder,
   (find this command in scripts of .gitlab-ci.yml)
-- to fix errors: npx eslint (file-name) --fix
+- to fix errors: `npx eslint (file-name) --fix`
   Warning: like the last command, you can target files into src folder and fix
-  linting errors with: npm run fix
+  linting errors with: `npm run fix`
 
 prettier command to fix errors:
-npx prettier (file-name) --write
+`npx prettier (file-name) --write`
 
 2. install extention:
 
@@ -115,7 +115,7 @@ First, we need to let Prettier do is job
 In order to be able to use ESLint alongside Prettier, the idea is to deactivate all ESLint rules that might conflict with Prettier (code formatting rules).
 Fortunately for us, the eslint-config-prettier package already does that.
 
-We will rewrite our .eslintrc file by adding prettier to the extends array and removing any code formatting rules we had.
+We will rewrite our `.eslintrc` file by adding prettier to the extends array and removing any code formatting rules we had.
 
 The prettier configuration will override any prior configuration in the extends array disabling all ESLint code formatting rules. With this configuration,
 Prettier and ESLint can be run separately without any issues.
@@ -125,7 +125,7 @@ Next, we need to integrate Prettier with ESLint
 The process of having to run two commands to lint and format our file is not very convenient. To fix this, we will integrate Prettier with ESLint by adding
 the eslint-plugin-prettier package.
 
-We will now rewrite our .eslintrc file by adding the prettier plugin in the plugins array and setting the newly established prettier rule to error so
+We will now rewrite our `.eslintrc` file by adding the prettier plugin in the plugins array and setting the newly established prettier rule to error so
 that any prettier formatting error is considered as an ESLint error.
 
 We can take an unlinted file and apply ESLint on it. They are marked by prettier/prettier as errors within our ESLint error output