anchor.diff:  
   If you get an error with "vagrant up" like this:
   
  -````
  -An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
  -
  -
  -Couldn't open file /home/student/akou0009/vagrant/precise64
  -````
  +
  + An error occurred while downloading the remote file. The error message, if any, is reproduced below. Please fix this error and try again.
  +
  + Couldn't open file /home/student/akou0009/vagrant/precise64
   
   try
   
  -    vagrant box add "precise64" http://files.vagrantup.com/precise64.box
  + vagrant box add "precise64" http://files.vagrantup.com/precise64.box
   
   Now, let's try something that will not work:
   
  
positive.code: 
  When you create a new virtual machine with Vagrant and VirtualBox, Vagrant needs to be able to talk to it on your behalf, and uses .ssh for this purpose. Just as we created a private key for you to hold on your laptop, with a matching public key on the server, so you need to have ANOTHER private/public key pair to communicate between your ssh session running directly on seis660, and your new virtual machine. And, because the Vagrant machine is pre-baked (more on this to come), you have to start by using a predefined key pair that comes with Vagrant.
  
  Review the image below. Right-click and open the image below in its own window or tab if it is too small.  ![architecture](Resources/sshDetails.jpg)
  
  
  So, let's copy the key to your own .ssh directory. First, we need to clean up our failed attempt:
  
  
negative.code: 
  In this lab you will learn more about IT infrastructure by running Vagrant and learning basic "infrastructure as code" principles.
  
  ==  Running Vagrant on the Course Server
  
  Vagrant is already installed on the SEIS660 course server, but you need to take a few steps before you can use it.
  Assuming you have .ssh configured and have logged in, you should find yourself in your default directory.
  
  IMPORTANT: In the following instructions when you see *teststu1*, substitute your user id.
  
  Do not type the "$" symbol - this represents the command prompt you see when you log into Linux. It may also be a "#" or have some directory information in front of it, e.g.
  
  