GITBOOK-31: No subject

developers/ocean-node/README.md

@@ -10,7 +10,7 @@ It integrates multiple services for secure and efficient data operations, utiliz
 
 The node is structured into separate layers, including the network layer for communication, and the components layer for core services like the Indexer and Provider. This layered architecture ensures efficient data management and high security.
 
-Flexibility and extensibility are key features of Ocean Node, allowing multiple compute engines, such as Docker and Kubernetes, to be managed within the same framework. The orchestration layer coordinates interactions between the core node and execution environments, ensuring the smooth operation of compute tasks. 
+Flexibility and extensibility are key features of Ocean Node, allowing multiple compute engines, such as Docker and Kubernetes, to be managed within the same framework. The orchestration layer coordinates interactions between the core node and execution environments, ensuring the smooth operation of compute tasks.
 
 For details on how to run a node see the [readme](https://github.com/oceanprotocol/ocean-node/) in the GitHub repository.
 
@@ -35,11 +35,9 @@ For details on how to run a node see the [readme](https://github.com/oceanprotoc
 **Ocean Nodes replace the Subgraph:**
 
 * Indexing the data from the smart contact events.
-* The data is indexed and updated in real-time. 
+* The data is indexed and updated in real-time.
 * Providing an API which receives and responds to queries.
-* Simplifying the development experience for anyone building on Ocean. 
+* Simplifying the development experience for anyone building on Ocean.
-
-
 
 ### API
 
@@ -47,13 +45,11 @@ For details on all of the HTTP endpoints exposed by the Ocean Nodes API, refer t
 
 {% embed url="https://github.com/oceanprotocol/ocean-node/blob/develop/API.md" %}
 
-###  Compute to Data (C2D)
+### Compute to Data (C2D)
-
-The Ocean nodes provide a convenient and easy way to run a compute-to-data environment. This gives you the opportunity to monetize your node as you can charge fees for using the C2D environment and there are also additional incentives provided Ocean Protocol Foundation (OPF). Soon we will also be releasing C2D V2 which will provide different environments and new ways to pay for computation. 
-
 
+The Ocean nodes provide a convenient and easy way to run a compute-to-data environment. This gives you the opportunity to monetize your node as you can charge fees for using the C2D environment and there are also additional incentives provided Ocean Protocol Foundation (OPF). Soon we will also be releasing C2D V2 which will provide different environments and new ways to pay for computation.
 
 For more details on the C2D V2 architecture, refer to the documentation in the repository:\
- 
+
 
 {% embed url="https://github.com/oceanprotocol/ocean-node/blob/develop/docs/C2DV2.md" %}

developers/ocean-node/node-architecture.md

@@ -1,8 +1,8 @@
 # Node Architecture
 
-Ocean Nodes are the core infrastructure component within the Ocean Protocol ecosystem, designed to facilitate decentralized data exchange and management. It operates by leveraging a multi-layered architecture that includes network, components, and module layers. 
+Ocean Nodes are the core infrastructure component within the Ocean Protocol ecosystem, designed to facilitate decentralized data exchange and management. It operates by leveraging a multi-layered architecture that includes network, components, and module layers.
 
-Key features include secure peer-to-peer communication via libp2p, flexible and secure encryption solutions, and support for various Compute-to-Data (C2D) operations. 
+Key features include secure peer-to-peer communication via libp2p, flexible and secure encryption solutions, and support for various Compute-to-Data (C2D) operations.
 
 Ocean Node's modular design allows for customization and scalability, enabling seamless integration of its core services—such as the Indexer for metadata management and the Provider for secure data transactions—ensuring robust and efficient decentralized data operations.
 
@@ -14,7 +14,7 @@ The Node stack is divided into the following layers:
 * Components layer (Indexer, Provider)
 * Modules layer
 
-<figure><img src="../../.gitbook/assets/image (1).png" alt=""><figcaption><p>Ocean Nodes Infrastructure diagram</p></figcaption></figure>
+<figure><picture><source srcset="../../.gitbook/assets/OceanNode-arhitecture.drawio.png" media="(prefers-color-scheme: dark)"><img src="../../.gitbook/assets/OceanNode-arhitecture.drawio (light).png" alt=""></picture><figcaption><p>Ocean Nodes Infrastructure diagram</p></figcaption></figure>
 
 ### Features
 
@@ -66,11 +66,11 @@ Features:
 * Decrypts the URL when the dataset is downloaded or a compute job is started.
 * Encrypts/decrypts files before storage/while accessing.
 * Provides access to data assets by streaming data (and never the URL).
-* Provides compute services.&#x20;
+* Provides compute services.
 * The node operator can charge provider fees, compensating the individuals or organizations operating their own node when users request assets.
 * Currently, we are providing the legacy Ocean C2D compute services (which run in Kubernetes) via the node. In the future, we will soon be releasing C2D V2 which will also allow connections to multiple C2D engines: light, Ocean C2D, and third parties.
 
-For more details on the C2D V2 architecture, refer to the documentation in the repository:&#x20;
+For more details on the C2D V2 architecture, refer to the documentation in the repository:
 
 {% embed url="https://github.com/oceanprotocol/ocean-node/blob/develop/docs/C2DV2.md" %}