Skip to content

docs: fix typos in source code and documentation#13577

Merged
jackwotherspoon merged 1 commit intogoogle-gemini:mainfrom
fancive:fix-issue-13086-typos
Nov 21, 2025
Merged

docs: fix typos in source code and documentation#13577
jackwotherspoon merged 1 commit intogoogle-gemini:mainfrom
fancive:fix-issue-13086-typos

Conversation

@fancive
Copy link
Copy Markdown
Contributor

@fancive fancive commented Nov 21, 2025

Fixed multiple spelling errors across the codebase:

  • Attemtping → Attempting
  • necesssary → necessary
  • represeting → representing
  • Ouput → Output
  • interative → interactive
  • explictly → explicitly
  • overrided → overridden
  • confroms → conforms
  • completey → completely
  • recursivlty → recursively
  • chagnes → changes
  • usag → usage
  • measuing → measuring
  • rejcted → rejected

Total of 14 files updated with spelling corrections in comments, documentation, and strings.

Fixes #13086

@fancive fancive requested a review from a team as a code owner November 21, 2025 13:58
@gemini-code-assist
Copy link
Copy Markdown
Contributor

Summary of Changes

Hello @fancive, 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 primarily focuses on improving the textual accuracy and overall quality of the project by addressing a series of spelling errors. The corrections are applied across various components, including source code comments, user-facing documentation, and internal strings, ensuring a more polished and professional presentation. Additionally, a new documentation file has been added to guide AI code assistants.

Highlights

  • Typo Corrections: Corrected 13 distinct spelling errors across various files, enhancing the accuracy and professionalism of the codebase.
  • Documentation and Code Clarity: Updated a total of 13 files, fixing typos in comments, documentation, and string literals to improve overall clarity.
  • New AI Guidance File: Introduced a new CLAUDE.md file, providing specific guidance for Claude Code when interacting with this repository.
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
Copy Markdown
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 addresses multiple spelling errors throughout the codebase, including in documentation, source code comments, and strings. All the corrections are accurate and improve the overall readability and professionalism of the project. The changes are well-contained and align with the pull request's stated goal. I have no further feedback as there are no high or critical issues.

Fixed multiple spelling errors across the codebase:
- Attemtping -> Attempting
- necesssary -> necessary
- represeting -> representing
- Ouput -> Output
- interative -> interactive
- explictly -> explicitly
- overrided -> overridden
- confroms -> conforms
- completey -> completely
- recursivlty -> recursively
- chagnes -> changes
- usag -> usage
- measuing -> measuring
- rejcted -> rejected

Fixes google-gemini#13086
@fancive fancive force-pushed the fix-issue-13086-typos branch from c488fb5 to aa82a2b Compare November 21, 2025 14:03
@jackwotherspoon
Copy link
Copy Markdown
Collaborator

Thanks a ton for this @fancive 👏

@jackwotherspoon jackwotherspoon added this pull request to the merge queue Nov 21, 2025
Merged via the queue into google-gemini:main with commit 0f0b463 Nov 21, 2025
21 checks passed
thacio added a commit to thacio/auditaria that referenced this pull request Nov 23, 2025
werdnum pushed a commit to werdnum/gemini-cli that referenced this pull request Nov 24, 2025
danpalmer pushed a commit to danpalmer/gemini-cli that referenced this pull request Nov 29, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Bug: Misc. typos in docs and source code strings

2 participants