fix readme spelling mistakes

Author: janishar

README.md

@@ -15,16 +15,16 @@ This open-source project is for you(community). Our Team at [AfterAcademy](https
 The main focus will be to create a maintainable and highly testable architecture.
 <br>
 Following are the features of this project:
-* **This backend in written in Typescript**: The type safety at build time and having intellisense for it in the IDE like vscode is unparallel to productivity. We have found production bug reduced to significant amount, since most of the code vulnarabilties are identified during the build phase itself.
-* **Separation of concern principle is applied**: Each component has been given a particular role. The role of the components are mutually exclusive. This makes the project easy to be unit tested.
-* **Feature enpasulation is adopted**: The files or components those are related to a particular feature has been grouped together unless that components is required in multiple features. This enhances the ability to share code across projects.
-* **Centralised Error handling is done**: We have created a framework where all the errors are handled centrally. This reduces the ambiguity in the developement when the project grow larger.
-* **Centralised Response handling is done**: Similar to Error handling we have response handling framework. This makes it very convinient to apply a common API response pattern.
-* **Mongodb is used through Mongoose**: Mongodb really fits very well to the node.js application. Being nosql, fast, and scalable makes it ideal for the modern web applications.
-* **Async execution is adopted**: We have used async/await for the promises and made sure to use non blocking version of all the functions with few exceptions.
+* **This backend is written in Typescript**: The type safety at build time and having intellisense for it in the IDE like vscode is unparalleled to productivity. We have found production bug reduced to a significant amount since most of the code vulnerabilities are identified during the build phase itself.
+* **Separation of concern principle is applied**: Each component has been given a particular role. The role of the components is mutually exclusive. This makes the project easy to be unit tested.
+* **Feature encapsulation is adopted**: The files or components that are related to a particular feature have been grouped unless those components are required in multiple features. This enhances the ability to share code across projects.
+* **Centralised Error handling is done**: We have created a framework where all the errors are handled centrally. This reduces the ambiguity in the development when the project grows larger.
+* **Centralised Response handling is done**: Similar to Error handling we have a response handling framework. This makes it very convenient to apply a common API response pattern.
+* **Mongodb is used through Mongoose**: Mongodb fits very well to the node.js application. Being NoSQL, fast, and scalable makes it ideal for modern web applications.
+* **Async execution is adopted**: We have used async/await for the promises and made sure to use the non-blocking version of all the functions with few exceptions.
 * **Docker compose has been configured**: We have created the Dockerfile to provide the easy deployability without any setup and configurations. 
-* **Unit test is favoured**: The tests has been written to test the functions and routes without the need of the database server. Integration tests has also been done but unit test is favoured.
-* **A pure backend project**: We have experienced that when a backend is developed clubed with a frontend then in the future it become really difficult to scale. We would want to create a separate backend project that servers many websites and mobile apps.
+* **Unit test is favored**: The tests have been written to test the functions and routes without the need of the database server. Integration tests has also been done but the unit test is favored.
+* **A pure backend project**: We have experienced that when a backend is developed clubbed with a frontend then in the future it becomes really difficult to scale. We would want to create a separate backend project that servers many websites and mobile apps.
 
 ## 3RE Architecture: Router, RouteHandler, ResponseHandler, ErrorHandler
 <p align="center">
@@ -55,7 +55,7 @@ Following are the features of this project:
 
 ## How to build and run this project
 
-* Install using Docker Componse [**Recomended Method**] 
+* Install using Docker Compose [**Recommended Method**] 
     * Clone this repo.
     * Make a copy of **.env.example** file to **.env**.
     * Make a copy of **keys/private.pem.example** file to **keys/private.pem**.
@@ -67,17 +67,17 @@ Following are the features of this project:
     * *If having any issue* then make sure 3000 port is not occupied else provide a different port in **.env** file.
     * *If having any issue* then make sure 27017 port is not occupied else provide a different port in **.env** file.
  * Run The Tests
-    * Install nodejs and npm on your local machine.
-    * From the root of the project execute in terminal `npm install`.
-    * *Use latest version of node on local machine if build fails*.
+    * Install node.js and npm on your local machine.
+    * From the root of the project executes in terminal `npm install`.
+    * *Use the latest version of node on the local machine if the build fails*.
     * To run the tests execute `npm test`.
  * Install Without Docker [**2nd Method**]
-    * Install mongodb on your local.
+    * Install MongoDB on your local.
     * Do step 1 to 5 as listed for **Install using Docker Componse**.
     * Do step 1 to 3 as listed for **Run The Tests**.
-    * Create users in mongodb and seed the data taking reference from the **addons/init-mongo.js**
+    * Create users in MongoDB and seed the data taking reference from the **addons/init-mongo.js**
     * Change the `DB_HOST` to `localhost` in **.env** and **tests/.env.test** files.
-    * Execute `npm start` and You will be able to access the api from http://localhost:3000
+    * Execute `npm start` and You will be able to access the API from http://localhost:3000
     * To run the tests execute `npm test`.
 
  ## Explore Online Tutorials and Courses To Learn More by AfterAcademy