diff --git a/node-operators/guides/base-config.mdx b/node-operators/guides/base-config.mdx
index 83c717fe9..344dbb8e4 100644
--- a/node-operators/guides/base-config.mdx
+++ b/node-operators/guides/base-config.mdx
@@ -14,7 +14,7 @@ To configure your node, you will need to do the following:
 3.  Configure your execution client to properly communicate with the Rollup Node.
 4.  Optionally, configure Legacy Geth.
 
-## Configuring Your execution client
+## Configuring your execution client
 
 You can choose between two execution clients for your OP Stack rollup node: `op-geth` or `nethermind`. Each has its own configuration requirements and recommended settings.
 
@@ -53,7 +53,7 @@ to initialize the data directory:
 ```bash
 #!/bin/sh
 FILE=/$DATADIR/genesis.json
-OP_GETH_GENESIS_URL=<<insert op-geth url to the genesis file>>
+OP_GETH_GENESIS_URL=<<insert the op-geth URL to the genesis file>>
 
 if [ ! -s $FILE ]; then
   apk add curl
diff --git a/node-operators/guides/management/regenesis-history.mdx b/node-operators/guides/management/regenesis-history.mdx
index c8c864a63..73e530305 100644
--- a/node-operators/guides/management/regenesis-history.mdx
+++ b/node-operators/guides/management/regenesis-history.mdx
@@ -1,6 +1,6 @@
 ---
 title: Accessing pre-regenesis history
-description: Learn how to use access pre-regenesis history using the Etherscan CSV exporting tool.
+description: Learn how to access pre-regenesis history using the Etherscan CSV exporting tool.
 ---
 
 This tutorial explains how to access transaction history between 23 June 2021 and the final regenesis.
@@ -46,8 +46,8 @@ The transaction data for this period of time was published to a smart contract
 on Ethereum called the [CanonicalTransactionChain](https://etherscan.io/address/0x5e4e65926ba27467555eb562121fac00d24e9dd2).
 While it is theoretically possible to recover the data by downloading and
 re-executing this chain of transactions from Ethereum, this is a labor intensive
-and costly task that may not fully recover the data. The OP Labs's team did
-attempt data recover efforts, including reaching out to several partners.
+and costly task that may not fully recover the data. The OP Labs team did
+attempt data recovery efforts, including reaching out to several partners.
 
 ### Impact
 
diff --git a/node-operators/guides/management/snapshots.mdx b/node-operators/guides/management/snapshots.mdx
index 2b1a265b7..2989d8722 100644
--- a/node-operators/guides/management/snapshots.mdx
+++ b/node-operators/guides/management/snapshots.mdx
@@ -81,7 +81,7 @@ Nethermind provides an official snapshot through their snapshot service:
 ### OP Mainnet (archive node)
 
 <Info>
-  You can also download access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs\&utm_medium=docs) to find other snapshots.
+  You can also access the [Optimism Foundation datadir explorer](https://datadirs.optimism.io/?utm_source=op-docs\&utm_medium=docs) to find other snapshots.
 </Info>
 
 | Snapshot Date                 | Size | Download Link                                                                                                                                                                                    | sha256sum                                                                                       |
diff --git a/node-operators/tutorials/run-node-from-source.mdx b/node-operators/tutorials/run-node-from-source.mdx
index c099ed53c..214a553b3 100644
--- a/node-operators/tutorials/run-node-from-source.mdx
+++ b/node-operators/tutorials/run-node-from-source.mdx
@@ -258,7 +258,7 @@ Once you've started your execution client and `op-node` you should see them begi
 
     <Steps>
   <Step title="Downloading the headers">
-`op-geth` log something like this as it is downloading the headers:
+`op-geth` will log something like this as it is downloading the headers:
   
         ```text
         lvl=info msg="Syncing beacon headers" downloaded=116775778 left=1162878 eta=53.182s 
@@ -373,7 +373,7 @@ You should then also begin to see logs from your execution client:
 
 OP Mainnet underwent a large database migration as part of the [Bedrock Upgrade](https://web.archive.org/web/20230608050602/https://blog.oplabs.co/introducing-optimism-bedrock/) in 2023.
 You will need access to the migrated OP Mainnet database to run an archive node.
-You can [migrate your own data directory](https://web.archive.org/web/20240110231645/https://blog.oplabs.co/reproduce-bedrock-migration/) or simply download database that has already been migrated.
+You can [migrate your own data directory](https://web.archive.org/web/20240110231645/https://blog.oplabs.co/reproduce-bedrock-migration/) or simply download a database that has already been migrated.
 In this section, you'll learn how to download and verify the pre-migrated database.
 
 <Steps>