Update ask-device-permission-api-takes-too-long.md

Author: kevinlg-mstdl

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/ask-device-permission-api-takes-too-long.md

@@ -13,19 +13,20 @@ ms.subservice: calling
 ---
 
 # The askDevicePermission API takes too long
-The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API has the end user is shown a browser prompt asking if they allow permission to use (camera or microphone).
-If the end users approves to use their camera or microphone, then those devices are available to be used in a call and their availability are reflected in available device list.
-If you find that this API is taking a long time to respond, it could be due to delays in the end user approving the permission prompt user interface.
+The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API prompts the end user via the browser asking if they allow permission to use camera or microphone.
+If the end users approves camera or microphone usage, then those devices are available to be used in a call. The devices availability is reflected in available device list.
+
+User taking a long time to approve the permission can cause delay in the API response.
 
 Occasionally, the device list update step can take a long time.
-This issue is usually because the driver layer responds late, which can happen with some virtual audio devices in particular. [Chromium Issue 1402866](https://bugs.chromium.org/p/chromium/issues/detail?id=1402866&no_tracker_redirect=1)
+This issue is usually caused by a delay in the driver layer. The issue can happen with some virtual audio devices in particular. [Chromium Issue 1402866](https://bugs.chromium.org/p/chromium/issues/detail?id=1402866&no_tracker_redirect=1)
 
 ## How to detect using the SDK
 To detect this issue, you can measure the time difference between when you call the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API and when the promise resolves or rejects.
 
 ## How to mitigate or resolve
-If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API fails due to the user not responding to the permission prompt UI,
-the application can retry the API again and the user should see the permission prompt UI.
+If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API fails due to the user not responding to the UI permission prompt,
+the application can retry the API again and the user should see the UI permission prompt .
 
 If the device list update step takes a long time, the user should check their audio device list and see if there's any device that could potentially be causing this issue.
 They may need to update or remove the problematic device to resolve the issue.