Fix Large data use cases Reliability kind typo (#505)

Signed-off-by: JesusPoderoso <[email protected]> (cherry picked from commit 6e05d74) Co-authored-by: Jesús Poderoso <[email protected]>
eProsima · Jun 13, 2023 · 4f9dc2a · 4f9dc2a
1 parent 5b2aa0b
commit 4f9dc2a
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/docs/fastdds/use_cases/large_data/large_data.rst b/docs/fastdds/use_cases/large_data/large_data.rst
@@ -294,7 +294,7 @@ If the message rate is high and the network is not reliable (i.e., lots of packe
 DataWriter can be filled up, blocking the publication of new messages until any
 of the old messages is acknowledged by all subscribers.
 
-If this strictness is not needed, :ref:`historyqospolicykind` can be set as |KEEP_ALL_HISTORY_QOS-api|.
+If this strictness is not needed, :ref:`historyqospolicykind` can be set as |KEEP_LAST_HISTORY_QOS-api|.
 In this case, when the history of the DataWriter is full, the oldest message that has not
 been fully acknowledged yet is overridden with the new one.
 If any subscriber did not receive the discarded message, the publisher