Skip to content

docs: fix spelling typos in installation guide#20579

Merged
jackwotherspoon merged 2 commits intogoogle-gemini:mainfrom
campox747:fix-installation-typos
Feb 27, 2026
Merged

docs: fix spelling typos in installation guide#20579
jackwotherspoon merged 2 commits intogoogle-gemini:mainfrom
campox747:fix-installation-typos

Conversation

@campox747
Copy link
Contributor

Summary

Minor documentation typo fix.

Details

Related Issues

N/A

How to Validate

Read the updated lines in docs/get-started/installation.md to verify the spelling corrections.

Pre-Merge Checklist

  • Updated relevant documentation and README (if needed)
  • Added/updated tests (if needed)
  • Noted breaking changes (if any)
  • Validated on required platforms/methods:
    • MacOS
      • npm run
      • npx
      • Docker
      • Podman
      • Seatbelt
    • Windows
      • npm run
      • npx
      • Docker
    • Linux
      • npm run
      • npx
      • Docker

@campox747 campox747 requested review from a team as code owners February 27, 2026 17:17
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the accuracy of the Gemini CLI installation documentation by rectifying a minor spelling mistake. The change ensures that users receive precise information regarding system requirements, thereby improving the overall readability and professionalism of the guide.

Highlights

  • Documentation Fix: Corrected a spelling error in the installation.md file, changing "sytem requriements" to "system requirements".
Changelog
  • docs/get-started/installation.md
    • Fixed a spelling typo from "sytem requriements" to "system requirements".
Activity
  • No specific review comments or activities have been recorded for this pull request yet.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request corrects two spelling errors in the docs/get-started/installation.md file. The change is straightforward and improves the quality of the documentation. No issues were found.

@gemini-cli gemini-cli bot added the priority/p1 Important and should be addressed in the near term. label Feb 27, 2026
@jackwotherspoon jackwotherspoon added this pull request to the merge queue Feb 27, 2026
Merged via the queue into google-gemini:main with commit ca13458 Feb 27, 2026
26 of 27 checks passed
@campox747 campox747 deleted the fix-installation-typos branch February 28, 2026 10:54
BryanBradfo pushed a commit to BryanBradfo/gemini-cli that referenced this pull request Mar 5, 2026
Co-authored-by: Jack Wotherspoon <jackwoth@google.com>
liamhelmer pushed a commit to badal-io/gemini-cli that referenced this pull request Mar 12, 2026
Co-authored-by: Jack Wotherspoon <jackwoth@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

priority/p1 Important and should be addressed in the near term.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants