Update deprecated API

Signed-off-by: Carlos Ferreira González <carlosferreira@eprosima.com>

Author: cferreiragonz

docs/03-exports/aliases-api.include

@@ -936,11 +936,11 @@
 
 .. |RTPSWriters-api| replace:: :cpp:class:`RTPSWriters <eprosima::fastdds::rtps::RTPSWriter>`
 .. |WriterAttributes-api| replace:: :cpp:class:`WriterAttributes<eprosima::fastdds::rtps::WriterAttributes>`
-.. |RTPSWriters::new_change-api| replace:: :cpp:func:`RTPSWriter::new_change() <eprosima::fastdds::rtps::RTPSWriter::new_change>`
 
 .. |History-api| replace:: :cpp:class:`History <eprosima::fastdds::rtps::History>`
 .. |WriterHistory-api| replace:: :cpp:class:`WriterHistory <eprosima::fastdds::rtps::WriterHistory>`
 .. |WriterHistory::add_change-api| replace:: :cpp:func:`WriterHistory::add_change() <eprosima::fastdds::rtps::WriterHistory::add_change>`
+.. |WriterHistory::create_change-api| replace:: :cpp:func:`WriterHistory::create_change() <CacheChange_t* eprosima::fastdds::rtps::WriterHistory::create_change(uint32_t payload_size, ChangeKind_t change_kind, InstanceHandle_t handle)>`
 .. |ReaderHistory-api| replace:: :cpp:class:`ReaderHistory <eprosima::fastdds::rtps::ReaderHistory>`
 .. |CacheChange_t-api| replace:: :cpp:class:`CacheChange_t<eprosima::fastdds::rtps::CacheChange_t>`
 

docs/fastdds/rtps_layer/rtps_layer.rst

@@ -94,9 +94,9 @@ Changes are always managed by the History.
 You can add a new :class:`CacheChange_t` to the History of the Writer to send data.
 The procedure is as follows:
 
-1. Request a :class:`CacheChange_t` from the Writer with |RTPSWriters::new_change-api|.
+1. Request a :class:`CacheChange_t` from the Writer History with |WriterHistory::create_change-api|.
    In order to allocate enough memory,
-   you need to provide a callback that returns the maximum number bytes in the payload.
+   you need to provide as argument the maximum number of bytes in the payload.
 2. Fill the :class:`CacheChange_t` with the data.
 3. Add it to the History with |WriterHistory::add_change-api|.