diff --git a/faq.md b/faq.md
index 0deb7fd..52e7c29 100644
--- a/faq.md
+++ b/faq.md
@@ -52,8 +52,7 @@ The NATS server \(`nats-server`\) is written in Go. There is client support for
 
 ### Who maintains NATS?
 
-NATS is maintained by a select group of Maintainers following a Governance process as part of the [Cloud Native Computing Foundation (CNCF)](http://cncf.io).
-The team of engineers at [Synadia](https://synadia.com) in conjunction with Community Maintainers, maintain the NATS server, NATS Streaming Server, as well as the official Go, Ruby, Node.js, C, C\#, Java and several other client libraries. Our very active user community also contributes client libraries and connectors for several other implementation languages. Please see the [download](https://nats.io/download) page for the complete list, and links to the relevant source repositories and documentation.
+NATS is maintained by a select group of Maintainers following a Governance process as part of the [Cloud Native Computing Foundation \(CNCF\)](http://cncf.io). The team of engineers at [Synadia](https://synadia.com) in conjunction with Community Maintainers, maintain the NATS server, NATS Streaming Server, as well as the official Go, Ruby, Node.js, C, C\#, Java and several other client libraries. Our very active user community also contributes client libraries and connectors for several other implementation languages. Please see the [download](https://nats.io/download) page for the complete list, and links to the relevant source repositories and documentation.
 
 ### What client support exists for NATS?
 
diff --git a/nats-protocol/nats-protocol/README.md b/nats-protocol/nats-protocol/README.md
index b45185b..9ee4f33 100644
--- a/nats-protocol/nats-protocol/README.md
+++ b/nats-protocol/nats-protocol/README.md
@@ -59,7 +59,7 @@ The following sections explain each protocol message.
 
 ### Description
 
-A client will need to start as a plain TCP connection, then when the server accepts a connection from the client, it will send information about itself, the configuration and security requirements are necessary for the client to successfully authenticate with the server and exchange messages. 
+A client will need to start as a plain TCP connection, then when the server accepts a connection from the client, it will send information about itself, the configuration and security requirements necessary for the client to successfully authenticate with the server and exchange messages.
 
 When using the updated client protocol \(see [`CONNECT`](./#connect) below\), `INFO` messages can be sent anytime by the server. This means clients with that protocol level need to be able to asynchronously handle `INFO` messages.
 
diff --git a/nats-streaming-concepts/monitoring/endpoints.md b/nats-streaming-concepts/monitoring/endpoints.md
index ee48f56..9ff9684 100644
--- a/nats-streaming-concepts/monitoring/endpoints.md
+++ b/nats-streaming-concepts/monitoring/endpoints.md
@@ -348,9 +348,10 @@ When that same durable goes offline, `is_offline` is be set to `true`. Although
 
 ## /isFTActive
 
-The endpoint [http://localhost:8222/streaming/isFTActive](http://localhost:8222/streaming/isFTActive) indicates, through the HTTP response code, if this server is running as the active server of a fault tolerant (FT) group. If the server is the active server, the HTTP response code returned is 200, otherwise 204 (which indicates either that the server is running as a FT standby server, or simply not running in FT mode).
+The endpoint [http://localhost:8222/streaming/isFTActive](http://localhost:8222/streaming/isFTActive) indicates, through the HTTP response code, if this server is running as the active server of a fault tolerant \(FT\) group. If the server is the active server, the HTTP response code returned is 200, otherwise 204 \(which indicates either that the server is running as a FT standby server, or simply not running in FT mode\).
 
 If the server is FT active:
+
 ```text
 curl -i http://localhost:8222/streaming/isFTActive
 HTTP/1.1 200 OK
@@ -359,8 +360,10 @@ Content-Length: 0
 ```
 
 If not:
+
 ```text
 curl -i http://localhost:8222/streaming/isFTActive
 HTTP/1.1 204 No Content
 Date: Wed, 24 Jun 2020 14:44:37 GMT
 ```
+