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

Adjust command wording to match up

This commit is contained in:
Brian Cain 2019-02-07 13:35:47 -08:00
parent aff66822ef
commit 767346ce81
No known key found for this signature in database
GPG Key ID: 9FC4639B2E4510A0
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
website/source/docs/triggers/configuration.html.md
View File

@ -82,7 +82,7 @@ The trigger class takes various options.
## Trigger Types
Optionally, it is possible to define a trigger that executes around Vagrant subcommands,
Optionally, it is possible to define a trigger that executes around Vagrant commands,
hooks, and actions.
<div class="alert alert-warning">
@ -106,7 +106,7 @@ A trigger can be one of three types:
* `type` (symbol) - Optional
- `:action` - Action triggers run before or after a Vagrant action
- `:command` - Command triggers run before or after a Vagrant subcommand
- `:command` - Command triggers run before or after a Vagrant command
- `:hook` - Action hook triggers run before or after a Vagrant hook
These types determine when and where a defined trigger will execute.
@ -135,8 +135,8 @@ end
### Commands
Command typed triggers can be defined for any valid Vagrant subcommand. They will always
run before or after the subcommand.
Command typed triggers can be defined for any valid Vagrant command. They will always
run before or after the command.
The difference between this and the default behavior is that these triggers are
not attached to any specific guest, and will always run before or after the given