small fixs

docs/build/zkEVM/bridge-to-zkevm.md

@@ -15,10 +15,10 @@ import walletselect from '/docs/build/zkEVM/img/wallet-select.jpg'
 
 ## Overview
 
-Here you will find information about how to bridge assets to the Astar zkEVM. Bridged ETH is the native token required for testing and deployment of dApps on the Astar zkEVM, so before using the network, developers need to bridge some ETH from Layer 1 to Layer 2. Presently, there are two options for bridging assets to the zkEVM: 
+Here you will find information about how to bridge assets to the Astar zkEVM. Presently, there are two options for bridging assets to the zkEVM: 
 
-1. A canonical Layer 1 -> Layer 2 bridge from Ethereum to Astar zkEVM - accessible through the Astar Portal, which can take approximately 10-30 minutes, depending on network usage.
-2. A 3rd-party asset bridge or message network facilitating locking and minting of synthetic (wrapped) assets between Astar Substrate EVM and Astar zkEVM. See the [integrations section](/docs/build/zkEVM/integrations/bridges-relays/) for more information about how to use 3rd-party bridge services and compatible assets.
+1. Ethereum L1 to Astar zkEVM -> Bridged ETH is the native token required for testing and deployment of dApps on the Astar zkEVM, so before using the network, developers need to bridge some ETH from Layer 1 to Layer 2. Accessible through the Astar Portal, which can take approximately 10-30 minutes, depending on network usage.
+2. Astar Parachain to Astar zkZVM -> A 3rd-party asset bridge or message network facilitating locking and minting of synthetic (wrapped) assets between Astar Substrate EVM and Astar zkEVM. See the [integrations section](/docs/build/zkEVM/integrations/bridges-relays/) for more information about how to use 3rd-party bridge services and compatible assets.
 
 ### Transfer ETH using the Astar Portal
 
@@ -49,7 +49,7 @@ Click on the Bridge tab on the left-hand side. Ensure Sepolia is selected as Bri
 Sign the MetaMask transaction. 
 
 :::note
-Once the transaction shows as confirmed on the MetaMask Activity tab, it will take approximately 6-10 minutes for the Astar Portal and MetaMask to update your balance on the zKatana network side.
+Once the transaction shows as confirmed on the MetaMask Activity tab, it will take approximately 5-10 minutes for the Astar Portal and MetaMask to update your balance on the zKatana network side.
 :::
 
 

docs/build/zkEVM/faq/zkevm-eth-faq.md

@@ -16,7 +16,7 @@ The ultimate goal is not **compatibility**. The ultimate goal is **equivalence**
 
 1. **Development teams don't have to make changes to their code**, which could introduce security vulnerabilities.
 2. **No code changes are needed**. You don't need additional audits, which saves time and money. 
-3. **zkEVM ultimately benefits from the security and decentralization of Ethereum**, since transactions are still finalized on Ethereum.
+3. **zkEVM ultimately benefits from the security and decentralization of Ethereum**, since transactions are finalized on Ethereum.
 4. Astar zkEVM **benefits from the already vibrant and active Ethereum community**.
 5. Allows for **fast user onboarding**, since dApps built on Ethereum are already compatible.
 

docs/build/zkEVM/quickstart.md

@@ -48,7 +48,7 @@ To add zKatana testnet to MetaMask, use the link at the bottom of the [block exp
 
 ## Astar zkEVM Support for Developers
 
-Developers requiring support can open an issue on [Ethereum StackExchange](https://discord.gg/astarnetwork) and tag it with `Astar` (preferred) or join the [Astar Discord server](https://discord.gg/astarnetwork). 
+Developers requiring support can open an issue on [Ethereum StackExchange](https://ethereum.stackexchange.com/) and tag it with `Astar` (preferred) or join the [Astar Discord server](https://discord.gg/astarnetwork). 
 
 <details>
 <summary>Ethereum StackExchange</summary>
@@ -67,6 +67,6 @@ Developers requiring support can open an issue on [Ethereum StackExchange](https
 
 2. Accept the invite.
 3. Take the **Developer** role under **#roles**.
-4. Navigate to the **Builder/#zkevm-support** channel.
+4. Navigate to the **Builder/#zkevm-learning** channel.
 
 </details>

docs/build/zkEVM/smart-contracts/using-hardhat.md

@@ -137,8 +137,6 @@ uint256 currentCount = 0;
 
     ​Here's an output example:
 
-    ```
+    ```bash
     Counter contract deployed to https://zkatana.blockscout.com/address/0x8731DC57f9C7e01f5Ba733E7a10692cA540862f8
     ```
-```
-

docs/build/zkEVM/smart-contracts/verify-smart-contract.md

@@ -25,8 +25,8 @@ After successfully compiling a smart contract, follow the next steps to verify y
 4. Select the **Contract** tab and click the **Verify and Publish** button.
 
 6. There are 3 options to provide the Contract's code. We will be diving into the following two options:
-   1. Solidity, Flattened Source Code
-   2. Solidity, Standard Input JSON
+   - Solidity, Flattened Source Code
+   - Solidity, Standard Input JSON
 
 ### Solidity, Flattened Source Code
 

docs/build/zkEVM/zkevm-faucet.md

@@ -3,10 +3,18 @@ sidebar_position: 4
 title: Astar zkEVM Faucet
 sidebar_label: Faucet
 ---
-
+import sepolia from '/docs/build/zkEVM/img/metamask-sepolia-select.png'
 import useBaseUrl from '@docusaurus/useBaseUrl';
 
-## Overview
+## Connect MetaMask to Sepolia Testnet
+
+Open MetaMask and click on the network list (top left corner). Toggle `Show test networks` and select `Sepolia`
+
+<div style={{textAlign: 'center'}}>
+  <img src={sepolia} style={{width: 400}} />
+  </div>
+
+## Faucets
 
 **Faucet** is a tool provided to obtain Testnet tokens.