monitoring and metrics - small vale corrections

docs/pages/management/diagnostics.mdx

@@ -20,8 +20,7 @@ Kubernetes probes to monitor the health of a Teleport process.
 The `http://127.0.0.1:3000/healthz` endpoint responds with a body of
 `{"status":"ok"}` and an HTTP 200 OK status code if the process is running.
 
-This is a simple check, suitable for determining if the Teleport process is
-still running.
+This is a check to determine if the Teleport process is still running.
 
 ## `/readyz`
 
@@ -78,7 +77,7 @@ The following metrics are available:
 
 <Notice scope={["cloud"]} type="tip">
 
-    Teleport Cloud does not expose monitoring endpoints for the Auth Service and Proxy Service.
+    Teleport Enterprise (cloud-hosted) does not expose monitoring endpoints for the Auth Service and Proxy Service.
 
 </Notice>
 
@@ -139,7 +138,7 @@ After updating `teleport.yaml`, start your `teleport` instance to apply the new
 
 ## tsh
 
-To capture traces from `tsh` simply add the `--trace` flag to your command. All traces generated by `tsh --trace` will be
+To capture traces from `tsh` add the `--trace` flag to your command. All traces generated by `tsh --trace` will be
 proxied to the `exporter_url` defined for the Auth Service of the cluster the command is being run on.
 
 ```code