From 2ecefe16707c55707827c2bbfbedf8976754da6b Mon Sep 17 00:00:00 2001 From: Justin Page Date: Wed, 18 Jun 2014 19:51:39 -0700 Subject: [PATCH] Update Teardown instructions explicitly. Explicitly define halting and destroying instructions. Leaves no room for implicit assumptions. --- .../v2/getting-started/teardown.html.md | 20 +++++++++---------- 1 file changed, 10 insertions(+), 10 deletions(-) diff --git a/website/docs/source/v2/getting-started/teardown.html.md b/website/docs/source/v2/getting-started/teardown.html.md index 919793dc9..764de1969 100644 --- a/website/docs/source/v2/getting-started/teardown.html.md +++ b/website/docs/source/v2/getting-started/teardown.html.md @@ -23,18 +23,18 @@ work. The downside is that the virtual machine still eats up your disk space, and requires even more disk space to store all the state of the virtual machine RAM on disk. -**Halting** the virtual machine will gracefully shut down the guest -operating system and power down the guest machine. You can use `vagrant up` -when you're ready to boot it again. The benefit of this method is that -it will cleanly shut down your machine, preserving the contents of disk, -and allowing it to be cleanly started again. The downside is that it'll -take some extra time to start from a cold boot, and the guest machine +**Halting** the virtual machine by calling `vagrant halt` will gracefully +shut down the guest operating system and power down the guest machine. +You can use `vagrant up` when you're ready to boot it again. The benefit of +this method is that it will cleanly shut down your machine, preserving the +contents of disk, and allowing it to be cleanly started again. The downside is +that it'll take some extra time to start from a cold boot, and the guest machine still consumes disk space. -**Destroying** the virtual machine will remove all traces of the guest -machine from your system. It'll stop the guest machine, power it down, -and remove all of the guest hard disks. Again, when you're ready to work -again, just issue a `vagrant up`. The benefit of this is that _no cruft_ +**Destroying** the virtual machine by calling `vagrant destroy` will remove +all traces of the guest machine from your system. It'll stop the guest machine, +power it down, and remove all of the guest hard disks. Again, when you're ready to +work again, just issue a `vagrant up`. The benefit of this is that _no cruft_ is left on your machine. The disk space and RAM consumed by the guest machine is reclaimed and your host machine is left clean. The downside is that `vagrant up` to get working again will take some extra time since it