update 5

Author: sloanster

articles/communication-services/concepts/voice-video-calling/calling-sdk-features.md

@@ -178,7 +178,7 @@ The Azure Communication Services Calling SDK supports the following streaming co
 | Limit | Web | Windows/Android/iOS |
 | --- | --- | --- |
 | **Maximum # of outgoing local streams that can be sent simultaneously**     | 1 video and 1 screen sharing | 1 video + 1 screen sharing |
-| **Maximum # of incoming remote streams that can be rendered simultaneously** | 16 videos + 1 screen sharing on desktop browsers*, 4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
+| **Maximum # of incoming remote streams that can be rendered simultaneously** | GA Webjs SDK - [16 videos + 1 screen sharing on desktop browsers](../../quickstarts/voice-video-calling/optimizing-video-placement.md#how-many-videos-to-place-in-a-grid-at-a-time) <br />4 videos + 1 screen sharing on web mobile browsers <br /> <br />  Public preview - [25 videos + 1 screen sharing on desktop browser](../../quickstarts/voice-video-calling/optimizing-video-placement.md#how-many-videos-to-place-in-a-grid-at-a-time) <br />4 videos + 1 screen sharing on web mobile browsers | 9 videos + 1 screen sharing |
 
 \* Starting from Azure Communication Services Web Calling SDK version [1.16.3](https://github.com/Azure/Communication/blob/master/releasenotes/acs-javascript-calling-library-release-notes.md#1163-stable-2023-08-24). While the Calling SDK doesn't enforce these limits, your users might experience performance degradation if they're exceeded. Use the API of [Optimal Video Count](../../how-tos/calling-sdk/manage-video.md?pivots=platform-web#remote-video-quality) to determine the number of incoming video streams your web environment can support. To properly support 16 incoming videos, the computer needs a minimum of 16-GB RAM and a 4-core or greater CPU that is less than three years old.
 

articles/communication-services/quickstarts/voice-video-calling/optimizing-video-placement.md

@@ -67,7 +67,7 @@ The optimal video count returns an integer defining the ideal number of videos t
 
 Developers should ensure that their application subscribes to changes in the `Optimal Video Count` in group calls and adjust the number of videos being rendered on a web page dynamically based on the OVC count. The value from optimal video count (OVC) updates every 10 seconds.
 
-You need to reference the feature `OptimalVideoCount` via the feature method of the Call object. You can then set a listener via the *on* method of the `OptimalVideoCountCallFeature` to be notified when the `optimalVideoCount` changes.
+You need to reference the feature `OptimalVideoCount` via the feature method of the Call object. You can then set a listener via the `on` method of the `OptimalVideoCountCallFeature` to be notified when the `optimalVideoCount` changes.
 
 To unsubscribe from the changes, you can call the off method. The current maximum number of incoming videos that can be rendered on a web page is **16**. To properly support 16 incoming videos, the computer should have a minimum of 16-GB RAM and a 4-core or greater CPU that is no older than three years old.