Use sentence case for all headers

https://brand.github.com/content/grammar#headers-and-ui-elements

Author: parkerbxyz

Diff for: docs/01_getting_ready_for_class.md

@@ -1,10 +1,10 @@
-## Getting Ready for Class
+## Getting ready for class
 
 While you are waiting for class to begin, please take a few minutes to set up your local work environment.
 
 <!-- toc -->
 
-### Step 1: Set Up Your GitHub.com Account
+### Step 1: Set up your GitHub.com account
 
 For this class, we will use a public account on GitHub.com. We do this for a few reasons:
 
@@ -43,13 +43,13 @@ In general, we recommend you stay within two minor versions of the [latest versi
 
 We suggest having version [2.29.2](https://github.com/git-for-windows/git/releases/tag/v2.29.2.windows.2) or more recent if you're using Git for Windows or Git Bash.
 
-#### Downloading and Installing Git
+#### Downloading and installing Git
 
 If you don't already have Git installed, you can download Git at www.git-scm.com.
 
 If you need additional assistance installing Git, you can find more information in [the ProGit chapter on installing Git](http://git-scm.com/book/en/v2/Getting-Started-Installing-Git).
 
-#### Where is Your Shell?
+#### Where is your shell?
 
 Now is a good time to create a shortcut to the command line application you will want to use with Git:
 
@@ -97,11 +97,11 @@ git config --global http.proxy https://YOUR_PROXY_USERNAME:YOUR_PROXY_PASSWORD@Y
 
 Replace `YOUR_PROXY_USERNAME` with the username used to authenticate into your proxy, `YOUR_PROXY_PASSWORD` with the password used to authenticate into your proxy, and `YOUR.PROXY.SERVER` with your proxy's URL.
 
-### Step 4: Set Up Your Text Editor
+### Step 4: Set up your text editor
 
 For this class, we will use a basic text editor to interact with our code. Let's make sure you have one installed and ready to work from the command line.
 
-#### Pick Your Editor
+#### Pick your editor
 
 You can use almost any text editor, but we have the best success with the following:
 
@@ -115,7 +115,7 @@ You can use almost any text editor, but we have the best success with the follow
 
 If you do not already have a text editor installed, go ahead and download and install one of the above editors now! You can also configure Atom as your default text editor for Git commands using the [instructions at docs.github.com](https://docs.github.com/github/using-git/associating-text-editors-with-git).
 
-#### Your Editor on the Command Line
+#### Your editor on the command line
 
 After you have installed an editor, confirm you can open it from the command line.
 

Diff for: docs/02_getting_started.md

@@ -1,4 +1,4 @@
-## Getting Started With Collaboration
+## Getting started with collaboration
 
 We will start by introducing you to Git, GitHub, and the collaboration features we will use throughout the class. Even if you have used GitHub in the past, we hope this information will provide a baseline understanding of how to use it to build better software!
 
@@ -25,7 +25,7 @@ In addition to being a place to host and share your Git projects, GitHub provide
 
 ![GitHub Collaboration Features](./img/collaboration-features.png)
 
-### The GitHub Ecosystem
+### The GitHub ecosystem
 
 Rather than force you into a "one size fits all" ecosystem, GitHub strives to be the place that brings all of your favorite tools together. For more information on integrations, check out <https://github.com/integrations>.
 
@@ -48,45 +48,45 @@ As we begin to discuss Git (and what makes it special) it would be helpful if yo
 
 We will learn more about how Git stores your code as we go through this class, but the first thing you will need to understand is how Git works with your content.
 
-#### Snapshots, not Deltas
+#### Snapshots, not deltas
 
 One of the first ideas you will need understand is that Git does not store your information as series of changes. Instead Git takes a snapshot of your repository at a given point in time. This snapshot is called a commit.
 
-#### Optimized for Local Operations
+#### Optimized for local operations
 
 Git is optimized for local operation. When you clone a copy of a repository to your local machine, you receive a copy of the entire repository and its history. This means you can work on the plane, on the train, or anywhere else your adventures find you!
 
-#### Branches are Lightweight and Cheap
+#### Branches are lightweight and cheap
 
 Branches are an essential concept in Git.
 
 When you create a new branch in Git, you are actually just creating a pointer that corresponds to the most recent commit in a line of work. Git keeps the commits for each branch separate until you explicitly tell it to merge those commits into the main line of work.
 
-#### Git is Explicit
+#### Git is explicit
 
 Which brings us to our final point for now; Git is very explicit. It does not do anything until you tell it to. No auto-saves or auto-syncing with the remote, Git waits for you to tell it when to take a snapshot and when to send that snapshot to the remote.
 
-### Exploring a GitHub Repository
+### Exploring a GitHub repository
 
 A repository is the most basic element of GitHub. It is easiest to imagine as a project's folder. However, unlike an ordinary folder on your laptop, a GitHub repository offers simple yet powerful tools for collaborating with others.
 
 A repository contains all of the project files (including documentation), and stores each file's revision history. Whether you are just curious or you are a major contributor, knowing your way around a repository is essential!
 
 ![GitHub Repositories](./img/repository-intro.png)
 
-### User Accounts vs. Organization Accounts
+### User accounts vs. organization accounts
 
 There are two account types in GitHub, user accounts and organization accounts. While there are many differences in these account types, one of the more notable differences is how you handle permissions.
 
-#### User Accounts
+#### User accounts
 
 When you signed up for GitHub, you were automatically given a user account. Permissions for a user account are simple, you add people as collaborators to specific repositories to give them full read-write access to the project.
 
-#### Organization Accounts
+#### Organization accounts
 
 Organization accounts provide more granular control over repository permissions. In an organization account you create teams of people and then give those teams access to specific repositories. Permissions can be assigned at the team level (e.g, read, write, or admin).
 
-### Repository Navigation
+### Repository navigation
 
 #### Code
 
@@ -135,7 +135,7 @@ In GitHub, you will use issues to record and discuss ideas, enhancements, tasks,
 
 GitHub uses a syntax called **Markdown** to help you add basic text formatting to Issues, Pull Requests, and files with the `.md` extension.
 
-### Commonly Used Markdown Syntax
+### Commonly used Markdown syntax
 
 #### `# Header`
 

Diff for: docs/02a_activity_create_github_issue.md

@@ -1,4 +1,4 @@
-### Activity: Creating A GitHub Issue
+### Activity: Creating a GitHub issue
 
 Follow these steps to create an issue in the class repository:
 

Diff for: docs/03_github_flow.md

@@ -2,7 +2,7 @@
 
 In this section, we discuss the collaborative workflow enabled by GitHub.
 
-### The Essential GitHub Workflow
+### The essential GitHub workflow
 
 ![GitHub Workflow](./img/github-workflow.png)
 

Diff for: docs/04_branching_with_git.md

@@ -2,7 +2,7 @@
 
 The first step in the GitHub Workflow is to create a branch. This will allow us to experiment with new features without accidentally introducing untested changes on our production branch.
 
-### Branching Defined
+### Branching defined
 
 ![GitHub Workflow](./img/github-workflow.png)
 

Diff for: docs/04a_activity_create_branch.md

@@ -1,4 +1,4 @@
-### Activity: Creating A Branch with GitHub
+### Activity: Creating a branch with GitHub
 
 Earlier you created an issue about the file you would like to edit. Let's create the branch you will use to edit your file.
 

Diff for: docs/05_local_git_configs.md

@@ -1,8 +1,8 @@
-## Local Git Configuration
+## Local Git configuration
 
 In this section, we will prepare your local environment to work with Git.
 
-### Checking Your Git Version
+### Checking your Git version
 
 First, let's confirm your [Git Installation](https://git-scm.com/downloads):
 
@@ -16,7 +16,7 @@ If you do not see a Git version listed or this command returns an error, you may
 
 > To get the latest version of Git, visit [www.git-scm.com](https://www.git-scm.com).
 
-### Git Configuration Levels
+### Git configuration levels
 
 ![Git Configuration Levels](./img/config-levels.png)
 
@@ -36,7 +36,7 @@ These are the repository level configurations. They only apply to the specific r
 
 > The default value for git config is `--local`.
 
-### Viewing Your Configurations
+### Viewing your configurations
 
 If you would like to see which config settings have been added automatically, you can type `git config --list`. This will automatically read from each of the three config files and list the setting they contain.
 
@@ -50,7 +50,7 @@ You can also narrow the list to a specific configuration level by including it b
 git config --global --list
 ```
 
-### Configuring Your User Name and Email
+### Configuring your name and email address
 
 Git uses the config settings for your user name and email address to generate a unique fingerprint for each of the commits you create. You can't create commits without these settings:
 
@@ -59,14 +59,14 @@ git config --global user.name "First-name Surname"
 git config --global user.email "[email protected]"
 ```
 
-Example:
+**Example:**
 
 ```sh
 git config --global user.name "Mona Octocat"
 git config --global user.email "[email protected]"
 ```
 
-#### Git Config and Your Privacy
+#### Git config and your privacy
 
 The instructions for this exercise use the `--global` flag when identifying your `user.name` and `user.email` configuration settings. If you are currently using a computer without a private, personal account, don't apply the `--global` flag. This way, the settings will only be stored in our assignment repository. If you work in another repository on this same computer, you will need to set these configuration options again.
 

Diff for: docs/06_working_locally.md

@@ -1,8 +1,8 @@
-## Working Locally with Git
+## Working locally with Git
 
 Using the command line, you can easily integrate Git into your current workflow.
 
-### Creating a Local Copy of the repo
+### Creating a local copy of the repo
 
 ![Cloning a repository](./img/clone-diagram.png)
 
@@ -19,7 +19,7 @@ Let's go ahead and clone the class repository to your local desktop.
 1. Retrieve a full copy of the repository from GitHub: `git clone <CLONE-URL>`
 1. Once the clone is complete, cd into the new directory created by the clone operation: `cd <REPOSITORY-NAME>`
 
-### Our Favorite Git command: `git status`
+### Our favorite Git command: `git status`
 
 ```shell-session
 $ git status
@@ -30,7 +30,7 @@ nothing to commit, working tree clean
 
 `git status` is a command you will use often to verify the current state of your repository and the files it contains. Right now, we can see that we are on branch main, everything is up to date with origin/main and our working tree is clean.
 
-### Using Branches locally
+### Using branches locally
 
 ```sh
 git branch
@@ -47,7 +47,7 @@ If you want to see all of the branches, including the read-only copies of your r
 
 > The `--all` and `-a` are actually synonyms for the branch command. Git often provides a verbose and a short option.
 
-### Switching Branches
+### Switching branches
 
 ```sh
 git switch <BRANCH-NAME>
@@ -59,7 +59,7 @@ To switch the branch you created online, type `git switch` and the name of your
 
 [include](06a_activity_create_file.md ':include')
 
-### The Two Stage Commit
+### The two stage commit
 
 After you have created your file, it is time to create your first snapshot of the repository. When working from the command line, you will need to be familiar with the idea of the two stage commit.
 

Diff for: docs/07_collaborating_on_code.md

@@ -1,8 +1,8 @@
-## Collaborating on Your Code
+## Collaborating on your code
 
 Now that you have made some changes in the project locally, let's learn how to push your changes back to the shared class repository for collaboration.
 
-### Pushing Your Changes to GitHub
+### Pushing your changes to GitHub
 
 ![Pushing to GitHub](./img/push-pull.png)
 
@@ -21,7 +21,7 @@ git push
 
 [include](07a_activity_create_pull_request.md ':include')
 
-### Exploring a Pull Request
+### Exploring a pull request
 
 Now that we have created a Pull Request, let's explore a few of the features that make Pull Requests the center of collaboration:
 
@@ -37,23 +37,23 @@ The **Commits** tab contains more detailed information about who has made change
 
 The **Files changed** tab allows you to see cumulative effect of all the changes made on the branch. We call this the `diff`. Our diff isn't very interesting yet, but as we make changes your diff will become very colorful.
 
-### Code Review in Pull Requests
+### Code review in pull requests
 
 To provide feedback on proposed changes, GitHub offers three levels of commenting:
 
-#### General Conversation
+#### General conversation
 
 You can provide general comments on the Pull Request within the **Conversation** tab.
 
-#### Line Comments
+#### Line comments
 
 In the **Files changed** tab, you can hover over a line to see a blue ![`+`][octicon-diff-added] icon. Clicking this icon will allow you to enter a comment on a specific line. These line level comments are a great way to give additional context on recommended changes. They will also be displayed in the **Conversation** tab.
 
 #### Review
 
 When you are making line comments, you can also choose to **Start a Review**. When you create a review, you can group many line comments together with a general message: Comments, Approve, or Request Changes. Reviews have special power in GitHub when used in conjunction with protected branches.
 
-### Activity: Code Review
+### Activity: Code review
 
 One of the best ways to ensure code quality is to make peer reviews a part of every Pull Request. Let's review your partner's code now:
 

Diff for: docs/07a_activity_create_pull_request.md

@@ -1,4 +1,4 @@
-### Activity: Creating a Pull Request
+### Activity: Creating a pull request
 
 Pull Requests are used to propose changes to the project files. A pull request introduces an action that addresses an Issue. A Pull Request is considered a "work in progress" until it is merged into the project.
 

Diff for: docs/08_edit_on_github.md

@@ -1,16 +1,16 @@
-## Editing Files on GitHub
+## Editing files on GitHub
 
 Since you created the pull request, you will be notified when someone adds a comment or a review. Sometimes, the reviewer will ask you to make a change to the file you just created. Let's see how GitHub makes this easy.
 
-### Editing a File on GitHub
+### Editing a file on GitHub
 
 To edit a pull request file, you will need to access the **Files changed** tab.
 
 1. Click ![octicon-kebab-horizontal] in the top right corner of the diff.
 1. Click **Edit file** to edit the file using the GitHub file editor.
 1. Make changes to the file based on the comments from your reviewer or your personal perspective.
 
-### Committing Changes on GitHub
+### Committing changes on GitHub
 
 Once you have made some changes to your file, you will need to create a new commit.
 
@@ -19,7 +19,7 @@ Once you have made some changes to your file, you will need to create a new comm
 1. Choose the option to **Commit directly to your branch**.
 1. Click **Commit changes**.
 
-### Activity: Editing Files in Pull Requests
+### Activity: Editing files in pull requests
 
 Go back to your Pull Request and make the edits requested by your collaborators.
 

Diff for: docs/09_merging_pull_requests.md

@@ -1,8 +1,8 @@
-## Merging Pull Requests
+## Merging pull requests
 
 Now that you have made the requested changes, your pull request should be ready to merge.
 
-### Merge Explained
+### Merge explained
 
 When you merge your branch, you are taking the content and history from your feature branch and adding it to the content and history of the `main` branch.
 
@@ -16,7 +16,7 @@ Many project teams have established rules about who should merge a pull request.
 
 This is a discussion you should have with the other members of your team.
 
-### Merging Your Pull Request
+### Merging your pull request
 
 Let's take a look at how you can merge the pull request.
 
@@ -33,7 +33,7 @@ Let's take a look at how you can merge the pull request.
 - **Squash and merge:** This option will take all of the commits on your branch and compress them into a single commit. The commit messages will be preserved in the extended commit message for the commit, but the individual commits will be lost.
 - **Rebase and merge:** This option will take all of the commits and replay them as if they just happened. This allows GitHub to perform a fast forward merge (and avoids the addition of the merge commit).
 
-### Updating Your Local Repository
+### Updating your local repository
 
 When you merged your Pull Request, you deleted the branch on GitHub, but this will not automatically update your local copy of the repository. Let's go back to our command line application and get everything in sync.
 
@@ -44,7 +44,7 @@ First, we need to get the changes we made on GitHub into our local copy of the r
 
 `git pull` is a combination command that retrieves all of the changes from GitHub and then updates the branch you are currently on to include the changes from the remote. The two separate commands being run are `git fetch` and `git merge`
 
-### Cleaning Up the Unneeded Branches
+### Cleaning up the unneeded branches
 
 If you type `git branch --all` you will probably see that, even though you deleted your branch on the remote, it is still listed in your local copy of the repository, both as a local branch and as a read-only remote tracking branch. Let's get rid of those extra branches.
 

Diff for: docs/10_local_history.md

@@ -1,8 +1,8 @@
-## Viewing Local Project History
+## Viewing local project history
 
 In this section, you will discover commands for viewing the history of your project.
 
-### Using Git Log
+### Using Git log
 
 When you clone a repository, you receive the history of all of the commits made in that repository. The log command allows us to view that history on our local machine.