Merge branch 'main' into ACT-1464-reference-page-object-type

Author: aednikanov

README.md

@@ -1,3 +1,9 @@
+> :warning: **Temporary pause on contributions to the MetaMask docs repository**
+> 
+> Starting August 3, 2024, contributions to this repository will be temporarily paused.
+> Pull requests submitted during this period will not be reviewed or merged until after the pause.
+> Thank you for your understanding.
+
 # MetaMask developer documentation
 
 This is the MetaMask developer documentation repository.

docs/whats-new.md

@@ -11,13 +11,16 @@ of the [MetaMask developer page](https://metamask.io/developer/).
 
 ## July 2024
 
-- Documented [Celo WebSocket support](/services/reference/celo/). ([#1446](https://github.com/MetaMask/metamask-docs/pull/1446))
-- Documented [ZKsync Era WebSocket support](/services/reference/zksync). ([#1438](https://github.com/MetaMask/metamask-docs/pull/1438))
+- Documented [Binance Smart Chain](/services/reference/bnb-smart-chain/) support. ([#1458](https://github.com/MetaMask/metamask-docs/pull/1458))
+- Documented [Celo WebSocket](/services/reference/celo/) support. ([#1446](https://github.com/MetaMask/metamask-docs/pull/1446))
+- Documented [ZKsync Era WebSocket](/services/reference/zksync) support. ([#1438](https://github.com/MetaMask/metamask-docs/pull/1438))
 - Documented support for the [ZKsync Era network API service](/services/reference/zksync). ([#1372](https://github.com/MetaMask/metamask-docs/pull/1372))
 - Added [Services](/services) and [Developer tools](/developer-tools) to MetaMask documentation. ([#1325](https://github.com/MetaMask/metamask-docs/pull/1325))
 
 ## June 2024
 
+- Documented [Snaps custom UI with JSX](/snaps/features/custom-ui/with-jsx).
+  ([#1348](https://github.com/MetaMask/metamask-docs/pull/1348))
 - Updated [React dapp with global state tutorial](/wallet/tutorials/react-dapp-global-state) with
   instructions for EIP-6963.
   ([#1330](https://github.com/MetaMask/metamask-docs/pull/1330))

services/concepts/archive-data.md

@@ -56,25 +56,21 @@ Infura applies [rate limits](../how-to/avoid-rate-limiting.md) to ensure network
 
 Requests for Ethereum archive data are more expensive and are therefore subject to different rate limits.
 
-**Free plan**
+### Free plan
 
-- 25,000 archive requests per day.
-- 100,000 total requests per day.
-
-Rate limits kick in on archive requests after 25,000 per day. 75,000 standard requests are still available after this point.
+You can make up to 25,000 archive requests and 100,000 total requests per day.
+After reaching 25,000 archive requests, you can still make 75,000 additional standard requests.
 
 :::info
 
 If you need more archive requests, upgrade to the Developer plan.
 
 :::
 
-**Developer plan**
-
-- 100,000 archive requests per day.
-- 200,000 total requests per day.
+### Developer plan
 
-Rate limits kick in on archive requests after 100,000 per day. 100,000 standard requests are still available after this point.
+You can make up to 100,000 archive requests and 200,000 total requests per day. 
+After reaching 100,000 archive requests, you can still make 100,000 additional standard requests.
 
 :::info
 

services/get-started/endpoints.md

@@ -47,6 +47,14 @@ request to `support@infura.io` and we will assess if your request can be accommo
 | Mainnet           | JSON-RPC over HTTPS | `https://blast-mainnet.infura.io/v3/<API-KEY>` |
 | Testnet (Sepolia) | JSON-RPC over HTTPS | `https://blast-sepolia.infura.io/v3/<API-KEY>` |
 
+## Binance Smart Chain
+
+| Network           | Transport type          | URL                                           |
+|-------------------|-------------------------|-----------------------------------------------|
+| Mainnet           | JSON-RPC over HTTPS     | `https://bsc-mainnet.infura.io/v3/<API-KEY>`  |
+| Mainnet           | JSON-RPC over WebSocket | `wss://bsc-mainnet.infura.io/ws/v3/<API-KEY>` |
+| Testnet (Sepolia) | JSON-RPC over HTTPS     | `https://bsc-testnet.infura.io/v3/<API-KEY>`  |
+
 ## Celo
 
 | Network             | Description             | URL                                              |
@@ -139,7 +147,7 @@ Sepolia instead.
 | Testnet (Amoy) | JSON-RPC over HTTPS     | `https://polygon-amoy.infura.io/v3/<API-KEY>`     |
 | Testnet (Amoy) | JSON-RPC over WebSocket | `wss://polygon-amoy.infura.io/ws/v3/<API-KEY>`    |
 
-## StarkNet
+## Starknet
 
 | Network           | Description         | URL                                               |
 | ----------------- | ------------------- | ------------------------------------------------- |

services/get-started/infura.md

@@ -29,14 +29,11 @@ For more information refer to the [Infura pricing information](https://www.infur
 
 ## 2. Configure your API key
 
-Once verified, you’ll be taken to the [Infura dashboard](../../../developer-tools/dashboard) where you can configure your
+After verification, you'll be directed to the [Infura dashboard](../../../developer-tools/dashboard) to configure your
 auto-generated API key.
 
-:::info
-
-Infura will automatically generate the **My First Key** API key for you.
+Infura will automatically generate the **My First Key** API key.
 
-:::
 
 <div class="left-align-container">
   <div class="img-large">
@@ -46,10 +43,10 @@ Infura will automatically generate the **My First Key** API key for you.
   </div>
 </div>
 
-In the API key page that appears, select **My First Key** to access your API key settings. In the **All Endpoints** tab, select
-the networks that you wish to connect to, and select **Save Changes**.
+In the API key page that displays, select **My First Key** to access your API key settings. In the **All Endpoints** tab, select
+the networks that you want to connect to, and select **Save Changes**.
 
-In this example, we've selected the Ethereum mainnet and Linea mainnet networks.
+In the following example, Ethereum mainnet and Linea mainnet networks are selected.
 
 <div class="left-align-container">
   <div class="img-large">
@@ -61,7 +58,7 @@ In this example, we've selected the Ethereum mainnet and Linea mainnet networks.
 
 ## 3. Send requests
 
-Use the API key when sending requests. The following examples interact with the Ethereum network by sending requests using HTTP.
+Use the API key when sending requests. The following examples interact with the Ethereum network by sending requests using HTTP:
 
 :::info
 
@@ -70,7 +67,13 @@ Use the API key when sending requests. The following examples interact with the
 
 :::
 
-Use a tool such as the [Client Uniform Resource Locator (curl)](../concepts/curl.md) or [Postman](https://www.postman.com/downloads/) to make requests. We recommend using Postman if you're a Windows user.
+Use a tool such as the [Client Uniform Resource Locator (curl)](../concepts/curl.md) or [Postman](https://www.postman.com/downloads/) to make requests. 
+
+:::info
+
+We recommend using Postman if you're a Windows user.
+
+:::
 
 ### 3.1 Get the current block number
 

services/how-to/enable-api-forwarding.md

@@ -1,6 +1,6 @@
 ---
 description: Enable API forwarding
-sidebar_position: 6
+sidebar_position: 7
 ---
 
 import Tabs from "@theme/Tabs";

services/how-to/interact-with-erc-20-tokens.md

@@ -1,6 +1,6 @@
 ---
 description: Interact with ERC 20 tokens
-sidebar_position: 2
+sidebar_position: 3
 ---
 
 import Tabs from "@theme/Tabs";

services/how-to/javascript-dotenv.md

@@ -1,6 +1,6 @@
 ---
 description: Use dotenv to load environment variables from a file.
-sidebar_position: 7
+sidebar_position: 8
 ---
 
 # Use JavaScript dotenv

services/how-to/json-web-token-jwt.md

@@ -1,6 +1,6 @@
 ---
 description: Use JSON Web Tokens to secure data exchange.
-sidebar_position: 8
+sidebar_position: 9
 ---
 
 import Tabs from "@theme/Tabs";
@@ -74,51 +74,49 @@ Upload the contents of the public key file that you [generated earlier](json-web
 
 1. Go to the **SECURITY** section in your project settings.
 
-![Security settings](../images/security-page.png)
+  ![Security settings](../images/security-page.png)
 
-:::info
+  :::info
 
-You must implement separate security settings for each project.
+  You must implement separate security settings for each project.
 
-:::
+  :::
 
-2. Check the **Require JWT for all requests** box to enforce JWT on all requests. This is optional.
+2. (Optional) Check the **Require JWT for all requests** box to enforce JWT on all requests.
 
-:::info
+  :::info
 
-Use allowlists to specify a subset of requests that must use JWTs.
+  Use allowlists to specify a subset of requests that must use JWTs.
 
-:::
+  :::
 
 3. Give the public key a name.
 
 4. Paste the public key into the **JWT PUBLIC KEY** input box. It looks something like this:
 
-```
------BEGIN PUBLIC KEY-----
-MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr7VlNytvNFt9wVkjJ8vG
-L4F0+id4kS1CpG7UMh1kghrLg9KMb8gauy7Bxk6PRz5Ckv1FnG4FL+Z3Cdzwd6c8
-jJlzJxbRTYvNi3elqAyItE3tRl6CatRur49t9nGepgFOrwmPP5We52G5O0BsW6Mx
-w/neqQH+Y/bXqs0PG/0ZbpTyr044Lh+p9grSuPIogIGIY5JM4AI+fpdH6hVnA7od
-PkinkWhQqAW+F8jngwZK+JCFS1GAeobTZVbvsiHZQGuP/T7hqE8z5Q8HYO4ymnkI
-MPH6zSKhSxsQRs/kWU5lXqY67ORC3DIMA+I/AJujLuoqC+YaMP0fO81XjrwXPf2j
-4wIDAQAB
------END PUBLIC KEY-----
-```
-
-5. Click **ADD** to add the key to the settings.
+  ```
+  -----BEGIN PUBLIC KEY-----
+  MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEAr7VlNytvNFt9wVkjJ8vG
+  L4F0+id4kS1CpG7UMh1kghrLg9KMb8gauy7Bxk6PRz5Ckv1FnG4FL+Z3Cdzwd6c8
+  jJlzJxbRTYvNi3elqAyItE3tRl6CatRur49t9nGepgFOrwmPP5We52G5O0BsW6Mx
+  w/neqQH+Y/bXqs0PG/0ZbpTyr044Lh+p9grSuPIogIGIY5JM4AI+fpdH6hVnA7od
+  PkinkWhQqAW+F8jngwZK+JCFS1GAeobTZVbvsiHZQGuP/T7hqE8z5Q8HYO4ymnkI
+  MPH6zSKhSxsQRs/kWU5lXqY67ORC3DIMA+I/AJujLuoqC+YaMP0fO81XjrwXPf2j
+  4wIDAQAB
+  -----END PUBLIC KEY-----
+  ```
 
-6. The key is added to security settings.
+5. Click **ADD** to add the key to the settings. After the key is added, the security settings look like the following:
 
-![JWT set up](../images/jwt-set-up.png)
+  ![JWT set up](../images/jwt-set-up.png)
 
-7. The key has a **NAME**, **ID**, **FINGERPRINT**. These are used for creating and verifying JWTs. You'll need the **ID** to [generate the JWT](json-web-token-jwt.md#generate-a-jwt).
+6. The key has a **NAME**, **ID**, **FINGERPRINT**. These are used for creating and verifying JWTs. You'll need the **ID** to [generate the JWT](json-web-token-jwt.md#generate-a-jwt).
 
-:::info
+  :::info
 
-For key rotation, upload up to three keys for each project.
+  For key rotation, upload up to three keys for each project.
 
-:::
+  :::
 
 ## Send requests with JWTs
 

services/how-to/make-batch-requests.md

@@ -1,6 +1,6 @@
 ---
 description: Make batch requests
-sidebar_position: 3
+sidebar_position: 4
 ---
 
 # Make batch requests