Modify section title for manual downgrade/upgrade

[1JorgeB]

Updated the section title to include 'upgrade' alongside 'downgrade' for clarity.

Before Submitting This PR, Please Ensure You Have Completed The Following:

1. Are internal links to wiki documents using relative file links?
2. Are all new documentation files lowercase, with dash separated names (ex. unraid-os.mdx)?
3. Are all assets (images, etc), located in an assets/ subfolder next to the .md/mdx files?
4. Have you checked to ensure there aren't other open Pull Requests for the same update/change?
5. Is the build succeeding?

Summary by CodeRabbit

• Documentation
  • Updated documentation structure and headings to better reflect coverage of both downgrade and upgrade procedures for Unraid
  • Reorganized downgrade section with two distinct methods presented via separate tabs: simplified graphical interface method and command line method
  • Each method includes detailed step-by-step instructions specific to that approach

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Documentation file updated to rename a heading from "Manual downgrade" to "Manual downgrade or upgrade" and adds a new tabbed UI section presenting two downgrade methods: "Simplest method" and "Command line method" with corresponding partials.

Changes

Cohort / File(s)	Change Summary
Documentation Update docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx	Renames "Manual downgrade" heading to "Manual downgrade or upgrade"; adds tabbed UI section under Downgrading Unraid with two methods ("Simplest method" and "Command line method") loading separate partials

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Poem

🐰 A heading now spans both ways,
Up and down in docs' new maze,
Tabs unfold like rabbit's ear,
Two paths forward, crystal clear!

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly and specifically describes the main change: modifying a section title to include both 'downgrade' and 'upgrade', which directly aligns with the file changes.
Description check	✅ Passed	The description provides a clear explanation of the changes and includes the complete contributor checklist template with all required sections present.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f343679 and 942ab3f.

📒 Files selected for processing (1)

• docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (1 hunks)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)

• GitHub Check: deploy-preview

🔇 Additional comments (2)

docs/unraid-os/system-administration/maintain-and-update/upgrading-unraid.mdx (2)

142-144: Verify heading-to-content consistency.

The heading states "Manual downgrade or upgrade," but the accompanying description (line 144) only references downgrading scenarios. Confirm that the documented methods in the partial files actually support both downgrade and upgrade operations. If they do, consider updating the description to clarify when each operation is appropriate.

---

21-21: Internal links follow relative path convention.

Both existing and new internal links correctly use relative file paths as required by the contributor checklist.

Also applies to: 144-144

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

PR Preview Action v1.6.3
🚀 View preview at https://unraid.github.io/docs/pr-preview/pr-392/
Built to branch gh-pages at 2025-11-22 10:56 UTC. Preview will be ready when the GitHub Pages deployment is complete.