Fix breadcrumb and title casing

[bradleycamacho]

Fixes a few casing issues

[netlify]

✅ Deploy Preview for docs-optimism ready!

Name	Link
🔨 Latest commit	fb9e162
🔍 Latest deploy log	https://app.netlify.com/sites/docs-optimism/deploys/6734eb10d3d4f60008f4a83d
😎 Deploy Preview	https://deploy-preview-1111--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 minor textual modifications in the documentation for Node Operators. Specifically, the title "Node Software Releases" has been changed to "Node software releases" in two files: node-operators.mdx and releases.mdx. These changes are purely stylistic and do not affect the functionality, logic, or structure of the documentation.

Changes

File Path	Change Summary
pages/builders/node-operators.mdx	Updated card title from "Node Software Releases" to "Node software releases."
pages/builders/node-operators/releases.mdx	Changed document title from "Node Software Releases" to "Node software releases." No other content changes.

Possibly related PRs

• docs: Improve search ability for docker images #809: This PR modifies the releases.mdx file, changing the title from "Node Software Releases" to "Software Releases," which is directly related to the title change in the main PR.
• Add links to OP Mainnet runbook #997: This PR updates the self-hosted.mdx file to include links to the OP Mainnet runbooks, which may relate to the documentation context of node operators, similar to the changes in the main PR.
• Fixed errors in RPC and typos in docs #1014: This PR addresses grammatical errors in the documentation, including files related to node operations, which may overlap with the documentation updates in the main PR.
• Documentation Improvements: Grammar, Structure, and Readability Fixes #1057: This PR focuses on grammar and readability improvements across various documentation files, potentially including those related to node operators, aligning with the stylistic changes in the main PR.

Suggested reviewers

• sbvegan

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL

📥 Commits

Reviewing files that changed from the base of the PR and between df55271 and fb9e162.

📒 Files selected for processing (2)

• pages/builders/node-operators.mdx (1 hunks)
• pages/builders/node-operators/releases.mdx (1 hunks)

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

• pages/builders/node-operators.mdx
• pages/builders/node-operators/releases.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.