Update README file.

Author: cmilr

README.md

@@ -5,13 +5,13 @@ This set of config files can help transform your command line from something ugl
 ![](screenshot.png)
 
 ## Setup
-First things first, you'll want to install a nice color theme for your terminal. The one in the screenshot above is called TupeloHoney, and you'll find it included in this repo. I based it off of the most excellent [Flat terminal theme](https://github.com/ahmetsulek/flat-terminal) from [ahmetsulek](https://github.com/ahmetsulek).
+First things first, you'll want to install a nice color theme for your terminal. The one in the screenshot above is called TupeloHoney, and you'll find it included in the repo. I based it off of the most excellent [Flat](https://github.com/ahmetsulek/flat-terminal) theme.
 
-You can load the theme by opening up your mac terminal and navigating to **Preferences > Profiles > Import**.
+Load the theme by opening up your mac terminal and navigating to **Preferences > Profiles > Import**. Don't expect things to suddenly look like they do above—*we still have work to do*.
 
-With that out of the way, we can now log into the bash terminal and set our git configuration to display colors. Here's my setup from the above screenshot.
+With that out of the way, log into your bash terminal and punch in the following git config commands. You should be able to copy & paste them as a full block and then just hit return. This tells git that we want color in our UI, and sets specific colors for specific file status types.
 
-MacOS & OS X:
+**MacOS & OS X:**
 
 ```sh
 git config --global color.ui true
@@ -22,19 +22,27 @@ git config --global color.status.updated "green normal"
 git config --global color.status.branch "yellow normal bold"
 git config --global color.status.header "white normal bold"
 ```
+The final step is to update your .bash_profile with the contents of the bash_profile file included in the repo. The easiest way to do this will be to first show all hidden files on your system, so that you can find that invisible .bash_profile file. You can do this with the following command.
 
-## Usage example
+```sh
+defaults write com.apple.finder AppleShowAllFiles YES; killall Finder /System/Library/CoreServices/Finder.app
+```
+Once your finder reloads, you should be able to see all hidden files (files with names that start with a '.') Now navigate to **Users/YourUserNameHere**, and you should see .bash_profile in the directory. If you don't, you simply have to create one (you can do this by just placing an empty text file there and naming it .bash_profile.)
 
-A few motivating and useful examples of how your product can be used. Spice this up with code blocks and potentially more screenshots.
+Either way, open your .bash_profile and paste in the contents of the bash_profile file included in this repo (paste it beneath any other content that's already in there.) Now save the file
 
-## Development setup
+**Congratulations!** Your .bash_profile now includes all the code that your terminal needs to display it's UI in color, including a nicely colorized bash -ls command, a customized command prompt, and aliases for a number of highly-readable git log formats. You can customize these to your heart's content, but hopefully this will give you a solid jumping-off point.
 
-Describe how to install all development dependencies and how to run an automated test-suite of some kind. Potentially do this for multiple platforms.
+Now let's hide those invisible files again, by pasting the following command into the terminal.
 
 ```sh
-make install
-npm test
+defaults write com.apple.finder AppleShowAllFiles NO; killall Finder /System/Library/CoreServices/Finder.app
 ```
+And then restart the terminal app. At this point, we're ready to go!
+
+## Usage example
+
+A few motivating and useful examples of how your product can be used. Spice this up with code blocks and potentially more screenshots.
 
 ## Release History