Correct MIPS architecture version

[pauldowman]

Cannon is actually MIPS32 R1, not MIPS III.

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	9ea5c8f
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/67aac436d470cd0008ed59a8
😎 Deploy Preview	https://deploy-preview-1344--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

Walkthrough

The pull request updates the terminology used in the documentation to reference the MIPS instruction set architecture. Specifically, it changes mentions of "MIPS III instructions" or "32-bit, Big-Endian, MIPS III Instruction Set Architecture" to "MIPS32 R1 instructions" or "MIPS32 R1 Instruction Set Architecture" in multiple documentation files. The affected pages include those for fault proofs and smart contracts, ensuring that all references accurately denote the correct architecture version. There are no changes to functional code, logic, error handling, or control flow.

Possibly related PRs

• docs: polish MIPS page #716: Clarifies the reference to "MIPS32 R1" in the context of the MIPS.sol smart contract.
• Update Security FAQ on Fault Proof and redefine Fault Proof contracts #1265: Updates the description of the MIPS contract to specify "MIPS32 R1," ensuring consistency in the documentation.
• Update smart-contracts.mdx to fix typo in change log #1017: Modifies documentation to consistently reference the "MIPS32 R1" instruction set across different files.

Suggested labels

flag:merge-pending-release

Suggested reviewers

• cpengilly
• sbvegan

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 86b2e35 and 9ea5c8f.

📒 Files selected for processing (3)

• pages/stack/fault-proofs/cannon.mdx (1 hunks)
• pages/stack/fault-proofs/mips.mdx (1 hunks)
• pages/stack/smart-contracts.mdx (1 hunks)

✅ Files skipped from review due to trivial changes (3)

• pages/stack/smart-contracts.mdx
• pages/stack/fault-proofs/mips.mdx
• pages/stack/fault-proofs/cannon.mdx

⏰ Context from checks skipped due to timeout of 90000ms (4)

• GitHub Check: pr-workflow
• GitHub Check: Redirect rules - docs-optimism
• GitHub Check: Header rules - docs-optimism
• GitHub Check: Pages changed - docs-optimism

---

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 generate docstrings to generate docstrings for this PR. (Beta)
• @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.

[mbaxter]

I think we probably still want to call out "Big-Endian" here.

[pauldowman]

good point, fixed in #1357 (for both places where it was removed).