Updated various small details

Author: sloanster

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

@@ -6,27 +6,25 @@ author: enricohuang
 ms.author: enricohuang
 
 services: azure-communication-services
-ms.date: 03/27/2024
+ms.date: 03/29/2024
 ms.topic: troubleshooting
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 # The askDevicePermission API takes too long
-The `askDevicePermission` API triggers the permission prompt and updates the device list internally.
-If you find that this API is taking a long time, it could be due to delays in either step.
-If the browser shows the permission prompt UI and the user doesn't respond for a while,
-the ACS Web Calling SDK resolves the promise and returns the permission result.
+The [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API will have the end user will be shown a browser prompt asking if they allow permission to use (camera or microphone).
+If the end users aproves to use their camera or microphone then those devices will be available to be used in a call and their availability will be 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.
 
 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)
 
-## How to detect
-### SDK
-To detect this issue, you can measure the time difference between when you call the `askDevicePermission` API and when the promise resolves or rejects.
+## 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#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API and when the promise resolves or rejects.
 
 ## How to mitigate or resolve
-If the `askDevicePermission` API fails due to the user not responding to the permission prompt UI,
+If the [`askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@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 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.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/no-enumerated-microphone-list.md

@@ -6,34 +6,31 @@ author: enricohuang
 ms.author: enricohuang
 
 services: azure-communication-services
-ms.date: 02/24/2024
+ms.date: 03/29/2024
 ms.topic: troubleshooting
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 # The getMicrophones API doesn't return detailed microphone list
-If a user reports that they can't see the detailed microphone list,
-it's likely because the browser isn't granted permission to access the microphone.
+If a user reports they can't see the detailed microphone list,
+it's likely because the user didn't grant permission to access the microphone.
 When the permission state is `prompt` or `denied`, the browser doesn't provide detailed information about the microphone devices.
-In this scenario, the `DeviceManager.getMicrophones` API returns an array with one object, where the `id` is set to `microphone:` and the name is set to an empty string.
+In this scenario, the [`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getmicrophones) API returns an array with one object, where the `id` is set to `microphone:` and the name is set to an empty string.
 
-It's important to note that this scenario is different from the scenario where a user doesn't have any microphone device.
-In the latter case, the `DeviceManager.getMicrophones` API only returns an empty array, indicating that there's no available microphone device in the user's system.
+It's important to note that this scenario is different from the scenario where a user doesn't have any microphone on their device. If a device doesn't have any microphones the [`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getmicrophones) API returns an empty array, indicating that there's no available microphone devices on the user's system.
 
-## How to detect
-### SDK
-`DeviceManager.getMicrophones` API returns an empty array or an array with an object, where the `id` is set to `microphone:` and the name is set to an empty string.
+## How to detect using the SDK
+[`DeviceManager.getMicrophones`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getmicrophones) API returns an empty array or an array with an object, where the `id` is set to `microphone:` and the name is set to an empty string.
 
 Additionally, to detect the scenario where the user removes the microphone during the call and there are no available microphones in the system,
-the application can listen to the `noMicrophoneDevicesEnumerated` bad event in the [User Facing Diagnostics Feature](../../../../concepts/voice-video-calling/user-facing-diagnostics.md).
+the application can listen to the [`noMicrophoneDevicesEnumerated`](/javascript/api/azure-communication-services/@azure/communication-calling/latestmediadiagnostics?view=azure-communication-services-js#@azure-communication-calling-latestmediadiagnostics-nomicrophonedevicesenumerated) bad event in the [User Facing Diagnostics Feature](../../../../concepts/voice-video-calling/user-facing-diagnostics.md).
 This event can help the application understand the current situation, so it can show a warning message on its UI accordingly.
 
 ## How to mitigate or resolve
-The application should always call the `DeviceManager.askDevicePermission` API to ensure that the required permissions are granted.
-If the user doesn't grant the microphone permission, the application should display a warning message on its UI.
+Your application should always call the [`DeviceManager.askDevicePermission`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-askdevicepermission) API to ensure that the required permissions are granted.
+If the user doesn't grant the microphone permission, your application should display a warning message on its user interface.
 
-Additionally, the application should listen to the `noMicrophoneDevicesEnumerated` event and show a message when there are no available microphone devices.
+Additionally, your application should listen to the [`noMicrophoneDevicesEnumerated`](/javascript/api/azure-communication-services/@azure/communication-calling/latestmediadiagnostics?view=azure-communication-services-js#@azure-communication-calling-latestmediadiagnostics-nomicrophonedevicesenumerated) event and show a message when there are no available microphone devices.
 If the application provides a device selection page before the call,
-it can also check whether the microphone list is empty and shows a warning accordingly indicating no mic devices available.
-This way can help users understand what is happening.
+it can also check whether the microphone list is empty and shows a warning accordingly indicating no mic devices available.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/no-enumerated-speaker-list.md

@@ -20,20 +20,19 @@ The way browsers currently work may seem counterintuitive, as the permission to
 The speaker and microphone enumeration shares the same permission information.
 
 When the microphone permission state is `prompt` or `denied`, the browser doesn't provide detailed information about the microphone devices and speaker devices.
-In this scenario, the `DeviceManager.getSpeakers` API returns an array with one object, where the `id` is set to `speaker:` and the name is set to an empty string.
+In this scenario, thv [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getspeakers) API returns an array with one object, where the `id` is set to `speaker:` and the name is set to an empty string.
 
-Some platforms, such as iOS Safari, macOS Safari, or earlier versions of Firefox, don't support speaker enumeration.
+Some platforms, such as iOS Safari, macOS Safari, or earlier versions of Firefox don't support speaker enumeration.
 
 It's important to note that this scenario is different from the scenario where a user doesn't have any audio output device.
-In the latter case, the `DeviceManager.getSpeakers` API only returns an empty array, indicating that there's no available audio output device in the user's system.
+In the latter case, the [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getspeakers) API only returns an empty array, indicating that there's no available audio output device in the user's system.
 
-## How to detect
-### SDK
-`DeviceManager.getSpeakers` API returns an empty array or an array with an object, where  the `id` is set to `speaker:` and the name is set to an empty string.
+## How to detect using the SDK
+[`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getspeakers) API returns an empty array or an array with an object, where  the `id` is set to `speaker:` and the name is set to an empty string.
 
 Additionally, to detect the scenario where the user removes the speaker during the call and there are no available audio output devices in the system, the application can listen to the `noSpeakerDevicesEnumerated` bad event in the [User Facing Diagnostics Feature](../../../../concepts/voice-video-calling/user-facing-diagnostics.md). This event can help the application understand the current situation, and show the warning message on its UI accordingly.
 
-For the platform that doesn't support speaker enumeration, you get an error when calling `DeviceManager.getSpeakers` API.
+For the platform that doesn't support speaker enumeration, you get an error when calling [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getspeakers) API.
 
 The error code/subcode is
 
@@ -46,7 +45,7 @@ The error code/subcode is
 
 ## How to mitigate or resolve
 The application should always call the `DeviceManager.askDevicePermission` API to ensure that the required permissions are granted.
-If the user doesn't grant the microphone permission, the application should show a warning on its UI, so the user knows that they aren't able to see the speaker device list.
+If the user doesn't grant the microphone permission, the application should show a warning on its user interface, so the user knows that they aren't able to see the speaker device list.
 
-The application should also check whether the speaker list is empty or handle the error when calling `DeviceManager.getSpeakers` API, and show a warning accordingly.
+The application should also check whether the speaker list is empty or handle the error when calling [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-getspeakers) API, and show a warning accordingly.
 Additionally, the application should listen to the `noSpeakerDevicesEnumerated` event and show a message when there are no available speaker devices.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/no-permission-prompt.md

@@ -6,27 +6,26 @@ author: enricohuang
 ms.author: enricohuang
 
 services: azure-communication-services
-ms.date: 02/24/2024
+ms.date: 03/29/2024
 ms.topic: troubleshooting
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 # No permission prompt shows when calling askDevicePermission
-If a user reports that they don't see any permission prompt, it may be because they have previously granted or denied permission and the browser caches the result.
+If a user reports that they don't see any permission prompts, it may be because they have previously granted or denied permission and the browser caches the result.
 
 Not showing the permission prompt isn't a problem if the browser has the required permission.
 However, if the user can't see the device list, it could be because they denied permission before.
 
 Another possible reason for the lack of a permission prompt is that the user's system doesn't have any microphone or camera devices available,
 causing the browser to skip the prompt even if the permission state is set to `prompt`.
 
-## How to detect
-### SDK
+## How to detect using the SDK
 We can't detect whether the permission prompt actually shows or not, as this browser behavior can't be detected at JavaScript layer.
 
 ## How to mitigate or resolve
-The application should check the result of `DeviceManager.askDevicePermission` API.
+The application should check the result of [`DeviceManager.askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) API.
 If the result is false, it may indicate that user denied the permission now or previously.
 
 The application should show a warning message and ask the user to check their browser settings to ensure that correct permissions have been granted.

articles/communication-services/resources/troubleshooting/voice-video-calling/device-issues/overview.md

@@ -6,14 +6,14 @@ author: enricohuang
 ms.author: enricohuang
 
 services: azure-communication-services
-ms.date: 02/24/2024
+ms.date: 03/29/2024
 ms.topic: troubleshooting
 ms.service: azure-communication-services
 ms.subservice: calling
 ---
 
 # Overview of device and permission issues
-There are two different types of permissions in general: browser permission and system permission.
+Within the WebJS calling SDK there are two general different types of permissions: browser permission and system permission.
 When an application needs to access a user's audio or video input device, it requires permissions granted at both the browser and system level.
 
 If an application doesn't have the required permission, it can't access the device,
@@ -23,7 +23,7 @@ To avoid these issues, it's important for users to grant the necessary permissio
 If a user accidentally denies permission or needs to change their permissions later, they can usually do so through the browser settings.
 
 The permission is also necessary for the application to retrieve detailed device list information.
-The application can call `DeviceManager.askDevicePermission` to trigger the permission prompt UI.
+The application can call [`DeviceManager.askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest#@azure-communication-react-calladapterdevicemanagement-askdevicepermission) to trigger the permission prompt UI.
 However, the browser may cache the permission result and return it without showing the permission prompt UI.
 If the permission result is `denied`, the user needs to update the permission through the browser settings.