update PoS - fixed links

EmpieichO · EmpieichO · commit 6ebf49b87ba5 · 2023-12-15T18:16:03.000+02:00
diff --git a/docs/pos/how-to/operating/validator-node/index.md b/docs/pos/how-to/operating/validator-node/index.md
@@ -1,5 +1,3 @@
-# Operating a Polygon Validator Node
-
 Operating as a validator on the Polygon Network involves playing a pivotal role in validating transactions within the blockchain. This guide provides details on how to run a Validator Node (including Sentry and Validator components) on the Polygon Network, the responsibilities involved, and the technical and operational aspects to consider.
 
 ## Eligibility and responsibilities
diff --git a/docs/pos/how-to/operating/validator-node/rewards.md b/docs/pos/how-to/operating/validator-node/rewards.md
@@ -1,18 +1,3 @@
----
-id: rewards
-title: Rewards
-sidebar_label: Rewards
-description: Learn about the Polygon Network staking incentives.
-keywords:
-  - docs
-  - matic
-  - polygon
-  - rewards
-  - staking
-  - incentives
-image: https://wiki.polygon.technology/img/polygon-logo.png
----
-
 In Polygon, validators stake their MATIC tokens as collateral to work for the security of the network, and in exchange for their service, earn rewards.
 
 To leverage Polygon's economics, you should either become a validator or a delegator.
diff --git a/docs/pos/reference/commands.md b/docs/pos/reference/commands.md
@@ -1,17 +1,7 @@
 This guide provides a curated list of common commands and Polygon-specific operations essential for node operators. Whether you're setting up a full node, validator node or troubleshooting, these commands will assist you in managing your Polygon PoS environment effectively.
 
-## Frequently Used Commands for Bor & Heimdall
-
-Use the tabs below to switch between commands for Bor and Heimdall:
-
-<Tabs
-  defaultValue="bor"
-  values={[
-    { label: 'Bor Commands', value: 'bor', },
-    { label: 'Heimdall Commands', value: 'heimdall', },
-  ]
-}>
-<TabItem value="bor">
+## Frequently used commands for Bor & Heimdall
+### Bor
 
 To execute Bor IPC commands, use the following syntax:
 
@@ -32,8 +22,7 @@ bor attach .bor/data/bor.ipc <command>
 | `eth.getBlock("latest").number` | `curl http://YourIP:8545 -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0", "id":1, "method":"bor_getSigners", "params":["0x98b3ea"]}'` | Queries the height of the latest Bor block. |
 |  | `curl http://YourIP:8545 -X POST -H "Content-Type: application/json" --data '{"method":"eth_chainId","params":[],"id":1,"jsonrpc":"2.0"}'` | Retrieves the `chainID`. |
 
-</TabItem>
-<TabItem value="heimdall">
+### Heimdall
 
 | Command | Description |
 | ------- | ----------- |
@@ -45,10 +34,8 @@ bor attach .bor/data/bor.ipc <command>
 | `heimdalld unsafe-reset-all` | Resets the database in case of issues. |
 | `curl localhost:26657/status` | Provides comprehensive information about Heimdall. |
 
-</TabItem>
-</Tabs>
 
-## Node Management Commands
+## Node management commands
 
 | Description                           | Command                                        |
 | ------------------------------------- | ---------------------------------------------- |
@@ -67,33 +54,33 @@ bor attach .bor/data/bor.ipc <command>
 | **Check Heimdall bridge logs**        | `tail -f heimdalld-bridge.log`                 |
 | **Check Bor logs**                    | `tail -f bor.log`                              |
 
-## Useful Configuration Commands
+## Useful configuration commands
 
-### Sync Status of Heimdall
+### Sync status of Heimdall
 
 To check if Heimdall is synced, run:
 
 ```bash
 curl http://localhost:26657/status
 ```
 
-### Latest Block Height on Heimdall
+### Latest block height on Heimdall
 
 To check the latest block height on Heimdall, run:
 
 ```bash
 curl localhost:26657/status
 ```
 
