Acrolinx

Author: Simonx Xu

support/dynamics-365/customer-service/omnichannel-for-customer-service/resource-not-found-error-when-configuring-whatsapp-channel.md

@@ -40,12 +40,12 @@ To resolve this issue, follow these steps:
 
 ### Step 3: Activate the Required Plugins
 
-1. In the **SDK Message Processing Steps** list, look in the **Name**column to locate the following plugins:
+1. In the **SDK Message Processing Steps** list, look in the **Name** column to locate the following plugins:
 
     - **Microsoft.Dynamics.OmnichannelSharedBase.Plugins.PostOperationUpdatePrivacyTermsPlugin**: `msdyn_UpdatePrivacyTerms` of any Entity.
     - **Microsoft.Dynamics.OmnichannelBase.Plugins.PostOperationUpdatePrivacyTermsPlugin**: `msdyn_UpdatePrivacyTerms` of any Entity.
 
-2. Verify the **Status**column for each plugin:
+2. Verify the **Status** column for each plugin:
 
     - If the plugin is disabled, select it by selecting the checkbox next to its name.
 

support/dynamics-365/customer-service/omnichannel-for-customer-service/the-remote-name-could-not-be-resolved-error-when-enabling-or-adding-a-user.md

@@ -1,6 +1,6 @@
 ---
 title: The Remote Name Could Not Be Resolved Error When Enabling Or Adding a user
-description: Solves the The remote name could not be resolved error when enabling or adding a user in Microsoft Dynamics 365 Contact Center.
+description: Solves the "The remote name could not be resolved" error when enabling or adding a user in Microsoft Dynamics 365 Contact Center.
 author: Yerragovula
 ms.author: srreddy
 ai-usage: ai-assisted
@@ -20,32 +20,32 @@ When you try to enable or add a user, you receive the following error message:
 
 ## Cause
 
-This issue can occur due to an out-of-the-box plugin associated with Omnichannel, that can affect the user synchronization process.
+This issue can occur due to an out-of-the-box plugin associated with Omnichannel that can affect the user synchronization process.
 
 ## Resolution
 
-Follow these steps to resolve the issue:
+To resolve the issue, follow these steps:
 
 1. Open the Customer Service admin center.
 
 2. Open the browser console using the shortcut <kbd>Ctrl</kbd>+<kbd>Shift</kbd>+<kbd>I</kbd>.
 
-3. Run the following command in the console to check the current app setting:
+3. Check the current app setting by running the following command in the console:
 
     `Xrm.Utility.getGlobalContext().getCurrentAppSetting("msdyn_IsCCaaSOrURProvisioned");`
 
     If the returned value is `true`, proceed to the next step.
 
-4. Run the following command in the console to update the setting to `false`:
+4. Update the setting to `false` by running the following command in the console:
 
     `Xrm.Utility.getGlobalContext().saveSettingValue('msdyn_IsCCaaSOrURProvisioned', false);`
 
 5. Wait approximately 15 minutes for the setting to update.
 
 6. Refresh the browser page or sign out and sign back in to the Customer Service admin center.
 
-7. Re-run the initial command to confirm the returned value is now `false`:
+7. Rerun the initial command to confirm the returned value is now `false`:
 
     `Xrm.Utility.getGlobalContext().getCurrentAppSetting("msdyn_IsCCaaSOrURProvisioned");`
 
-8. Once the setting is confirmed to be updated, attempt to enable or add the user again.
+8. Once the setting update is confirmed, attempt to enable or add the user again.