anchor.diff:  
   ....
   Vagrant.configure(2) do |config|
  -  config.vm.box = "xenial64"
  +  config.vm.box = .....
     config.vm.provision             :shell, path: "./MyStudentID-Lab02.sh"
   end
   ....
  
positive.code: 
  We will work with a commercial implementation of the Git platform in this class provided by Github. You can create a free account on Github and host public code repositories, like the one we setup for this lab.
  
  NOTE: Everyone should setup an individual Github account. If you are working in teams, you have the option of either doing the next section individually, or choosing one team member to perform the git forking and cloning tasks.
  
  You will do the exercises in part 2 on the main server, not your VM (which you have now destroyed, right?).
  
  
negative.code: ....
  vagrant@xenial64:~$ cd /vagrant
  vagrant@xenial64:/vagrant$ ls
  README.md  starter.sh  YourStudentID-testfile.adoc  Vagrantfile
  ....
  
  If you examine the /vagrant directory, you will realize it has the same contents as your ~/examples directory on the class server. In fact, it's the exact same directory! What's going on here? The /vagrant directory in your virtual machine is linked to the ~/examples directory on the  host machine (class server). This virtual link provides an easy mechanism to
  