ansible · EMcWhinn · Jan 22, 2026 · Jan 19, 2026 · Jan 21, 2026 · Jan 21, 2026
diff --git a/downstream/assemblies/analytics/assembly-automation-savings-planner.adoc b/downstream/assemblies/analytics/assembly-automation-savings-planner.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-automation-savings-planner-ctxt
 
-= About the {planner}
+= Plan, track, and analyze returns with {planner}
 
 [role="_abstract"]
 An automation savings plan gives you the ability to plan, track, and analyze the potential efficiency and cost savings of your automation initiatives. Use automation analytics to create an automation savings plan by defining a list of tasks needed to complete an automation job.

diff --git a/downstream/assemblies/analytics/assembly-evaluating-automation-return.adoc b/downstream/assemblies/analytics/assembly-evaluating-automation-return.adoc
@@ -7,7 +7,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-evaluating-automation-return-ctxt
 
-= About Automation Calculator
+= Use automation calculator to determine automation savings
 
 [role="_abstract"]
 The automation calculator provides graphs, metrics and calculations that help you determine the total savings on your investment in automated processes.

diff --git a/downstream/assemblies/analytics/assembly-insights-reports.adoc b/downstream/assemblies/analytics/assembly-insights-reports.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-insights-reports-ctxt
 
-= Viewing your reports on {PlatformName}
+= Get a comprehensive visual overview of automation with reports
 
 [role="_abstract"]
 The reports feature on the {PlatformName} provides users with a visual overview of their automation efforts across different teams by using Ansible.

diff --git a/downstream/assemblies/analytics/assembly-using-job-explorer.adoc b/downstream/assemblies/analytics/assembly-using-job-explorer.adoc
@@ -6,7 +6,7 @@ ifdef::context[:parent-context: {context}]
 
 :context: assembly-using-job-explorer-ctxt
 
-= About the Job Explorer
+= View data about automation jobs across your organization
 
 [role="_abstract"]
 The *Job Explorer* provides a detailed view of jobs run on {ControllerName} clusters across your organizations. You can access the *Job Explorer* by selecting {MenuAAJobExplorer} from the navigation panel or using the drill-down view available across each of the application's charts.

diff --git a/...automation-dashboard/assembly-appendix-inventory-file-automation-dashboard.adoc b/...automation-dashboard/assembly-appendix-inventory-file-automation-dashboard.adoc
@@ -1,9 +1,9 @@
 :_mod-docs-content-type: ASSEMBLY
 
 [id="assembly-appendix-inventory-file-automation-dashboard"]
-= Appendix
+= Inventory file variables for {AutomationDashboardName}
 
 [role="_abstract"]
-The inventory variables required by the {AutomationDashboardName} installer are described in the following table: 
+The inventory variables required by the {AutomationDashboardName} installation program are described in the following table: 
 
 include::automation-dashboard/ref-automation-dashboard-inventory-variables.adoc[leveloffset=+1]
diff --git a/downstream/assemblies/builder/assembly-MCP-servers-and-EE.adoc b/downstream/assemblies/builder/assembly-MCP-servers-and-EE.adoc
@@ -10,7 +10,7 @@ An MCP eliminates the need for custom integrations by providing a universal "lan
 
 The MCP operates using a client-server architecture:
 
-[cols="a,a", options="header"]
+[cols="a,a,a", options="header"]
 |===
 | Component | Role | Description
 | MCP Host | The application environment | This is where the user interacts with the AI, such as an AI-powered IDE like VS Code or a chatbot interface.

diff --git a/downstream/assemblies/platform/assembly-controlling-data-collection.adoc b/downstream/assemblies/platform/assembly-controlling-data-collection.adoc
@@ -3,7 +3,7 @@
 ifdef::context[:parent-context: {context}]
 
 [id="assembly-controlling-data-collection"]
-= Managing usability analytics and data collection from {ControllerName}
+= Manage analytics and data collection in {PlatformNameShort}
 
 :context: data-collection
 

diff --git a/downstream/modules/analytics/con-drill-down.adoc b/downstream/modules/analytics/con-drill-down.adoc
@@ -6,7 +6,7 @@
 
 [id="con-drill-down"]
 
-= Drilling down into cluster  data
+= Change your {analytics} settings
 
 [role="_abstract"]
 You can drill down into cluster data to review more detailed information about successful or failed jobs.

diff --git a/downstream/modules/analytics/proc-calculating-automation.adoc b/downstream/modules/analytics/proc-calculating-automation.adoc
@@ -6,7 +6,7 @@
 
 [id="proc-calculating_automation"]
 
