edu feedback

Author: shainaraskas

deploy-manage/monitor/kibana-task-manager-health-monitoring.md

@@ -63,6 +63,8 @@ Additionally, there are two ways to consume these metrics:
 ```{applies_to}
 deployment:
   self:
+  ece:
+  eck:
 ```
 
 In self-managed deployments, you can configure health stats to be logged in the {{kib}} `DEBUG` logger at a regular cadence. To enable Task Manager debug logging in your {{kib}} instance, add the following to your `kibana.yml`:

deploy-manage/monitor/logging-configuration.md

@@ -71,7 +71,7 @@ Files in `%KIBANA_HOME%` risk deletion during an upgrade. In production, you sho
 
 :::::::
 
-If you run {{kib}} from the command line, {{es}} prints logs to the standard output (`stdout`).
+If you run {{kib}} from the command line, {{kib}} prints logs to the standard output (`stdout`).
 
 You can also consume logs using [stack monitoring](/deploy-manage/monitor/stack-monitoring/kibana-monitoring-self-managed.md).
 

deploy-manage/monitor/orchestrators/ece-monitoring-ece-access.md

@@ -39,7 +39,7 @@ To access logs and metrics for your deployment:
     If you have a license from 2018 or earlier, you might receive a warning that your cluster license is about to expire. Don’t panic, it isn’t really. Elastic Cloud Enterprise manages the cluster licenses so that you don’t have to. In rare cases, such as when a cluster is overloaded, it can take longer for Elastic Cloud Enterprise to reapply the cluster license. If you have a license from 2019 and later, you’ll receive a warning only when your full platform license is about to expire, which you’ll need to renew.
     ::::
 
-4. Select one of the links and log in with the `elastic` user. If you do not know the password, you can [reset it first](../../users-roles/cluster-or-deployment-auth/built-in-users.md).
+4. Select one of the links and log in with the `elastic` user of the `logging-and-metrics` deployment. If you do not know the password, you can [reset it first](../../users-roles/cluster-or-deployment-auth/built-in-users.md).
 
     ::::{tip} 
     The password you specify must be for the `elastic` user on the `logging-and-metrics` cluster, where the logging and metrics indices are collected. If you need to reset the password for the user, make sure you reset for the `logging-and-metrics` cluster.

deploy-manage/monitor/orchestrators/ece-platform-monitoring.md

@@ -14,9 +14,7 @@ By default, {{ece}} collects monitoring data for your installation using Filebea
 * Monitoring metrics for core {{ece}} services, system processes on the host, and any third-party software
 * Logs and monitoring metrics for {{es}} clusters and for {{kib}} instances
 
-These monitoring indices are collected in addition to the [monitoring you might have enabled for specific clusters](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md), which also provides monitoring metrics that you can access in Kibana. 
-
-The `logging-and-metrics` deployment is used for monitoring data from system deployments only. For non-system deployments, monitoring data must be sent to a deployment other than `logging-and-metrics`.
+These monitoring indices are collected in addition to the [stack monitoring you might have enabled for specific clusters](/deploy-manage/monitor/stack-monitoring/ece-ech-stack-monitoring.md), which also provides monitoring metrics that you can access in {{kib}}. 
 
 In this section, you'll learn the following about using ECE platform monitoring: