GITBOOK-616: Updates on the discover section

developers/barge/README.md

@@ -13,7 +13,7 @@ To explore all the available options and gain a deeper understanding of how to u
 By utilizing the Barge component, developers gain the freedom to conduct experiments, customize, and fine-tune their local development environment, and offers the flexibility to override the Docker image tag associated with specific components. By setting the appropriate environment variable before executing the start\_ocean.sh command, developers can customize the versions of various components according to their requirements. For instance, developers can modify the: `AQUARIUS_VERSION`, `PROVIDER_VERSION`, `CONTRACTS_VERSION`, `RBAC_VERSION`, and `ELASTICSEARCH_VERSION` environment variables to specify the desired Docker image tags for each respective component. 
 
 {% hint style="warning" %}
-⚠️ We've got an important heads-up about Barge that we want to share with you. Brace yourself, because it's not for the faint-hearted!  Here's the deal: the barge works great on Linux, but we need to be honest about its limitations on macOS. And, well, it doesn't work at all on Windows. Sorry, Windows users!
+⚠️ We've got an important heads-up about Barge that we want to share with you. Brace yourself, because **Barge is not for the faint-hearted**!  Here's the deal: the barge works great on Linux, but we need to be honest about its limitations on macOS. And, well, it doesn't work at all on Windows. Sorry, Windows users!
 
 To make things easier for everyone, we **strongly** recommend giving a try first on a **testnet**. Everything is configured already so it should be sufficient for your needs as well. Visit our [networks](../../discover/networks/) page to have clarity on the available test networks. ⚠️\
 

developers/contracts/README.md

@@ -16,12 +16,11 @@ However, Ocean V3 faced limitations in terms of flexibility. It lacked support f
 
 Ocean V4 effectively tackles these challenges by adopting **ERC721** **tokens** to explicitly represent the **base IP** as "data NFTs" (Non-Fungible Tokens). [**Data NFT**](data-nfts.md) owners can now deploy ERC20 "datatoken" contracts specific to their data NFTs, with each datatoken contract offering its own distinct licensing terms.
 
