edits

Author: alexandratran

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

@@ -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/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.
 :::

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

@@ -23,6 +23,6 @@ Set rate limiting in the API key's **Settings** tab **Key Credit Limits** sectio
     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.
+    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

@@ -188,7 +188,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.
 

services/get-started/infura.md

@@ -30,7 +30,7 @@ For more information refer to the [Infura pricing information](https://www.infur
 ## 2. Configure your API key
 
 After verification, you'll be directed to the [Infura dashboard](../../../developer-tools/dashboard) to configure your
-auto-generated API key.
+autogenerated API key.
 
 Infura will automatically generate the **My First Key** API key.
 
@@ -80,7 +80,7 @@ We recommend using Postman if you're a Windows user.
 Retrieve the current block number.
 
 <Tabs>
-  <TabItem value="cURL" label="cURL" default>
+  <TabItem value="curl" label="curl" default>
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -122,7 +122,7 @@ Check the balance of an Ethereum smart contract.
 The example code checks the latest balance of the Ethereum Proof of Stake (PoS) contract.
 
 <Tabs>
-  <TabItem value="cURL" label="cURL" default>
+  <TabItem value="curl" label="curl" default>
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -158,9 +158,9 @@ You'll receive a result similar to:
 {"jsonrpc": "2.0", "id": 1, "result": "0x96c8e932f1e499c855045"}
 ```
 
-This result is the hexadecimal value of the contract in Wei (the smallest denomination of Ether).
+This result is the hexadecimal value of the contract in wei (the smallest denomination of Ether).
 
-The decimal conversion of the result is `11392978000069000000000069` Wei, which equals `11392978.000069000000000069` Ether.
+The decimal conversion of the result is `11392978000069000000000069` wei, which equals `11392978.000069000000000069` Ether.
 
 ## 4. Secure your API key
 

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

@@ -42,7 +42,7 @@ Use [`eth_sendRawTransaction`](../reference/ethereum/json-rpc-methods/eth_sendra
 The JSON-RPC format expects `eth_sendRawTransaction` to have a specific data field format that requires normalizing the `Transfer` function to a short [function selector](https://solidity.readthedocs.io/en/develop/abi-spec.html#function-selector). To do this, set the parameters for the function and run it through Ethereum’s [sha3 keccak hash](https://solidity.readthedocs.io/en/develop/abi-spec.html#function-selector):
 
 <Tabs>
-  <TabItem value="Javascript" label="Javascript" default>
+  <TabItem value="JavaScript" label="JavaScript" default>
 
 ```javascript
 web3.sha3("Transfer(address, address, uint256)")[0..4]

services/reference/_partials/_eth_accounts-request.mdx

@@ -2,7 +2,7 @@ import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
 
 <Tabs>
-  <TabItem value="cURL">
+  <TabItem value="curl">
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \

services/reference/_partials/_eth_blobbasefee-request.mdx

@@ -2,7 +2,7 @@ import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
 
 <Tabs>
-  <TabItem value="cURL">
+  <TabItem value="curl">
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \

services/reference/_partials/_eth_blocknumber-request.mdx

@@ -2,7 +2,7 @@ import Tabs from "@theme/Tabs"
 import TabItem from "@theme/TabItem"
 
 <Tabs>
-  <TabItem value="cURL">
+  <TabItem value="curl">
 
 ```bash
 curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \

services/reference/_partials/_eth_call-parameters.mdx

@@ -2,8 +2,8 @@
 - `to`: 20 bytes - Address the transaction is directed to.
 - `gas`: Hexadecimal value of the gas provided for the transaction execution. `eth_call` consumes zero gas, but this parameter may be needed by some executions.
 - `gasPrice`: Hexadecimal value of the `gasPrice` used for each paid gas.
-- `maxPriorityFeePerGas`: Maximum fee, in Wei, the sender is willing to pay per gas above the base fee. See [EIP-1559 transactions](../../concepts/transaction-types.md#eip-1559-transactions).
-- `maxFeePerGas`: Maximum total fee (base fee + priority fee), in Wei, the sender is willing to pay per gas. See [EIP-1559 transactions](../../concepts/transaction-types.md#eip-1559-transactions).
+- `maxPriorityFeePerGas`: Maximum fee, in wei, the sender is willing to pay per gas above the base fee. See [EIP-1559 transactions](../../concepts/transaction-types.md#eip-1559-transactions).
+- `maxFeePerGas`: Maximum total fee (base fee + priority fee), in wei, the sender is willing to pay per gas. See [EIP-1559 transactions](../../concepts/transaction-types.md#eip-1559-transactions).
 - `value`: Hexadecimal of the value sent with this transaction.
 - `data`: Hash of the method signature and encoded parameters. See [Ethereum contract ABI specification](https://docs.soliditylang.org/en/latest/abi-spec.html).
 - `block parameter`: [_Required_] A hexadecimal block number, or one of the string tags `latest`, `earliest`, `pending`, `safe`, or `finalized`. See the [default block parameter](https://ethereum.org/en/developers/docs/apis/json-rpc/#default-block).