Fixing broken proxyd link

[praetoriansentry]

Updating broken proxyd link

Description

It looks like the linked proxyd path was moved a few weeks ago by ethereum-optimism/optimism#12826

This small change links to the updated infra repo.

Tests

Additional context

Metadata

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	1b16f85
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/6744c9c2d7ea790008bf8d71
😎 Deploy Preview	https://deploy-preview-1141--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 includes updates to the document titled "Chain architecture," which focuses on the rollup protocol. Key changes involve modifying references to the proxyd configuration, shifting the link from a specific path in the optimism repository to a more generalized path in the infra repository. This adjustment reflects an organizational change in documentation structure. Additionally, the text has been refined for clarity, particularly in sections that describe the roles of components such as op-geth, op-node, op-batcher, and op-proposer. The modifications aim to enhance readability while maintaining the original intent of the descriptions. Overall, the structure and content of the document remain consistent with the previous version, with no significant alterations to logic, error handling, or control flow.

Possibly related issues

• [2024 Q4 Audit] builders/chain-operators/configuration/overview.md #919: The updates in this PR clarify the rollup configuration, which aligns with the issue's request for improved explanations of configurations for L1 smart contracts during deployment.

Possibly related PRs

• Update Rollup Deployment Configuration #795: This PR involves updates to rollup configuration documentation, aligning with the main PR's focus on enhancing clarity and references related to rollup protocol components.
• Update rollup.mdx #1018: This PR updates the rollup.mdx file, specifically focusing on deployment configuration values, which is directly related to the main PR's changes regarding the rollup protocol.
• Op deployer updates #1020: Modifications in this PR enhance clarity and detail regarding deployment in the op-deployer documentation, relevant to the main PR's updates on rollup protocol components.
• Documentation Improvements: Grammar, Structure, and Readability Fixes #1057: This PR aims to improve the overall quality of documentation, aligning with the main PR's goal of enhancing clarity and readability in rollup protocol documentation.
• Documentation Text Fixes Changes Made #1128: This PR addresses grammatical errors and improves readability across various documentation files, consistent with the main PR's aim to enhance clarity in rollup protocol documentation.

Suggested reviewers

• sbvegan: Suggested as a reviewer due to their involvement in related documentation efforts.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between 4684951 and 1b16f85.

📒 Files selected for processing (1)

• pages/builders/chain-operators/architecture.mdx (1 hunks)

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

• pages/builders/chain-operators/architecture.mdx

---

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.