diff --git a/.github/ISSUE_TEMPLATE/general_docs_request.md b/.github/ISSUE_TEMPLATE/general_docs_request.md
index c92562ffa..d8a9b499c 100644
--- a/.github/ISSUE_TEMPLATE/general_docs_request.md
+++ b/.github/ISSUE_TEMPLATE/general_docs_request.md
@@ -6,7 +6,7 @@ labels: 'community-request,documentation'
 
 ---
 
-<!-- please fill out the description and acceptance criteria to the best to your ability. While the other sections are optional, it makes resolving the issue much easier. -->
+<!-- please fill out the description and acceptance criteria to the best of your ability. While the other sections are optional, it makes resolving the issue much easier. -->
 
 ## Description 
 <!-- Write a clear and concise description of the docs request. For example, is the request related to an existing page or are you suggesting a brand-new docs page? -->
diff --git a/connect/contribute/stack-contribute.mdx b/connect/contribute/stack-contribute.mdx
index afd6d640d..7cf7d8911 100644
--- a/connect/contribute/stack-contribute.mdx
+++ b/connect/contribute/stack-contribute.mdx
@@ -18,7 +18,7 @@ To start contributing components to the stack, check out some of these [useful i
 
 The OP Stack codebase is not a product (in the traditional sense) but rather a collection of software components that power the Optimism ecosystem.
 If you'd like to contribute to the current release of OP Stack codebase, rather than creating new components, your contribution would be greatly appreciated.
-**A "Release"of the OP Stack codebase is a particular set of software components that are production-ready and which fit the stack's design principles and goals.**
+**A "Release" of the OP Stack codebase is a particular set of software components that are production-ready and which fit the stack's design principles and goals.**
 
 To make your first contribution to the codebase, check out the [open issues](https://github.com/ethereum-optimism/optimism/issues) on the Optimism Monorepo.
 
diff --git a/connect/resources/glossary.mdx b/connect/resources/glossary.mdx
index 38ecef4d4..19b6980b6 100644
--- a/connect/resources/glossary.mdx
+++ b/connect/resources/glossary.mdx
@@ -17,7 +17,7 @@ The glossary provides definitions of important terminology used throughout the O
 
 ### Address aliasing
 
-When a contract submits a [deposit](#deposit) from L1 to L2, it's address (as returned by `ORIGIN` and `CALLER`) will be
+When a contract submits a [deposit](#deposit) from L1 to L2, its address (as returned by `ORIGIN` and `CALLER`) will be
 aliased with a modified representation of the address of a contract.
 
 ### Block
@@ -235,7 +235,7 @@ An individual chain within the Optimism Superchain. All chains, regardless of th
 
 ### OP Mainnet
 
-Layer 2 blockchain powered by the OP Stack. Previously known as just "Optimism,"OP Mainnet is where it all started, and the first chain to commit to the Superchain vision.
+Layer 2 blockchain powered by the OP Stack. Previously known as just "Optimism," OP Mainnet is where it all started, and the first chain to commit to the Superchain vision.
 
 ### OP Stack
 
@@ -503,7 +503,7 @@ the [sequencer](#sequencer). These unsafe blocks will later need to be confirmed
 ### User-Deposited Transaction
 
 Deposited transaction which is derived from an L1 call to the deposit contract and [depositing call](#depositing-call); explicitly excludes [L1 attributes deposited
-transactions](#l1-attributes-depositedtransaction).
+transactions](#l1-attributes-deposited-transaction).
 
 ### Withdrawal transaction