Skip to content

Commit 8717bc4

Browse files
committed
Fix typo: build-in -> built-in
1 parent 851ad6a commit 8717bc4

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/reliability/concept-redundancy-replication-backup.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -89,7 +89,7 @@ A cloud environment's physical location as whole can be organized into physical
8989
| A group of datacenters, which in Azure is called an *availability zone* | City-wide electrical storm |
9090
| The wider geographical area that the datacenter is in, such as a city, which is an Azure *region* | Widespread natural disaster |
9191

92-
From a reliability perspective, an important way to mitigate the risks associated with a physical scope is to spread instances of a component across different physical scopes. Azure services with build-in redundancy may offer you one or more of the following three ways to deploy redundant instances:
92+
From a reliability perspective, an important way to mitigate the risks associated with a physical scope is to spread instances of a component across different physical scopes. Azure services with built-in redundancy may offer you one or more of the following three ways to deploy redundant instances:
9393

9494
- *Local redundancy* places instances in multiple parts of a single Azure datacenter and protects against hardware failures that might affect a single instance. Local redundancy typically provides the lowest cost and latency. However, a datacenter failure could mean that all of the instances are unavailable.
9595

0 commit comments

Comments
 (0)