diff --git a/nats-server/configuration/securing_nats/auth_intro/nkey_auth.md b/nats-server/configuration/securing_nats/auth_intro/nkey_auth.md
index ec95736..4eaea92 100644
--- a/nats-server/configuration/securing_nats/auth_intro/nkey_auth.md
+++ b/nats-server/configuration/securing_nats/auth_intro/nkey_auth.md
@@ -177,7 +177,7 @@ resolver_preload = {
 }
 ```
 
-**These two servers even though they have different auth mechanisms are able to route the accounts because the account public nkeys are the same.**
+Even though they have different authorization mechanisms, these two servers are able to route account messages because they share the same NKEY. 
 
 We have created at least one user, in this case with creds:
 
diff --git a/nats-streaming-concepts/monitoring/README.md b/nats-streaming-concepts/monitoring/README.md
index 01643e7..dedc2bf 100644
--- a/nats-streaming-concepts/monitoring/README.md
+++ b/nats-streaming-concepts/monitoring/README.md
@@ -67,7 +67,7 @@ curl 127.0.0.1:8222/streaming/channelsz
 
 ## Monitoring a NATS Streaming channel with Grafana and Prometheus
 
-Here you can find a few examples of monitoring NATS Streaming channels:
+Here you'll find examples demonstrating how to use Prometheus query expressions to monitor NATS streaming channels.
 
 ### Pending Messages from Channel Foo