-= Calculating your automation savings
+= Calculate your automation savings
 
 [role="_abstract"]
 The *Automation Calculator* produces its default total savings figure based on estimates for each variable.

diff --git a/downstream/modules/analytics/proc-create-savings-plan.adoc b/downstream/modules/analytics/proc-create-savings-plan.adoc
@@ -6,7 +6,7 @@
 
 [id="proc-create-savings-plan_{context}"]
 
-= Creating a new automation savings plan
+= Create a new automation savings plan
 
 [role="_abstract"]
 Create an automation savings plan by defining the tasks needed to complete an automation job by using the {planner}.

diff --git a/downstream/modules/analytics/proc-curate-templates.adoc b/downstream/modules/analytics/proc-curate-templates.adoc
@@ -6,7 +6,7 @@
 
 [id="proc-curating-templates"]
 
-= Curating top templates
+= Curate top templates
 
 [role="_abstract"]
 You can use the toggle switch for each template to show or hide it in the bar graph to compare performance and savings based on specific templates.

diff --git a/downstream/modules/analytics/proc-ignoring-nested-workflows-jobs.adoc b/downstream/modules/analytics/proc-ignoring-nested-workflows-jobs.adoc
@@ -4,7 +4,7 @@
 // assembly-using-job-explorer.adoc
 
 [id="ignoring-nested-workflows"]
-= Ignoring nested workflows and jobs
+= Ignore nested workflows and jobs
 
 [role="_abstract"]
 Ignoring nested workflows and jobs filters out duplicate workflow and job template entries and excludes those items from overall totals.

diff --git a/downstream/modules/analytics/proc-jobs-explorer.adoc b/downstream/modules/analytics/proc-jobs-explorer.adoc
@@ -7,7 +7,7 @@
 
 [id="proc-jobs-explorer"]
 
-= Creating a filtered and sorted view of jobs
+= Create a filtered and sorted view of jobs
 
 [role="_abstract"]
 You can view a list of jobs, filtered by attributes you choose, using the *Job Explorer*.

diff --git a/downstream/modules/analytics/proc-review-job-details.adoc b/downstream/modules/analytics/proc-review-job-details.adoc
@@ -7,7 +7,7 @@
 
 [id="proc-review-job-details"]
 
-= Reviewing job details on {ControllerName}
+= Review job details on {ControllerName}
 
 [role="_abstract"]
 You review job details on {ControllerName}.

diff --git a/downstream/modules/analytics/proc-review-reports.adoc b/downstream/modules/analytics/proc-review-reports.adoc
@@ -6,7 +6,7 @@
 
 [id="proc-review-reports"]
 
-= Reviewing your reports
+= Review your reports
 
 [role="_abstract"]
 To view reports about your Ansible automation environment, proceed with the following steps:

diff --git a/downstream/modules/analytics/proc-top-template-job-explorer.adoc b/downstream/modules/analytics/proc-top-template-job-explorer.adoc
@@ -5,7 +5,7 @@
 
 
 [id="proc-top-template-job-explorer"]
-= Viewing top templates job details for a specific cluster
+= View top templates job details for a specific cluster
 
 [role="_abstract"]
 You can view job instances for top templates in a cluster to learn more about individual job runs associated with that template or to apply filters to further drill down into the data.

diff --git a/downstream/modules/analytics/proc-view-failed-jobs-detail.adoc b/downstream/modules/analytics/proc-view-failed-jobs-detail.adoc
@@ -7,7 +7,7 @@
 
 [id="proc-view-failed-jobs"]
 
-= Example: Reviewing failed jobs
+= Example: Review failed jobs
 
 [role="_abstract"]
 You can view detailed information about failed jobs across your organization by drilling down on a graph in the *Clusters* view and using the *Job Explorer* to refine results.

diff --git a/downstream/modules/analytics/proc-view-more-job-info.adoc b/downstream/modules/analytics/proc-view-more-job-info.adoc
@@ -7,7 +7,7 @@
 
 [id="proc-view-more-job-info"]
 
-= Viewing more information about an individual job
+= View more information about an individual job
 
 [role="_abstract"]
 You can view additional information about each individual job.

diff --git a/downstream/modules/analytics/proc-view-template-details.adoc b/downstream/modules/analytics/proc-view-template-details.adoc
@@ -6,7 +6,7 @@
 
 [id="proc-view-template-details"]
 
