added gateways, leafnodes, nats-account-server, fixed typos etc.

nats_server/configuration.md

@@ -9,8 +9,8 @@ The NATS configuration file supports the following syntax:
 	- Equals sign: `foo = 2`
 	- Colon: `foo: 2`
 	- Whitespace: `foo 2`
-- Arrays are enclosed in brackets: `[...]`
-- Maps are enclosed in braces: `{...}`
+- Arrays are enclosed in brackets: `["a", "b", "c"]`
+- Maps are enclosed in braces: `{foo: 2}`
 - Maps can be assigned with no key separator
 - Semicolons can be used as terminators
 
@@ -46,7 +46,7 @@ Server configurations can specify variables. Variables allow you to reference a
 Variables:
 - Are block scoped
 - Are referenced with a `$` prefix.
-- Can be resolved from the environment variables having the same name
+- Can be resolved from environment variables having the same name
 
 > If the environment variable value begins with a number you may have trouble resolving it depending on the server version you are running.
 

nats_server/flags.md

@@ -1,7 +1,7 @@
 ## Flags
 
 
-The NATS server has many flags to customize it's behaviour without having to write a configuration file.
+The NATS server has many flags to customize its behaviour without having to write a configuration file.
 
 The configuration flags revolve around:
 

nats_server/tls_mutual_auth.md

@@ -26,7 +26,7 @@ Or via the command line:
 
 This option simply verifies the client's certificate has been signed by the CA specified in the `ca_file` option. 
 
-## Mapping Client Certificates To An User
+## Mapping Client Certificates To A User
 
 In addition to verifying that a client certificate was issued by a specified CA, you can use information encoded in the certificate to authenticate a client. The client wouldn't have to provide or track usernames or passwords.
 

nats_server/tokens.md

@@ -42,7 +42,7 @@ authorization {
 }
 ```
 
-The client will still require the clear-text password to connect:
+The client will still require the clear-text token to connect:
 
 ```
 nats-sub -s nats://dag0HTXl4RGg7dXdaJwbC8@localhost:4222 ">"

nats_server/username_password.md

@@ -37,13 +37,14 @@ bcrypt hash: $2a$11$V1qrpBt8/SLfEBr4NJq4T.2mg8chx8.MTblUiTBOLV3MKDeAy.f7u
 ```
 And on the configuration file:
 
+```
 authorization: {
 	users: [
 		{user: a, password: "$2a$11$V1qrpBt8/SLfEBr4NJq4T.2mg8chx8.MTblUiTBOLV3MKDeAy.f7u"},
 		...	
 	]
 }
-
+```
 
 ## Reloading a Configuration