Fix docs

notes/nextra.md

@@ -14,5 +14,5 @@ Remark plugins can be injected into Nextra by modifying the `mdxOptions` object
 
 #### remarkCodeImport
 
-Rule is modified via [patch](/patches/remark-code-import@1.2.0.patch) to require that all code imports include a md5 content hash of the imported content.
+Rule is modified via [patch](/patches/remark-code-import@1.2.0.patch) to require that all code imports include an md5 content hash of the imported content.
 Requiring this hash means that changes to the underlying content must also come with corresponding changes to the relevant imports and imports cannot silently break.

pages/builders/app-developers/bridging/messaging.mdx

@@ -220,7 +220,7 @@ We call this period of time the "challenge period" because it is the time during
 Optimistic Rollups are "optimistic" because they're based around the idea of publishing the *result* of a transaction to Ethereum without actually executing the transaction on Ethereum.
 In the "optimistic" case, this transaction result is correct and one can completely avoid the need to perform complicated (and expensive) logic on Ethereum.
 
-However, one still needs some way to prevent incorrect transaction results from being published in place of correct ones.
+However, one still needs to find a way to prevent incorrect transaction results from being published in place of correct ones.
 Here's where the "fault proof" comes into play.
 Whenever a transaction result is published, it's considered "pending" for a period of time known as the challenge period.
 During this period of time, anyone may re-execute the transaction *on Ethereum* in an attempt to demonstrate that the published result was incorrect.

pages/builders/app-developers/tutorials/cross-dom-solidity.mdx

@@ -95,7 +95,7 @@ Paste your address into the field next to the "greeting" function and click the
 You should see the message you sent from L1.
 
 <Callout>
-Don't see your message yet?
+Haven't seen your message yet?
 You might need to wait a little longer.
 L2 transactions triggered on L1 are typically processed within one minute but can occasionally be slightly delayed.
 </Callout>

pages/builders/app-developers/tutorials/deploy-for-free.mdx

@@ -27,7 +27,7 @@ This tutorial walks you through the process of verifying and deploying your cont
 
   ### Link your wallet on the Superchain Dev Console
 
-  *   Once you have your Coinbase Verification, go the [Superchain Developer Console](https://console.optimism.io/?utm_source=docs) and login with your preferred email.
+  *   Once you have your Coinbase Verification, go to the [Superchain Developer Console](https://console.optimism.io/?utm_source=docs) and login with your preferred email.
   *   Select the account drop down and click **Wallets**. Click **Link wallet**, and follow the connect wallet flow to link your public key that has a Coinbase Verification to associate your public key with your Superchain Developer Console login.
 
   ### Verify your contracts on the Superchain Dev Console