Skip to content

Commit 278ecac

Browse files
authored
Apply suggestions from PR review
1 parent 77140f6 commit 278ecac

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-resource-manager/management/lock-resources.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -61,7 +61,7 @@ Applying locks can lead to unexpected results. Some operations, which don't seem
6161
- A read-only lock on a **storage account** protects RBAC assignments scoped for a storage account or a data container (blob container or queue).
6262

6363
- A read-only lock on a **storage account** prevents the creation of a blob container.
64-
- ++ A read-only lock on a s**storage account** prevents the creation of a blob container. However, create operations on a storage account can be done through both the control plane and data plane. Read-only locks only block control plane create requests, but a user can still perform a valid create operation on the resource through the data plane..
64+
- A read-only lock on a **storage account** prevents the creation of a blob container. However, create operations on a storage account can be done through both the control plane and data plane. Read-only locks only block control plane create requests, but a user can still perform a valid create operation on the resource through the data plane.
6565

6666
- A read-only lock or cannot-delete lock on a **storage account** doesn't prevent its data from deletion or modification. It also doesn't protect the data in a blob, queue, table, or file.
6767

0 commit comments

Comments
 (0)