Website updates based on feedback

hashicorp · Apr 23, 2018 · 1eabd09 · 1eabd09
1 parent daffd87
commit 1eabd09
Show file tree

Hide file tree

Showing 2 changed files with 5 additions and 6 deletions.
diff --git a/website/source/docs/triggers/configuration.html.md b/website/source/docs/triggers/configuration.html.md
@@ -3,19 +3,18 @@ layout: "docs"
 page_title: "Vagrant Triggers Configuration"
 sidebar_current: "triggers-configuration"
 description: |-
-  Documentation of various configuration options for Vagrnat Triggers
+  Documentation of various configuration options for Vagrant Triggers
 ---
 
 # Configuration
 
-Vagrant Triggers has a few various options that can be set which define how the
-trigger should behave.
+Vagrant Triggers has a few options to define trigger behavior.
 
 ## Options
 
 The trigger class takes various options.
 
-* `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.
+* `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. A list of valid core commands can be found [here](/docs/cli).
 
 * `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
@@ -12,7 +12,7 @@ As of version 2.1.0, Vagrant is capable of executing machine triggers _before_ o
 _after_ Vagrant commands.
 
 Each trigger is expected to be given a command key for when it should be fired
-during the Vagrant command life cycle. These could be defined as a single key or
+during the Vagrant command lifecycle. These could be defined as a single key or
 an array which acts like a _whitelist_ for the defined trigger.
 
 
@@ -76,7 +76,7 @@ config.vm.define "ubuntu" do |ubuntu|
 end
 ```
 
-Global and machine scopped triggers will execute in the order that they are
+Global and machine-scoped triggers will execute in the order that they are
 defined within a Vagrantfile. Take for example an abstracted Vagrantfile:
 
 ```