Update storage-blob-rehydration.md

Author: xyh1

articles/storage/blobs/storage-blob-rehydration.md

@@ -32,7 +32,7 @@ If you don't want to rehydrate your archive blob, you can choose to do a [Copy B
 Copying a blob from archive can take hours to complete depending on the rehydrate priority selected. Behind the scenes, the **Copy Blob** operation reads your archive source blob to create a new online blob in the selected destination tier. The new blob may be visible when you list blobs but the data is not available until the read from the source archive blob is complete and data is written to the new online destination blob. The new blob is as an independent copy and any modification or deletion to it does not affect the source archive blob.
 
 > [!IMPORTANT]
-> Do not delete the the source blob until the copy is completed successfully at the destination. If the source blob is deleted then the destination copy may not complete copying and the destination blob will be empty. You may check the *x-ms-copy-status* to determine the state of the copy operation.
+> Do not delete the the source blob until the copy is completed successfully at the destination. If the source blob is deleted then the destination blob may not complete copying and will be empty. You may check the *x-ms-copy-status* to determine the state of the copy operation.
 
 Archive blobs can only be copied to online destination tiers within the same storage account. Copying an archive blob to another archive blob is not supported. The following table indicates CopyBlob's capabilities.