docs: fix typos

docs/development/behavior.md

@@ -12,7 +12,7 @@ You are welcome to make it better, and do not need to criticize the works of oth
 
 We ask that you respect the time of the contributors and maintainers who are helping you.
 This means accepting that sometimes a question might sit around for a bit before getting answered.
-This also means that features/bugfixes that you really want can take a long time to appear.
+This also means that features or bug fixes that you really want can take a long time to appear.
 
 ## Be respectful to competitors
 

docs/development/new-package-manager-template.md

@@ -54,7 +54,7 @@
 - [ ] Custom-parsed line by line
 - [ ] Other
 
-### Does the package file structure distinguish between different "types" of dependencies? e.g. production dependencies, dev dependencies, etc?
+### Does the package file structure distinguish between different "types" of dependencies? e.g. production dependencies, development dependencies, etc?
 
 - [ ] Yes, production and development dependencies
 - [ ] No, all dependencies are treated the same
@@ -105,7 +105,7 @@
 
 ### If so, what tool and exact commands should be used if updating one or more package versions in a dependency file?
 
-### If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or env? Do you recommend the cache be kept or disabled/ignored?
+### If applicable, describe how the tool maintains a cache and if it can be controlled via CLI or environment variables? Do you recommend the cache be kept or disabled/ignored?
 
 ### If applicable, what command should be used to generate a lock file from scratch if you already have a package file? This will be used for "lock file maintenance"
 

docs/usage/configuration-options.md

@@ -1384,7 +1384,7 @@ Here is an example where you might want to limit the "noisy" package `aws-sdk` t
 }
 ```
 
-For Maven dependencies, the package name is `<groupId:artefactId>`, eg `"matchPackageNames": ["com.thoughtworks.xstream:xstream"]`
+For Maven dependencies, the package name is `<groupId:artefactId>`, e.g. `"matchPackageNames": ["com.thoughtworks.xstream:xstream"]`
 
 Note how the above uses `matchPackageNames` instead of `matchPackagePatterns` because it is an exact match package name.
 This is the equivalent of defining `"matchPackagePatterns": ["^aws\-sdk$"]` and hence much simpler.

docs/usage/dependency-pinning.md

@@ -209,7 +209,7 @@ Don't forget that there is some form of transitive trust too.
 You need to pick your direct dependencies carefully, and which versions of them you use.
 Hopefully in doing that you pick dependencies partly for how well _they_ look after their own dependencies and versions (e.g. do they have good enough test coverage, do they use something like Renovate to keep updated, etc?).
 So the reality is that even if 90% of the entries in your lock file are indirect dependencies, those are ones you have somewhat "delegated" responsibility for to your dependencies.
-e.g. I'd hope that Express are even better at watching their deps for breaks than I am, to use the example above.
+e.g. I'd hope that Express are even better at watching their dependencies for breaks than I am, to use the example above.
 
 But certainly "does it give a false sense of security" is not a question we can really answer quantifiably.
 

docs/usage/examples/self-hosting.md

@@ -158,7 +158,7 @@ If you are using CircleCI, you can use the third-party [daniel-shuy/renovate](ht
 
 By default, the orb looks for the self-hosted configuration file in the project root, but you can specify another path to the configuration file with the `config_file_path` parameter.
 
-Secrets should be configured using environment variables (eg. `RENOVATE_TOKEN`, `GITHUB_COM_TOKEN`).
+Secrets should be configured using environment variables (e.g. `RENOVATE_TOKEN`, `GITHUB_COM_TOKEN`).
 
 [Configure environment variables in CircleCI Project Settings](https://circleci.com/docs/2.0/env-vars/#setting-an-environment-variable-in-a-project).
 To share environment variables across projects, use CircleCI [Contexts](https://circleci.com/docs/2.0/contexts/).
@@ -249,7 +249,7 @@ Also replace `gitlab-token` value with the one created during the previous step.
 
 If running against GitHub Enterprise Server, change the above `gitlab` values to the equivalent GitHub ones.
 
-You can save this file as anything you want and then use `RENOVATE_CONFIG_FILE` env variable to tell Renovate where to find it.
+You can save this file as anything you want and then use the `RENOVATE_CONFIG_FILE` environment variable to tell Renovate where to find it.
 
 Most people will run Renovate via cron, e.g. once per hour.
 Here is an example Bash script that you can point `cron` to:
@@ -268,7 +268,7 @@ renovate
 
 <!-- prettier-ignore -->
 !!! note
-    The GitHub.com token in env is necessary in order to retrieve Release Notes that are usually hosted on github.com.
+    The GitHub.com token as an environment variable is needed to fetch Release Notes that are usually hosted on github.com.
     You don't need to add it if you are already running the bot against github.com, but you do need to add it if you're using GitHub Enterprise Server, GitLab, Azure DevOps, or Bitbucket.
 
 You should save and test out this script manually first, and add it to cron once you've verified it.

docs/usage/faq.md

@@ -21,7 +21,7 @@ Renovate will:
 ## Which Renovate versions are officially supported?
 
 The Renovate maintainers only support the latest version of Renovate.
-The Renovate team will only create bugfixes for an older version if the hosted app needs to stay on an older major version for a short time or if some critical bug needs to be fixed and the new major is blocked.
+The Renovate team will only fix bugs for an older version if the hosted app needs to stay on an older major version for a short time or if some critical bug needs to be fixed and the new major is blocked.
 
 If you're using the hosted app, you don't need to do anything, as the Renovate maintainers update the hosted app regularly.
 If you're self hosting Renovate, use the latest release if possible.

docs/usage/rust.md

@@ -23,7 +23,7 @@ Renovate updates Rust crates by default.
 
 If any dependencies are hosted in private Git repositories, [Git Authentication for cargo](https://doc.rust-lang.org/cargo/appendix/git-authentication.html) must be set up.
 
-If any dependencies are hosted on private crate registries (ie., not on `crates.io`), then credentials should be set up in such a way that the Git command-line is able to clone the registry index.
+If any dependencies are hosted on private crate registries (i.e., not on `crates.io`), then credentials should be set up in such a way that the Git command-line is able to clone the registry index.
 Third-party crate registries usually provide instructions to achieve this.
 
 Both of these are currently only possible when running Renovate self-hosted.