Apply a clarification to "Frame" glossary entry

[sfshaza2]

Applying a clarification/tweak that git wouldn't accept in my last PR.

[gemini-code-assist]

Summary of Changes

Hello @sfshaza2, 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 refining the existing documentation by applying a clarification to the 'Frame' definition within the project's glossary. The update aims to improve the precision and readability of information related to frame rates and rendering targets, ensuring that the technical documentation is as clear and helpful as possible.

Highlights

• Glossary Clarification: The definition of 'Frame' in the src/data/glossary.yml file has been updated to provide more explicit details regarding the target rendering times for 60 fps and 120 fps, enhancing clarity for developers.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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 applies a clarification to the definition of "Frame" in the glossary, which improves clarity. I've added a couple of suggestions to improve the formatting of the updated text, as the current line wrapping could lead to awkward rendering in the final output due to how YAML literal block scalars handle newlines.

[flutter-website-bot]

Visit the preview URL for this PR (updated for commit aceb76d):

https://flutter-docs-prod--pr12892-tweak-frame-16pmue6k.web.app