Remove all un-necessary "Output" or "Example Output" between two code…

… block (they are redundant and make the doc longer for no reason because the fact that it is an example output is obvious visually from the fact the command being used and its output are in two separate codeblocks, and that all doc examples are just that.
bk62 · Apr 14, 2022 · ceb819b · ceb819b
1 parent cf26036
commit ceb819b
Show file tree

Hide file tree

Showing 51 changed files with 0 additions and 330 deletions.
diff --git a/legacy/nas/inspecting_jwts.md b/legacy/nas/inspecting_jwts.md
@@ -7,7 +7,6 @@ The endpoint for retrieving an account JWT is: `/jwt/v1/accounts/<account_id>`.
 ```shell
 curl http://localhost:9090/jwt/v1/accounts/AC7PO3MREV26U3LFZFP5BN3HAI32X3PKLBRVMPAETLEHWPQEUG7EJY4H\?decode=true
 ```
-Example output
 ```text
 {
     "typ": "jwt",

diff --git a/legacy/nas/nas_conf.md b/legacy/nas/nas_conf.md
@@ -19,7 +19,6 @@ You can start a server using a plain directory. In this case you'll be responsib
 mkdir /tmp/jwts
 nats-account-server -dir /tmp/jwts
 ```
-Output
 ```text
 2019/05/10 11:33:40.501305 [INF] starting NATS Account server, version 0.0-dev
 2019/05/10 11:33:40.501383 [INF] server time is Fri May 10 11:33:40 CDT 2019
@@ -130,7 +129,6 @@ List all accounts
 ```shell
 nsc list accounts
 ```
-Output
 ```text
 ╭─────────────────────────────────────────────────────────────────╮
 │                            Accounts                             │
@@ -193,7 +191,6 @@ Try to subscribe on account without permissions, this should fail
 ```shell
 nats sub -creds nsc/nkeys/creds/KO/A/test.creds foo
 ```
-Output
 ```text
 nats: Permissions Violation for Subscription to "foo"
 ```

diff --git a/legacy/nas/notifications.md b/legacy/nas/notifications.md
@@ -62,7 +62,6 @@ The nats-account-server has to be running before that nats-server starts, as cur
 ```shell
 nats-account-server -c nas_not.conf
 ```
-Output
 ```text
 2019/05/31 18:00:26.327583 [INF] loading configuration from "/Users/synadia/Desktop/nats_jwt_doc/as_dir/nas_not.conf"
 2019/05/31 18:00:26.327833 [INF] starting NATS Account server, version 0.0-dev
@@ -87,7 +86,6 @@ Then start the NATS server:
 ```shell
 nats-server -c /tmp/server.conf
 ```
-Output
 ```text
 [57440] 2019/05/31 18:01:29.940149 [INF] Starting nats-server version 1.4.1
 [57440] 2019/05/31 18:01:29.940234 [INF] Git commit [not set]
@@ -100,7 +98,6 @@ At this point, you have both servers running. You can submit updates to the nats
 ```shell
 nsc push -A
 ```
-Output
 ```text
 successfully pushed all accounts [A, B, SYS]
 ```

diff --git a/legacy/stan/nats-streaming-concepts/monitoring/README.md b/legacy/stan/nats-streaming-concepts/monitoring/README.md
@@ -55,7 +55,6 @@ Confirm that the monitoring endpoint is enabled by sending a request:
 ```bash
 curl 127.0.0.1:8222/streaming/channelsz
 ```
-Output
 ```JSON
 {
   "cluster_id": "test-cluster",

diff --git a/legacy/stan/nats-streaming-server/configuring/tls.md b/legacy/stan/nats-streaming-server/configuring/tls.md
@@ -53,9 +53,6 @@ However, NATS Streaming Server uses the NATS Server command line parsing code an
 ```bash
 nats-streaming-server -tls_ca_cert test/certs/ca.pem
 ```
-
-Output
-
 ```
 TLS Server certificate must be present and valid
 ```

diff --git a/legacy/stan/nats-streaming-server/run.md b/legacy/stan/nats-streaming-server/run.md
@@ -34,7 +34,6 @@ You should see the following, indicating that the NATS Streaming Server is runni
 ```bash
 go run nats-streaming-server.go
 ```
-Example output
 ```text
 [59232] 2019/05/22 14:24:54.426344 [INF] STREAM: Starting nats-streaming-server[test-cluster] version 0.14.2
 [59232] 2019/05/22 14:24:54.426423 [INF] STREAM: ServerID: 3fpvAuXHo3C66Rkd4rmfFX
@@ -77,7 +76,6 @@ Use the `--all` flag to receive all published messages.
 cd $GOPATH/src/github.com/nats-io/stan.go/examples/stan-sub
 go run main.go --all -c test-cluster -id myID foo
 ```
-Example output
 ```text
 Connected to nats://localhost:4222 clusterID: [test-cluster] clientID: [myID]
 subscribing with DeliverAllAvailable

diff --git a/nats-concepts/jetstream/js_walkthrough.md b/nats-concepts/jetstream/js_walkthrough.md
@@ -9,7 +9,6 @@ You can then check that JetStream is enabled by using
 ```shell
 nats account info
 ```
-which should output something like
 ```
 Connection Information:
 
@@ -47,7 +46,6 @@ Enter `nats stream add <Stream name>` (in the examples below we will name the st
 ```shell
 nats stream add my_stream
 ```
-example output
 ```text
 ? Subjects to consume foo
 ? Storage backend file
@@ -93,7 +91,6 @@ You can then check the information about the stream you just created:
 ```shell
 nats stream info my_stream
 ```
-which should output something like
 ```text
 Information for Stream my_stream created 2021-10-12T08:42:10-07:00
 
@@ -140,7 +137,6 @@ We can administratively create a consumer using the 'nats consumer add <Consumer
 ```shell
 nats consumer add
 ```
-example output
 ```text
 ? Consumer name pull_consumer
 ? Delivery target (empty for Pull Consumers)

diff --git a/nats-concepts/jetstream/key-value-store/kv_walkthrough.md b/nats-concepts/jetstream/key-value-store/kv_walkthrough.md
@@ -9,7 +9,6 @@ You can then check that JetStream is enabled by using
 ```shell
 nats account info
 ``` 
-Which should output something like:
 ```
 Connection Information:
 
@@ -45,7 +44,6 @@ Just like you have to create streams before you can use them, you need to first
 ```shell
 nats kv add my_kv
 ```
-which should output:
 ```text
 my_kv Key-Value Store Status
 
@@ -74,7 +72,6 @@ Now that we have value stored at key "Key1" we can retrieve that value with a 'g
 ```shell
 nats kv get my_kv Key1
 ```
-which should output
 ```
 my_kv > Key1 created @ 12 Oct 21 20:08 UTC
 
@@ -95,7 +92,6 @@ For example run `nats kv watch my_kv`: this will start a watcher on the bucket w
 ```shell
 nats kv watch my_kv
 ```
-which should output
 ```
 [2021-10-12 13:15:03] DEL my_kv > Key1
 ```

diff --git a/nats-concepts/jetstream/object-store/obj_walkthrough.md b/nats-concepts/jetstream/object-store/obj_walkthrough.md
@@ -64,7 +64,6 @@ myobjbucket Object Store Status
 ```shell
 nats object put myobjbucket ~/Movies/NATS-logo.mov
 ```
-ouput
 ```
 
 1.5 GiB / 1.5 GiB [====================================================================================]
@@ -82,7 +81,6 @@ Object information for myobjbucket > /Users/jnmoyne/Movies/NATS-logo.mov
 ```shell
 nats object ls myobjbucket
 ```
-output
 ```
 ╭───────────────────────────────────────────────────────────────────────────╮
 │                              Bucket Contents                              │
@@ -98,7 +96,6 @@ output
 ```shell
 nats object get myobjbucket ~/Movies/NATS-logo.mov
 ```
-output
 ```
 
 1.5 GiB / 1.5 GiB [====================================================================================]
@@ -111,7 +108,6 @@ Wrote: 1.5 GiB to /Users/jnmoyne/NATS-logo.mov in 5.68s average 279 MiB/s
 ```shell
 nats object rm myobjbucket ~/Movies/NATS-logo.mov
 ```
-output
 ```
 ? Delete 1.5 GiB byte file myobjbucket > /Users/jnmoyne/Movies/NATS-logo.mov? Yes
 Removed myobjbucket > /Users/jnmoyne/Movies/NATS-logo.mov
@@ -131,7 +127,6 @@ myobjbucket Object Store Status
 ```shell
 nats object info myobjbucket
 ```
-output
 ```
 myobjbucket Object Store Status
 
@@ -149,7 +144,6 @@ myobjbucket Object Store Status
 ```shell
 nats object watch myobjbucket
 ```
-output
 ```
 [2022-04-13 17:51:28] PUT myobjbucket > /Users/jnmoyne/Movies/NATS-logo.mov: 1.5 GiB bytes in 12,656 chunks
 [2022-04-13 17:53:27] DEL myobjbucket > /Users/jnmoyne/Movies/NATS-logo.mov
@@ -162,7 +156,6 @@ You can seal a bucket, meaning that no further changes are allowed on that bucke
 ```shell
 nats object seal myobjbucket
 ```
-output
 ```
 ? Really seal Bucket myobjbucket, sealed buckets can not be unsealed or modified Yes
 myobjbucket has been sealed

diff --git a/nats-concepts/what-is-nats/walkthrough_setup.md b/nats-concepts/what-is-nats/walkthrough_setup.md
@@ -63,7 +63,6 @@ curl -L https://github.com/nats-io/nats-server/releases/download/v2.6.5/nats-ser
 ```shell
 unzip nats-server.zip -d nats-server
 ```
-which should output something like
 ```text
 Archive:  nats-server.zip
    creating: nats-server-v2.6.2-linux-amd64/

diff --git a/reference/nats-protocol/nats-protocol/README.md b/reference/nats-protocol/nats-protocol/README.md
@@ -98,9 +98,6 @@ Below you can see a sample connection string from a telnet connection to the `de
 ```bash
 telnet demo.nats.io 4222
 ```
-
-Output
-
 ```
 Trying 107.170.221.32...
 Connected to demo.nats.io.

diff --git a/running-a-nats-service/clients.md b/running-a-nats-service/clients.md
@@ -38,7 +38,6 @@ Open a terminal and [start a nats-server](/running-a-nats-service/introduction/r
 ```shell
 nats-server
 ```
-Example output
 ```text
 [45695] 2021/09/29 02:22:53.570667 [INF] Starting nats-server
 [45695] 2021/09/29 02:22:53.570796 [INF]   Version:  2.6.1
@@ -53,7 +52,6 @@ On another terminal session first check the connection to the server
 ```shell
 nats server check
 ```
-Example output
 ```text
 OK Connection OK:connected to nats://127.0.0.1:4222 in 790.28µs OK:rtt time 69.896µs OK:round trip took 0.000102s | connect_time=0.0008s;0.5000;1.0000 rtt=0.0001s;0.5000;1.0000 request_time=0.0001s;0.5000;1.0000
 ```
@@ -71,7 +69,6 @@ To make the server output more lively, you can specify the `-V` flag to enable l
 ```shell
 nats-server -V
 ```
-Example output
 ```text
 [45703] 2021/09/29 02:23:05.189377 [INF] Starting nats-server
 [45703] 2021/09/29 02:23:05.189489 [INF]   Version:  2.6.1

diff --git a/running-a-nats-service/configuration/clustering/README.md b/running-a-nats-service/configuration/clustering/README.md
@@ -194,7 +194,6 @@ Testing server A
 nats sub -s "nats://127.0.0.1:4222" hello &
 nats pub -s "nats://127.0.0.1:4222" hello world_4222
 ```
-Output
 ```text
 23:34:45 Subscribing on hello
 23:34:45 Published 10 bytes to "hello"
@@ -207,7 +206,6 @@ Testing server B
 ```shell
 nats pub -s "nats://127.0.0.1:5222" hello world_5222
 ```
-Output
 ```text
 [#2] Received on "hello"
 23:36:09 Published 10 bytes to "hello"
@@ -218,7 +216,6 @@ Testing server C
 ```shell
 nats pub -s "nats://127.0.0.1:6222" hello world_6222
 ```
-Output
 ```text
 23:38:40 Published 10 bytes to "hello"
 [#3] Received on "hello"
@@ -229,7 +226,6 @@ Testing using seed (i.e. A, B and C) server URLs
 ```shell
 nats pub -s "nats://127.0.0.1:4222,nats://127.0.0.1:5222,nats://127.0.0.1:6222" hello whole_world
 ```
-Output
 ```text
 [#4] Received on "hello"
 23:39:16 Published 11 bytes to "hello"

diff --git a/...-a-nats-service/configuration/clustering/jetstream_clustering/administration.md b/...-a-nats-service/configuration/clustering/jetstream_clustering/administration.md
@@ -45,7 +45,6 @@ Users can get overall statistics about their streams and also where these stream
 ```shell
 nats stream report
 ```
-Example output
 ```text
 Obtaining Stream stats
 +----------+-----------+----------+--------+---------+------+---------+----------------------+
@@ -69,7 +68,6 @@ Moving leadership away from a node does not remove it from the cluster and does
 ```shell
 nats stream cluster step-down ORDERS
 ```
-Example output
 ```text
 14:32:17 Requesting leader step down of "n1-c1" in a 3 peer RAFT group
 14:32:18 New leader elected "n4-c1"
@@ -97,7 +95,6 @@ We have a high level report of cluster state:
 ```shell
 nats server report jetstream --user system
 ```
-Example output
 ```text
 +--------------------------------------------------------------------------------------------------+
 |                                        JetStream Summary                                         |
@@ -138,7 +135,6 @@ This report is built using raw data that can be obtained from the monitor port o
 ```shell
 nats server req jetstream --help
 ```
-Output
 ```text
 usage: nats server request jetstream [<flags>] [<wait>]
 
@@ -192,7 +188,6 @@ Similar to Streams and Consumers above the Meta Group allows leader stand down.
 ```shell
 nats server raft step-down --user system
 ```
-Example output
 ```text
 17:44:24 Current leader: n2-c2
 17:44:24 New leader: n1-c2
@@ -209,7 +204,6 @@ After the node is removed the cluster will notice that the replica count is not
 ```shell
 nats stream cluster peer-remove ORDERS
 ```
-Example output
 ```text
 ? Select a Peer n4-c1
 14:38:50 Removing peer "n4-c1"
@@ -221,7 +215,6 @@ At this point the stream and all consumers will have removed `n4-c1` from the gr
 ```shell
 $ nats stream info ORDERS
 ```
-Example output
 ```text
 ....
 Cluster Information:

diff --git a/running-a-nats-service/configuration/gateways/gateway.md b/running-a-nats-service/configuration/gateways/gateway.md
@@ -26,9 +26,6 @@ Starting a server:
 ```shell
 nats-server -c A.conf
 ```
-
-Output
-
 ```
 [85803] 2019/05/07 10:50:55.902474 [INF] Starting nats-server version 2.0.0
 [85803] 2019/05/07 10:50:55.903669 [INF] Gateway name is A
-Original file line number
+Diff line change
@@ Expand Up @@
     ```bash
     curl 127.0.0.1:8222/streaming/channelsz
     ```
-    Output
     ```JSON
     {
       "cluster_id": "test-cluster",
@@ Expand Down @@