Assorted renaming and string changes

docs/credentials/README.md

@@ -1 +1 @@
-This folder contains documentation related to credentials in AWX / Ansible Tower.
+This folder contains documentation related to credentials in AWX.

docs/credentials/extract_credentials.md

@@ -4,10 +4,10 @@ Extracting Credential Values
 AWX stores a variety of secrets in the database that are either used for automation or are a result of automation. These secrets include:
 
 - all secret fields of all credential types (passwords, secret keys, authentication tokens, secret cloud credentials)
-- secret tokens and passwords for external services defined in Ansible Tower settings
+- secret tokens and passwords for external services defined in AWX settings
 - "password" type survey fields entries
 
-To encrypt secret fields, Tower uses AES in CBC mode with a 256-bit key for encryption, PKCS7 padding, and HMAC using SHA256 for authentication.
+To encrypt secret fields, AWX uses AES in CBC mode with a 256-bit key for encryption, PKCS7 padding, and HMAC using SHA256 for authentication.
 
 If necessary, credentials and encrypted settings can be extracted using the AWX shell:
 

docs/credentials/multi_credential_assignment.md

@@ -168,7 +168,7 @@ Vault credentials in AWX now have an optional field, `vault_id`, which is
 analogous to the `--vault-id` argument to `ansible-playbook`.  To run
 a playbook which makes use of multiple Vault passwords:
 
-1.  Make a Vault credential in Tower for each Vault password; specify the Vault
+1.  Make a Vault credential in AWX for each Vault password; specify the Vault
     ID as a field on the credential and input the password (which will be
     encrypted and stored).
 2.  Assign multiple Vault credentials to the job template via the new