Fix list styling.

docs/how-to/unified_memory.rst

@@ -87,19 +87,16 @@ depends on your architecture. For further details, visit :ref:`unified memory
 system requirements` and :ref:`checking unified memory management support`.
 
 - **HIP Managed Memory Allocation API**:
-The ``hipMallocManaged()`` is a dynamic memory allocator that is available on
-all GPUs with unified memory support. For more details, visit :doc:`reference
-page <reference/unified_memory_reference>`.
+
+  The ``hipMallocManaged()`` is a dynamic memory allocator that is available on all GPUs with unified memory support. For more details, visit :doc:`reference page <reference/unified_memory_reference>`.
 
 - **HIP Managed Variables**:
-The ``__managed__`` declaration specifier, which serves as its counterpart, is
-supported on all modern AMD cards and can be utilized for static allocation.
+
+  The ``__managed__`` declaration specifier, which serves as its counterpart, is supported on all modern AMD cards and can be utilized for static allocation.
 
 - **System Allocation API**:
-Starting with the MI300 series, the ``malloc()`` system allocator allows you
-to reserve unified memory. The system allocator is more versatile, and it
-offers an easy transition from a CPU written C++ code to a HIP code as the same
-system allocation API is used.
+
+  Starting with the MI300 series, the ``malloc()`` system allocator allows you to reserve unified memory. The system allocator is more versatile, and it offers an easy transition from a CPU written C++ code to a HIP code as the same system allocation API is used.
 
 .. _checking unified memory management support:
 
@@ -330,18 +327,16 @@ and a GPU, which would require large memory transfers. Here are some areas
 where UMM can be beneficial:
 
 - **Simplification of Memory Management**:
-UMM can help to simplify the complexities of memory management. This can make
-it easier for developers to write code without worrying about memory allocation
-and deallocation details.
 
-- **Data Migration**:
-UMM allows for efficient data migration between the host (CPU) and the device
-(GPU). This can be particularly useful for applications that need to move data
-back and forth between the device and host.
+  UMM can help to simplify the complexities of memory management. This can make it easier for developers to write code without worrying about memory allocation and deallocation details.
+
+- **Data Migration**: 
+
+  UMM allows for efficient data migration between the host (CPU) and the device (GPU). This can be particularly useful for applications that need to move data back and forth between the device and host.
 
 - **Improved Programming Productivity**:
-As a positive side effect, the use of UMM can reduce the lines of code,
-thereby improving programming productivity.
+
+  As a positive side effect, the use of UMM can reduce the lines of code, thereby improving programming productivity.
 
 In HIP, pinned memory allocations are coherent by default. Pinned memory is
 host memory mapped into the address space of all GPUs, meaning that the pointer