fix(links): correct two broken relative paths in SAN content

- task-14: ../../phase-06-post-deployment → ../phase-06-post-deployment
  (file is inside phase-03-os-configuration, not 04-cluster-deployment)
- san/ad/portal: ../../active-directory → ../../s2d/active-directory
  (path moved into s2d/ subdirectory during W3.2 restructure)

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: kristopherjturner

docs/implementation/04-cluster-deployment/phase-03-os-configuration/task-14-verify-san-lun-presentation-conditional.mdx

@@ -49,7 +49,7 @@ This task applies only to **disaggregated SAN deployments**. If you are deployin
 :::danger Do NOT initialize the infrastructure or performance history LUNs
 The infrastructure volume LUN and performance history LUN must remain **RAW** (no partition table, no file system) until the Azure Local deployment wizard runs. If you initialize these LUNs before deployment, the wizard will fail.
 
-Workload LUNs are added and initialized **after** cluster deployment — see [Phase 06 Task 05](../../phase-06-post-deployment/task-05-storage-configuration.mdx).
+Workload LUNs are added and initialized **after** cluster deployment — see [Phase 06 Task 05](../phase-06-post-deployment/task-05-storage-configuration.mdx).
 :::
 
 ---

docs/implementation/04-cluster-deployment/phase-05-cluster-deployment/deployment-methods/san/active-directory/portal-instructions.mdx

@@ -39,7 +39,7 @@ This runbook deploys a disaggregated Azure Local cluster using the Azure Portal
 - **Storage**: External SAN (Fiber Channel) — not Storage Spaces Direct
 - **Identity**: Active Directory with domain-joined nodes
 
-The portal wizard flow is similar to the [S2D AD portal deployment](../../active-directory/portal-instructions.mdx) but with key differences in storage and networking configuration.
+The portal wizard flow is similar to the [S2D AD portal deployment](../../s2d/active-directory/portal-instructions.mdx) but with key differences in storage and networking configuration.
 
 ---