Update copy in ReadMe and Resource

[lethargicpanda]

Update copy in ReadMe and Resource:

• Update Nano Banana references,
• Use "Gemini Live API" instead of "Gemini Live"
• Use "to-do" instead of "Todo".

[lethargicpanda]

cc @JolandaVerhoef

[gemini-code-assist]

Summary of Changes

Hello @lethargicpanda, I'm Gemini Code Assist¹! 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 clarity and accuracy of documentation and user-facing text by updating specific terminology. It ensures that model names, API references, and common phrases are consistent with current branding and grammatical standards, improving the overall user experience and readability of the project's resources.

Highlights

• Model Name Updates: References to "Nano Banana" and "Gemini 2.5 Flash Image model" have been updated to "Nano Banana Pro" and "Gemini 3 Pro Image model" respectively.
• API Naming Consistency: "Gemini Live" has been consistently updated to "Gemini Live API" across relevant descriptions and titles.
• Grammar Correction: The term "Todo" has been standardized to "to-do" for improved grammatical correctness.

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

[gemini-code-assist]

Code Review

This pull request updates copy across several README files and string resources. The changes align with the goals stated in the description, such as updating model names, standardizing 'Gemini Live' to 'Gemini Live API', and using 'to-do' instead of 'Todo'. The updates are mostly consistent, but I've pointed out a couple of minor issues. One is a deviation from the naming convention in the main README.md, and the other is the removal of a potentially useful guidance string in one of the samples. Overall, good job on keeping the documentation and resources up to date.

[JolandaVerhoef]

two small remarks, lgtm otherwise.