fix: metamask broken links

Author: nijoe1

basics/assets/transfer-fil.md

@@ -26,10 +26,10 @@ Remember that Filecoin is fully compatible with Ethereum tools, like wallets. Bu
 
 If you want to transfer FIL tokens from one `f4` address to another `f4` address using their corresponding `0x` addresses, you need to understand how to convert between `f4` and `0x` addresses.
 
-* If you have `f4` address, you can convert it to `0x` address using [Beryx Address converter](https://beryx.zondax.ch/address\_converter).
-* If you have a `0x` address, you can directly search it on [Filfox Explorer](https://filfox.info/en), which will show the `0x` address and corresponding `f4` address.
+- If you have `f4` address, you can convert it to `0x` address using [Beryx Address converter](https://beryx.zondax.ch/address_converter).
+- If you have a `0x` address, you can directly search it on [Filfox Explorer](https://filfox.info/en), which will show the `0x` address and corresponding `f4` address.
 
-Apart from that, you just need to follow the standard process using your preferred Ethereum-compatible wallet, like MetaMask, MethWallet, etc. For instance, [MetaMask has a simple guide](https://support.metamask.io/hc/en-us/articles/360015488931-How-to-send-tokens-from-your-MetaMask-wallet) for how to send Ethereum from one account to another.
+Apart from that, you just need to follow the standard process using your preferred Ethereum-compatible wallet, like MetaMask, MethWallet, etc. For instance, [MetaMask has a simple guide](https://support.metamask.io/manage-crypto/move-crypto/send/how-to-send-tokens-from-your-metamask-wallet/) for how to send Ethereum from one account to another.
 
 ## 0x => f address
 
@@ -74,8 +74,8 @@ If you want to transfer your FIL tokens from the `f1\f3` to the `0x` address, bu
 8. Once the funds appear in the burner wallet, click on **Send FIL**.
 9. Enter the necessary information into the text fields:
 
-* In the **Recipient** field, enter your `0x` style address. GLIF automatically converts it to an `f4` address.
-* In the **Amount** field, enter the amount of FIL to send. Make sure you have enough FIL to cover the GAS cost.
+- In the **Recipient** field, enter your `0x` style address. GLIF automatically converts it to an `f4` address.
+- In the **Amount** field, enter the amount of FIL to send. Make sure you have enough FIL to cover the GAS cost.
 
 ![Fill out send detail](<../../.gitbook/assets/basics-assets-transfer-fil-send-detail-burner-wallet (1).webp>)
 
@@ -89,6 +89,4 @@ If you are transferring FIL from any exchange to your `0x` address on MetaMask,
 
 There are no special steps or requirements for sending Filecoin from one Filecoin-style address to another on the Filecoin network.
 
-
-
-[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill\_Page+URL=https://docs.filecoin.io/basics/assets/transfer-fil)
+[Was this page helpful?](https://airtable.com/apppq4inOe4gmSSlk/pagoZHC2i1iqgphgl/form?prefill_Page+URL=https://docs.filecoin.io/basics/assets/transfer-fil)

smart-contracts/developing-contracts/best-practices.md

@@ -30,7 +30,7 @@ We recommend users resubmit the message with a higher gas fee or priority fee so
 
 #### **Metamask**
 
-If you are building your project using MetaMask, it would be easier to educate the users to speed up a transaction by increasing the gas fee directly in MetaMask. Refer to the [official MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015489251-How-to-speed-up-or-cancel-a-pending-transaction) for more details.
+If you are building your project using MetaMask, it would be easier to educate the users to speed up a transaction by increasing the gas fee directly in MetaMask. Refer to the [official MetaMask documentation](https://support.metamask.io/manage-crypto/transactions/how-to-speed-up-or-cancel-a-pending-transaction/) for more details.
 
 #### **Lotus**
 

smart-contracts/developing-contracts/client-contract-tutorial.md

@@ -47,7 +47,7 @@ First, let’s grab the kit and set up the development environment.
     ```shell
     mv .env.example .env
     ```
-4. Within the `.env` file, replace the example private key with your actual private key. If you are using Metamask, follow [this tutorial to get your private key](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key).
+4. Within the `.env` file, replace the example private key with your actual private key. If you are using Metamask, follow [this tutorial to get your private key](https://support.metamask.io/configure/accounts/how-to-export-an-accounts-private-key/).
 
 {% hint style="info" %}
 Take precautions and never share your private key with anyone! Also make sure to not check your private key into Git. The `.gitignore` of the Hardhat kit is already set to ignore `.env` files.

smart-contracts/developing-contracts/foundry.md

@@ -33,7 +33,7 @@ cd fevm-foundry-kit
 yarn install
 ```
 
-3. Export your private key from MetaMask. See the [MetaMask documentation](https://support.metamask.io/hc/en-us/articles/360015289632-How-to-export-an-account-s-private-key) to find out how to export your private key.
+3. Export your private key from MetaMask. See the [MetaMask documentation](https://support.metamask.io/configure/accounts/how-to-export-an-accounts-private-key/) to find out how to export your private key.
 
 4. Create your env file by running