Merge pull request #39 from vchepkov/targets

change nodes to targets in README

Author: nmaludy

README.md

@@ -38,7 +38,7 @@
 A framework for building patching workflows. This module is designed to be used as building
 blocks for complex patching environments of Windows and Linux (RHEL, Ubuntu) systems.
 
-No Puppet agent is required on the end nodes. The node executing the patching will need to 
+No Puppet agent is required on the end targets. The node executing the patching will need to 
 have `bolt` installed.
 
 ## Setup
@@ -66,7 +66,7 @@ mod 'encore/patching'
 EOF
 
 bolt puppetfile install
-bolt plan run patching::available_updates --nodes group_a
+bolt plan run patching::available_updates --targets group_a
 
 # install rbvmomi for VMware snapshot support
 /opt/puppetlabs/bolt/bin/gem install --user-install rbvmomi
@@ -77,9 +77,9 @@ bolt plan run patching::available_updates --nodes group_a
 This module is designed to work in enterprise patching environments.
 
 Assumptions:
-* RHEL nodes are registered to Satellite / Foreman or the internet
-* Ubuntu nodes are registered to Landscape or the internet
-* Windows nodes are registered to WSUS and Chocolatey (optional)
+* RHEL targets are registered to Satellite / Foreman or the internet
+* Ubuntu targets are registered to Landscape or the internet
+* Windows targets are registered to WSUS and Chocolatey (optional)
 
 Registration to a central patching server is preferred for speed of software downloads 
 and control of phased patching promotions.
@@ -94,7 +94,7 @@ these central patching server tools.
 `patching` is designed around `bolt` tasks and plans. 
 
 Individual tasks have been written to accomplish targeted steps in the patching process.
-Examples: `patching::available_updates` is used to check for available updates on target nodes.
+Examples: `patching::available_updates` is used to check for available updates on targets.
 
 Plans are then used to pretty up output and tie tasks together.
 
@@ -129,14 +129,14 @@ This workflow consists of the following phases:
 
 ### Check for available updates
 
-This will reach out to all nodes in `group_a` in your inventory and check for any available
+This will reach out to all targets in `group_a` in your inventory and check for any available
 updates through the system's package manager:
 * RHEL = yum
 * Ubuntu = apt
 * Windows = Windows Update + Chocolatey (if installed)
 
 ``` shell
-bolt plan run patching::available_updates --nodes group_a
+bolt plan run patching::available_updates --targets group_a
 ```
 
 ### Disable monitoring
@@ -148,7 +148,7 @@ This plan/task utilizes the `remote` transport []
 
 
 ``` shell
-bolt plan run patching::monitoring_solarwinds --nodes group_a action=disable' monitoring_target=solarwinds
+bolt plan run patching::monitoring_solarwinds --targets group_a action=disable' monitoring_target=solarwinds
 ```
 
 ### Create snapshots
@@ -159,7 +159,7 @@ be the `uri` of the node the inventory file.
 ``` shell
 /opt/puppetlabs/bolt/bin/gem install rbvmomi
 
-bolt plan run patching::snapshot_vmware --nodes group_a action='create' vsphere_host='vsphere.domain.tld' vsphere_username='xyz' vsphere_password='abc123' vsphere_datacenter='dctr1'
+bolt plan run patching::snapshot_vmware --targets group_a action='create' vsphere_host='vsphere.domain.tld' vsphere_username='xyz' vsphere_password='abc123' vsphere_datacenter='dctr1'
 ```
 
 ### Perform pre-patching checks and actions
@@ -172,10 +172,10 @@ Best practice is to define and distribute these scripts as part of your normal P
 as part of othe role for that node.
 
 ``` shell
-bolt plan run patching::pre_update --nodes group_a
+bolt plan run patching::pre_update --targets group_a
 ```
 
-By default this executes the following scripts (nodes where the script doesn't exist are ignored):
+By default this executes the following scripts (targets where the script doesn't exist are ignored):
 * Linux = `/opt/patching/bin/pre_update.sh`
 * Windows = `C:\ProgramData\patching\pre_update.ps1`
 
@@ -236,7 +236,7 @@ Then, for each group:
 * `patching::snapshot_vmware action='delete'`
 
 ``` shell
-bolt plan run patching --nodes group_a
+bolt plan run patching --targets group_a
 ```
 
 ### Patching with Puppet Enterprise (PE)
@@ -275,7 +275,7 @@ in the inventory file.
 
 For details on all of the available configuration options, see [REFERENCE_CONFIGURATION.md](REFERENCE_CONFIGURATION.md)
 
-Example: Let's say we want to prevent some nodes from rebooting during patching.
+Example: Let's say we want to prevent some targets from rebooting during patching.
 This can be customized with the `patching_reboot_strategy` variable in inventory:
 
 ``` yaml