[Docs] Fix some of the broken links

docs/docs/concepts/pools.md

@@ -93,7 +93,7 @@ $ dstack pool add-ssh -i ~/.ssh/id_rsa ubuntu@54.73.155.119 \
 The `--network` argument accepts the IP address range (CIDR) of the private network of the instance.
 
 Once you've added multiple instances with the same network value, you can use them as a cluster to run
-[multi-node tasks](../reference/dstack.yml/task.md#_nodes).
+[multi-node tasks](../reference/dstack.yml/task.md#distributed-tasks).
 
 ## Removing instances
 

docs/docs/guides/protips.md

@@ -8,7 +8,7 @@ By default, when running dev environments, tasks, or services, `dstack apply` re
 instances from existing fleets. If no `idle` instances match the requirements, it creates a new fleet automatically.
 
 To avoid creating new fleet automatically, 
-set [ `creation_policy`](reference/dstack.yml/dev-environment.md#creation_policy) to `reuse` in the configuration.
+set [ `creation_policy`](../reference/dstack.yml/dev-environment.md#creation_policy) to `reuse` in the configuration.
 
 > Use [fleets](../fleets.md) configurations to create fleets manually. This reduces startup time for dev environments,
 > tasks, and services, and is very convenient if you want to reuse fleets across runs.
@@ -161,14 +161,14 @@ for this time, `dstack` terminates them.
 If you create a fleet manually, the idle duration is not set.
 
 > You can override idle duration for fleets, dev environment, tasks, and services by
-> setting [`termination_idle_duration`](../reference/dstack.yml/dev-environment.md#termination_idle_duration) in the configuration file. 
+> setting [`termination_idle_time`](../reference/dstack.yml/dev-environment.md#termination_idle_time) in the configuration file. 
 
 [//]: # (## Profiles)
 [//]: # ()
 [//]: # (If you don't want to specify the same parameters for each configuration, you can define them once via [profiles](../reference/profiles.yml.md))
 [//]: # (and reuse them across configurations.)
 [//]: # ()
-[//]: # (This can be handy, for example, for configuring parameters such as `max_duration`, `max_price`, `termination_idle_duration`,)
+[//]: # (This can be handy, for example, for configuring parameters such as `max_duration`, `max_price`, `termination_idle_time`,)
 [//]: # (`regions`, etc.)
 [//]: # ()
 [//]: # (Set `default` to `true` in your profile, and it will be applied automatically to any run.)

docs/docs/reference/dstack.yml/fleet.md

@@ -70,13 +70,13 @@ ssh_config:
       type:
         required: true
 
-## `ssh`
+## `ssh_config`
 
 #SCHEMA# dstack._internal.core.models.fleets.SSHParams
     overrides:
       show_root_heading: false
 
-## `ssh.hosts[n]`
+## `ssh_config.hosts[n]`
 
 #SCHEMA# dstack._internal.core.models.fleets.SSHHostParams
     overrides:

docs/docs/services.md

@@ -58,7 +58,7 @@ If you don't specify your Docker image, `dstack` uses the [base](https://hub.doc
 
 !!! info "Auto-scaling"
     By default, the service is deployed to a single instance. However, you can specify the
-    [number of replicas and scaling policy](reference/dstack.yml/service.md#replicas-and-auto-scaling).
+    [number of replicas and scaling policy](reference/dstack.yml/service.md#auto-scaling).
     In this case, `dstack` auto-scales it based on the load.
 
 !!! info "Reference"

examples/accelerators/amd/README.md

@@ -9,7 +9,7 @@ you can specify an AMD GPU under `resources`. Below are a few examples.
 
 ### Running as a service
 
-Here's an example of a [service](../../docs/services.md) that deploys
+Here's an example of a [service](https://dstack.ai/docs/services) that deploys
 Llama 3.1 70B in FP16 using [TGI :material-arrow-top-right-thin:{ .external }](https://huggingface.co/docs/text-generation-inference/en/installation_amd){:target="_blank"}.
 
 <div editor-title="examples/deployment/tgi/amd/service.dstack.yml">