Issue-#1048: Fix broken links and remove duplicate resources

core-concepts/architecture.md

@@ -9,7 +9,7 @@ description: Data NFTs and datatokens architecture
 
 Here is the Ocean architecture.
 
-![Ocean Protocol tools architecture](<images/architecture (1) (1).png>)
+![Ocean Protocol tools architecture](./images/architecture.png)
 
 Here’s an overview of the figure.
 
@@ -18,11 +18,11 @@ Here’s an overview of the figure.
   * **Aquarius**: Provides metadata cache for faster search by caching on-chain data into elasticsearch
   * **Provider**: Facilitates downloading assets, DDO encryption, and communicating with `operator-service` for Compute-to-Data jobs.
   * **The Graph**: It is a 3rd party tool that developers can utilize the libraries to build their custom applications and marketplaces.
-* The lowest level has the **smart contracts**. The smart contracts are deployed on the Ethereum mainnet and other compatible networks. Libraries encapsulate the calls to these smart contracts and provide features like publishing new assets, facilitating consumption, managing pricing, and much more. To see the supported networks click [here](../concepts/networks/).
+* The lowest level has the **smart contracts**. The smart contracts are deployed on the Ethereum mainnet and other compatible networks. Libraries encapsulate the calls to these smart contracts and provide features like publishing new assets, facilitating consumption, managing pricing, and much more. To see the supported networks click [here](./networks.md).
 
 ### Data NFTs, Datatokens and Access Control Tools
 
