0xPolygon · hsutaiyu · Oct 1, 2024 · Sep 19, 2024 · Sep 27, 2024 · Sep 27, 2024
diff --git a/docs/img/pos/change-owner-1.png b/docs/img/pos/change-owner-1.png
diff --git a/docs/img/pos/change-owner-2.png b/docs/img/pos/change-owner-2.png
diff --git a/docs/img/pos/polygon-instance.png b/docs/img/pos/polygon-instance.png
diff --git a/docs/img/pos/support-portal-1.png b/docs/img/pos/support-portal-1.png
diff --git a/docs/pos/architecture/bor/commands.md b/docs/pos/architecture/bor/commands.md
diff --git a/docs/pos/architecture/bor/index.md → docs/pos/architecture/bor/introduction.md b/docs/pos/architecture/bor/index.md → docs/pos/architecture/bor/introduction.md
diff --git a/docs/pos/architecture/heimdall/index.md → ...pos/architecture/heimdall/introduction.md b/docs/pos/architecture/heimdall/index.md → ...pos/architecture/heimdall/introduction.md
diff --git a/docs/pos/architecture/index.md → docs/pos/architecture/overview.md b/docs/pos/architecture/index.md → docs/pos/architecture/overview.md
@@ -54,7 +54,7 @@ An overview of the process:
 * A selected proposer from the validator set is responsible for collecting all signatures for a particular checkpoint and committing the checkpoint on the Ethereum mainnet.
 * The responsibility of creating blocks and proposing checkpoints is variably dependent on a validator’s stake ratio in the overall pool.
 
-See also [Heimdall architecture](heimdall/index.md).
+See also [Heimdall architecture](../architecture/heimdall/introduction.md).
 <!-- (/docs/pos/design/heimdall/overview). -->
 
 ## Bor: Block production layer
@@ -63,5 +63,5 @@ Bor is Polygon PoS's block producer — the entity responsible for aggregating t
 
 Bor block producers are a subset of the validators and are shuffled periodically by the Heimdall validators.
 
-See also [Bor architecture](bor/index.md).
+See also [Bor architecture](../architecture/bor/introduction.md).
 <!-- (/docs/pos/design/bor/overview). -->
diff --git a/docs/pos/concepts/index.md b/docs/pos/concepts/index.md
diff --git a/docs/pos/concepts/tokens/index.md b/docs/pos/concepts/tokens/index.md
diff --git a/docs/pos/concepts/transactions/index.md b/docs/pos/concepts/transactions/index.md
diff --git a/docs/pos/get-started/becoming-a-validator.md b/docs/pos/get-started/becoming-a-validator.md
@@ -191,12 +191,12 @@ The following step-by-step guides will take you through the process of running a
 
 * [Start and run the nodes with Ansible](../how-to/validator/validator-ansible.md).
 * [Start and run the nodes with binaries](../how-to/validator/validator-binaries.md).
