Clean up

enricohuang · enricohuang · commit 35e8859c6eb3 · 2024-04-04T12:08:54.000-07:00
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-freeze.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-freeze.md
@@ -16,7 +16,7 @@ ms.subservice: calling
 A `cameraFreeze` UFD event with a `true` value occurs when the SDK detects that the input framerate goes down to zero, causing the video output to appear frozen or not changing.
 
 The underlying issue may suggest problems with the user's video camera, or in certain instances, the device may cease sending video frames.
-For example, on certain Android device models, the browser may trigger the `cameraFreeze` UFD when the user locks the screen or puts the browser in the background.
+For example, on certain Android device models, you may see a `cameraFreeze` UFD event when the user locks the screen or puts the browser in the background.
 In this situation, the Android operating system stops sending video frames, and thus on the other end of the call a user may see a `cameraFreeze` UFD event.
 
 | cameraFreeze                          | Details                |
@@ -25,12 +25,12 @@ In this situation, the Android operating system stops sending video frames, and
 | value type                            | DiagnosticFlag         |
 | possible values                       | true, false            |
 
-## Example code to catch a camera freeze UFD event
+## Example code to catch a cameraFreeze UFD event
 ```typescript
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'cameraFreeze') {
        if (diagnosticInfo.value === true) {
-           // cameraFreeze UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The cameraFreeze UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-permission-denied.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-permission-denied.md
@@ -26,7 +26,7 @@ The `cameraPermissionDenied` UFD event with a `true` value occurs when the SDK d
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'cameraPermissionDenied') {
        if (diagnosticInfo.value === true) {
-           // camera permission denied, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The cameraPermissionDenied UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-start-failed.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-start-failed.md
@@ -13,9 +13,9 @@ ms.subservice: calling
 ---
 
 # cameraStartFailed UFD
-The `cameraStartFailed` UFD with a `true` value occurs when the SDK is unable to acquire the camera stream because the source is unavailable.
+The `cameraStartFailed` UFD event with a `true` value occurs when the SDK is unable to acquire the camera stream because the source is unavailable.
 This error typically happens when the specified video device is being used by another process.
-For example, the user may encounter this `cameraStartFailed` UFD  when they attempt to join a call with video on a browser such as Chrome while another Edge browser has been using the same camera.
+For example, the user may see this `cameraStartFailed` UFD event when they attempt to join a call with video on a browser such as Chrome while another Edge browser has been using the same camera.
 
 | cameraStartFailed                     | Details                |
 | --------------------------------------|------------------------|
@@ -28,15 +28,15 @@ For example, the user may encounter this `cameraStartFailed` UFD  when they atte
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'cameraStartFailed') {
        if (diagnosticInfo.value === true) {
-           // cameraStartFailed UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // cameraStartFailed UFD recovered, notify the user
        }
     }
 });
 ```
 ## How to mitigate or resolve
-The `cameraStartFailed` UFD is due to external reasons, so your application should subscribe to events from the User Facing Diagnostics and display a message on the UI to alert users of camera start failures. To resolve this issue, users can check if there are other processes using the same camera and close them if necessary.
+The `cameraStartFailed` UFD event is due to external reasons, so your application should subscribe to events from the User Facing Diagnostics and display a message on the UI to alert users of camera start failures. To resolve this issue, users can check if there are other processes using the same camera and close them if necessary.
 
 ## Next steps
 * Learn more about [User Facing Diagnostics feature](../../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web).
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-start-timed-out.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-start-timed-out.md
@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # cameraStartTimedOut UFD
-The `cameraStartTimedOut` UFD with a `true` value occurs when the SDK is unable to acquire the camera stream because the promise returned by `getUserMedia` browser method doesn't resolve within a certain period of time.
+The `cameraStartTimedOut` UFD event with a `true` value occurs when the SDK is unable to acquire the camera stream because the promise returned by `getUserMedia` browser method doesn't resolve within a certain period of time.
 This issue can happen when the user starts a call with video enabled, but the browser displays a UI permission prompt and the user doesn't respond to it.
 
 | cameraStartTimedOut                   | Details                |
