Skip to content

docs: Rename aidaptivcache documents - #69

Merged
tsaishawn merged 2 commits into
mainfrom
docs/rename_aidaptivache_docs
Jan 19, 2026
Merged

docs: Rename aidaptivcache documents#69
tsaishawn merged 2 commits into
mainfrom
docs/rename_aidaptivache_docs

Conversation

@tsaishawn

Copy link
Copy Markdown
Contributor

No description provided.

@gemini-code-assist

Copy link
Copy Markdown

Summary of Changes

Hello @tsaishawn, I'm Gemini Code Assist1! 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 a significant documentation cleanup and consistency effort. It renames several key documents and updates all associated terminology to uniformly use 'aiDAPTIVCache'. Beyond naming, the changes also enhance user experience by simplifying navigation instructions within the OtterScale platform and refining the technical details and configuration parameters for finetuning and inference jobs.

Highlights

  • Documentation Renaming: Renamed three core documentation files from 'aidaptiv' to 'aidaptivcache' to ensure consistent terminology across the project.
  • Content Terminology Update: Updated all internal references within the affected documents, changing 'aiDAPTIV' to 'aiDAPTIVCache' in titles, descriptions, and body text.
  • Navigation Instruction Improvement: Replaced direct URL links for OtterScale UI navigation (e.g., File System, Jobs, Services, Workloads) with more user-friendly, path-based instructions (e.g., 'Storage → File System').
  • Job Configuration Adjustment: Modified the ttlSecondsAfterFinished parameter for finetune jobs from 3600 seconds to 60 seconds, reducing the retention period for completed job resources.
  • Inference Feature Refinement: Streamlined the feature list for aiDAPTIVCache Inference by removing 'PagedAttention memory optimization', 'DRAM/SSD' from 'KV Cache offloading', and 'Prefix Caching' from the overview.
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 gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request renames aiDAPTIV to aiDAPTIVCache across several documentation files for consistency, including renaming the files themselves. The changes are mostly correct and also include some nice usability improvements by replacing direct URLs with navigation steps. I've found a few minor inconsistencies where the renaming was missed or done incorrectly. Please see my detailed comments below.

Comment thread src/content/docs/demos/07-aidaptivcache-operator.mdx Outdated
Comment thread src/content/docs/demos/08-aidaptivcache-finetune.mdx Outdated
Comment thread src/content/docs/demos/09-aidaptivcache-inference.mdx Outdated
Comment thread src/content/docs/demos/09-aidaptivcache-inference.mdx Outdated
Comment thread src/content/docs/demos/09-aidaptivcache-inference.mdx Outdated
@tsaishawn
tsaishawn merged commit 2d86cf3 into main Jan 19, 2026
1 check passed
@iasthc
iasthc deleted the docs/rename_aidaptivache_docs branch March 6, 2026 08:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant