Skip to content

Commit 861c77a

Browse files
authored
Update reliability-container-registry.md
1 parent 7a1634b commit 861c77a

File tree

1 file changed

+1
-4
lines changed

1 file changed

+1
-4
lines changed

articles/reliability/reliability-container-registry.md

Lines changed: 1 addition & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -46,7 +46,7 @@ Microsoft is responsible for managing the underlying Container Registry infrastr
4646

4747
- **Data plane maintenance** for container image operations across regions and availability zones
4848

49-
As a customer, you're responsible for the following scenarios:
49+
As a customer, you're responsible for the following actions:
5050

5151
- **Application-level resilience:** Implement appropriate retry logic and failover handling in your container applications and orchestration platforms.
5252

@@ -203,9 +203,6 @@ This section describes what to expect when a registry is configured for geo-repl
203203

204204
Replication typically completes within minutes of changes. However, there's no guarantee on data replication timing. Large container images or high-frequency updates might take longer to replicate across all regions.
205205

206-
> [!IMPORTANT]
207-
> The data replication approach across regions is usually different than the approach used across zones.
208-
209206
### Region-down experience
210207

211208
This section describes what to expect when a registry is configured for geo-replication and there's an outage in the primary region.

0 commit comments

Comments
 (0)