Issue-#908: Fix image and did-ddo page link

content/concepts/did-ddo.md

@@ -15,7 +15,7 @@ Decentralized identifiers (DIDs) are a type of identifier that enable verifiable
 
 A DID Document (DDO) is a JSON blob that holds information about the DID. Given a DID, a _resolver_ will return the DDO of that DID.
 
-## Rules for DIDs & DDOs
+## Rules for DID & DDO
 
 An _asset_ in Ocean represents a downloadable file, compute service, or similar. Each asset is a _resource_ under the control of a _publisher_. The Ocean network itself does _not_ store the actual resource (e.g. files).
 
@@ -129,7 +129,7 @@ Example:
 An asset of type `algorithm` has additional attributes under `metadata.algorithm`, describing the algorithm and the Docker environment it is supposed to be run under.
 
 | Attribute                | Type                                        | Required | Description                                                                                |
-| --------------- | --------------------------- | -------- | ------------------------------------------------------------------------------------------ |
+| ------------------------ | ------------------------------------------- | -------- | ------------------------------------------------------------------------------------------ |
 | **`language`**           | `string`                                    |          | Language used to implement the software.                                                   |
 | **`version`**            | `string`                                    |          | Version of the software preferably in [SemVer](https://semver.org) notation. E.g. `1.0.0`. |
 | **`consumerParameters`** | [Consumer Parameters](#consumer-parameters) |          | An object the defines required consumer input before running the algorithm                 |
@@ -163,7 +163,7 @@ The `container` object has the following attributes defining the Docker image fo
         "tag": "latest",
         "checksum": "44e10daa6637893f4276bb8d7301eb35306ece50f61ca34dcab550"
       },
-    "consumerParameters":{},
+      "consumerParameters": {}
     }
   }
 }
@@ -176,7 +176,7 @@ Services define the access for an asset, and each service is represented by its
 An asset should have at least one service to be actually accessible, and can have as many services which make sense for a specific use case.
 
 | Attribute                | Type                                        | Required                        | Description                                                                                                                                  |
