dstackai · peterschmidt85 · Sep 4, 2026 · Sep 4, 2026 · Sep 4, 2026 · Sep 7, 2026
diff --git a/mkdocs/blog/posts/benchmark-amd-containers-and-partitions.md b/mkdocs/blog/posts/benchmark-amd-containers-and-partitions.md
@@ -215,7 +215,7 @@ taskset -c 0-31 ./ib_write_bw -d rocep28s0 -F -a --report_gbits -q $SERVER_IP_AD
 
 #### Containers
 
-For the container experiments we used a `dstack`’s [distributed task](../../docs/concepts/tasks.md#distributed-tasks).
+For the container experiments we used a `dstack`’s [multi-node task](../../docs/concepts/tasks.md#nodes).
 
 **RCCL tests**
 

diff --git a/mkdocs/blog/posts/digitalocean-and-amd-dev-cloud.md b/mkdocs/blog/posts/digitalocean-and-amd-dev-cloud.md
@@ -139,7 +139,7 @@ $ dstack apply -f examples/models/gpt-oss/120b.dstack.yml
 </div>
 
 > If you prefer to use bare-metal clusters with `dstack`, you can create an [SSH fleet](../../docs/concepts/fleets.md#ssh-fleets).
-> This way, you’ll be able to run [distributed tasks](../../docs/concepts/tasks.md#distributed-tasks) efficiently across the cluster.
+> This way, you’ll be able to run [multi-node tasks](../../docs/concepts/tasks.md#nodes) efficiently across the cluster.
 
 !!! info "What's next?"
     1. Check [Quickstart](../../docs/quickstart.md)

diff --git a/mkdocs/blog/posts/gpu-health-checks.md b/mkdocs/blog/posts/gpu-health-checks.md
@@ -51,7 +51,7 @@ A healthy instance is ready for workloads. A warning means you should monitor it
 
 This release focuses on passive checks using DCGM background health checks. These run continuously and do not interrupt workloads.
 
-For active checks today, you can run [NCCL/RCCL tests](../../docs/examples/clusters/nccl-rccl-tests.md) as a [distributed task](../../docs/concepts/tasks.md#distributed-tasks) to verify GPU-to-GPU communication and bandwidth across a fleet. Active tests like these can reveal network or interconnect issues that passive monitoring might miss. More built-in support for active diagnostics is planned.
+For active checks today, you can run [NCCL/RCCL tests](../../docs/examples/clusters/nccl-rccl-tests.md) as a [multi-node task](../../docs/concepts/tasks.md#nodes) to verify GPU-to-GPU communication and bandwidth across a fleet. Active tests like these can reveal network or interconnect issues that passive monitoring might miss. More built-in support for active diagnostics is planned.
 
 ## Supported backends
 

diff --git a/mkdocs/blog/posts/hotaisle.md b/mkdocs/blog/posts/hotaisle.md
@@ -103,7 +103,7 @@ $ dstack apply -f .dstack.yml
 Currently, `dstack` supports 1xGPU Hot Aisle VMs. Support for 8xGPU VMs will be added once Hot Aisle supports it.
 
 > If you prefer to use Hot Aisle’s bare-metal 8-GPU clusters with dstack, you can create an [SSH fleet](../../docs/concepts/fleets.md#ssh-fleets).
-> This way, you’ll be able to run [distributed tasks](../../docs/concepts/tasks.md#distributed-tasks) efficiently across the cluster.
+> This way, you’ll be able to run [multi-node tasks](../../docs/concepts/tasks.md#nodes) efficiently across the cluster.
 
 !!! info "What's next?"
     1. Check [Quickstart](../../docs/quickstart.md)

diff --git a/mkdocs/blog/posts/kubernetes-beta.md b/mkdocs/blog/posts/kubernetes-beta.md
@@ -128,12 +128,12 @@ Dev environments support many [different options](../../docs/concepts/dev-enviro
 
 ## Running distributed training
 
-Distributed training can be performed in `dstack` using [distributed tasks](../../docs/concepts/tasks.md#distributed-tasks). 
+Distributed training can be performed in `dstack` using [multi-node tasks](../../docs/concepts/tasks.md#nodes). 
 The configuration is similar to a dev environment, except it runs across multiple nodes.
 
 ### Creating a cluster fleet
 
-Before running a distributed task, create a fleet with `placement` set to `cluster`:
+Before running a multi-node task, create a fleet with `placement` set to `cluster`:
 
 <div editor-title="examples/misc/fleets/.dstack.yml">
 
@@ -172,11 +172,11 @@ Provisioning...
 
 </div>
 
-Once the fleet is created, you can run distributed tasks on it.
+Once the fleet is created, you can run multi-node tasks on it.
 
 ### NCCL tests example
 
-Below is an example of using distributed tasks to run NCCL tests.
+Below is an example of using multi-node tasks to run NCCL tests.
 It also demonstrates how to use mpirun with `dstack`:
 
 <div editor-title="examples/clusters/nccl-tests/.dstack.yml">

diff --git a/mkdocs/blog/posts/nebius-in-dstack-sky.md b/mkdocs/blog/posts/nebius-in-dstack-sky.md
@@ -101,7 +101,7 @@ $ dstack apply -f my-cluster.dstack.yml
 
 </div>
 
-Once the fleet is ready, you can run [distributed tasks](../../docs/concepts/tasks.md#distributed-tasks). 
+Once the fleet is ready, you can run [multi-node tasks](../../docs/concepts/tasks.md#nodes). 
 `dstack` automatically configures drivers, networking, and fast GPU-to-GPU interconnect.
 
 To learn more, see the [clusters](../../docs/examples/clusters/nebius.md) guide.

diff --git a/mkdocs/blog/posts/nebius.md b/mkdocs/blog/posts/nebius.md
@@ -101,7 +101,7 @@ $ dstack apply -f .dstack.yml
 </div>
 
 The new `nebius` backend supports CPU and GPU instances, [fleets](../../docs/concepts/fleets.md), 
-[distributed tasks](../../docs/concepts/tasks.md#distributed-tasks), and more. 
+[multi-node tasks](../../docs/concepts/tasks.md#nodes), and more. 
 
 > Support for [network volumes](../../docs/concepts/volumes.md#network-volumes) and accelerated cluster 
 interconnects is coming soon.

diff --git a/mkdocs/blog/posts/nvidia-dynamo.md b/mkdocs/blog/posts/nvidia-dynamo.md
@@ -29,7 +29,7 @@ Dynamo brings together disaggregated serving, intelligent routing, KV cache mana
 
 ## PD disaggregation with dstack
 
-To deploy NVIDIA Dynamo with PD disaggregation, define a [service](../../docs/concepts/services.md) with three [replica groups](../../docs/concepts/services.md#replicas-and-scaling):
+To deploy NVIDIA Dynamo with PD disaggregation, define a [service](../../docs/concepts/services.md) with three [replica groups](../../docs/concepts/services.md#replica-groups):
 
 - a Dynamo router
 - prefill workers

diff --git a/mkdocs/blog/posts/sglang-router.md b/mkdocs/blog/posts/sglang-router.md
@@ -121,7 +121,7 @@ $ dstack apply -f gateway.dstack.yml
 
 Once the gateway has a hostname, update your domain’s DNS settings by adding a record for `*.<gateway domain>`.
 
-After that, if you configure [replicas and scaling](../../docs/concepts/services.md#replicas-and-scaling), the gateway will automatically scale the number of replicas and route traffic across them.
+After that, if you configure [replicas and scaling](../../docs/concepts/services.md#scaling), the gateway will automatically scale the number of replicas and route traffic across them.
 
 ### Router
 

diff --git a/mkdocs/blog/posts/volumes-on-runpod.md b/mkdocs/blog/posts/volumes-on-runpod.md
@@ -131,7 +131,7 @@ In this case, `dstack` attaches the specified volume to each new replica. This e
 once, reducing cold start time in proportion to the model size.
 
 A notable feature of Runpod is that volumes can be attached to multiple containers simultaneously. This capability is
-particularly useful for auto-scalable services or distributed tasks.
+particularly useful for auto-scalable services or multi-node tasks.
 
 Using [volumes](../../docs/concepts/volumes.md) not only optimizes inference cold start times but also enhances the
 efficiency of data and model checkpoint loading during training and fine-tuning.

diff --git a/mkdocs/docs/concepts/fleets.md b/mkdocs/docs/concepts/fleets.md
@@ -136,7 +136,7 @@ Backend fleets support [many options](../reference/dstack.yml/fleet.md); see som
 
 Both [backend fleets](#backend-fleet) and [SSH fleets](#ssh-fleet) allow the `placement` property to be set to `cluster`. 
 
-This property ensures that instances are interconnected. This is required for running [distributed tasks](tasks.md#distributed-tasks).
+This property ensures that instances are interconnected. This is required for running [multi-node tasks](tasks.md#nodes).
 
 === "Backend fleets"
     Backend fleets allow to provision interconnected clusters across supported backends.
@@ -405,8 +405,8 @@ For example, with 8 GPUs, 128 CPUs, and 2TB RAM, setting `blocks` to `8` gives e
 
 Set `blocks` to `auto` to match the number of blocks to the number of GPUs.
 
-!!! info "Distributed tasks"
-    Distributed tasks require exclusive access to all host resources and therefore must use all blocks on each node.
+!!! info "Multi-node tasks"
+    Multi-node tasks require exclusive access to all host resources and therefore must use all blocks on each node.
 
 ### SSH config