fix versions in docker commands

Author: mdbirnstiehl

solutions/observability/apm/apm-server-binary.md

@@ -857,13 +857,13 @@ Obtaining APM Server for Docker is as simple as issuing a `docker pull` command
 1. Pull the Docker image:
 
     ```shell
-    docker pull docker.elastic.co/apm/apm-server:9.0.0
+    docker pull docker.elastic.co/apm/apm-server:{{version.stack}}
     ```
 
     Alternately, you can use the hardened [Wolfi](https://wolfi.dev/) image:
 
     ```shell
-    docker pull docker.elastic.co/apm/apm-server-wolfi:9.0.0
+    docker pull docker.elastic.co/apm/apm-server-wolfi:{{version.stack}}
     ```
 
 1. Verify the Docker image:

solutions/observability/synthetics/monitor-resources-on-private-networks.md

@@ -66,7 +66,7 @@ The `elastic-agent-complete` Docker image is the only way to have all available
 To pull the Docker image run:
 
 ```sh
-docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:8.16.1
+docker pull docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}}
 ```
 
 Then enroll and run an {{agent}}. You’ll need an enrollment token and the URL of the {{fleet-server}}. You can use the default enrollment token for your policy or create new policies and [enrollment tokens](/reference/fleet/fleet-enrollment-tokens.md) as needed.
@@ -80,7 +80,7 @@ docker run \
   --env FLEET_ENROLLMENT_TOKEN={enrollment_token} \
   --cap-add=NET_RAW \
   --cap-add=SETUID \
-  --rm docker.elastic.co/elastic-agent/elastic-agent-complete:8.16.1
+  --rm docker.elastic.co/elastic-agent/elastic-agent-complete:{{version.stack}}
 ```
 
 ::::{important}
@@ -119,15 +119,15 @@ By default {{private-location}}s are configured to allow two simultaneous browse
 
 It is critical to allocate enough memory and CPU capacity to handle configured limits. Resource requirements will vary depending on simultaneous workload and monitor complexity:
 
-**For browser monitors**: Start by allocating at least 2 GiB of memory and two cores _per browser instance_ to ensure consistent performance and avoid out-of-memory errors. Then adjust as needed. 
+**For browser monitors**: Start by allocating at least 2 GiB of memory and two cores _per browser instance_ to ensure consistent performance and avoid out-of-memory errors. Then adjust as needed.
 **For tcp, http, icmp**: Much less memory is needed, start by allocating at least 512MiB of memory and two cores _globally_. While this will be enough to run a large number of lightweight monitors, it is recommended to track the resource usage and adjust accordingly.
 
 Example: For a private location expected to run 2 concurrent browser monitors and 100 HTTP checks, the recommended allocation is 2 * (2 GiB + 2 vCPU) + (512 MiB + 2 vCPU) => 4,5 GiB + 6 vCPU.
 
 ### Known limitations on vertical scaling
 
 - A single private location will not scale beyond 10,000 monitors. Exceeding this number will result in agent degradation and inconsistent execution, regardless of the resources allocated.
-- Complex monitor configuration can disproportionately increase the private location policy size, leading to agent communication errors and degradation even if the limit mentioned above hasn't been reached. 
+- Complex monitor configuration can disproportionately increase the private location policy size, leading to agent communication errors and degradation even if the limit mentioned above hasn't been reached.
 
 If you're facing one of these scenarios, it is likely that the private location has grown too large and needs to be split into smaller locations, each alloted a portion of the original location monitors.