Merge branch 'main' into trivy-cache-workflow

Author: joshuafernandes

developer-tools/dashboard/get-started/create-api.md

@@ -20,33 +20,24 @@ For more information, see to the [Infura pricing page](https://www.infura.io/pri
 Infura allows you to enable multiple network endpoints and expansion APIs for your API key. If calls are
 made to a disabled network or service, then all requests to that network or service will fail.
 
-To keep your account secure and cost effective, add only the necessary endpoints, as some have usage limits or charges based
-on request volume.
+To keep your account secure and cost effective, add only the necessary endpoints, as some have usage
+limits or charges based on request volume.
 
 To create an API key:
 
-1. Open the [Infura dashboard](https://infura.io/dashboard). Enter your login details, if required.
-1. Select **CREATE NEW API KEY**.
-
-<div class="left-align-container">
-<div class="img-large">
-    <img
-    src={require("../../images/create_key.png").default}
-    />
-</div>
-</div>
-
-1. From the pop-up window, provide a name, then click **CREATE**.
+1. Open the [MetaMask Developer dashboard](https://infura.io/dashboard). Enter your login details, if required.
+1. In the top right corner, select **Create new API key**.
+1. From the pop-up window, provide a name, then click **Create**.
 1. Select the networks that you want your API key to access, and select **Save Changes**.
 
-You can [configure additional security](../how-to/secure-an-api/api-key-secret.md) for your API key by requiring an API key secret or JWTs with
-each API request.
+You can [configure additional security](../how-to/secure-an-api/api-key-secret.md) for your API key by
+requiring an API key secret or JWTs with each API request.
 
 ## Best practices for configuring API key endpoints
 
 We recommend the following best practices when creating your API keys:
 
-- Group API key endpoints by environment. For example, create seperate API keys for production or development environments.
+- Group API key endpoints by environment. For example, create separate API keys for production or development environments.
 - Group API key endpoints by groups or individuals [sharing the API key](../how-to/project-sharing.md).
 - Limit the number of networks or services per API key only to the necessary endpoints.
 - Group the API key endpoints based on shared security considerations such as

developer-tools/dashboard/how-to/credit-usage.md

@@ -7,7 +7,7 @@ description: View your Infura credit usage stats.
 You can view your daily credit usage in relation to your daily credit quota limit. Daily credit usage
 counts are reset everyday at 00:00 UTC for all customers.
 
-Select **View Usage** from the **Daily Credit Usage** section on the Infura dashboard, or select
+Select **View Usage** from the **Daily Credit Usage** section on the dashboard, or select
 the **Usage** tab from the **Settings** > **Billing** dropdown.
 
 View your usage for the previous 24 hours, 7 days, or 30 days by methods used, networks, or API key.

developer-tools/dashboard/how-to/dashboard-stats.md

@@ -11,7 +11,7 @@ This data is crucial for optimizing your applications and ensuring they run smoo
 
 ## Specify stats to view
 
-1. In the top menu of the [Infura dashboard](https://app.infura.io/), select **Stats**.
+1. In the left menu of the [MetaMask Developer dashboard](https://developer.metamask.io/), select **Stats**.
    The stats page displays the total volume of requests sent to Infura over the specified time period.
    By default, data is shown from the last 24 hours from all Web3 API keys.
 
@@ -40,13 +40,13 @@ You can view your Web3 API usage stats in the following charts and tables.
 
 ### Requests Volume chart
 
-This chart displays the total volume of requests sent to Infura using the selected API key(s) over
+This chart displays the total volume of requests sent to Infura using the selected API keys over
 the selected time period.
 
 ### Product Request Volumes
 
 This chart displays the aggregate request volumes for the top five API methods called using the
-selected API key(s) over the selected time period.
+selected API keys over the selected time period.
 To view stats for a particular product (network) instead of the default of all products, make a
 selection from the products dropdown.
 This change will impact what API methods are displayed in the
@@ -55,14 +55,14 @@ This change will impact what API methods are displayed in the
 ### Method Request Volumes
 
 This chart displays the aggregate request volumes for requests made on the top five networks using
-the selected API key(s) over the selected time period.
+the selected API keys over the selected time period.
 To view stats for a particular method instead of the default of all methods, make a selection from
 the methods dropdown.
 
 ### Requests Activity
 
 This table displays the total request volumes and successful and failed requests, based on each
-product (network) and method called using the selected API key(s) over the selected time period.
+product (network) and method called using the selected API keys over the selected time period.
 
 For more details about the failure status codes, select the two diagonal arrows to the right of the
 **FAILED REQUESTS (%)** values.
@@ -72,7 +72,7 @@ requests, grouped by the returned status codes.
 ### Eth_call activity
 
 This table displays the activities made on the `eth_call` method, including contract addresses that
-interacted with the selected API key(s).
+interacted with the selected API keys.
 This table only shows the `eth_call` activity for the last 30 minutes, and is not impacted by any
 time period selection.
 
@@ -85,15 +85,15 @@ You can view your IPFS usage stats in the following charts.
 
 ### Data Transfer Up
 
-This chart displays the amount of data sent to the IPFS service using the selected API key(s) over
+This chart displays the amount of data sent to the IPFS service using the selected API keys over
 the selected time period.
 
 ### Data Transfer Down
 
-This chart displays the amount of data retrieved from the IPFS service using the selected API key(s)
+This chart displays the amount of data retrieved from the IPFS service using the selected API keys
 over the selected time period.
 
 ### Total Storage
 
-This chart displays the total amount of data stored by the selected API key(s) over the selected
+This chart displays the total amount of data stored by the selected API keys over the selected
 time period.

developer-tools/dashboard/how-to/network-status.md

@@ -5,10 +5,10 @@ sidebar_position: 8
 
 # View the network status
 
-View the [Infura status page](https://status.infura.io/) to check for service outages and other incidents, as well as
+View the [Infura status page](https://status.infura.io/) to check for service outages, incidents, and
 scheduled maintenance notices. You can also subscribe to status updates via email, SMS, webhook, Slack, and Atom/RSS.
 
-You can also select the **Status** link at the top of the Infura dashboard to view the status page.
+You can also select the **Status** link on the left of the MetaMask Developer dashboard to view the status page.
 
 <div class="left-align-container">
   <div class="img-medium">

developer-tools/dashboard/how-to/project-sharing.md

@@ -11,9 +11,9 @@ You can share access to your Infura API keys by inviting existing Infura account
 
 To share an API key:
 
-1. In the Infura dashboard, select the API that you want to share.
+1. In the dashboard, select the API that you want to share.
 1. Select the **API Key Sharing** tab.
-1. Select **INVITE MEMBERS** in the top right.
+1. Select **Invite Members** in the top right.
 
    <div class="left-align-container">
      <div class="img-large">
@@ -23,8 +23,8 @@ To share an API key:
      </div>
    </div>
 
-1. Input one or more user emails, select the [user role](#user-roles), and select **SUBMIT**.
-1. Confirm your email address and select **CONFIRM**.
+1. Input one or more user emails, select the [user role](#user-roles), and select **Submit**.
+1. Confirm your email address and select **Confirm**.
 
 :::note
 
@@ -72,28 +72,20 @@ You can view all keys that you own, and all keys shared with you, by selecting *
 
 ## Update user role or remove user
 
-1. In the Infura dashboard, select the API key that the user is assigned to.
+1. In the dashboard, select the API key that the user is assigned to.
 1. Select the **API Key Sharing** tab.
 1. Select the vertical ellipsis icon next to the relevant user.
 
    - To remove a user, select **Remove Member**. They are removed immediately.
    - To update a user's role, select **Update Role**.
 
-     <div class="left-align-container">
-       <div class="img-large">
-         <img
-           src={require("../../images/update-role.png").default}
-         />
-       </div>
-     </div>
-
-1. Upgrade or downgrade accordingly and select **UPDATE ROLE**.
+1. Upgrade or downgrade accordingly and select **Update Role**.
 
 ## Revoke or resend an invite
 
 While invitations remain in a pending state, they can be revoked or sent again.
 
-1. In the Infura dashboard, select the API key for the user.
+1. In the dashboard, select the API key for the user.
 
 1. Select the **API Key Sharing** tab.
 

developer-tools/dashboard/how-to/secure-an-api/api-key-secret.md

@@ -22,7 +22,7 @@ If your dapp operates solely on the client side without a server, use only the A
 The API key is exposed in client-side code, so you should secure it using [allowlists](use-an-allowlist.md).
 
 :::tip
-For customers on the Developer tier or higher, Infura supports [overriding your allowlist](use-an-allowlist.md#overide-your-allowlist-settings)
+For customers on the Developer tier or higher, Infura supports [overriding your allowlist](use-an-allowlist.md#override-your-allowlist-settings)
 when you specify an API key secret. This allows you to apply the principle of least privilege on the
 client side while allowing unrestricted access on the server side.
 :::
@@ -34,7 +34,7 @@ In the API key's **Settings** tab, select **Require API Key secret for all reque
 <div class="left-align-container">
   <div class="img-large">
     <img
-      src={require("../../../images/security-page.png").default}
+      src={require("../../../images/settings-tab.png").default}
     />
   </div>
 </div>

developer-tools/dashboard/how-to/secure-an-api/api-key.md

@@ -13,7 +13,7 @@ A request will fail if it does not have a valid API key appended to the request
 
 :::
 
-Select the API key in the Infura dashboard to view the key's details. The API key to include in your requests can be
+Select the API key in the dashboard to view the key's details. The API key to include in your requests can be
 copied at the top of the page.
 
 Apply the principle of least privilege. Add only the endpoints that you plan to use, and then use the other

developer-tools/dashboard/how-to/secure-an-api/set-rate-limits.md

@@ -15,14 +15,14 @@ Set rate limiting in the API key's **Settings** tab **Key Credit Limits** sectio
   </div>
 </div>
 
-- **PER SECOND CREDIT RATE-LIMITING** restricts credits per second (throughput) for the API key. Set
+- **Per second credit rate-limiting** restricts credits per second (throughput) for the API key. Set
     the maximum number of credits per second in whole numbers. When credits per second rate exceeds
     this value, requests are rejected. When the credit rate drops below the limit, requests
     are accepted again.
 
     The value `0` means default limits are applied.
 
-- **PER DAY TOTAL CREDITS** restricts total daily credit usage for the API key. Set a limit on number of
-    credits per day in integers, e.g. 20000. The value `0` means default limits are applied.
+- **Per day total credits** restricts total daily credit usage for the API key. Set a limit on number of
+    credits per day in integers, for example, 20000. The value `0` means default limits are applied.
 
     When the number of used credits reach this limit, all requests will be rejected until the next day (00:00 UTC).

developer-tools/dashboard/how-to/secure-an-api/use-an-allowlist.md

@@ -29,16 +29,17 @@ Add the restriction details in the **ALLOWLISTS** section of your API key's **Se
 #### Allowlist behavior
 
 - If an API key has no allowlists, all requests are accepted.
-- As soon as an API key has an allowlist definition, all requests must pass it.
+- When an API key has an allowlist definition, all requests must pass the definition.
 - Each API key has a maximum of 30 allowlist entries per type.
 - Each allowlist type is "AND"ed together.
 - Multiple entries of the same type are "OR"ed.
 
 ## Contract addresses
 
-If your application only queries data from specific Ethereum smart contracts or addresses, add those addresses to the **CONTRACT ADDRESSES** allowlist.
+If your application only queries data from specific Ethereum smart contracts or addresses, add those
+addresses to the **Contract Addresses** allowlist.
 
-Any requests which query addresses that are not in the allowlist are rejected.
+Any requests which query addresses that aren't in the allowlist are rejected.
 
 The following RPC methods take an Ethereum address parameter and are compatible with this type of allowlisting.
 
@@ -52,7 +53,8 @@ The following RPC methods take an Ethereum address parameter and are compatible
 
 #### Example request
 
-To allow a specific Ethereum address, click **ADD** and input it into the **CONTRACT ADDRESSES** allowlist.
+To allow a specific Ethereum address, input it into the **Contract Addresses** field and select **Add**.
+In the following example we'll use `0xfe05a3e72235c9f92fd9f2282f41a8154`.
 
 <div class="left-align-container">
   <div class="img-medium">
@@ -62,7 +64,7 @@ To allow a specific Ethereum address, click **ADD** and input it into the **CONT
   </div>
 </div>
 
-Test with a method from the list.
+You can test using a method that supports this type of allowlisting.
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -83,7 +85,7 @@ Result:
 
 ## User agents
 
-To limit access to your application to specific user agents, add them to the **USER AGENTS** allowlist.
+To limit access to your application to specific user agents, add them to the **User agents** allowlist.
 
 :::info
 
@@ -95,15 +97,15 @@ When you add a User-Agent to an allowlist, any API requests originating from oth
 
 :::info
 
-The **USER AGENTS** allowlist uses partial string matching. If the allowlisted string is present in the
-request's full User-Agent, it is registered as a match.
+The **User agents** allowlist uses partial string matching, meaning if the string is present in the
+request's full User-Agent, it's registered as a match.
 
 :::
 
 #### Example request
 
-For example, to allow requests from Android phones alone, select **ADD** and input `Android` into
-the **USER AGENTS** allowlist.
+For example, to allow requests from Android phones alone, input `Android` into
+the **User agent** field, and select **Add**.
 
 <div class="left-align-container">
   <div class="img-medium">
@@ -113,7 +115,7 @@ the **USER AGENTS** allowlist.
   </div>
 </div>
 
-Test with a simple call from a desktop terminal.
+Test with a call from a desktop terminal.
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -136,7 +138,7 @@ Result:
 
 ## Origins
 
-To limit access to your application to specific URLs, add them to the **ORIGINS** allowlist.
+To limit access to your application to specific URLs, add them to the **Origins** allowlist.
 
 :::info
 
@@ -148,7 +150,7 @@ When you add an origin to an allowlist, any API requests originating from other
 
 Origin allowlists support wildcard subdomain patterns.
 
-For example, allowlist entry `https://*.example.com` matches `https://your-app.example.com` ,
+For example, allowlist entry `https://*.example.com` matches `https://your-app.example.com`,
 `https://our-app.example.com`, and `https://their-app.example.com`, etc.
 
 The origin scheme (HTTPS in the example above) is optional. However, if you include it, it must match.
@@ -161,25 +163,14 @@ An entry with _only_ a scheme allows requests coming from that scheme alone.
 
 #### Example request
 
-To limit requests to your hosted web3 application, click **ADD** and input `mydapp.example.com` into the **ORIGINS** allowlist.
-
-Any requests that do not include `Origin: mydapp.example.com` are rejected.
+To limit requests to your hosted Web3 application, input `mydapp.example.com` into the **Origins**
+field, and select **Add**. Any requests that don't include `Origin: mydapp.example.com` are rejected.
 
 ## API request method
 
-To limit the methods allowed, add them to the **API REQUEST METHOD** allowlist.
-
-If the list is not empty, any method calls not specified in the list are rejected.
-
-Use the dropdown list to select a method.
+To limit the methods allowed, select them from the **API request method** drop down.
 
-<div class="left-align-container">
-  <div class="img-medium">
-    <img
-      src={require("../../../images/api-request-method.png").default}
-    />
-  </div>
-</div>
+If the list isn't empty, any method calls not specified in the list are rejected.
 
 ## Override your allowlist settings
 
@@ -188,7 +179,7 @@ This functionality is only available to customers on the Developer tier or highe
 [upgrade your plan](../upgrade-your-plan.md) if you're currently on the free Core tier.
 :::
 
-The **OVERIDE ALLOWLIST** switch lets you overide your allowlist settings when a request includes an
+The **OVERRIDE ALLOWLIST** switch lets you override your allowlist settings when a request includes an
 [API key secret](api-key-secret.md). This means requests will be accepted even if an IP address or
 URL isn't on your allowlist, provided they include both the API key and the API key secret.
 

developer-tools/dashboard/how-to/secure-an-api/use-jwts.md

@@ -4,9 +4,9 @@ description: Use JSON Web Tokens to authorize users and external parties.
 
 # JWTs
 
-Enable JSON Web Tokens (JWTs) for all requests in the **REQUIREMENTS** section of your API key's security settings.
+Enable JSON Web Tokens (JWTs) for all requests in the API key's **Settings** tab.
 
-Input the **JWT PUBLIC KEY NAME** and the key and select **ADD**.
+Input the **JWT Public key name** and the key and select **Add**.
 
 <div class="left-align-container">
   <div class="img-medium">