diff --git a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst
index 80c7ed74d..5ae3254c5 100644
--- a/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst
+++ b/source/linux/Foundational_Components_Multimedia_D5520_VXE384.rst
@@ -92,9 +92,10 @@ Software Stack of Accelerated Codec Encoding/Decoding
 As shown in the figures below, the software stack of the accelerated
 encoding and decoding has two parts:
 
-        -  A V4L2 (Video4Linux version 2) software driver running as part of Linux
-        on the A72 MPU subsystem
-        -  The firmware running on the DECODER and ENCODER
+   - A V4L2 (Video4Linux version 2) software driver running as part of Linux on
+     the A72 MPU subsystem
+
+   - The firmware running on the DECODER and ENCODER
 
 The driver communicates with the firmware running on the ENCODER/DECODER
 through its own IPC (inter-processor communication).
@@ -698,7 +699,8 @@ decoder driver support for it. An example of using dmabuf-import in a gstreamer
 pipeline:
 
 .. code-block:: text
-    gst-launch-1.0 filesrc location=<file_location> ! h264parse ! v4l2h264dec capture-io-mode=5 ! kmssink driver-name=tidss
+
+   gst-launch-1.0 filesrc location=<file_location> ! h264parse ! v4l2h264dec capture-io-mode=5 ! kmssink driver-name=tidss
 
 With the TI V4L2 Video Decoder Driver, the best latency performance to display is achieved
 with "dmabuf-import" (GST_V4L2_IO_DMABUF_IMPORT). This feature provides
diff --git a/source/linux/Release_Specific_CoreSDK_Release_Notes.rst b/source/linux/Release_Specific_CoreSDK_Release_Notes.rst
index 25f815d0c..e515f993a 100644
--- a/source/linux/Release_Specific_CoreSDK_Release_Notes.rst
+++ b/source/linux/Release_Specific_CoreSDK_Release_Notes.rst
@@ -50,7 +50,7 @@ Released August 2024
       * SYSFW: v10.00.08
       * DM: 10.00.00.08
   * Important Bug and Stability fixes on top of 9.2 Release
-  ** Review Issue Tracker Section for the new fixes.
+      * Review Issue Tracker Section for the new fixes.
 
 
 Build Information
diff --git a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst
index b06f92a4a..e74572dae 100644
--- a/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst
+++ b/source/rtos/PDK_Platform_Software/Boot_Board_and_EVM_Abstractions/_BOOT_K2G.rst
@@ -140,6 +140,7 @@ Booting via SD Card
 
 | Below is an example of K2G SBL successfully booting the diagnostic
   application:
+
 .. Image:: ../images/K2g_boot_diag.jpg
 
 QSPI Boot Mode
diff --git a/source/rtos/PDK_Platform_Software/IPC/_Use_Cases_for_IPC.rst b/source/rtos/PDK_Platform_Software/IPC/_Use_Cases_for_IPC.rst
index 9313f08e3..ee70a3d22 100644
--- a/source/rtos/PDK_Platform_Software/IPC/_Use_Cases_for_IPC.rst
+++ b/source/rtos/PDK_Platform_Software/IPC/_Use_Cases_for_IPC.rst
@@ -25,6 +25,7 @@ In the following sections, figures show modules used by each scenario.
 
 .. role:: raw-html(raw)
    :format: html
+
 - :raw-html:`<font color="blue">Blue boxes,</font>` identify modules for which your application will call C API functions other than those used to dynamically create objects.
 - :raw-html:`<font color="red">Red boxes,</font>` identify modules that require only configuration by your application. Static configuration is performed in an XDCtools configuration script (.cfg). Dynamic configuration is performed in C code.
 - :raw-html:`<font color="grey">Grey boxes,</font>` identify modules that are used internally but do not need to be configured or have their APIs called.