Added receive video constraints

Author: sloanster

articles/communication-services/concepts/voice-video-calling/video-constraints.md

@@ -15,34 +15,18 @@ ms.subservice: calling
 
 # Video constraints
 
-[!INCLUDE [Public Preview Disclaimer](../../includes/public-preview-include.md)]
-
-The Video Constraints API is a powerful tool that enables developers to control the video quality from within their video calls. With this API, developers can set maximum video resolutions, frame rate, and bitrate used so that the call is optimized for the user's device and network conditions. The Azure Communication Services video engine is optimized to allow the video quality to change dynamically based on devices ability and network quality. But there might be certain scenarios where you would want to have tighter control of the video quality that end users experience. For instance, there may be situations where the highest video quality is not a priority, or you may want to limit the video bandwidth usage in the application. To support those use cases, you can use the Video Constraints API to have tighter control over video quality.
+The Video constraints API is a powerful tool that enables developers to control the video quality from within their video calls. With this API, developers can set maximum video resolutions, frame rate, and bitrate used so that the call is optimized for the user's device and network conditions. The ACS video engine is optimized to allow the video quality to change dynamically based on devices ability and network quality. But there might be certain scenarios where you would want to have tighter control of the video quality that end users experience. For instance, there may be situations where the highest video quality is not a priority, or you may want to limit the video bandwidth usage in the application. To support those use cases, you can use the Video Constraints API to have tighter control over video quality.
 
 Another benefit of the Video Constraints API is that it enables developers to optimize the video call for different devices. For example, if a user is using an older device with limited processing power, developers can set constraints on the video resolution to ensure that the video call runs smoothly on that device
 
-## Send constraints
-Azure Communication Services Web Calling SDK supports setting the maximum video resolution, framerate, or bitrate that a client sends. The sender video constraints are supported on Desktop browsers (Chrome, Edge, Firefox) and when using iOS Safari mobile browser or Android Chrome mobile browser.
-
-Azure Communication Services Native Calling SDK (Android, iOS, Windows) supports setting the maximum values of video resolution and framerate for outgoing video streams.
-
-## Receive constraints
-Azure Communication Services Web Calling SDK does not have a dedicated API to control setting the maximum video resolution that client can receive for a given video.
-Instead to control resolution on the receiver side, application can adjust size of the renderer of that video, as SDK will automatically try to adjust received resolution based on the dimensions of the renderer, in practice - SDK will not request more stream (width/height) than it can fit into the renderer.
-
-Azure Communication Services Native Calling SDK (Android, iOS, Windows) supports setting the maximum resolution for incoming video streams. 
-
-
 ## Supported constraints
 
-These constraints can be set at the start of the call and during the call.
-
 | Platform | Supported Constraints | 
 | ----------- | ----------- |
-| Web | Outgoing video: resolution, framerate, bitrate |
-| Android | Incoming video: resolution<br />Outgoing video: resolution, framerate |
-| iOS | Incoming video: resolution<br />Outgoing video: resolution, framerate |
-| Windows | Incoming video: resolution<br />Outgoing video: resolution, framerate |
+| **Web** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate, bitrate |
+| **Android** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate |
+| **iOS** | **Incoming video**: resolution<br />**Outgoing video**: resolution, framerate |
+| **Windows** | **Incoming video**: resolution<br />**Outgoing** video: resolution, framerate |
 
 ## Next steps
 For more information, see the following articles:

articles/communication-services/quickstarts/voice-video-calling/includes/video-constraints/video-constraints-javascript.md

@@ -13,10 +13,13 @@ ms.subservice: calling
 
 You can set video constraints in your calls to control the video quality based on resolution or frameRate or bitrate in your video calls. In this quickstart guide, we'll illustrate how to set video constraints at the start of a call and how to use our `setConstraints` method on the call object to set video constraints dynamically during the call.
 
-> [!NOTE]
-> Currently, we only support setting video send constraints. You cannot set video constraints on incoming videos at this point of time.
 
-## Setting video constraints at the start of a call
+[!INCLUDE [Public Preview](../../../../includes/public-preview-include-document.md)]
+
+## Send video constraints
+Azure Communication Services Web Calling SDK supports setting the maximum video resolution, framerate, or bitrate that a client sends. The sender video constraints are supported on Desktop browsers (Chrome, Edge, Firefox) and when using iOS Safari mobile browser or Android Chrome mobile browser.
+
+### Setting video constraints at the start of a call - outgoing (send) video
 The video constraints setting is implemented on the `Call` interface. To use the Video Constraints, you can specify the constraints from within `CallOptions` when you make a call, accept a call, or join a call. You will also have to specify `localVideoStreams` in `videoOptions`. <br/>
 Do note that constraints don't work if you join a call with audio only option and turn on the camera later. In this case, you can set video constraints dynamically using the `setConstraints` method on the `Call` interface (guide below).
 
@@ -94,7 +97,7 @@ The `frameHeight` in `VideoSendConstraints` has a different meaning when a mobil
 
 If you use MediaStats API to track the sent video resolution, you may find out that the sent resolution can change during the call. It can go up and down, but should be equal or smaller than the constraint value you provide. This resolution change is an expected behavior. The browser also has some degradation rule to adjust sent resolution based on cpu or network conditions.
 
-## Setting video constraints during the call
+### Setting video constraints during the call - outgoing (send) video
 You can set video constraints during the call by using the `setConstraints` method on the `Call` object.
 ```javascript
 // For eg, when you've started a call,
@@ -141,7 +144,12 @@ await currentCall.setConstraints({
 
 <br/>
 
-### Media stats
+## Receive video constraints
+To control resolution on the receiver side usingAzure Communication Services Web Calling SDK you can adjust size of the renderer of that video. The calling SDK will automatically adjust received resolution based on the dimensions of the renderer. The SDK will not request more stream (width annd height) than it can fit into the renderer video window.
+
+
+
+## Using Media statics to understand video constraints impact
 To evaluate and compare the video quality after applying the video constraints, you can access [MediaStats API](../../../../concepts/voice-video-calling/media-quality-sdk.md) to get video resolution and bitrate information of the sending stream. The media stats also include other granular stats related to the streams, such as jitter, packet loss, round trip time, etc.
 
 ```javascript
@@ -152,4 +160,4 @@ mediaStatsCollector.on('sampleReported', (sample: SDK.MediaStatsReportSample) =>
     // process the stats for the call.
     console.log(sample);
 });
-```
+```