Skip to content

Commit 0942eeb

Browse files
alexandratranbgravenorst
authored andcommitted
Vale fixes (#1716)
* Vale fixes * edits * edits * edits
1 parent e9388bf commit 0942eeb

File tree

711 files changed

+1093
-1029
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

711 files changed

+1093
-1029
lines changed

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

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -40,13 +40,13 @@ You can view your Web3 API usage stats in the following charts and tables.
4040

4141
### Requests Volume chart
4242

43-
This chart displays the total volume of requests sent to Infura using the selected API key(s) over
43+
This chart displays the total volume of requests sent to Infura using the selected API keys over
4444
the selected time period.
4545

4646
### Product Request Volumes
4747

4848
This chart displays the aggregate request volumes for the top five API methods called using the
49-
selected API key(s) over the selected time period.
49+
selected API keys over the selected time period.
5050
To view stats for a particular product (network) instead of the default of all products, make a
5151
selection from the products dropdown.
5252
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
5555
### Method Request Volumes
5656

5757
This chart displays the aggregate request volumes for requests made on the top five networks using
58-
the selected API key(s) over the selected time period.
58+
the selected API keys over the selected time period.
5959
To view stats for a particular method instead of the default of all methods, make a selection from
6060
the methods dropdown.
6161

6262
### Requests Activity
6363

6464
This table displays the total request volumes and successful and failed requests, based on each
65-
product (network) and method called using the selected API key(s) over the selected time period.
65+
product (network) and method called using the selected API keys over the selected time period.
6666

6767
For more details about the failure status codes, select the two diagonal arrows to the right of the
6868
**FAILED REQUESTS (%)** values.
@@ -72,7 +72,7 @@ requests, grouped by the returned status codes.
7272
### Eth_call activity
7373

7474
This table displays the activities made on the `eth_call` method, including contract addresses that
75-
interacted with the selected API key(s).
75+
interacted with the selected API keys.
7676
This table only shows the `eth_call` activity for the last 30 minutes, and is not impacted by any
7777
time period selection.
7878

@@ -85,15 +85,15 @@ You can view your IPFS usage stats in the following charts.
8585

8686
### Data Transfer Up
8787

88-
This chart displays the amount of data sent to the IPFS service using the selected API key(s) over
88+
This chart displays the amount of data sent to the IPFS service using the selected API keys over
8989
the selected time period.
9090

9191
### Data Transfer Down
9292

93-
This chart displays the amount of data retrieved from the IPFS service using the selected API key(s)
93+
This chart displays the amount of data retrieved from the IPFS service using the selected API keys
9494
over the selected time period.
9595

9696
### Total Storage
9797

98-
This chart displays the total amount of data stored by the selected API key(s) over the selected
98+
This chart displays the total amount of data stored by the selected API keys over the selected
9999
time period.

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ If your dapp operates solely on the client side without a server, use only the A
2222
The API key is exposed in client-side code, so you should secure it using [allowlists](use-an-allowlist.md).
2323

2424
:::tip
25-
For customers on the Developer tier or higher, Infura supports [overriding your allowlist](use-an-allowlist.md#overide-your-allowlist-settings)
25+
For customers on the Developer tier or higher, Infura supports [overriding your allowlist](use-an-allowlist.md#override-your-allowlist-settings)
2626
when you specify an API key secret. This allows you to apply the principle of least privilege on the
2727
client side while allowing unrestricted access on the server side.
2828
:::

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -23,6 +23,6 @@ Set rate limiting in the API key's **Settings** tab **Key Credit Limits** sectio
2323
The value `0` means default limits are applied.
2424

2525
- **PER DAY TOTAL CREDITS** restricts total daily credit usage for the API key. Set a limit on number of
26-
credits per day in integers, e.g. 20000. The value `0` means default limits are applied.
26+
credits per day in integers, for example, 20000. The value `0` means default limits are applied.
2727

2828
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -188,7 +188,7 @@ This functionality is only available to customers on the Developer tier or highe
188188
[upgrade your plan](../upgrade-your-plan.md) if you're currently on the free Core tier.
189189
:::
190190

191-
The **OVERIDE ALLOWLIST** switch lets you overide your allowlist settings when a request includes an
191+
The **OVERRIDE ALLOWLIST** switch lets you override your allowlist settings when a request includes an
192192
[API key secret](api-key-secret.md). This means requests will be accepted even if an IP address or
193193
URL isn't on your allowlist, provided they include both the API key and the API key secret.
194194

docs/whats-new.md

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,12 +11,17 @@ of the [MetaMask developer page](https://metamask.io/developer/).
1111

1212
## November 2024
1313

14+
- Added tutorial for
15+
[creating a simple Starknet dapp](/wallet/how-to/use-non-evm-networks/starknet/create-a-simple-starknet-dapp).
16+
([#1656](https://github.com/MetaMask/metamask-docs/pull/1656))
1417
- Documented Snaps [`Card`](/snaps/features/custom-ui/#card) and [`Section`](/snaps/features/custom-ui/#section) UI components.
15-
([#1707](https://github.com/MetaMask/metamask-docs/pull/1707)) ([#1700](https://github.com/MetaMask/metamask-docs/pull/1700))
18+
([#1707](https://github.com/MetaMask/metamask-docs/pull/1707) and
19+
[#1700](https://github.com/MetaMask/metamask-docs/pull/1700))
1620

1721
## October 2024
1822

19-
- Documented support for [non-EVM networks](/wallet/how-to/use-non-evm-networks), starting with [Starknet](/wallet/how-to/use-non-evm-networks/starknet). ([#1509](https://github.com/MetaMask/metamask-docs/pull/1509))
23+
- Documented support for [non-EVM networks](/wallet/how-to/use-non-evm-networks), starting with [Starknet](/wallet/how-to/use-non-evm-networks/starknet).
24+
([#1509](https://github.com/MetaMask/metamask-docs/pull/1509))
2025
- Documented [Scroll](/services/reference/scroll) support.
2126
([#1641](https://github.com/MetaMask/metamask-docs/pull/1641))
2227
- Updated [Wallet landing page](/wallet) and added [Connect to MetaMask](/wallet/connect) section

services/concepts/curl.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -52,15 +52,15 @@ Replace `<YOUR-API-KEY>` with a specific [API key](../../../developer-tools/dash
5252

5353
:::
5454

55-
#### -X flag
55+
#### `-X` flag
5656

5757
The `-X` flag specifies a common [HTTP method](https://www.w3schools.com/tags/ref_httpmethods.asp).
5858

5959
```bash
6060
-X POST \
6161
```
6262

63-
#### -H flag
63+
#### `-H` flag
6464

6565
The `-H` or `--header` flag specifies [header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers) information.
6666

@@ -70,7 +70,7 @@ The example specifies the `Content-Type` to be `application/json` which means th
7070
-H "Content-Type: application/json" \
7171
```
7272

73-
#### -d flag
73+
#### `-d` flag
7474

7575
The `-d` or `--data` flag specifies more information sent along with the curl request.
7676

services/concepts/gas.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ executing a smart contract or sending a transaction. To perform an action, users
1010
calculated based on the computational resources required for the action, and to compensate the miners who execute the
1111
request.
1212

13-
The amount paid is the units of gas consumed multiplied by the gas price. So for a network such as Ethereum, this is the
13+
The amount paid is the units of gas consumed multiplied by the gas price. For Ethereum, this is the
1414
amount of Ether a user is willing to pay for each unit of gas. The gas price is set by the user and is a key factor in
1515
determining the priority of their transaction relative to other transactions on the network.
1616

@@ -23,7 +23,8 @@ The Ethereum London hard fork update changed the blockchain’s transaction fee
2323
[EIP-1559](https://eips.ethereum.org/EIPS/eip-1559). This update changed the way users pay gas fees on the Ethereum
2424
network and other EVM chains.
2525

26-
Before EIP-1559, users specified a gas price, which was the amount they were willing to pay for a transaction to be mined. The auction-style system meant gas prices often fluctuated wildly. After EIP-1559, this has been replaced by two new values:
26+
Before EIP-1559, users specified a gas price, which was the amount they were willing to pay for a transaction to be mined.
27+
The auction-style system meant gas prices fluctuated often. After EIP-1559, this has been replaced by two new values:
2728

2829
- **Base fee**: The minimum transaction fee for every transaction to be included in a block. This is calculated by the network
2930
and is affected by the number of transactions included in the previous block. The base fee gets burned, meaning

services/concepts/transaction-types.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -46,4 +46,4 @@ They also contain a `maxPriorityFeePerGas` parameter, which specifies the maximu
4646

4747
An EIP-1559 transaction always pays the base fee of the block it’s included in, and it pays a priority fee as priced by `maxPriorityFeePerGas` or, if the base fee per gas + `maxPriorityFeePerGas` exceeds `maxFeePerGas`, it pays a priority fee as priced by `maxFeePerGas` minus the base fee per gas. The base fee is burned, and the priority fee is paid to the miner that included the transaction. A transaction’s priority fee per gas incentivizes miners to include the transaction over other transactions with lower priority fees per gas.
4848

49-
Read the [ConsenSys EIP-1559 primer](https://consensys.net/blog/quorum/what-is-eip-1559-how-will-it-change-ethereum/) for more information on how EIP-1559 changes Ethereum.
49+
Read the [Consensys EIP-1559 primer](https://consensys.net/blog/quorum/what-is-eip-1559-how-will-it-change-ethereum/) for more information on how EIP-1559 changes Ethereum.

services/concepts/websockets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,6 +100,6 @@ Additional credit-based charges are applied for the events returned:
100100
- `newHeads`: Each new block event consumes 50 credits from your daily quota. This event is triggered
101101
once per announced block.
102102
- `logs`: Depending on the filters applied, this event can consume 300 credits per block from your
103-
daily quota. At most, one event per announced block is charged, and potentially none if filter constraints are not met.
103+
daily quota. At most, one event per announced block is charged, or none if filter constraints are not met.
104104
- `newPendingTransaction`: An event is generated every 700-800ms, aggregating the total amount of
105105
pending transactions collected during that period. Each event consumes 200 credits from your daily quota.

services/get-started/infura.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -30,7 +30,7 @@ For more information refer to the [Infura pricing information](https://www.infur
3030
## 2. Configure your API key
3131

3232
After verification, you'll be directed to the [Infura dashboard](../../../developer-tools/dashboard) to configure your
33-
auto-generated API key.
33+
autogenerated API key.
3434

3535
Infura will automatically generate the **My First Key** API key.
3636

@@ -80,7 +80,7 @@ We recommend using Postman if you're a Windows user.
8080
Retrieve the current block number.
8181

8282
<Tabs>
83-
<TabItem value="cURL" label="cURL" default>
83+
<TabItem value="curl" label="curl" default>
8484

8585
```bash
8686
curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -122,7 +122,7 @@ Check the balance of an Ethereum smart contract.
122122
The example code checks the latest balance of the Ethereum Proof of Stake (PoS) contract.
123123

124124
<Tabs>
125-
<TabItem value="cURL" label="cURL" default>
125+
<TabItem value="curl" label="curl" default>
126126

127127
```bash
128128
curl https://mainnet.infura.io/v3/<YOUR-API-KEY> \
@@ -158,9 +158,9 @@ You'll receive a result similar to:
158158
{"jsonrpc": "2.0", "id": 1, "result": "0x96c8e932f1e499c855045"}
159159
```
160160

161-
This result is the hexadecimal value of the contract in Wei (the smallest denomination of Ether).
161+
This result is the hexadecimal value of the contract in wei (the smallest denomination of Ether).
162162

163-
The decimal conversion of the result is `11392978000069000000000069` Wei, which equals `11392978.000069000000000069` Ether.
163+
The decimal conversion of the result is `11392978000069000000000069` wei, which equals `11392978.000069000000000069` Ether.
164164

165165
## 4. Secure your API key
166166

0 commit comments

Comments
 (0)