fix(clustered): clarify compactor scaling guidance for CPU and memory

Addresses customer confusion where scaling CPU alone doesn't improve
compactor performance. Compactor concurrency scales based on memory
allocation, not CPU count, so both resources should be scaled together.

Closes influxdata/DAR#514

add related links

fix(clustered): correct anchor link in scale-cluster documentation

Fix broken internal anchor link from #rrecommended-scaling-strategies-per-component
to #recommended-scaling-strategies-per-component (removed extra 'r').

This was used to test the improved link-checker anchor validation functionality.

fix(clustered): correct anchor link in scale-cluster documentation

Fixes broken anchor link #rrecommended-scaling-strategies-per-component
to the correct #recommended-scaling-strategies-per-component

TESTING.md

@@ -184,6 +184,31 @@ link-checker check public/path/to/file.html
 link-checker config
 ```
 
+### Link Resolution Behavior
+
+The link-checker automatically handles relative link resolution based on the input type:
+
+**Local Files → Local Resolution**
+```bash
+# When checking local files, relative links resolve to the local filesystem
+link-checker check public/influxdb3/core/admin/scale-cluster/index.html
+# Relative link /influxdb3/clustered/tags/kubernetes/ becomes:
+# → /path/to/public/influxdb3/clustered/tags/kubernetes/index.html
+```
+
+**URLs → Production Resolution**
+```bash
+# When checking URLs, relative links resolve to the production site
+link-checker check https://docs.influxdata.com/influxdb3/core/admin/scale-cluster/
+# Relative link /influxdb3/clustered/tags/kubernetes/ becomes:
+# → https://docs.influxdata.com/influxdb3/clustered/tags/kubernetes/
+```
+
+**Why This Matters**
+- **Testing new content**: Tag pages generated locally will be found when testing local files
+- **Production validation**: Production URLs validate against the live site
+- **No false positives**: New content won't appear broken when testing locally before deployment
+
 ### Content Mapping Workflows
 
 #### Scenario 1: Map and check InfluxDB 3 Core content

content/influxdb3/clustered/admin/scale-cluster.md

@@ -8,9 +8,11 @@ menu:
     parent: Administer InfluxDB Clustered
     name: Scale your cluster
 weight: 207
-influxdb3/clustered/tags: [scale]
+influxdb3/clustered/tags: [scale, performance, Kubernetes]
 related:
   - /influxdb3/clustered/reference/internals/storage-engine/
+  - /influxdb3/clustered/write-data/best-practices/data-lifecycle/
+  - /influxdb3/clustered/query-data/troubleshoot-and-optimize/optimize-queries/
   - https://kubernetes.io/docs/concepts/configuration/manage-resources-containers/#requests-and-limits, Kubernetes resource requests and limits
 ---
 
@@ -559,11 +561,14 @@ concurrency demands or reaches the hardware limits of your underlying nodes.
 
 ### Compactor
 
-- **Recommended**: Maintain **1 Compactor pod** and use [vertical scaling](#vertical-scaling) (especially
-increasing the available CPU) for the Compactor.
+- **Recommended**: Maintain **1 Compactor pod** and use [vertical scaling](#vertical-scaling) for the Compactor.
+Scale CPU and memory resources together, as compactor concurrency settings scale based on memory, not CPU count.
 - Because compaction is a compute-heavy process, horizontal scaling increases compaction throughput, but not as
 efficiently as vertical scaling.
 
+> [!Important]
+> When scaling the Compactor, scale CPU and memory resources together.
+
 ### Garbage collector
 
 The [Garbage collector](/influxdb3/clustered/reference/internals/storage-engine/#garbage-collector) is a lightweight process that typically doesn't require