Set indent to 4 for sub items

Author: soumeh01

.github/markdownlint.jsonc

@@ -4,5 +4,8 @@
     "line_length": 120
   },
   "MD034": false,
-  "MD041": false
+  "MD041": false,
+  "MD007": {
+    "indent": 4
+  }
 }

CHANGELOG.md

@@ -8,71 +8,71 @@ loses modifications from other extensions.
 `launch.json` leaves behind the breakpoint.
 - Partially implements [#96](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/96): Enable Peripheral
 Inspector.
-  - Extracts first SVD file path found in `*.cbuild-run.yml` debug configuration file to automatically set up
+    - Extracts first SVD file path found in `*.cbuild-run.yml` debug configuration file to automatically set up
   Peripheral Inspector.
 - Adds initial version of extension [documentation](https://open-cmsis-pack.github.io/vscode-cmsis-debugger/).
 - Updates included pyOCD distribution
-  - Fixes [#133](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/133): Adds default memory map for
-  Cortex-M devices.
-  - Improves memory map creation and flash algorithms sorting.
-  - Selects current processor core (for example used for flash programming) based on active gdb server connection.
+    - Fixes [#133](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/133): Adds default memory map for
+    Cortex-M devices.
+    - Improves memory map creation and flash algorithms sorting.
+    - Selects current processor core (for example used for flash programming) based on active gdb server connection.
 
 ## 0.1.0
 
 - Updates included pyOCD distribution
-  - Fixes [#92](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/92): `monitor reset halt` command
-  fails for LPCXpresso55S69 if using CMSIS-Pack support in pyOCD.
-  - Fixes [#93](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/93): Download to LPC55S69 flash with
-  GDB and pyOCD ends in errors.
-  - Fixes [#94](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/94): Cannot connect to
-  NXP FRDM-K32L3A6 with pyOCD.
-  - Fixes support for `<memory>` elements from CMSIS PDSC files.
-  - Fixes progress bar output during program download.
-  - Fixes handling of `__ap` variable in debug sequences.
-  - Improves connection robustness and DP sticky error bits handling for temporary target communication losses and
-   `__errorcontrol` usage (CMSIS debug descriptions). For example in reset scenarios.
-  - Updates CMSIS-DAP probe detection (filters out Cypress KitProg3 bridge).
-  - Extends and improves support for `*.cbuild-run.yml` debug configuration files.
+    - Fixes [#92](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/92): `monitor reset halt` command
+    fails for LPCXpresso55S69 if using CMSIS-Pack support in pyOCD.
+    - Fixes [#93](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/93): Download to LPC55S69 flash with
+    GDB and pyOCD ends in errors.
+    - Fixes [#94](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/94): Cannot connect to
+    NXP FRDM-K32L3A6 with pyOCD.
+    - Fixes support for `<memory>` elements from CMSIS PDSC files.
+    - Fixes progress bar output during program download.
+    - Fixes handling of `__ap` variable in debug sequences.
+    - Improves connection robustness and DP sticky error bits handling for temporary target communication losses and
+    `__errorcontrol` usage (CMSIS debug descriptions). For example in reset scenarios.
+    - Updates CMSIS-DAP probe detection (filters out Cypress KitProg3 bridge).
+    - Extends and improves support for `*.cbuild-run.yml` debug configuration files.
 
 ## 0.0.3
 
 - Fixes [#84](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/84): Cannot use cbuild-run files with
 pyOCD without CMSIS_PACK_ROOT environment variable.
 - Implements [#83](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/83): Make built-in pyOCD available
 in VS Code terminals.
-  - Note that there is a known issue with a pyOCD installation in Python virtual environments taking precedence over
-  the built-in pyOCD variant.
+    - Note that there is a known issue with a pyOCD installation in Python virtual environments taking precedence over
+    the built-in pyOCD variant.
 - Updates included pyOCD distribution
-  - Fixes [#91](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/91): "Zephyr kernel detected" warning
-  in shipped pyOCD.
-  - Fixes [#100](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/100): [macOS] - Cannot connect with
-  pyOCD and ULINKplus. Fixes missing `libusb` for macOS.
-  - Fixes [#126](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/126): Flash programming fails on
-  devices where the flash memory's erased value is 0x00. Initializes XPSR register before executing flash algorithm
-  function.
-  - Fixes [#127](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/127): CoreSight root component
-  discovery fails. Fixes how to address APv2.
-  - Fixes [#128](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/128): Programming fails on LPC55S69
-   when device is erased. Debugger no longer reads back programmed flash memory if `Verify` function is
-   provided by flash algorithm.
-  - Fixes [#131](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/131):
-   AP access failure due to invalid security flags (SPROT).
-  - Extends support for `*.cbuild-run.yml` debug configuration files.
+    - Fixes [#91](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/91): "Zephyr kernel detected" warning
+    in shipped pyOCD.
+    - Fixes [#100](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/100): [macOS] - Cannot connect with
+    pyOCD and ULINKplus. Fixes missing `libusb` for macOS.
+    - Fixes [#126](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/126): Flash programming fails on
+    devices where the flash memory's erased value is 0x00. Initializes XPSR register before executing flash algorithm
+    function.
+    - Fixes [#127](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/127): CoreSight root component
+    discovery fails. Fixes how to address APv2.
+    - Fixes [#128](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/128): Programming fails on LPC55S69
+    when device is erased. Debugger no longer reads back programmed flash memory if `Verify` function is
+    provided by flash algorithm.
+    - Fixes [#131](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/131):
+    AP access failure due to invalid security flags (SPROT).
+    - Extends support for `*.cbuild-run.yml` debug configuration files.
 
 ## 0.0.2
 
 - Removes [Arm Tools Environment Manager](https://marketplace.visualstudio.com/items?itemName=Arm.environment-manager)
- from extension pack. Instead, README lists it as one of the recommended extensions to use with the Arm CMSIS Debugger.
+from extension pack. Instead, README lists it as one of the recommended extensions to use with the Arm CMSIS Debugger.
 - Fixes use of `${workspace}` to `${workspaceFolder}` in default debug configurations.
 - Reduces and aligns default `initCommands` lists for pseudo debugger types `cmsis-debug-pyocd`
- and `cmsis-debug-jlink`.
+and `cmsis-debug-jlink`.
 - Implements [#69](https://github.com/Open-CMSIS-Pack/vscode-cmsis-debugger/issues/69): Bring Debug Console to
- front during connection.
+front during connection.
 
 ## 0.0.1
 
 - Initial release of extension pack on GitHub.
 - Adds pseudo debugger types `cmsis-debug-pyocd` and `cmsis-debug-jlink`.
 - Adds debug configuration providers for debugger type `gdbtarget` to resolve settings for pyOCD and Segger J-Link
- GDB server connections.
+GDB server connections.
 - Contributes setting `cmsis`.`cbuildRunFile` to all debugger types (`*` debugger type).

DEVELOPMENT.md

@@ -4,7 +4,7 @@
 
 - Install **Visual Studio Code®**.
 - Install **Node.js®** on your machine and ensure it is on your path.
-  - The currently recommended version is 20.x (LTS).
+    - The currently recommended version is 20.x (LTS).
 - Install **Yarn** which is used to build and execute scripts in this repository:
 
   ```sh

README.md

@@ -106,10 +106,10 @@ the following gaps during debug launch:
 - If option `target`>`server` is set to `pyocd`, then it expands to the absolute path of
  the built-in pyOCD distribution.
 - Extends the `target`>`serverParameters` list of `pyocd` command line arguments:
-  - Prepends `gdbserver` if not present.
-  - Appends `--port <gdbserver_port>` if the `target`>`port` setting is set, where `<gdbserver_port>` gets
-  that port setting's value.
-  - Appends `--cbuild-run` and the corresponding `cbuildRunFile` path if `cmsis`>`cbuildRunFile` is set.
+    - Prepends `gdbserver` if not present.
+    - Appends `--port <gdbserver_port>` if the `target`>`port` setting is set, where `<gdbserver_port>` gets
+	that port setting's value.
+    - Appends `--cbuild-run` and the corresponding `cbuildRunFile` path if `cmsis`>`cbuildRunFile` is set.
 
 **Note**: The built-in version of pyOCD supports the command line option `--cbuild-run` which isn't available
 in releases outside this extension.
@@ -131,8 +131,7 @@ Additionally, the extension contributes a debug configuration resolver which aut
 gaps during debug launch:
 
 - Extends the `target`>`serverParameters` list of `JLinkGDBServer`/`JLinkGDBServerCL` command line arguments:
-  - Appends `--port <gdbserver_port>` if the `target`>`port` setting is set, where `<gdbserver_port>` gets that port
-  setting's value.
+    - Appends `--port <gdbserver_port>` if the `target`>`port` setting is set, where `<gdbserver_port>` gets that port setting's value.
 
 ## Known Limitations and Workarounds
 

docs/debug_views.md

@@ -133,9 +133,9 @@ To add a conditional breakpoint:
 
 - Create a conditional breakpoint
 
-  - Right-click in the editor margin and select Add Conditional Breakpoint.
+    - Right-click in the editor margin and select Add Conditional Breakpoint.
 
-  - Use the Add Conditional Breakpoint command in the Command Palette (⇧⌘P).
+    - Use the Add Conditional Breakpoint command in the Command Palette (⇧⌘P).
 
 - Choose the type of condition you want to set (expression, hit count, or wait for breakpoint).
 
@@ -145,10 +145,10 @@ To add a condition to an existing breakpoint:
 
 - Edit an existing breakpoint
 
-  - Right-click on the breakpoint in the editor margin and select Edit Breakpoint.
+    - Right-click on the breakpoint in the editor margin and select Edit Breakpoint.
 
-  - Select the pencil icon next for an existing breakpoint in the **BREAKPOINTS section** of
-  the **Run and Debug view**.
+    - Select the pencil icon next for an existing breakpoint in the **BREAKPOINTS section** of
+    the **Run and Debug view**.
 
 - Edit the condition (expression, hit count, or wait for breakpoint).