Update integration ui text referenced in the docs

deploy-manage/monitor/stack-monitoring/collecting-monitoring-data-with-elastic-agent.md

@@ -36,8 +36,8 @@ To collect {{es}} monitoring data, add an {{es}} integration to an {{agent}} and
 
 5. Configure the integration name and optionally add a description. Make sure you configure all required settings:
 
-    1. Under **Collect {{es}} logs**, modify the log paths to match your {{es}} environment.
-    2. Under **Collect {{es}} metrics**, make sure the hosts setting points to your {{es}} host URLs. By default, the integration collects {{es}} monitoring metrics from `localhost:9200`. If that host and port number are not correct, update the `hosts` setting. If you configured {{es}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:9200`.
+    1. Under **Logs**, modify the log paths to match your {{es}} environment.
+    2. Under **Metrics (Stack Monitoring)**, make sure the hosts setting points to your {{es}} host URLs. By default, the integration collects {{es}} monitoring metrics from `localhost:9200`. If that host and port number are not correct, update the `hosts` setting. If you configured {{es}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:9200`.
     3. Expand **Advanced options**. If the Elastic {{security-features}} are enabled, enter the username and password of a user that has the `remote_monitoring_collector` role.
     4. Specify the scope:
 

deploy-manage/monitor/stack-monitoring/kibana-monitoring-elastic-agent.md

@@ -19,7 +19,7 @@ To learn about monitoring in general, refer to [](/deploy-manage/monitor/stack-m
 
 ## Prerequisites [_prerequisites]
 
-* [Set up {{es}} monitoring](/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md) and optionally [create a monitoring cluster](/deploy-manage/monitor/stack-monitoring/es-self-monitoring-prod.md). 
+* [Set up {{es}} monitoring](/deploy-manage/monitor/stack-monitoring/elasticsearch-monitoring-self-managed.md) and optionally [create a monitoring cluster](/deploy-manage/monitor/stack-monitoring/es-self-monitoring-prod.md).
 * Create a user on the production cluster that has the `remote_monitoring_collector` [built-in role](../../users-roles/cluster-or-deployment-auth/built-in-roles.md).
 
 
@@ -43,8 +43,8 @@ To collect {{kib}} monitoring data, add a {{kib}} integration to an {{agent}} an
 
 5. Configure the integration name and optionally add a description. Make sure you configure all required settings:
 
-    * Under **Collect {{kib}} logs**, modify the log paths to match your {{kib}} environment.
-    * Under **Collect {{kib}} metrics**, make sure the hosts setting points to your {{kib}} host URLs. By default, the integration collects {{kib}} monitoring metrics from `localhost:5601`. If that host and port number are not correct, update the `hosts` setting. If you configured {{kib}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:5601`.
+    * Under **Logs**, modify the log paths to match your {{kib}} environment.
+    * Under **Metrics (Stack Monitoring)**, make sure the hosts setting points to your {{kib}} host URLs. By default, the integration collects {{kib}} monitoring metrics from `localhost:5601`. If that host and port number are not correct, update the `hosts` setting. If you configured {{kib}} to use encrypted communications, you must access it via HTTPS. For example, use a `hosts` setting like `https://localhost:5601`.
     * If the Elastic {{security-features}} are enabled, expand **Advanced options** under the Hosts setting and enter the username and password of a user that has the `remote_monitoring_collector` role.
 
 6. Choose where to add the integration policy. Click **New hosts** to add it to new agent policy or **Existing hosts** to add it to an existing agent policy.