GITBOOK-16: No subject

Author: Bojan Angjelkoski

.gitbook/SUMMARY.md

@@ -92,10 +92,17 @@
 ## Nodes
 
 * [Getting Started](nodes/getting-started/README.md)
+  * [Interact with a node](nodes/getting-started/interact-with-a-node.md)
   * [Running a node](nodes/getting-started/running-a-node/README.md)
     * [Setting up the keyring](nodes/getting-started/running-a-node/1.-setting-up-the-keyring.md)
-  * [Interact with a node](nodes/getting-started/interact-with-a-node.md)
+    * [Join a network](nodes/getting-started/running-a-node/join-a-network.md)
+    * [Upgrade your node](nodes/getting-started/running-a-node/upgrade-your-node.md)
 * [Validators](nodes/validators/README.md)
+  * [Mainnet](nodes/validators/mainnet/README.md)
+    * [Peggo](nodes/validators/mainnet/peggo.md)
+    * [Canonical Chain Upgrades](nodes/validators/mainnet/canonical-chain-upgrades.md)
+  * [Testnet](nodes/validators/testnet/README.md)
+    * [Testnet Peggo](nodes/validators/testnet/testnet-peggo.md)
   * [Cosmosvisor](nodes/validators/cosmosvisor.md)
 * [Public Endpoints](nodes/public-endpoints.md)
 * [Private Nodes](nodes/private-nodes.md)

.gitbook/developers/cosmwasm-developers/README.md

@@ -2,4 +2,4 @@
 
 CosmWasm is a novel smart contracting platform built for the Cosmos ecosystem. You can learn more about CosmWasm [here](https://docs.cosmwasm.com/docs/), or see the [CosmWasm Book](https://book.cosmwasm.com/index.html) for a guide on creating CosmWasm smart contracts.
 
-**Start your builder journey on Injective using Cosmwasm by visiting the** [your-first-smart-contract.md](your-first-smart-contract.md "mention")**pager.** 
+**Start your builder journey on Injective using Cosmwasm here** [your-first-smart-contract.md](your-first-smart-contract.md "mention") 

.gitbook/developers/exchange-developers/provider-oracle.md

@@ -6,17 +6,15 @@ Prerequisite reading [Injective Oracle Module](../modules/injective/oracle/)
 
 The goal of this section is to provide users a guide on how to launch and maintain an oracle provider on Injective. These oracles can be used for various purposes, like Perpetual Markets, Expiry Futures Markets, [Binary Options markets](https://docs.injective.network/develop/modules/injective/exchange/binary\_options\_markets), etc.
 
-First, what is an oracle provider? It's an oracle **TYPE** that allows external parties to relay price feed to the Injective chain. These external parties are called providers. Each external party is identified by a provider and all of the price feeds provided on the chain are stored under that particular provider. This allows custom price feed to be created on Injective which can power creative and advanced markets being launched on Injective.
+First, what is an oracle provider? It's an oracle **TYPE** that allows external parties to relay price feed to the Injective chain. These external parties are called providers. A provider identifies each external party and all of the price feeds provided on the chain are stored under that particular provider. This allows custom price feed to be created on Injective which can power creative and advanced markets being launched on Injective.
 
-The first thing developers need to do is register their provider under the Oracle Provider type. You can do that by submitting a `GrantProviderPrivilegeProposal` governance proposal. Once the proposal passes, your provider will be registered and you'll be able to relay price feeds. You can do it in a CLI environment using `injectived` (`grant-provider-privilege-proposal [providerName] [relayers] --title [title] --description [desc] [flags]`) or using any of our SDKs to create the message and broadcast it to the chain.
+The first thing developers need to do is register their provider under the Oracle Provider type. You can do that by submitting a `GrantProviderPrivilegeProposal` governance proposal. Once the proposal passes, your provider will be registered and you can relay price feeds. You can do it in a CLI environment using `injectived` (`grant-provider-privilege-proposal [providerName] [relayers] --title [title] --description [desc] [flags]`) or using any of our SDKs to create the message and broadcast it to the chain.
 
 {% hint style="info" %}
 You can see an example on how to submit this proposal in the Oracle Module Proposals Section
 {% endhint %}
 
-
-
-_Note: the `relayers` of the `GrantProviderPrivilegeProposal` are addresses which will be whitelisted to submit the price feeds to Injective._
+_Note: the `relayers` of the `GrantProviderPrivilegeProposal` are addresses that will be whitelisted to submit the price feeds to Injective._
 
 Once the proposal passes, the `relayers` can use the `MsgRelayProviderPrices` to submit prices for a base/quote pair within their provider namespace of the Oracle Provider Type oracle on Injective. You can do it in a CLI environment using `injectived` (`relay-provider-prices [providerName] [symbol:prices] [flags]`) or using any of our SDKs to create the message and broadcast it to the chain.
 

.gitbook/nodes/getting-started/running-a-node/README.md

@@ -2,41 +2,25 @@
 
 It is highly recommended that you set up a local private network before joining a public network. This will help you get familiar with the setup process and provide an environment for testing.
 
-**Private Network**
+### **Private Network**
 
 * Join by setting up a standalone network locally
 
-**Public Network**
+### **Public Network**
 
 * Use the network via public endpoints; or
 * Join by running a node
 
-Anyone can set up their node with endpoints to communicate with the Injective blockchain. For convenience, there are also some public endpoints available to querying the chain. These are recommended for development and testing purposes. For maximum control and reliability, running your own node is recommended.
+Anyone can set up their node with endpoints to communicate with the Injective blockchain. For convenience, there are also some public endpoints available to querying the chain. These are recommended for development and testing purposes. For maximum control and reliability, running your node is recommended.
 
-### Preparation For Running a Node
+## Preparation For Running a Node
 
 If you choose to run a node (either to set up a private network or join the public network), you must set up the keyring. You can also choose to install Cosmovisor, which assists with chain upgrades for minimal downtime.
 
-### Interacting With The Node
+## Interacting With The Node
 
-Once the node is up and running, there are a few ways to interact with a node, namely using the gPRC endpoints, REST endpoints, or `injectived` CLI.
+Once the node is up and running, there are a few ways to interact with a node, namely using the gPRC endpoints, REST endpoints, or `injectived` CLI. You can learn more here[#interacting-with-the-node](./#interacting-with-the-node "mention")
 
-### Contents
+## Guides on Running Your Node
 
-**Preparation**
-
-1. **Set Up Keyring**
-2. **Install Cosmosvisor**
-
-**Join a Network**
-
-1. **Set Up a Local Private Network**
-2. **Join via Public Endpoints**
-3. **Run Node and Join Testnet**
-4. **Run Node and Join Mainnet**
-5. **Upgrading Your Node**
-6. **Running a Node for API Traders**
-
-**Interact with a Node**
-
-1. **Interacting With a Node**
+<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="files"></th></tr></thead><tbody><tr><td>Setup Keyring</td><td>Learn how to setup your keyring</td><td><a href="1.-setting-up-the-keyring.md">1.-setting-up-the-keyring.md</a></td><td><a href="../../../.gitbook/assets/user-hero.png">user-hero.png</a></td></tr><tr><td>Join a Network</td><td>Learn how to join a network</td><td><a href="join-a-network.md">join-a-network.md</a></td><td><a href="../../../.gitbook/assets/bridge-hero.png">bridge-hero.png</a></td></tr><tr><td>Upgrade your node</td><td>Learn how to upgrade your node</td><td><a href="upgrade-your-node.md">upgrade-your-node.md</a></td><td><a href="../../../.gitbook/assets/validator-hero.png">validator-hero.png</a></td></tr></tbody></table>