diff --git a/apps/base-docs/docs/building-with-base/guides/account-abstraction-with-biconomy.md b/apps/base-docs/docs/building-with-base/guides/account-abstraction-with-biconomy.md index 0221cf7513..0baaff5918 100644 --- a/apps/base-docs/docs/building-with-base/guides/account-abstraction-with-biconomy.md +++ b/apps/base-docs/docs/building-with-base/guides/account-abstraction-with-biconomy.md @@ -558,7 +558,7 @@ export default function Home() { Later in this guide, you will use the `provider` and user’s `smartAccount` to execute transactions on the deployed smart contract. Store the `provider` and `smartAccount` to React state so you can use it later. -To store the the `provider` and `smartAccount`, add the following code: +To store the `provider` and `smartAccount`, add the following code: ```javascript ... diff --git a/apps/base-docs/docs/building-with-base/guides/complex-onchain-nfts.md b/apps/base-docs/docs/building-with-base/guides/complex-onchain-nfts.md index e64e2cd4b0..bae80f7af5 100644 --- a/apps/base-docs/docs/building-with-base/guides/complex-onchain-nfts.md +++ b/apps/base-docs/docs/building-with-base/guides/complex-onchain-nfts.md @@ -228,7 +228,7 @@ contract SVGRenderer { } ``` -Open the exemplar SVG in a code editor, and using it as an example, build out a function that uses `abi.encodePacked` to build everything from the SVG **except** the actual art. That's much to big for one contract, so add stubs instead. +Open the exemplar SVG in a code editor, and using it as an example, build out a function that uses `abi.encodePacked` to build everything from the SVG **except** the actual art. That's much too big for one contract, so add stubs instead. Depending on the tool you used to make the SVG, there may be unneeded extras you can remove from these lines. You also **don't** need the items in `` or ``. You'll take advantage of the flexibility of the format to include those in the pieces returned by the supporting contract. @@ -596,7 +596,7 @@ function _buildOffsetValue( } ``` -This function uses hashing to create a psuedo-random number with the token id and stop as seeds, guaranteeing a consistent value, unique for each token and each stop within that token. It takes advantage of the way the offset property is interpreted - in this case, `".12+.20" == ".32"`. +This function uses hashing to create a pseudo-random number with the token id and stop as seeds, guaranteeing a consistent value, unique for each token and each stop within that token. It takes advantage of the way the offset property is interpreted - in this case, `".12+.20" == ".32"`. Finally, update your `render` function to call `_buildStop`: diff --git a/apps/base-docs/docs/building-with-base/guides/cross-chain-with-layerzero.md b/apps/base-docs/docs/building-with-base/guides/cross-chain-with-layerzero.md index 820e654667..cde4acd0fd 100644 --- a/apps/base-docs/docs/building-with-base/guides/cross-chain-with-layerzero.md +++ b/apps/base-docs/docs/building-with-base/guides/cross-chain-with-layerzero.md @@ -358,7 +358,7 @@ Overriding the `_lzReceive` function allows you to provide any custom logic you ### Final code -Once you complete all of the steps above, you're contract should look like this: +Once you complete all of the steps above, your contract should look like this: ```solidity // SPDX-License-Identifier: MIT @@ -653,7 +653,7 @@ You can view the status of your cross-chain transaction on [LayerZero Scan](http ### Receiving the message -Once the message has been sent and received on the destination chain,the \_Receive function will be called on the `ExampleContract` and the message payload will be stored in the contract's public `data` variable. +Once the message has been sent and received on the destination chain, the \_Receive function will be called on the `ExampleContract` and the message payload will be stored in the contract's public `data` variable. You can use the `cast` command to read the latest message received by the `ExampleContract` stored in the `data` variable. diff --git a/apps/base-docs/docs/building-with-base/guides/nft-minting-frame.md b/apps/base-docs/docs/building-with-base/guides/nft-minting-frame.md index 444a6ab266..6a81feeb60 100644 --- a/apps/base-docs/docs/building-with-base/guides/nft-minting-frame.md +++ b/apps/base-docs/docs/building-with-base/guides/nft-minting-frame.md @@ -89,7 +89,7 @@ The route: Currently, you can't get the user to authorize a transaction from a frame, so you'll have to foot the bill to do a mint. -Our strategy use the contract from the [Complex Onchain NFTs] guide, modified so that a designated address can mint for a provided address: +Our strategy uses the contract from the [Complex Onchain NFTs] guide, modified so that a designated address can mint for a provided address: ```solidity function mintFor(address _recipient) public onlyOwner { @@ -123,7 +123,7 @@ Create `.env.local` and add: Install dotenv with `yarn add dotenv`, then open `route.ts`. -Add a new image in the `public` folder. Per the [Frames] docs, images must be a 1.91 to 1 aspect ration. We used a grey-scale copy of the NFT, but others show the full image, or another call to action. +Add a new image in the `public` folder. Per the [Frames] docs, images must have a 1.91 to 1 aspect ratio. We used a grey-scale copy of the NFT, but others show the full image, or another call to action. For now, just use something you'll recognize as a placeholder.