clean up

Author: enricohuang

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

@@ -66,6 +66,3 @@ This means if there's a [`networkReconnect`](../../../../concepts/voice-video-ca
 If there are network issues from the connection on the receiver's side, your application should subscribe to the video after [`networkReconnect`](../../../../concepts/voice-video-calling/user-facing-diagnostics.md?pivots=platform-web#network-values) UFD is recovered.
 You'll likely have limited control over network issues. Thus, we advise monitoring the network information and presenting the information on the user interface. You should also consider monitoring your client [media quality and network status](../../../../concepts/voice-video-calling/media-quality-sdk.md?pivots=platform-web) and make necessary changes to your client as needed. For instance, you might consider automatically turning off incoming video streams when you notice that the client is experience degraded network performance.
 
-### When a user enables the camera while waiting in the lobby
-In an ACS to Teams call, if other participants attempt to subscribe to a video while the video sender is still in the lobby, the [`createView`](/javascript/api/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview)  API fails
-because of no incoming video frames are received while the sender is still in the lobby.

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

@@ -56,7 +56,6 @@ Here we list several common video issues, along with potential causes for each i
 * The video sender experiences network issues
 * The receiver experiences network issues
 * The frames are received but not decoded
-* The participant enables the camera while waiting in the lobby
 
 ### The user only sees black video from the remote participant
 * The video sender's browser is in the background

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

@@ -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/%40azure/communication-react/statefulcallclient?view=azure-node-latest&preserve-view=true#@azure-communication-react-statefulcallclient-createview) API.
 In such case, applications can check isAvailable again before invoking the createView API.