[SFTP] Explicit owning user and owning group verbiage

Author: mikewill4

articles/storage/blobs/secure-file-transfer-protocol-support.md

@@ -81,27 +81,27 @@ For container-level permissions, you can choose which containers you want to gra
 | List | l | <li>List content within container</li><li>List content within directory</li> |
 | Delete | d | <li>Delete file/directory</li> |
 | Create | c | <li>Upload file if file doesn't exist</li><li>Create directory if directory doesn't exist</li> |
-| Modify Ownership | o | <li>Change owner or group for file/directory</li> |
+| Modify Ownership | o | <li>Change the owning user or owning group for file/directory</li> |
 | Modify Permissions | p | <li>Change permissions for file/directory</li> |
 
 When performing write operations on blobs in sub directories, Read permission is required to open the directory and access blob properties.
 
 ## ACLs
 
-For directory or blob level permissions, you can change owner, group, and mode that are used by ADLS Gen2 ACLs. Most SFTP clients expose commands for changing these properties. The following table describes common commands in more detail.
+For directory or blob level permissions, you can change owning user, owning group, and mode that are used by ADLS Gen2 ACLs. Most SFTP clients expose commands for changing these properties. The following table describes common commands in more detail.
 
 | Command | Required Container Permission | Description |
 |---|---|---|
-| chown | o | <li>Change owner for file/directory</li><li>Must specify numeric ID</li> |
-| chgrp | o | <li>Change group for file/directory</li><li>Must specify numeric ID</li> |
+| chown | o | <li>Change owning user for file/directory</li><li>Must specify numeric ID</li> |
+| chgrp | o | <li>Change owning group for file/directory</li><li>Must specify numeric ID</li> |
 | chmod | p | <li>Change permissions/mode for file/directory</li><li>Must specify POSIX style octal permissions</li> |
 
-The IDs required for changing owner and group are part of new properties for Local Users. The following table describes each new Local User property in more detail. 
+The IDs required for changing owning user and owning group are part of new properties for Local Users. The following table describes each new Local User property in more detail. 
 
 | Property | Description |
 |---|---|
-| UserId | <li>Unique identifier for the Local User within the storage account</li><li>Generated by default when the Local User is created</li><li>Used for setting owner on file/directory</li> |
-| GroupId | <li>Identifer for a group of Local Users</li> |
+| UserId | <li>Unique identifier for the Local User within the storage account</li><li>Generated by default when the Local User is created</li><li>Used for setting owning user on file/directory</li> |
+| GroupId | <li>Identifer for a group of Local Users</li><li>Used for setting owning group on file/directory</li> |
 | AllowAclAuthorization | <li>Allow authorizing this Local User's requests with ACLs</li> |
 
 Once the desired ACLs have been configured and the Local User enables `AllowAclAuthorization`, they may use ACLs to authorize their requests. Similar to RBAC, container permissions can interoperate with ACLs. Only if the local user doesn't have sufficient container permissions will ACLs be evaluated. To learn more, see [Access control model in Azure Data Lake Storage Gen2](data-lake-storage-access-control-model.md).