Skip to content

docs(dynamo_run): fix typos and improve clarity #1603

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 6 commits into from

Conversation

ShriyashP
Copy link
Contributor

@ShriyashP ShriyashP commented Jun 21, 2025

Fix Documentation Typos in dynamo_run.md

Description

This PR addresses minor typos and formatting issues in the dynamo_run.md documentation to improve readability.

Changes Made

  • Fixed inconsistent capitalization: "HUgging Face" → "Hugging Face"
  • Fixed verb agreement: "automatically downloads" → "automatically download"

Type of Change

  • Documentation improvement
  • Bug fix (formatting corrections)

Checklist

  • Changes are documentation-only
  • Commit includes DCO sign-off
  • PR follows project guidelines for concise changes
  • No functional code changes

Testing

No testing required - these are purely documentation formatting fixes with no impact on functionality.

Summary by CodeRabbit

  • Documentation
    • Improved formatting and readability of the documentation for the dynamo run command.
    • Clarified instructions and reworded sections for better understanding.
    • Corrected minor typos and enhanced visual separation of examples and code blocks.

ShriyashP and others added 3 commits June 16, 2025 20:19
Signed-off-by: Shriyash.Patil <shriyash81@gmail.com>
- Fix inconsistent capitalization of 'Hugging Face'
- Fix verb agreement: 'downloads' -> 'download'

These changes improve documentation readability with no functional impact.

Signed-off-by: Shriyash.Patil <shriyash81@gmail.com>
Copy link

copy-pr-bot bot commented Jun 21, 2025

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

Copy link

👋 Hi ShriyashP! Thank you for contributing to ai-dynamo/dynamo.

Just a reminder: The NVIDIA Test Github Validation CI runs an essential subset of the testing framework to quickly catch errors.Your PR reviewers may elect to test the changes comprehensively before approving your changes.

🚀

@github-actions github-actions bot added the external-contribution Pull request is from an external contributor label Jun 21, 2025
Copy link
Contributor

coderabbitai bot commented Jun 21, 2025

Walkthrough

The documentation for the dynamo run command was revised to enhance formatting, readability, and textual clarity. Changes include improved spacing, consistent indentation, better separation of code blocks and lists, and minor typo corrections. No functional instructions or code snippets were altered.

Changes

File(s) Change Summary
docs/guides/dynamo_run.md Improved formatting, spacing, indentation, typo fixes, and clarified explanations for better readability. No functional changes.

Possibly related PRs

Poem

In the docs where commands are spun,
New lines and spaces have begun.
Clarity hops from block to list,
Typos fixed, no steps are missed.
Now guides are neat, a joy to read—
A rabbit’s work, tidy indeed!
🐇✨


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (13)
docs/guides/dynamo_run.md (13)

34-35: Fix verb agreement in instruction
Change “and starts it in interactive text mode” to “and start it in interactive text mode” for grammatical correctness.


