acrolinx; fix grammar

Author: b-hchen

articles/azure-netapp-files/manage-default-individual-user-group-quotas.md

@@ -15,7 +15,7 @@ This article explains the considerations and steps for managing user and group q
 
 ## Quotas in cross-region replication relationships
 
-Quota rules is synced from cross-region replication (CRR) source to destination volumes. Quota rules that you create, delete, or update on a CRR source volume automatically applies to the CRR destination volume.
+Quota rules are synced from cross-region replication (CRR) source to destination volumes. Quota rules that you create, delete, or update on a CRR source volume automatically applies to the CRR destination volume.
 
 Quota rules only come into effect on the CRR destination volume after the replication relationship is deleted because the destination volume is read-only. To learn how to break the replication relationship, see [Delete volume replications](cross-region-replication-delete.md#delete-volume-replications). If source volumes have quota rules and you create the CRR destination volume at the same time as the source volume, all the quota rules are created on destination volume.
 
@@ -35,10 +35,10 @@ Quota rules only come into effect on the CRR destination volume after the replic
     * During sync or reverse resync operations:
         * If you create, update, or delete a rule on a source volume, you must perform the same operation on the destination volume. 
         * If you create, update, or delete a rule on a destination volume after the deletion of the replication relationship, the rule will be reverted to keep the source and destination volumes in sync.
-* If you are using [large volumes](large-volumes-requirements-considerations.md) (volumes larger than 100 TiB):    
+* If you're using [large volumes](large-volumes-requirements-considerations.md) (volumes larger than 100 TiB):    
     * The space and file usage in a large volume might exceed as much as five percent more than the configured hard limit before the quota limit is enforced and rejects traffic.   
-    * To provide optimal performance, the space consumption may exceed configured hard limit before the quota is enforced. The additional space consumption will not exceed either the lower of 1 GB or five percent of the configured hard limit.    
-    * After reaching the quota limit, if a user or administrator delete files or directories to reduce quota usage under the limit, subsequent quota-consuming file operations may resume with a delay of up to five seconds.
+    * To provide optimal performance, the space consumption may exceed configured hard limit before the quota is enforced. The additional space consumption won't exceed either the lower of 1 GB or five percent of the configured hard limit.    
+    * After reaching the quota limit, if a user or administrator deletes files or directories to reduce quota usage under the limit, subsequent quota-consuming file operations may resume with a delay of up to five seconds.
 
 ## Register the feature