haskal
/
vagrant
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Changed "`destroy command`" to "`destroy` command" 

The word "command" was enclosed in a code block despite not being part of the actual command you would run at the CLI.
This commit is contained in:
James Thomas 2016-02-05 12:02:06 +00:00
parent 082e65291e
commit 52fa68f9f5
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
website/source/docs/cli/destroy.html.md
View File

@ -27,7 +27,7 @@ directory containing the `shutdown` command.
* `-f` or `--force` - Do not ask for confirmation before destroying. * `-f` or `--force` - Do not ask for confirmation before destroying.
<div class="alert alert-info"> <div class="alert alert-info">
The `destroy command` does not remove a box that may have been installed on The `destroy` command does not remove a box that may have been installed on
your computer during `vagrant up`. Thus, even if you run `vagrant destroy`, your computer during `vagrant up`. Thus, even if you run `vagrant destroy`,
the box installed in the system will still be present on the hard drive. To the box installed in the system will still be present on the hard drive. To
return your computer to the state as it was before `vagrant up` command, you return your computer to the state as it was before `vagrant up` command, you