Skip to content

Commit c71bd37

Browse files
authored
Merge pull request #797 from cratiu222/fix-docs
Fix docs
2 parents 2afdd3b + b111001 commit c71bd37

File tree

4 files changed

+4
-4
lines changed

4 files changed

+4
-4
lines changed

notes/nextra.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -14,5 +14,5 @@ Remark plugins can be injected into Nextra by modifying the `mdxOptions` object
1414

1515
#### remarkCodeImport
1616

17-
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.
17+
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.
1818
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -220,7 +220,7 @@ We call this period of time the "challenge period" because it is the time during
220220
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.
221221
In the "optimistic" case, this transaction result is correct and one can completely avoid the need to perform complicated (and expensive) logic on Ethereum.
222222

223-
However, one still needs some way to prevent incorrect transaction results from being published in place of correct ones.
223+
However, one still needs to find a way to prevent incorrect transaction results from being published in place of correct ones.
224224
Here's where the "fault proof" comes into play.
225225
Whenever a transaction result is published, it's considered "pending" for a period of time known as the challenge period.
226226
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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -95,7 +95,7 @@ Paste your address into the field next to the "greeting" function and click the
9595
You should see the message you sent from L1.
9696

9797
<Callout>
98-
Don't see your message yet?
98+
Haven't seen your message yet?
9999
You might need to wait a little longer.
100100
L2 transactions triggered on L1 are typically processed within one minute but can occasionally be slightly delayed.
101101
</Callout>

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

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ This tutorial walks you through the process of verifying and deploying your cont
2727

2828
### Link your wallet on the Superchain Dev Console
2929

30-
* Once you have your Coinbase Verification, go the [Superchain Developer Console](https://console.optimism.io/?utm_source=docs) and login with your preferred email.
30+
* 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.
3131
* 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.
3232

3333
### Verify your contracts on the Superchain Dev Console

0 commit comments

Comments
 (0)