GITBOOK-351: Updating headings & wordings

Author: aw126

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

@@ -1,6 +1,6 @@
 # Running Nodes
 
-This section explains how to build, run, and maintain Cronos nodes across Mainnet, Testnet, and Devnet. It covers key areas such as compiling `cronosd`, configuring validators and full nodes, managing upgrades, and optimizing synchronization with tools like state sync, snapshots, and VersionDB. The aim is to provide node operators with clear guidance to keep their infrastructure stable and efficient.
+This section explains how to build, run, and maintain Cronos nodes across Mainnet, Testnet, and Devnet. It covers key areas such as compiling `cronosd`, configuring validators and full nodes, managing upgrades, and optimizing synchronization with tools like snapshots, local state sync, VersionDB and MemlAVL. The aim is to provide node operators with clear guidance to keep their infrastructure stable and efficient.
 
 Whether you’re launching a validator, hosting infrastructure, or contributing to the network, this page walks you through everything from initial setup to advanced optimizations.
 

for-node-hosts/running-nodes/cronos-evm-snapshots/quicksync.md

@@ -27,7 +27,9 @@ After executing the command `./cronosd` start at [Step 3-2](../cronos-mainnet/#s
 \
 Both RocksDB and LevelDB snapshots are now available for Cronos Chain.
 
+{% hint style="info" %}
 ### Step 2: Quicksync Extract
+{% endhint %}
 
 To start with Quicksync, you need to run `brew install lz4` to install lz4 in a new terminal.\
 Then download the file with preferred pruning settings directly from [Quicksync](https://quicksync.io/cronos).

for-node-hosts/running-nodes/cronos-evm-snapshots/state-sync.md

@@ -26,7 +26,7 @@ IMPORTANT
 State-sync depends on the ability to pull a snapshot from its persistent-peers, so there is some amount of timing and luck involved with this method. Although it is the fastest way, it is not always going to work, in case state-sync is not syncing, we recommend using [quicksync](quicksync.md), although it takes a longer time to download the snapshot, this method is more guaranteed to work.
 {% endhint %}
 
-#### Step 1: Get the latest cronosd binary
+### Step 1: Get the latest cronosd binary
 
 {% hint style="info" %}
 The latest Cronosd [version](https://github.com/crypto-org-chain/cronos/releases) release is `cronosd v1.4.5`
@@ -45,7 +45,7 @@ The latest Cronosd [version](https://github.com/crypto-org-chain/cronos/releases
 1.4.5
 ```
 
-#### Step 2: Configure cronosd
+### Step 2: Configure cronosd
 
 * Initialize **cronosd.** Replace the **\[moniker]** with an ID for your node.  
 
@@ -81,7 +81,7 @@ s|^(persistent_peers[[:space:]]+=[[:space:]]+).*$|\1\"0d5cf1394a1cfde28dc8f02356
 s|^(seeds[[:space:]]+=[[:space:]]+).*$|\1\"\"|" ~/.cronos/config/config.toml
 ```
 
-#### Step 3: Run everything
+### Step 3: Run everything
 
 * Now that `cronosd` has been configured, we are ready to start the node: