docs: spelling and whitespace (#21)

Fixes in Markdown files

Author: jbampton

apache-trusted-release/data-model.md

@@ -50,7 +50,7 @@ These are a set of choices which control how a release vote is conducted by the
    This will be helpful in getting dependent projects to check releases early.
 3. Manual Vote Process flag - if this is set then the vote will be completely manual and following policy is ignored.
 4. Minimum Number of Hours - the minimum time to run the vote. If set to `0` then wait until 3 +1 votes and more +1 than -1.
-5. Release Checklist - markdown text describing how to test release candidates.
+5. Release Checklist - Markdown text describing how to test release candidates.
 6. Pause for RM check if any -1 votes flag - normally when the vote passes we proceed to the next steps,
    but we should allow the RM a chance to confirm if a -1 vote should stop the release.
 

apache-trusted-release/digital-signatures.md

@@ -2,7 +2,7 @@
 
 For certain artifact types in a release the PMC wishes to add Digital Signatures using approved and current services.
 
-Currently ssl.com, but a google based one may be coming in the summer.
+Currently ssl.com, but a Google based one may be coming in the summer.
 
 ## Policy
 

apache-trusted-release/platform.md

@@ -98,7 +98,7 @@ Note: this section is a flexible outline of what we intend for the UI, and may c
 2. Release Page
    - [Download page requirements](https://infra.apache.org/release-download-pages.html)
    - Release level metadata
-   - PMC Information and webspage links
+   - PMC Information and webpage links
    - Download package from directory of release
    - Maintenance actions
    - History of events

apache-trusted-release/vote.md

@@ -12,7 +12,7 @@ The ATR should take over responsibility from the Release Manager for running a V
 
 ## Vote Policy
 
-The are reasonable adjustments that a PMC can apply to a release vote.
+There are reasonable adjustments that a PMC can apply to a release vote.
 
 1. Normally a vote goes for a minimum of 72 hours. A PMC may choose a longer time period.
    In case of a security emergency a PMC may shorten the time to as soon as there are 3 +1 votes.

content/pages/data-model.md

@@ -54,7 +54,7 @@ These are a set of choices which control how a release vote is conducted by the
    This will be helpful in getting dependent projects to check releases early.
 3. Manual Vote Process flag - if this is set then the vote will be completely manual and following policy is ignored.
 4. Minimum Number of Hours - the minimum time to run the vote. If set to `0` then wait until 3 +1 votes and more +1 than -1.
-5. Release Checklist - markdown text describing how to test release candidates.
+5. Release Checklist - Markdown text describing how to test release candidates.
 6. Pause for RM check if any -1 votes flag - normally when the vote passes we proceed to the next steps,
    but we should allow the RM a chance to confirm if a -1 vote should stop the release.
 

content/pages/platform.md

@@ -102,7 +102,7 @@ Note: this section is a flexible outline of what we intend for the UI, and may c
 2. Release Page
    - [Download page requirements](https://infra.apache.org/release-download-pages.html)
    - Release level metadata
-   - PMC Information and webspage links
+   - PMC Information and webpage links
    - Download package from directory of release
    - Maintenance actions
    - History of events

content/pages/team.md

@@ -5,7 +5,7 @@ license: https://www.apache.org/licenses/LICENSE-2.0
 The ASF Tooling team, known as **Tooling**, provides tooling development for select ASF Initiatives.
 
 ## About us
-Tooling has a core team made up of a number of paid contractors, whom are senior software engineers; and volunteers. The core team collaborates to develop specific software, work with and contribute to Infrs. The volunteers bring their skills to bear on their areas of interest, reducing the load on the core team.
+Tooling has a core team made up of a number of paid contractors, whom are senior software engineers; and volunteers. The core team collaborates to develop specific software, work with and contribute to Infra. The volunteers bring their skills to bear on their areas of interest, reducing the load on the core team.
 
 ## How you can help
 Volunteers are the driving force of the ASF. The Tooling team is looking for people willing to help out at whatever effort level suits. If you're interested, visit our [volunteer information](volunteer.html) page.

content/pages/volunteer.md

@@ -11,7 +11,7 @@ There are some basic things you could do if you're going to help out with the AS
   - Read #tooling-discuss in the ASF Slack space.
   - Bring your `python` and `asfquart` skills and offer to help with modules.
   - Work on documentation.
-  - Discuss policy clarifications and other difficult issues including moving questions and  proposals to the apprioriate place.
+  - Discuss policy clarifications and other difficult issues including moving questions and proposals to the appropriate place.
 
 **Come talk to us on [Slack](https://the-asf.slack.com/) in the #tooling-discuss channel!**