Multiple typo and bug fixes

* Typos in prose
* Typo fix in copy/paste (dropped a letter)
* markup fix: keep list within quoted text
* Auto-corrupt cleanup: Jason to JSON
* gateway: multiple typos and language nits
* monitoring: add missing leafz, fix subsz spelling

nats-server/configuration/securing_nats/README.md

@@ -4,5 +4,4 @@ The NATS server provides several forms of security:
 
 * Connections can be [_encrypted_ with TLS](tls.md)
 * Client connections can require [_authentication_](auth_intro/)
-* Clients can require [_authorization_](authorization.md) for subjects the publish or subscribe to
-
+* Clients can require [_authorization_](authorization.md) for subjects they publish or subscribe to

nats-server/configuration/securing_nats/auth_intro/accounts.md

@@ -36,11 +36,11 @@ accounts: {
 > These two accounts are isolated from each other. Messages published by users in `A` are not visible to users in `B`.
 >
 > The user configuration map is the same as any other NATS [user configuration map](./#user-configuration-map). You can use:
-
-* username/password
-* nkeys
-* and add permissions
-
+>
+> * username/password
+> * nkeys
+> * and add permissions
+>
 > While the name _account_ implies one or more users, it is much simpler and enlightening to think of one account as a messaging container for one application. Users in the account are simply the minimum number of services that must work together to provide some functionality. In simpler terms, more accounts with few \(even one\) clients is a better design topology than a large account with many users with complex authorization configuration.
 
 ### Exporting and Importing

nats-server/configuration/securing_nats/auth_intro/username_password.md

@@ -34,7 +34,7 @@ Username/password also supports bcrypted passwords using the [`mkpasswd`](../../
 
 ```text
 > mkpasswd
-ass: (Uffs#rG42PAu#Oxi^BNng
+pass: (Uffs#rG42PAu#Oxi^BNng
 bcrypt hash: $2a$11$V1qrpBt8/SLfEBr4NJq4T.2mg8chx8.MTblUiTBOLV3MKDeAy.f7u
 ```