diff --git a/developers/barge/local-setup-ganache.md b/developers/barge/local-setup-ganache.md
index feb138ad..75a13945 100644
--- a/developers/barge/local-setup-ganache.md
+++ b/developers/barge/local-setup-ganache.md
@@ -8,7 +8,7 @@ description: 🧑🏽💻 Your Local Development Environment for Ocean Protoc
Barge offers several functionalities that enable developers to create and test the Ocean Protocol infrastructure efficiently. Here are its key components:
-
Functionality
Description
Aquarius
A metadata storage and retrieval service for Ocean Protocol. Allows indexing and querying of metadata.
Provider
A service that facilitates interaction between users and the Ocean Protocol network.
Ganache
A local Ethereum blockchain network for testing and development purposes.
TheGraph
A decentralized indexing and querying protocol used for building subgraphs in Ocean Protocol.
ocean-contracts
Smart contracts repository for Ocean Protocol. Deploys and manages the necessary contracts for local development.
Customization and Options
Barge provides various options to customize component versions, log levels, and enable/disable specific blocks.
+
Functionality
Description
Aquarius
A metadata storage and retrieval service for Ocean Protocol. Allows indexing and querying of metadata.
Provider
A service that facilitates interaction between users and the Ocean Protocol network.
Ganache
A local Ethereum blockchain network for testing and development purposes.
TheGraph
A decentralized indexing and querying protocol used for building subgraphs in Ocean Protocol.
ocean-contracts
Smart contracts repository for Ocean Protocol. Deploys and manages the necessary contracts for local development.
Customization and Options
Barge provides various options to customize component versions, log levels, and enable/disable specific blocks.
Barge helps developers to get started with Ocean Protocol by providing a local development environment. With its modular and user-friendly design, developers can focus on building and testing their applications without worrying about the intricacies of the underlying infrastructure.
diff --git a/developers/contracts/datanft-and-datatoken.md b/developers/contracts/datanft-and-datatoken.md
index 083d1339..ed0eb505 100644
--- a/developers/contracts/datanft-and-datatoken.md
+++ b/developers/contracts/datanft-and-datatoken.md
@@ -9,7 +9,7 @@ description: >-
-In summary: A [**data NFT**](data-nfts.md) serves as a **representation of the copyright** or exclusive license for a data asset on the blockchain, known as the "[**base IP**](../../discover/glossary.md)". **Datatokens**, on the other hand, function as a crucial mechanism for **decentralized access** to data assets.
+In summary: A [**data NFT**](data-nfts.md) serves as a **representation of the copyright** or exclusive license for a data asset on the blockchain, known as the [**base IP**](../../discover/glossary.md). **Datatokens**, on the other hand, function as a crucial mechanism for **decentralized access** to data assets.
For a specific data NFT, multiple ERC20 datatoken contracts can exist. Here's the main concept: Owning 1.0 datatokens grants you the ability to **consume** the corresponding dataset. Essentially, it acts as a **sub-license** from the [base IP](../../discover/glossary.md), allowing you to utilize the dataset according to the specified license terms (when provided by the publisher). License terms can be established with a "good default" or by the Data NFT owner.