docs: fix incorrect relative links to command reference

[kanywst]

Summary

This PR corrects the relative links to the commands.md reference page in the documentation.

Details

The previous links used ../../reference/ which pointed outside the docs/ directory. Since the
reference/ directory is located directly under docs/, the correct path from subdirectories like
get-started/ and resources/ is ../reference/.

• Modified docs/get-started/index.md
• Modified docs/resources/quota-and-pricing.md

Related Issues

How to Validate

Pre-Merge Checklist

• Updated relevant documentation and README (if needed)
• Added/updated tests (if needed)
• Noted breaking changes (if any)
• Validated on required platforms/methods:
  • MacOS
    • npm run
    • npx
    • Docker
    • Podman
    • Seatbelt
  • Windows
    • npm run
    • npx
    • Docker
  • Linux
    • npm run
    • npx
    • Docker

[gemini-code-assist]

Summary of Changes

Hello, 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 addresses an issue with broken relative links within the documentation. By adjusting the paths to the commands.md reference file, it improves the navigability and accuracy of the documentation, ensuring users can correctly access command-line interface details from various sections.

Highlights

• Documentation Link Correction: Corrected incorrect relative links to the commands.md reference page in the documentation, ensuring proper navigation.

Changelog

• docs/get-started/index.md
  • Corrected the relative path for the "Command Reference" link from ../../reference/commands.md#stats to ../reference/commands.md#stats.
• docs/resources/quota-and-pricing.md
  • Corrected the relative path for the "Command Reference" link from ../../reference/commands.md#stats to ../reference/commands.md#stats.

Activity

• The author, kanywst, created the pull request to fix incorrect relative links in the documentation.
• The author has marked the "Updated relevant documentation and README" and "Validated on MacOS (npm run)" checklist items as complete.

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 correctly fixes broken relative links in two documentation files. The change updates the path from ../../reference/ to ../reference/ to accurately point to the command reference page. The fix is appropriate and no issues were found.

_{Note: Security Review has been skipped due to the limited scope of the PR.}

[g-samroberts]

Thank you for your contribution, @kanywst!