GITBOOK-484: Moved the revenue page

SUMMARY.md

@@ -38,10 +38,10 @@
     * [Data NFTs and Datatokens](developers/contracts/datanft-and-datatoken.md)
     * [Datatoken Templates](developers/contracts/datatoken-templates.md)
     * [Roles](developers/contracts/roles.md)
-    * [Revenue](developers/contracts/revenue.md)
     * [Pricing Schemas](developers/asset-pricing.md)
     * [Fees](developers/fees.md)
     * [Metadata](developers/contracts/metadata.md)
+  * [Revenue](developers/revenue.md)
   * [Fractional Ownership](developers/fractional-ownership.md)
   * [Community Monetization](developers/community-monetization.md)
   * [Identifiers & Metadata](developers/Identifiers-Metadata.md)

developers/community-monetization.md

@@ -16,7 +16,7 @@ The datasets can take one of many shapes. For AI use cases, they may be raw data
 
 The first opportunity of data NFTs is the potential to sell the base intellectual property (IP) as an exclusive license to others. This is akin to EMI selling the Beatles’ master tapes to Universal Music: whoever owns the masters has the right to create records, CDs, and digital [sub-licenses](../discover/glossary.md#sub-licensee). It’s the same for data: as the data NFT owner you have the **exclusive right** to create ERC20 datatoken sub-licenses. With Ocean V4, this right is now transferable as a data NFT. You can sell these data NFTs in **OpenSea** and other NFT marketplaces.
 
-If you’re part of an established organization or a growing startup, you’ll also love the new role structure that comes with data NFTs. For example, you can specify a different address to collect [revenue](contracts/revenue.md) compared to the address that owns the NFT. It’s now possible to fully administer your project through these [roles](contracts/roles.md).
+If you’re part of an established organization or a growing startup, you’ll also love the new role structure that comes with data NFTs. For example, you can specify a different address to collect [revenue](revenue.md) compared to the address that owns the NFT. It’s now possible to fully administer your project through these [roles](contracts/roles.md).
 
 **In short, if you have data to sell, then Ocean V4 gives you superpowers to scale up and manage your data project. We hope this enables you to bring your data to new audiences and increase your profits.**
 
@@ -30,7 +30,7 @@ Another new opportunity is using your own **ERC20** token in your dApp, where it
 
 ### 3. Running Your Own Provider
 
-Now this is a completely brand new opportunity to start generating [revenue](contracts/revenue.md) — running your own [provider](https://github.com/oceanprotocol/provider). We have been aware for a while now that many of you haven’t taken up the opportunity to run your own provider, and the reason seems obvious — there aren’t strong enough incentives to do so.
+Now this is a completely brand new opportunity to start generating [revenue](revenue.md) — running your own [provider](https://github.com/oceanprotocol/provider). We have been aware for a while now that many of you haven’t taken up the opportunity to run your own provider, and the reason seems obvious — there aren’t strong enough incentives to do so.
 
 For those that aren’t aware, [Ocean Provider](provider/) is the proxy service that’s responsible for encrypting/ decrypting the data and streaming it to the consumer. It also validates if the user is allowed to access a particular data asset or service. It’s a crucial component in Ocean’s architecture.
 

developers/contracts/revenue.md

@@ -1,54 +0,0 @@
----
-description: Explore and manage the revenue generated from your data NFTs.
----
-
-# Revenue
-
-Having a [data NFT](data-nfts.md) that generates revenue continuously, even when you're not actively involved, is an excellent source of income. This revenue stream allows you to earn consistently without actively dedicating your time and effort. Each time someone buys access to your NFT, you receive money, further enhancing the financial benefits. This steady income allows you to enjoy the rewards of your asset while minimizing the need for constant engagement. :moneybag:
-
-<figure><img src="../../.gitbook/assets/sponge-money.gif" alt=""><figcaption><p>Make it rain</p></figcaption></figure>
-
-By default, the revenue generated from a [data NFT](data-nfts.md) is directed to the [owner](roles.md#nft-owner) of the NFT. This arrangement automatically updates whenever the data NFT is transferred to a new owner. C
-
-However, there are scenarios where you may prefer the revenue to be sent to a different account instead of the owner. This can be accomplished by designating a new payment collector. This feature becomes particularly beneficial when the data NFT is owned by an organization or enterprise rather than an individual.
-
-{% hint style="info" %}
-There are two templates available: [ERC20Template](datatoken-templates.md#regular-template) and [ERC20TemplateEnterprise](datatoken-templates.md#enterprise-template).
-
-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 %}
-
-
-
-There are several methods available for establishing a new **payment collector**. You have the option to utilize the ERC20Template/ERC20TemplateEnterprise contract directly. Another approach is to leverage the [ocean.py](../ocean.py/) and [ocean.js](../ocean.js/) libraries. Alternatively, you can employ the network explorer associated with your asset. Lastly, you can directly set it up within the Ocean Market.
-
-Here are some examples of how to set up a new payment collector using the mentioned methods:
-
-1. Using [Ocean.js](https://github.com/oceanprotocol/ocean.js/blob/ae2ff1ccde53ace9841844c316a855de271f9a3f/src/contracts/Datatoken.ts#L393).&#x20;
-
-```typescript
-datatokenAddress = 'Your datatoken address'
-paymentCollectorAddress = 'New payment collector address'
-
-await datatoken.setPaymentCollector(datatokenAddress, callerAddress, paymentCollectorAddress)
-```
-
-2. Using [Ocean.py](https://github.com/oceanprotocol/ocean.py/blob/bad11fb3a4cb00be8bab8febf3173682e1c091fd/ocean\_lib/models/test/test\_datatoken.py#L39).
-
-```python
-datatokenAddress = 'Your datatoken address'
-paymentCollectorAddress = 'New payment collector address'
-
-datatoken.setPaymentCollector(paymentCollectorAddress, {"from": publisher_wallet})
-```
-
-3. Using the [Ocean Market](https://market.oceanprotocol.com/)
-
-Go to the asset detail page and then click on “Edit Asset” and then scroll down to the field called “Payment Collector Address”. Add the new Ethereum address in this field and then click “Submit“. Finally, you will then need to sign two transactions to finalize the update.
-
-<figure><img src="../../.gitbook/assets/market/change-payment-collector.png" alt=""><figcaption><p>Update payment collector</p></figcaption></figure>
-

developers/revenue.md

@@ -0,0 +1,54 @@
+---
+description: Explore and manage the revenue generated from your data NFTs.
+---
+
+# Revenue
+
+Having a [data NFT](contracts/data-nfts.md) that generates revenue continuously, even when you're not actively involved, is an excellent source of income. This revenue stream allows you to earn consistently without actively dedicating your time and effort. Each time someone buys access to your NFT, you receive money, further enhancing the financial benefits. This steady income allows you to enjoy the rewards of your asset while minimizing the need for constant engagement. :moneybag:
+
+<figure><img src="../.gitbook/assets/sponge-money.gif" alt=""><figcaption><p>Make it rain</p></figcaption></figure>
+
+By default, the revenue generated from a [data NFT](contracts/data-nfts.md) is directed to the [owner](contracts/roles.md#nft-owner) of the NFT. This arrangement automatically updates whenever the data NFT is transferred to a new owner. C
+
+However, there are scenarios where you may prefer the revenue to be sent to a different account instead of the owner. This can be accomplished by designating a new payment collector. This feature becomes particularly beneficial when the data NFT is owned by an organization or enterprise rather than an individual.
+
+{% hint style="info" %}
+There are two templates available: [ERC20Template](contracts/datatoken-templates.md#regular-template) and [ERC20TemplateEnterprise](contracts/datatoken-templates.md#enterprise-template).
+
+In the case of [ERC20TemplateEnterprise](contracts/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](contracts/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 %}
+
+
+
+There are several methods available for establishing a new **payment collector**. You have the option to utilize the ERC20Template/ERC20TemplateEnterprise contract directly. Another approach is to leverage the [ocean.py](ocean.py/) and [ocean.js](ocean.js/) libraries. Alternatively, you can employ the network explorer associated with your asset. Lastly, you can directly set it up within the Ocean Market.
+
+Here are some examples of how to set up a new payment collector using the mentioned methods:
+
+1. Using [Ocean.js](https://github.com/oceanprotocol/ocean.js/blob/ae2ff1ccde53ace9841844c316a855de271f9a3f/src/contracts/Datatoken.ts#L393).&#x20;
+
+```typescript
+datatokenAddress = 'Your datatoken address'
+paymentCollectorAddress = 'New payment collector address'
+
+await datatoken.setPaymentCollector(datatokenAddress, callerAddress, paymentCollectorAddress)
+```
+
+2. Using [Ocean.py](https://github.com/oceanprotocol/ocean.py/blob/bad11fb3a4cb00be8bab8febf3173682e1c091fd/ocean\_lib/models/test/test\_datatoken.py#L39).
+
+```python
+datatokenAddress = 'Your datatoken address'
+paymentCollectorAddress = 'New payment collector address'
+
+datatoken.setPaymentCollector(paymentCollectorAddress, {"from": publisher_wallet})
+```
+
+3. Using the [Ocean Market](https://market.oceanprotocol.com/)
+
+Go to the asset detail page and then click on “Edit Asset” and then scroll down to the field called “Payment Collector Address”. Add the new Ethereum address in this field and then click “Submit“. Finally, you will then need to sign two transactions to finalize the update.
+
+<figure><img src="../.gitbook/assets/market/change-payment-collector.png" alt=""><figcaption><p>Update payment collector</p></figcaption></figure>
+