Various stylistic, grammatical and typographical errors in documentation (#1260)

* Spelling and syntax errors

* Typo

* Spelling

* typo
This commit is contained in:
zerod0t
2024-12-05 18:58:45 +02:00
committed by GitHub
parent 39c46133f3
commit 9a0007f5a2
3 changed files with 6 additions and 6 deletions

View File

@@ -93,7 +93,7 @@ Put `mintTo(address)` as the function to allowlist then click `Save` at the bott
![cdp-allowlist-contracts.png](../../assets/images/gasless-transaction-on-base/cdp-allowlist-contract.png)
:::note Use your own contract
You will be using this [simple NFT contract]deployed on Base mainnet for our example. Feel free to use a contract of your choice.
You will be using this [simple NFT contract] deployed on Base mainnet for our example. Feel free to use a contract of your choice.
:::
### Global & Per User Limits:
@@ -126,7 +126,7 @@ You will now test the policy that was created.
In this tutorial, You use foundry to create two key pairs that will allow us to create Smart Accounts that you will sponsor transactions on behalf of. You will **not** need to send any funds (ETH) to these wallets. You may use private keys of wallets you own as an alternative.
Foundry depends on Rust to work. If you do not have rust install:
Foundry depends on Rust to work. If you do not have rust installed:
```bash
curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
@@ -198,7 +198,7 @@ You will also need the address of the entrypoint contract for Base. A full list
Add the following to lines of code after your import statements:
```javascript
const rpcUrl = https://api.developer.coinbase.com/rpc/v1/base/<SPECIAL-KEY> //Paymaster & Bundler endpoint
const rpcUrl = 'https://api.developer.coinbase.com/rpc/v1/base/<SPECIAL-KEY>' //Paymaster & Bundler endpoint
```
```javascript
@@ -328,7 +328,7 @@ Feel free to use your own contract to interact with the Paymaster. For learning
You will be interacting with the NFT + ABI from a simple NFT contract deployed at: `0x83bd615eb93eE1336acA53e185b03B54fF4A17e8`
Copy and paste the NFT's abi into `index.js`
Copy and paste the NFT's ABI into `index.js`
```javascript
const abi = [

View File

@@ -96,7 +96,7 @@ You'll encounter providers divided into three general categories: Public Provide
Many tutorials and guides, including the getting started guide for [wagmi], use a _Public Provider_ as the default to get you up and running. Public means that they're open, permissionless, and free, so the guides will also usually warn you that you need to add another provider if you don't want to run into rate limiting. Listen to these warnings! The rate-limits of public providers are severe, and you'll start getting limited very quickly.
In wagmi, a public client is automatically included in the default confit. This client is just a wrapper setting up a [JSON RPC] provider using the `chain` and `rpcUrls` listed in Viem's directory of chain information. You can view the [data for Base Sepolia here].
In wagmi, a public client is automatically included in the default config. This client is just a wrapper setting up a [JSON RPC] provider using the `chain` and `rpcUrls` listed in Viem's directory of chain information. You can view the [data for Base Sepolia here].
Most chains will list this information in their docs as well. For example, on the network information pages for [Base] and [Optimism]. If you wanted, you could manually set up a `jsonRpcProvider` in wagmi using this information.

View File

@@ -106,7 +106,7 @@ You'll also want to keep track of addresses that have already minted, to prevent
:::danger
Make sure you added `.env.local` to ``.gitignore`! **If you don't do this you are going to expose your key and lose your wallet!**
Make sure you added `.env.local` to `.gitignore`! **If you don't do this you are going to expose your key and lose your wallet!**
:::