diff --git a/docs/adding-a-package-manager.md b/docs/adding-a-package-manager.md
index a3098302db7b31f3236c8b2f73d9809461b42796..b5ecdb592c9b24d2d37b57f21021985ccc148b5e 100644
--- a/docs/adding-a-package-manager.md
+++ b/docs/adding-a-package-manager.md
@@ -43,7 +43,7 @@ This function doesn't necessarily need to _understand_ the file or even syntax t
 
 As a general approach, we want to extract _all_ dependencies from each dependency file, even if they contain values we don't support. For any that have unsupported values that we cannot renovate, this `extractPackageFile` function should set a `skipReason` to a value that would be helpful to someone reading the logs.
 
-Also, if a file is passed to `extractPackageFile` that is a "false match" (e.g. not an actual package file, or contains no dependencies) then this function can return `null` to have it ignored and removed from the list of package files. A common case for this is in Meteor, where its `package.js` file name is not unique and there many be many non-Meteor projects using that filename.
+Also, if a file is passed to `extractPackageFile` which is a "false match" (e.g. not an actual package file, or contains no dependencies) then this function can return `null` to have it ignored and removed from the list of package files. A common case for this is in Meteor, where its `package.js` file name is not unique and there may be many non-Meteor projects using that filename.
 
 ##### `extractAllPackageFiles(packageFiles)` (async, optional)
 
diff --git a/docs/branches-commits.md b/docs/branches-commits.md
index fe68893e477a6bab5cada71a23709ee3efe93103..dffbee930bdbcb7e2870646d92cabc88124cf258 100644
--- a/docs/branches-commits.md
+++ b/docs/branches-commits.md
@@ -20,7 +20,7 @@ For GitHub, we use the low-level `git`-based API to manually make the commits an
 
 #### GitLab
 
-In GitLab, Merge Request are not automatically closed if you delete the associated branch, so that gives us more flexibility. Therefore the way we update a branch is simply to delete it and then create the branch + commits again, and GitLab immediately reassociates the new (single) commit with the existing PR.
+In GitLab, Merge Requests are not automatically closed if you delete the associated branch, so that gives us more flexibility. Therefore the way we update a branch is simply to delete it and then create the branch + commits again, and GitLab immediately reassociates the new (single) commit with the existing PR.
 
 #### Azure DevOps
 
diff --git a/docs/configuration.md b/docs/configuration.md
index 41ce140402038d866897de724d76869794e2784e..cb94edfb6b7b4e953d968e7b8e09a185c1325253 100644
--- a/docs/configuration.md
+++ b/docs/configuration.md
@@ -10,7 +10,7 @@ Configuration is supported via any or all of the below:
 - `renovate.json`, `renovate.json5`, `.github/renovate.json`, `.github/renovate.json5`, `.renovaterc.json`, or `.renovaterc` in target repository
 - `renovate` field of `package.json` in target repository
 
-The above are listed in reverse order of preference. i.e. `package.json`
+The above are listed in **_reverse order_** of preference. i.e. `package.json`
 settings will override `renovate.json` settings, CLI, which overrides env, which
 overrides the config file, which overrides defaults.
 
diff --git a/docs/pre-release.md b/docs/pre-release.md
index 1d4786217e675c1c34f8fc144457948a595d0a67..449034879ef91253cf9e63ea40d22a443c5091c1 100644
--- a/docs/pre-release.md
+++ b/docs/pre-release.md
@@ -40,7 +40,7 @@ How to use: Add `"gradle": { "enabled": true }` to either your bot config or you
 
 Status: beta
 
-Maven support has been implemented, initially supporting exact/pinned versions only, which should still be useful for hte majority of users who don't specify ranges in their `pom.xml` files.
+Maven support has been implemented, initially supporting exact/pinned versions only, which should still be useful for the majority of users who don't specify ranges in their `pom.xml` files.
 
 How to use: Add `"maven": { "enabled": true }` to either your bot config or your repository's `renovate.json`. If your repository contains _only_ Maven package files and no others then you'll need to add the `renovate.json` manually as otherwise Renovate won't detect any package files by default and will skip the Onboarding PR.
 
diff --git a/docs/readme.md b/docs/readme.md
index 187ec69c6054e444e87f3d297be72a126def8e64..43dab4078fdd96b377910824987a03d0cdb116bc 100644
--- a/docs/readme.md
+++ b/docs/readme.md
@@ -2,4 +2,4 @@
 
 This directory is intended to provide documentation for developers/contributors on the Renovate project. For user-facing documentation - e.g. for how to configure Renovate as a user - please see https://docs.renovatebot.com
 
-If you would like to contribute to Renovate or get it running locally for some others reason, please check out [contributing.md](../.github/contributing.md) for steps on how to set up the project locally.
+If you would like to contribute to Renovate or get it running locally for some other reason, please check out [contributing.md](../.github/contributing.md) for steps on how to set up the project locally.