-* [Stake as a validator](../how-to/operate-validator-node/validator-staking-operations.md).
+* [Stake as a validator](../how-to/operate-validator-node/next-steps.md#stake-tokens).
 
 ### Maintain your validator nodes
 
 * [Change the signer address](../how-to/operate-validator-node/change-signer-address.md).
-* [Change the commission](../how-to/operate-validator-node/validator-commission-operations.md).
+* [Change the commission](../how-to/operate-validator-node/next-steps.md#changing-your-commission-rate).
 
 ### Community assistance
 

diff --git a/docs/pos/how-to/choose-node-type.md b/docs/pos/how-to/choose-node-type.md
diff --git a/docs/pos/how-to/erigon-archive-node.md b/docs/pos/how-to/erigon-archive-node.md
@@ -8,9 +8,9 @@ comments: true
 - RAM: 64GB
 - Storage
     - Basically `io1` or above with at least 20k+ iops and RAID-0 based disk structure
-    - Mainnet archive node: 10TB
+    - Mainnet archive node: 15TB
     - Amoy testnet archive node: 1TB
-    - SSD or NVMe. Bear in mind that SSD performance deteriorates when close to capacity
+    - SSD or NVMe. Bear in mind that SSD performance deteriorates when close to capacity.
 - Golang: >= v1.20
 - GCC: >= v10
 
@@ -34,16 +34,16 @@ This should create the binary at `./build/bin/erigon`
 
 ## Start Erigon client
 
-When connecting to Amoy testnet, use the following command to start your Erigon client:
+If you're deploying to mainnet, run the following command:
 
 ```bash
-erigon --chain=amoy
+erigon --chain=bor-mainnet --db.size.limit=12TB --db.pagesize=16KB # remaining flags follow
 ```
 
-If you're deploying to mainnet, run the following command:
+When connecting to Amoy testnet, use the following command to start your Erigon client:
 
 ```bash
-erigon --chain=bor-mainnet --db.size.limit=12TB --db.pagesize=16KB # remaining flags follow
+erigon --chain=amoy
 ```
 
 ## Configure Erigon client
@@ -60,11 +60,11 @@ If you are not using local **heimdall**, use `-bor.heimdall=<your heimdall url>`
 erigon --chain=amoy --bor.heimdall=<your heimdall url> --datadir=<your_data_dir>
 ```
 
-!!! note "Node RPC"
+## Node RPC
 
-    - If you want to connect to Polygon Amoy Testnet, use: [https://heimdall-api-amoy.polygon.technology](https://heimdall-api-amoy.polygon.technology)
+- If you want to connect to PoS Amoy Testnet, use: [https://heimdall-api-amoy.polygon.technology](https://heimdall-api-amoy.polygon.technology)
 
-    - For Polygon mainnet, use: [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)
+- For PoS mainnet, use: [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)
 
 !!! tip 
 

diff --git a/docs/pos/how-to/full-node/full-node-ansible.md b/docs/pos/how-to/full-node/full-node-ansible.md
@@ -2,36 +2,18 @@
 comments: true
 ---
 
-An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) is used to configure and manage a full node. 
+An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playbooks_intro.html) can be used to configure and manage a full node. 
 
 ## Prerequisites
 
 - Install Ansible on your local machine with Python3.x. The setup doesn't run on Python 2.x.
     - To install Ansible with Python 3.x, you can use pip. If you do not have pip on your machine,
       follow the steps outlined [here](https://pip.pypa.io/en/stable/). Run `pip3 install ansible` to install
       Ansible.
-- Check the [Polygon PoS Ansible repository](https://github.com/maticnetwork/node-ansible#requirements) for
-  requirements.
+- Check the [Polygon PoS Ansible repository](https://github.com/maticnetwork/node-ansible#requirements) for requirements.
 - You also need to ensure that Go is *not installed* in your environment. You will run into issues if you attempt to set up your full node through Ansible with Go installed as Ansible requires specific packages of Go.
 - You will also need to make sure that your VM / Machine does not have any previous setups for Polygon Validator or Heimdall or Bor. You will need to delete them as your setup will run into issues.
 
-!!! info "Heimdall source enhancements"
-
-    The latest Heimdall version, **[v1.0.3](https://github.com/maticnetwork/heimdall/releases/tag/v1.0.3)**, contains a few enhancements.
-    The delay time between the contract events of different validators **has been increased** to ensure that the mempool doesn't get filled quickly in case of a burst of events that could hamper the chain's progress.
-
-    Additionally, the data size **has been restricted in state sync txs to 30Kb (when represented in bytes) and 60Kb (when defined as string)**.
-
-    For example:
-
-    ```bash
-    Data - "abcd1234"
-    Length in string format - 8
-    Hex Byte representation - [171 205 18 52]
-    Length in byte format - 4
-    ```
-
-
 ## Full node setup
 
 - Ensure you have access to the remote machine or VM on which the full node is being set up.
@@ -97,10 +79,10 @@ An [Ansible playbook](https://docs.ansible.com/ansible/latest/user_guide/playboo
     - On the remote machine/VM, run `curl localhost:26657/status`
     - In the output, `catching_up` value should be `false`
 
-- Once Heimdall is synced, run
+- Once Heimdall is synced, run:
     - `sudo service bor start`
 
-You have successfully set up a full node with Ansible.
+If you've reached this point, you have successfully set up a full node with Ansible.
 
 !!! note
 
@@ -120,14 +102,8 @@ Logs can be managed by the `journalctl` linux tool. Here is a tutorial for advan
 journalctl -u heimdalld.service -f
 ```
 
-### Check Bor REST-server logs
+### Check Bor node logs
 
 ```bash
 journalctl -u bor.service -f
-```
-
-## Ports and firewall setup
-
-Open ports `22`, `26656` and `30303` to world (0.0.0.0/0) on sentry node firewall.
-
-You can use VPN to restrict access for port 22 as per your requirement and security guidelines.
+```