diff --git a/apps/base-docs/base-learn/docs/writing-to-contracts/useSimulateContract.md b/apps/base-docs/base-learn/docs/writing-to-contracts/useSimulateContract.md index 74b3272..51f87f7 100644 --- a/apps/base-docs/base-learn/docs/writing-to-contracts/useSimulateContract.md +++ b/apps/base-docs/base-learn/docs/writing-to-contracts/useSimulateContract.md @@ -20,7 +20,7 @@ By the end of this guide you should be able to: ## Refining the Claim Component -In the previous step-by-step, you used [`useWriteContract`] to set up a hook you can use to to call the `claim` function in your smart contract when the user clicks a button. The component works well enough, but it can take a long time for the wallet to pop up, particularly if there is network congestion. You also have no way of responding to a problem with the transaction inputs until after the user tries to initiate a transaction. +In the previous step-by-step, you used [`useWriteContract`] to set up a hook you can use to call the `claim` function in your smart contract when the user clicks a button. The component works well enough, but it can take a long time for the wallet to pop up, particularly if there is network congestion. You also have no way of responding to a problem with the transaction inputs until after the user tries to initiate a transaction. ### Using `useSimulateContract` diff --git a/apps/base-docs/docs/tools/node-providers.md b/apps/base-docs/docs/tools/node-providers.md index 0311f4b..d4f9335 100644 --- a/apps/base-docs/docs/tools/node-providers.md +++ b/apps/base-docs/docs/tools/node-providers.md @@ -246,7 +246,7 @@ hide_table_of_contents: true ## Unifra -[Unifra](https://base.unifra.io/) is a Web3 developer platform that provides tools, APIs, and node infrastructure, and provides access to Base nodes that are nodes are reliabile, scalable, and easy to use. +[Unifra](https://base.unifra.io/) is a Web3 developer platform that provides tools, APIs, and node infrastructure, and provides access to Base nodes that are nodes are reliable, scalable, and easy to use. #### Supported Networks diff --git a/apps/base-docs/tutorials/docs/2_9_2_thirdweb-unreal-nft-items.md b/apps/base-docs/tutorials/docs/2_9_2_thirdweb-unreal-nft-items.md index 5b06acd..203f244 100644 --- a/apps/base-docs/tutorials/docs/2_9_2_thirdweb-unreal-nft-items.md +++ b/apps/base-docs/tutorials/docs/2_9_2_thirdweb-unreal-nft-items.md @@ -358,7 +358,7 @@ Connect the output to the `Base Color` of `M_NFT_Color`, then save and close the Again in the content browser, right-click on the `M_NFT_Color` asset and select `Create Material Instance`. Name the instance `MI_NFT_Color`. -Navigate to the sports car mesh located in `VehicleTemplate>Blueprints>SportsCar` and double-click to to open the `SportsCar_pawn`. Select the `Mesh` from the `Components` tree and you should see the car in the editor. +Navigate to the sports car mesh located in `VehicleTemplate>Blueprints>SportsCar` and double-click to open the `SportsCar_pawn`. Select the `Mesh` from the `Components` tree and you should see the car in the editor. On the right side, change the `Element 2` material to `MI_NFT_Color`. The car is now bright red. Radical! Take your newly red car for a spin. diff --git a/apps/base-docs/tutorials/docs/4_account-abstraction-with-privy-and-base-paymaster.md b/apps/base-docs/tutorials/docs/4_account-abstraction-with-privy-and-base-paymaster.md index be82be3..1b1fd34 100644 --- a/apps/base-docs/tutorials/docs/4_account-abstraction-with-privy-and-base-paymaster.md +++ b/apps/base-docs/tutorials/docs/4_account-abstraction-with-privy-and-base-paymaster.md @@ -77,7 +77,7 @@ Onchain applications are difficult to use for many people, as they require a len For example,the preliminary steps a user needs to go through before they can use an onchain app are: -1. Create a wallet wallet (Coinbase Wallet, Metamask, etc) +1. Create a wallet (Coinbase Wallet, Metamask, etc) 1. Store the wallet mnemonic safely, without losing it or compromising it 1. Sign a slightly frightening message to connect to an onchain app 1. Try to do anything with the app and get a popup asking them to approve a transaction diff --git a/apps/base-docs/tutorials/docs/5_shopify-storefront-commerce.md b/apps/base-docs/tutorials/docs/5_shopify-storefront-commerce.md index dcbcf64..a6bea49 100644 --- a/apps/base-docs/tutorials/docs/5_shopify-storefront-commerce.md +++ b/apps/base-docs/tutorials/docs/5_shopify-storefront-commerce.md @@ -150,4 +150,4 @@ Remember to link "activate" your Coinbase Commerce plugin. You now have a custom store front with the products from your Shopify account. -In this tutorial, you learned how to to integrate Coinbase as a payment provider for your Shopify store. You've also learned how to use Hydrogen and Oxygen to create and deploy a version of your store separate from Shopify. +In this tutorial, you learned how to integrate Coinbase as a payment provider for your Shopify store. You've also learned how to use Hydrogen and Oxygen to create and deploy a version of your store separate from Shopify. diff --git a/apps/bridge/src/utils/hooks/useCCTPBridgeStatus.ts b/apps/bridge/src/utils/hooks/useCCTPBridgeStatus.ts index f9b105f..75264ff 100644 --- a/apps/bridge/src/utils/hooks/useCCTPBridgeStatus.ts +++ b/apps/bridge/src/utils/hooks/useCCTPBridgeStatus.ts @@ -99,7 +99,7 @@ export function useCCTPBridgeStatus({ // We still need to check whether or not the message was received on the other chain. // If it hasn't been received yet, the user needs to call receiveMessage on the MessageTransmitter. - // It it has been received, the bridge is complete. + // If it has been received, the bridge is complete. // We can check if the message has been received by simulating a call to receiveMessage. // If it fails, assume it's because the message has already been received. try {