DA-1354 refactor: tutorial titles

[VirajAgarwal1]

Refactor the H1 titles in the tutorial

[gemini-code-assist]

Summary of Changes

Hello @VirajAgarwal1, 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 readability and consistency of tutorial documentation by refactoring various H1 titles. The changes aim to make the tutorial headings more concise, descriptive, and aligned with best practices for technical documentation, ultimately improving the user experience and information retrieval.

Highlights

• Tutorial Title Refinements: Updated the main H1 titles across several tutorial markdown files to improve clarity and conciseness, making them more descriptive and easier to understand at a glance.
• Heading Level Adjustment: Adjusted a heading level from H1 to H2 in the Grafana Dashboards tutorial's 'Prerequisites' section, improving the document's structural hierarchy.
• Enhanced Specificity: Refined certain tutorial titles to include more specific technology mentions (e.g., 'Keycloak' for OpenID Connect) or to remove redundant phrasing (e.g., 'A Step-by-Step Tutorial').

🧠 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 refactors titles in several tutorial markdown files. The changes are mostly good, improving consistency and document structure. I've found one instance where an H1 title is kept, but a comment in the file's frontmatter suggests it should be removed. I've left a specific comment with a suggestion for that file. The other changes look good.

[ejscribner]

Everything else looks great!

[ejscribner]

I think # Quickstart **for** Couchbase **in** C++ is more grammatically correct here, since we work "in" a language and the tutorial is "for" couchbase. It looks like its incorrect in the frontmatter, so perhaps we should change that back instead.