-### Latest Block Height on Bor
+### Latest block height on Bor
 
 To check the latest block height on Bor, use:
 
 ```bash
 curl http://<your ip>:8545 -X POST -H "Content-Type: application/json" -d '{"jsonrpc":"2.0", "id":1, "method":"bor_getSigners", "params":["0x98b3ea"]}'
 ```
 
-### Cleanup: Deleting Remnants of Heimdall and Bor
+### Cleanup: deleting remnants of Heimdall and Bor
 
 **For Linux package:**
 
@@ -109,7 +96,7 @@ sudo rm -rf /etc/bor
 sudo rm /etc/heimdall
 ```
 
-### Terminate Bor Process
+### Terminate Bor process
 
 **For Linux:**
 
@@ -125,7 +112,7 @@ cd CS-2003/bor
 bash stop.sh
 ```
 
-### Retrieve Latest Peer Details
+### Retrieve latest peer details
 
 To retrieve the latest peer details, run:
 
@@ -137,7 +124,7 @@ admin.peers.forEach(function(value){
 exit
 ```
 
-### Stop Heimdall and Bor Services
+### Stop Heimdall and Bor services
 
 **For Linux packages:**
 
@@ -146,7 +133,7 @@ sudo service heimdalld stop
 sudo service bor stop
 ```
 
-**For Binaries:**
+**For binaries:**
 
 ```bash
 pkill heimdalld
@@ -155,7 +142,7 @@ cd CS-2001/bor
 bash stop.sh
 ```
 
-### Remove Heimdall and Bor Directories
+### Remove Heimdall and Bor directories
 
 **For Linux packages:**
 
@@ -164,7 +151,7 @@ sudo rm -rf /etc/heimdall/*
 sudo rm -rf /etc/bor/*
 ```
 
-**For Binaries:**
+**For binaries:**
 
 ```bash
 sudo rm -rf /var/lib/heimdalld/
diff --git a/docs/pos/reference/contracts/delegation.md b/docs/pos/reference/contracts/delegation.md
@@ -10,7 +10,7 @@ When a validator gets rewarded with more `MATIC` tokens, new tokens are added to
 
 `VATIC`: Validator specific minted validator share tokens (ERC20 tokens)
 
-## Technical Specification
+## Technical specification
 
 ```solidity
 uint256 public validatorId; // Delegation contract for validator
@@ -29,7 +29,7 @@ Exchange rate is calculated as below:
 ExchangeRate = (totalDelegatedPower + delegatorRewardPool) / totalDelegatorShares
 ```
 
-## Methods and Variables
+## Methods and variables
 
 ### buyVoucher
 
diff --git a/docs/pos/reference/contracts/genesis-contracts.md b/docs/pos/reference/contracts/genesis-contracts.md
@@ -1,15 +1,8 @@
 Here you will find a list of contracts deployed on Polygon together with their initial address, that is, their location on the blockchain. 
 
-<Tabs
-  defaultValue="mainnet"
-  values={[
-    { label: 'Polygon-Mainnet', value: 'mainnet', },
-    { label: 'Mumbai-Testnet', value: 'mumbai', },
-  ]
-}>
-<TabItem value="mumbai">
+### Mumbai
 
-Parent Chain: Goerli
+Parent chain: Goerli
 
 | Contracts             | Address                                                                                                                      |
 |-----------------------|------------------------------------------------------------------------------------------------------------------------------|
@@ -49,11 +42,9 @@ Parent Chain: Goerli
 |-----------------------|--------------------------------------------|
 | ChildChain            | [0x1EDd419627Ef40736ec4f8ceffdE671a30803c5e](https://mumbai.polygonscan.com/address/0x1EDd419627Ef40736ec4f8ceffdE671a30803c5e/) |
 
-</TabItem>
-
-<TabItem value="mainnet">
+### Mainnet
 
-Parent Chain: Ethereum Mainnet
+Parent chain: Ethereum mainnet
 
 | Contracts             | [Address](https://etherscan.io/address/Address)                                                                       |
 |-----------------------|-----------------------------------------------------------------------------------------------------------------------|
@@ -88,7 +79,7 @@ Parent Chain: Ethereum Mainnet
 | ERC721Predicate       | [0x54150f44c785d412ec262fe895cc3b689c72f49b](https://etherscan.io/address/0x54150f44c785d412ec262fe895cc3b689c72f49b) |
 
 
-**Child Chain: Polygon Mainnet**
+**Child chain: Polygon mainnet**
 
 | Contracts             | Address                                    |
 |-----------------------|--------------------------------------------|
diff --git a/docs/pos/reference/contracts/stakingmanager.md b/docs/pos/reference/contracts/stakingmanager.md
@@ -9,7 +9,7 @@ For the Polygon's Proof of Security based consensus, all the ⅔+1 proof verific
     From one Ethereum address, a **Staker can only be a validator or delegator** (it's just a design choice, no hard reasons).
 
 
-## Validator Admissions / Replacement
+## Validator admissions / replacement
 
 ### Admissions
 At present, there are no open validator slots available on Polygon PoS. There is also a waitlist to become a validator. In the future, if slots become available, validators may apply to be considered and removed off of the waitlist.
@@ -23,7 +23,7 @@ PIP4 introduced the concept of showcasing validator performance for community vi
     Currently, [<ins>Phase 2 of PART C in PIP4</ins>](https://forum.polygon.technology/t/pip-4-validator-performance-management/9956/24) is being implemented. This is where the community decides on validator prospect evaluation criteria. In time, this exercise will produce an application and admissions process.
 
 
-## Methods and Variables
+## Methods and variables
 
 !!!caution
     Slashing Implementation
@@ -182,7 +182,7 @@ function checkSignatures(
 
 Checks if a given validator is active validator for the current epoch.
 
-## Timeline Data Structure
+## Timeline data structure
 
 ```solidity
 struct State {
diff --git a/docs/pos/reference/errors.md b/docs/pos/reference/errors.md
@@ -1,6 +1,6 @@
 This guide aims to provide solutions for common errors you might encounter while interacting with Polygon PoS. If you come across an error that is not listed here, please consult Polygon Support or community forums for additional help.
 
-## Table of Node Errors
+## Table of node errors
 
 | Error                                         | Component  | Description                                                      | Cause                                           | Solution                                                                                     |
 |-----------------------------------------------|------------|------------------------------------------------------------------|--------------------------------------------------|----------------------------------------------------------------------------------------------|
diff --git a/docs/pos/reference/mapped-tokens.md b/docs/pos/reference/mapped-tokens.md
@@ -6,14 +6,7 @@
     If you want to get your token mapped then please send your mapping request via [<ins>mapper.polygon.technology</ins>](https://mapper.polygon.technology/).
 
 
-<Tabs
-defaultValue="mainnet"
-values={[
-{ label: 'PoS mainnet', value: 'mainnet', },
-{ label: 'Mumbai testnet', value: 'mumbai', },
-]
-}>
-<TabItem value="mumbai">
+### Mumbai
 
 | Token Name        | Bridge | Parent Chain Address: Goerli                                                                                                 | Child Chain: MUMBAI                                                                                                                  |
 | ----------------- | ------ | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ |
@@ -22,10 +15,10 @@ values={[
 | DummyERC721Token  | PoS    | [0x084297B12F204Adb74c689be08302FA3f12dB8A7](https://goerli.etherscan.io/address/0x084297B12F204Adb74c689be08302FA3f12dB8A7) | [0x757b1BD7C12B81b52650463e7753d7f5D0565C0e](https://mumbai.polygonscan.com/address/0x757b1BD7C12B81b52650463e7753d7f5D0565C0e) |
 | DummyERC1155Token | PoS    | [0x2e3Ef7931F2d0e4a7da3dea950FF3F19269d9063](https://goerli.etherscan.io/address/0x2e3Ef7931F2d0e4a7da3dea950FF3F19269d9063) | [0xA07e45A987F19E25176c877d98388878622623FA](https://mumbai.polygonscan.com/address/0xA07e45A987F19E25176c877d98388878622623FA) |
 
-</TabItem>
-<TabItem value="mainnet">
+### Mainnet
+
+| Token name        | Bridge | Parent chain address: Ethereum mainnet                                                                                | Child chain: Polygon network                                                                                                      |
 
-| Token Name        | Bridge | Parent Chain Address: Ethereum Mainnet                                                                                | Child Chain: Polygon Network                                                                                                      |
 | ----------------- | ------ | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------- |
 | PoS\-WETH         | PoS    | [0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE](https://etherscan.io/address/0xEeeeeEeeeEeEeeEeEeEeeEEEeeeeEeeeeeeeEEeE) | [0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619](https://polygonscan.com/address/0x7ceB23fD6bC0adD59E62ac25578270cFf1b9f619) |
 | PoS\-USDC         | PoS    | [0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48](https://etherscan.io/address/0xa0b86991c6218b36c1d19d4a2e9eb0ce3606eb48) | [0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174](https://polygonscan.com/address/0x2791Bca1f2de4661ED88A30C99A7a9449Aa84174) |
@@ -46,5 +39,3 @@ values={[
 | DummyERC1155Token | PoS    | [0x556f501CF8a43216Df5bc9cC57Eb04D4FFAA9e6D](https://etherscan.io/address/0x556f501CF8a43216Df5bc9cC57Eb04D4FFAA9e6D) | [0xA0c68C638235ee32657e8f720a23ceC1bFc77C77](https://polygonscan.com/address/0xA0c68C638235ee32657e8f720a23ceC1bFc77C77) |
 | WDEV | PoS    | [0x4a5df63b0c37b38515e4ee51baf40edd420bf7d5](https://etherscan.io/address/0x4a5df63b0c37b38515e4ee51baf40edd420bf7d5) | [0xa5577d1cec2583058a6bd6d5deac44797c205701](https://polygonscan.com/address/0xa5577d1cec2583058a6bd6d5deac44797c205701) |
 
-</TabItem>
-</Tabs>
diff --git a/docs/pos/reference/port-management.md b/docs/pos/reference/port-management.md
@@ -1,6 +1,6 @@
 This guide provides a detailed list of default ports used across Polygon nodes, including Bor and Heimdall. Understanding these ports is crucial for network configuration and effective communication between nodes.
 
-## Bor Node
+## Bor node
 
 | Name                    | Port  | Tags                      | Description                                                                                                    |
 |-------------------------|-------|---------------------------|----------------------------------------------------------------------------------------------------------------|
@@ -13,7 +13,7 @@ This guide provides a detailed list of default ports used across Polygon nodes,
 | Pprof Server            | 7071  | Internal, Monitoring      | Pprof server for collecting Bor metrics.                                                                        |
 | UDP Discovery           | 30301 | Can be Public, Internal   | Default port for Bootnode peer discovery.                                                                       |
 
-## Heimdall Node
+## Heimdall node
 
 | Name                    | Port  | Tags                      | Description                                                                                                    |
 |-------------------------|-------|---------------------------|----------------------------------------------------------------------------------------------------------------|
diff --git a/docs/pos/reference/rpc-endpoints.md b/docs/pos/reference/rpc-endpoints.md
diff --git a/docs/pos/reference/snapshot-instructions-heimdall-bor.md b/docs/pos/reference/snapshot-instructions-heimdall-bor.md

Original file line number	Diff line number	Diff line change
`@@ -1,5 +1,3 @@`
`1`		`-# Operating a Polygon Validator Node`
`2`		`-`
`3`	`1`	`Operating as a validator on the Polygon Network involves playing a pivotal role in validating transactions within the blockchain. This guide provides details on how to run a Validator Node (including Sentry and Validator components) on the Polygon Network, the responsibilities involved, and the technical and operational aspects to consider.`
`4`	`2`
`5`	`3`	`## Eligibility and responsibilities`