anchor.diff:  ```
   After the command completes, go back to your browser and refresh your repository page. You should see you nice new readme file rendered in all it's glory.
   
  -From here, take a little time and play with this workflow.  Make some changes to the html file or the readme or both. Commit them and push them up to github.  Add other files if you want, and commit and push those.  Just get used to the make changes > add/commit > push sequence.  If you haven't already continue to explore the repository page and the links therein.  Especially note the "commits" link just above the branch dropdown. You can see you commit history all laid out, and even drill down to view the actual changes.
  +From here, take a little time and play with this workflow.  Make some changes to the html file or the readme or both. Commit them and push them up to github. You don't have to push one commit at a time, you can make several before you do a push. It still works the same way. Add other files if you want, and commit and push those.  Just get used to the sequence: 
  +
  +. make changes 
  +. add/commit
  +. repeat 1 and 2 until ready to share
  +. push to the remote
  +
  +If you haven't already continue to explore the repository page and the links therein.  Especially note the "commits" link just above the branch dropdown. You can see your commit history log, and even drill down to view the actual changes.
   
   
   
  +== Pshew!
   This was a long one with a lot of information. Go slow and play around with it. Let things sink in a little bit.  While you are messing around on github, go ahead and follow me https://github.com/rh0 it will let me know what your github username is, so I can start to look over your work as we progress. Dun dun dun....
positive.code: 
  By running these commands on your local repository you have done a couple things. The first command says to _add_ a _remote_ repository (called _origin_) and point it at our newly created github repository. The second command says to _push_ local commits (remember making those) to _origin_ (the remote repository) on branch _master_.
  
  NOTE: If you are curious the `-u` option in the push command is short for "set __u__pstream tracking" and tells git that the remote branch you pushed to will track the branch you pushed from. Since we are only dealing with one branch (_master_) this isn't so important. *You don't need to include the `-u` in any future pushes*
  
  So after running these commands, if everything went well, refresh the repository page in your browser and you should see your spiffy `index.html` file sitting on the screen.  Check out the information on this page, and click around and explore a bit. GitHub shows a lot of information about the state of your (remote) repository, and is a great way to review commits, and see just what's going on.
  
  
negative.code: 
  If you're still with me then GREAT JOB! You've done a lot.  But things are still looking a little bare up on your github repository page. We need to create a README file to let the world know about our super sweet html file.  Now you can of course just click the "Add a README" button and let github walk you through it, but I think it is worth while to create this file locally, and push it up to the repository. This will demonstrate a typical workflow when working with a remote.
  
  Jump over to your text editor and create a new file. Do a "save as" and call it `README.md` and save it in your `basic-html` folder. The same place your `index.html` file is.  The `.md` suffix denotes a https://en.wikipedia.org/wiki/Markdown[markdown] file.  If you are not familiar with markdown, it's simply a formatting shorthand. GitHub has its own https://help.github.com/articles/markdown-basics/[flavor of markdown that you can review]. So in your newly created file add some markdown content describing your awesome repository. Mess with it, and put whatever you want. Something like:
  
  [source,markdown]
  ----
  