diff --git a/docs/getting-started/boxes.md b/docs/getting-started/boxes.md
index f31185f84..7cb14371c 100644
--- a/docs/getting-started/boxes.md
+++ b/docs/getting-started/boxes.md
@@ -25,15 +25,15 @@ for all the servers, so we'll instead cover a more simple case, although
 the rails box was created completely with Vagrant provisioning.
 
 Vagrant supports adding boxes from both the local filesystem and an
-HTTP URL. Beginning running the following command so it can begin downloading
+HTTP URL. Begin running the following command so it can begin downloading
 while box installation is covered in more detail:
 
 {% highlight bash %}
 $ vagrant box add getting_started http://files.vagrantup.com/getting_started.box
 {% endhighlight %}
 
-Installed boxes reside in ~/.vagrant/boxes, and they are global to the current vagrant 
-installation. This means that once the rails box has been added, it can be used by 
+Installed boxes reside in ~/.vagrant/boxes, and they are global to the current vagrant
+installation. This means that once the rails box has been added, it can be used by
 multiple projects at the same time. Each project uses the box as a _base_ only, so once the
 project VM is created, modifications can be made without affecting other
 projects which may use the same box.
@@ -47,7 +47,7 @@ the filename and logical name are equal in this case.
 ## Removing Boxes
 
 Just as easily as they're added, boxes can be removed as well. The following
-is an example command to remove a box. 
+is an example command to remove a box.
 
 **Do not run this command if you're following the guide. It is just an example.**
 
diff --git a/docs/getting-started/packaging.md b/docs/getting-started/packaging.md
index dc5b50c2a..e001b5eae 100644
--- a/docs/getting-started/packaging.md
+++ b/docs/getting-started/packaging.md
@@ -42,6 +42,18 @@ Vagrant::Config.run do |config|
 end
 {% endhighlight %}
 
+<div class="info">
+  <h3>What's with the MAC address?</h3>
+  <p>
+    When an OS is installed, it typically sets up the MAC address associated
+    with the <code>eth0</code> network interface, which allows the VM to connect to the
+    internet. But when importing a base, VirtualBox changes the MAC address
+    to something new, which breaks <code>eth0</code>. The MAC address of the base must
+    be persisted in the box Vagrantfile so that Vagrant can setup the MAC address
+    to ensure internet connectivity.
+  </p>
+</div>
+
 ## Packaging the Project
 
 Run the following code to package the environment up:
diff --git a/docs/getting-started/why.md b/docs/getting-started/why.md
index 9d620b6aa..d76ad9f34 100644
--- a/docs/getting-started/why.md
+++ b/docs/getting-started/why.md
@@ -20,7 +20,7 @@ to create its virtual machines and then uses [Chef](http://www.opscode.com/chef)
 
 Maintaining consistent development environments over multiple projects is simply an
 unfeasible task for a modern web developer. Each project depends on its own libraries,
-message queue systems, databases, framework, and more each with their own versions.
+message queue systems, databases, framework, and more, each with their own versions.
 In addition to the dependencies, running all these on a single home machine and remembering
 to turn it all off at the end of the day or when working on other projects is also unfeasible.
 Vagrant gives you the tools to build unique development environments for each project once