diff --git a/components/Search/docsearch.tsx b/components/Search/docsearch.tsx
index 2e826073d..902a5c34c 100644
--- a/components/Search/docsearch.tsx
+++ b/components/Search/docsearch.tsx
@@ -83,7 +83,7 @@ export function DocSearch({
           (e.metaKey /* for Mac */ || /* for non-Mac */ e.ctrlKey))
       ) {
         e.preventDefault();
-        // prevent to scroll to top
+        // prevent scrolling to the top
         input.current.focus({ preventScroll: true });
       } else if (e.key === "Escape") {
         setShow(false);
diff --git a/content/OpProposerDescriptionShort.md b/content/OpProposerDescriptionShort.md
index babd3da55..7e5339631 100644
--- a/content/OpProposerDescriptionShort.md
+++ b/content/OpProposerDescriptionShort.md
@@ -1 +1 @@
-`op-proposer` is the service that submits the output roots to the L1. This is to enable trustless execution of L2-to-L1 messaging and creates the view of the L2 state from the L1's perspective.
+`op-proposer` is the service that submits the output roots to the L1. This is to enable trustless execution of L2-to-L1 messaging and create the view of the L2 state from the L1's perspective.
diff --git a/notes/kapa-ai-assistant.md b/notes/kapa-ai-assistant.md
index a0c4999a7..0410f59ee 100644
--- a/notes/kapa-ai-assistant.md
+++ b/notes/kapa-ai-assistant.md
@@ -10,4 +10,4 @@ Currently the website has the modal enabled by a custom button component located
 
 ## Enabling/disabling the feature
 
-The kapa AI assistant con be toggled on and off on the website by toggling the **`enable_docs_ai_widget`** feature flag.
+The kapa AI assistant can be toggled on and off on the website by toggling the **`enable_docs_ai_widget`** feature flag.
diff --git a/pages/app-developers/transactions/statuses.mdx b/pages/app-developers/transactions/statuses.mdx
index ed635a400..de6dfa5de 100644
--- a/pages/app-developers/transactions/statuses.mdx
+++ b/pages/app-developers/transactions/statuses.mdx
@@ -11,7 +11,7 @@ Understanding these statuses can help you troubleshoot issues, build safer appli
 
 ## Pending
 
-**Instant after sending to Sequencer**
+**Instant after sending to the Sequencer**
 
 A transaction is considered "pending" when it has been sent to the Sequencer but has not yet been included in a block.
 This is the first status a transaction will have after being sent to the Sequencer.
diff --git a/pages/app-developers/tutorials/transactions/sdk-trace-txns.mdx b/pages/app-developers/tutorials/transactions/sdk-trace-txns.mdx
index 8bcbc4348..4da100c27 100644
--- a/pages/app-developers/tutorials/transactions/sdk-trace-txns.mdx
+++ b/pages/app-developers/tutorials/transactions/sdk-trace-txns.mdx
@@ -44,7 +44,7 @@ Since viem is a [Node.js](https://nodejs.org/en/) library, you'll need to create
 
 ## Add RPC URLs to your environment
 
-You'll be using the `getTransactionReceipt` function from the viem library during this tutorial. This function use event queries to retrieve the receipt for a deposit or withdrawal.
+You'll be using the `getTransactionReceipt` function from the viem library during this tutorial. This function uses event queries to retrieve the receipt for a deposit or withdrawal.
 Since this function uses large event queries, you'll need to use an RPC provider like [Alchemy](https://alchemy.com) that supports indexed event queries.
 Grab an L1 and L2 RPC URL for Sepolia and OP Sepolia, respectively.