diff --git a/projects/rocprofiler-sdk/source/docs/how-to/using-rocpd-output-format.rst b/projects/rocprofiler-sdk/source/docs/how-to/using-rocpd-output-format.rst
index f4f6a3d9fc..74c12ca98e 100644
--- a/projects/rocprofiler-sdk/source/docs/how-to/using-rocpd-output-format.rst
+++ b/projects/rocprofiler-sdk/source/docs/how-to/using-rocpd-output-format.rst
@@ -61,7 +61,9 @@ To transform database files into target formats, run the ``rocpd convert`` comma
 
     /opt/rocm/bin/rocpd convert -i <input-file>.db --output-format csv
 
-  The converted CSV files are generated as ``rocpd-output-data/out_hip_api_trace.csv``, where the ``rocpd-output-data`` is relative to the current working directory.
+  The CSV conversion process generates a consolidated trace output file ``rocpd-output-data/out_regions_trace.csv`` path relative to the current working directory.
+
+This consolidated approach replaces the previous API-specific CSV files (``out_hip_api_trace.csv``, ``out_hsa_api_trace.csv``, ``out_marker_api_trace.csv``, etc.) to provide comprehensive coverage of all traced regions, including MPI functions, pthread functions, and other regions captured by rocprofiler-systems beyond the core ROCm APIs.
 
 - **OTF2 format conversion**