edits: reviewed content and made edits

components/products.tsx

@@ -220,7 +220,7 @@ const items: { [key: string]: Item[] } = {
  title: "Ledger",
  description: <>Get started with the Fetch Ledger.</>,
  icon: ledgerIcon,
- path: "/concepts/ledger/intro",
+ path: "/concepts/fetch-network/ledger/intro",
  },
  ],
 };

pages/concepts.mdx

@@ -140,17 +140,6 @@ import { GuideBox } from "../components/feature-guide-tabs";
  }}
  />
 
- <GuideBox
- content={{
- title: "Block explorers 🔎",
- description: "Explore the block explorers associated with each network.",
- path: "/concepts/fetch-network/ledger/block-explorer"
- }}
- />
-
-</Grid2>
-<Grid2>
-
  <GuideBox
  content={{
  title: "Validators overview",

pages/concepts/fetch-network/ledger/_meta.json

@@ -1,5 +1,4 @@
 {
  "intro": "Introduction \uD83D\uDE80",
- "block-explorer": "Block explorers \uD83D\uDD0E",
  "validators": "Validators"
 }

pages/concepts/fetch-network/ledger/intro.mdx

@@ -4,15 +4,17 @@ import { Callout } from 'nextra/components'
 
 ## Introduction 🚀
 
-The fetchhub mainnet forms the core of the Fetch.ai ecosystem. In these pages, you will find all information to setup your client and connect on the [network ↗️](/concepts/ledger/active-networks) and [CLI introduction ↗️](/guides/ledger/cli/intro) pages.
+The Fetch Ledger is the blockchain network developed by Fetch.ai and which constitutes the underlying infrastructure for various decentralized applications and contracts. It employs a consensus mechanism where [validators ↗️](/concepts/fetch-network/ledger/validators) are responsible for validating transactions and creating new blocks in the blockchain. The ledger utilizes Fetch native cryptocurrency, FET, which is used for various activities within the network, including transaction fees and staking. The ledger also supports features like [multi-signature keys ↗️](/guides/fetch-network/ledger/cli/multisig-keys), allowing users to control [keys ↗️](/guides/fetch-network/ledger/cli/keys) in different configurations.
 
-This documentation covers some of the things you need to know in order to prepare for and develop on this network.
+The fetchhub mainnet forms the core of the Fetch.ai ecosystem. In these pages, you will find all information to setup your client and connect on the [network ↗️](/references/fetch-network/ledger/active-networks).
+
+This documentation covers some of the things you need to know in order to prepare for and develop on the Fetch network.
 
 ## Test networks
 
-The starting point for most will be [our test network ↗️](/concepts/ledger/active-networks#test-nets), since it can provide you with test tokens with no value, that you can safely experiment with.
+The starting point for most is [our test network ↗️](/references/fetch-network/ledger/active-networks#test-nets), since it can provide you with test tokens with no value, that you can safely experiment with through the [faucet ↗️](/guides/fetch-network/ledger/faucet).
 
-Head over the [Command Line client ↗️](/guides/ledger/cli/intro) section for guidance on how to install and configure the `fetchd` client.
+Head over to the [Command Line Interface (CLI) client ↗️](/guides/fetch-network/ledger/cli/intro) section for guidance on how to install and configure the `fetchd` client and perform different operations within the ledger.
 
 <Callout type="warning" emoji="⚠️">
  This documentation is currently under construction, and the content may not be up-to-date.

pages/concepts/fetch-network/ledger/validators.mdx

@@ -28,13 +28,13 @@ In this context, the Fetch.ai Ledger relies on a set of validators that are resp
 
 If validators double sign, are frequently offline or do not participate in governance, their staked FET (including FET of users that delegated to them) can be slashed. The penalty depends on the severity of the violation.
 
-### Testnet vs Mainnet
+### Test network (Testnet) vs Main Network (Mainnet)
 
 We can distinguish between:
 
  - **Testnet**: it is a separate blockchain environment that developers and users can use to test new features or applications without risking real tokens. It allows for experimentation in a controlled environment.
 
- - **Mainnet**: it is the actual production blockchain where real transactions occur with real tokens. It's the live version of the blockchain.
+ - **Mainnet**: it is the actual production blockchain where real transactions occur with real tokens. It is the live version of the blockchain.
 
 By setting up and experimenting on a testnet first, developers can ensure that everything works as intended before deploying it on the mainnet. This helps in avoiding potential issues or vulnerabilities in a live environment.
 

pages/guides.mdx

@@ -395,6 +395,14 @@ import { GuideBox } from "../components/feature-guide-tabs";
 </Grid3>
 <Grid3>
 
+ <GuideBox
+ content={{
+ title: "How to use the block explorer 🔎",
+ description: "Learn how to use the block explorer.",
+ path: "/guides/fetch-network/ledger/block-explorer"
+ }}
+ />
+
  <GuideBox
  content={{
  title: "Setting up a validator node 🌐",
@@ -411,6 +419,9 @@ import { GuideBox } from "../components/feature-guide-tabs";
  }}
  />
 
+</Grid3>
+<Grid3>
+
  <GuideBox
  content={{
  title: "How to use the token faucet",
@@ -419,9 +430,6 @@ import { GuideBox } from "../components/feature-guide-tabs";
  }}
  />
 
-</Grid3>
-<Grid3>
-
  <GuideBox
  content={{
  title: "Governance",
@@ -473,7 +481,7 @@ import { GuideBox } from "../components/feature-guide-tabs";
 
  <GuideBox
  content={{
- title: "CLI - Delegator guide",
+ title: "CLI - Delegation",
  description: "Discover the various staking and delegation operations on the Fetch blockchain using CLI.",
  path: "/guides/fetch-network/ledger/cli/delegator"
  }}

pages/guides/fetch-network/ledger/_meta.json

@@ -2,10 +2,11 @@
  "installation": "Installation \uD83D\uDEE0",
  "snapshots": "How to use chain state snapshots \uD83D\uDCF8",
  "state-sync": "State-sync",
+ "block-explorer": "How to use the block explorer \uD83D\uDD0E",
  "setup-validator-node": "How to set up a validator node \uD83C\uDF10",
  "joining-testnet": "How to join a testnet",
  "single-node-testnet": "How to run a single node network",
  "governance": "Governance",
- "faucet": "How to use the token faucet",
- "cli": "CLI - Command Line client"
+ "faucet": "How to use the token faucet \uD83D\uDCB0",
+ "cli": "CLI - Command Line Interface"
 }

pages/guides/fetch-network/ledger/block-explorer.mdx

@@ -0,0 +1,42 @@
+import { Callout } from 'nextra/components'
+
+# How to use the block explorer 🔎
+
+## Introduction
+
+A block explorer is a web-based tool that offers a visual interface for interacting with a blockchain network. It enables users to view details about individual blocks, explore transactions, check wallet balances and histories, verify transaction statuses, and access network statistics. Additionally, it provides real-time or historical data on network activity and offers insights into smart contract interactions for platforms with this capability. Block explorers are essential for users, developers, and researchers to easily access and comprehend blockchain data, enhancing transparency and accessibility.
+
+Each of the available Fetch [networks ↗️](/references/fetch-network/ledger/active-networks) has a dedicated block explorer website associated with it.
+
+## Logging in with the ledger nano
+
+The Ledger Nano is a hardware wallet designed to provide a secure and convenient way to store and manage cryptocurrencies. It is a physical device, similar in appearance to a USB drive, that is used to securely store the private keys necessary for accessing and managing cryptocurrency holdings. To log in with you ledger nano device:
+
+1. Navigate towards the block explorer landing page.
+2. Click on the key button (🔑) in the top right corner of the block explorer landing page.
+3. At this point, you will be prompted to a _sign in with ledger_ page using either USB or bluetooth connection.
+4. Now, **accept this request on your ledger nano device**.
+5. After completing this process, the key button will be replaced by a person icon with a link to your personal address page, which keeps track of the activity that you have performed on the testnet.
+
+## Getting testnet tokens from the faucet
+
+For networks that support it, you can obtain tokens for your account in the following way:
+
+ 1. Copy your account's address and paste it into the [token faucet ↗️](/guides/fetch-network/ledger/faucet).
+ 2. Then, return to the **main page**, and press the **Get Funds** button.
+ 3. Paste your address in the pop-up window.
+ 4. You can now return to your address page, via the person icon, and should see that you have been allocated **1 TESTFET**.
+
+## Transferring tokens to another address
+
+After receiving tokens, you can send these tokens to another address using the purple **Transfer** button on your address page. This will trigger a pop-up window that prompts you to specify the destination address and the amount of tokens you wish to transfer. After filling in this information, you will be asked to sign the transaction using your ledger nano device. The transaction confirmation gives two links that can be used to check that the transaction has been executed on the blockchain using either the transaction hash or your account page.
+
+<Callout type="info" emoji="ℹ️">
+ The transaction format includes a memo field that can be used to check the transaction information on the ledger nano display.
+</Callout>
+
+## Delegating stake to a validator
+
+Within the block explorer landing page, you can delegate your tokens to a validator which is operating on the network by clicking on the **Validators** tab, and selecting one of the validators that you wish to delegate stake towards. By clicking on a validator name, you will be redirected towards that validator's details.
+
+For more information on how to delegate tokens to validators, visit our [guide ↗️](/guides/fetch-network/ledger/cli/delegator).

pages/guides/fetch-network/ledger/cli/_meta.json

@@ -3,6 +3,6 @@
  "keys": "CLI - Managing keys \uD83D\uDD11",
  "tokens": "CLI - Managing tokens",
  "multisig-keys": "CLI - Multisig keys",
- "delegator": "CLI - Delegator guide",
+ "delegator": "CLI - Delegation",
  "governance-proposals": "Governance proposals \uD83D\uDCDD"
 }