Fix typos and clarify wording (#414)

* Fix typos and clarify wording

* Small fixes in README 'Adding teams' section

Author: camelid

README.md

@@ -48,19 +48,19 @@ standard --fix js/
 
 # Contributing
 
-## Adding Teams
+## Adding teams
 
-Any Rust team can have a section in the Rust Forge. If you'd like to add your team you first need to add them as an item to `src/SUMMARY.md`, like so replacing `TEAM NAME` with your respective team's name to show on forge, and `<TEAM_NAME>` with a filesystem and url friendly version of that name where your documentation will be stored.
+Any Rust team can have a section in the Rust Forge. If you'd like to add your team, you first need to add them as an item to `src/SUMMARY.md`, like below, replacing `TEAM NAME` with your respective team's name to show on Forge, and `<TEAM_NAME>` with a filesystem- and URL-friendly version of that name where your documentation will be stored.
 
 ```markdown
 - [TEAM NAME](src/<TEAM_NAME>/README.md)
 <!-- or -->
 - [TEAM NAME](src/<TEAM_NAME>.md)
 ```
 
- If you run `mdbook build`, `mdbook` will automatically create the folder and file for your team.
+If you run `mdbook build`, `mdbook` will automatically create the folder and file for your team.
 
- It's recommended that you put general team information in `src/<TEAM_NAME>/README.md` such as where the meetings happen, repositories that the team manages, links to chat platforms, etc. Larger topics should be made as a subpage e.g. (`src/release/topic.md`).
+It's recommended that you put general team information in `src/<TEAM_NAME>/README.md`, such as where the meetings happen, repositories that the team manages, links to chat platforms, etc. Larger topics should be made as a subpage e.g. (`src/release/topic.md`).
 
 ```markdown
 - [TOPIC](src/<TEAM_NAME>/TOPIC.md)

src/platforms/email.md

@@ -7,14 +7,14 @@ mailing lists for teams through the [rust-lang/team] repository. Our email
 domain is `rust-lang.org`, e.g. `ferris@rust-lang.org`.
 
 ## Sending a public broadcast
-If your teams need to reach everyone in Rust organisation they can send a
+If your teams need to reach everyone in the Rust organisation, they can send an
 email to `all@`. It is recommended that you only use this mailing list when you
-know that you need contact every member, such as for organising a members event
-like the All Hands, or security alerts.
+know that you need to contact every member, such as for organising a members event
+like the All Hands, or for security alerts.
 
 ### Keeping responses private
 When sending a message to `all@`, do not put `all@` in `To`. This will mean that
-any replies to your broadcast will also be sent to everyone. Instead put your
+any replies to your broadcast will also be sent to everyone. Instead, put your
 team's email address in `To` field, and place `all@` in the `Bcc` field. Then
 any replies will be sent to just your team.
 

src/platforms/github.md

@@ -1,5 +1,5 @@
 # GitHub
-Github is where the Rust project hosts all of its code, as well as a large parts
+Github is where the Rust project hosts all of its code, as well as large parts
 of its discussions.
 
 ## Organisations