anchor.diff:  end
   ....
   
  -Vagrant up your machine and ssh into it, verify that your script has been run.
  +Vagrant up your machine and ssh into it, verify that your script has been run. What happened here? Vagrant automatically executed your shell script on the new virtual machine after it started up.
  +
  +Verify that the following tasks were successfully completed on the virtual machine:
   
   . Directory "main" properly configured in /vagrant
   . git installed (run git --version)
  
positive.code:  create mode 100755 YourStudentID-Lab02.sh
  ....
  
  
  
  In reviewing the directory structure, there are duplicate directories. Also, it is getting messy with three directories at the same level.
  
  Fix the directory creation logic so that
  
  1. there are not duplicate C and D directories (you will need to use another letter).
  2. all the directories are inside one called "main"
  
  Run it & confirm it works.
  
  ....
  vagrant@vagrant:/vagrant$ tree
  
negative.code: example-Instructions.md  LICENSE  README.md  resources  starter.sh  YourStudentID-testfile.adoc  Vagrantfile
  ....
  
  If you examine the /vagrant directory, you will realize it has the same contents as your ~/example 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 ~/example directory on the  host machine (class server). This virtual link provides an easy mechanism to
  share and move files between your virtual machine and the host server. You should see your *-testfile.adoc in the /vagrant directory file listing.
  
  Now for the main work of this section:
  
  Starting with starter.sh, write a shell script that automates:
  