-= Viewing template details
+= View template details
 
 [role="_abstract"]
 View detailed information for each template in *Top templates* to learn more about the template's context in the calculation of automation savings.

diff --git a/downstream/modules/automation-dashboard/con-filter-automation-data.adoc b/downstream/modules/automation-dashboard/con-filter-automation-data.adoc
@@ -32,6 +32,6 @@ After selecting your filters, select a time period for analysis, and select a cu
 * A longer time period is useful when considering overall platform usage and automation growth.
 * Changing from one currency to another does not convert the value of that currency. You must manually change the manual and automation cost figures to reflect whichever currency you select. 
 
-== Saving a report
+== Save a report
 
 Use *Save as Report* to save this report to your {AutomationDashboardName}. You can retrieve it at any time by using *Select a Report*.
diff --git a/downstream/modules/automation-dashboard/con-top-overview-usage.adoc b/downstream/modules/automation-dashboard/con-top-overview-usage.adoc
@@ -3,7 +3,7 @@
 
 [id="con-top-overview-usage"]
 
-= Summary of top and overview usage
+= Summary of key automation data metrics
 
 [role="_abstract"]
 {AutomationDashboardNameStart} displays a summary of the top and overview usage for your selected report. This includes the following data:

diff --git a/downstream/modules/automation-dashboard/proc-analyzing-costs-savings.adoc b/downstream/modules/automation-dashboard/proc-analyzing-costs-savings.adoc
@@ -3,7 +3,7 @@
 
 [id="proc-analyzing-costs-savings"]
 
-= Analyzing costs and savings
+= Calculate savings from automation
 
 [role="_abstract"]
 The costs and savings analysis compares the cost of manual automation compared to the cost of automation execution by using {PlatformNameShort} to calculate the total savings derived from automation execution.

diff --git a/downstream/modules/builder/proc-installing-the-collection.adoc b/downstream/modules/builder/proc-installing-the-collection.adoc
@@ -15,7 +15,7 @@ Install or upgrade the `ansible.mcp_builder` collection through the {Galaxy} com
 
 *Collections*
 
-*ansible.mcp for execution of MCP servers.
+* `ansible.mcp` for execution of MCP servers.
 
 *External dependencies*
 

diff --git a/downstream/modules/builder/ref-mcp-builder-collection.adoc b/downstream/modules/builder/ref-mcp-builder-collection.adoc
@@ -24,7 +24,7 @@ Roles
 Installs the link:https://github.com/github/github-mcp-server[GitHub MCP server] with support for local (build from source) and remote modes
 |===
 
-== Playbooks
+*Playbooks*
 
 [cols="a,a", options="header"]
 |===

diff --git a/downstream/modules/platform/con-user-data-tracking.adoc b/downstream/modules/platform/con-user-data-tracking.adoc
@@ -2,7 +2,7 @@
 
 [id="con-usability-analytics_{context}"]
 
-= Usability analytics and data collection
+= Get insights on automation across your environment with {Analytics}
 
 [role="_abstract"]
 Usability data collection is included with {ControllerName} to collect data to better understand how {ControllerName} users specifically interact with {ControllerName}, to help enhance future releases, and to continue streamlining your user experience.

diff --git a/downstream/modules/platform/proc-control-data-collection.adoc b/downstream/modules/platform/proc-control-data-collection.adoc
@@ -2,7 +2,7 @@
 
 [id="proc-controlling-data-collection_{context}"]
 
-= Controlling data collection from {ControllerName}
+= Control data collection from {ControllerName}
 
 [role="_abstract"]
 You can control how {ControllerName} collects data from the {MenuSetSystem} menu.

diff --git a/downstream/modules/platform/proc-controller-configure-analytics.adoc b/downstream/modules/platform/proc-controller-configure-analytics.adoc
@@ -2,7 +2,7 @@
 
 [id="proc-controller-configure-analytics"]
 
-= Configuring {Analytics}
+= Configure {Analytics}
 
 [role="_abstract"]
 When you imported your license for the first time, you were automatically opted in for the collection of data that powers {Analytics}, a cloud service that is part of the {PlatformNameShort} subscription.

diff --git a/downstream/modules/platform/ref-controller-data-collection-details.adoc b/downstream/modules/platform/ref-controller-data-collection-details.adoc
@@ -2,7 +2,7 @@
 
 [id="ref-controller-data-collection-details"]
 
-= Details of data collection
+= Details about data collected for {analytics}
 
 [role="_abstract"]
 Learn about the specific data that {ControllerName} collects and sends to Red Hat when you enable {Analytics}.