docs/user-guide: Fix indentation and spacing for numbered lists

docs/eval/user-guide/mem/adxl355-pmdz/index.rst

@@ -28,7 +28,7 @@
 selectable measurement ranges. The ADXL355 supports the ±2g, ±4g, and ±8g
 ranges, and offers industry leading noise, offset drift over temperature, and
 long term stability, enabling precision applications with minimal calibration
 and with very low power consumption. Applications include:
 
 -  Inertial measurement units (IMUs)/altitude and heading reference systems (AHRS)
 -  Platform stabilization systems
@@ -41,7 +41,7 @@
 The ADXL355 accelerometers offer guaranteed temperature stability with null
 offset coefficients of 0.15mg/°C (max). The stability minimizes resource and
 expense associated with calibration and testing effort, helping to achieve
 higher throughput for device OEMs. In addition, the hermetic package helps
 ensure that the end product conforms to its repeatability and stability
 specifications long after they leave the factory.
 
@@ -57,20 +57,20 @@
 Input and Output Connections and Configurations
 ===============================================
 
 The PMOD board is small in size with dimensions approximately 2.5 cm in width
 by 2.5 cm in length.
 
 Pmod  Processor Connector
 -------------------------
 
 The PMOD interface is a series of standardized digital interfaces for various
 digital communication protocols such as SPI, I2C, and UART. These interface
 types were standardized by Digilent, which is now a division of National
 Instruments. Complete details on the Pmod specification can be found on the
 `Digilent Pmod landing page <https://digilent.com/reference/pmod/start>`__.
 
 The specific interface used for the EVAL-ADXL355-PMDZ boards is the extended
 SPI. In general ADI has adopted the extended SPI connector for all PMOD devices
 which have an SPI interface. It provides flexibility to add interrupts, general
 purpose I/O, resets, and other digitally controlled functions.
 
@@ -96,37 +96,37 @@
 ADXL355 Interrupt Pins
 ----------------------
 
 The EVAL-ADXL355-PMDZ has two interrupt pins and a data ready pin which can be
 used as external indicators for the user. The interrupt pins can be programmed
 through software to reflect various status flags within the ADXL355, and those
 pins are accessible through the SPI PMOD header. For complete details on the
 individual status flags, what they mean, and how to program the chip to reflect
 those interrupts, please consult the :adi:`ADXL355` data sheet.
 
 Power Supply Considerations and Configuration
 ---------------------------------------------
 
 When using the ADXL355 PMOD board, the 3.3V power for the PMOD comes directly
 from the host board it is connected to. Most Pmod platform boards can supply at
 least 100 mA, more than adequate for the EVAL-ADXL355-PMDZ.
 
 Device Driver and Software Support
 ==================================
 
 There are two device driver and accompanying software solutions provided for
 the EVAL-ADXL355-PMDZ:
 
 **ADXL355 no-OS Driver**
 
    * The :git-no-OS:`ADXL355 no-OS driver <main:drivers/accel/adxl355>` is used
      in bare-metal applications, typically running on low-power, embedded
      microcontrollers.
 
    * The :git-no-OS:`ADXL355 no-OS example project <main:projects/eval-adxl355-pmdz>`
      uses the ADXL355 no-OS driver and has several configuration options:
 
       * The tinyiiod configuration emulates the Linux IIO framework through the
         tinyiiod daemon library. The application communicates with the host computer
         via the serial backend, over a USB-UART physical connection. This facilitates
         rapid application development on a host computer, independent from embedded
         code development. This is the configuration that will be referenced in the
@@ -271,19 +271,19 @@
 ------------
 
 1. Connect **MAX32655FTHR** with the **FTHR-PMOD-INTZ**. Note that MAXIM
-feather board should have stacking headers for feather board where the
-interposer board will be connected.
+   feather board should have stacking headers for feather board where the
+   interposer board will be connected.
 
 2. Connect **EVAL-ADXL355-PMDZ** to the **FTHR-PMOD-INTZ**.
 
 3. Power up the **MAX32655FTHR** by connecting it to your laptop using micro-USB
 
 4. Open the file explorer. Drag-and-drop the pre-built hex file to the DAPLINK.
-If the transfer was not completed, update the firmware for the DAPLINK. Follow
-the steps here: https://github.com/MaximIntegrated/max32625pico-firmware-images/
+   If the transfer was not completed, update the firmware for the DAPLINK. Follow
+   the steps here: https://github.com/MaximIntegrated/max32625pico-firmware-images/
 
 5. Open PuTTY or other similar software. Check the Device Manager to set
-correct COM for the MAX32655FTHR. Set baud rate according to hex file used:
+   correct COM for the MAX32655FTHR. Set baud rate according to hex file used:
 
 +------------------------------------------------------------------+-----------+
 | Hex file                                                         | Baud rate |

docs/eval/user-guide/transceiver/adrv9009/prerequisites.rst

@@ -20,7 +20,7 @@ start out with:
       or Linux).
    -  :ref:`See the supported carriers <adrv9009 carriers>`.
 
-#.  some way to interact with the platform,
+#. Some way to interact with the platform,
 
    #. for the ARM/FPGA SoC platforms, this normally includes: