Correct tokenlist

[bradleycamacho]

Doc only applies to OPM. We should move the doc in that case, but will do that in a following PR

[netlify]

✅ Deploy Preview for docs-optimism ready!

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

This pull request updates the terminology in the token list documentation by replacing the term "OP Stack chains" with "OP Mainnet". The changes affect several instances in the document, including the introductory statement, the section header for USDC, and the callout that notifies users about the deprecation of the legacy bridged version of USDC (USDC.e). There are no changes to the declarations of exported or public entities, and the overall structure of the document remains the same.

Sequence Diagram(s)

Possibly related PRs

• Move USDC Section to OP Mainnet-Specific #1160: This PR addresses changes related to the USDC token and its deprecation on OP Mainnet, making it directly relevant to the terminology updates in this pull request.

Suggested labels

documentation

Suggested reviewers

• krofax
• zainbacchus

---

📜 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 896d5bc and b5c07e2.

📒 Files selected for processing (1)

• pages/superchain/tokenlist.mdx (2 hunks)

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

• pages/superchain/tokenlist.mdx

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

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

---

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.