GitBook: [#34] Re-order step 0 on running nodes and update FAQ

for-dapp-developers/chain-integration/desktop-wallet-integration.md

@@ -11,19 +11,21 @@ Crypto.com DeFi Desktop Wallet supports staking operations, validator selections
 
 The Desktop Wallet currently supports the following networks:
 
-**Mainnet**:
-
+{% tabs %}
+{% tab title="Mainnet" %}
 * Cronos Mainnet Beta;
 * Crypto.org Chain.
+{% endtab %}
 
-**Testnet**:
-
-* Cronos Testnet;
-* Croeseid Testnet;
+{% tab title="Testnet" %}
+* Cronos Testnet
+* Croeseid Testnet
+{% endtab %}
+{% endtabs %}
 
 Integrations with additional chains are planned for the near future.
 
-## Integrating with Desktop Wallet
+## Integrating with the Desktop Wallet
 
 The DApp Browsers in Desktop Wallet works the same way as MetaMask does: it injects the global `ethereum` object into the DApp's `window` object. It has implemented the essential Ethereum Provider API most DApps use, which means that if your DApp can works with MetaMask, it can also work with the Desktop Wallet.
 

for-dapp-developers/chain-integration/web-extension-integration.md

@@ -13,21 +13,23 @@ Crypto.com DeFi Wallet is a non-custodial wallet that gives users full control o
 
 The Crypto.com Wallet Extension currently supports the following networks:
 
-**Mainnet**:
-
-* Cronos Mainnet Beta;
-* Ethereum Mainnet;
-* Crypto.org Chain.
-
-**Testnet**:
-
-* Cronos Testnet;
-* Croeseid Testnet;
-* Ethereum Testnet (Ropsten, Kovan, Ribkeby, Goerli);
+{% tabs %}
+{% tab title="Mainnet" %}
+* Cronos Mainnet Beta
+* Ethereum Mainnet
+* Crypto.org Chain
+{% endtab %}
+
+{% tab title="Testnet" %}
+* Cronos Testnet
+* Croeseid Testnet
+* Ethereum Testnet (Ropsten, Kovan, Ribkeby, Goerli)
+{% endtab %}
+{% endtabs %}
 
 Integrations with additional chains are planned for the near future.
 
-## Integrating with Defi Connect
+## Integrating with De**F**i Connect
 
 Integrate your DApp with Crypto.com | Wallet Extension to provide a seamless and native experience for your end users to sign transactions.
 
@@ -62,7 +64,7 @@ const connector = new window.DeFiConnect.DeFiWeb3Connector({
 ### Usage
 
 {% hint style="info" %}
-Note: `DeFiWeb3Connector` has implement `AbstractConnector` from `web3-react` 
+Note: `DeFiWeb3Connector` has implement `AbstractConnector` from `web3-react`
 {% endhint %}
 
 #### For `web3-react`
@@ -175,10 +177,10 @@ const signedTypedData = await web3.eth.signTypedData(msg)
 
 ## Example Apps
 
-The following git folder will provide you with some basic deficonnect integrations via react and web3modal. 
+The following git folder will provide you with some basic deficonnect integrations via react and web3modal.
 
 {% hint style="info" %}
-Note You need to replace `INFURA_API_KEY` with a key generated at [Infura](https://infura.io/) 
+Note You need to replace `INFURA_API_KEY` with a key generated at [Infura](https://infura.io/)
 {% endhint %}
 
 ### Git clone `deficonnect-examples`

for-dapp-developers/cronos-smart-contract/token-contract-addresses.md

@@ -1,11 +1,7 @@
 # Token Contract Addresses
 
-## Official token contract addresses for Cronos mainnet Beta
-
-
-
 {% tabs %}
-{% tab title="Mainnet" %}
+{% tab title="Cronos Mainnet Beta" %}
 | Token name | Address                                                                                                                               | Decimal |
 | ---------- | ------------------------------------------------------------------------------------------------------------------------------------- | ------- |
 | WCRO       | [0x5C7F8A570d578ED84E63fdFA7b1eE72dEae1AE23](https://cronoscan.com/tokens/0x5C7F8A570d578ED84E63fdFA7b1eE72dEae1AE23/token-transfers) | 18      |

for-dapp-developers/useful-projects-on-cronos/band-protocol.md

@@ -4,9 +4,9 @@
 
 ### Introduction
 
-**Band Protocol** is a secure, blockchain-agnostic decentralized oracle solution ([more detail here](https://docs.bandchain.org)). It features a blockchain of its own (**BandChain**) that does the heavy-lifting job of pulling data from external sources, aggregating all the results, and creating a verifiable proof of data integrity to be used in other blockchain applications — all with a secure crypto-economic which guarantees data availability and correctness.
+Band Protocol is a secure, blockchain-agnostic decentralised oracle solution ([more detail here](https://docs.bandchain.org/)). It features a blockchain of its own (BandChain) that does the heavy lifting of pulling data from external sources, aggregating all the results, and creating a verifiable proof of data integrity to be used in other blockchain applications — all with a secure crypto-economic which guarantees data availability and correctness.
 
-Developers building applications on **Cronos** can now utilize **Band**’s decentralized oracle services. With **Band**’s oracle, they now have access to various cryptocurrency price data to integrate into their applications.
+Developers building applications on Cronos can now utilise Band’s decentralised oracle services. With Band’s oracle, they now have access to various cryptocurrency price data points to integrate into their applications.
 
 ### Currency Pair and Supported Currencies
 
@@ -119,8 +119,8 @@ contract DemoOracleUSD {
 2. Specify `//SPDX-License-Identifier`, or put `// SPDX-License-Identifier: UNLICENSED` if unlicensed, at the first line of the above code;
 3. Compile the contract with compiler version 0.8.13;
 4. Switch to the **DEPLOY & RUN TRANSACTIONS** tab of [Remix](https://remix.ethereum.org/);
-5. Select `Injected Web3` in the **ENVIRONMENT** dropdown in the top left to connect with Metamask;
-   * Make sure that Metamask is connected to the Cronos testnet, you can refer to our [official documentation](../../for-users/metamask.md);
+5. Select `Injected Web3` in the **ENVIRONMENT** dropdown in the top left to connect with MetaMask;
+   * Make sure that MetaMask is connected to the Cronos testnet, you can refer to our [official documentation](../../for-users/metamask.md);
 6. Deploy the contract with the below Cronos testnet Band reference data proxy address;
    * `0xD0b2234eB9431e850a814bCdcBCB18C1093F986B`;
 7. Hooray, you can now fetch the latest supported token prices from Band Protocol!

for-dapp-developers/useful-projects-on-cronos/covalent.md

@@ -102,7 +102,7 @@ The Covalent API supports a broad range of Web3 data use cases including:
 | ![Trading](https://www.covalenthq.com/static/images/partner-docs/trading.png) | ![Predictions](https://www.covalenthq.com/static/images/partner-docs/predictions.png) | ![Governance](https://www.covalenthq.com/static/images/partner-docs/governance.png)        | ![Pricing](https://www.covalenthq.com/static/images/partner-docs/pricing.png) |
 | DEXs & Trading                                                                | Predictive Analytics                                                                  | Governance                                                                                 | Pricing                                                                       |
 
-Check out our collection of ready-to-ship [**Code Templates**](https://github.com/covalenthq/web3-resources?utm\_source=cronos\&utm\_medium=partner-docs) that you can use to build your Web3 data-powered dApps.
+Check out our collection of ready-to-ship [**Code Templates**](https://github.com/covalenthq/web3-resources?utm\_source=cronos\&utm\_medium=partner-docs) that you can use to build your Web3 data-powered DApps.
 
  
 

for-node-hosts/running-nodes/cronos-mainnet/README.md

@@ -35,6 +35,19 @@ canonicalUrl: https://docs.cronos.org/getting-started/cronos-mainnet.html
 
 This is a detailed documentation for setting up a Validator or a full node on Crypto.org Cronos mainnet Beta `cronosmainnet_25-1`.
 
+## Pre-requisites
+
+### Supported OS
+
+We officially support macOS, Windows, and Linux only. Other platforms may work but there is no guarantee. We will extend our support to other operating systems after we have stabilised our current architecture.
+
+### Prepare your machine
+
+* To run Cronos Mainnet Beta nodes, you will need a machine with the following minimum requirements:
+  * 4-core, x86\_64/ARM architecture processor;
+  * 16 GB RAM;
+  * 1 TB of storage space.
+
 ## Step 0 : Notes on "Huygen" Network upgrade
 
 Before we start, please note that there was "_Huygen_" network upgrade at the block height `2,693,800`, which requires the node operator to update their Cronos Mainnet binary `cronosd` from `v0.6.*` to `v0.7.0`.
@@ -49,32 +62,18 @@ For the host who would like to build a Full Node with complete blockchain data f
 
 Users can refer to the [upgrade guide of "Huygen"](huygen.md) for the detailed upgrade steps.
 
-## Pre-requisites
-
-### Supported OS
-
-We officially support macOS, Windows and Linux only. Other platforms may work but there is no guarantee. We will extend our support to other platforms after we have stabilized our current architecture.
-
-### Prepare your machine
-
-* To run Cronos mainnet Beta nodes, you will need a machine with the following minimum requirements:
-  * 4-core, x86\_64/ARM architecture processor;
-  * 16 GB RAM;
-  * 1 TB of storage space.
-
-## Step 1. Get the Cronos mainnet Beta binary
+## Step 1. Get the Cronos Mainnet Beta binary
 
 {% hint style="info" %}
 Remarks:
 
 The following is the minimal setup for a **validator node** / **full node**.
 {% endhint %}
 
-To simplify the following step, we will be using **Linux** (Intel x86) for illustration. Binary for
-
-**Mac** ([Intel x86](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Darwin\_x86\_64.tar.gz) / [M1](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Darwin\_arm64.tar.gz)) and [Windows](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Windows\_x86\_64.zip) are also available.
+To simplify the following step, we will be using **Linux** (Intel x86) for illustration. \
+Binaries for **Mac** ([Intel x86](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Darwin\_x86\_64.tar.gz) / [M1](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Darwin\_arm64.tar.gz)) and [Windows](https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos\_0.6.5\_Windows\_x86\_64.zip) are also available.
 
-*   To install released **Cronos mainnet Beta binaries** from github:
+*   To install released **Cronos Mainnet Beta binaries** from github:
 
     ```bash
     $ curl -LOJ https://github.com/crypto-org-chain/cronos/releases/download/v0.6.5/cronos_0.6.5_Linux_x86_64.tar.gz
@@ -116,7 +115,8 @@ Before kick-starting your node, we will have to configure your node so that it c
 
     This `moniker` will be the displayed id of your node when connected to Cronos Chain network.
 
-    When providing the moniker value, make sure you drop the square brackets since they are not needed.
+    When providing the moniker value, make sure you drop the square brackets since they are not needed.\
+
 
     The example below shows how to initialize a node named `pegasus-node` :
 
@@ -201,7 +201,7 @@ You should obtain an address with `crc` prefix, e.g. `crc10u5mgfflasrfj9s94mt8l9
 
 ### Step 3-2. Run everything
 
-Once the `cronosd` has been configured, we are ready to start the node and sync the blockchain data:
+Once `cronosd` has been configured, we are ready to start the node and sync the blockchain data:
 
 * Start cronosd, e.g.:
 
@@ -362,8 +362,3 @@ Example: Restart `cronosd start` with QuickSync
 ```
 {% endhint %}
 
-***
-
-## Cronos Mainnet Beta explorer: Cronoscan
-
-* You can lookup data within the `cronosmainnet_25-1` network by the [explorer](https://cronoscan.com/);

for-node-hosts/running-nodes/cronos-testnet.md

@@ -33,9 +33,21 @@ canonicalUrl: https://docs.cronos.org/getting-started/cronos-testnet.html
 
 # Cronos Testnet
 
-## Cronos Testnet: Running Nodes
+### Pre-requisites
+
+#### Supported OS
+
+We officially support macOS, Windows, and Linux only. Other platforms may work but there is no guarantee. We will extend our support to other operating systems after we have stabilised our current architecture.
+
+#### Prepare your machine
+
+To run Cronos Testnet nodes, you will need a machine with the following minimum requirements:
+
+* 4-core, x86\_64/ARM architecture processor;
+* 16 GB RAM;
+* 1 TB of storage space.
 
-The latest Crypto.org EVM Chain Testnet has been named as **Cronos**.
+### Step 0 : Notes on "Huygen" Network upgrade
 
 This is a detailed documentation for setting up a Validator or a full node on Crypto.org Cronos testnet `cronostestnet_338-3`.
 
@@ -62,22 +74,7 @@ Before we start, please note that there are 3 binary upgrade along with the test
    * After it reaches the block height `2483600`, update the binary to [cronos\_0.7.0-rc3-testnet](https://github.com/crypto-org-chain/cronos/releases/tag/v0.7.0-rc3);
    * Start the node again
 
-##
-
-### Pre-requisites
-
-#### Supported OS
-
-We officially support macOS, Windows and Linux only. Other platforms may work but there is no guarantee. We will extend our support to other platforms after we have stabilized our current architecture.
-
-#### Prepare your machine
-
-* To run Cronos testnet nodes, you will need a machine with the following minimum requirements:
-  * 4-core, x86\_64/ARM architecture processor;
-  * 16 GB RAM;
-  * 1 TB of storage space.
-
-### Step 1. Get the Cronos testnet binary
+### Step 1. Get the Cronos Testnet binary
 
 {% hint style="info" %}
 Remarks: The following is the minimal setup for a **full node**.
@@ -94,7 +91,7 @@ To simplify the following step, we will be using **Linux** (Intel x86) for illus
     $ tar -zxvf cronos_0.6.0-testnet_Linux_x86_64.tar.gz
     ```
 
-    Afterward, you can check the version of `cronosd` by
+    Afterwards, you can check the version of `cronosd` by
 
     ```bash
     $ ./cronosd version
@@ -110,14 +107,13 @@ To simplify the following step, we will be using **Linux** (Intel x86) for illus
     ```bash
     $ ./cronosd unsafe-reset-all
     ```
-
-    and remove the old genesis file by
+*   Remove the old genesis file:
 
     ```bash
     $ rm ~/.cronos/config/genesis.json
     ```
 
-Before kick-starting your node, we will have to configure your node so that it connects to the Cronos testnet:
+Before kick-starting your node, we will have to configure your node so that it connects to the Cronos Testnet:
 
 #### Step 2-1 Initialize `cronosd`
 
@@ -191,7 +187,7 @@ CAUTION: This page only shows the minimal setup for validator / full node.
 Furthermore, you may want to run full nodes as sentries (see [Tendermint](https://docs.tendermint.com/master/tendermint-core/running-in-production.html)), restrict your validator connections to only connect to your full nodes, test secure storage of validator keys etc.
 {% endhint %}
 
-Once the `cronosd` has been configured, we are ready to start the node and sync the blockchain data:
+Once `cronosd` has been configured, we are ready to start the node and sync the blockchain data.
 
 * Start cronosd, e.g.:
 
@@ -269,10 +265,11 @@ It should begin fetching blocks from the other peers. Please wait until it is fu
     $ ./cronosd status 2>&1 | jq '.SyncInfo.latest_block_height'
     ```
 
-### Cronos testnet faucet and explorer
+### Cronos Testnet Faucet
 
-* You can lookup data within the `cronostestnet_338-3` network by the [explorer](https://testnet.cronoscan.com);
 * To interact with the blockchain, simply use the [test-token faucet](https://cronos.org/faucet) to obtain test CRO tokens for performing transactions on the **Cronos** testnet.
-  * Users can use the [faucet](https://cronos.org/faucet) to obtain test tokens, please note that you would need a Ethereum type address `0x...` that can be obtained by [Using metamask](../../for-users/metamask.md#using-metamask-on-cronos-testnet).
+* Users can use the [faucet](https://cronos.org/faucet) to obtain test tokens, please note that you would need a Ethereum type address `0x...` that can be obtained by [Using metamask](../../for-users/metamask.md#using-metamask-on-cronos-testnet).
 
+{% hint style="info" %}
 In case you have reached the daily limit on faucet , you can simply send a message on [Discord](https://discord.gg/pahqHz26q4) #request-tcro channel , stating who you are and your `0x...` address.
+{% endhint %}