-Data NFTs are based on [ERC721](https://eips.ethereum.org/EIPS/eip-721) standard. The publisher can use Marketplace or client libraries to deploy a new data NFT contract. To save gas fees, it uses [ERC1167](https://eips.ethereum.org/EIPS/eip-1167) proxy approach on the **ERC721 template**. Publisher can then assign manager role to other Ethereum addresses who can deploy new datatoken contracts and even mint them. Each datatoken contract is associated with one data NFT contract. Click [here](../concepts/datanft-and-datatoken/) to further read about data NFTs and datatokens.
+Data NFTs are based on [ERC721](https://eips.ethereum.org/EIPS/eip-721) standard. The publisher can use Marketplace or client libraries to deploy a new data NFT contract. To save gas fees, it uses [ERC1167](https://eips.ethereum.org/EIPS/eip-1167) proxy approach on the **ERC721 template**. Publisher can then assign manager role to other Ethereum addresses who can deploy new datatoken contracts and even mint them. Each datatoken contract is associated with one data NFT contract. Click [here](./datanft-and-datatoken.md) to further read about data NFTs and datatokens.
 
 ERC721 data NFTs represent holding copyright/base IP of a data asset, and ERC20 datatokens represent licenses to access the asset by downloading the content or running Compute-to-Data jobs.
 
@@ -57,7 +57,7 @@ Complementary to Ocean Market, Ocean has reference code to ease building **third
 
 Marketplaces use the Metadata of the asset for discovery. Metadata consists of information like the type of asset, name of the asset, creation date, license, etc. Each data asset can have a [decentralized identifier](https://w3c-ccg.github.io/did-spec/) (DID) that resolves to a DID document (DDO) for associated metadata. The DDO is essentially [JSON](https://www.json.org/) filling in metadata fields. For more details on working with OCEAN DIDs check out the [DID concept documentation](https://docs.oceanprotocol.com/concepts/did-ddo/). The [DDO Metadata documentation](https://docs.oceanprotocol.com/concepts/ddo-metadata/) goes into more depth regarding metadata structure.
 
-[OEP8](../concepts/did-ddo/) specifies Ocean metadata schema, including fields that must be filled. It’s based on the public [DataSet schema from schema.org](https://schema.org/Dataset).
+[OEP8](./did-ddo.md) specifies Ocean metadata schema, including fields that must be filled. It’s based on the public [DataSet schema from schema.org](https://schema.org/Dataset).
 
 Ocean uses the Ethereum mainnet and other compatible networks as an **on-chain metadata store**, i.e. to store both DID and DDO. This means that once the transaction fee is paid, there are no further expenses or devops work needed to ensure metadata availability into the future, aiding in the discoverability of data assets. It also simplifies integration with the rest of the Ocean system, which is Ethereum-based. Storage cost on Ethereum mainnet is not negligible, but not prohibitive and the other benefits are currently worth the trade-off compared to alternatives.
 

core-concepts/asset-pricing.md

@@ -7,7 +7,7 @@ description: Choose the revenue model during asset publishing
 
 Ocean Protocol offers 3 types of pricing options for asset monetization. The publisher can choose a pricing model which best suits their needs while publishing an asset. The pricing model selected cannot be changed once the asset is published.
 
-The price of an asset is determined by the number of Ocean tokens a buyer must pay to access the asset. When users pay the right amount of Ocean tokens, they get a _datatoken_ in their wallets, a tokenized representation of the access right stored on the blockchain. To read more about datatoken and data NFT click [here](../concepts/datanft-and-datatoken/).
+The price of an asset is determined by the number of Ocean tokens a buyer must pay to access the asset. When users pay the right amount of Ocean tokens, they get a _datatoken_ in their wallets, a tokenized representation of the access right stored on the blockchain. To read more about datatoken and data NFT click [here](./datanft-and-datatoken.md).
 
 ### Fixed pricing
 
@@ -19,7 +19,7 @@ Publishers can choose this fixed pricing model when they do not want Automated M
 
 The image below shows how to set the fixed pricing of an asset in the Ocean's Marketplace. Here, the price of the asset is set to 10 Ocean tokens.
 
-![fixed-asset-pricing](<images/fixed-asset-pricing (1) (1).png>)
+![fixed-asset-pricing](./images/fixed-asset-pricing.png)
 
 ### Dynamic pricing
 
@@ -39,7 +39,7 @@ Publishers can set the pricing model of an asset to Dynamic pricing if they want
 
 The image below shows how to set the Dynamic pricing of an asset in the Ocean's Marketplace. Here, the asset price is initially set to 50 Ocean tokens.
 
-![dynamic-asset-pricing](<images/dynamic-asset-pricing (1) (1).png>)
+![dynamic-asset-pricing](./images/dynamic-asset-pricing.png)
 
 Ocean Protocol also allows publishers to set the pricing using ocean.js and ocean.py library.
 
@@ -75,4 +75,4 @@ Free pricing is suitable for individuals and organizations working in the public
 
 The image below shows how to set free access to an asset in the Ocean's Marketplace.
 
-![free-asset-pricing](<images/free-asset-pricing (1) (1).png>)
+![free-asset-pricing](./images/free-asset-pricing.png)

core-concepts/contributing.md

@@ -9,7 +9,7 @@ To report a bug that isn't a vulnerability, go to the relevant GitHub repository
 
 Before reporting a bug, search existing open and closed issues and PRs to see if something has already been reported. If not, then go ahead and create a new bug report, following the structure suggested in the issue template.
 
-To report a vulnerability, you may do so in a [less public manner](/concepts/vulnerabilities/).
+To report a vulnerability, you may do so in a [less public manner](./vulnerabilities.md).
 
 ## Suggest a new feature
 
@@ -25,8 +25,8 @@ Before you start coding right away, please follow those basic guidelines:
 
 - If no issue for your case is present, open one first before starting to work on something, so it can be discussed.
 - Make yourself familiar with eventual repository-specific contribution requirements and code style requirements.
-- Because of the weird world of intellectual property, we need you to follow the [legal requirements](/concepts/legal-reqs/) for contributing code.
-- Be excellent to each other, as outlined in our [Contributor Code of Conduct](/concepts/code-of-conduct/).
+- Because of the weird world of intellectual property, we need you to follow the [legal requirements](./legal-reqs.md) for contributing code.
+- Be excellent to each other, as outlined in our [Contributor Code of Conduct](./code-of-conduct.md).
 
 ### Workflow
 

core-concepts/datanft-and-datatoken.md

@@ -11,7 +11,7 @@ A non-fungible token stored on the blockchain represents a unique asset. NFTs ca
 
 Fungible tokens represent fungible assets. If you have 5 ETH and Alice has 5 ETH, you and Alice could swap your ETH and your final holdings remain the same. They're apples-to-apples. Licenses (contracts) to access a copyrighted asset are naturally fungible - they can be swapped with each other.
 
-![Data NFT and datatoken](<images/datanft-and-datatoken (1) (1).png>)
+![Data NFT and datatoken](./images/datanft-and-datatoken.png)
 
 ### High-Level Architecture
 
@@ -37,7 +37,7 @@ ERC721 tokens are non-fungible, thus cannot be used for automatic price discover
 
 ### High-Level Behavior
 
-![Flow](<images/use-case (1) (1).png>)
+![Flow](./images/use-case.png)
 
 Here's an example.
 

core-concepts/did-ddo.md

@@ -33,7 +33,7 @@ The DDO is stored on-chain as part of the NFT contract and stored in encrypted f
 
 Here is the flow:
 
-![DDO flow](<images/ddo-flow (1) (1).png>)
+![DDO flow](./images/ddo-flow.png)
 
 <details>
 

using-ocean-market/marketplace-publish-data-asset.md

@@ -89,11 +89,11 @@ With the _free pricing_ schema, the publisher provides an asset that is free to
 
 With the _dynamic pricing_ schema, the publisher sets the asset price and creates a datatoken liquidity pool with an initial amount of OCEAN tokens.
 
-For more information on the pricing models, please refer this [document](../concepts/asset-pricing/).
+For more information on the pricing models, please refer this [document](../core-concepts/asset-pricing.md).
 
 The publisher can also change the **Swap Fee** of the liquidity pool.
 
-For a deep dive into the fee structure, please refer to this [document](../concepts/fees/).
+For a deep dive into the fee structure, please refer to this [document](../core-concepts/fees.md).
 
 ![publish part-3](./images/marketplace/publish-3.png)
 
@@ -105,13 +105,9 @@ For a deep dive into the fee structure, please refer to this [document](../conce
 
 ![publish part-5](./images/marketplace/publish-5.png)
 
-\
-
 
 ![publish part-6](./images/marketplace/publish-6.png)
 
-\
-
 
 ![publish part-7](./images/marketplace/publish-7.png)