fix: correct MIG, NVIDIA, vGPU, HAMi casing across docs#565
Merged
hami-robot[bot] merged 1 commit intoJul 8, 2026
Merged
Conversation
Signed-off-by: mesutoezdil <mesudozdil@gmail.com>
✅ Deploy Preview for project-hami ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
📝 WalkthroughWalkthroughThis PR applies consistent capitalization for product and technology names ("MIG", "HAMi"/"HAMi-core", "NVIDIA", "vGPU") throughout documentation files, including titles, headings, and body text, across docs/, versioned_docs/, and i18n/zh locales/versions. No code or functional behavior is changed. ChangesDocumentation branding/casing consistency
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested labels: Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Contributor
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: mesutoezdil The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Note
Due to the large number of review comments, Critical, Major severity comments were prioritized as inline comments.
🟡 Minor comments (23)
docs/developers/dynamic-mig.md-12-12 (1)
12-12: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNormalize the remaining
hami-corecasing.The visible project name is still lowercase here, so the terminology cleanup is incomplete in this doc. Please capitalize the link text and sentence to
HAMi-core.Patch
- HAMi is done by using [hami-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and hami-core is needed. + HAMi is done by using [HAMi-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and HAMi-core is needed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@docs/developers/dynamic-mig.md` at line 12, The terminology cleanup is incomplete in this paragraph because the project name still appears as lowercase hami-core. Update the prose and the link text in the dynamic-mig document so the visible name is consistently capitalized as HAMi-core, keeping the rest of the MIG description unchanged.versioned_docs/version-v2.5.1/developers/dynamic-mig.md-15-20 (1)
15-20: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winCapitalize the remaining
hami-corereference.The visible link text is still lowercase here, so the terminology cleanup is incomplete in this paragraph. Please change it to
HAMi-core.Patch
- HAMi is done by using [hami-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and hami-core is needed. + HAMi is done by using [HAMi-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and HAMi-core is needed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.5.1/developers/dynamic-mig.md` around lines 15 - 20, The paragraph still contains a lowercase visible reference to hami-core in the dynamic-mig documentation. Update the linked text in the intro sentence near the dynamic-mig discussion to use HAMi-core consistently, while keeping the existing link target intact. Verify the terminology cleanup is complete by checking the surrounding prose in this section for any remaining lowercase hami-core mentions.i18n/zh/docusaurus-plugin-content-docs/current/developers/dynamic-mig.md-12-17 (1)
12-17: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish capitalizing the
HAMi-corereferences here.This paragraph still uses lowercase
hami-corein the visible link text and the API sentence, which leaves the terminology cleanup incomplete. Please update the visible term toHAMi-core.Patch
- HAMi 是通过使用 [hami-core](https://github.com/Project-HAMi/HAMi-core) 完成的，这是一个 cuda-hacking 库。但 MIG 在全球范围内也被广泛使用。需要一个用于动态-mig 和 hami-core 的统一 API。 + HAMi 是通过使用 [HAMi-core](https://github.com/Project-HAMi/HAMi-core) 完成的，这是一个 cuda-hacking 库。但 MIG 在全球范围内也被广泛使用。需要一个用于动态-mig 和 HAMi-core 的统一 API。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/developers/dynamic-mig.md` around lines 12 - 17, The terminology cleanup in this paragraph is incomplete because the visible text still says hami-core in the opening description and the unified API sentence. Update the wording in the dynamic-mig doc so every reference matches the capitalized HAMi-core form, including the sentence that mentions the library and the related API description, while keeping the existing link target unchanged.versioned_docs/version-v2.5.0/developers/dynamic-mig.md-15-20 (1)
15-20: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winCapitalize the remaining
hami-corereference.The visible link text is still lowercase here, so the terminology cleanup is incomplete in this paragraph. Please change it to
HAMi-core.Patch
- HAMi is done by using [hami-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and hami-core is needed. + HAMi is done by using [HAMi-core](https://github.com/Project-HAMi/HAMi-core), which is a cuda-hacking library. But MIG is also widely used across the world. A unified API for dynamic-mig and HAMi-core is needed.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.5.0/developers/dynamic-mig.md` around lines 15 - 20, The terminology cleanup in this paragraph is incomplete because the visible link text in the dynamic-mig docs still uses the lowercase hami-core reference. Update the link text in the affected paragraph to HAMi-core while keeping the existing link target and also check nearby references in the same document for consistent capitalization.i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/nvidia-device/dynamic-mig-support.md-189-191 (1)
189-191: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFix the spelling in this note.
Ampere architectis a typo here; it should readAmpere architecturefor the note to be readable.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/nvidia-device/dynamic-mig-support.md` around lines 189 - 191, The note in the MIG support doc has a spelling typo: “Ampere architect” should be corrected to “Ampere architecture” in the text under the MIG device guidance. Update the affected sentence in the documentation content so the wording is readable and accurate, keeping the rest of the note unchanged.Source: Linters/SAST tools
i18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/developers/dynamic-mig.md-14-14 (1)
14-14: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the casing cleanup here.
This sentence still uses lowercase
hami-corein both the link text and prose, so the terminology normalization is incomplete. Please change both occurrences toHAMi-core.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/developers/dynamic-mig.md` at line 14, The terminology cleanup is incomplete in the dynamic MIG docs sentence because both the link text and the surrounding prose still use lowercase hami-core. Update the text in the referenced documentation snippet so both occurrences use the normalized HAMi-core casing consistently, matching the existing HAMi naming used elsewhere in the docs.versioned_docs/version-v2.6.0/developers/dynamic-mig.md-15-15 (1)
15-15: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the casing cleanup here.
This sentence still uses lowercase
hami-corein both the link text and prose, so the terminology normalization is incomplete. Please change both occurrences toHAMi-core.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.6.0/developers/dynamic-mig.md` at line 15, The terminology cleanup in this sentence is incomplete because both the link text and the prose still use lowercase hami-core. Update the wording in the affected markdown so the reference consistently uses HAMi-core in both places, matching the rest of the document’s casing normalization.i18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/nvidia-device/dynamic-mig-support.md-180-182 (1)
180-182: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNormalize the remaining lowercase terms in the notes.
'mig'and'hami-core'are still lowercase here, which is inconsistent with the rest of the terminology cleanup in this doc. Please switch the prose toMIG/HAMi-coreso the note matches the normalized branding.Proposed fix
-2. Ampere 架构之前的 NVIDIA 设备无法使用 'mig' 模式 -3. 你不会在节点上看到任何 MIG 资源（即 `nvidia.com/mig-1g.10gb`），HAMi 对 'mig' 和 'hami-core' 节点使用统一的资源名称。 +2. Ampere 架构之前的 NVIDIA 设备无法使用 MIG 模式 +3. 你不会在节点上看到任何 MIG 资源（即 `nvidia.com/mig-1g.10gb`），HAMi 对 MIG 和 HAMi-core 节点使用统一的资源名称。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/nvidia-device/dynamic-mig-support.md` around lines 180 - 182, The note in this section still uses inconsistent lowercase branding for the terms in the prose. Update the text in the relevant note under the dynamic MIG support docs to use the normalized forms MIG and HAMi-core, and check nearby wording in the same paragraph for any remaining lowercase occurrences of these product terms.i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/nvidia-device/dynamic-mig-support.md-180-182 (1)
180-182: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNormalize the note wording here too.
These note items still quote lowercase
mig/hami-corein prose. Please switch them to the branded forms used elsewhere in this pass (MIG/HAMi-core) so the section stays consistent.Proposed fix
-2. Ampere 架构之前的 NVIDIA 设备无法使用 'mig' 模式 -3. 你不会在节点上看到任何 MIG 资源（即 `nvidia.com/mig-1g.10gb`），HAMi 对 'mig' 和 'hami-core' 节点使用统一的资源名称。 +2. Ampere 架构之前的 NVIDIA 设备无法使用 MIG 模式 +3. 你不会在节点上看到任何 MIG 资源（即 `nvidia.com/mig-1g.10gb`），HAMi 对 MIG 和 HAMi-core 节点使用统一的资源名称。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/nvidia-device/dynamic-mig-support.md` around lines 180 - 182, The note wording still uses lowercase branded terms in prose; update the items in the dynamic MIG support section to match the rest of the docs by using the consistent branded forms for MIG and HAMi-core. Locate the list entries in the dynamic MIG support content and normalize the text so the terminology is consistent throughout the section.i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/developers/dynamic-mig.md-14-19 (1)
14-19: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNormalize the intro terminology as well.
The first sentence still uses lowercase
dynamic-mig/hami-core, even though the surrounding section has been updated to the branded forms. Please align this sentence too so the terminology stays consistent.Proposed fix
-需要一个用于动态-mig 和 hami-core 的统一 API。 +需要一个用于动态 MIG 和 HAMi-core 的统一 API。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/developers/dynamic-mig.md` around lines 14 - 19, The intro text still uses inconsistent lowercase terminology for the feature and library, so update the opening sentence in the dynamic MIG doc to match the branded naming used elsewhere. Adjust the wording in the introductory paragraph so the references to dynamic MIG and HAMi Core are consistently capitalized and formatted, keeping the terminology aligned throughout the section.versioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md-7-7 (1)
7-7: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winFix the resource-request sentence.
resource.limitshould beresources.limits, and the phrasing can be tightened to:vGPU can be requested by setting "volcano.sh/vgpu-number", "volcano.sh/vgpu-cores", and "volcano.sh/vgpu-memory" in \resources.limits`.`🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md` at line 7, Fix the resource-request sentence in the vGPU example text: the path should be referred to as resources.limits, not resource.limit, and the wording should be tightened to say that vGPU can be requested by setting volcano.sh/vgpu-number, volcano.sh/vgpu-cores, and volcano.sh/vgpu-memory in resources.limits. Update the sentence in the affected markdown example so the terminology is consistent and clear.i18n/zh/docusaurus-plugin-content-docs/current/installation/how-to-use-volcano-vgpu.md-92-94 (1)
92-94: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse
resources.limitshere. The prose saysresource.limit, but the YAML example below usesresources.limits; keep the field name consistent.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/current/installation/how-to-use-volcano-vgpu.md` around lines 92 - 94, The documentation text uses the wrong field name for requesting vGPU resources, which is inconsistent with the YAML example. Update the prose in the vGPU usage section to refer to resources.limits instead of resource.limit, keeping the terminology aligned with the example and the existing vGPU resource keys like volcano.sh/vgpu-number, volcano.sh/vgpu-cores, and volcano.sh/vgpu-memory.versioned_docs/version-v2.5.1/installation/how-to-use-volcano-vgpu.md-2-2 (1)
2-2: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winCapitalize the product name in the page title.
volcano vGPUshould beVolcano vGPUto match the naming used elsewhere in the docs.Suggested fix
-title: Use volcano vGPU +title: Use Volcano vGPU🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.5.1/installation/how-to-use-volcano-vgpu.md` at line 2, The page title text is using the wrong capitalization for the product name; update the frontmatter title in this docs page so it matches the canonical “Volcano vGPU” naming used elsewhere. Make this change in the title field only, keeping the rest of the document unchanged.i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md-2-2 (1)
2-2: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winCapitalize the product name in the page title.
volcano vGPUis still lowercase here, while sibling docs useVolcano vGPU. Please update the frontmatter title for consistency.Suggested fix
-title: How to use volcano vGPU +title: How to use Volcano vGPU🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md` at line 2, The frontmatter title uses a lowercase product name, so update the title in the document metadata to match the canonical “Volcano vGPU” capitalization used by sibling docs. Locate the title field at the top of the markdown file and change only the product name casing; no other content needs to change.i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/installation/how-to-use-volcano-vgpu.md-94-96 (1)
94-96: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse
resources.limitshere.
resource.limitis not the field path used in the upstream docs, so this sentence will mislead readers.Fix
-可以通过在 resource.limit 中设置 "volcano.sh/vgpu-number"、"volcano.sh/vgpu-cores" 和 "volcano.sh/vgpu-memory" 来请求 vGPU。 +可以通过在 `resources.limits` 中设置 `volcano.sh/vgpu-number`、`volcano.sh/vgpu-cores` 和 `volcano.sh/vgpu-memory` 来请求 vGPU。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/installation/how-to-use-volcano-vgpu.md` around lines 94 - 96, The wording in the vGPU usage section uses the wrong field path, so update the sentence in the documentation content referenced by the vGPU guide to say resources.limits instead of resource.limit. Keep the rest of the explanation about volcano.sh/vgpu-number, volcano.sh/vgpu-cores, and volcano.sh/vgpu-memory unchanged, and make sure the corrected field path matches the upstream docs terminology.i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/installation/how-to-use-volcano-vgpu.md-93-95 (1)
93-95: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse
resources.limitshere.
resource.limitis not the field path used in the upstream docs, so this sentence will mislead readers.Fix
-可以通过在 resource.limit 中设置 "volcano.sh/vgpu-number"、"volcano.sh/vgpu-cores" 和 "volcano.sh/vgpu-memory" 来请求 vGPU。 +可以通过在 `resources.limits` 中设置 `volcano.sh/vgpu-number`、`volcano.sh/vgpu-cores` 和 `volcano.sh/vgpu-memory` 来请求 vGPU。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/installation/how-to-use-volcano-vgpu.md` around lines 93 - 95, The vGPU request example uses the wrong field path and should match the upstream docs. Update the sentence in the Volcano vGPU installation doc to refer to resources.limits instead of resource.limit, keeping the same listed keys ("volcano.sh/vgpu-number", "volcano.sh/vgpu-cores", and "volcano.sh/vgpu-memory") so readers are pointed to the correct configuration path.i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md-2-8 (1)
2-8: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse
resources.limitshere.
resource.limitis not the field path used in the upstream docs, so this line will mislead readers.Fix
-vGPU 可以通过在 resource.limit 中设置 "volcano.sh/vgpu-number"、"volcano.sh/vgpu-cores" 和 "volcano.sh/vgpu-memory" 来请求。 +vGPU 可以通过在 `resources.limits` 中设置 `volcano.sh/vgpu-number`、`volcano.sh/vgpu-cores` 和 `volcano.sh/vgpu-memory` 来请求。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md` around lines 2 - 8, The vGPU request field name in the translated docs is incorrect: replace the reference to resource.limit in the userguide example text with resources.limits so it matches the upstream documentation. Update the wording in the translated markdown around the vGPU description to use the correct field path consistently, keeping the existing symbols like the vGPU resource keys unchanged.i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md-7-7 (1)
7-7: 🎯 Functional Correctness | 🟡 Minor | ⚡ Quick winUse
resources.limitshere.
resource.limitis singular, but the example below uses Kubernetes'resources.limits. The current wording will mislead readers.🛠️ Suggested fix
-vGPU 可以通过在 resource.limit 中设置 "volcano.sh/vgpu-number"、"volcano.sh/vgpu-cores" 和 "volcano.sh/vgpu-memory" 来请求。 +vGPU 可以通过在 resources.limits 中设置 "volcano.sh/vgpu-number"、"volcano.sh/vgpu-cores" 和 "volcano.sh/vgpu-memory" 来请求。🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md` at line 7, The wording in this document uses the singular resource.limit, which is inconsistent with the Kubernetes field shown in the example. Update the sentence in the vGPU usage section to refer to resources.limits instead, and keep the vGPU resource keys unchanged so the text matches the example and does not mislead readers.versioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md-2-14 (1)
2-14: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the capitalization pass in this doc.
This hunk updates the title and the “Running vGPU Jobs” section, but the same file still has lowercase
vgpuin the scheduler comment and warning text, so the terminology remains inconsistent. Please normalize the remaining occurrences too.Also applies to: 94-96
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md` around lines 2 - 14, Finish the capitalization cleanup in this document by normalizing the remaining lowercase “vgpu” occurrences so the terminology matches the updated title and section headings. Update the remaining references in the scheduler comment and warning text in the same markdown file to use the same “vGPU” casing already used elsewhere, keeping the wording consistent across the doc.versioned_docs/version-v2.4.1/installation/how-to-use-volcano-vgpu.md-2-14 (1)
2-14: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the capitalization pass in this doc.
This hunk updates the title and the “Running vGPU Jobs” section, but the same file still has lowercase
vgpuin the scheduler comment and warning text, so the terminology remains inconsistent. Please normalize the remaining occurrences too.Also applies to: 94-96
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v2.4.1/installation/how-to-use-volcano-vgpu.md` around lines 2 - 14, The doc still has inconsistent vGPU capitalization in the remaining scheduler comment and warning text, so finish the terminology cleanup across this file. Update the relevant markdown in the same document to use the same vGPU capitalization style as the title and “Running vGPU Jobs” section, and verify any other occurrences of the lowercase form near the referenced Volcano vGPU content are normalized as well.versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md-2-14 (1)
2-14: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the capitalization pass in this doc.
This hunk updates the title and the “Running vGPU Jobs” section, but the same file still has lowercase
vgpuin the scheduler comment and warning text, so the terminology remains inconsistent. Please normalize the remaining occurrences too.Also applies to: 94-96
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md` around lines 2 - 14, The capitalization pass is incomplete in this doc because other references to volcano vGPU still use lowercase “vgpu.” Update the remaining terminology in the same document, including the scheduler comment and warning text mentioned in the review, so that all occurrences consistently use the same volcano vGPU capitalization as the title and “Running vGPU Jobs” section.versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/monitor.md-18-18 (1)
18-18: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winNormalize the remaining
vgpudescriptions.Line 18 is updated, but the table still mixes
vGPUand lowercasevgpuin the remaining rows. Please normalize the rest of the descriptions too.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/monitor.md` at line 18, The monitor table still has inconsistent vGPU capitalization in the remaining metric descriptions, so normalize the wording across all affected rows in the same table. Update the descriptions for the related entries in the NVIDIA GPU monitor docs to use a consistent “vGPU” style, and verify the surrounding metric names like volcano_vgpu_device_allocated_memory remain unchanged while only the human-readable descriptions are adjusted.versioned_docs/version-v1.3.0/installation/how-to-use-volcano-vgpu.md-2-14 (1)
2-14: 📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick winFinish the capitalization pass in this doc.
This hunk updates the title and the “Running vGPU Jobs” section, but the same file still has lowercase
vgpuin the scheduler comment and warning text, so the terminology remains inconsistent. Please normalize the remaining occurrences too.Also applies to: 94-96
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@versioned_docs/version-v1.3.0/installation/how-to-use-volcano-vgpu.md` around lines 2 - 14, The capitalization pass is incomplete in this doc, leaving lowercase “vgpu” in the remaining scheduler comment and warning text. Update the leftover occurrences in the volcano-vgpu installation markdown so the terminology matches the already-corrected title and “Running vGPU Jobs” section, and keep the wording consistent throughout the file.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Minor comments:
In `@docs/developers/dynamic-mig.md`:
- Line 12: The terminology cleanup is incomplete in this paragraph because the
project name still appears as lowercase hami-core. Update the prose and the link
text in the dynamic-mig document so the visible name is consistently capitalized
as HAMi-core, keeping the rest of the MIG description unchanged.
In `@i18n/zh/docusaurus-plugin-content-docs/current/developers/dynamic-mig.md`:
- Around line 12-17: The terminology cleanup in this paragraph is incomplete
because the visible text still says hami-core in the opening description and the
unified API sentence. Update the wording in the dynamic-mig doc so every
reference matches the capitalized HAMi-core form, including the sentence that
mentions the library and the related API description, while keeping the existing
link target unchanged.
In
`@i18n/zh/docusaurus-plugin-content-docs/current/installation/how-to-use-volcano-vgpu.md`:
- Around line 92-94: The documentation text uses the wrong field name for
requesting vGPU resources, which is inconsistent with the YAML example. Update
the prose in the vGPU usage section to refer to resources.limits instead of
resource.limit, keeping the terminology aligned with the example and the
existing vGPU resource keys like volcano.sh/vgpu-number, volcano.sh/vgpu-cores,
and volcano.sh/vgpu-memory.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/nvidia-device/dynamic-mig-support.md`:
- Around line 189-191: The note in the MIG support doc has a spelling typo:
“Ampere architect” should be corrected to “Ampere architecture” in the text
under the MIG device guidance. Update the affected sentence in the documentation
content so the wording is readable and accurate, keeping the rest of the note
unchanged.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md`:
- Line 2: The frontmatter title uses a lowercase product name, so update the
title in the document metadata to match the canonical “Volcano vGPU”
capitalization used by sibling docs. Locate the title field at the top of the
markdown file and change only the product name casing; no other content needs to
change.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/developers/dynamic-mig.md`:
- Line 14: The terminology cleanup is incomplete in the dynamic MIG docs
sentence because both the link text and the surrounding prose still use
lowercase hami-core. Update the text in the referenced documentation snippet so
both occurrences use the normalized HAMi-core casing consistently, matching the
existing HAMi naming used elsewhere in the docs.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/nvidia-device/dynamic-mig-support.md`:
- Around line 180-182: The note in this section still uses inconsistent
lowercase branding for the terms in the prose. Update the text in the relevant
note under the dynamic MIG support docs to use the normalized forms MIG and
HAMi-core, and check nearby wording in the same paragraph for any remaining
lowercase occurrences of these product terms.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/developers/dynamic-mig.md`:
- Around line 14-19: The intro text still uses inconsistent lowercase
terminology for the feature and library, so update the opening sentence in the
dynamic MIG doc to match the branded naming used elsewhere. Adjust the wording
in the introductory paragraph so the references to dynamic MIG and HAMi Core are
consistently capitalized and formatted, keeping the terminology aligned
throughout the section.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/installation/how-to-use-volcano-vgpu.md`:
- Around line 94-96: The wording in the vGPU usage section uses the wrong field
path, so update the sentence in the documentation content referenced by the vGPU
guide to say resources.limits instead of resource.limit. Keep the rest of the
explanation about volcano.sh/vgpu-number, volcano.sh/vgpu-cores, and
volcano.sh/vgpu-memory unchanged, and make sure the corrected field path matches
the upstream docs terminology.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/nvidia-device/dynamic-mig-support.md`:
- Around line 180-182: The note wording still uses lowercase branded terms in
prose; update the items in the dynamic MIG support section to match the rest of
the docs by using the consistent branded forms for MIG and HAMi-core. Locate the
list entries in the dynamic MIG support content and normalize the text so the
terminology is consistent throughout the section.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md`:
- Around line 2-8: The vGPU request field name in the translated docs is
incorrect: replace the reference to resource.limit in the userguide example text
with resources.limits so it matches the upstream documentation. Update the
wording in the translated markdown around the vGPU description to use the
correct field path consistently, keeping the existing symbols like the vGPU
resource keys unchanged.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/installation/how-to-use-volcano-vgpu.md`:
- Around line 93-95: The vGPU request example uses the wrong field path and
should match the upstream docs. Update the sentence in the Volcano vGPU
installation doc to refer to resources.limits instead of resource.limit, keeping
the same listed keys ("volcano.sh/vgpu-number", "volcano.sh/vgpu-cores", and
"volcano.sh/vgpu-memory") so readers are pointed to the correct configuration
path.
In
`@i18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md`:
- Line 7: The wording in this document uses the singular resource.limit, which
is inconsistent with the Kubernetes field shown in the example. Update the
sentence in the vGPU usage section to refer to resources.limits instead, and
keep the vGPU resource keys unchanged so the text matches the example and does
not mislead readers.
In `@versioned_docs/version-v1.3.0/installation/how-to-use-volcano-vgpu.md`:
- Around line 2-14: The capitalization pass is incomplete in this doc, leaving
lowercase “vgpu” in the remaining scheduler comment and warning text. Update the
leftover occurrences in the volcano-vgpu installation markdown so the
terminology matches the already-corrected title and “Running vGPU Jobs” section,
and keep the wording consistent throughout the file.
In
`@versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md`:
- Around line 2-14: The capitalization pass is incomplete in this doc because
other references to volcano vGPU still use lowercase “vgpu.” Update the
remaining terminology in the same document, including the scheduler comment and
warning text mentioned in the review, so that all occurrences consistently use
the same volcano vGPU capitalization as the title and “Running vGPU Jobs”
section.
In `@versioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/monitor.md`:
- Line 18: The monitor table still has inconsistent vGPU capitalization in the
remaining metric descriptions, so normalize the wording across all affected rows
in the same table. Update the descriptions for the related entries in the NVIDIA
GPU monitor docs to use a consistent “vGPU” style, and verify the surrounding
metric names like volcano_vgpu_device_allocated_memory remain unchanged while
only the human-readable descriptions are adjusted.
In `@versioned_docs/version-v2.4.1/installation/how-to-use-volcano-vgpu.md`:
- Around line 2-14: The doc still has inconsistent vGPU capitalization in the
remaining scheduler comment and warning text, so finish the terminology cleanup
across this file. Update the relevant markdown in the same document to use the
same vGPU capitalization style as the title and “Running vGPU Jobs” section, and
verify any other occurrences of the lowercase form near the referenced Volcano
vGPU content are normalized as well.
In
`@versioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.md`:
- Around line 2-14: Finish the capitalization cleanup in this document by
normalizing the remaining lowercase “vgpu” occurrences so the terminology
matches the updated title and section headings. Update the remaining references
in the scheduler comment and warning text in the same markdown file to use the
same “vGPU” casing already used elsewhere, keeping the wording consistent across
the doc.
In `@versioned_docs/version-v2.5.0/developers/dynamic-mig.md`:
- Around line 15-20: The terminology cleanup in this paragraph is incomplete
because the visible link text in the dynamic-mig docs still uses the lowercase
hami-core reference. Update the link text in the affected paragraph to HAMi-core
while keeping the existing link target and also check nearby references in the
same document for consistent capitalization.
In
`@versioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.md`:
- Line 7: Fix the resource-request sentence in the vGPU example text: the path
should be referred to as resources.limits, not resource.limit, and the wording
should be tightened to say that vGPU can be requested by setting
volcano.sh/vgpu-number, volcano.sh/vgpu-cores, and volcano.sh/vgpu-memory in
resources.limits. Update the sentence in the affected markdown example so the
terminology is consistent and clear.
In `@versioned_docs/version-v2.5.1/developers/dynamic-mig.md`:
- Around line 15-20: The paragraph still contains a lowercase visible reference
to hami-core in the dynamic-mig documentation. Update the linked text in the
intro sentence near the dynamic-mig discussion to use HAMi-core consistently,
while keeping the existing link target intact. Verify the terminology cleanup is
complete by checking the surrounding prose in this section for any remaining
lowercase hami-core mentions.
In `@versioned_docs/version-v2.5.1/installation/how-to-use-volcano-vgpu.md`:
- Line 2: The page title text is using the wrong capitalization for the product
name; update the frontmatter title in this docs page so it matches the canonical
“Volcano vGPU” naming used elsewhere. Make this change in the title field only,
keeping the rest of the document unchanged.
In `@versioned_docs/version-v2.6.0/developers/dynamic-mig.md`:
- Line 15: The terminology cleanup in this sentence is incomplete because both
the link text and the prose still use lowercase hami-core. Update the wording in
the affected markdown so the reference consistently uses HAMi-core in both
places, matching the rest of the document’s casing normalization.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 2d61711d-1300-4a11-a74b-494a2e1778de
📒 Files selected for processing (101)
docs/developers/dynamic-mig.mddocs/developers/protocol.mddocs/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/current/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/current/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/current/userguide/nvidia-device/dynamic-resource-allocation.mdi18n/zh/docusaurus-plugin-content-docs/current/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/current/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/current/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/get-started/nginx-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/installation/uninstall.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/monitor.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.4.1/get-started/nginx-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.4.1/installation/uninstall.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/get-started/nginx-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/get-started/nginx-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/installation/uninstall.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/userguide/mthreads-device/enable-mthreads-gpu-sharing.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.5.1/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/get-started/nginx-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.6.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/installation/uninstall.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/installation/uninstall.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/nvidia-device/dynamic-mig-support.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/nvidia-device/dynamic-resource-allocation.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.8.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/developers/dynamic-mig.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/installation/how-to-use-volcano-vgpu.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/userguide/benchmark.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/userguide/nvidia-device/dynamic-resource-allocation.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/userguide/nvidia-device/examples/dynamic-mig-example.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdi18n/zh/docusaurus-plugin-content-docs/version-v2.9.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdversioned_docs/version-v1.3.0/developers/dynamic-mig.mdversioned_docs/version-v1.3.0/installation/how-to-use-volcano-vgpu.mdversioned_docs/version-v1.3.0/userguide/mthreads-device/enable-mthreads-gpu-sharing.mdversioned_docs/version-v1.3.0/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdversioned_docs/version-v1.3.0/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.4.1/developers/dynamic-mig.mdversioned_docs/version-v2.4.1/installation/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.4.1/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.4.1/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.5.0/developers/dynamic-mig.mdversioned_docs/version-v2.5.0/installation/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.5.0/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.5.0/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.5.1/developers/dynamic-mig.mdversioned_docs/version-v2.5.1/installation/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.5.1/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.5.1/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v2.5.1/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.6.0/developers/dynamic-mig.mdversioned_docs/version-v2.6.0/installation/how-to-use-volcano-vgpu.mdversioned_docs/version-v2.6.0/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.6.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v2.6.0/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.7.0/developers/dynamic-mig.mdversioned_docs/version-v2.7.0/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/examples/default-use.mdversioned_docs/version-v2.7.0/userguide/volcano-vgpu/nvidia-gpu/monitor.mdversioned_docs/version-v2.8.0/developers/dynamic-mig.mdversioned_docs/version-v2.8.0/userguide/nvidia-device/examples/dynamic-mig-example.mdversioned_docs/version-v2.9.0/developers/dynamic-mig.mdversioned_docs/version-v2.9.0/userguide/nvidia-device/examples/dynamic-mig-example.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Follow up on the review from #562 and #563. Fixes wrong casing for MIG, NVIDIA, vGPU, HAMi in prose text across docs, versioned_docs, and zh translations, all versions.
Code, config, and CLI literal values are left as is, only prose text changed.
Summary by CodeRabbit