add documentation link

Author: wongchar

content/en/blog/_posts/2025-xx-xx-prefer-align-cpus-by-uncore-cache-beta/index.md

@@ -52,7 +52,7 @@ The benefit only shows up if your nodes use a split uncore cache topology for th
 
 The following diagram below illustrates uncore cache alignment when the feature is enabled.
 
-![cache-align-diagram](./cache-align-diagram.png)
+![Diagram showing an example workload CPU assignment, default static policy, and with prefer-align-cpus-by-uncorecache](./cache-align-diagram.png)
 
 By default, Kubernetes does not account for uncore cache topology; containers are assigned CPU resources using a packed methodology.
 As a result, Container 1 and Container 2 can experience a noisy neighbor impact due to
@@ -88,7 +88,9 @@ If you're making this change to an existing node, remove the `cpu_manager_state`
 `prefer-align-cpus-by-uncorecache` can be enabled on nodes with a monolithic uncore cache processor. The feature will mimic a best-effort socket alignment effect and will pack CPU resources on the socket similar to the default static CPU Manager policy.
 
 ## Further reading
-See [Node Resource Managers](/docs/concepts/policy/node-resource-managers/) to learn more about the CPU Manager and the available policies.
+See [Node Resource Managers](/docs/concepts/policy/node-resource-managers/) to learn more about the CPU Manager and the available policies. 
+
+Reference the documentation for `prefer-align-cpus-by-uncorecache` [here](/docs/concepts/policy/node-resource-managers/#prefer-align-cpus-by-uncorecache).
 
 Please see the [Kubernetes Enhancement Proposal](https://github.com/kubernetes/enhancements/tree/master/keps/sig-node/4800-cpumanager-split-uncorecache) for more information on how `prefer-align-cpus-by-uncorecache` is implemented.