-| ---------------------- | --------------------------- | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
+| ------------------------ | ------------------------------------------- | ------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------- |
 | **`id`**                 | `string`                                    | **✓**                           | Unique ID                                                                                                                                    |
 | **`type`**               | `string`                                    | **✓**                           | Type of service (`access`, `compute`, `wss`, etc.                                                                                            |
 | **`name`**               | `string`                                    |                                 | Service friendly name                                                                                                                        |
@@ -202,7 +202,6 @@ Example:
 
 During the publish process, file URLs must be encrypted with a respective _Provider_ API call before storing the DDO on-chain. For this an array of objects defining the storage access details are sent.
 
-
 Type of objects supported :
 
 <table>
@@ -257,7 +256,6 @@ First class integrations supported in the future :
 <tr><td>"sql"</td><td>Sql connection, dataset is generated by a query</td><td>&nbsp;</td></tr>
 </table>
 
-
 A service can contain multiple files, using multiple storage types.
 
 Example:
@@ -268,7 +266,6 @@ Example:
     "type": "url",
     "url": "https://url.com/file1.csv",
     "method": "GET"
-
   },
   {
     "type": "ipfs",
@@ -377,7 +374,6 @@ An asset with a service of `type` `compute` has the following additional attribu
   </tbody>
 </table>
 
-
 The `publisherTrustedAlgorithms ` is an array of objects with the following structure:
 
 | Attribute                      | Type     | Required | Description                                                               |
@@ -477,7 +473,6 @@ where:
 - description = description of this element
 - options = for select types, a list of options
 
-
 Example:
 
 ```json
@@ -536,7 +531,6 @@ Algorithms will have access to a JSON file located at /data/inputs/algoCustomDat
 }
 ```
 
-  
 ### Credentials
 
 By default, a consumer can access a resource if they have 1 datatoken. _Credentials_ allow the publisher to optionally specify more fine-grained permissions.
@@ -622,14 +616,14 @@ Each asset has a state, which is held by the NFT contract. The possible states a
 
 The following fields are added by _Aquarius_ in its DDO response for convenience reasons, where an asset returned by _Aquarius_ inherits the DDO fields stored on-chain.
 
-These additional fields are never stored on-chain, and are never taken into consideration when [hashing the DDO](#ddo-hash).
+These additional fields are never stored on-chain, and are never taken into consideration when [hashing the DDO](#ddo-checksum).
 
 ### NFT
 
 The `nft` object contains information about the ERC721 NFT contract which represents the intellectual property of the publisher.
 
 | Attribute      | Type                   | Description                                                               |
-| ------------- | ---------------------- | ------------------------------------------------------------------------- |
+| -------------- | ---------------------- | ------------------------------------------------------------------------- |
 | **`address`**  | `string`               | Contract address of the deployed ERC721 NFT contract.                     |
 | **`name`**     | `string`               | Name of NFT set in contract.                                              |
 | **`symbol`**   | `string`               | Symbol of NFT set in contract.                                            |
@@ -736,7 +730,7 @@ Example:
 The `stats` section contains different statistics fields.
 
 | Attribute    | Type     | Description                                                                                                  |
-| -------------- | -------- | ------------------------------------------------------------------------------------------------------------- |
+| ------------ | -------- | ------------------------------------------------------------------------------------------------------------ |
 | **`orders`** | `number` | How often an asset was ordered, meaning how often it was either downloaded or used as part of a compute job. |
 
 Example:
@@ -767,7 +761,8 @@ Example:
     "author": "OPF",
     "license": "https://market.oceanprotocol.com/terms"
   },
-	"services": [{
+  "services": [
+    {
       "id": "1",
       "type": "access",
       "files": "0x044736da6dae39889ff570c34540f24e5e084f4e5bd81eff3691b729c2dd1465ae8292fc721e9d4b1f10f56ce12036c9d149a4dab454b0795bd3ef8b7722c6001e0becdad5caeb2005859642284ef6a546c7ed76f8b350480691f0f6c6dfdda6c1e4d50ee90e83ce3cb3ca0a1a5a2544e10daa6637893f4276bb8d7301eb35306ece50f61ca34dcab550b48181ec81673953d4eaa4b5f19a45c0e9db4cd9729696f16dd05e0edb460623c843a263291ebe757c1eb3435bb529cc19023e0f49db66ef781ca692655992ea2ca7351ac2882bf340c9d9cb523b0cbcd483731dc03f6251597856afa9a68a1e0da698cfc8e81824a69d92b108023666ee35de4a229ad7e1cfa9be9946db2d909735",
@@ -776,7 +771,8 @@ Example:
       "datatokenAddress": "0x123",
       "serviceEndpoint": "https://myprovider.com",
       "timeout": 0,
-			"consumerParameters": [{
+      "consumerParameters": [
+        {
           "name": "surname",
           "type": "text",
           "label": "Name",
@@ -807,7 +803,8 @@ Example:
         "allowRawAlgorithm": false,
         "allowNetworkAccess": true,
         "publisherTrustedAlgorithmPublishers": ["0x234", "0x235"],
-				"publisherTrustedAlgorithms": [{
+        "publisherTrustedAlgorithms": [
+          {
             "did": "did:op:123",
             "filesChecksum": "100",
             "containerSectionChecksum": "200"
@@ -822,14 +819,18 @@ Example:
     }
   ],
   "credentials": {
-		"allow": [{
+    "allow": [
+      {
         "type": "address",
         "values": ["0x123", "0x456"]
-		}],
+      }
-		"deny": [{
+    ],
+    "deny": [
+      {
         "type": "address",
         "values": ["0x2222", "0x333"]
-		}]
+      }
+    ]
   },
 
   "nft": {
@@ -842,7 +843,8 @@ Example:
     "tokenURI": "xxx"
   },
 
-	"datatokens": [{
+  "datatokens": [
+    {
       "address": "0x000000",
       "name": "Datatoken 1",
       "symbol": "DT-1",

data/sidebars/concepts.yml

@@ -20,7 +20,7 @@
 
 - group: Specifying Assets
   items:
-    - title: DIDs & DDOs
+    - title: DID & DDO
       link: /concepts/did-ddo/
 
 - group: Contribute