Address Acrolinx comment

Author: enricohuang

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/incoming-audio-low-volume.md

@@ -28,7 +28,7 @@ This value is derived from `audioLevel` in WebRTC Stats. [https://www.w3.org/TR/
 A low `audioOutputLevel` value indicates that the volume sent by the sender is also low.
 
 ## How to mitigate or resolve
-If the `audioOutputLevel` value is low, this is likely that the volume sent by the sender is also low.
+If the `audioOutputLevel` value is low, it's likely that the volume sent by the sender is also low.
 To troubleshoot this issue, users should investigate why the audio input volume is low on the sender's side.
 This problem could be due to various factors, such as microphone settings, or hardware issues.
 
@@ -53,10 +53,10 @@ Below is a flow diagram of the troubleshooting process for this issue.
 
 :::image type="content" source="./media/low-volume-troubleshooting.svg" alt-text="Diagram of troubleshooting the low volume issue.":::
 
-1. When a user reports experiencing low audio volume, the first thing to check is whether the the volume of the incoming audio is low. The application can obtain this information by checking `audioOutputLevel` in the mediastats.
+1. When a user reports experiencing low audio volume, the first thing to check is whether the volume of the incoming audio is low. The application can obtain this information by checking `audioOutputLevel` in the media stats.
 2. If the `audioOutputLevel` value is constantly low, it indicates that the volume of audio sent by the speaking participant is low. In this case, ask the user to verify if the speaking participant has issues with their microphone device or input volume settings.
-3. If the `audioOutputLevel` value is not always low, the user may still experience low audio volume issue due to system volume settings. Ask the user to check their system volume settings. 
+3. If the `audioOutputLevel` value isn't always low, the user may still experience low audio volume issue due to system volume settings. Ask the user to check their system volume settings. 
 4. If the user's system volume is set to a low value, the user should increase the volume in the settings.
-5. In some systems that support app-specific volume settings, the audio volume output from the app may be low even if system volume is not. In this case, the user should check their volume setting of the app within the system.
+5. In some systems that support app-specific volume settings, the audio volume output from the app may be low even if system volume isn't low. In this case, the user should check their volume setting of the app within the system.
 6. If the volume setting of the app in the system is low, the user should increase it.
-7. If you still cannot determine why the audio output volume is low, ask the user to check their speaker device or select another audio output device. The issue may be due to a device problem and not related to the software or operating system. Note that not all platforms support speaker enumeration in the browser. For example, you cannot select an audio output device through the JavaScript API in the Safari browser or in Chrome on Android. In these cases, you should configure the audio output device in the system settings.
+7. If you still can't determine why the audio output volume is low, ask the user to check their speaker device or select another audio output device. The issue may be due to a device problem and not related to the software or operating system. Not all platforms support speaker enumeration in the browser. For example, you can't select an audio output device through the JavaScript API in the Safari browser or in Chrome on Android. In these cases, you should configure the audio output device in the system settings.

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/microphone-issue.md

@@ -45,22 +45,22 @@ By doing so, the user is aware of the issue and can troubleshoot by switching to
 
 ## References
 ### Troubleshooting process
-If a user cannot hear sound during a call, one possibility is that the speaking participant has an issue with their microphone.
+If a user can't hear sound during a call, one possibility is that the speaking participant has an issue with their microphone.
 If the speaking participant is using your application, you can follow this flow diagram to troubleshoot the issue.
 
 :::image type="content" source="./media/microphone-issue-troubleshooting.svg" alt-text="Diagram of troubleshooting the microphone issue.":::
 
 1. First, check if a microphone is available. The application can obtain this information by invoking `DeviceManager.getMicrophone` API or by detecting a `noMicrophoneDevicesEnumerated` UFD Bad event.
 2. If no microphone device is available, prompt the user to plug in a microphone.
-3. If a microphone is available but there is no outgoing audio, consider other possibilities such as permission issues, device issues, or network problems.
+3. If a microphone is available but there's no outgoing audio, consider other possibilities such as permission issues, device issues, or network problems.
 4. If permission is denied, refer to [The speaking participant doesn't grant the microphone permission](./microphone-permission.md) for more information.
-5. If permission is granted, consider the whether the issue is due to a external problem, such as `microphoneMuteUnexpectedly` UFD.
-6. The `microphoneMuteUnexpectedly` UFD Bad event is triggered when the browser mutes the audio input track. The application can monitor this UFD but is not able to detect the reason at JavaScript layer. You can still provide instructions in the app and ask if the user is using hardware mute button on their headset.
+5. If permission is granted, consider whether the issue is due to an external problem, such as `microphoneMuteUnexpectedly` UFD.
+6. The `microphoneMuteUnexpectedly` UFD Bad event is triggered when the browser mutes the audio input track. The application can monitor this UFD but isn't able to detect the reason at JavaScript layer. You can still provide instructions in the app and ask if the user is using hardware mute button on their headset.
 7. If the user releases the hardware mute and the `microphoneMuteUnexpectedly` UFD recovers, the issue is resolved.
-8. If the user is not using the hardware mute, ask the user to unplug and replug the microphone, or to select another microphone. Ensure the user has not muted the microphone at the system level.
-9. No outgoing audio issue can also happen when there is a `microphoneNotFunctioning` UFD Bad event.
-10. If there is no `microphoneNotFunctioning` UFD Bad event, consider other possiblities, such as network issues.
-11. If there is a `networkReconnect` Bad UFD, outgoing audio may be temporarily lost due to a network disconnection. Refer to [There's a network issue in the call](./network-issue.md) for detailed information.
+8. If the user isn't using the hardware mute, ask the user to unplug and replug the microphone, or to select another microphone. Ensure the user hasn't muted the microphone at the system level.
+9. No outgoing audio issue can also happen when there's a `microphoneNotFunctioning` UFD Bad event.
+10. If there's no `microphoneNotFunctioning` UFD Bad event, consider other possibilities, such as network issues.
+11. If there's a `networkReconnect` Bad UFD, outgoing audio may be temporarily lost due to a network disconnection. Refer to [There's a network issue in the call](./network-issue.md) for detailed information.
 12. If there are no microphone-related events and no network-related events, create a support ticket for ACS team to investigate the issue. Refer to [Reporting an issue](../general-troubleshooting-strategies/report-issue.md).
 13. If a `microphoneNotFunctioning` UFD Bad event occurs, and the user has no outgoing audio, they can try to recover the stream by using ACS [mute](/javascript/api/azure-communication-services/@azure/communication-calling/call?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-call-mute) and [unmute](/javascript/api/azure-communication-services/@azure/communication-calling/call?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-call-unmute).
-14. If the `microphoneNotFunctioning` UFD doesn't recover after the user performs ACS mute and unmute, there might be an issue with the microphone device. Ask the user to unplug and replug the microhpone or select another microphone.
+14. If the `microphoneNotFunctioning` UFD doesn't recover after the user performs ACS mute and unmute, there might be an issue with the microphone device. Ask the user to unplug and replug the microphone or select another microphone.

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/network-issue.md

@@ -34,14 +34,14 @@ users on the receiving end are unable to know about it because currently the SDK
 
 ## References
 ### Troubleshooting process
-If a user cannot hear sound during a call, one possibility is that the speaking participant or the receiving end has network issues.
+If a user can't hear sound during a call, one possibility is that the speaking participant or the receiving end has network issues.
 
 Below is a flow diagram of the troubleshooting process for this issue.
 
 :::image type="content" source="./media/network-issue-troubleshooting.svg" alt-text="Diagram of troubleshooting the network issue.":::
 
-1. First, check if there is a `networkReconnect` UFD. The user may experience audio loss during the network reconnection.
-2. The UFD can happen on either the sender's end or the receiver's end. In both cases, packets don't flow, so the user cannot hear the audio.
-3. If there is no `networkReconnect` UFD, consider other potential causes, such as permission issues or device problems.
+1. First, check if there's a `networkReconnect` UFD. The user may experience audio loss during the network reconnection.
+2. The UFD can happen on either the sender's end or the receiver's end. In both cases, packets don't flow, so the user can't hear the audio.
+3. If there's no `networkReconnect` UFD, consider other potential causes, such as permission issues or device problems.
 4. If the permission is denied, refer to [The speaking participant doesn't grant the microphone permission](./microphone-permission.md) for more information.
 5. The issue could also be due to device problems, refer to [The speaking participant's microphone has a problem](./microphone-issue.md).

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/poor-quality.md

@@ -66,11 +66,11 @@ Below is a flow diagram of the troubleshooting process for this issue.
 
 :::image type="content" source="./media/poor-audio-quality-issue-troubleshooting.svg" alt-text="Diagram of troubleshooting the poor audio quality issue.":::
 1. When a user reports experiencing poor audio quality during a call, the first thing to check is the source of the issue. It could be coming from the sender's side or the receiver's side. If other participants on different networks also have similar issues, it's very possible that the issue comes from the sender's side.
-2. Check if there is `networkSendQuality` UFD Bad event on the sender's side.
-3. If there is no `networkSendQuality` UFD Bad event on the sender's side, the poor audio could be due to device issues or audio distortion caused by the browser's audio processing module. Ask the user to collect diagnostic audio recordings from the browser. Refer to [How to collect diagnostic audio recordings](../references/how-to-collect-diagnostic-audio-recordings.md)
-4. If there is a `networkSendQuality` UFD Bad event, the poor audio quality might be due to the sender's network issues. Check the sender's network.
+2. Check if there's `networkSendQuality` UFD Bad event on the sender's side.
+3. If there's no `networkSendQuality` UFD Bad event on the sender's side, the poor audio could be due to device issues or audio distortion caused by the browser's audio processing module. Ask the user to collect diagnostic audio recordings from the browser. Refer to [How to collect diagnostic audio recordings](../references/how-to-collect-diagnostic-audio-recordings.md)
+4. If there's a `networkSendQuality` UFD Bad event, the poor audio quality might be due to the sender's network issues. Check the sender's network.
 5. If the user experiences poor audio quality but no other participants have the same issue, and there are only two participants in the call, still check the sender's network.
 6. If the user experiences poor audio quality but no other participants have the same issue in a group call, the issue might be due to the receiver's network. Check for a `networkReceiveQuality` UFD Bad event on the receiver's end.
-7. If there is a `networkReceiveQuality` UFD Bad event, check the receiver's network.
-8. If you cannot find a `networkReceiveQuality` UFD Bad event, check if other mediastats metrics on the receiver's end are poor, such as packetsLost, jitter, etc.
-9. If you cannot determine why the audio quality on the receiver's end is poor, create a support ticket for the ACS team to investigate.
+7. If there's a `networkReceiveQuality` UFD Bad event, check the receiver's network.
+8. If you can't find a `networkReceiveQuality` UFD Bad event, check if other media stats metrics on the receiver's end are poor, such as packetsLost, jitter, etc.
+9. If you can't determine why the audio quality on the receiver's end is poor, create a support ticket for the ACS team to investigate.

articles/communication-services/resources/troubleshooting/voice-video-calling/audio-issues/speaker-issue.md

@@ -35,7 +35,7 @@ If the user uses Windows, they should also check the volume mixer settings and a
 
 :::image type="content" source="./media/apps-volume-mixer.png" alt-text="Screenshot of volume mixer.":::
 
-If you are using Web Audio API in your application, you might also check if there's `AudioRenderer error with rendering audio code: 3` in the log.
+If you're using Web Audio API in your application, you might also check if there's `AudioRenderer error with rendering audio code: 3` in the log.
 This error occurs when there are too many AudioContext instances open at the same time, particularly if the application doesn't properly close the AudioContext or 
 if there's an AudioContext creation associated with the UI component refresh logic.
 

articles/communication-services/resources/troubleshooting/voice-video-calling/call-setup-issues/call-setup-takes-too-long.md

@@ -25,7 +25,7 @@ The application can calculate the delay between when the call is initiated and w
 If a user consistently experiences long call setup times, they should check their network for issues such as slow network speed, long round trip time, or high packet loss.
 These issues can affect call setup time because the signaling layer uses a `TCP` connection, and factors such as retransmissions can cause delays.
 Additionally, if the user suspects the delay comes from stream acquisition, they should check their devices. For example, they can choose a different audio input device.
-If a user consistently experiences this issue and you are unable to determine the cause, you may consider filing a support ticket for further assistance.
+If a user consistently experiences this issue and you're unable to determine the cause, you may consider filing a support ticket for further assistance.
 
 ### Check the duration of stream acquisition
 The stream acquisition is part of the call setup flow. You can get this information from webrtc-internals page.