PoS: update mumbai/goerli to amoy/sepolia

Author: hsutaiyu

docs/pos/get-started/building-on-polygon.md

@@ -4,9 +4,9 @@ comments: true
 
 Ethereum developers are by default Polygon developers. Welcome. Simply switch to the [Polygon RPC](https://polygon-rpc.com/) and get started. All familiar tools used on Ethereum are supported on Polygon. Whether it is Truffle, Remix or Web3.js, Polygon offers the same UX as Ethereum.
 
-Connect your wallet and deploy any decentralized application to either Polygon Mainnet or Polygon Mumbai Testnet.
+Connect your wallet and deploy any decentralized application to either PoS mainnet or Amoy testnet.
 
-Polygon Mumbai Testnet connects to Ethereum Goërli Testnet, which acts as its ParentChain, a testnet layer 1 (L1).
+Polygon Amoy testnet connects to Ethereum Sepolia testnet, which acts as its parent chain, a testnet layer 1 (L1).
 
 Find all the network-related details in the [network documentation](../reference/rpc-endpoints.md).
 
@@ -74,7 +74,7 @@ const { Alchemy, Network } = require("alchemy-sdk");
 
 const settings = {
   apiKey: "demo", // Can replace with your API Key from https://www.alchemy.com
-  network: Network.MATIC_MAINNET, // Can replace with MATIC_MUMBAI
+  network: Network.MATIC_MAINNET, // Can replace with MATIC_AMOY for testnet config
 };
 
 const alchemy = new Alchemy(settings);

docs/pos/governance/governance-fundamentals.md

@@ -49,7 +49,7 @@ Assuming that the change or upgrade agreed upon via community consensus requires
 1. The protocol decision is made on a PPGC, and implementation begins in the form of modifications to the relevant GitHub repositories.
 2. Core developers create pull requests containing the changes, which can then be merged into the respective code base, and a new [tag](https://github.com/maticnetwork/bor/tags) is created.
 3. Core developers test new releases by deploying them on local devnets. If everything continues to function normally, the tag is marked as "**beta**", which is essentially the "**pre-release**" state.
-4. The modifications and upgrades are rolled out to the Mumbai testnet, and left out to soak for at least one week. Currently, the [Mumbai Testing Committee](https://forum.polygon.technology/t/introducing-mumbai-testing-committee/12970) reports on the stability of the release in the PPGC.
+4. The modifications and upgrades are rolled out to the Amoy testnet, and left out to soak for at least one week. Currently, the [Mumbai Testing Committee](https://forum.polygon.technology/t/introducing-mumbai-testing-committee/12970) reports on the stability of the release in the PPGC.
 5. Finally, once confirmed that the upgrade doesn't break anything, it is scheduled to be released to mainnet on a PPGC. At this point, the tag version is marked as "**final**".
 6. Validators upgrade their nodes to the latest version after considering the changes. The upgrade is now made canonical via on-chain consensus of the validating stake, including that delegated by token holders. 
 

docs/pos/how-to/snapshots.md

@@ -16,9 +16,9 @@ When setting up a new sentry, validator, or full node server, it is recommended
 ## Client snapshots
 
 To begin, ensure that your node environment meets the **prerequisites** outlined [here](../how-to/full-node/full-node-binaries.md). Before starting any services, execute the shell script provided below. This script will download and extract the snapshot data, which allows for faster bootstrapping. In our example, we will be using an Ubuntu Linux m5d.4xlarge machine with an 8TB block device attached.
-To transfer the correct chaindata to your disk, follow these steps:
+To transfer the correct chain data to your disk, follow these steps:
 
-- All one has to do is specify the network ("mainnet" or "mumbai") and client type ("heimdall" or "bor" or "erigon") of your desired snapshot and run the following command:
+- All one has to do is specify the network ("mainnet" or "amoy") and client type ("heimdall" or "bor" or "erigon") of your desired snapshot and run the following command:
 
 ```bash
 curl -L https://snapshot-download.polygon.technology/snapdown.sh | bash -s -- --network {{ network }} --client {{ client }} --extract-dir {{ extract_dir }} --validate-checksum {{ true / false }}
@@ -43,8 +43,8 @@ curl -L https://snapshot-download.polygon.technology/snapdown.sh | bash -s -- --
   #!/bin/bash
 
   function validate_network() {
-    if [[ "$1" != "mainnet" && "$1" != "mumbai" ]]; then
-      echo "Invalid network input. Please enter 'mainnet' or 'mumbai'."
+    if [[ "$1" != "mainnet" && "$1" != "amoy" ]]; then
+      echo "Invalid network input. Please enter 'mainnet' or 'amoy'."
       exit 1
     fi
   }
@@ -99,7 +99,7 @@ curl -L https://snapshot-download.polygon.technology/snapdown.sh | bash -s -- --
   done
 
   # Set default values if not provided through command-line arguments
-  network=${network:-mumbai}
+  network=${network:-amoy}
   client=${client:-heimdall}
   extract_dir=${extract_dir:-"${client}_extract"}
   checksum=${checksum:-false}
@@ -214,7 +214,7 @@ sudo service bor start
 
 ## Recommended disk size guidance
 
-**Polygon Mumbai Testnet**
+**Polygon Amoy testnet**
 
 | Metric | Calculation Breakdown | Value |
 | ------ | --------------------- | ----------- |
@@ -223,7 +223,7 @@ sudo service bor start
 | approx. total extracted size | 350 GB (bor) + 50 GB (heimdall) | 400 GB |
 | suggested disk size (2.5x buffer) | 400 GB * 2.5 (natural chain growth) | 1 TB | 
 
-**Polygon Mainnet**
+**Polygon mainnet**
 
 | Metric | Calculation Breakdown | Value |
 | ------ | --------------------- | ----------- |
@@ -232,7 +232,7 @@ sudo service bor start
 | approx. total extracted size | 2.1 TB (bor) + 300 GB (heimdall) | 2.4 TB |
 | suggested disk size (2.5x buffer) | 2.4 TB * 2.5 (natural chain growth) | 6 TB |
 
-**Polygon Mumbai Erigon Archive**
+**Polygon Amoy Erigon Archive**
 
 | Metric | Calculation Breakdown | Value |
 | ------ | --------------------- | ----------- |