Updates and fixes

Author: hsutaiyu

docs/pos/how-to/snapshots.md

@@ -6,7 +6,7 @@ When setting up a new sentry, validator, or full node server, it is recommended
 
 ## Community snapshots
 
-With the [deprecation of the Mumbai testnet](https://forum.polygon.technology/t/pos-tooling-after-mumbai-deprecation-no-action-required/13740), Polygon PoS is shifting to a community-driven model for snapshots where active validators like Vault Staking, Stakepool, StakeCraft, and Girnaar Nodes will now provide snapshots. See [All4nodes.io](https://all4nodes.io/Polygon), an aggregator for Polygon community snapshots, for future community snapshots on the Sepolia-anchored Amoy testnet.
+With the [deprecation of the Mumbai testnet](https://forum.polygon.technology/t/pos-tooling-after-mumbai-deprecation-no-action-required/13740), Polygon PoS is shifting to a community-driven model for snapshots. Active validators such as Vault Staking, Stakepool, StakeCraft, and Girnaar Nodes will now provide snapshots. For future community snapshots on the Sepolia-anchored Amoy testnet, visit [All4nodes.io](https://all4nodes.io/Polygon), an aggregator for Polygon community snapshots.
 
 !!! tip "Older snapshots"
 
@@ -259,9 +259,7 @@ Please check the hardware requirements for an Erigon mainnet archive node on the
 
 ## Recommended disk type and IOPS guidance
 
-- Disk IOPS will impact speed of downloading/extracting snapshots,
-  getting in sync, and performing LevelDB compaction
+- Disk IOPS will impact speed of downloading/extracting snapshots, getting in sync, and performing LevelDB compaction.
 - To minimize disk latency, direct attached storage is ideal.
-- In AWS, when using gp3 disk types, we recommend provisioning IOPS of 16000 and
-  throughput of 1000 - this minimizes cost and adds a lot of performance. io2 EBS volumes with matching IOPS and throughput values are similarly performant.
+- In AWS, when using gp3 disk types, we recommend provisioning IOPS of 16000 and throughput of 1000. This minimizes cost and adds a lot of performance. io2 EBS volumes with matching IOPS and throughput values are similarly performant.
 - For GCP, we recommend using performance (SSD) persistent disks (`pd-ssd`) or extreme persistent disks (`pd-extreme`) with similar IOPS and throughput values as seen above.

docs/pos/reference/rpc-endpoints.md

@@ -6,9 +6,13 @@ This guide provides an index of network details for the Polygon Amoy testnet and
 
 ## Network details
 
+!!! warning "Mumbai testnet deprecated"
+
+    The Goerli-anchored Mumbai testnet is now deprecated. Please use the Sepolia-anchored Amoy testnet for all future testing and dApp development activities on Polygon PoS.
+
 ### Amoy
 
-The Amoy testnet serves as a replica of the Polygon mainnet and is primarily used for testing. **Amoy network will soon replace Mumbai Testnet**. Obtain testnet tokens from the [faucet](https://faucet.polygon.technology/). Note that these tokens hold no value and differ from MATIC.
+The Amoy testnet serves as a replica of the Polygon mainnet and is primarily used for testing. Obtain testnet tokens from the [faucet](https://faucet.polygon.technology/). Note that these tokens hold no value and differ from MATIC.
 
 | Properties       | Network details                                                                                    |
 | ---------------- | -------------------------------------------------------------------------------------------------- |
@@ -22,8 +26,7 @@ The Amoy testnet serves as a replica of the Polygon mainnet and is primarily use
 | Heimdall API     | [https://heimdall-api-amoy.polygon.technology](https://heimdall-api-amoy.polygon.technology)       |
 | Block Explorer   | [https://amoy.polygonscan.com/](https://amoy.polygonscan.com/)                                         |
 
-!!!note
-    Additional information
+!!! note "Additional information"
 
     For more details, refer to this [**JSON data**](https://static.polygon.technology/network/testnet/amoy/index.json).
 
@@ -44,8 +47,7 @@ The native token for the Polygon PoS mainnet is MATIC, which is used for transac
 | Heimdall API     | [https://heimdall-api.polygon.technology](https://heimdall-api.polygon.technology)                 |
 | Block explorer   | [https://polygonscan.com/](https://polygonscan.com/)                                               |
 
-!!!note
-    Additional information
+!!! note "Additional information"
 
     For more details, refer to this [**JSON data**](https://github.com/maticnetwork/static/blob/master/network/mainnet/v1/index.json).
 
@@ -66,9 +68,9 @@ The Mumbai testnet serves as a replica of the Polygon mainnet and is primarily u
 | Heimdall API     | [https://heimdall-api-testnet.polygon.technology](https://heimdall-api-testnet.polygon.technology) |
 | Block Explorer   | [https://mumbai.polygonscan.com/](https://mumbai.polygonscan.com/)                                 |
 
-!!!note
-    Additional information
-
+!!! note "Additional information
+"
+    
     For more details, refer to this [**JSON data**](https://static.polygon.technology/network/testnet/mumbai/index.json).
 
 </TabItem>
@@ -78,8 +80,7 @@ The Mumbai testnet serves as a replica of the Polygon mainnet and is primarily u
 
 Developers can interact with on-chain data and execute various types of transactions using network endpoints. These APIs adhere to the JSON-RPC standard, a stateless, lightweight remote procedure call (RPC) protocol.
 
-!!!info
-    Getting started with RPC calls
+!!! info "Getting started with RPC calls"
 
     For a comprehensive list of API documentation, visit [**Polygon JSON-RPC calls**](https://github.com/0xPolygon/polygon-edge/tree/develop/docs/docs/api).