[Doc]: fix some typos in various files.

[didier-durand]

Hi,
As per title, fixing typos in various files: see commit diffs for details
Cheers
Didier

[gemini-code-assist]

Summary of Changes

Hello @didier-durand, 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 quality of the project's documentation by addressing several typos and grammatical errors. The changes span across governance documents, the main README, and detailed specification files, ensuring a more professional and precise presentation of information for all readers.

Highlights

• Documentation Clarity: Corrected various grammatical errors and inconsistencies across multiple documentation files to improve readability and accuracy.
• Consistent Terminology: Standardized the usage of terms like 'subproject' and 'subcommittee' in the GOVERNANCE.md file.
• Grammar and Spelling: Fixed minor spelling and grammatical mistakes, such as 'long running tasks' to 'long-running tasks' and 'A object' to 'An object'.

Ignored Files

• Ignored by pattern: CHANGELOG.md (1)
  • CHANGELOG.md

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 addresses several typographical errors across various documentation files, enhancing their clarity and professionalism. The corrections are accurate and beneficial. I have one suggestion for an additional minor correction in GOVERNANCE.md to ensure consistency. Please see the detailed comment.

[gemini-code-assist]

For consistency with the change from sub-projects to subprojects at the beginning of this line, you might want to update the second occurrence of sub-projects as well.

Suggested change

	3. organizing subprojects and removing sub-projects;
	3. organizing subprojects and removing subprojects;

[didier-durand]

Change suggested by Gemini's review has now been done

[holtskinner]

Be sure to update this for the latest version of the spec