Minor updates to Dynamo blog from NVIDIA marketing review #5577
Conversation
There was a problem hiding this comment.
Pull request overview
This PR contains minor marketing-driven updates to the Dynamo blog post based on NVIDIA's review. The changes primarily focus on improving product naming accuracy, enhancing clarity, and updating the example scenario to be more specific to AKS deployment contexts.
Changes:
- Updated product naming to be more precise (Azure ND GB200-v6 VMs accelerated by NVIDIA GB200 NVL72)
- Refined language for better clarity and conciseness
- Modified the example scenario to emphasize AKS mission-critical workloads
- Replaced the image file from PNG to JPG format
Reviewed changes
Copilot reviewed 1 out of 3 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| website/blog/2026-01-22-dynamo-on-aks-part-2/index.md | Updates product naming, improves clarity, and refines example scenario with AKS context |
| website/blog/2026-01-22-dynamo-on-aks-part-2/disag-serving-with-dynamo.png | Old image file removed (replaced with JPG version) |
Co-authored-by: Copilot <[email protected]>
| NVIDIA GB200 NVL72, achieving a | ||
| staggering **1.2M tokens per second** across 10 nodes using NVIDIA Dynamo. | ||
| Today, we’re shifting focus from raw throughput to **developer velocity** and | ||
| Today, we shift focus from raw throughput to **developer velocity** and |
There was a problem hiding this comment.
Removing the contraction "we're" in favor of "we" goes against the Microsoft Style Guide, which recommends using common contractions like "it's", "you're", "we're", and "let's" to maintain a conversational, friendly tone. Consider keeping "we're shifting" for better readability and alignment with Microsoft's voice guidelines.
| Today, we shift focus from raw throughput to **developer velocity** and | |
| Today, we're shifting focus from raw throughput to **developer velocity** and |
| [**Dynamo Planner**](https://github.com/ai-dynamo/dynamo/blob/main/docs/planner/sla_planner.md) | ||
| and | ||
| [**Dynamo Profiler**](https://github.com/ai-dynamo/dynamo/tree/main/benchmarks/profiler) | ||
| remove the guesswork from performance tuning on Azure Kubernetes Service (AKS). |
There was a problem hiding this comment.
The acronym "(AKS)" is spelled out here even though "AKS" is already used multiple times earlier in the document (in the title and throughout). This creates unnecessary redundancy. Since AKS is already established in the context, you can simply write "remove the guesswork from performance tuning" without the full expansion.
| remove the guesswork from performance tuning on Azure Kubernetes Service (AKS). | |
| remove the guesswork from performance tuning on AKS. |
1 participant
No description provided.