PoS: node how-tos reoerg and revision

- Page restructuring
- Content revision

Author: hsutaiyu

docs/img/pos/change-owner-1.png

@@ -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
 

docs/img/pos/change-owner-2.png

@@ -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 
 

docs/img/pos/polygon-instance.png

@@ -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.
+```

docs/img/pos/support-portal-1.png

@@ -2,7 +2,7 @@
 comments: true
 ---
 
-This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [minimum technical requirements](../validator/validator-system-requirements.md) guide.
+This deployment guide walks you through starting and running a full node through various methods. For the system requirements, see the [minimum technical requirements](../prerequisites.md) guide.
 
 !!! tip "Snapshots"
 
@@ -17,7 +17,7 @@ This deployment guide walks you through starting and running a full node through
 
 !!! warning
 
-    It's crucial to follow the outlined sequence of actions precisely; deviating from it may result in encountering issues.
+    It is essential to follow the outlined sequence of actions precisely, as any deviation may lead to potential issues.
 
 - Prepare the machine.
 - Install Heimdall and Bor binaries on the full node machine.
@@ -29,7 +29,7 @@ This deployment guide walks you through starting and running a full node through
 
 ### Install `build-essential`
 
-This is **required** for your full node. In order to install, run the below command:
+This is *required* for your full node. In order to install, run the below command:
 
 ```bash
 sudo apt-get update
@@ -44,22 +44,7 @@ Both binaries must be installed and run in the correct order to function properl
 
 ### Heimdall
 
-Install the latest version of Heimdall and related services. Make sure you checkout to the correct [release version](https://github.com/maticnetwork/heimdall/releases). Note that the latest version, [Heimdall v1.0.5](https://github.com/maticnetwork/heimdall/releases/tag/v1.0.5), contains enhancements such as:
-
-1. Restricting data size in state sync txs to:
-    * *30Kb* when represented in `bytes`
-    * *60Kb* when represented as `string`
-
-2. Increasing the `delay time` between the contract events of different validators to ensure that the mempool doesn't get filled very quickly in case of a burst of events which can hamper the progress of the chain.
-
-The following example shows how the data size is restricted:
-
-```
-Data - "abcd1234"
-Length in string format - 8
-Hex Byte representation - [171 205 18 52]
-Length in byte format - 4
-```
+Install the latest version of Heimdall and related services. Make sure you checkout to the correct [release version](https://github.com/maticnetwork/heimdall/releases).
 
 To install *Heimdall*, run the following commands:
 
@@ -73,7 +58,7 @@ You can run the above command with following options:
 - `network_type`: `mainnet` and `amoy`
 - `node_type`: `sentry`
 
-That will install the `heimdalld` and `heimdallcli` binaries. Verify the installation by checking the Heimdall version on your machine:
+This will install the `heimdalld` and `heimdallcli` binaries. Verify the installation by checking the Heimdall version on your machine:
 
 ```bash
 heimdalld version --long
@@ -88,9 +73,9 @@ chown heimdall /var/lib/heimdall
 
 ### Configure Heimdall seeds (Amoy)
 
-The Heimdall seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
+The Heimdall and Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
 
-### Bor install
+### Bor
 
 Install the latest version of Bor, based on valid v1.0+ [released version](https://github.com/maticnetwork/bor/releases).
 
@@ -119,7 +104,7 @@ chown bor /var/lib/bor
 
 ### Configure Bor seeds (Amoy)
 
-The Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
+The Heimdall and Bor seeds don't need to be configured manually for Amoy testnet since they've already been included at genesis.
 
 ### Update service config user permission
 
@@ -160,20 +145,8 @@ Logs can be managed by the `journalctl` linux tool. Here is a tutorial for advan
 journalctl -u heimdalld.service -f
 ```
 
-### Check Heimdall REST-server logs
-
-```bash
-journalctl -u heimdalld-rest-server.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.
+```