code snippets markdown fixes

developers/ocean-cli/consuming-an-asset.md

@@ -6,4 +6,4 @@ In this command, replace 'assetDID' with the specific DID of the asset you want
 
 Once executed, this command seamlessly orchestrates both the ordering of datatoken and the subsequent download operation. The asset's content will be automatically retrieved and saved at the specified location, simplifying the consumption process for users.
 
-<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2Fqiex0R1FVw2XSzqmSdu6%2FScreenshot%202023-09-28%20at%2001.25.23.png?alt=media&token=70f5e7b7-6698-4817-824c-28ea7483d39c alt=""><figcaption>dowload method example</figcaption></figure>
+<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2Fqiex0R1FVw2XSzqmSdu6%2FScreenshot%202023-09-28%20at%2001.25.23.png?alt=media&token=70f5e7b7-6698-4817-824c-28ea7483d39c" alt=""><figcaption>dowload method example</figcaption></figure>

developers/ocean-cli/downloading-compute-results.md

@@ -8,4 +8,4 @@ For the first method, you'll need both the dataset DID and the compute job DID.
 
 For the second method, the dataset DID is no longer required. Instead, you'll need to specify the job ID, the index of the result you wish to download from the available results for that job, and the destination folder where you want to save the downloaded content. The corresponding command is as follows: <code> npm run cli downloadJobResults 'JOB_ID' 'RESULT_INDEX' 'DESTINATION_FOLDER'</code>
 
-<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2FjvvCAOQVQvAv2ygNtPby%2FScreenshot%202023-09-28%20at%2002.01.42.png?alt=media&token=da8868d7-6fdb-4dce-ac9a-6b395a0960e5 alt=""><figcaption>downloadJobResults</figcaption></figure>
+<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2FjvvCAOQVQvAv2ygNtPby%2FScreenshot%202023-09-28%20at%2002.01.42.png?alt=media&token=da8868d7-6fdb-4dce-ac9a-6b395a0960e5" alt=""><figcaption>downloadJobResults</figcaption></figure>

developers/ocean-cli/installation.md

@@ -2,26 +2,20 @@
 
 **Clone the Repository**: Begin by cloning the repository. You can achieve this by executing the following command in your terminal:
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 $ git clone https://github.com/oceanprotocol/ocean.js-cli.git
 ```
-</code></pre>
 
 Cloning the repository will create a local copy on your machine, allowing you to access and work with its contents.
 
 **Install NPM Dependencies**: After successfully cloning the repository, you should install the necessary npm dependencies to ensure that the project functions correctly. This can be done with the following command:
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 npm install
 ```
-</code></pre>
 
 Build the TypeScript code
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 npm run build
 ```
-</code></pre>

developers/ocean-cli/publish-a-dataset.md

@@ -2,13 +2,11 @@
 
 Once the RPC environment variable has been configured, we can proceed to publish a new dataset on the connected network. The flexibility of our setup allows us to easily switch to a different network by simply substituting the RPC endpoint with one corresponding to another network.
 
-To initiate this process, we'll begin by updating the helper DDO example named "SimpleDownloadDataset.json." This example can be found in the "./metadata" folder, which is located at the root directory of the cloned Ocean CLI project.
+To initiate this process, we'll begin by updating the helper DDO example named "SimpleDownloadDataset.json". This example can be found in the "./metadata" folder, which is located at the root directory of the cloned Ocean CLI project.
 
-<pre><code>```json
+```json
 {
-  "@context": [
+	"@context": ["https://w3id.org/did/v1"],
-    "https://w3id.org/did/v1"
-  ],
 	"id": "",
 	"nftAddress": "",
 	"version": "4.1.0",
@@ -19,9 +17,7 @@ To initiate this process, we'll begin by updating the helper DDO example named "
 		"type": "dataset",
 		"name": "ocean-cli demo asset",
 		"description": "asset published using ocean cli tool",
-    "tags": [
+		"tags": ["test"],
-      "test"
-    ],
 		"author": "oceanprotocol",
 		"license": "https://market.oceanprotocol.com/terms",
 		"additionalInformation": {
@@ -48,8 +44,7 @@ To initiate this process, we'll begin by updating the helper DDO example named "
 			"timeout": 86400
 		}
 	],
-  "event": {
+	"event": {},
-  },
 	"nft": {
 		"address": "",
 		"name": "Ocean Data NFT",
@@ -62,8 +57,7 @@ To initiate this process, we'll begin by updating the helper DDO example named "
 	"purgatory": {
 		"state": false
 	},
-  "datatokens": [
+	"datatokens": [],
-  ],
 	"stats": {
 		"allocated": 0,
 		"orders": 0,
@@ -73,7 +67,6 @@ To initiate this process, we'll begin by updating the helper DDO example named "
 	}
 }
 ```
-</code></pre>
 
 Note: The provided example creates a consumable asset with a predetermined price of 2 OCEAN tokens. If you wish to modify this and create an asset that is freely accessible, you can do so by replacing the value of "stats.price.value" with 0 in the JSON example mentioned above.
 Next step is to run the npm run cli publish metadata/simpleDownloadDataset.json command

developers/ocean-cli/setting-environment-variables.md

@@ -4,26 +4,20 @@ To successfully configure the CLI tool, two essential steps must be undertaken:
 
 **Private Key Configuration**: The CLI tool necessitates the configuration of the account's private key. This private key serves as the means by which the CLI tool establishes a connection to the associated wallet. It plays a crucial role in authenticating and authorizing operations performed by the tool.
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 export MNEMONIC="XXXX"
 ```
-</code></pre>
 
 **RPC Endpoint Specification**: Additionally, it is imperative to specify the RPC endpoint that corresponds to the desired network for executing operations. The CLI tool relies on this user-provided RPC endpoint to connect to the network required for its functions. This connection to the network is vital as it enables the CLI tool to interact with the blockchain and execute operations seamlessly.
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 export RPC='XXXX'
 ```
-</code></pre>
 
 Furthermore, there are additional environment variables that can be configured to enhance the flexibility and customization of the environment. These variables include options such as the metadataCache URL and Provider URL, which can be specified if you prefer to utilize a custom deployment of Aquarius or Provider in contrast of the default settings. Moreover, you have the option to provide a custom address file path if you wish to use customized smart contracts or deployments for your specific use case. Remeber setting the next envariament variables is optional.
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 export AQUARIUS_URL='XXXX'
 export PROVIDER_URL='XXXX'
 export ADDRESS_FILE='../path/to/your/address-file'
 ```
-</code></pre>

developers/ocean-cli/usage.md

@@ -2,10 +2,8 @@
 
 The command <code>npm run cli h</code> returns a list of all commands and option flags.
 
-<pre><code>```bash
+```bash
-#!/bin/bash
 npm run cli h
 ```
-</code></pre>
 
-<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2FBCFAxxcCjwVPJfiKOOt1%2FScreenshot%202023-09-27%20at%2023.55.43.png?alt=media&token=76114c63-da9c-4d34-afdb-97b6bafca9d9" alt=""><figcaption></figcaption></figure>
+<figure><img src="https://files.gitbook.com/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FzQlpIJEeu8x5yl0OLuXn%2Fuploads%2FBCFAxxcCjwVPJfiKOOt1%2FScreenshot%202023-09-27%20at%2023.55.43.png?alt=media&token=76114c63-da9c-4d34-afdb-97b6bafca9d9" alt=""><figcaption>available options</figcaption></figure>