@@ -27,7 +27,7 @@ This issue can happen when the user starts a call with video enabled, but the br
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'cameraStartTimedOut') {
        if (diagnosticInfo.value === true) {
-           // cameraStartTimedOut UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The cameraStartTimedOut UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-stopped-unexpectedly.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/camera-stopped-unexpectedly.md
@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # cameraStoppedUnexpectedly UFD
-The `cameraStoppedUnexpectedly` UFD with a `true` value occurs when the SDK detects that the camera track was muted.
+The `cameraStoppedUnexpectedly` UFD event with a `true` value occurs when the SDK detects that the camera track was muted.
 
 Keep in mind that this event relates to the camera track's `mute` event triggered by an external source.
 The event can be triggered on mobile browsers when the browser goes to background.
@@ -30,7 +30,7 @@ Additionally, in some browser implementations, the browser sends black frames wh
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'cameraStoppedUnexpectedly') {
        if (diagnosticInfo.value === true) {
-           // cameraStoppedUnexpectedly UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The cameraStoppedUnexpectedly UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-start-failed.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-start-failed.md
@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # capturerStartFailed UFD
-The `capturerStartFailed` UFD with a `true` value occurs when the SDK is unable to acquire the screen sharing stream because the source is unavailable.
+The `capturerStartFailed` UFD event with a `true` value occurs when the SDK is unable to acquire the screen sharing stream because the source is unavailable.
 This issue can happen when the underlying layer prevents the sharing of the selected source.
 
 | capturerStartFailed         | Details                |
@@ -27,7 +27,7 @@ This issue can happen when the underlying layer prevents the sharing of the sele
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'capturerStartFailed') {
        if (diagnosticInfo.value === true) {
-           // capturerStartFailed UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The capturerStartFailed UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-stopped-unexpectedly.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/capturer-stopped-unexpectedly.md
@@ -13,9 +13,9 @@ ms.subservice: calling
 ---
 
 # capturerStoppedUnexpectedly UFD
-The `capturerStoppedUnexpectedly` UFD with a `true` value occurs when the SDK detects that the screen sharing track was muted.
+The `capturerStoppedUnexpectedly` UFD event with a `true` value occurs when the SDK detects that the screen sharing track was muted.
 This issue can happen due to external reasons and depends on the browser implementation.
-For example, if the user shares a window and minimize that window, the `capturerStoppedUnexpectedly` UFD may fire.
+For example, if the user shares a window and minimize that window, the `capturerStoppedUnexpectedly` UFD event may fire.
 
 | capturerStoppedUnexpectedly | Details                |
 | ----------------------------|------------------------|
@@ -28,7 +28,7 @@ For example, if the user shares a window and minimize that window, the `capturer
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'capturerStoppedUnexpectedly') {
        if (diagnosticInfo.value === true) {
-           // capturerStoppedUnexpectedly UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The capturerStoppedUnexpectedly UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-mute-unexpectedly.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-mute-unexpectedly.md
@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # microphoneMuteUnexpectedly UFD
-The `microphoneMuteUnexpectedly` UFD with a `true` value occurs when the SDK detects that the microphone track was muted. Keep in mind, that the event is related to the `mute` event of the microphone track, when it's triggered by an external source rather than by the SDK mute API. The underlying layer triggers the event, such as the audio stack muting the audio input session. The hardware mute button of some headset models can also trigger the `microphoneMuteUnexpectedly` UFD. Additionally, some browser platforms, such as iOS Safari browser, may mute the microphone when certain interruptions occur, such as an incoming phone call.
+The `microphoneMuteUnexpectedly` UFD event with a `true` value occurs when the SDK detects that the microphone track was muted. Keep in mind, that the event is related to the `mute` event of the microphone track, when it's triggered by an external source rather than by the SDK mute API. The underlying layer triggers the event, such as the audio stack muting the audio input session. The hardware mute button of some headset models can also trigger the `microphoneMuteUnexpectedly` UFD. Additionally, some browser platforms, such as iOS Safari browser, may mute the microphone when certain interruptions occur, such as an incoming phone call.
 
 | microphoneMuteUnexpectedly            | Details                |
 | --------------------------------------|------------------------|
@@ -26,7 +26,7 @@ The `microphoneMuteUnexpectedly` UFD with a `true` value occurs when the SDK det
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'microphoneMuteUnexpectedly') {
        if (diagnosticInfo.value === true) {
-           // microphoneMuteUnexpectedly UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The microphoneMuteUnexpectedly UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-not-functioning.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-not-functioning.md
@@ -13,8 +13,8 @@ ms.subservice: calling
 ---
 
 # microphoneNotFunctioning UFD
-The `microphoneNotFunctioning` UFD with a `true` value occurs when the SDK detects that the microphone track was ended. The microphone track ending happens in many situations.
-For example, unplugging a microphone in use triggers the browser to end the microphone track. The SDK would then fire `microphoneNotFunctioning` UFD.
+The `microphoneNotFunctioning` UFD event with a `true` value occurs when the SDK detects that the microphone track was ended. The microphone track ending happens in many situations.
+For example, unplugging a microphone in use triggers the browser to end the microphone track. The SDK would then fire `microphoneNotFunctioning` UFD event.
 It can also occur when the user removes the microphone permission at browser or at OS level. The underlying layers, such as audio driver or media stack at OS level, may also end the session, causing the browser to end the microphone track.
 
 | microphoneNotFunctioning              | Details                |
@@ -28,7 +28,7 @@ It can also occur when the user removes the microphone permission at browser or
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'microphoneNotFunctioning') {
        if (diagnosticInfo.value === true) {
-           // microphoneNotFunctioning UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The microphoneNotFunctioning UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-permission-denied.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/microphone-permission-denied.md
@@ -13,7 +13,7 @@ ms.subservice: calling
 ---
 
 # microphonePermissionDenied UFD
-The `microphonePermissionDenied` UFD with a `true` value occurs when the SDK detects that the microphone permission was denied either at browser or OS level.
+The `microphonePermissionDenied` UFD event with a `true` value occurs when the SDK detects that the microphone permission was denied either at browser or OS level.
 
 | microphonePermissionDenied            | Details                |
 | --------------------------------------|------------------------|
@@ -26,7 +26,7 @@ The `microphonePermissionDenied` UFD with a `true` value occurs when the SDK det
 call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'microphonePermissionDenied') {
        if (diagnosticInfo.value === true) {
-           // microphonePermissionDenied UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The microphonePermissionDenied UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-receive-quality.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-receive-quality.md
@@ -13,9 +13,9 @@ ms.subservice: calling
 ---
 
 # networkReceiveQuality UFD
-The `networkReceiveQuality` UFD with a `Bad` value indicates the presence of network quality issues for incoming streams, as detected by the ACS Calling SDK.
+The `networkReceiveQuality` UFD event 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.
+When this UFD event fires with a`Bad` value, the user may experience degraded audio quality.
 
 | networkReceiveQualityUFD | Details                |
 | -------------------------|------------------------|
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-reconnect.md b/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 a `Bad` value occurs when the Interactive Connectivity Establishment (ICE) transport state on the connection is `failed`.
+The `networkReconnect` UFD event 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` UFD with a `Bad` value is fired. If the connection recovers, `networkReconnect` UFD with a `Good` value is fired.
+Internally, the ACS Calling SDK will trigger reconnection after a `networkReconnect` UFD event with a `Bad` value is fired. If the connection recovers, `networkReconnect` UFD event 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.
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-relays-not-reachable.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-relays-not-reachable.md
@@ -13,9 +13,9 @@ ms.subservice: calling
 ---
 
 # networkRelaysNotReachable UFD
-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.
+The `networkRelaysNotReachable` UFD event 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.
+When users see the `networkRelaysNotReachable` UFD event, it also indicates that the local client isn't able to make a direct connection to the remote endpoint.
 
 | networkRelaysNotReachable UFD | Details                |
 | ------------------------------|------------------------|
@@ -28,7 +28,7 @@ When users see the `networkRelaysNotReachable` UFD, it also indicates that the l
 call.feature(Features.UserFacingDiagnostics).network.on('diagnosticChanged', (diagnosticInfo) => {
     if (diagnosticInfo.diagnostic === 'networkRelaysNotReachable') {
        if (diagnosticInfo.value === true) {
-           // networkRelaysNotReachable UFD, show a warning message on UI
+           // show a warning message on UI
        } else {
            // The networkRelaysNotReachable UFD recovered, notify the user
        }
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/network-send-quality.md b/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 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.
+The `networkSendQuality` UFD event 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.
 
 
@@ -40,7 +40,7 @@ From the perspective of the ACS Calling SDK, network issues are considered exter
 To solve network issues, it's typically necessary to have an understanding of the network topology and the nodes that are causing the problem.
 These parts involve network infrastructure, which is outside the scope of the ACS Calling SDK.
 
-Your application should subscribe to events from the User Facing Diagnostics and display a message on the user interface, so that users are aware of network quality issues. While these issues are often temporary and recover soon, frequent occurrences of the `networkSendQuality` UFD for a particular user may require further investigation.
+Your application should subscribe to events from the User Facing Diagnostics and display a message on the user interface, so that users are aware of network quality issues. While these issues are often temporary and recover soon, frequent occurrences of the `networkSendQuality` UFD event for a particular user may require further investigation.
 For example, users should check their network equipment or check with their internet service provider (ISP).
 
 ## Next steps
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-microphone-devices-enumerated.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-microphone-devices-enumerated.md
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-network.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-network.md
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-speaker-devices-enumerated.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/no-speaker-devices-enumerated.md
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/screenshare-recording-disabled.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/screenshare-recording-disabled.md
diff --git a/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/speaking-while-microphone-is-muted.md b/articles/communication-services/resources/troubleshooting/voice-video-calling/references/ufd/speaking-while-microphone-is-muted.md

Original file line number	Diff line number	Diff line change
@@ -26,7 +26,7 @@ The `cameraPermissionDenied` UFD event with a `true` value occurs when the SDK d
`26`	`26`	`call.feature(Features.UserFacingDiagnostics).media.on('diagnosticChanged', (diagnosticInfo) => {`
`27`	`27`	`if (diagnosticInfo.diagnostic === 'cameraPermissionDenied') {`
`28`	`28`	`if (diagnosticInfo.value === true) {`
`29`		`- // camera permission denied, show a warning message on UI`
	`29`	`+ // show a warning message on UI`
`30`	`30`	`} else {`
`31`	`31`	`// The cameraPermissionDenied UFD recovered, notify the user`
`32`	`32`	`}`