GitBook: [master] 61 pages modified

nats-tools/nas/README.md

@@ -1,7 +1,6 @@
 # nats-account-server
 
-The [NATS Account Server](https://github.com/nats-io/nats-account-server) is an HTTP server that hosts and vends [JWTs](../../nats-server/configuration/securing_nats/jwt/README.md) for nats-server 2.0 account authentication. 
-The server supports an number of stores which enable it to serve account [JWTs](../../nats-server/configuration/securing_nats/jwt/README.md) from:
+The [NATS Account Server](https://github.com/nats-io/nats-account-server) is an HTTP server that hosts and vends [JWTs](../../nats-server/configuration/securing_nats/jwt/) for nats-server 2.0 account authentication. The server supports an number of stores which enable it to serve account [JWTs](../../nats-server/configuration/securing_nats/jwt/) from:
 
 * a [directory](nas_conf.md#directory-configuration)
 * an [NSC](../nsc/nsc.md) [directory](nas_conf.md#nsc-configuration)
@@ -14,5 +13,5 @@ The server supports replica mode, which allows load balancing, fault tolerance a
 
 The account server can host activation tokens as well as account JWTs. These tokens are used when one account needs to give permission to another account to access a private export. Tokens can be configured as full tokens, or URLs. By hosting them in the account server you can avoid the copy/paste process of embedding tokens. They can also be updated more easily on expiration. The account serer furthermore allows for jwt inspection.
 
-All account server configuration options can be found [here](nas_conf.md#Configuration-File).
-It futhermore allows [inspection](inspecting_jwts.md) of JWT.
+All account server configuration options can be found [here](nas_conf.md#Configuration-File). It futhermore allows [inspection](inspecting_jwts.md) of JWT.
+

nats-tools/nas/dir_store.md

@@ -100,4 +100,5 @@ Quick check on nsc to verify the ids of the accounts on nsc, match the files:
 
 Note that the `@` before the file name is required for `curl` to read the specified file, and use it as the payload. Otherwise, it will simply post the path specified, which will result in an update error.
 
-Curl can also be used to [inspect](inspecting_jwts.md) JWTs.
+Curl can also be used to [inspect](inspecting_jwts.md) JWTs.
+

nats-tools/nas/nas_conf.md

@@ -168,7 +168,7 @@ Provided a setup with 4 accounts, one of them a system account, this example sho
 * configure a `nats-server` to make use of the account server
 * test the setup
 
-```sh
+```bash
 $ export NKEYS_PATH=$(pwd)/nsc/nkeys
 $ export NSC_HOME=$(pwd)/nsc/accounts
 
@@ -230,3 +230,4 @@ Listening on [test]
 # Subscribe using the system account user credentials can receive all system events
 $ nats-sub -creds nsc/nkeys/creds/KO/SYS/sys.creds '>'
 ```
+

nats-tools/nas/notifications.md

@@ -1,8 +1,8 @@
 # Update Notifications
 
-The `nats-account-server` can notify a nats-server about [JWT](../../nats-server/configuration/securing_nats/jwt/README.md) updates, enabling the NATS server to update itself to the newly updated JWT.
+The `nats-account-server` can notify a nats-server about [JWT](../../nats-server/configuration/securing_nats/jwt/) updates, enabling the NATS server to update itself to the newly updated JWT.
 
-To push notifications, the nats-account-server makes use of [system accounts](../../nats-server/configuration/sys_accounts/sys_accounts.md).
+To push notifications, the nats-account-server makes use of [system accounts](https://github.com/nats-io/nats.docs/tree/aecb86faf9be946a413d1c6200fc0ff5d1b0baef/nats-server/configuration/sys_accounts/sys_accounts.md).
 
 Here's a nats-account-server configuration with updates enabled:
 

nats-tools/nsc/README.md

@@ -23,7 +23,7 @@ The script will download the latest version of `nsc` and install it into your sy
 
 Alternatively, you can use `nsc` with the [nats-box](https://hub.docker.com/r/synadia/nats-box) Docker image:
 
-```sh
+```bash
 $ docker run --rm -it -v $(pwd)/nsc:/nsc synadia/nats-box:latest
 
 # In case NSC not initialized already: