small updates for clarity

Author: sloanster

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

@@ -20,7 +20,7 @@ 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, thv [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@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.
+In this scenario, [`DeviceManager.getSpeakers`](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@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.
 
@@ -40,7 +40,7 @@ The error code/subcode is
 |------------------|-------------------------------------------------------|
 | code             | 405 (Method Not Allowed)                              |
 | subcode          | 40606                                                 |
-| message          | This device does not support speaker enumeration.     |
+| message          | This device doesn't support speaker enumeration.     |
 | resultCategories | Expected                                              |
 
 ## How to mitigate or resolve

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

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # No permission prompt shows when calling askDevicePermission
-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.
+If a user reports that they don't see any permission prompts, it may be because they 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.
@@ -28,5 +28,5 @@ We can't detect whether the permission prompt actually shows or not, as this bro
 The application should check the result of [`DeviceManager.askDevicePermission`](/javascript/api/%40azure/communication-react/calladapterdevicemanagement?view=azure-node-latest&preserve-view=true#@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.
+The application should show a warning message and ask the user to check their browser settings to ensure that correct permissions were granted.
 They also need to verify that their system has the necessary devices installed and configured properly.