Bug in the GitHub Guides

[timburgan]

Just kidding.

**Add commits**
Once your branch has been created, it's time to start making changes. 
Whenever you add, edit, or delete a file, you're making a commit, and 
adding them to your branch. This process of adding commits keeps 
track of your progress as you work on a feature branch.

Commits also create a transparent history of your work that others 
can follow to understand what you've done and why. Each commit has 
an associated commit message, which is a description explaining why 
a particular change was made. Furthermore, each commit is 
considered a separate unit of change. This lets you roll back changes 
if a bug is found, or if you decide to head in a different direction.

**ProTip**
Commit messages are important, especially since Git tracks your 
changes and then displays them as commits once they're pushed 
to the server. By writing clear commit messages, you can make it easier 
for other people to follow along and provide feedback.

[timburgan]

Looks like this:

[timburgan]

Hmm... looks a bit fuzzy 😢