docs: Update sharding private DNS zones article

Author: asudbring

articles/dns/sharding-private-dns-zones.md

@@ -28,10 +28,10 @@ Sharding mitigates this risk by ensuring DNS changes are scoped to a clearly def
 > [!NOTE]
 > Sharding is an architectural pattern. Azure doesn't provide a built-in feature or toggle to enable sharding.
 
-**Figure 1: Flat private DNS zone linked to many virtual networks compared to a sharded design with zones segmented by ownership and environment**
-
 :::image type="content" source="media/sharding-private-dns-zones/dns-shard-flat-architecture.png" alt-text="Screenshot of sharded private DNS zones design with zones segmented by ownership and environment.":::
 
+**Figure 1: Flat private DNS zone linked to many virtual networks compared to a sharded design with zones segmented by ownership and environment**
+
 ## How sharding improves operational resiliency
 
 In large Azure tenants, private DNS zones frequently span multiple subscriptions, regions, and application teams. When you share a single zone broadly:
@@ -63,15 +63,15 @@ Partition DNS zones by:
 
 - Service type or workload class (for example, database)
 
-**Table 1: Example namespace patterns and tradeoffs for common sharding strategies**
-
 | Sharding strategy | Example zone pattern | Benefits | Tradeoffs | Best fit scenarios |
 |---|---|---|---|---|
 | By Team | `orders.contoso.internal` | Clear ownership, RBAC simplicity | Cross-team resolution requires planning | Large orgs with independent teams |
 | By Environment | `orders.prod.contoso.internal` | Strong isolation, safe deployments | Zone duplication across environments | Regulated or CI/CD-heavy workloads |
 | By Region | `orders.eastus.contoso.internal` | Regional fault isolation | More complex naming and routing | Geo-distributed applications |
 | By Service Type | `db.contoso.internal` | Logical grouping by function | Risk of over-centralization | Shared platform services |
 
+**Table 1: Example namespace patterns and tradeoffs for common sharding strategies**
+
 **Implementation notes**
 
 - Strategies can be combined (for example, by team + environment: `orders.prod.contoso.internal`)
@@ -130,12 +130,12 @@ Sharding doesn't require new Azure features. Implement it by using existing Priv
 
     - This approach is recommended for hub-and-spoke or hybrid architectures.
 
-**Figure 2: Sharded private DNS zones with selective virtual network links and centralized resolution**
-
 :::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolution.png" alt-text="Screenshot of sharded private DNS zones with selective virtual network links and centralized resolution.":::
 
 :::image type="content" source="media/sharding-private-dns-zones/dns-shard-central-resolver.png" alt-text="Screenshot of sharded private DNS zones architecture with centralized resolution.":::
 
+**Figure 2: Sharded private DNS zones with selective virtual network links and centralized resolution**
+
 ## When to use sharding
 
 Private DNS zone sharding is most valuable when: