Fix typos in the vagrant builder doc

This commit is contained in:
Vadym Haidamaka 2019-03-12 05:07:55 +02:00
parent 6e442e616c
commit 535dfd9333
1 changed files with 3 additions and 3 deletions

View File

@ -27,7 +27,7 @@ You can change the behavior so that the builder doesn't destroy the box by
setting the `teardown_method` option. You can change the behavior so the builder setting the `teardown_method` option. You can change the behavior so the builder
doesn't package it (not all provisioners support the `vagrant package` command) doesn't package it (not all provisioners support the `vagrant package` command)
by setting the `skip package` option. You can also change the behavior so that by setting the `skip package` option. You can also change the behavior so that
rather than inititalizing a new Vagrant workspace, you use an already defined rather than initializing a new Vagrant workspace, you use an already defined
one, by using `global_id` instead of `source_box`. one, by using `global_id` instead of `source_box`.
## Configuration Reference ## Configuration Reference
@ -76,8 +76,8 @@ one, by using `global_id` instead of `source_box`.
{{ .SyncedFolder }}, which correspond to the Packer options `box_name` and {{ .SyncedFolder }}, which correspond to the Packer options `box_name` and
`synced_folder` `synced_folder`
- `skip_add` (string) - Don't call "vagrant add" to add the box to your local - `skip_add` (bool) - Don't call "vagrant add" to add the box to your local
environment; this is necesasry if you want to launch a box that is already environment; this is necessary if you want to launch a box that is already
added to your vagrant environment. added to your vagrant environment.
- `teardown_method` (string) - Whether to halt, suspend, or destroy the box when - `teardown_method` (string) - Whether to halt, suspend, or destroy the box when