diff --git a/.gitbook/assets/binance-receive.png b/.gitbook/assets/wallet/binance-receive.png similarity index 100% rename from .gitbook/assets/binance-receive.png rename to .gitbook/assets/wallet/binance-receive.png diff --git a/.gitbook/assets/polygon-explorer.png b/.gitbook/assets/wallet/polygon-explorer.png similarity index 100% rename from .gitbook/assets/polygon-explorer.png rename to .gitbook/assets/wallet/polygon-explorer.png diff --git a/.gitbook/assets/wallet/polygon-login.png b/.gitbook/assets/wallet/polygon-login.png index c45118d7..e9b366dc 100644 Binary files a/.gitbook/assets/wallet/polygon-login.png and b/.gitbook/assets/wallet/polygon-login.png differ diff --git a/discover/networks/bridges.md b/discover/networks/bridges.md index b5910d30..74da807e 100644 --- a/discover/networks/bridges.md +++ b/discover/networks/bridges.md @@ -18,7 +18,7 @@ To transfer Ocean tokens to and from the Binance Smart Chain, we recommend using {% hint style="warning" %} In case you opt for an alternative bridge option and intend to transfer tokens to Binance, it is crucial to ensure that the contract address you are sending the tokens to is correct. -## +## {% endhint %} @@ -63,7 +63,7 @@ Unlike the first two cases where transactions are signed on the Ethereum Mainnet The easiest one is to go to the [polygon network explorer](https://polygonscan.com/) and tap on the "Add polygon network" button. -
+
Alternatively, you can manually configure the network on Metamask by using the following parameters. To learn how to set up a custom network in Metamask using these values, you can refer to our guide.