From 9ea3ec24cac35bdcf29c3eb0e1a551866ea5f0c7 Mon Sep 17 00:00:00 2001 From: beeankha Date: Mon, 13 May 2019 15:46:24 -0400 Subject: [PATCH] Address comments/suggested changes --- docs/inventory_plugins.md | 4 ++-- docs/notification_system.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/inventory_plugins.md b/docs/inventory_plugins.md index ce4fcdc57319..1d60a337cb14 100644 --- a/docs/inventory_plugins.md +++ b/docs/inventory_plugins.md @@ -47,7 +47,7 @@ More hostvars will appear if the inventory plugins are used. To maintain backwar A small number of hostvars will be lost because of general deprecation needs. -#### Host nNames +#### Host Names In many cases, the host names will change. In all cases, accurate host tracking will still be maintained via the host `instance_id`. (after: https://github.com/ansible/awx/pull/3362) @@ -68,7 +68,7 @@ The `inputs` for this credential constitute one source of data for running inven - `instance_filters` - `group_by` -The way these data are applied to the environment (including files and environment vars) is highly dependent on the specific source. +The way this data is applied to the environment (including files and environment vars) is highly dependent on the specific source. With plugins, the inventory file may reference files that contain secrets from the credential. With scripts, typically an environment variable will reference a filename that contains a ConfigParser format file with parameters for the update, and possibly including fields from the credential. diff --git a/docs/notification_system.md b/docs/notification_system.md index d346da1ca20e..e3819f44ef32 100644 --- a/docs/notification_system.md +++ b/docs/notification_system.md @@ -17,7 +17,7 @@ Notification templates assigned at certain levels will inherit notifications def * Job Templates will use notifications defined on it as well as inheriting notifications from the Project used by the Job Template and from the Organization that it is listed under (via the Project). * Project Updates will use notifications defined on the project and will inherit notifications from the Organization associated with it. -* Inventory Updates will use notifications defined on the Organization under which it is listed. +* Inventory Updates will use notifications defined on the Organization it is in. * Ad-hoc commands will use notifications defined on the Organization with which that inventory is associated. ## Workflow