Skip to content

[docs] fix misspellings & typos#18276

Merged
b8zhong merged 3 commits intosgl-project:mainfrom
rinbaro:docs-misspellings
Feb 5, 2026
Merged

[docs] fix misspellings & typos#18276
b8zhong merged 3 commits intosgl-project:mainfrom
rinbaro:docs-misspellings

Conversation

@rinbaro
Copy link
Contributor

@rinbaro rinbaro commented Feb 5, 2026

Motivation

To fix misspellings for more professional docs.

None of the misspellings seem intentional.

@github-actions github-actions bot added documentation Improvements or additions to documentation amd deepseek npu labels Feb 5, 2026
@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @rinbaro, 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 improving the overall quality and professionalism of the project's documentation. It addresses a series of misspellings, grammatical inaccuracies, and inconsistent terminology found across multiple markdown files, ensuring a more polished and reliable resource for users and developers.

Highlights

  • Documentation Clarity: Corrected numerous spelling and grammatical errors across various documentation files to enhance readability and professionalism.
  • Consistency in Terminology: Standardized terms like "builtin" and "SGLang" for consistency throughout the documentation.
  • Code Example Accuracy: Updated code snippets in documentation to fix minor syntax errors and improve clarity, such as in deepseek_v3.md.

🧠 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.

Changelog
  • docs/advanced_features/dp_for_multi_modal_encoder.md
    • Corrected "deocoder" to "decoder".
  • docs/advanced_features/server_arguments.md
    • Changed "buliltin" to "builtin" in two instances.
  • docs/basic_usage/deepseek_v3.md
    • Corrected "an city" to "a city" in tool descriptions.
    • Fixed "Hows" to "How's" in user message examples.
  • docs/basic_usage/glmv.md
    • Improved sentence structure from "on. and using" to "on, and use".
    • Corrected "likes" to "like" when referring to an example.
  • docs/basic_usage/gpt_oss.md
    • Corrected "helfpul" to "helpful" in assistant instructions (two occurrences).
  • docs/basic_usage/sampling_params.md
    • Corrected "structal tag" to "structural tag".
  • docs/developer_guide/bench_serving.md
    • Corrected --model mode-name to --model model-name.
  • docs/developer_guide/benchmark_and_profiling.md
    • Fixed punctuation: "correctly ." to "correctly.".
  • docs/developer_guide/development_guide_using_docker.md
    • Corrected "Monting" to "Mounting" in an example description.
  • docs/developer_guide/setup_github_runner.md
    • Changed "GitHub Action" to "GitHub Actions" in the title.
  • docs/platforms/amd_gpu.md
    • Added "to" in "how run SGLang" to make it "how to run SGLang".
  • docs/platforms/ascend_contribution_guide.md
    • Capitalized "We" in "we recommend" for proper sentence start.
  • docs/platforms/ascend_npu_best_practice.md
    • Corrected "Ascend Npu" to "Ascend NPU" for consistent capitalization.
  • docs/references/environment_variables.md
    • Corrected "algorithom" to "algorithm".
  • docs/references/multi_node_deployment/lws_pd/lws_pd_deploy.md
    • Corrected "SGlang" to "SGLang" for consistent capitalization.
  • docs/references/post_training_integration.md
    • Corrected "maxium-powered" to "maximum-powered".
    • Corrected "design parternes" to "design partners".
  • docs/references/production_request_trace.md
    • Corrected "SGlang" to "SGLang" for consistent capitalization.
  • docs/supported_models/mindspore_models.md
    • Changed "Offline infer" to "Offline inference" in heading and description.
Activity
  • No human activity (comments, reviews, etc.) has been recorded for this pull request yet.
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.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

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 fixes several misspellings and typos across various documentation files, improving their overall quality and professionalism. The changes are correct and well-spotted. I've added a couple of minor suggestions to further enhance clarity in two of the documents.

b8zhong and others added 2 commits February 4, 2026 22:32
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
@b8zhong b8zhong enabled auto-merge (squash) February 5, 2026 03:33
@b8zhong b8zhong merged commit de6a032 into sgl-project:main Feb 5, 2026
46 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

amd deepseek documentation Improvements or additions to documentation npu

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants