docs: update format issues left in EN docs

docs/en/api-reference/system/app_image_format.rst

@@ -90,8 +90,8 @@ Application Description
 The ``DROM`` segment of the application binary starts with the :cpp:type:`esp_app_desc_t` structure which carries specific fields describing the application:
 
  * ``magic_word`` - the magic word for the esp_app_desc structure.
- * ``secure_version`` - see :doc:`Anti-rollback</api-reference/system/ota>`.
- * ``version`` - see :doc:`App version</api-reference/system/misc_system_api>`. ``*``
+ * ``secure_version`` - see :doc:`Anti-rollback </api-reference/system/ota>`.
+ * ``version`` - see :doc:`App version </api-reference/system/misc_system_api>`. ``*``
  * ``project_name`` is filled from ``PROJECT_NAME``. ``*``
  * ``time`` and ``date`` - compile time and date.
  * ``idf_ver`` - version of ESP-IDF. ``*``

docs/en/api-reference/system/mem_alloc.rst

@@ -51,12 +51,12 @@ To find the amount of statically allocated memory, use the :ref:`idf.py size <id
 
 .. only:: esp32
 
-    .. note:: 
-        
+    .. note::
+
         See the :ref:`dram` section for more details about the DRAM usage limitations.
 
-.. note:: 
-    
+.. note::
+
     At runtime, the available heap DRAM may be less than calculated at compile time, because, at startup, some memory is allocated from the heap before the FreeRTOS scheduler is started (including memory for the stacks of initial FreeRTOS tasks).
 
 IRAM
@@ -126,7 +126,7 @@ Memory allocated with ``MALLOC_CAP_32BIT`` can **only** be accessed via 32-bit r
 
     .. only:: esp32
 
-        To use the region above the 4 MiB limit, you can use the :doc:`himem API</api-reference/system/himem>`.
+        To use the region above the 4 MiB limit, you can use the :doc:`himem API </api-reference/system/himem>`.
 
 Thread Safety
 -------------

docs/en/api-reference/system/ota.rst

@@ -201,7 +201,7 @@ The verification of signed OTA updates can be performed even without enabling ha
 OTA Tool ``otatool.py``
 -----------------------
 
-The component ``app_update`` provides a tool :component_file:`otatool.py<app_update/otatool.py>` for performing OTA partition-related operations on a target device. The following operations can be performed using the tool:
+The component ``app_update`` provides a tool :component_file:`otatool.py <app_update/otatool.py>` for performing OTA partition-related operations on a target device. The following operations can be performed using the tool:
 
   - read contents of otadata partition (read_otadata)
   - erase otadata partition, effectively resetting device to factory app (erase_otadata)

docs/en/api-reference/system/random.rst

@@ -37,7 +37,7 @@ To re-enable the entropy source temporarily during app startup, or for an applic
     Secondary Entropy
     -----------------
 
-    {IDF_TARGET_NAME} RNG contains a secondary entropy source, based on sampling an asynchronous 8MHz internal oscillator (see the Technical Reference Manual for details). This entropy source is always enabled in ESP-IDF and continuously mixed into the RNG state by hardware. In testing, this secondary entropy source was sufficient to pass the `Dieharder`_ random number test suite without the main entropy source enabled (test input was created by concatenating short samples from a continuously resetting {IDF_TARGET_NAME}). However, it is currently only guaranteed that true random numbers are produced when the main entropy source is also enabled as described above.
+    {IDF_TARGET_NAME} RNG contains a secondary entropy source, based on sampling an asynchronous 8 MHz internal oscillator (see the Technical Reference Manual for details). This entropy source is always enabled in ESP-IDF and continuously mixed into the RNG state by hardware. In testing, this secondary entropy source was sufficient to pass the `Dieharder`_ random number test suite without the main entropy source enabled (test input was created by concatenating short samples from a continuously resetting {IDF_TARGET_NAME}). However, it is currently only guaranteed that true random numbers are produced when the main entropy source is also enabled as described above.
 
 API Reference
 -------------
@@ -45,8 +45,8 @@ API Reference
 .. include-build-file:: inc/esp_random.inc
 .. include-build-file:: inc/bootloader_random.inc
 
-Getrandom
----------
+``getrandom()``
+---------------
 
 A compatible version of the Linux ``getrandom()`` function is also provided for ease of porting:
 
@@ -62,8 +62,8 @@ The ``flags`` argument is ignored, this function is always non-blocking but the
 
 Return value is -1 (with ``errno`` set to ``EFAULT``) if the ``buf`` argument is NULL, and equal to ``buflen`` otherwise.
 
-getentropy
-----------
+``getentropy()``
+----------------
 
 A compatible version of the Linux ``getentropy()`` function is also provided for ease of porting:
 

docs/en/api-reference/system/wdts.rst

@@ -131,7 +131,7 @@ The following config options control TWDT configuration. They are all enabled by
   Configuration
   """""""""""""
 
-  - When the external 32KHz crystal or oscillator is selected (:ref:`CONFIG_RTC_CLK_SRC`) the XTWDT can be enabled via the :ref:`CONFIG_ESP_XT_WDT` configuration option.
+  - When the external 32 KHz crystal or oscillator is selected (:ref:`CONFIG_RTC_CLK_SRC`) the XTWDT can be enabled via the :ref:`CONFIG_ESP_XT_WDT` configuration option.
   - The timeout is configured by setting the :ref:`CONFIG_ESP_XT_WDT_TIMEOUT` option.
   - The automatic backup clock functionality is enabled via the ref:`CONFIG_ESP_XT_WDT_BACKUP_CLK_ENABLE` configuration option.