Update doc

Author: enricohuang

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-permission-denied.md

@@ -40,7 +40,7 @@ Additionally, your application should acquire camera browser permission before l
 If there's no permission granted, the application is unable to get the detailed information of the camera devices on the user's system.
 
 The camera permission can also be revoked during a call, so your application should also subscribe to events from the User Facing Diagnostics events to display a message on the user interface.
-The end users can then take steps to resolve the issue on their own, such as enabling the browser permission or checking whether they disabled the camera access at OS level.
+Users can then take steps to resolve the issue on their own, such as enabling the browser permission or checking whether they disabled the camera access at OS level.
 
 > [!NOTE]
 > Some browser platforms cache the permission results.

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-start-failed.md

@@ -36,7 +36,7 @@ call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diag
 ```
 ## How to mitigate or resolve
 The `capturerStartFailed` is due to external reasons, so your application should subscribe to events from the User Facing Diagnostics and display a message on your user interface to alert users of screen sharing failures.
-The end users can then take steps to resolve the issue on their own, such as checking if there are other processes causing this issue.
+Users can then take steps to resolve the issue on their own, such as checking if there are other processes causing this issue.
 
 ## Next steps
 * Learn more about [User Facing Diagnostics feature](../../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web).

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-stopped-unexpectedly.md

@@ -38,7 +38,7 @@ call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diag
 
 ## How to mitigate or resolve
 Your application should subscribe to events from the User Facing Diagnostics and display a message on your user interface to alert users of screen sharing issues.
-The end users can then take steps to resolve the issue on their own, such as checking whether they accidentally minimize the window being shared.
+Users can then take steps to resolve the issue on their own, such as checking whether they accidentally minimize the window being shared.
 
 ## Next steps
 * Learn more about [User Facing Diagnostics feature](../../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web).

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-mute-unexpectedly.md

@@ -35,7 +35,7 @@ call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diag
 ```
 
 ## How to mitigate or resolve
-Your application should subscribe to events from the User Facing Diagnostics and display an alert message to the users if there's  microphone state changes. By doing so, the users are aware of muted issues and aren't surprised if they found other participants can't hear their audio during a call.
+Your application should subscribe to events from the User Facing Diagnostics and display an alert message to users of any microphone state changes. By doing so, users are aware of muted issues and aren't surprised if they found other participants can't hear their audio during a call.
 
 ## Next steps
 * Learn more about [User Facing Diagnostics feature](../../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web).

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-receive-quality.md

@@ -13,8 +13,8 @@ ms.subservice: calling
 ---
 
 # networkReceiveQuality UFD
-The `networkReceiveQuality` UFD with `Bad` value indicates the presence of network quality issues for incoming streams, as detected by the ACS Calling SDK.
-This warning suggests that there may be problems with the network connection between the local endpoint and remote endpoint.
+The `networkReceiveQuality` UFD with a `Bad` value indicates the presence of network quality issues for incoming streams, as detected by the ACS Calling SDK.
+This event suggests that there may be problems with the network connection between the local endpoint and remote endpoint.
 When this UFD fires with the `Bad` value, the user may experience degraded audio quality.
 
 | networkReceiveQualityUFD | Details                |

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-reconnect.md

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # networkReconnect UFD
-The `networkReconnect` UFD with Bad value occurs when the Interactive Connectivity Establishment (ICE) transport state on the connection is `failed`.
+The `networkReconnect` UFD with a `Bad` value occurs when the Interactive Connectivity Establishment (ICE) transport state on the connection is `failed`.
 This event indicates that there may be network issues between the two endpoints, such as packet loss or firewall issues.
 The connection failure is detected by the ICE consent freshness mechanism implemented in the browser.
 
@@ -46,7 +46,7 @@ From the perspective of the ACS Calling SDK, network issues are considered exter
 To solve network issues, you need to understand the network topology and identify the nodes that are causing the problem.
 These parts involve network infrastructure, which is outside the scope of the ACS Calling SDK.
 
-Internally, the ACS Calling SDK will trigger reconnection after a `networkReconnect` Bad UFD is fired. If the connection recovers, `networkReconnect` Good UFD is fired.
+Internally, the ACS Calling SDK will trigger reconnection after a `networkReconnect` UFD with a `Bad` value is fired. If the connection recovers, `networkReconnect` UFD with a `Good` value is fired.
 
 Your application should subscribe to events from the User Facing Diagnostics.
 Display a message on your user interface that informs users of network connection issues and potential audio loss.

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-relays-not-reachable.md

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # networkRelaysNotReachable UFD
-The `networkRelaysNotReachable` UFD with `true` value occurs when the media connection fails to establish and no relay candidates are available. This issue usually happens when the firewall policy blocks connections between the local client and relay servers.
+The `networkRelaysNotReachable` UFD with a `true` value occurs when the media connection fails to establish and no relay candidates are available. This issue usually happens when the firewall policy blocks connections between the local client and relay servers.
 
 When users see the `networkRelaysNotReachable` UFD, it also indicates that the local client isn't able to make a direct connection to the remote endpoint.
 

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-send-quality.md

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # networkSendQuality UFD
-The `networkSendQuality` UFD indicates that there are network quality issues for outgoing streams, such as packet loss, as detected by the ACS Calling SDK.
+The `networkSendQuality` UFD with a `Bad` value indicates that there are network quality issues for outgoing streams, such as packet loss, as detected by the ACS Calling SDK.
 This event suggests that there may be problems with the network quality issues between the local endpoint and remote endpoint.
 
 

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-network.md

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # noNetwork UFD
-The `noNetwork` UFD with `true` value occurs when there's no network available for ICE candidates being gathered, which means there are network setup issues in the local environment, such as a disconnected Wi-Fi or Ethernet cable.
+The `noNetwork` UFD with a `true` value occurs when there's no network available for ICE candidates being gathered, which means there are network setup issues in the local environment, such as a disconnected Wi-Fi or Ethernet cable.
 Additionally, if the adapter fails to acquire an IP address and there are no other networks available, this situation can also result in `noNetwork` UFD.
 
 | noNetwork UFD        | Details                 |
@@ -38,7 +38,7 @@ call.feature(Features.UserFacingDiagnostics).network.on('diagnosticChanged', (di
 Your application should subscribe to events from the User Facing Diagnostics and display a message in your user interface to alert users of any network setup issues.
 Users can then take steps to resolve the issue on their own.
 
-The end user should also check if they disabled the network adapters or whether they have an available network.
+Users should also check if they disabled the network adapters or whether they have an available network.
 
 ## Next steps
 * Learn more about [User Facing Diagnostics feature](../../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web).

articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-speaker-devices-enumerated.md

@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # noSpeakerDevicesEnumerated UFD
-The `noSpeakerDevicesEnumerated` UFD with `true` value occurs when there's no speaker device presented in the device list returned by the browser API. This issue occurs when the `navigator.mediaDevices.enumerateDevices` browser API doesn't include any audio output devices. This event indicates that there are no speakers available on the user's machine, which could be because the user unplugged or disabled the speaker.
+The `noSpeakerDevicesEnumerated` UFD with a `true` value occurs when there's no speaker device presented in the device list returned by the browser API. This issue occurs when the `navigator.mediaDevices.enumerateDevices` browser API doesn't include any audio output devices. This event indicates that there are no speakers available on the user's machine, which could be because the user unplugged or disabled the speaker.
 
 On some platforms such as iOS, the browser doesn't provide the audio output devices in the device list. In this case, the SDK considers it as expected behavior and doesn't fire `noSpeakerDevicesEnumerated` UFD.