From 8e81d333e623cf16dff82c250bf239eefd7e8e8a Mon Sep 17 00:00:00 2001
From: elianalf <62831776+elianalf@users.noreply.github.com>
Date: Fri, 17 May 2024 09:55:54 +0200
Subject: [PATCH] Refs #20849: Apply suggestions

Signed-off-by: elianalf <62831776+elianalf@users.noreply.github.com>
---
 code/XMLTester.xml                            |  2 +-
 .../non_consolidated_qos.rst                  | 25 +++++++++++++------
 2 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/code/XMLTester.xml b/code/XMLTester.xml
index 9855496f4..cc8c3b8c6 100644
--- a/code/XMLTester.xml
+++ b/code/XMLTester.xml
@@ -3258,7 +3258,7 @@
 <data_writer profile_name="max_msg_size_datawriter_xml_profile">
     <propertiesPolicy>
         <properties>
-            <!-- Set the maximum size in bytes for all RTPS datagrams sent by the participant -->
+            <!-- Set the maximum size in bytes for all RTPS datagrams sent by the writer -->
             <property>
                 <name>fastdds.max_message_size</name>
                 <value>1200</value>
diff --git a/docs/fastdds/property_policies/non_consolidated_qos.rst b/docs/fastdds/property_policies/non_consolidated_qos.rst
index f6b958fc1..17d91f7bb 100644
--- a/docs/fastdds/property_policies/non_consolidated_qos.rst
+++ b/docs/fastdds/property_policies/non_consolidated_qos.rst
@@ -360,14 +360,15 @@ Maximum Message Size
 One common requirement is the differentiation between the maximum size of received and sent datagrams.
 This capability is especially important in scenarios where a system might need to handle large incoming
 data sizes but should restrict the size of the data it sends to prevent overwhelming network resources
-or complying with network traffic policies. The primary attribute for controlling datagram size is
-`maxMessageSize`, which sets the upper limit for both the size of datagrams that can be received and
-those that can be sent. For applications that need to restrict the size of outgoing datagrams without
-changing the size of incoming ones, it's possible to set the new property ``fastdds.max_message_size``.
+or complying with network traffic policies.
+The primary attribute for controlling datagram size is `maxMessageSize`, which sets the upper limit
+for both the size of datagrams that can be received and those that can be sent.
+Property ``fastdds.max_message_size`` allows restricting the size of outgoing datagrams without
+changing the size of incoming ones.
 This property allows for the specific configuration of the maximum number of bytes for datagrams that
-are sent. By configuring this property to a value lower than the smallest `maxMessageSize` across all
-transports, applications can achieve a lower sending limit while maintaining the ability to receive
-larger datagrams.
+are sent.
+By configuring this property to a value lower than the smallest `maxMessageSize` across all transports,
+applications can achieve a lower sending limit while maintaining the ability to receive larger datagrams.
 
 .. list-table::
    :header-rows: 1
@@ -384,6 +385,11 @@ larger datagrams.
     An invalid value of ``fastdds.max_message_size`` would log an error,
     and the default value will be used.
 
+.. _setting_max_message_size_participant:
+
+Setting ``fastdds.max_message_size`` At Participant Level
+"""""""""""""""""""""""""""""""""""""""""""""""""""""""""
+
 .. tabs::
 
     .. tab:: C++
@@ -402,6 +408,11 @@ larger datagrams.
             :end-before: <!--><-->
             :lines: 2,4-16
 
+.. _setting_max_message_size_writer:
+
+Setting ``fastdds.max_message_size`` At Writer Level
+""""""""""""""""""""""""""""""""""""""""""""""""""""
+
 .. tabs::
 
     .. tab:: C++