61-61: Convert bare URL to markdown link
Replace the bare URL with a markdown link (e.g., [Llama-3.2-3B-Instruct-GGUF](https://huggingface.co/bartowski/Llama-3.2-3B-Instruct-GGUF)) to satisfy MD034 and improve consistency.


66-66: Add language specifier to fenced code block
Specify a language (e.g., bash) for this code fence to enable syntax highlighting (MD040).


74-75: Use heading instead of emphasis
Convert _Text interface_ to a proper subheading (e.g., #### Text interface) instead of italic for clarity and accessibility.


80-81: Replace emphasis with heading
Change _HTTP interface_ to a heading (#### HTTP interface) to maintain consistent styling.


88-89: Use heading for list title
Convert _List the models_ into a heading (#### List the models) to align with other section titles.


94-94: Use heading instead of italic for section
Replace _Send a request_ with a heading (#### Send a request) for consistency.


128-131: Refine list punctuation and style
Add a comma after “Usually,” in the first bullet for clarity and ensure code‐style backticks around Namespace, Component, Endpoint, and Instance are consistent.


176-176: Improve list formatting for “or”
The standalone **or** breaks the numbered list. Merge it into the preceding item or indent it as a sub-point to preserve numbering.


195-195: Align indentation of explanatory text
The line “If you patched locally (instead of installing ai-dynamo-vllm)…” should align under the surrounding code block context for readability.


232-232: Add language to code fence
Mark this fence as bash (or appropriate) to enable syntax highlighting (MD040).


240-240: Specify language for code block
Add a language label (e.g., bash) to this fence to satisfy MD040.


267-267: Add language specifiers across multiple fences
Several newly formatted code blocks at the listed lines lack a language label. Please specify languages (bash, python, json, etc.) for proper syntax highlighting.

Also applies to: 273-273, 292-292, 392-392, 429-429, 543-543, 551-551, 561-561, 665-665

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9622caa and 60ef75c.

📒 Files selected for processing (1)
  • docs/guides/dynamo_run.md (22 hunks)
🧰 Additional context used
🪛 markdownlint-cli2 (0.17.2)
docs/guides/dynamo_run.md

36-36: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


61-61: Bare URL used
null

(MD034, no-bare-urls)


62-62: Bare URL used
null

(MD034, no-bare-urls)


66-66: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


74-74: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


76-76: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


80-80: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


82-82: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


88-88: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


90-90: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


94-94: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)


139-139: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


232-232: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


240-240: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


267-267: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


273-273: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


292-292: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


392-392: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


429-429: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


543-543: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


551-551: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)


561-561: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

🪛 LanguageTool
docs/guides/dynamo_run.md

[typographical] ~128-~128: Consider adding a comma after ‘Usually’ for more clarity.
Context: ...ger system. - Namespace: A pipeline. Usually a model. e.g "llama_8b". Just a name. -...

(RB_LY_COMMA)


[uncategorized] ~548-~548: Possible missing comma found.
Context: ...er in output.jsonl. At the end of the run some statistics are printed. The output...

(AI_HYDRA_LEO_MISSING_COMMA)


[uncategorized] ~653-~653: Loose punctuation mark.
Context: ...ke the following kwargs: - model_name: The name to call the model. Your incomi...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~654-~654: Loose punctuation mark.
Context: ...r the GGUF file name. - context_length: Max model length in tokens. Defaults to...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~655-~655: Loose punctuation mark.
Context: ...o fit into VRAM. - kv_cache_block_size: Size of a KV block for the engine, in t...

(UNLIKELY_OPENING_PUNCTUATION)


[uncategorized] ~665-~665: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...hello_world/server_sglang_tok.py) More fully-featured Backend engines (used by dynamo-run):...

(HYPHENATED_LY_ADVERB_ADJECTIVE)

⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: Build and Test - vllm
🔇 Additional comments (1)
docs/guides/dynamo_run.md (1)

10-10: Approve: Blank line before usage block
Adding a blank line before the Usage: code block improves readability.

Copy link
Contributor

coderabbitai bot commented Jun 21, 2025

Walkthrough

The documentation for the dynamo run command was revised to improve formatting, readability, and clarity. Changes include enhanced spacing, restructured bullet points, corrected typos, and refined sentence structure. No code or functional modifications were made; all updates are editorial and pertain solely to the documentation.

Changes

File(s) Change Summary
docs/guides/dynamo_run.md Improved formatting, clarified explanations, corrected minor typos, and enhanced readability.

Possibly related PRs

Poem

In the meadow of docs, a rabbit hopped through,
Tidying spaces and fixing a typo or two.
Italics and bullets now neatly aligned,
Clarity and order blissfully combined.
No code was disturbed, just words set to shine—
A guide now as crisp as a carrot on the vine! 🥕


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 1

🔭 Outside diff range comments (1)
docs/guides/dynamo_run.md (1)

172-177: Restructure ‘either/or’ list for consistency
Embedding or as a bold line breaks the ordered list structure. Turn it into a second list item:

-1. Install Dynamo's vllm branch:
-   ```bash
-   uv pip install ai-dynamo-vllm
-   ```
-   **or**
-1. Install upstream vllm 0.8.4:
-   ```bash
-   uv pip install vllm==0.8.4
-   ```
+1. Install Dynamo's vllm branch:
+   ```bash
+   uv pip install ai-dynamo-vllm
+   ```
+2. Install upstream vllm 0.8.4:
+   ```bash
+   uv pip install vllm==0.8.4
+   ```
🧹 Nitpick comments (2)
docs/guides/dynamo_run.md (2)

60-63: Convert bare URLs to markdown links
Raw URLs reduce readability and can’t carry descriptive text. Wrap model references in markdown links. Example:

-One of the models available from Hugging Face should be high quality and fast on almost any machine: https://huggingface.co/bartowski/Llama-3.2-3B-Instruct-GGUF
+One high-quality model available on Hugging Face is [bartowski/Llama-3.2-3B-Instruct-GGUF](https://huggingface.co/bartowski/Llama-3.2-3B-Instruct-GGUF), which runs efficiently on most machines.

195-200: Clarify patch‐reversion instructions and formatting
The note about undoing the local patch would be clearer as a subheading with consistent indentation, and code fences should specify the diff language.

##### Undo local vllm patch (if not using `ai-dynamo-vllm`)
1. Open `platforms/__init__.py` in your patched vllm installation.
2. Revert the version assignment:
   ```diff
-  #vllm_version = version("ai_dynamo_vllm")
-  vllm_version = version("vllm")
+  #vllm_version = version("ai_dynamo_vllm")
+  vllm_version = version("vllm")

</blockquote></details>

</blockquote></details>

<details>
<summary>📜 Review details</summary>

**Configuration used: .coderabbit.yaml**
**Review profile: CHILL**
**Plan: Pro**


<details>
<summary>📥 Commits</summary>

Reviewing files that changed from the base of the PR and between 9622caaa7bf7429ef3c943c6f5659531808178d8 and 60ef75c18250a79d9a89101fbc26177225b44a25.

</details>

<details>
<summary>📒 Files selected for processing (1)</summary>

* `docs/guides/dynamo_run.md` (22 hunks)

</details>

<details>
<summary>🧰 Additional context used</summary>

<details>
<summary>🪛 markdownlint-cli2 (0.17.2)</summary>

<details>
<summary>docs/guides/dynamo_run.md</summary>

36-36: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

61-61: Bare URL used
null

(MD034, no-bare-urls)

---

62-62: Bare URL used
null

(MD034, no-bare-urls)

---

66-66: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

74-74: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

76-76: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

80-80: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

82-82: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

88-88: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

90-90: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

94-94: Emphasis used instead of a heading
null

(MD036, no-emphasis-as-heading)

---

139-139: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

232-232: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

240-240: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

267-267: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

273-273: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

292-292: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

392-392: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

429-429: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

543-543: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

551-551: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

---

561-561: Fenced code blocks should have a language specified
null

(MD040, fenced-code-language)

</details>

</details>
<details>
<summary>🪛 LanguageTool</summary>

<details>
<summary>docs/guides/dynamo_run.md</summary>

[typographical] ~128-~128: Consider adding a comma after ‘Usually’ for more clarity.
Context: ...ger system.  - _Namespace_: A pipeline. Usually a model. e.g "llama_8b". Just a name. -...

(RB_LY_COMMA)

---

[uncategorized] ~548-~548: Possible missing comma found.
Context: ...er in `output.jsonl`. At the end of the run some statistics are printed. The output...

(AI_HYDRA_LEO_MISSING_COMMA)

---

[uncategorized] ~653-~653: Loose punctuation mark.
Context: ...ke the following kwargs:  - `model_name`: The name to call the model. Your incomi...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~654-~654: Loose punctuation mark.
Context: ...r the GGUF file name. - `context_length`: Max model length in tokens. Defaults to...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~655-~655: Loose punctuation mark.
Context: ...o fit into VRAM. - `kv_cache_block_size`: Size of a KV block for the engine, in t...

(UNLIKELY_OPENING_PUNCTUATION)

---

[uncategorized] ~665-~665: Although a hyphen is possible, it is not necessary in a compound modifier in which the first word is an adverb that ends in ‘ly’.
Context: ...hello_world/server_sglang_tok.py)  More fully-featured Backend engines (used by `dynamo-run`):...

(HYPHENATED_LY_ADVERB_ADJECTIVE)

</details>

</details>

</details>

<details>
<summary>⏰ Context from checks skipped due to timeout of 90000ms (1)</summary>

* GitHub Check: Build and Test - vllm

</details>

<details>
<summary>🔇 Additional comments (1)</summary><blockquote>

<details>
<summary>docs/guides/dynamo_run.md (1)</summary>

`10-13`: **Add blank line before usage code block**  
The inserted blank line before the fenced code block under “Usage:” improves visual separation and readability.

</details>

</blockquote></details>

</details>

<!-- This is an auto-generated comment by CodeRabbit for review status -->

@ShriyashP ShriyashP changed the title Fix dynamo run typos docs(dynamo_run): fix typos and improve clarity Jun 21, 2025
@github-actions github-actions bot added the docs label Jun 21, 2025
@ShriyashP ShriyashP closed this Jun 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
docs external-contribution Pull request is from an external contributor size/M
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant