Merge branch 'main' of https://github.com/0xPolygon/polygon-docs into km/learn-frontpage

Author: kmurphypolygon

docs/pos/how-to/bridging/ethereum-polygon/index.md

@@ -1,10 +1,10 @@
-Polygon brings you a trustless two-way transaction channel between Polygon PoS and Ethereum by introducing the cross-chain bridge. With this users can transfer tokens across Polygon PoS without incurring third-party risks and market liquidity limitations. "img/home/The PoS Bridge is available on both Mumbai Testnet as well as Polygon PoS Mainnet"img/home/. You can bridge assets to Polygon PoS using the [Polygon Wallet Suite](https://wallet.polygon.technology/polygon/bridge/deposit).
+Polygon brings you a trustless two-way transaction channel between Polygon PoS and Ethereum by introducing the cross-chain bridge. With this users can transfer tokens across Polygon PoS without incurring third-party risks and market liquidity limitations. 
 
-Polygon also offers the "img/home/zkEVM Bridge"img/home/ which can also be used via the [Polygon Wallet Suite](https://wallet.polygon.technology/polygon/bridge/deposit). This document is not about zkEVM Bridge.
+The PoS Bridge is available on both Mumbai Testnet as well as Polygon PoS Mainnet. You can access it and bridge assets over to Polygon PoS using the [Polygon Wallet Suite](https://wallet.polygon.technology/polygon/bridge/deposit).
 
-"img/home/Polygon PoS bridge provides a bridging mechanism that is near-instant, low-cost, and quite flexible"img/home/.
+Polygon PoS bridge provides a bridging mechanism that is near-instant, low-cost, and quite flexible.
 
-"img/home/There is no change to the circulating supply of your token when it crosses the bridge"img/home/;
+There is no change to the circulating supply of your token when it crosses the bridge;
 
 - Tokens that leave the Ethereum network are locked and the same number of tokens are minted on Polygon PoS as a pegged token (1:1).
 - To move the tokens back to the Ethereum network, tokens are burned on Polygon PoS network and unlocked on Ethereum network during the process.

docs/zkEVM/get-started/setup-nodes/production-node.md

@@ -75,7 +75,7 @@ Let's start setting up our zkNode:
 
 2. Download and extract the artifacts. Note that you may need to [install unzip](https://formulae.brew.sh/formula/unzip) before running this command. Also, unlike the mainnet and the Goerli testnet that use the latest version, Cardona testnet uses a specific version.
 
-   So use the next `curl` command specifically for Cardona, which uses version 0.5.5 (Note that the latest version, [Cardona v0.5.6](https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.5.6), is available and can equally be used.):
+   So use the next `curl` command specifically for Cardona, which uses version 0.5.5 (Note that the latest version, [Cardona v0.5.7](https://github.com/0xPolygonHermez/zkevm-node/releases/tag/v0.5.7), is available and can equally be used.):
 
    ```bash
     curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/download/v0.5.5/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip
@@ -87,14 +87,14 @@ Let's start setting up our zkNode:
     curl -L https://github.com/0xPolygonHermez/zkevm-node/releases/latest/download/$ZKEVM_NET.zip > $ZKEVM_NET.zip && unzip -o $ZKEVM_NET.zip -d $ZKEVM_DIR && rm $ZKEVM_NET.zip
    ```
 
-3. Copy the `example.env` file with the environment parameters:
+4. Copy the `example.env` file with the environment parameters:
 
     ```sh
     cp $ZKEVM_DIR/$ZKEVM_NET/example.env $ZKEVM_CONFIG_DIR/.env
 
     ```
 
-4. The `example.env` file must be modified according to your configurations.
+5. The `example.env` file must be modified according to your configurations.
 
     Edit the .env file with your favourite editor (we'll use nano in this guide): ```nano $ZKEVM_CONFIG_DIR/.env```
 
@@ -111,13 +111,13 @@ Let's start setting up our zkNode:
       ZKEVM_NODE_POOLDB_DATA_DIR = "/path/to/persistent/data/pooldb"
       ```
 
-5. To run the zkNode instance, run the following command:
+6. To run the zkNode instance, run the following command:
 
     ```bash
     sudo docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml up -d
     ```
 
-6. Run this command to check if everything went well and all the components are running properly:
+7. Run this command to check if everything went well and all the components are running properly:
 
     ```bash
     docker compose --env-file $ZKEVM_CONFIG_DIR/.env -f $ZKEVM_DIR/$ZKEVM_NET/docker-compose.yml ps
@@ -130,7 +130,7 @@ Let's start setting up our zkNode:
       - **zkevm-pool-db**
       - **zkevm-prover**
 
-7. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
+8. You should now be able to run queries to the JSON-RPC endpoint at `http://localhost:8545`.
 
 ## Testing