diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md index 4fa90b7d9..f66333a79 100644 --- a/website/source/docs/triggers/configuration.html.md +++ b/website/source/docs/triggers/configuration.html.md @@ -15,8 +15,7 @@ trigger should behave. The trigger class takes various options. -* `action` (symbol) - The first argument that comes after either __before__ or __after__ when defining a new trigger (For example when the action is `:up` : `config.trigger.before :up`). -Can be any valid Vagrant command. It also accepts a special value `:all` which will make the trigger fire for every action. An action can be ignored with the `ignore` setting if desired. +* `action` (symbol, array) - Expected to be a single symbol value, an array of symbols, or a _splat_ of symbols. The first argument that comes after either __before__ or __after__ when defining a new trigger. Can be any valid Vagrant command. It also accepts a special value `:all` which will make the trigger fire for every action. An action can be ignored with the `ignore` setting if desired. * `ignore` (symbol, array) - Symbol or array of symbols corresponding to the action that a trigger should not fire on. diff --git a/website/source/docs/triggers/index.html.md b/website/source/docs/triggers/index.html.md index ac24fb635..074e09f1d 100644 --- a/website/source/docs/triggers/index.html.md +++ b/website/source/docs/triggers/index.html.md @@ -34,9 +34,9 @@ end ``` Alternatively, the key `:all` could be given which would run the trigger for every -Vagrant command. This trigger will run before or after every Vagrant command. -This must include the ability to blacklist a command so that the trigger isn’t -run. The blacklist will be defined within the `:all` config block. +Vagrant command. This trigger will run before or after every Vagrant command. If +there is a command you don't want the trigger to run on, you can ignore that +command with the `ignore` option. ```ruby # single command trigger