Improving clarity

Author: dbasantes

articles/communication-services/concepts/call-automation/call-recording/bring-your-own-storage.md

@@ -18,7 +18,7 @@ ms.service: azure-communication-services
 
 Bring Your Own Storage (BYOS) for Call Recording allows you to specify an Azure blob storage account for storing call recording files. BYOS enables businesses to store their data in a way that meets their compliance requirements and business needs. For example, end-users could customize their own rules and access to the data, enabling them to store or delete content whenever they need it. BYOS provides a simple and straightforward solution that eliminates the need for developers to invest time and resources in downloading and exporting files.
 
-The same Azure Communication Services Call Recording APIs are used to export recordings to your Azure Blob Storage Container. While starting recording for a call, specify the container path where the recording needs to be exported. Upon recording completion, Azure Communication Services automatically fetch and upload your recording to your storage.
+The same Azure Communication Services Call Recording APIs are used to export recordings to your Azure Blob Storage Container. While starting recording for a call, specify the container path where the recording needs to be exported. Upon recording completion, Azure Communication Services automatically fetches and uploads your recording to your storage.
 
 ![Diagram showing a call recording being automatically exported to storage container](../media/byos-concept.png)
 
@@ -29,7 +29,7 @@ BYOS uses [Azure Managed Identities](../../../../active-directory/managed-identi
 
 ## Known Issues
 
-- After exporting your files, during Private Preview, those files will be also stored in a built-in storage for 48 hours.
+- After exporting your files with call recording BYOS, Azure Communication Services will also store your files in a built-in storage for 48 hours.
 - Randomly, recording files are duplicated during the exporting process when using BYOS. Make sure you delete the duplicated file to avoid extra storage costs in your storage account.
 
 

articles/communication-services/quickstarts/call-automation/call-recording/bring-your-own-storage.md

@@ -26,7 +26,7 @@ This quickstart gets you started with BYOS (Bring your own storage) for Call Rec
 
 1. Open your Azure Communication Services resource. Navigate to *Identity* on the left.
 2. System Assigned Managed Identity is disabled by default. Enable it and click of *Save*
-3. Once completed, you are able to see the Object principal ID of the newly created identity (shown below)
+3. Once completed, you're able to see the Object principal ID of the newly created identity.
 
 ![Diagram showing a communication service resource with managed identity enabled](../media/byos-managed-identity-2.png)
 
@@ -47,7 +47,7 @@ This quickstart gets you started with BYOS (Bring your own storage) for Call Rec
 ![Diagram showing a communication service resource managed identity adding role assignment details](../media/role-assignment-2.png)
 
 3. Click on *"Save"*.
-4. Once completed, you see the newly added role assignment in the *"Azure role assignment"* window (shown below).
+4. Once completed, you see the newly added role assignment in the *"Azure role assignment"* window.
 
 ![Diagram showing a communication service resource managed identity role assignment success](../media/role-assignment-3.png)
 
@@ -67,7 +67,7 @@ Use the server call ID received during initiation of the call.
 
 Use an [Azure Event Grid](../../../../event-grid/overview.md) web hook, or other triggered action, to notify your services when the recorded media is ready and have been exported to the external storage location.
 
-Below is an example of the event schema.
+Refer to this example of the event schema.
 
 ```JSON
 {