Fix typos in Foundations.

Author: Deledrius

foundations/index-extras.md

@@ -53,7 +53,7 @@ byline: Discovering the GitHub collaboration platform
   * Images
   * Maps
   * Spreadsheets
-  * models
+  * Models
 * Branch view
 * Branch ahead/behind positions
 * Network graph
@@ -138,7 +138,7 @@ The GitHub collaboration platform facilitates:
 
 
 
-### Drive by contributions
+### Drive-by contributions
 <iframe src="//player.vimeo.com/video/88472114" width="500" height="281" frameborder="0" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>
 
 
@@ -162,7 +162,7 @@ The GitHub collaboration platform facilitates:
 
 * Editing content of track file(s)
 * Examining differences in GHfD
-* Commiting changes as-needed
+* Committing changes as-needed
 
 
 
@@ -249,13 +249,10 @@ The GitHub collaboration platform facilitates:
 * Explain what a Fork is, its purpose, reasons
 * Demonstrate who has Forked from Network Members page
 * GitHub Student creates a Fork to follow along
-* Perform the same branching, commiting pattern
+* Perform the same branching, committing pattern
 * Open a Pull Request and see the "linkage"
 * Review and create local branch relating to PRs (even from Fork) ???
 * Use "Checkout this Branch for..."" to create local branch of any PR and branch
   * Show how branch cannot be synced for Forks' branches
   * Show how branch directly on repo can be changed
 * Review how a Fork's branch and PR can be manipulated, merged locally into another branch, integrated, and close original PR
-
-
-

foundations/index-simple.md

@@ -14,7 +14,7 @@ redirect_from:
 
 ---
 
-![Gitl logo](../assets/diagrams/git-logo-black.svg)
+![Git logo](../assets/diagrams/git-logo-black.svg)
 
 ---
 
@@ -221,7 +221,7 @@ Repositories can be created in numerous ways, including:
 * With a GitHub GUI
 * With `git init` at the command line
 
-And important decision when creating your repository is in its name. Giving it a human readable, quick-to-identify, and sensible name makes it most effective and efficient for both yourself, and your colleagues to understand.
+An important decision when creating your repository is in its name. Giving it a human readable, quick-to-identify, and sensible name makes it most effective and efficient for both yourself, and your colleagues to understand.
 
 
 
@@ -321,13 +321,13 @@ Just as with the Git technology operating on GitHub, local repositories also use
 1. Using the GitHub web UI, create a branch with an articulate feature name
 2. Make two distinct commits to the branch, each contributing part of the feature's changes
 3. Return to the homepage of the repository by clicking the repository's name
-4. Notice the suggestion message asking if you'd like to "compare and pull request"
+4. Notice the suggestion message asking if you'd like to "compare and Pull Request"
 5. Click on *Compare and Pull Request*
-6. Describe the reasoning behind the changes on this branch via the pull request
+6. Describe the reasoning behind the changes on this branch via the Pull Request
 7. @mention a team or colleague, asking for a code review
 8. Address the points raised by the reviewers through an additional commit to the branch
 9. Ask for a final review and :+1: from a colleague
-10. Merge the pull request
+10. Merge the Pull Request
 {% endcapture %}{% include lab %}
 
 ### Details
@@ -356,7 +356,7 @@ A branch is a divergent path in the history of the code base. It may contain an
 1. Create a Fork of a repository needing contributions
 2. Follow the contribution pattern of the [GitHub Flow](https://guides.github.com/introduction/flow/), with the branch creation and commits happening on your fork of the repository
 3. Observe the Network and Members graph that offer visualizations of your commits and fork
-4. Merge the pull request
+4. Merge the Pull Request
 5. Observe your contributions in the original repository, having preserved your username as the author of the code
 {% endcapture %}{% include lab %}
 

foundations/index.md

@@ -37,7 +37,7 @@ Explore an introduction to core concepts of the [Git](https://git-scm.com) techn
 
 ---
 
-![Gitl logo](../assets/diagrams/git-logo-black.svg)
+![Git logo](../assets/diagrams/git-logo-black.svg)
 
 ---
 
@@ -249,7 +249,7 @@ Repositories can be created in numerous ways, including:
 * With a GitHub GUI
 * With `git init` at the command line
 
-And important decision when creating your repository is in its name. Giving it a human readable, quick-to-identify, and sensible name makes it most effective and efficient for both yourself, and your colleagues to understand.
+An important decision when creating your repository is in its name. Giving it a human readable, quick-to-identify, and sensible name makes it most effective and efficient for both yourself, and your colleagues to understand.
 
 
 
@@ -339,7 +339,7 @@ Just as with the Git technology operating on GitHub, local repositories also use
 
 ## Exploring the GitHub Flow
 
-Discover the simplicity and flexibility in Git-based collaboration workflows with context-specific sets of changes and code review via pull requests
+Discover the simplicity and flexibility in Git-based collaboration workflows with context-specific sets of changes and code review via Pull Requests
 
 ---
 
@@ -355,13 +355,13 @@ Discover the simplicity and flexibility in Git-based collaboration workflows wit
 1. Using the GitHub web UI, create a branch with an articulate feature name
 2. Make two distinct commits to the branch, each contributing part of the feature's changes
 3. Return to the homepage of the repository by clicking the repository's name
-4. Notice the suggestion message asking if you'd like to "compare and pull request"
+4. Notice the suggestion message asking if you'd like to "Compare and Pull Request"
 5. Click on *Compare and Pull Request*
-6. Describe the reasoning behind the changes on this branch via the pull request
+6. Describe the reasoning behind the changes on this branch via the Pull Request
 7. @mention a team or colleague, asking for a code review
 8. Address the points raised by the reviewers through an additional commit to the branch
 9. Ask for a final review and :+1: from a colleague
-10. Merge the pull request
+10. Merge the Pull Request
 {% endcapture %}{% include lab %}
 
 ### Details
@@ -390,7 +390,7 @@ A branch is a divergent path in the history of the code base. It may contain an
 1. Create a Fork of a repository needing contributions
 2. Follow the contribution pattern of the [GitHub Flow](https://guides.github.com/introduction/flow/), with the branch creation and commits happening on your fork of the repository
 3. Observe the Network and Members graph that offer visualizations of your commits and fork
-4. Merge the pull request
+4. Merge the Pull Request
 5. Observe your contributions in the original repository, having preserved your username as the author of the code
 {% endcapture %}{% include lab %}
 
@@ -403,7 +403,7 @@ A branch is a divergent path in the history of the code base. It may contain an
 
 ## Syncing local and GitHub repos
 
-Publish and syncrhonize local commit history with a GitHub hosted repository from graphical clients and command line.
+Publish and synchronize local commit history with a GitHub hosted repository from graphical clients and command line.
 
 ---