diff --git a/docs/base-account/basenames/basename-transfer.mdx b/docs/base-account/basenames/basename-transfer.mdx
index cd92011d..36148d49 100644
--- a/docs/base-account/basenames/basename-transfer.mdx
+++ b/docs/base-account/basenames/basename-transfer.mdx
@@ -1,7 +1,7 @@
 ---
 title: Basename Transfer Guide
 slug: /basename-transfer
-description: 'Step-by-step guide for Base App users to transfer their Basenames to new a wallet addresses.'
+description: 'Step-by-step guide for Base App users to transfer their Basenames to new wallet addresses.'
 ---
 
 # Basename Transfer Guide
diff --git a/docs/base-account/guides/accept-payments.mdx b/docs/base-account/guides/accept-payments.mdx
index 588390ad..6c6d7467 100644
--- a/docs/base-account/guides/accept-payments.mdx
+++ b/docs/base-account/guides/accept-payments.mdx
@@ -133,7 +133,7 @@ export async function checkPayment(txId, testnet = false) {
     testnet  // Must match the testnet setting from the original pay() call
   });
   if (status.status === 'completed') {
-    // fulfil order
+    // fulfill order
   }
 }
 ```
@@ -179,4 +179,4 @@ If you intend on using the BasePayButton, please follow the [Brand Guidelines](/
 2. Pass <code>testnet: true</code> in your <code>pay()</code> and <code>getPaymentStatus()</code> calls.  
 3. Use <a href="https://sepolia.basescan.org" target="_blank">Sepolia BaseScan</a> to watch the transaction.
 
- 
\ No newline at end of file
+ 
diff --git a/docs/cookbook/introduction-to-mini-apps.mdx b/docs/cookbook/introduction-to-mini-apps.mdx
index 5105fe78..4e7eacec 100644
--- a/docs/cookbook/introduction-to-mini-apps.mdx
+++ b/docs/cookbook/introduction-to-mini-apps.mdx
@@ -5,9 +5,9 @@ description: Mini Apps represent a paradigm shift in application development and
 
 # Vibe Coding a Mini App
 
-In the following sections you will be guided through the best practices for vibe coding a mini app game starting with te fundamentals of prompting, what documentation to leverage, to deployment and posting.
+In the following sections you will be guided through the best practices for vibe coding a mini app game starting with the fundamentals of prompting, what documentation to leverage, to deployment and posting.
 
-Mini Apps are lightweight web applications that run across Farcaster clients like Farcaster and TBA. Posting your mini app and TBA will populate on Farcaster and visa versa
+Mini Apps are lightweight web applications that run across Farcaster clients like Farcaster and TBA. Posting your mini app and TBA will populate on Farcaster and vice versa
 
 # Introduction to Mini Apps
 
diff --git a/docs/cookbook/successful-miniapps-in-tba.mdx b/docs/cookbook/successful-miniapps-in-tba.mdx
index 5c936fa4..f9ce19d2 100644
--- a/docs/cookbook/successful-miniapps-in-tba.mdx
+++ b/docs/cookbook/successful-miniapps-in-tba.mdx
@@ -15,7 +15,7 @@ Mini Apps succeed when they create the smoothest possible user experience. **Min
 | Batched Transactions | Reduce interaction complexity     | Bundle related operations efficiently | Transaction completion rates |
 
 <Steps>
-  <Step title='Audit Connect Walet touchpoints'>
+  <Step title='Audit Connect Wallet touchpoints'>
     If you are using a custom wallet connection flow, you can replace it with
     MiniKit + Base Account.
   </Step>
@@ -24,11 +24,11 @@ Mini Apps succeed when they create the smoothest possible user experience. **Min
     align with Base UI patterns and speed up development.
   </Step>
   <Step title='Implement Paymaster'>
-    If you app requires a user to mint a NFT or submit a transaction onchain,
+    If your app requires a user to mint a NFT or submit a transaction onchain,
     ensure it is gasless by making that component interact with a Paymaster.
   </Step>
   <Step title='Use Batched Transactions'>
-    If you are using doing multiple transactions in a row, you can use batched
+    If you are doing multiple transactions in a row, you can use batched
     transactions to reduce the number of popups and approvals.
   </Step>
 </Steps>