@@ -18,7 +18,7 @@ This article will walk you through the development process of OS.js modules and
 Before beginning read the [overview article](../resource/overview/README.md) to familiarize yourself with the
 architecture and involved technologies.
 
-With a standard [intallation](../install/README.md) you get a fully working development environment out of the box.
+With a standard [installation](../install/README.md) you get a fully working development environment out of the box.
 
 > [info] Note that by default package extensions (applications, themes, etc.) are built separately from your installation/distribution.
 > Make sure to run commands inside the **correct directory**

@@ -31,7 +31,7 @@ npm run build
 
 ## Git submodules
 
-Same as above, except that the overrided modules are kept in separate repositories using Git [submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
+Same as above, except that the overridden modules are kept in separate repositories using Git [submodules](https://git-scm.com/book/en/v2/Git-Tools-Submodules).
 
 ```bash
 # In your OS.js root directory, set up the submodule
@@ -51,7 +51,7 @@ With the `npm link` feature you override the paths inside `node_modules/` by lin
 
 Workflow is similar to [local checkout](#local-checkout) or [Git submodules](#git-submodules), except that `package.json` does not reference local packages.
 
-Useful when maintaining a large set of overrided packages in a monorepo.
+Useful when maintaining a large set of overridden packages in a monorepo.
 
 > **[warning] It is highly recommended that you either manage your node installation with [nvm](https://.com/creationix/nvm) or [modify you npm setup](https://docs.npmjs.com/getting-started/fixing-npm-permissions) to prevent permission errors when using the npm link feature.**