Link

docs/client-cli.md

@@ -14,4 +14,4 @@ Storing and reading blobs from Walrus can be achieved through the following comm
 CONFIG=working_dir/client_config.yaml # adjust for your configuration file
 walrus -c $CONFIG store <some file> # store a file
 walrus -c $CONFIG read <some blob ID> # read a blob
-```
+```

docs/interacting.md

@@ -1,6 +1,7 @@
 # Interacting with Walrus
 
 We provide 3 ways to interact directly with the Walrus storage system:
+
 - Through the walrus [client command line interface (CLI)](client-cli.md).
 - Through a [JSON API](json-api.md) of the walrus CLI.
 - Through an [HTTP API](web-api.md) exposed by the walrus client daemon.

docs/json-api.md

@@ -1,8 +1,8 @@
 # JSON mode
 
 All Walrus client commands (except, currently, the `info` command) are available in JSON mode.
-In this mode, all the command line flags of the original CLI command can be specified in JSON format.
-The JSON mode therefore simplifies programmatic access to the CLI.
+In this mode, all the command line flags of the original CLI command can be specified in JSON
+format. The JSON mode therefore simplifies programmatic access to the CLI.
 
 For example, to store a blob, run:
 

docs/web-api.md

@@ -38,4 +38,4 @@ curl "http://$ADDRESS/v1/<some blob ID>" # read a blob from Walrus (with aggrega
 
 Modern browsers will attempt to sniff the content type for such resources, and will generally do a
 good job of inferring content types for media. However, the aggregator on purpose prevents such
-sniffing from inferring dangerous executable types such as javascript or style sheet types.
+sniffing from inferring dangerous executable types such as javascript or style sheet types.