Update for 2.5.3 release

Author: dolbyio-gh-bot

docs/.buildinfo

@@ -1,4 +1,4 @@
 # Sphinx build info version 1
 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done.
-config: 15cdc79de79cedec229ed6d21d0af612
+config: 135432971695597e094c4d465df306dc
 tags: 645f666f9bcd5a90fca523b33c5a78b7

docs/.doctrees/api/sdk/device_management.doctree

@@ -50,6 +50,9 @@ The :ref:`api_device_management` events that are emitted by the SDK. They can be
 .. doxygenstruct:: dolbyio::comms::video_device_error
 	:project: C++ SDK
 
+.. doxygenstruct:: dolbyio::comms::screen_share_error
+	:project: C++ SDK
+
 .. _devman_models:
 
 Device Structs

docs/.doctrees/api/sdk/video.doctree

@@ -3,9 +3,6 @@
 Video Service
 =============
 
-.. note::
-  The Video Service is considered to be in Beta phase on Linux systems.
-
 The Video Service allows managing the local participant's video stream as well as attaching a Video Sink to remote video streams.
 
 Video interface
@@ -27,8 +24,14 @@ The remote video API allows attaching a :cpp:class:`Video Sink <dolbyio::comms::
 
 .. _vid_frame_handle:
 
+Video Forwarding Startegy
+_________________________
+Using the :cpp:enum:`Video Forwarding Strategy <dolbyio::comms::video_forwarding_strategy>` option when :cpp:func:`joining a conference <dolbyio::comms::services::conference::join>` applications can set how many video streams they want forwarded to them. They can then :cpp:func:`subscribe <dolbyio::comms::utils::vfs_event::add_event_handler>` to the :cpp:class:`vfs event <dolbyio::comms::utils::vfs_event>` which can be used to know which participants streams are being forwarded to them at a given time and thus which streams to render.
+
+.. doxygenstruct:: dolbyio::comms::utils::vfs_event
+
 Video frame handling
---------------------
+---------------------
 #include <dolbyio/comms/media_engine/media_engine.h>
 
 The application can use the :cpp:class:`video frame handling <dolbyio::comms::video_frame_handler>` capabilities of the SDK to process captured :cpp:class:`VideoFrames <dolbyio::comms::video_frame>`. The frame handler is an interface providing a :cpp:class:`Video Sink <dolbyio::comms::video_sink>` and a :cpp:class:`Video Source <dolbyio::comms::video_source>`, thus inserting the frame handler into the video capture pipeline allows the application to receive, process, and then inject 

docs/.doctrees/environment.pickle

@@ -1,6 +1,6 @@
 var DOCUMENTATION_OPTIONS = {
     URL_ROOT: document.getElementById("documentation_options").getAttribute('data-url_root'),
-    VERSION: '2.5.2',
+    VERSION: '2.5.3',
     LANGUAGE: 'en',
     COLLAPSE_INDEX: false,
     BUILDER: 'html',

docs/.doctrees/index.doctree

@@ -4,7 +4,7 @@
   <meta charset="utf-8" /><meta name="generator" content="Docutils 0.19: https://docutils.sourceforge.io/" />
 
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Core API &mdash; C++ SDK 2.5.2 documentation</title>
+  <title>Core API &mdash; C++ SDK 2.5.3 documentation</title>
       <link rel="stylesheet" href="../_static/pygments.css" type="text/css" />
       <link rel="stylesheet" href="../_static/css/theme.css" type="text/css" />
       <link rel="stylesheet" href="../_static/graphviz.css" type="text/css" />

docs/_sources/api/sdk/device_management.rst.txt

@@ -4,7 +4,7 @@
   <meta charset="utf-8" /><meta name="generator" content="Docutils 0.19: https://docutils.sourceforge.io/" />
 
   <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-  <title>Audio &mdash; C++ SDK 2.5.2 documentation</title>
+  <title>Audio &mdash; C++ SDK 2.5.3 documentation</title>
       <link rel="stylesheet" href="../../_static/pygments.css" type="text/css" />
       <link rel="stylesheet" href="../../_static/css/theme.css" type="text/css" />
       <link rel="stylesheet" href="../../_static/graphviz.css" type="text/css" />