procedure formatting fixed

ee/ucp/admin/configure/collect-cluster-metrics.md

@@ -25,27 +25,33 @@ Events, logs, and metrics are sources of data that provide observability of your
 
 The Docker EE platform provides a base set of metrics that gets you running and into production without having to rely on external or 3rd party tools. Docker strongly encourages the use of additional monitoring to provide more comprehensive visibility into your specific Docker environment, but recognizes the need for a basic set of metrics built into the product. The following are examples of these metrics:
 
-- **Business metrics**: These are high-level aggregate metrics that typically combine technical, financial, and organizational data to create metrics for business leaders of the IT infrastructure. Some examples of business metrics might be:
+## Business metrics ##
+
+These are high-level aggregate metrics that typically combine technical, financial, and organizational data to create metrics for business leaders of the IT infrastructure. Some examples of business metrics might be:
     - Company or division-level application downtime
     - Aggregate resource utilization
     - Application resource demand growth
 
+## Application metrics ##
 
-- **Application metrics**: These are metrics about domain of APM tools like AppDynamics or DynaTrace and provide metrics about the state or performance of the application itself.
+These are metrics about domain of APM tools like AppDynamics or DynaTrace and provide metrics about the state or performance of the application itself.
     - Service state metrics
     - Container platform metrics
     - Host infrastructure metrics
 
-
 Docker EE 2.1 does not collect or expose application level metrics. The following are metrics Docker EE 2.1 collects, aggregates, and exposes:
 
-- **Service state metrics**: These are metrics about the state of services running on the container platform. These types of metrics have very low cardinality, meaning the values are typically from a small fixed set of possibilities, commonly binary.
+## Service state metrics ##
+
+These are metrics about the state of services running on the container platform. These types of metrics have very low cardinality, meaning the values are typically from a small fixed set of possibilities, commonly binary.
     - Application health
     - Convergence of K8s deployments and Swarm services
     - Cluster load by number of services or containers or pods
 
 
-- **Host infrastructure metrics**: These are metrics taken from te software & hardware infrastructure.
+## Host infrastructure metrics ##
+
+These are metrics taken from te software & hardware infrastructure.
     - CPU - Container-level CPU utilization, Node-level load average
     - Memory - RSS, swap
     - Network I/O - bandwidth, packets, drops
@@ -53,7 +59,9 @@ Docker EE 2.1 does not collect or expose application level metrics. The followin
     - Operating System – file descriptors, open network connections, number of processes/threads
 
 
-- **Container infrastructure system metrics**: These are application-level metrics derived from the container platform itself.
+## Container infrastructure system metrics ##
+
+These are application-level metrics derived from the container platform itself.
     - Infrastructure Quorum Leader - Swarm RAFT, etcd, rethink
     - UCP Component health - Healthy / Unhealthy
 
@@ -112,7 +120,7 @@ To configure your external Prometheus server to scrape metrics from Prometheus i
    On AWS with Kube’s cloud provider configured, you can replace `ClusterIP` with `LoadBalancer` in the service YAML then access the service through the load balancer. If running Prometheus external to UCP, change the following domain for the inventory container in the Prometheus deployment from `ucp-controller.kube-system.svc.cluster.local` to an external domain to access UCP from the Prometheus node.
 
     ```
-kubectl apply -f - <<EOF
+    kubectl apply -f - &lt;&lt;EOF
     apiVersion: v1
     kind: ConfigMap
     metadata: