Fix links

Author: enricohuang

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

@@ -62,5 +62,5 @@ If the speaking participant is using your application, you can follow this flow
 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.
 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#@azure-communication-calling-call-mute) and [unmute](https://learn.microsoft.com/en-us/javascript/api/azure-communication-services/@azure/communication-calling/call?view=azure-communication-services-js#@azure-communication-calling-call-unmute).
+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.

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

@@ -26,7 +26,7 @@ The listener should check for events with the value of `microphonePermissionDeni
 It's important to note that if the user revokes access permission during the call, this `microphonePermissionDenied`  event also fires.
 
 ## How to mitigate or resolve
-Your application should always call the [askDevicePermission](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js#@azure-communication-calling-devicemanager-askdevicepermission) API after the `CallClient` is initialized.
+Your application should always call the [askDevicePermission](/javascript/api/azure-communication-services/@azure/communication-calling/devicemanager?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-devicemanager-askdevicepermission) API after the `CallClient` is initialized.
 This way gives the user a chance to grant the device permission if they didn't do so before or if the permission state is `prompt`.
 The application can also show a warning message if the user denies the permission, so the user can fix it before joining a call.
 
@@ -44,5 +44,5 @@ If the speaking participant is using your application, you can follow this flow
 3. The app must call `askDevicePermission` if this API has not been invoked before the user joins the call. By determining the current state of permissions, the app can offer a smoother user experience. For instance, it can display a message instructing the user to adjust their permissions if necessary.
 4. If the app has called `askDevicePermission` API, but the user still gets a `microphonePermissionDenied` Bad UFD event. The user has to reset or grant the microphone permission in the browser. If they have confirmed that the permission is granted in the browser, they should check if the OS is blocking mic access to the browser.
 5. If there is no `microphonePermissionDenied` Bad UFD, we need to consider other possiblities. For the speaking participant, there might be other potential reasons for issues with outgoing audio, such as network reconnection, or device issues.
-6. If there is a `networkReconnect` Bad UFD, the outgoing audio may be temporarily lost due to a network disconnection. See [There's a network issue in the call](./network-issue) for detailed information.
-7. If no `networkReconnect` Bad UFD occurs, there might be a problem on the speaking participant's microphone. See [The speaking participant's microphone has a problem](./microphone-issue) for detailed information.
+6. If there is a `networkReconnect` Bad UFD, the outgoing audio may be temporarily lost due to a network disconnection. See [There's a network issue in the call](./network-issue.md) for detailed information.
+7. If no `networkReconnect` Bad UFD occurs, there might be a problem on the speaking participant's microphone. See [The speaking participant's microphone has a problem](./microphone-issue.md) for detailed information.

articles/communication-services/resources/troubleshooting/voice-video-calling/video-issues/application-disposes-video-renderer.md

@@ -12,9 +12,9 @@ ms.service: azure-communication-services
 ms.subservice: calling
 ---
 # Your application disposes the video renderer while subscribing to a video
-The [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview)  API doesn't resolve immediately, as there are multiple underlying asynchronous operations involved in the video subscription process and thus this API response is an asynchronous response.
+The [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API doesn't resolve immediately, as there are multiple underlying asynchronous operations involved in the video subscription process and thus this API response is an asynchronous response.
 
-If your application disposes of the render object while the video subscription is in progress, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API throws an error.
+If your application disposes of the render object while the video subscription is in progress, the [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API throws an error.
 
 ## How to detect using the SDK
 

articles/communication-services/resources/troubleshooting/voice-video-calling/video-issues/create-view-timeout.md

@@ -18,7 +18,7 @@ the SDK detects this issue and throws an createView timeout error.
 
 This error is unexpected from SDK's perspective. This error indicates a discrepancy between signaling and media transport.
 ## How to detect using SDK
-When there's a `create view timeout` issue, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API throws an error.
+When there's a `create view timeout` issue, the  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API throws an error.
 
 | Error            | Details                                               |
 |------------------|-------------------------------------------------------|
@@ -30,12 +30,12 @@ When there's a `create view timeout` issue, the [`createView`](/javascript/api/%
 ## Reasons behind createView timeout failures and how to mitigate the issue
 ### The video sender's browser is in the background
 Some mobile devices don't send any video frames when the browser is in the background or a user locks the screen.
-The [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API detects no incoming video frames and considers this situation a subscription failure, therefore, it throws a createView timeout error.
+The  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API detects no incoming video frames and considers this situation a subscription failure, therefore, it throws a createView timeout error.
 No further detailed information is available because currently the SDK doesn't support notifying receivers that the sender's browser is in the background.
 
 Your application can implement its own detection mechanism and notify the participants in a call when the sender's browser goes back to foreground.
 The participants can subscribe the video again.
-A feasible but less elegant approach for handling this createView timeout error is to continuously retry invoking the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API until it succeeds.
+A feasible but less elegant approach for handling this createView timeout error is to continuously retry invoking the  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API until it succeeds.
 
 ### The video sender dropped from the call unexpectedly
 Some users might end the call by terminating the browser process instead of by hanging up.
@@ -50,7 +50,7 @@ If the video sender has network issues during the time other participants are su
 This error is unexpected on the video receiver's side.
 For example, if the sender experiences a temporary network disconnection, other participants are unable to receive video frames from the sender. 
 
-A workaround approach for handling this createView timeout error is to continuously retry invoking [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API until it succeeds when this network event is happening.
+A workaround approach for handling this createView timeout error is to continuously retry invoking  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API until it succeeds when this network event is happening.
 
 ### The video receiver has network issues
 Similar to the sender's network issues, if a video receiver has network issues the video subscription may fail.

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

@@ -30,7 +30,7 @@ After the SDK completes the handshake at the signaling layer with the server, it
 The browser performs video encoding and packetization at the RTP(Real-time Transport Protocol) layer for transmission.
 The other participants in the call receive notifications from the server, indicating the availability of a video stream from the sender.
 Your application can decide whether to subscribe to the video stream or not. 
-If your application subscribes to the video stream from the server (for example, using [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API), the server forwards the sender's video packets to the receiver.
+If your application subscribes to the video stream from the server (for example, using  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API), the server forwards the sender's video packets to the receiver.
 The receiver's browser decodes and renders the incoming video.
 
 When you use ACS Web Calling SDK for video calls, the SDK and browser may adjust the video quality of the sender based on the available bandwidth.

articles/communication-services/resources/troubleshooting/voice-video-calling/video-issues/reaching-max-number-of-active-video-subscriptions.md

@@ -15,7 +15,7 @@ ms.subservice: calling
 Azure Communication Service currently imposes a maximum limit on the number of active incoming video subscriptions that are rendered at a time. The current limit is 10 videos on desktop browsers and 6 videos on mobile browsers. Review the [supported browser list](../../../../concepts/voice-video-calling/calling-sdk-features.md#javascript-calling-sdk-support-by-os-and-browser) to see what browsers currently work with Azure Communication Services WebJS SDK.
 
 ## How to detect using the SDK
-If the number of active video subscriptions exceeds the limit, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API throws an error.
+If the number of active video subscriptions exceeds the limit, the  [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API throws an error.
 
 
 | Error details    | Details                                               |

articles/communication-services/resources/troubleshooting/voice-video-calling/video-issues/remote-video-becomes-unavailable.md

@@ -18,7 +18,7 @@ The SDK detects this change and throws an error.
 
 This error is expected from SDK's perspective as the remote endpoint stops sending the video.
 ## How to detect using the SDK
-If the video becomes unavailable before the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API finishes, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API throws an error.
+If the video becomes unavailable before the [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API finishes, the [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API throws an error.
 
 | error            | Details                                               |
 |------------------|-------------------------------------------------------|

articles/communication-services/resources/troubleshooting/voice-video-calling/video-issues/subscribing-video-not-available.md

@@ -18,7 +18,7 @@ Subscribing a video in this case results in failure.
 
 This error is expected from SDK's perspective as applications shouldn't subscribe to a video that is currently not available.
 ## How to detect using the SDK
-If you subscribe to a video that is unavailable, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API throws an error.
+If you subscribe to a video that is unavailable, the [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API throws an error.
 
 
 | error            | Details                                               |
@@ -33,5 +33,5 @@ While the SDK throws an error in this scenario,
 applications should refrain from subscribing to a video when the remote video isn't available, as it doesn't satisfy the precondition.
 
 The recommended practice is to monitor the isAvailable change within the `isAvailable` event callback function and to subscribe to the video when `isAvailable` changes to `true`.
-However, if there's asynchronous processing in the application layer, that might cause some delay before invoking [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API.
+However, if there's asynchronous processing in the application layer, that might cause some delay before invoking [`createView`](/javascript/api/azure-communication-services/@azure/communication-calling/videostreamrenderer?view=azure-communication-services-js&preserve-view=true#@azure-communication-calling-videostreamrenderer-createview) API.
 In such case, applications can check isAvailable again before invoking the createView API.