docs: fix markdown lint issues

Author: rokath

README.md

@@ -57,26 +57,32 @@ Instead of storing log strings on your embedded device, Trice keeps them on your
 ## When to Use Trice
 
 ### Logging and Debugging
+
 You can use Trice for `printf` debugging and as a logging system. The advantage is very short messages (no strings) for data transfer. Remember that the file [til.json](./demoTIL.json) is needed to read all output from devices in the field for 10+ years.
 
 - **Optional:** Add [til.json](./demoTIL.json) as a compressed resource to your target image. You can use [SRecord](http://srecord.sourceforge.net/download.html) or provide a download link.
 
 ### Data Compression
+
 Trice looks like data compression (IDs instead of strings), which is useful for [IoT](https://en.wikipedia.org/wiki/Internet_of_things) devices, especially [NB-IoT](https://en.wikipedia.org/wiki/Narrowband_IoT) with very low data rates.
 
 ### FLASH Memory Storage
+
 [Store Trice messages in FLASH memory](./docs/TriceUserManual.md#writing-the-trice-logs-into-an-sd-card-(or-a-user-specific-output)) for later analysis. A typical `trice` uses only 4 bytes, no matter how long the format string is.
 
 ### Encryption
+
 You can **encrypt** Trice transfer packets for security.
 
 - Deliver firmware images with encrypted Trice output that only works with the right key and [til.json](./demoTIL.json)
 - [XTEA](https://en.m.wikipedia.org/wiki/XTEA) encryption is available
 
 ### Translation
+
 Translate the [til.json](./demoTIL.json) file into **different languages**. Change the language by changing the [til.json](./demoTIL.json) file without changing the target binary.
 
 ### Timing Analysis
+
 Trice makes **timing analysis** easy on distributed embedded systems. It supports both host and target timestamps.
 
 ## How Trice Works (UART Example)

docs/TriceUserManual_AI_reworked_NOT_reviewed.md

@@ -454,7 +454,7 @@ This is the fastest path if you have a Segger J-Link and can use RTT:
 
 4. **Insert IDs and build**
    * Run `trice insert` (or `trice i ...`), then build your firmware.  
-     See: [Insert IDs](#insert-ids).
+     <!-- See: [Insert IDs](#insert-ids). -->
 
 5. **View logs via RTT**
    * Start the Trice host tool and connect via RTT.  
@@ -475,7 +475,7 @@ Use this if you have a serial port connected to your target (or a USB CDC ACM po
 
 4. **View logs via UART**
    * Start `trice log` and connect to the COM/tty port.  
-     See: [Trice tool in logging action](#trice-tool-in-logging-action) and [Trice tool CLI usage examples](#trice-tool-cli-usage-examples).
+     See: [Trice tool in logging action](#trice-tool-in-logging-action). <!-- and [Trice tool CLI usage examples](#trice-tool-cli-usage-examples). -->
 
 ###  1.3. <a id='where-to-go-next'></a>Where to go next