Address feedback

website/source/docs/job-specification/group.html.md

@@ -53,8 +53,9 @@ job "docs" {
   within this group. This can be specified multiple times, to add a task as part
   of the group.
 
-- `vault` <code>([Vault][]: nil)</code> - Specifies the configuration options
-  for connecting the tasks in this group to Vault.
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this group. Overrides a `vault` block set at the
+  `job` level.
 
 ## `group` Examples
 

website/source/docs/job-specification/job.html.md

@@ -87,8 +87,8 @@ job "docs" {
 - `update` <code>([Update][update]: nil)</code> - Specifies the task's update
   strategy. When omitted, rolling updates are disabled.
 
-- `vault` <code>([Vault][]: nil)</code> - Specifies the configuration options
-  for connecting the tasks in this job to Vault.
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by all tasks in this job.
 
 - `vault_token` `(string: "")` - Specifies the Vault token that proves the
   submitter of the job has access to the specified policies in the

website/source/docs/job-specification/task.html.md

@@ -66,8 +66,9 @@ job "docs" {
   defaults to the same user as the Nomad client. This can only be set on Linux
   platforms.
 
-- `vault` <code>([Vault][]: nil)</code> - Specifies the configuration options
-  for connecting this task to Vault.
+- `vault` <code>([Vault][]: nil)</code> - Specifies the set of Vault policies
+  required by the task. This overrides any `vault` block set at the `group` or
+  `job` level.
 
 ## `task` Examples