#822: DOCS: cleans up linux docs to remove homebrew mention

[alanionita]

Clarifies Linux installation steps

Summary by CodeRabbit

• Documentation
  • Streamlined the installation guide by removing redundant instructions for macOS Homebrew.
  • Updated the formatting to ensure a consistent and readable presentation across installation options.

[vercel]

@alanionita is attempting to deploy a commit to the FlutterTools Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

Walkthrough

The pull request updates the FVM installation documentation. Redundant Homebrew installation and uninstallation commands under the MacOS tab have been removed to streamline the content. The "Install.sh" section remains unchanged, and the overall tab structure is preserved while the closing tag for the <Tabs> component has been corrected for proper formatting.

Changes

File(s)	Summary
docs/pages/.../installation.mdx	Removed redundant Homebrew installation/uninstallation commands; adjusted <Tabs> closing tag; kept Install.sh section unchanged.

Poem

In a field of docs I softly roam,
Pruning excess lines to make it home.
Homebrew bits hop out of sight,
Tabs now clear in the daylight.
A bunny cheers with pure delight! 🐇

---

📜 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 863c977 and 4a39565.

📒 Files selected for processing (1)

• docs/pages/documentation/getting-started/installation.mdx (1 hunks)

🔇 Additional comments (5)

docs/pages/documentation/getting-started/installation.mdx (5)

20-44: MacOS Tab Verification

The first tab is dedicated to MacOS and now clearly includes both the "Install.sh" script and the Homebrew installation/uninstallation commands. Keeping Homebrew instructions here is appropriate because Homebrew is a macOS-specific package manager. This change helps ensure that Linux users are not confused by irrelevant Homebrew content.

🧰 Tools

🪛 LanguageTool

[grammar] ~20-~20: The operating system from Apple is written “macOS”.
Context: ...oafarias/fvm/releases). <Tabs items={['MacOS', 'Windows', 'Linux', 'Pub']}> <Tabs....

(MAC_OS)

---

45-53: Windows Tab Verification

The Windows tab correctly provides Chocolatey installation instructions. This section is properly isolated and does not include any unnecessary content. No further modifications are needed in this block.

---

55-61: Linux Tab Clean-Up

The Linux tab now only contains the "Install.sh" command. This is perfectly in line with the PR objective to remove Homebrew-related content for Linux users, thereby clearing any confusion. The streamlined instructions enhance clarity for the Linux installation process.

---

63-76: Pub Package Tab Check

The Pub tab continues to offer the information for installing FVM as a Dart package and includes a clear callout warning regarding its use with global Flutter installs. This section remains clear and helpful for users, and no adjustments are needed.

🧰 Tools

🪛 LanguageTool

[style] ~64-~64: As a shorter alternative for ‘able to’, consider using “can also”.
Context: ... | bash ``` </Tabs.Tab> <Tabs.Tab> You are also able to install FVM as a [pub package](https://...

(BE_ABLE_TO)

---

[style] ~66-~66: Try using a more formal synonym here to elevate your writing.
Context: ...pub.dev/packages/fvm). However, if you plan on using FVM to manage your [global Flutter inst...

(PLAN_ON_INTEND)

---

77-77: Closing Tabs Element Formatting

The closing </Tabs> tag (line 77) has been updated (indicated by the diff marker "~") to ensure proper formatting and component closure. Verify that the corrected tag renders correctly in all environments.

---

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.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.