docs: minor corrections

[danielclow]

fix some minor formatting issues

[gemini-code-assist]

Summary of Changes

Hello @danielclow, 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 and consistency of the documentation. It standardizes the formatting of SQL code examples, corrects a functional typo in an SQL window function, and resolves various minor grammatical and structural inconsistencies across several documentation pages. The changes aim to improve the overall readability and accuracy of the technical content.

Highlights

• SQL Formatting Standardization: Standardized SQL keyword capitalization (e.g., 'insert' to 'INSERT') and added semicolons to the end of SQL statements across several examples in the documentation.
• Code Block Indentation: Adjusted the indentation for SQL code blocks to improve readability and consistency.
• Typo Correction: Fixed a typo in the ANOMALY_WINDOW function name within an example, changing 'ANOMAYL_WINDOW' to 'ANOMALY_WINDOW'.
• Documentation Clarity Improvements: Addressed minor grammatical, punctuation, and formatting issues in the backup and disaster recovery documentation files for enhanced clarity.
• SQL Example Correction: Corrected a syntax error in an INSERT statement example and updated a tag value from 'beijing.chaoyang' to 'California.SanFrancisco'.

🧠 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 introduces several minor corrections to the documentation, including fixing SQL syntax errors, correcting typos, and improving markdown formatting. The changes are generally good and improve the quality of the documentation. I've added a couple of suggestions to further improve the consistency of SQL code formatting in one of the files.