copy edits

docs/modules/maintain-cluster/pages/monitoring.adoc

@@ -534,7 +534,7 @@ Setting up monitoring via Prometheus consists of two steps. The first step
 is exposing an HTTP endpoint with metrics. The second step is setting up
 Prometheus server, which pulls the metrics in a specified interval.
 
-The Prometheus java agent is already part of the Hazelcast
+The Prometheus Java agent is already part of the Hazelcast
 distribution and just needs to be enabled. Enable the agent and expose
 all metrics via HTTP endpoint by setting an environment variable
 PROMETHEUS_PORT, you can change the port to any available port:
@@ -2487,15 +2487,15 @@ com.hazelcast.sql.HazelcastSqlException: Cannot resolve IMap schema because it d
 ```
 
 
-* Prometheus: You can use this third party tool to filter alert metrics. See the
+* Prometheus: You can use this third-party tool to filter alert metrics. See the
 xref:maintain-cluster:monitoring.adoc#prometheus-2[Prometheus section] for details.
 
 Besides the above channels, you can also benefit from Hazelcast logging mechanism as an indirect
 way of getting alerts. See the xref:maintain-cluster:monitoring.adoc#logging[Logging section] for details.
 
 To learn the possible actions on the alerts, see the xref:troubleshoot:remedies-for-alerts.adoc[Actions and Remedies for Alerts section].
 
-== Integrating with Third Party Tools
+== Integrating with Third-Party Tools
 
 Management Center monitors your entire Hazelcast cluster, making it much easier to integrate with third-party tools without needing to connect to individual members, manage changes from scaling and restarts, or collate metrics from all members.