-By utilizing ERC721 tokens, Ocean V4 **grants data creators greater flexibility and control over licensing arrangements**. The introduction of data NFTs allows for the representation of [base IP](../../discover/glossary.md#base ip) and the creation of customized ERC20 datatoken contracts tailored to individual licensing requirements. 
+By utilizing ERC721 tokens, Ocean V4 **grants data creators greater flexibility and control over licensing arrangements**. The introduction of data NFTs allows for the representation of [base IP](../../discover/glossary.md#base-ip) and the creation of customized ERC20 datatoken contracts tailored to individual licensing requirements.
-
 
 <figure><img src="../../.gitbook/assets/contracts/v4_contracts_overview.png" alt=""><figcaption><p>Ocean Protocol V4 Smart Contracts</p></figcaption></figure>
 
-### [**Community monetization**](../community-monetization.md), to help the community create sustainable businesses.
+#### [**Community monetization**](../community-monetization.md), to help the community create sustainable businesses.
 
 Ocean V4 brings forth enhanced opportunities for marketplace operators, creating a conducive environment for the emergence of a thriving market of **third-party Providers**.
 
@@ -29,8 +28,7 @@ With Ocean V4, marketplace operators can unlock additional benefits. Firstly, th
 
 In addition to empowering marketplace operators, Ocean V4 facilitates the participation of third-party [Providers](../provider/) who can offer compute services in exchange for a fee. This paves the way for the development of a diverse marketplace of Providers. This model supports both centralized trusted providers, where data publishers and consumers have established trust relationships, as well as trustless providers that leverage decentralization or other privacy-preserving mechanisms.
 
-By enabling a marketplace of [Providers](../provider/), Ocean V4 fosters competition, innovation, and choice. It creates an ecosystem where various providers can offer their compute services, catering to the diverse needs of data publishers and consumers. Whether based on trust or privacy-preserving mechanisms, this expansion in provider options enhances the overall functionality and accessibility of the Ocean Protocol ecosystem.\
+By enabling a marketplace of [Providers](../provider/), Ocean V4 fosters competition, innovation, and choice. It creates an ecosystem where various providers can offer their compute services, catering to the diverse needs of data publishers and consumers. Whether based on trust or privacy-preserving mechanisms, this expansion in provider options enhances the overall functionality and accessibility of the Ocean Protocol ecosystem.
-
 
 Key features of the V4 smart contracts:
 

developers/contracts/fees.md

@@ -73,11 +73,11 @@ function updateOPCFee(uint256 _newSwapOceanFee, uint256 _newSwapNonOceanFee,
 Each of these fees plays a role in ensuring fair compensation and supporting the Ocean community. 
 
 | Fee              | Value in Ocean Market | Value in Other Markets                                   |
-| ---------------- | --------------------- | -------------------------------------------------------- |
+| ---------------- | :-------------------: | -------------------------------------------------------- |
-| Publisher Market | 0                     | Customizable in market config.                           |
+| Publisher Market |           0           | Customizable in market config.                           |
-| Consume Market   | 0                     | Customizable in market config.                           |
+| Consume Market   |           0           | Customizable in market config.                           |
-| Provider         | 0                     | Customizable. See details [below](fees.md#provider-fee). |
+| Provider         |           0           | Customizable. See details [below](fees.md#provider-fee). |
-| Ocean Community  | 0.03 DT               | 0.03 DT                                                  |
+| Ocean Community  |        0.03 DT        | 0.03 DT                                                  |
 
 ### Provider fee
 

developers/contracts/pricing-schemas.md

@@ -4,9 +4,9 @@ description: Choose the revenue model during asset publishing.
 
 # Pricing Schemas
 
-Ocean Protocol offers you flexible and customizable pricing options to monetize your valuable data assets. You have two main pricing models to choose from: 
+Ocean Protocol offers you flexible and customizable pricing options to monetize your valuable data assets. You have two main pricing models to choose from:
 
-* [Fixed pricing ](pricing-schemas.md#fixed-pricing)
+* [Fixed pricing](pricing-schemas.md#fixed-pricing)
 * [Free pricing](pricing-schemas.md#free-pricing)
 
 These models are designed to cater to your specific needs and ensure a smooth experience for data consumers.
@@ -64,9 +64,9 @@ Furthermore, Ocean Protocol recognizes that different data assets may have disti
 
 ### Fixed pricing
 
-With the fixed pricing model, you have the power to set a specific price for your data assets. This means that buyers interested in accessing your data will need to pay the designated amount of configured tokens. To make things even easier, Ocean automatically creates a special token called a "datatoken" behind the scenes. 
+With the fixed pricing model, you have the power to set a specific price for your data assets. This means that buyers interested in accessing your data will need to pay the designated amount of configured tokens. To make things even easier, Ocean automatically creates a special token called a "datatoken" behind the scenes.
 
-This datatoken represents the access right to your data, so buyers don't have to worry about the technical details. If you ever want to adjust the price of your dataset, you have the flexibility to do so whenever you need. 
+This datatoken represents the access right to your data, so buyers don't have to worry about the technical details. If you ever want to adjust the price of your dataset, you have the flexibility to do so whenever you need.
 
 The fixed pricing model relies on the [createNftWithErc20WithFixedRate](https://github.com/oceanprotocol/contracts/blob/main/contracts/ERC721Factory.sol#LL674C14-L674C45) in our smart contract, which securely stores the pricing information for assets published using this model.
 
@@ -122,16 +122,14 @@ There are two templates available: [ERC20Template](datatoken-templates.md#regula
 
 In the case of [ERC20TemplateEnterprise](datatoken-templates.md#enterprise-template), when you deploy a fixed rate exchange, the funds generated as revenue are automatically sent to the owner's address. The owner receives the revenue without any manual intervention.
 
-
-
 On the other hand, with [ERC20Template](datatoken-templates.md#regular-template), for a fixed rate exchange, the revenue is available at the fixed rate exchange level. The owner or the payment collector has the authority to manually retrieve the revenue.
 {% endhint %}
 
 ### Free pricing
 
-On the other hand, the free pricing model gives data consumers access to your asset without requiring them to make a direct payment. Users can freely access your data, with the only cost being the transaction fees associated with the blockchain network. 
+On the other hand, the free pricing model gives data consumers access to your asset without requiring them to make a direct payment. Users can freely access your data, with the only cost being the transaction fees associated with the blockchain network.
 
-In this model, datatokens are allocated to a dispenser smart contract, which dispenses data tokens to users at no charge when they access your asset. This is perfect if you want to make your data widely available and encourage collaboration. It's particularly suitable for individuals and organizations working in the public domain or for assets that need to comply with open access licenses.
+In this model, datatokens are allocated to a dispenser smart contract, which dispenses data tokens to users at no charge when they access your asset. This is perfect if you want to make your data widely available and encourage collaboration. It's particularly suitable for individuals and organizations working in the public domain or for assets that need to comply with open-access licenses.
 
 The fixed pricing model relies on the [createNftWithErc20WithDispenser](https://github.com/oceanprotocol/contracts/blob/main/contracts/ERC721Factory.sol#LL713C14-L713C45) in our smart contract, which securely stores the pricing information for assets published using this model.
 
@@ -184,8 +182,8 @@ function createNftWithErc20WithDispenser(
 
 </details>
 
-To make the most of these pricing models, you can rely on user-friendly libraries such as [Ocean.js ](../ocean.js/)and [Ocean.py](../ocean.py/), specifically developed for interacting with Ocean Protocol.&#x20;
+To make the most of these pricing models, you can rely on user-friendly libraries such as [Ocean.js ](../ocean.js)and [Ocean.py](../ocean.py), specifically developed for interacting with Ocean Protocol.
 
 With Ocean.js, you can use the [createFRE() ](../ocean.js/publish.md)function to effortlessly deploy a data NFT (non-fungible token) and datatoken with a fixed-rate exchange pricing model. Similarly, in Ocean.py, the [create\_url\_asset()](../ocean.py/publish-flow.md#create-an-asset-and-pricing-schema-simultaneously) function allows you to create an asset with fixed pricing. These libraries simplify the process of interacting with Ocean Protocol, managing pricing, and handling asset creation.
 
-By taking advantage of Ocean Protocol's pricing options and leveraging the capabilities of [Ocean.js](../ocean.js/) and [Ocean.py](../ocean.py/) (or by using the [Market](../../user-guides/using-ocean-market.md)), you can effectively monetize your data assets while ensuring transparent and seamless access for data consumers.&#x20;
+By taking advantage of Ocean Protocol's pricing options and leveraging the capabilities of [Ocean.js](../ocean.js) and [Ocean.py](../ocean.py) (or by using the [Market](../../user-guides/using-ocean-market.md)), you can effectively monetize your data assets while ensuring transparent and seamless access for data consumers.

developers/contracts/roles.md

@@ -15,8 +15,6 @@ The [data NFT](data-nfts.md) serves as the foundational intellectual property (I
 
 The NFT owner is the owner of the base-IP and is therefore at the highest level. The NFT owner can perform any action or assign any role but crucially, the NFT owner is the only one who can assign the manager role. Upon deployment or transfer of the data NFT, the NFT owner is automatically added as a manager. The NFT owner is also the only role that can’t be assigned to multiple users — the only way to share this role is via multi-sig or a DAO.
 
-
-
 ## Roles-NFT level
 
 <figure><img src="../../.gitbook/assets/contracts/roles_nft_level.png" alt=""><figcaption><p>Roles at the data NFT level</p></figcaption></figure>
@@ -25,13 +23,13 @@ The NFT owner is the owner of the base-IP and is therefore at the highest level.
 With the exception of the NFT owner role, all other roles can be assigned to multiple users.
 {% endhint %}
 
-There are several methods available to assign roles and permissions. One option is to utilize the [ocean.py](../ocean.py/) and [ocean.js](../ocean.js/) libraries that we provide. These libraries offer a streamlined approach for assigning roles and permissions programmatically.
+There are several methods available to assign roles and permissions. One option is to utilize the [ocean.py](../ocean.py) and [ocean.js](../ocean.js) libraries that we provide. These libraries offer a streamlined approach for assigning roles and permissions programmatically.
 
 Alternatively, for a more straightforward solution that doesn't require coding, you can utilize the network explorer of your asset's network. By accessing the network explorer, you can directly interact with the contracts associated with your asset. Below, we provide a few examples to help guide you through the process.
 
 ### Manager
 
-The ability to add or remove Managers is exclusive to the **NFT Owner**. If you are the NFT Owner and wish to add/remove a new manager, simply call the [addManager](https://github.com/oceanprotocol/contracts/blob/9e29194d910f28a4f0ef17ce6dc8a70741f63309/contracts/templates/ERC721Template.sol#L426)/[removeManager](https://github.com/oceanprotocol/contracts/blob/9e29194d910f28a4f0ef17ce6dc8a70741f63309/contracts/templates/ERC721Template.sol#L438) function within the ERC721Template contract. This function enables you to grant managerial permissions to the designated individual.&#x20;
+The ability to add or remove Managers is exclusive to the **NFT Owner**. If you are the NFT Owner and wish to add/remove a new manager, simply call the [addManager](https://github.com/oceanprotocol/contracts/blob/9e29194d910f28a4f0ef17ce6dc8a70741f63309/contracts/templates/ERC721Template.sol#L426)/[removeManager](https://github.com/oceanprotocol/contracts/blob/9e29194d910f28a4f0ef17ce6dc8a70741f63309/contracts/templates/ERC721Template.sol#L438) function within the ERC721Template contract. This function enables you to grant managerial permissions to the designated individual.
 
 <details>
 
@@ -252,9 +250,7 @@ function addMultipleUsersToRoles(address[] memory addresses, RolesType[] memory
 
 ### Roles & permissions in data NFT (ERC721) smart contract
 
-<table><thead><tr><th width="216">Action ↓ / Role →</th><th width="121">NFT Owner</th><th width="102">Manager</th><th width="160">ERC20 Deployer</th><th width="160">Store Updater</th><th width="170">Metadata Updater</th></tr></thead><tbody><tr><td>Set token URI</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Add manager</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Remove manager</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Clean permissions</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Set base URI</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Set Metadata state</td><td></td><td></td><td></td><td></td><td><strong>✓</strong></td></tr><tr><td>Set Metadata</td><td></td><td></td><td></td><td></td><td><strong>✓</strong></td></tr><tr><td>Create new datatoken</td><td></td><td></td><td><strong>✓</strong></td><td></td><td></td></tr><tr><td>Executes any other smart contract</td><td></td><td><strong>✓</strong></td><td></td><td></td><td></td></tr><tr><td>Set new key-value in store</td><td></td><td></td><td></td><td><strong>✓</strong></td><td></td></tr></tbody></table>
+<table><thead><tr><th width="216">Action ↓ / Role →</th><th width="122">NFT Owner</th><th width="102">Manager</th><th width="160">ERC20 Deployer</th><th width="160">Store Updater</th><th width="170">Metadata Updater</th></tr></thead><tbody><tr><td>Set token URI</td><td></td><td></td><td></td><td></td><td></td></tr><tr><td>Add manager</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Remove manager</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Clean permissions</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Set base URI</td><td><strong>✓</strong></td><td></td><td></td><td></td><td></td></tr><tr><td>Set Metadata state</td><td></td><td></td><td></td><td></td><td><strong>✓</strong></td></tr><tr><td>Set Metadata</td><td></td><td></td><td></td><td></td><td><strong>✓</strong></td></tr><tr><td>Create new datatoken</td><td></td><td></td><td><strong>✓</strong></td><td></td><td></td></tr><tr><td>Executes any other smart contract</td><td></td><td><strong>✓</strong></td><td></td><td></td><td></td></tr><tr><td>Set new key-value in store</td><td></td><td></td><td></td><td><strong>✓</strong></td><td></td></tr></tbody></table>
-
-##
 
 ## Roles-datatokens level
 

developers/ocean.js/configuration.md

@@ -15,13 +15,7 @@ cd my-ocean-project
 
 In the working directory create a `.env` file. The content of this file will store the values for following variables:
 
-| Variable name           | Description                                                                                                                                                                 | Required |
+<table><thead><tr><th width="241.33333333333331">Variable name</th><th>Description</th><th>Required</th></tr></thead><tbody><tr><td><strong>OCEAN_NETWORK</strong></td><td>Name of the network where the Ocean Protocol's smart contracts are deployed.</td><td>Yes</td></tr><tr><td><strong>OCEAN_NETWORK_URL</strong></td><td>The URL of the Ethereum node (along with API key for non-local networks)**</td><td>Yes</td></tr><tr><td><strong>PRIVATE_KEY</strong></td><td>The private key of the account which you want to use. A private key is made up of 64 hex characters. Make sure you have sufficient balance to pay for the transaction fees.</td><td>Yes</td></tr><tr><td><strong>AQUARIUS_URL</strong></td><td>The URL of the Aquarius. This value is needed when reading an asset from off-chain store.</td><td>No</td></tr><tr><td><strong>PROVIDER_URL</strong></td><td>The URL of the Provider. This value is needed when publishing a new asset or update an existing asset.</td><td>No</td></tr></tbody></table>
-| ----------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- |
-| **OCEAN\_NETWORK**      | Name of the network where the Ocean Protocol's smart contracts are deployed.                                                                                                | Yes      |
-| **OCEAN\_NETWORK\_URL** | The URL of the Ethereum node (along with API key for non-local networks)\*\*                                                                                                | Yes      |
-| **PRIVATE\_KEY**        | The private key of the account which you want to use. A private key is made up of 64 hex characters. Make sure you have sufficient balance to pay for the transaction fees. | Yes      |
-| **AQUARIUS\_URL**       | The URL of the Aquarius. This value is needed when reading an asset from off-chain store.                                                                                   | No       |
-| **PROVIDER\_URL**       | The URL of the Provider. This value is needed when publishing a new asset or update an existing asset.                                                                      | No       |
 
 {% hint style="info" %}
 Treat this file as a secret and do not commit this file to git or share the content publicly. If you are using git, then include this file name in `.gitignore` file.

developers/retrieve-datatoken-address.md

@@ -4,7 +4,7 @@ description: >-
   list the buyers of a datatoken
 ---
 
-# Find datatoken/data NFT addresses & Chain ID
+# Retrieve datatoken/data NFT addresses & Chain ID
 
 ### How to find the network, datatoken address, and data NFT address from an Ocean Market link?
 
@@ -38,7 +38,7 @@ For example, for the following DID:op: "did:op:1b26eda361c6b6d307c8a139c4aaf36aa
 
 Here are the networks and their corresponding chain IDs:
 
-```
+```json
 "mumbai: 80001"
 "polygon: 137"
 "bsc: 56"

discover/README.md

@@ -14,14 +14,17 @@ The concentration of vast datasets in the hands of a few organizations can lead
 
 * 📛 **Monopolistic Control**: When a small number of organizations control large amounts of data and AI tools, they gain a significant advantage over competitors. This can lead to monopolistic behavior, where these organizations dominate the market and stifle competition. As a result, innovation may suffer, prices can be inflated, and consumer choice becomes limited.
 * 📛 **Single Point of Failure**: Concentrating data in the hands of a few organizations creates a single point of failure. If a breach or data leak occurs within one of these organizations, the impact can be far-reaching, affecting a significant portion of the population whose data is held by that organization. The potential scale of such breaches can be much larger than if data were distributed across multiple entities, making the consequences more severe.
-* 📛 **Algorithmic Bias and Discrimination**: AI tools rely on data to make decisions and predictions. If the datasets used for training are biased or incomplete, AI systems can perpetuate and amplify existing biases and discrimination. Concentration of datasets in the hands of a few organizations can exacerbate this issue, as their AI models may reflect the biases present in their data, leading to unfair or discriminatory outcomes in various domains, such as hiring, lending, and criminal justice.
+* 📛 **Algorithmic Bias and Discrimination**: AI tools rely on data to make decisions and predictions. If the datasets used for training are biased or incomplete, AI systems can perpetuate and amplify existing biases and discrimination. The concentration of datasets in the hands of a few organizations can exacerbate this issue, as their AI models may reflect the biases present in their data, leading to unfair or discriminatory outcomes in various domains, such as hiring, lending, and criminal justice.
 * 📛 **Lack of Transparency and Accountability**: The complex nature of AI algorithms and the concentration of power make it difficult to understand and scrutinize the decisions made by these systems. When only a few organizations control AI tools, it can limit transparency and accountability. This lack of visibility can lead to distrust in AI systems, as people are unable to understand how decisions are being made or to challenge them when they are unfair or erroneous. The desire to extract value from data can create a conflict between the need to protect individual privacy and the pursuit of business interests.
+* 📛 **Lack of Privacy**: In today's digital age, traditional data-sharing methods often compromise privacy, raising concerns among individuals and organizations alike. With the increasing amount of personal and sensitive information being collected, stored, and shared, it has become essential to address it.
+* 📛 **Limited Data Monetization**: Many data owners struggle to monetize their data assets effectively due to various factors. Firstly, they often lack data-driven business models that can translate their data into valuable insights and actionable opportunities. Additionally, data quality and trust play a critical role, as inaccurate or unreliable data hinders the development of data-driven products and erodes trust among potential buyers. Limited market access is another challenge, with the fragmented data economy and the absence of standardized platforms or marketplaces making it difficult for data owners to connect with the right audience.
+* 📛 **Intermediaries and Inefficiencies**: In the current data economy, intermediaries play a significant role in facilitating data transactions between data owners and data consumers. However, the reliance on intermediaries introduces additional costs and complexities that can hinder efficient data monetization.
 
-If we don't enable personal sovereignty over our data, then we could be at the mercy of Big Tech's decisions again in the future of Web3. What's worse, we could even be excluded from developing AI innovations entirely. ☢️☠️
+If we don't enable personal **sovereignty** over our data, then we could be at the mercy of Big Tech's decisions again in the future of Web3. What's worse, we could even be excluded from developing AI innovations entirely. ☢️☠️
 
 {% embed url="https://giphy.com/clips/spongebob-PPEmM68bHy2zEZUcs7" %}
 
-That's why we made the decision to take action, and it led to the creation of **Ocean Protocol**.
+That's why we made the decision to take action, and it led to the creation of the **Ocean Protocol**.
 
 **Ocean Protocol aims to kick-start a new data economy by giving power back to people and giving researchers the data they need. Ocean Protocol technology enables data to become an asset.**
 

discover/explore.md

@@ -9,18 +9,11 @@ Ocean Protocol is a **decentralized data exchange protocol** that aims to unlock
 Ocean Protocol is used for a variety of purposes, including:
 
 1. **Data Sharing**: Ocean Protocol allows individuals and organizations to share data securely and privately, enabling data owners to monetize their data assets while maintaining control over their data.
-2. **Data Monetization**: Data owners can monetize their data by offering it for sale or by providing data services through compute-to-data (C2D) capabilities. Data consumers can access and utilize data assets to train machine learning models, perform data analysis, and drive insights.
+2. **Data Monetization**: Data owners can monetize their data by offering it for sale or by providing data services through compute-to-data (C2D) capabilities. Data consumers can access and utilize data assets.
 3. **Decentralized Data Marketplaces**: Ocean Protocol facilitates the creation of decentralized data marketplaces where data providers can list their data assets and data consumers can discover and access them. These marketplaces operate on a peer-to-peer basis, eliminating the need for intermediaries and providing more efficient and transparent data transactions.
 4. **AI Development**: Ocean Protocol supports the development of AI models by providing access to diverse and high-quality datasets. Data scientists and AI developers can leverage these datasets to train and improve their models, leading to more accurate and robust AI systems.
 
-Ocean Protocol exists to address several challenges in the current data ecosystem:
+By leveraging **blockchain technology** and **smart contracts**, Ocean Protocol offers **open-source tools** to securely publish [NFTs](../developers/contracts/data-nfts.md) of your data and algorithms to seamlessly collaborate, trade, and innovate with others.
-
-1. **Data Silos**: Data is often locked within organizations and inaccessible to others. Ocean Protocol aims to break down these data silos and enable data sharing across different entities, fostering collaboration and innovation.
-2. **Lack of Privacy**: Traditional data sharing methods often compromise privacy. Ocean Protocol incorporates privacy-preserving techniques, such as encryption and access control, to ensure that data owners maintain control over their data and only share it with authorized parties.
-3. **Limited Data Monetization**: Many data owners struggle to monetize their data assets effectively. Ocean Protocol provides a platform for data owners to list their data assets and earn revenue by selling or offering data services, creating new opportunities for data monetization.
-4. **Intermediaries and Inefficiencies**: The current data economy rely on intermediaries, which introduce additional costs and complexities. Ocean Protocol eliminates intermediaries by leveraging blockchain technology and smart contracts, enabling direct peer-to-peer transactions and reducing friction in data exchange.
-
-By leveraging **blockchain technology** and **smart contracts**, Ocean Protocol offers **open-source tools** to securely publish NFTs of your data and algorithms to seamlessly collaborate, trade, and innovate with others.
 
 <figure><img src="../.gitbook/assets/architecture/decentralized_exchanges_marketplaces.png" alt="" width="375"><figcaption><p>A vast ocean of data awaits you...</p></figcaption></figure>
 
@@ -144,4 +137,4 @@ As an Ocean Ambassador, you become an advocate for the protocol, promoting its v
 
 </details>
 
-This is just the beginning of what Ocean Protocol has to offer. Join us as we explore, innovate, and push the boundaries of what's possible with decentralized data. Together, we can shape a future where data is accessible, secure, and empowers individuals and organizations alike. Let's dive in and discover the endless possibilities of Ocean Protocol :ocean:
+This is just the beginning of what Ocean Protocol has to offer. Join us as we explore, innovate, and push the boundaries of what's possible with decentralized data. Together, we can shape a future where data is accessible, secure and empowers individuals and organizations alike. Let's dive in and discover the endless possibilities of Ocean Protocol :ocean:

user-guides/asset-hosting/README.md

@@ -27,5 +27,5 @@ When you publish your asset as an NFT, then the URL/TX ID/CID required to access
 We recommend implementing a security policy that allows **only the Provider's IP address to access the file** and blocks requests from other unauthorized actors is recommended. Since not all hosting services provide this feature, **you must carefully consider the security features while choosing a hosting service.**
 
 {% hint style="warning" %}
-**Please use a proper hosting solution to keep your files.** Systems like `Google Drive` are not specifically designed for this use case. They include various virus checks and rate limiters that prevent the `Provider`downloading the asset once it was purchased.
+**Please use a proper hosting solution to keep your files.** Systems like `Google Drive` are not specifically designed for this use case. They include various virus checks and rate limiters that prevent the [`Provider`](../../developers/provider/)downloading the asset once it was purchased.
 {% endhint %}

user-guides/asset-hosting/aws.md

@@ -76,7 +76,7 @@ To have the bucket granted public access, its policy needs to be modified likewi
 
 Note that the `<BUCKET-NAME>` must be chosen from the personal buckets dashboard.
 
-```JSON
+```json
 {
   "Version": "2012-10-17",
   "Statement": [