docs: fix typo of macOS

[wcbing]

Description

As the title, fix typo of "macOS".

There are some peripheral change that doesn't affect functionality.

Related Issues

None

Summary by CodeRabbit

• Documentation

  • Standardized platform name formatting across README files, configuration guides, and test documentation for proper branding conventions.

• Style

  • Updated capitalization of platform names in comments and documentation headers for consistency throughout the project.

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

[coderabbitai]

Walkthrough

This pull request corrects the capitalization of "MacOS" to "macOS" across documentation files, comments, and website content. All changes are purely textual corrections to align with Apple's official branding, with no functional, logical, or control-flow modifications.

Changes

Cohort / File(s)	Summary
Documentation files README.md, testsuite/README.md, testsuite/Notes.md	Corrected capitalization of "MacOS" to "macOS" in section headings and documentation text for consistent branding
Source code comments src/internal/function.go	Updated comment string in isExternalDiskPath function from "MacOS" to "macOS"
Website documentation website/src/content/docs/configure/superfile-config.mdx	Corrected platform name casing from "MacOS" to "macOS" in editor and directory editor configuration documentation

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

• Straightforward capitalization corrections following a single consistent pattern
• Changes are cosmetic/branding-only with zero functional impact
• Simple verification: confirm each "MacOS" instance was changed to "macOS"

Suggested labels

documentation

Suggested reviewers

• lazysegtree

Poem

🐰 A rabbit hops through docs with care,
Fixing "MacOS" here and there,
Now "macOS" gleams just right—
Apple's brand shines clear and bright! 🍎✨

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'docs: fix typo of macOS' accurately reflects the main change in the pull request, which consistently corrects macOS capitalization across multiple documentation files.
Docstring Coverage	✅ Passed	Docstring coverage is 100.00% which is sufficient. The required threshold is 80.00%.

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

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

---

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.}

[coderabbitai]

Actionable comments posted: 1

📜 Review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 2d6d6f0 and e9317eb.

📒 Files selected for processing (5)

• README.md (5 hunks)
• src/internal/function.go (1 hunks)
• testsuite/Notes.md (1 hunks)
• testsuite/README.md (1 hunks)
• website/src/content/docs/configure/superfile-config.mdx (2 hunks)

🧰 Additional context used

🧠 Learnings (3)

📚 Learning: 2025-07-15T10:32:28.063Z

Learnt from: lazysegtree
Repo: yorukot/superfile PR: 935
File: website/src/content/docs/changelog.md:17-26
Timestamp: 2025-07-15T10:32:28.063Z
Learning: In the superfile changelog (website/src/content/docs/changelog.md), lazysegtree prefers to maintain the existing heading format with main version headings using # and sub-sections using #### (Update, Bug fix, Optimization, etc.) consistently throughout all releases, prioritizing established format consistency over strict markdown heading hierarchy compliance.

Applied to files:

• testsuite/README.md
• README.md
• website/src/content/docs/configure/superfile-config.mdx

📚 Learning: 2025-07-21T08:49:44.628Z

Learnt from: lazysegtree
Repo: yorukot/superfile PR: 953
File: website/public/install.sh:42-42
Timestamp: 2025-07-21T08:49:44.628Z
Learning: In the superfile bash installer (website/public/install.sh), lazysegtree maintains the same principle as the PowerShell installer - users should supply correct environment variable values (SPF_INSTALL_VERSION without leading 'v') rather than adding validation code to handle malformed input, following the philosophy that users should provide properly formatted values.

Applied to files:

• README.md

📚 Learning: 2025-04-12T12:00:32.688Z

Learnt from: lazysegtree
Repo: yorukot/superfile PR: 0
File: :0-0
Timestamp: 2025-04-12T12:00:32.688Z
Learning: In PR #767 for yorukot/superfile, the focus is on moving code (especially sidebar-related functionality) to a more organized structure without changing functionality. Pre-existing issues should be ignored since the purpose is code reorganization, not fixing existing problems.

Applied to files:

• website/src/content/docs/configure/superfile-config.mdx

🪛 LanguageTool

README.md

[grammar] ~183-~183: Ensure spelling is correct
Context: .... If you installed superfile with sudo, runw bash sudo rm /usr/local/bin/spf If you installed superfile without sudo,...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (5)

testsuite/README.md (1)

18-18: LGTM!

The capitalization change to "macOS" correctly aligns with Apple's official branding.

src/internal/function.go (1)

48-48: LGTM!

The comment now uses the correct "macOS" capitalization.

testsuite/Notes.md (1)

18-18: LGTM!

The header now correctly uses "macOS" capitalization.

website/src/content/docs/configure/superfile-config.mdx (1)

29-29: LGTM!

All instances now correctly use "macOS" capitalization, aligning with Apple's branding.

Also applies to: 33-33, 49-49

README.md (1)

16-16: LGTM!

All instances now correctly use "macOS" capitalization, consistent with Apple's official branding.

Also applies to: 67-67, 117-117, 147-147, 181-181

[coderabbitai]

⚠️ Potential issue | 🟡 Minor

Fix the typo in user-facing documentation.

The word "runw" should be "run".

🔎 Proposed fix

-On macOS and Linux, you can uninstall superfile by simply removing the binary. If you installed superfile with sudo, runw
+On macOS and Linux, you can uninstall superfile by simply removing the binary. If you installed superfile with sudo, run

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change

	On macOS and Linux, you can uninstall superfile by simply removing the binary. If you installed superfile with sudo, runw
	On macOS and Linux, you can uninstall superfile by simply removing the binary. If you installed superfile with sudo, run

🧰 Tools

🪛 LanguageTool

[grammar] ~183-~183: Ensure spelling is correct
Context: .... If you installed superfile with sudo, runw bash sudo rm /usr/local/bin/spf If you installed superfile without sudo,...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🤖 Prompt for AI Agents

In README.md around line 183, there's a typo in the user-facing sentence ("runw"
should be "run"); edit that line to replace "runw" with "run" so the sentence
reads correctly (e.g., "If you installed superfile with sudo, run").