Merge pull request #61 from quaxalber/development

Fix debug output

README.md

@@ -356,11 +356,16 @@ Here's a few things you could try:
   ```
 
 - When you interact with your Bluetooth devices with `-d` set, you should see debug output in the logs such as:
-
+- 
   ```console
   user@pi0w:~ $ sudo service bluetooth_2_usb stop && sudo bluetooth_2_usb -i /dev/input/event3,a1:b2:c3:d4:e5:f6,Logi -d ; sudo service bluetooth_2_usb start
-<details><summary>[show debug output]</summary>
-<p>
+  # Click [show debug output] for more
+  ```
+
+  <details><summary>[show debug output]</summary>
+  <p> 
+
+  ```console
   23-12-04 14:05:57 [DEBUG] CLI args: Namespace(device_ids=['/dev/input/event3', 'a1:b2:c3:d4:e5:f6', 'Logi'], auto_discover=False, debug=True, log_to_file=False, log_path='/var/log/bluetooth_2_usb/bluetooth_2_usb.log', version=False, list_devices=False)
   23-12-04 14:05:57 [DEBUG] Logging to stdout
   23-12-04 14:05:57 [INFO] Launching Bluetooth 2 USB v0.6.2
@@ -410,10 +415,11 @@ Here's a few things you could try:
   ^C23-12-04 14:07:57 [INFO] Exiting gracefully. Received signal: 2, frame: <frame at 0xb5f80df8, file '/usr/lib/python3.11/selectors.py', line 468, code select>
   23-12-04 14:07:57 [CRITICAL] AceRK Keyboard cancelled
   23-12-04 14:07:57 [CRITICAL] AceRK Mouse cancelled
-</p>
-</details> 
   ```
 
+  </p>
+  </details> 
+
 - Still not resolved? Double-check the [installation instructions](#4-installation)
 
 - For more help, open an [issue](https://github.com/quaxalber/bluetooth_2_usb/issues) in the [GitHub repository](https://github.com/quaxalber/bluetooth_2_usb)