Fix typos

README.md

@@ -35,8 +35,8 @@ This project uses [Oomph](https://projects.eclipse.org/projects/tools.oomph), an
 2. Downloading the Eclipse Installer from https://www.eclipse.org/downloads/ and start it.
 3. On the initial page, click on the *Switch to advanced mode* button in the top right.
 4. On the *Product* page, select *Eclipse for RCP and RAP Developers*.
-5. On the *Projects* page, collapse the *Eclipse Projects* to scroll down to the *Github Projects* and select *m2e-code-quality*.
-6. Make sure to choose the HTTPS anonymous option for the repository
+5. On the *Projects* page, collapse the *Eclipse Projects* to scroll down to the *GitHub Projects* and select *m2e-code-quality*.
+6. Make sure to choose the HTTPS anonymous option for the repository.
 7. Choose other preferred installation settings on the *Variables* page.
 8. Finish the wizard and watch your development environment being assembled.
 9. Create an Eclipse run configuration. The target platform will automatically be setup correctly.

doc/release.md

@@ -5,7 +5,7 @@ m2e-code-quality is built with Tycho.
 
 To make a release:
 
-1. Run a build. Use Apache Maven version 3.0.3 or newer. Always run mvn clean install;
+1. Run a build. Use Apache Maven version 3.0.3 or newer. Always run `mvn clean install`;
 Tycho has some stupid bug that goes off if you don't start from clean.
 
 2. Test as you feel the urge using the plugins and features.
@@ -15,17 +15,17 @@ maintain it.
 
 4. Release notes are generated automatically from merged PR and closed issues. If you want some custom
 [release summary](https://github.com/github-changelog-generator/github-changelog-generator#using-the-summary-section-feature),
-create a new GitHub Issue, set the label `release-summary` and add it to a GitHub milestone named after the inteded
+create a new GitHub Issue, set the label `release-summary` and add it to a GitHub milestone named after the intended
 release version (see next section). The description of the issue will then be used as the release summary.
 
-5. When you're satified and all changes are pushed to the develop branch, tag the head
+5. When you're satisfied and all changes are pushed to the develop branch, tag the head
 commit with a 3-digit version number (e.g. 1.1.0). This will automatically build a site,
 publish it to
 [https://m2e-code-quality.github.io/m2e-code-quality-p2-site/](https://m2e-code-quality.github.io/m2e-code-quality-p2-site/),
 and update the development branch to the next version number. Please note that the produced artifacts
 will always have a 4 digit version number, otherwise the release build would be newer then the last snapshot build
 in OSGi's version ordering. A release build is marked with a -r version qualifier. This will also produce a
-[release](https://github.com/m2e-code-quality/m2e-code-quality/releases) in github.
+[release](https://github.com/m2e-code-quality/m2e-code-quality/releases) in GitHub.
 
 6. Just in case something failed you can repeat step 5 by moving the tag. A re-spin will completely replace the version
 in the P2 repository.