Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Updating Old wip callout to the new callout #775

Merged
merged 1 commit into from
Jun 28, 2024

Conversation

brokewhale
Copy link
Contributor

Description

Replaced the old callout for the new ones

Before

image

After (and it sticks to the top when scrolling aswell)

image

Let me know if you want both callouts to be there or just one callout

@brokewhale brokewhale requested a review from a team as a code owner June 28, 2024 10:24
@brokewhale brokewhale requested a review from a team June 28, 2024 10:24
Copy link
Contributor

coderabbitai bot commented Jun 28, 2024

Walkthrough

This update primarily focuses on removing maintenance warnings and error callouts from multiple tutorial pages and replacing them with a consistent "work-in-progress" message through a new WipCallout component. It also includes a minor update to a text file by removing the term Routescan and adding rollups.

Changes

Files (Grouped) Change Summary
…/tutorials/cross-dom-bridge-erc20.mdx Removed maintenance warning and adjusted content layout by removing a callout.
…/tutorials/cross-dom-bridge-eth.mdx, …/cross-dom-solidity.mdx Replaced error callout section with imported WipCallout component and rendered it.
…/tutorials/sdk-estimate-costs.mdx Replaced callout component with WipCallout for WIP indication.
…/tutorials/sdk-trace-txns.mdx Replaced <Callout> with <WipCallout>, removed maintenance content.
…/tutorials/sdk-view-txns.mdx Replaced Callout with WipCallout, removed warning message.
…/tutorials/send-tx-from-eth.mdx Replaced Callout with WipCallout, removed maintenance content.
…/tutorials/standard-bridge-custom-token.mdx Replaced informational callout with WipCallout.
…/tutorials/standard-bridge-standard-token.mdx Removed introductory callout section, added WipCallout.
…/tutorials/create-l2-rollup.mdx Updated imports and replaced error callout with WipCallout, retained informational callout.
…/tutorials/sdk.mdx Removed error callout, added WipCallout component.
words.txt Removed Routescan, added rollups.

Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between f52fb27 and e064639.

Files selected for processing (12)
  • pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/cross-dom-solidity.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/sdk-trace-txns.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/sdk-view-txns.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/send-tx-from-eth.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx (1 hunks)
  • pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx (1 hunks)
  • pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (1 hunks)
  • pages/builders/chain-operators/tutorials/sdk.mdx (1 hunks)
  • words.txt (1 hunks)
Files not reviewed due to errors (2)
  • pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx (no review received)
  • pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx (no review received)
Additional context used
Path-based instructions (11)
pages/builders/chain-operators/tutorials/sdk.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/sdk-view-txns.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/send-tx-from-eth.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/sdk-trace-txns.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/app-developers/tutorials/cross-dom-solidity.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (1)

Pattern **/*.mdx: "ALWAYS review Markdown content THOROUGHLY with the following criteria:

  • Use proper nouns in place of personal pronouns like 'We' and 'Our' to maintain consistency in communal documentation.
  • Avoid gender-specific language and use the imperative form.
  • Monitor capitalization for emphasis. Use bold for prominence instead of all caps or italics.
  • Ensure proper nouns are capitalized in sentences.
  • Apply the Oxford comma.
  • Use proper title case for headers, buttons, tab names, page names, and links. Sentence case should be used for body content and short phrases, even in links.
  • Use correct spelling and grammar at all times (IMPORTANT).
    "
LanguageTool
words.txt

[duplication] ~1-~1: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ACCOUNTQUEUE accountqueue ACCOUNTSLOTS accountslots ADDI ADDIU AD...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~2-~2: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ACCOUNTQUEUE accountqueue ACCOUNTSLOTS accountslots ADDI ADDIU ADDU airgap Allocs allocs AN...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~8-~8: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...OTS accountslots ADDI ADDIU ADDU airgap Allocs allocs ANDI Apeworx Arweave authrpc Badgeholde...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~23-~23: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...GTZ Biconomy birthdate BLEZ BLOBBASEFEE BLOBPOOL blobpool blobspace blockhash blocklists BLOCKLOG...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~28-~28: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...blobpool blobspace blockhash blocklists BLOCKLOGS blocklogs BLOCKPROFILERATE blockprofilerate Block...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~30-~30: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...lockhash blocklists BLOCKLOGS blocklogs BLOCKPROFILERATE blockprofilerate Blockscout blocktime BLOOMFILTER bloomf...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~34-~34: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...E blockprofilerate Blockscout blocktime BLOOMFILTER bloomfilter BLTZ Bluesweep Bootcamp BOOTNODES Bootn...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~39-~39: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...TER bloomfilter BLTZ Bluesweep Bootcamp BOOTNODES Bootnodes bootnodes bottlenecked Brotli brotli Ca...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~43-~43: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...TNODES Bootnodes bootnodes bottlenecked Brotli brotli Callouts callouts CCIP Celestia Celesti...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~45-~45: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...es bootnodes bottlenecked Brotli brotli Callouts callouts CCIP Celestia Celestia's Chainlink chai...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~48-~48: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ed Brotli brotli Callouts callouts CCIP Celestia Celestia's Chainlink chainlist Chainstack chaosn...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~58-~58: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...t Clabby codebases collateralized compr COMPUTEPENDINGBLOCK computependingblock confs corsdomain counterfactually Cross...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~64-~64: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...s corsdomain counterfactually Crossmint DATACAP datacap DATADIR datadir Dencun derviation Devne...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~66-~66: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...nterfactually Crossmint DATACAP datacap DATADIR datadir Dencun derviation Devnet devnet Devnode...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~70-~70: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...tacap DATADIR datadir Dencun derviation Devnet devnet Devnode direnv DISABLETXPOOLGOSSIP disa...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~74-~74: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...derviation Devnet devnet Devnode direnv DISABLETXPOOLGOSSIP disabletxpoolgossip Discv discv DIVU Drand Eigen ENABLEDEPR...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~76-~76: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...DISABLETXPOOLGOSSIP disabletxpoolgossip Discv discv DIVU Drand Eigen ENABLEDEPRECATEDPERSON...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~81-~81: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...poolgossip Discv discv DIVU Drand Eigen ENABLEDEPRECATEDPERSONAL enabledeprecatedpersonal enablements Erigon erigon ETHERBASE eth...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~84-~84: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...AL enabledeprecatedpersonal enablements Erigon erigon ETHERBASE etherbase ETHSTATS ethstats E...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~86-~86: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...catedpersonal enablements Erigon erigon ETHERBASE etherbase ETHSTATS ethstats EVMTIMEOUT evmtimeout...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~88-~88: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ments Erigon erigon ETHERBASE etherbase ETHSTATS ethstats EVMTIMEOUT evmtimeout EXITWHENSYNCED ex...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~90-~90: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...n ETHERBASE etherbase ETHSTATS ethstats EVMTIMEOUT evmtimeout EXITWHENSYNCED exitwhensynced EXTRADATA...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~92-~92: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ETHSTATS ethstats EVMTIMEOUT evmtimeout EXITWHENSYNCED exitwhensynced EXTRADATA extradata Farcaster farcaster...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~94-~94: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...vmtimeout EXITWHENSYNCED exitwhensynced EXTRADATA extradata Farcaster farcaster Fastnode FDLIMIT fd...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~96-~96: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...NCED exitwhensynced EXTRADATA extradata Farcaster farcaster Fastnode FDLIMIT fdlimit featureset for...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~99-~99: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... extradata Farcaster farcaster Fastnode FDLIMIT fdlimit featureset forkable forkchoice FPVM FPV...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~108-~108: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ble forkchoice FPVM FPVMs Fraxtal Funct GASCAP gascap gaslessly GCMODE gcmode Gelato gifs GLO...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~111-~111: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...s Fraxtal Funct GASCAP gascap gaslessly GCMODE gcmode Gelato gifs GLOBALQUEUE globalqueue GLO...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~115-~115: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...cap gaslessly GCMODE gcmode Gelato gifs GLOBALQUEUE globalqueue GLOBALSLOTS globalslots gokzg growthepi...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~117-~117: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ode Gelato gifs GLOBALQUEUE globalqueue GLOBALSLOTS globalslots gokzg growthepie hardfork hardforks HEA...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~123-~123: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ots gokzg growthepie hardfork hardforks HEALTHCHECK healthcheck heartbeating HISTORICALRPC historicalrp...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~126-~126: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ks HEALTHCHECK healthcheck heartbeating HISTORICALRPC historicalrpc HISTORICALRPCTIMEOUT historicalrpctimeo...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~128-~128: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...eartbeating HISTORICALRPC historicalrpc HISTORICALRPCTIMEOUT historicalrpctimeout HOLESKY Holesky holesky IGNOREPRICE ign...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~130-~130: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...STORICALRPCTIMEOUT historicalrpctimeout HOLESKY Holesky holesky IGNOREPRICE ignoreprice implici...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~133-~133: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ricalrpctimeout HOLESKY Holesky holesky IGNOREPRICE ignoreprice implicity Inator inator INFLUXDBV influ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~136-~136: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...lesky IGNOREPRICE ignoreprice implicity Inator inator INFLUXDBV influxdbv initcode IPCDISABLE...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~138-~138: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ICE ignoreprice implicity Inator inator INFLUXDBV influxdbv initcode IPCDISABLE ipcdisable ipcfile ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~141-~141: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...tor inator INFLUXDBV influxdbv initcode IPCDISABLE ipcdisable ipcfile IPCPATH ipcpath IPFS ipfs JALR ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~144-~144: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... initcode IPCDISABLE ipcdisable ipcfile IPCPATH ipcpath IPFS ipfs JALR JOURNALREMOTES journalre...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~146-~146: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ABLE ipcdisable ipcfile IPCPATH ipcpath IPFS ipfs JALR JOURNALREMOTES journalremotes JSPA...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~149-~149: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... ipcfile IPCPATH ipcpath IPFS ipfs JALR JOURNALREMOTES journalremotes JSPATH jspath jwtsecret Keccak leveldb ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~151-~151: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ipfs JALR JOURNALREMOTES journalremotes JSPATH jspath jwtsecret Keccak leveldb lightkdf logfi...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~159-~159: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... Keccak leveldb lightkdf logfile logfmt MAXAGE maxage MAXBACKUPS maxbackups MAXPEERS maxpeers...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~161-~161: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...b lightkdf logfile logfmt MAXAGE maxage MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendp...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~163-~163: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...fmt MAXAGE maxage MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxp...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~165-~165: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...MAXBACKUPS maxbackups MAXPEERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxprice MCOPY MEMPROFILERATE ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~167-~167: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...EERS maxpeers MAXPENDPEERS maxpendpeers MAXPRICE maxprice MCOPY MEMPROFILERATE memprofilerate Mer...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~170-~170: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...RS maxpendpeers MAXPRICE maxprice MCOPY MEMPROFILERATE memprofilerate Merkle merkle MFHI MFLO MINFREEDISK min...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~172-~172: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ice MCOPY MEMPROFILERATE memprofilerate Merkle merkle MFHI MFLO MINFREEDISK minfreedisk MINSU...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~176-~176: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... memprofilerate Merkle merkle MFHI MFLO MINFREEDISK minfreedisk MINSUGGESTEDPRIORITYFEE minsuggestedpri...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~178-~178: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...erkle MFHI MFLO MINFREEDISK minfreedisk MINSUGGESTEDPRIORITYFEE minsuggestedpriorityfee Mintable Mintplex MIPSEVM Moralis Mordo...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~195-~195: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...LT multiaddr multisigs MULTU nethermind NETRESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpaylo...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~197-~197: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ULTU nethermind NETRESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpayload nextra NOCOMPACTI...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~199-~199: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ESTRICT netrestrict NETWORKID networkid NEWPAYLOAD newpayload nextra NOCOMPACTION nocompaction NODEKE...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~202-~202: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... networkid NEWPAYLOAD newpayload nextra NOCOMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex n...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~204-~204: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ayload nextra NOCOMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex nodename NODISCOV...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~206-~206: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...COMPACTION nocompaction NODEKEY nodekey NODEKEYHEX nodekeyhex nodename NODISCOVER nodiscover NOLOCALS...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~209-~209: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... nodekey NODEKEYHEX nodekeyhex nodename NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~211-~211: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...dekeyhex nodename NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruni...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~213-~213: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...NODISCOVER nodiscover NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncs...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~215-~215: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...NOLOCALS nolocals NOPREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncserve Numba Offchain ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~217-~217: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...PREFETCH noprefetch NOPRUNING nopruning NOSYNCSERVE nosyncserve Numba Offchain offchain oplabs opnode's...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~220-~220: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...nopruning NOSYNCSERVE nosyncserve Numba Offchain offchain oplabs opnode's Opti pausable pcscdpath...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~227-~227: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...oplabs opnode's Opti pausable pcscdpath Peerstore peerstore peerstores Permissioned permissioned Pe...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~230-~230: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...cscdpath Peerstore peerstore peerstores Permissioned permissioned Permissionless permissionless permissio...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~232-~232: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...re peerstores Permissioned permissioned Permissionless permissionless permissionlessly Perps personhood Pimli...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~240-~240: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...sly Perps personhood Pimlico POAP POAPs PPROF pprof preconfigured predeploy Predeployed pre...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~244-~244: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...APs PPROF pprof preconfigured predeploy Predeployed predeployed predeploys Preimage preimage PREIMAGES ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~247-~247: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ploy Predeployed predeployed predeploys Preimage preimage PREIMAGES preimages Preinstalls preinst...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~249-~249: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...redeployed predeploys Preimage preimage PREIMAGES preimages Preinstalls preinstalls Prestate presta...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~251-~251: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...s Preimage preimage PREIMAGES preimages Preinstalls preinstalls Prestate prestate prestates PRICEBUMP p...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~253-~253: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...MAGES preimages Preinstalls preinstalls Prestate prestate prestates PRICEBUMP pricebump PRICELIMI...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~256-~256: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...preinstalls Prestate prestate prestates PRICEBUMP pricebump PRICELIMIT pricelimit productionize pro...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~258-~258: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... prestate prestates PRICEBUMP pricebump PRICELIMIT pricelimit productionize productionized Protip pro...

(GERMAN_WORD_REPEAT_RULE)


[style] ~263-~263: Möchten Sie die modernere Schreibweise „proxid“ verwenden?
Context: ...mit productionize productionized Protip proxyd pseudorandomly QRNG Quicknode quicknode...

(I_ANSTATT_Y)


[duplication] ~266-~266: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...nized Protip proxyd pseudorandomly QRNG Quicknode quicknode quickstarts RANDAO Regenesis regenesis ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~270-~270: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... Quicknode quicknode quickstarts RANDAO Regenesis regenesis REJOURNAL rejournal REMOTEDB remotedb r...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~272-~272: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... quickstarts RANDAO Regenesis regenesis REJOURNAL rejournal REMOTEDB remotedb replayability reprove...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~274-~274: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...Regenesis regenesis REJOURNAL rejournal REMOTEDB remotedb replayability reproven REQUIREDBLOCKS r...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~278-~278: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...EMOTEDB remotedb replayability reproven REQUIREDBLOCKS requiredblocks Rollouts Rollups rollups Routescan rpck...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~281-~281: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... REQUIREDBLOCKS requiredblocks Rollouts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix r...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~285-~285: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...louts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix rpcs RPGF Rpgf rpgf RWAs Schnorr secp S...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~288-~288: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...tescan rpckind RPCPREFIX rpcprefix rpcs RPGF Rpgf rpgf RWAs Schnorr secp SELFDESTRUCT seq...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~296-~296: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...gf RWAs Schnorr secp SELFDESTRUCT seqnr SEQUENCERHTTP sequencerhttp serv Shapella signup SLLV SLTI SLTIU SL...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~312-~312: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...log soulbound soyboy spacebar SRAV SRLV Stablecoins stablecoins subcomponents subgame subheaders SUBU S...

(GERMAN_WORD_REPEAT_RULE)


[uncategorized] ~318-~318: Hier werden zwei Wörter wiederholt. Meinten Sie „SUPERCHAIN Superchain“?
Context: ...s subcomponents subgame subheaders SUBU SUPERCHAIN Superchain superchain Superchain's Superchains Superscan SYNCMODE syncmo...

(DE_PHRASE_REPETITION)


[duplication] ~324-~324: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...hain Superchain's Superchains Superscan SYNCMODE syncmode SYNCTARGET synctarget syscalls therealb...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~326-~326: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...Superchains Superscan SYNCMODE syncmode SYNCTARGET synctarget syscalls therealbytes threadcreate tili...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~337-~337: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...ies trustlessly trustrpc txfeecap txmgr TXPOOL txpool uncountered Unprotect unsubmitted UPNP ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~343-~343: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... uncountered Unprotect unsubmitted UPNP VERKLE verkle Vetoable VHOSTS vhosts Viem viem VMDEBU...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~346-~346: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...unsubmitted UPNP VERKLE verkle Vetoable VHOSTS vhosts Viem viem VMDEBUG vmdebug VMODULE vmodu...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~348-~348: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...NP VERKLE verkle Vetoable VHOSTS vhosts Viem viem VMDEBUG vmdebug VMODULE vmodule wagmi X...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~350-~350: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...verkle Vetoable VHOSTS vhosts Viem viem VMDEBUG vmdebug VMODULE vmodule wagmi XORI xtensibility...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~352-~352: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...VHOSTS vhosts Viem viem VMDEBUG vmdebug VMODULE vmodule wagmi XORI xtensibility ZKPs ZKVM Zora ...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~359-~359: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...odule wagmi XORI xtensibility ZKPs ZKVM Zora zora

(GERMAN_WORD_REPEAT_RULE)

pages/builders/chain-operators/tutorials/sdk.mdx

[uncategorized] ~16-~16: Possible missing comma found.
Context: ...sm SDK natively supports various OP Chains including OP Mainnet and Base. To check...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~32-~32: Consider a shorter alternative to avoid wordiness.
Context: ...ts that are part of your OP Stack chain in order to use the Optimism SDK. If you followed t...

(IN_ORDER_TO_PREMIUM)


[uncategorized] ~94-~94: Possible missing comma found.
Context: ...ith the Optimism SDK. To start the Node REPL run the following command in your termi...

(AI_HYDRA_LEO_MISSING_COMMA)

pages/builders/app-developers/tutorials/sdk-view-txns.mdx

[style] ~15-~15: Consider removing “of” to be more concise
Context: ...m SDK](https://sdk.optimism.io) to view all of the [Standard Bridge](../bridging/standard-...

(ALL_OF_THE)


[style] ~144-~144: Consider removing “of” to be more concise
Context: ...ry for Deposits You'll first query for all of the deposits made by the target address. Th...

(ALL_OF_THE)


[style] ~163-~163: Consider removing “of” to be more concise
Context: ... for Withdrawals You'll next query for all of the withdrawals made by the target address....

(ALL_OF_THE)

pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx

[typographical] ~15-~15: It appears that a comma is missing.
Context: ...en Using the Standard Bridge In this tutorial you'll learn how to bridge a standard E...

(DURING_THAT_TIME_COMMA)


[style] ~30-~30: Consider a shorter alternative to avoid wordiness.
Context: ... contract must implement this interface in order to be bridged using the Standard Bridge sy...

(IN_ORDER_TO_PREMIUM)


[style] ~62-~62: Consider a shorter alternative to avoid wordiness.
Context: ...onment} You'll need a private key in order to sign transactions. Set your private key...

(IN_ORDER_TO_PREMIUM)


[style] ~72-~72: Consider a shorter alternative to avoid wordiness.
Context: ...vironment} You'll need an RPC URL in order to connect to OP Sepolia. Set your RPC URL...

(IN_ORDER_TO_PREMIUM)


[style] ~80-~80: Consider a shorter alternative to avoid wordiness.
Context: ...now the address of your L1 ERC-20 token in order to create a bridged representation of it o...

(IN_ORDER_TO_PREMIUM)

pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx

[typographical] ~15-~15: It appears that a comma is missing.
Context: ...en Using the Standard Bridge In this tutorial you'll learn how to bridge a custom ERC...

(DURING_THAT_TIME_COMMA)


[style] ~30-~30: Consider a shorter alternative to avoid wordiness.
Context: ... contract must implement this interface in order to be bridged using the Standard Bridge sy...

(IN_ORDER_TO_PREMIUM)


[style] ~51-~51: Consider a shorter alternative to avoid wordiness.
Context: ...d the OP Sepolia network to your wallet in order to follow this tutorial. You can use [this...

(IN_ORDER_TO_PREMIUM)


[style] ~121-~121: Consider an alternative for the overused word “exactly”.
Context: ...for the token you just created! This is exactly what this tutorial was meant to demonst...

(EXACTLY_PRECISELY)

pages/builders/app-developers/tutorials/send-tx-from-eth.mdx

[uncategorized] ~17-~17: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short).
Context: ... their highly decentralized counterparts but they are also more vulnerable to potent...

(COMMA_COMPOUND_SENTENCE)


[typographical] ~23-~23: It appears that a comma is missing.
Context: ...ing a transaction on Ethereum. In this tutorial you'll learn how to trigger a transacti...

(DURING_THAT_TIME_COMMA)


[style] ~88-~88: Consider a shorter alternative to avoid wordiness.
Context: ...our Environment You need a private key in order to sign transactions. Set your private key...

(IN_ORDER_TO_PREMIUM)


[typographical] ~170-~170: Consider inserting a comma for improved readability.
Context: ...ctions via the OptimismPortal contract it's important to always include a gas buf...

(INITIAL_ADVP_COMMA)

pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx

[style] ~69-~69: Consider a shorter alternative to avoid wordiness.
Context: ...will need to get some ETH on OP Sepolia in order to run the code in this tutorial. <Callou...

(IN_ORDER_TO_PREMIUM)


[style] ~77-~77: Consider a shorter alternative to avoid wordiness.
Context: ...our Environment You need a private key in order to sign transactions. Set your private key...

(IN_ORDER_TO_PREMIUM)

pages/builders/app-developers/tutorials/sdk-trace-txns.mdx

[uncategorized] ~183-~183: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...arch for Mint events to determine the amount of tokens that were minted as a result ...

(AMOUNTOF_TO_NUMBEROF)


[uncategorized] ~220-~220: ‘Amount of’ should usually only be used with uncountable or mass nouns. Consider using “number” if this is not the case.
Context: ...arch for Burn events to determine the amount of tokens that were burned as a result ...

(AMOUNTOF_TO_NUMBEROF)

pages/builders/app-developers/tutorials/cross-dom-bridge-eth.mdx

[style] ~21-~21: Consider using an alternative to strengthen your wording.
Context: ...lopers/bridging/standard-bridge) if you want to learn more about how the bridge work...

(WANT_KEEN)


[style] ~27-~27: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... included in the SDK by default. If you want to use a network that isn't included by de...

(REP_WANT_TO_VB)


[uncategorized] ~27-~27: Possible missing comma found.
Context: ...to use a network that isn't included by default you can simply [instantiate the SDK wit...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~83-~83: Consider a shorter alternative to avoid wordiness.
Context: ...our Environment You need a private key in order to sign transactions. Set your private key...

(IN_ORDER_TO_PREMIUM)


[uncategorized] ~146-~146: Possible missing comma found.
Context: ...osit ETH Now that you have some ETH on L1 you can deposit that ETH into the `L1St...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~248-~248: The preposition ‘to’ seems more likely in this position.
Context: ...rom L2 to L1 is to relay the withdrawal on L1. This can only happen after the faul...

(AI_HYDRA_LEO_REPLACE_ON_TO)


[uncategorized] ~261-~261: Possible missing comma found.
Context: ...3>} Once the withdrawal is ready to be relayed you can finally complete the withdrawal...

(AI_HYDRA_LEO_MISSING_COMMA)

pages/builders/app-developers/tutorials/cross-dom-bridge-erc20.mdx

[style] ~21-~21: Consider using an alternative to strengthen your wording.
Context: ...lopers/bridging/standard-bridge) if you want to learn more about how the bridge work...

(WANT_KEEN)


[style] ~34-~34: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... included in the SDK by default. If you want to use a network that isn't included by de...

(REP_WANT_TO_VB)

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

[grammar] ~16-~16: The expression “vice versa” is spelled without hyphens.
Context: ...variable on a contract on Ethereum, and vice-versa. This is a simple example, but the same...

(VICE_VERSA)


[style] ~55-~55: ‘exactly the same’ might be wordy. Consider a shorter alternative.
Context: ...7bc9769f3055#code). Both contracts have exactly the same source code. Feel free to review the s...

(EN_WORDINESS_PREMIUM_EXACTLY_THE_SAME)


[style] ~56-~56: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...cts have exactly the same source code. Feel free to review the source code for these two co...

(FEEL_FREE_TO_STYLE_ME)


[style] ~81-~81: The phrase ‘feel free to’ is used quite frequently. Consider using a less frequent alternative to set your writing apart from others and make it sound more professional.
Context: ...w minutes for your message to reach L2. Feel free to take a quick break while you wait. <Ca...

(FEEL_FREE_TO_STYLE_ME)


[style] ~166-~166: Consider a shorter alternative to avoid wordiness.
Context: ...vironment} You need a private key in order to sign transactions. Set your private key...

(IN_ORDER_TO_PREMIUM)


[style] ~287-~287: ‘exactly the same’ might be wordy. Consider a shorter alternative.
Context: .... Luckily, both Greeter contracts are exactly the same so it's easy to see how everything come...

(EN_WORDINESS_PREMIUM_EXACTLY_THE_SAME)


[grammar] ~300-~300: The expression “vice versa” is spelled without hyphens.
Context: ...dress of the L2 Greeter contract, and vice-versa. ```solidity file=/public/tut...

(VICE_VERSA)


[style] ~355-~355: The phrase “a variety of” may be wordy. To make your writing clearer, consider replacing it.
Context: ...cross-chain communication is useful for a variety of reasons. For example, the [Standard Bri...

(A_VARIETY_OF)

pages/builders/chain-operators/tutorials/create-l2-rollup.mdx

[style] ~20-~20: Consider using an alternative to strengthen your wording.
Context: ...rial is designed for developers who want to learn about the OP Stack by spinning...

(WANT_KEEN)


[style] ~21-~21: Consider removing “of” to be more concise
Context: ...e full deployment process and teach you all of the components that make up the OP Stack, a...

(ALL_OF_THE)


[style] ~21-~21: Try using a synonym here to elevate your writing.
Context: ...nd teach you all of the components that make up the OP Stack, and **you'll end up with ...

(CONSTITUTE_COMPRISE)


[typographical] ~24-~24: Consider adding a comma here.
Context: ... To learn about the different components please read the [deployment overview page](/bu...

(PLEASE_COMMA)


[uncategorized] ~28-~28: If this is a compound adjective that modifies the following noun, use a hyphen.
Context: ...r own needs. **The OP Stack is free and open source software licensed entirely under the MI...

(EN_COMPOUND_ADJECTIVE_INTERNAL)


[uncategorized] ~89-~89: Possible missing comma found.
Context: ...our OP Stack chain directly from source code instead of using a container system lik...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~99-~99: Possible missing preposition found.
Context: ...ial. ### Build the Optimism Monorepo {

Clone the Optimism Monor...

(AI_HYDRA_LEO_MISSING_OF)


[style] ~134-~134: Consider removing “of” to be more concise
Context: ...g script and double check that you have all of the required versions installed. If you don...

(ALL_OF_THE)


[style] ~147-~147: This phrase is redundant. Consider using “inside”.
Context: ...ll {<h3>Build the various packages inside of the Optimism Monorepo</h3>} bash ma...

(OUTSIDE_OF)


[style] ~214-~214: The phrase ‘has the ability to’ might be wordy. Consider using “can”.
Context: ... up the chain: * The Admin address has the ability to upgrade contracts. * The Batcher ad...

(HAS_THE_ABILITY_TO)


[uncategorized] ~298-~298: Possible missing comma found.
Context: ...hell](#configuring-direnv). Next you'll need to allow direnv to read t...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~327-~327: This phrase is redundant. Consider using “inside”.
Context: ...n. Currently, chain configuration lives inside of the [contracts-bedrock](https://githu...

(OUTSIDE_OF)


[style] ~345-~345: This phrase is redundant. Consider using “inside”.
Context: ...etting-started.jsonconfiguration file inside of thedeploy-config` directory. ```bash...

(OUTSIDE_OF)


[uncategorized] ~380-~380: Use a comma before ‘and’ if it connects two independent clauses (unless they are closely connected and short).
Context: ...69 then the contract has been deployed and you can safely skip this section. {<h3...

(COMMA_COMPOUND_SENTENCE)


[uncategorized] ~433-~433: Possible missing comma found.
Context: ...es Now that you've set up the L1 smart contracts you can automatically generate several ...

(AI_HYDRA_LEO_MISSING_COMMA)


[style] ~487-~487: You have already used this phrasing in nearby sentences. Consider replacing it to add variety to your writing.
Context: ... be running a Sequencer node, so you'll need to import the Sequencer private key that...

(REP_NEED_TO_VB)


[style] ~607-~607: This phrase is redundant. Consider using “inside”.
Context: ...ou'll start to see blocks being created inside of op-geth. **By ...

(OUTSIDE_OF)


[style] ~637-~637: The phrase ‘a lot of’ might be wordy and overused. Consider using an alternative.
Context: ... it can expend ETH quickly if there are a lot of transactions to publish. {<h3...

(A_LOT_OF)

Gitleaks
pages/builders/chain-operators/tutorials/create-l2-rollup.mdx

251-252: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)


255-256: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)


259-260: Detected a Generic API Key, potentially exposing access to various services and sensitive operations.

(generic-api-key)

Additional comments not posted (12)
words.txt (1)

Line range hint 1-359: Changes to words.txt are consistent with PR objectives.

The addition of "rollups" and the removal of "Routescan" align with the updates mentioned in the AI-generated summary. This change seems to be accurately reflected in the file.

Tools
LanguageTool

[duplication] ~281-~281: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ... REQUIREDBLOCKS requiredblocks Rollouts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix r...

(GERMAN_WORD_REPEAT_RULE)


[duplication] ~285-~285: Möglicher Tippfehler: ein Wort wird wiederholt
Context: ...louts Rollups rollups Routescan rpckind RPCPREFIX rpcprefix rpcs RPGF Rpgf rpgf RWAs Schnorr secp S...

(GERMAN_WORD_REPEAT_RULE)

pages/builders/chain-operators/tutorials/sdk.mdx (1)

8-8: Replacement of Callout with WipCallout is correctly implemented.

This change aligns with the PR objectives to update the callout components across the documentation.

pages/builders/app-developers/tutorials/sdk-view-txns.mdx (1)

8-8: Replacement of Callout with WipCallout is correctly implemented.

This change aligns with the PR objectives to update the callout components across the documentation.

pages/builders/app-developers/tutorials/standard-bridge-standard-token.mdx (1)

8-8: Replacement of Callout with WipCallout is correctly implemented.

This change aligns with the PR objectives to update the callout components across the documentation.

pages/builders/app-developers/tutorials/standard-bridge-custom-token.mdx (1)

8-8: Replacement of Callout with WipCallout is correctly implemented.

This change aligns with the PR objectives to update the callout components across the documentation.

pages/builders/app-developers/tutorials/send-tx-from-eth.mdx (1)

8-8: Confirm the new component import.

The import statement for WipCallout has been added as expected based on the PR summary. Ensure that the path @/components/WipCallout is correctly set up in the project configuration to resolve properly.

pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx (1)

8-8: Confirm the new component import.

The import statement for WipCallout has been added as expected based on the PR summary. Ensure that the path @/components/WipCallout is correctly set up in the project configuration to resolve properly.

pages/builders/app-developers/tutorials/sdk-trace-txns.mdx (1)

8-8: Confirm the new component import.

The import statement for WipCallout has been added as expected based on the PR summary. Ensure that the path @/components/WipCallout is correctly set up in the project configuration to resolve properly.

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

8-8: Updated import statement for new WipCallout component.

This change correctly introduces the new WipCallout component which is part of the documentation's update to enhance visual elements and functionality. Ensure all pages that use this component have similar import updates.


10-10: Introduction of WipCallout component.

The placement of the WipCallout at the beginning of the document is appropriate for highlighting work-in-progress or important notices right away. This aligns with the PR's objective to enhance the visibility and effectiveness of callouts.

pages/builders/chain-operators/tutorials/create-l2-rollup.mdx (2)

8-8: Updated import statement for new WipCallout component.

This change correctly introduces the new WipCallout component which is part of the documentation's update to enhance visual elements and functionality. Ensure all pages that use this component have similar import updates.


10-10: Introduction of WipCallout component.

The placement of the WipCallout at the beginning of the document is appropriate for highlighting work-in-progress or important notices right away. This aligns with the PR's objective to enhance the visibility and effectiveness of callouts.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

netlify bot commented Jun 28, 2024

Deploy Preview for docs-optimism ready!

Name Link
🔨 Latest commit e064639
🔍 Latest deploy log https://app.netlify.com/sites/docs-optimism/deploys/667e8f5453902b0008b9f0d9
😎 Deploy Preview https://deploy-preview-775--docs-optimism.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 8

Outside diff range and nitpick comments (6)
pages/builders/app-developers/tutorials/send-tx-from-eth.mdx (3)

Line range hint 23-23: Grammar Improvement Suggested.

Consider adding a comma after "tutorial" to improve the flow of the sentence.

- In this tutorial you'll learn how to trigger a transaction on OP Mainnet from Ethereum.
+ In this tutorial, you'll learn how to trigger a transaction on OP Mainnet from Ethereum.

Line range hint 88-88: Consider simplifying the sentence.

The phrase "in order to" could be simplified to "to" for conciseness.

- You need a private key in order to sign transactions.
+ You need a private key to sign transactions.

Line range hint 170-170: Grammar Improvement Suggested.

Consider adding a comma after "contract" for better readability.

- When sending transactions via the `OptimismPortal` contract it's important to always include a gas buffer.
+ When sending transactions via the `OptimismPortal` contract, it's important to always include a gas buffer.
pages/builders/app-developers/tutorials/sdk-estimate-costs.mdx (2)

Line range hint 69-69: Consider simplifying the sentence.

The phrase "in order to" could be simplified to "to" for conciseness.

- You will need to get some ETH on OP Sepolia in order to run the code in this tutorial.
+ You will need to get some ETH on OP Sepolia to run the code in this tutorial.

Line range hint 77-77: Consider simplifying the sentence.

The phrase "in order to" could be simplified to "to" for conciseness.

- You need a private key in order to sign transactions.
+ You need a private key to sign transactions.
pages/builders/app-developers/tutorials/sdk-trace-txns.mdx (1)

Line range hint 183-183: Grammar Improvement Suggested.

Consider changing "amount of tokens" to "number of tokens" for grammatical accuracy.

- ...arch for `Mint` events to determine the amount of tokens that were minted as a result...
+ ...arch for `Mint` events to determine the number of tokens that were minted as a result...

@cpengilly cpengilly merged commit db9c6d7 into ethereum-optimism:main Jun 28, 2024
5 of 6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants