edits

Author: tejaswikolli-web

articles/container-registry/intro-connected-registry.md

@@ -65,12 +65,14 @@ It can also be configured to synchronize a subset of the repositories from the c
 
 A connected registry can work in one of two modes: *ReadWrite* or *ReadOnly*
 
-- **ReadWrite mode** - The default mode allows clients to pull and push artifacts (read and write) to the connected registry. Artifacts that are pushed to the connected registry will be synchronized with the cloud registry. 
+- **ReadWrite mode** - The mode allows clients to pull and push artifacts (read and write) to the connected registry. Artifacts that are pushed to the connected registry will be synchronized with the cloud registry. 
 
-  The ReadWrite mode is useful when a local development environment is in place. The images are pushed to the local connected registry and from there synchronized to the cloud.
+ The ReadWrite mode is useful when a local development environment is in place. The images are pushed to the local connected registry and from there synchronized to the cloud.
 
 - **ReadOnly mode** - When the connected registry is in ReadOnly mode, clients can only pull (read) artifacts. This configuration is used for nested IoT Edge scenarios, or other scenarios where clients need to pull a container image to operate.
 
+- **Default mode** - The ***ReadOnly mode*** is now the default mode for connected registries. This change is likely due to security concerns and customer preferences. Starting with CLI version 2.60.0, the default mode is ReadOnly.
+
 ### Registry hierarchy
 
 Each connected registry must be connected to a parent. The top parent is the cloud registry. For hierarchical scenarios such as [nested IoT Edge](overview-connected-registry-and-iot-edge.md), you can nest connected registries in either mode. The parent connected to the cloud registry can operate in either mode.