Product-related updates. (#74454)

docs/docsite/rst/community/communication.rst

@@ -18,7 +18,7 @@ Mailing list information
 Ansible has several mailing lists.  Your first post to the mailing list will be moderated (to reduce spam), so please allow up to a day or so for your first post to appear.
 
 * `Ansible Announce list <https://groups.google.com/forum/#!forum/ansible-announce>`_ is a read-only list that shares information about new releases of Ansible, and also rare infrequent event information, such as announcements about an upcoming AnsibleFest, which is our official conference series. Worth subscribing to!
-* `Ansible AWX List <https://groups.google.com/forum/#!forum/awx-project>`_ is for `Ansible AWX <https://github.com/ansible/awx>`_ the upstream version of `Red Hat Ansible Tower <https://www.ansible.com/products/tower>`_
+* `Ansible AWX List <https://groups.google.com/forum/#!forum/awx-project>`_ is for `Ansible AWX <https://github.com/ansible/awx>`_ 
 * `Ansible Container List <https://groups.google.com/forum/#!forum/ansible-container>`_ is for users and developers of the Ansible Container project.
 * `Ansible Development List <https://groups.google.com/forum/#!forum/ansible-devel>`_ is for learning how to develop on Ansible, asking about prospective feature design, or discussions about extending ansible or features in progress.
 * `Ansible Lockdown List <https://groups.google.com/forum/#!forum/ansible-lockdown>`_ is for all things related to Ansible Lockdown projects, including DISA STIG automation and CIS Benchmarks.
@@ -59,7 +59,7 @@ Many of our community `Working Groups <https://github.com/ansible/community/wiki
 
 - `Amazon (AWS) Working Group <https://github.com/ansible/community/wiki/AWS>`_ - ``#ansible-aws``
 - `Ansible Lockdown Working Group <https://github.com/ansible/community/wiki/Lockdown>`_ | `gh/ansible/ansible-lockdown <https://github.com/ansible/ansible-lockdown>`_ - ``#ansible-lockdown``- Security playbooks/roles
-- `AWX Working Group <https://github.com/ansible/awx>`_ - ``#ansible-awx`` - Upstream for Ansible Tower
+- `AWX Working Group <https://github.com/ansible/awx>`_ - ``#ansible-awx``
 - `Azure Working Group <https://github.com/ansible/community/wiki/Azure>`_ - ``#ansible-azure``
 - `Community Working Group <https://github.com/ansible/community/wiki/Community>`_ - ``#ansible-community`` - Including Meetups
 - `Container Working Group <https://github.com/ansible/community/wiki/Container>`_ - ``#ansible-container``
@@ -95,13 +95,13 @@ IRC meetings
 The Ansible community holds regular IRC meetings on various topics, and anyone who is interested is invited to
 participate. For more information about Ansible meetings, consult the `meeting schedule and agenda page <https://github.com/ansible/community/blob/master/meetings/README.md>`_.
 
-Ansible Tower support questions
-===============================
+Ansible Automation Platform support questions
+=============================================
 
-Red Hat Ansible `Tower <https://www.ansible.com/products/tower>`_ is a UI, Server, and REST endpoint for Ansible.
-The Red Hat Ansible Automation subscription contains support for Ansible, Ansible Tower, Ansible Automation for Networking, and more.
+Red Hat Ansible `Automation Platform <https://www.ansible.com/products/automation-platform>`_ is a subscription that contains support, certified content, and tooling for Ansible including
+content management, a controller, UI and REST API.
 
-If you have a question about Ansible Tower, visit `Red Hat support <https://access.redhat.com/products/ansible-tower-red-hat/>`_ rather than using the IRC channel or the general project mailing list.
+If you have a question about Ansible Automation Platform, visit `Red Hat support <https://access.redhat.com/products/red-hat-ansible-automation-platform/>`_ rather than using the IRC channel or the general project mailing list.
 
 The Bullhorn
 ============

docs/docsite/rst/community/other_tools_and_programs.rst

@@ -115,7 +115,7 @@ Other tools
 - `Ansigenome <https://github.com/nickjj/ansigenome>`_ - a command line tool designed to help you manage your Ansible roles.
 - `ARA <https://github.com/openstack/ara>`_ - records Ansible playbook runs and makes the recorded data available and intuitive for users and systems by integrating with Ansible as a callback plugin.
 - `Awesome Ansible <https://github.com/jdauphant/awesome-ansible>`_ - a collaboratively curated list of awesome Ansible resources.
-- `AWX <https://github.com/ansible/awx>`_ - provides a web-based user interface, REST API, and task engine built on top of Ansible. AWX is the upstream project for Red Hat Ansible Tower, part of the Red Hat Ansible Automation subscription.
+- `AWX <https://github.com/ansible/awx>`_ - provides a web-based user interface, REST API, and task engine built on top of Ansible. Red Hat Ansible Automation Platform includes code from AWX.
 - `Mitogen for Ansible <https://mitogen.networkgenomics.com/ansible_detailed.html>`_ - uses the `Mitogen <https://github.com/dw/mitogen/>`_ library to execute Ansible playbooks in a more efficient way (decreases the execution time).
 - `nanvault <https://github.com/marcobellaccini/nanvault>`_ - a standalone tool to encrypt and decrypt files in the Ansible Vault format, featuring UNIX-style composability.
 - `OpsTools-ansible <https://github.com/centos-opstools/opstools-ansible>`_ - uses Ansible to configure an environment that provides the support of `OpsTools <https://wiki.centos.org/SpecialInterestGroup/OpsTools>`_, namely centralized logging and analysis, availability monitoring, and performance monitoring.

docs/docsite/rst/community/release_managers.rst

@@ -13,7 +13,6 @@ coordinate between:
 * Contributors without commit privileges
 * The community
 * Ansible documentation team
-* Ansible Tower team
 
 Pre-releases: what and why
 ==========================
@@ -70,7 +69,7 @@ The last RC should be as close to the final as possible. The following things ma
 .. note:: We want to specifically emphasize that code (in :file:`bin/`, :file:`lib/ansible/`, and
     :file:`setup.py`) must be the same unless there are extraordinary extenuating circumstances.  If
     there are extenuating circumstances, the Release Manager is responsible for notifying groups
-    (like the Tower Team) which would want to test the code.
+    which would want to test the code.
 
 
 Ansible release process

docs/docsite/rst/dev_guide/developing_api.rst

@@ -14,7 +14,7 @@ write plugins, and you can plug in inventory data from external data sources.  T
 gives a basic overview and examples of the Ansible execution and playbook API.
 
 If you would like to use Ansible programmatically from a language other than Python, trigger events asynchronously,
-or have access control and logging demands, please see the `Ansible Tower documentation <https://docs.ansible.com/ansible-tower/>`_.
+or have access control and logging demands, please see the `AWX project <https://github.com/ansible/awx/>`_.
 
 .. note:: Because Ansible relies on forking processes, this API is not thread safe.
 

docs/docsite/rst/dev_guide/developing_inventory.rst

@@ -469,7 +469,7 @@ An easy way to see how this should look is using :ref:`ansible-inventory`, which
        Get started with developing a module
    :ref:`developing_plugins`
        How to develop plugins
-   `Ansible Tower <https://www.ansible.com/products/tower>`_
+   `AWX <https://github.com/ansible/awx>`_
        REST API endpoint and GUI for Ansible, syncs with dynamic inventory
    `Development Mailing List <https://groups.google.com/group/ansible-devel>`_
        Mailing list for development topics

docs/docsite/rst/dev_guide/developing_modules_documenting.rst

@@ -233,8 +233,8 @@ Linking and other format macros within module documentation
 
 You can link from your module documentation to other module docs, other resources on docs.ansible.com, and resources elsewhere on the internet with the help of some pre-defined macros. The correct formats for these macros are:
 
-* ``L()`` for links with a heading. For example: ``See L(Ansible Tower,https://www.ansible.com/products/tower).`` As of Ansible 2.10, do not use ``L()`` for relative links between Ansible documentation and collection documentation.
-* ``U()`` for URLs. For example: ``See U(https://www.ansible.com/products/tower) for an overview.``
+* ``L()`` for links with a heading. For example: ``See L(Ansible Automation Platform,https://www.ansible.com/products/automation-platform).`` As of Ansible 2.10, do not use ``L()`` for relative links between Ansible documentation and collection documentation.
+* ``U()`` for URLs. For example: ``See U(https://www.ansible.com/products/automation-platform) for an overview.``
 * ``R()`` for cross-references with a heading (added in Ansible 2.10). For example: ``See R(Cisco IOS Platform Guide,ios_platform_options)``.  Use the RST anchor for the cross-reference. See :ref:`adding_anchors_rst` for details.
 * ``M()`` for module names. For example: ``See also M(ansible.builtin.yum) or M(community.general.apt_rpm)``.
 

docs/docsite/rst/dev_guide/style_guide/spelling_word_choice.rst

@@ -12,7 +12,7 @@ Spell out the acronym before using it in alone text, such as "The Embedded DevKi
 
 Applications
 +++++++++++++++++++
-When used as a proper name, use the capitalization of the product, such as GNUPro, Source-Navigator, and Ansible Tower. When used as a command, use lowercase as appropriate, such as "To start GCC, type ``gcc``."
+When used as a proper name, use the capitalization of the product, such as GNUPro or Source-Navigator. When used as a command, use lowercase as appropriate, such as "To start GCC, type ``gcc``."
 
 .. note::
 

docs/docsite/rst/dev_guide/style_guide/trademarks.rst

@@ -12,7 +12,7 @@ General Rules:
 
 Trademarks should be used on 1st references on a page or within a section.
 
-Use Red Hat® Ansible Tower® or Ansible®, on first reference when referring to products.
+Use Red Hat® Ansible® Automation Platform or Ansible®, on first reference when referring to products.
  
 Use "Ansible" alone as the company name, as in "Ansible announced quarterly results," which is not marked.
 
@@ -38,7 +38,7 @@ Always use proper trademark form and spelling.
 Never use a trademark as a noun. Always use a trademark as an adjective modifying the noun.
 
     Correct:
-    Red Hat® Ansible Tower® system performance is incredible.
+    Red Hat® Ansible® Automation Platform system performance is incredible.
 
     Incorrect:
     Ansible's performance is incredible.
@@ -46,7 +46,7 @@ Never use a trademark as a noun. Always use a trademark as an adjective modifyin
 Never use a trademark as a verb. Trademarks are products or services, never actions.
 
     Correct:
-    "Orchestrate your entire network using Red Hat® Ansible Tower®."
+    "Orchestrate your entire network using Red Hat® Ansible® Automation Platform."
     
     Incorrect:
     "Ansible your entire network."
@@ -54,7 +54,7 @@ Never use a trademark as a verb. Trademarks are products or services, never acti
 Never modify a trademark to a plural form. Instead, change the generic word from the singular to the plural.
 
     Correct:
-    "Corporate demand for Red Hat® Ansible Tower® configuration software is surging."
+    "Corporate demand for Red Hat® Ansible® Automation Platform software is surging."
 
     Incorrect:
     "Corporate demand for Ansible is surging."
@@ -81,7 +81,6 @@ The mark consists of the letter "A" in a shaded circle. As of 5/11/15, this was
 Common Ansible Trademarks
 +++++++++++++++++++++++++++++++++++++++
 * Ansible®
-* Ansible Tower®
 
 Other Common Trademarks and Resource Sites:
 ++++++++++++++++++++++++++++++++++++++++++++++++