Skip to content

Commit b4d3769

Browse files
committed
more edits
1 parent e764d15 commit b4d3769

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/operator-nexus/concepts-nexus-availability.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -125,7 +125,7 @@ For more information about the upgrade process, see [this article](./howto-clust
125125

126126
Workloads should ideally follow a cloud-native design, with N+k clusters that can be deployed across multiple nodes and racks within a site, using the Operator Nexus zone concept.
127127

128-
The Well Architected Framework guidance on [mission critical](/well-architected/mission-critical/) and [carrier grade](/well-architected/carrier-grade/) workloads on Azure also applies to workloads on Operator Nexus.
128+
The Well Architected Framework guidance on [mission critical](/azure/well-architected/mission-critical/) and [carrier grade](/azure/well-architected/carrier-grade/) workloads on Azure also applies to workloads on Operator Nexus.
129129

130130
Designing and implementing highly available workloads on any platform requires a top-down approach. Start with an understanding of the availability required from the solution as a whole. Consider the key elements of the solution and their predicted availability. Then determine how these attributes need to be combined in order to achieve the solution level goals.
131131

0 commit comments

Comments
 (0)