Update smart-contracts.mdx to fix typo in change log

[sbvegan]

Description

These are supposed to be v.2.2.0. You can follow the link and see the semver is the same in the contract. You can also go to the release notes and see there was no change to the SystemConfig in these releases since the upgrade to v2.2.0 in op-contracts/v1.4.0

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	31c1f96
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67182c2ca69857000814b4bd
😎 Deploy Preview	https://deploy-preview-1017--docs-optimism.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

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

[coderabbitai]

Walkthrough

The pull request introduces extensive updates to the smart-contracts.mdx documentation, enhancing the overview of smart contracts in the OP Stack. Key changes include a refined introduction to layer 1 contracts, expanded details on the op-contracts/v1.6.0 release, and updates to various contract functionalities. Additionally, it revises the changelog for previous versions, clarifying the evolution of contract roles and security measures. The document aims to provide a clearer understanding of the architecture and governance of smart contracts within the ecosystem.

Changes

File Path	Change Summary
pages/stack/smart-contracts.mdx	Updated introduction, expanded official releases section, detailed changelog for op-contracts, and clarified contract roles.
src/cannon/MIPS.sol	Method added: MIPS: [1.1.0]
src/cannon/PreimageOracle.sol	Method added: PreimageOracle: [1.1.2]
src/dispute/FaultDisputeGame.sol	Method added: FaultDisputeGame: [1.3.0]
src/dispute/PermissionedDisputeGame.sol	Method added: PermissionedDisputeGame: [1.3.0]
src/dispute/weth/DelayedWETH.sol	Method added: DelayedWETH: [1.1.0]
src/Safe/SafeSigners.sol	Method added: DeputyGuardianModule: [2.0.0]
src/dispute/AnchorStateRegistry.sol	Method added: AnchorStateRegistry: [2.0.0]
src/L1/SystemConfig.sol	Method signature updated: SystemConfig: [2.0.0] to SystemConfig: [2.2.0]

Possibly related issues

• Update the smart contract release page for op-contracts/v1.6.0 #887: This issue requests updates to the smart contract release page for op-contracts/v1.6.0, which aligns with the changes made in this PR regarding the documentation of that release.

Possibly related PRs

• fp updates #732: Updates documentation related to the Fault Proof System, directly referenced in the changes regarding Fault Proof contracts.
• contracts: update standard version to v1.6.0, CGT to v2.0.0-beta.3 #895: Updates the recommended deployment version for contracts to v1.6.0, aligning with the emphasis on security fixes in this PR.
• making updates after the granite activation #899: Incorporates the op-contracts/v1.6.0 release, a key focus of this PR.
• adding op-deployer callouts #1016: Adds callouts to direct users to the op-deployer tool, relevant to the updates on contract deployment processes.

Suggested reviewers

• bradleycamacho
• OPMattie

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 06b7e70 and 31c1f96.

📒 Files selected for processing (1)

• pages/stack/smart-contracts.mdx (2 hunks)

🧰 Additional context used

📓 Path-based instructions (1)

pages/stack/smart-contracts.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. Avoid using all caps, italics, or bold for emphasis.
• 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).
• Use sentence case for H1, H2, and H3 headers, capitalizing only the first word and any proper nouns.
• For all headers (H1, H2, H3), do not change the capitalization of proper nouns; keep them as they are.
  "

🔇 Additional comments (1)

pages/stack/smart-contracts.mdx (1)

65-65: LGTM! Version update is accurate.

The SystemConfig version has been correctly updated to 2.2.0, which matches the version in the contract source at op-contracts/v1.4.0.

Also applies to: 109-109

---

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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>, please review it.
  • 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 gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @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 using 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.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

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.