anchor.diff:  end
   ....
   
  -You used a shell provisioner in your previous lab to apply your script to your new VM. But what's this? In the first line in the example above, it's commented out here (the # means that Vagrant won't execute that line).
  -
  -Instead, we are starting to use Chef. As mentioned in the  http://dm-academy.github.io/aitm/#_policy_based_approaches[readings for Session 02], Chef is a configuration management system.
  +You used a shell provisioner in your previous lab to apply your script to your new VM. But what's this? The first line in the example above is commented out (the # means that Vagrant won't execute that line).
  +
  +Rather than using another provisioner to install software on our VM, we are starting to use Chef. As mentioned in the  http://dm-academy.github.io/aitm/#_policy_based_approaches[readings for Session 02], Chef is a configuration management system.
   
   Now, http://searchaws.techtarget.com/definition/Opscode-Chef[read a bit about Chef] and https://docs.chef.io/chef_quick_overview.html[a bit more] before you continue.
   
  -Now, a full treatment of Chef is beyond the scope of this class. However, you should look at a few things. You should still be in your Calavera directory. Run tree:
  +A full treatment of Chef is beyond the scope of this class. However, you should understand a few things. You should still be in your Calavera directory. Run the tree command:
   
   ....
   YourStudentID@serverXXX:~/Calavera$ tree
  
positive.code: 
  == A look at the application
  
  Let's look at what goes into making this little app work. First, how did it get there? Exit from your ssh into the VM, if you are still in there. Be sure you are in the Calavera directory.
  
  You can see the resources used by the application if you go:
  
  
negative.code: 
  *Have a look at some of them.*  Use "cat."
  
    YourStudentID@serverXXX:~/Calavera$ cat cookbooks/localAnt/recipes/default.rb
  
  The combination of these recipes precisely describes what the virtual machine will look like. If you delete a VM and bring it back up, it should look exactly the same every time.
  
  Now, the current Vagrantfile is a little dangerous, because if you type "vagrant up" it will try to bring up ALL of the machines. So, I have created a branch in git with a Vagrantfile for just the manos machine. Let's switch to that.
  
  Return to the Calavera base directory and issue the following commands:
  
  ....
  YourStudentID@serverXXX:~/Calavera$ cd ~/Calavera/
  