anchor.diff:  = GitHub Pages
  -:hp-tags: git, webservers
  +:hp-tags: git, webserver
   
  -After some thought, and while we're on the subject, I think it may be a good time to introduce https://pages.github.com/[GitHub pages].  To put it simply, github pages exposes a very simple https://en.wikipedia.org/wiki/Web_server[webserver] for files in a branch of a git repository.  A webserver _serves_ files to the _web_.  When your browser makes a request to an webserver the webserver will expose the files in its contol for the browser to render.  What this all amounts to is that you will be able to see your code rendered out on the internet (at a given ip, or domain name) rather than pointing your browser at a local file.  This of course means that others _( I )_ can see your work online rather than having to look over your shoulder, or pull down your code and open locally in my browser.  In large part, this is why I would like to introduce this sooner than later.
  -There are benifits for you too of course.  You will get a basic feeling for what a webserver does, a very brief look at branches in git, and an example of how folder structure is represented as paths in a url and how to link to them.
  +After some thought, and while we're on the subject, I think it may be a good time to introduce https://pages.github.com/[GitHub pages].  To put it simply, GitHub pages exposes a very simple https://en.wikipedia.org/wiki/Web_server[webserver] for files in a branch of a git repository.  A webserver _serves_ files to the _web_.  When your browser makes a request to a webserver the webserver will expose the files in its contol for the browser to render.  What this all amounts to is that you will be able to see your code rendered out on the internet (at a given ip, or domain name) just like when you point your browser at a local file as you have been.  This of course means that others ( I ) can see your work online rather than having to look over your shoulder, or pull down your code and open locally in my browser.  In large part, this is why I would like to introduce this sooner than later.
  +There are benifits for you too of course.  You will get a basic feeling for what a webserver does, and a very brief look at branches in git.
   
   === Enable GitHub Pages
  -We're going to do this on the github repository that you created in the last lesson, go ahead and navigate there in your browser.  Look to the sidebar and click on *settings* (it has a hammer and screwdriver icon.)  In the settings page you should see a section called *GitHub Pages* with some information on how to enable it.  Github pages looks for a branch in your repository called _gh-pages_ so we will need to make this branch and push it to github. A https://git-scm.herokuapp.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging[branch] in git can be thought of as a copy of your current history that you can continue to modify, without altering the _master_ branch. Almost like a fork in your breadcrumb trail.  At this point it's not real important to understand the branching concept fully, we're just touching on it briefly to setup GitHub pages.
  +We're going to do this on the github repository that you created in the last lesson, go ahead and navigate there in your browser.  Look to the sidebar and click on *settings* (it has a hammer and screwdriver icon.)  In the settings page you should see a section called *GitHub Pages* with some information on how to enable it.  Github pages looks for a specially named branch in your repository called _gh-pages_ so we will need to make this branch and push it to github. A https://git-scm.herokuapp.com/book/en/v2/Git-Branching-Basic-Branching-and-Merging[branch] in git can be thought of as a copy of your current history that you can continue to modify without altering the _master_ branch. Almost like a fork in your breadcrumb trail.  At this point it's not real important to understand the branching concept fully, we're just touching on it briefly to setup GitHub pages.
   
   ===== Create the gh-pages branch.
  -Jump over to your terminal window and navigate to your the directory where you setup your repository.  It might be a good idea to run `git status` to make sure everything is clean. If not go ahead and commit or remove changes that are pending. Now to create the new branch run:
  +Open a your terminal window and navigate to the directory where you setup your repository.  It might be a good idea to run `git status` to make sure everything is clean. If it is not, go ahead and commit or remove changes that are pending. 
  +
  +TIP: To remove any uncommitted changes, and bring your files back to the state of your last commit you can run `git reset --hard HEAD`. This command says _reset_ the repository to _HEAD_ (a shorthand for the most recent commit). The _--hard_ option means that your local files will be changed to match. Use this command with caution though, *it will delete any uncommitted changes*.
  +
  +Now to create the new gh-pages branch run:
   ```
   $>git branch gh-pages
   ```
  
positive.code: ```
  You may have noticed this is a lot like the `git push origin master` we have been doing.  In this case we're __push__ing to GitHub (_origin_) the branch _gh-pages_. Since this branch doesn't yet exist on GitHub, you recive a message that it has been created.
  
  Now jump back to your browser that has the settings page we navigated to earlier and refreh. You should now see a green notification that _"Your site is published at \http://<github-username>.github.io/<repository-name>"_
  
negative.code: * master
    remotes/origin/master
  ```
  NOTE: The `-a` in the previous command is an option to show both local and remote branches. If you run this command without it, it will only show the local branches
  
  The astrisk indicates the current _local_ branch you are on. We use `git checkout` to switch branches, so lets switch to our newly created gh-pages branch:
  ```
  $>git checkout gh-pages
  Switched to branch 'gh-pages'
  