Fix formatting issues

docs/interfaces/spi-nor-flash.md

@@ -22,13 +22,13 @@ This setup assigns 512KB to U-Boot, 256KB each for U-Boot environment 1 and 2, a
 
 To verify the presence of the SPI-Nor Flash, you can list the MTD devices using the following command:
 
-```sh
+```
 cat /proc/mtd
 ```
 
 The expected output should resemble the following:
 
-```sh
+```
 mtd0: 00080000 00010000 "u-boot"
 mtd1: 00040000 00010000 "u-boot-env1"
 mtd2: 00040000 00010000 "u-boot-env2"
@@ -46,7 +46,7 @@ Here is an example of how to write a file to the `user` partition:
 1. Prepare the file you want to store in the Flash.
 2. Use `dd` to copy the file to the `user` partition:
 
-```sh
+```
 dd if=mydata.bin of=/dev/mtd3 bs=4096
 ```
 
@@ -56,7 +56,7 @@ This writes the contents of `mydata.bin` to the `user` partition (`mtd3`), using
 
 To read data from the `user` partition, you can use `dd` to copy the contents to a file:
 
-```sh
+```
 dd if=/dev/mtd3 of=readback.bin bs=4096
 ```
 
@@ -64,7 +64,7 @@ This command copies the content of the `user` partition to `readback.bin`. You c
 
 Alternatively, you can display the content directly in the terminal:
 
-```sh
+```
 cat /dev/mtd3
 ```
 

docs/interfaces/usb-otg.md

@@ -27,7 +27,7 @@ The USB controller on the Kumquat board is the **Allwinner V3s MUSB** controller
 
 The typical path for the MUSB controller's sysfs interface will look something like:
 
-```sh
+```
 /sys/class/udc/musb-hdrc.1.auto/
 ```
 
@@ -49,7 +49,7 @@ In this example, we will configure the Kumquat board to act as a USB-serial devi
 
    Load the **g_serial** module, which creates a USB serial device that can communicate with the host PC over the USB-OTG port.
 
-   ```sh
+   ```
    modprobe g_serial
    ```
 
@@ -57,7 +57,7 @@ In this example, we will configure the Kumquat board to act as a USB-serial devi
 
    After loading the module, the board will create a new serial device that the host PC can detect. You can check the created device by looking at `/dev`:
 
-   ```sh
+   ```
    ls /dev/ttyGS0
    ```
 
@@ -67,7 +67,7 @@ In this example, we will configure the Kumquat board to act as a USB-serial devi
 
    On the host PC, open a terminal and use a serial communication program such as `screen` or `minicom` to connect to the serial device. For example:
 
-   ```sh
+   ```
    screen /dev/ttyUSB0 115200
    ```
 
@@ -77,7 +77,7 @@ In this example, we will configure the Kumquat board to act as a USB-serial devi
 
    To stop the USB-serial device and return to the previous configuration, unload the `g_serial` module:
 
-   ```sh
+   ```
    rmmod g_serial
    ```
 
@@ -95,7 +95,7 @@ In this example, we will use the Kumquat board as a USB host to connect and acce
 
    Use the `lsusb` command to verify that the USB stick has been detected by the Kumquat board:
 
-   ```sh
+   ```
    lsusb
    ```
 
@@ -109,19 +109,19 @@ In this example, we will use the Kumquat board as a USB host to connect and acce
 
    First, create a mount point where the USB stick will be mounted:
 
-   ```sh
+   ```
    mkdir /mnt/usb
    ```
 
    Then, find the device name of the USB stick by using the `dmesg` or `lsblk` command:
 
-   ```sh
+   ```
    lsblk
    ```
 
    You should see a block device like `/dev/sda1`. Mount the USB stick to the mount point:
 
-   ```sh
+   ```
    mount /dev/sda1 /mnt/usb
    ```
 
@@ -129,7 +129,7 @@ In this example, we will use the Kumquat board as a USB host to connect and acce
 
    You can now access files on the USB stick from the `/mnt/usb` directory:
 
-   ```sh
+   ```
    ls /mnt/usb
    ```
 
@@ -137,7 +137,7 @@ In this example, we will use the Kumquat board as a USB host to connect and acce
 
    After finishing, unmount the USB stick to safely remove it:
 
-   ```sh
+   ```
    umount /mnt/usb
    ```
 

docs/interfaces/wifi-bt.md

@@ -16,13 +16,13 @@ The Kumquat board uses the standard `NetworkManager` service to manage WiFi conn
 
 First, check if the `espsta0` interface is up and running:
 
-```sh
+```
 nmcli device status
 ```
 
 This should show `espsta0` listed as a WiFi device. If it’s not listed, you may need to bring the interface up manually:
 
-```sh
+```
 ip link set espsta0 up
 ```
 
@@ -30,7 +30,7 @@ ip link set espsta0 up
 
 To scan for nearby WiFi networks:
 
-```sh
+```
 nmcli device wifi list
 ```
 
@@ -40,7 +40,7 @@ This command will output a list of available WiFi networks. Note the SSID of the
 
 To connect to a WiFi network, use the following command:
 
-```sh
+```
 nmcli device wifi connect "<SSID>" password "<password>"
 ```
 
@@ -48,7 +48,7 @@ Replace `<SSID>` with the name of your network and `<password>` with the network
 
 Once connected, you can verify the connection with:
 
-```sh
+```
 nmcli connection show
 ```
 
@@ -58,7 +58,7 @@ This will display the active network connections, including the one established
 
 After successfully connecting, test the internet connection by pinging a reliable external server:
 
-```sh
+```
 ping 8.8.8.8
 ```
 
@@ -72,7 +72,7 @@ The Kumquat board supports Bluetooth through the **hci0** interface, managed by
 
 Ensure the Bluetooth interface is up by running:
 
-```sh
+```
 hciconfig hci0 up
 ```
 
@@ -80,7 +80,7 @@ hciconfig hci0 up
 
 To scan for nearby Bluetooth devices, use the following command:
 
-```sh
+```
 hcitool scan
 ```
 
@@ -92,26 +92,26 @@ Once you have the device's MAC address, you can initiate pairing using `bluetoot
 
 1. Start the `bluetoothctl` tool:
 
-    ```sh
+    ```
     bluetoothctl
     ```
 
 2. Enter pairing mode:
 
-    ```sh
+    ```
     agent on
     default-agent
     ```
 
 3. Scan for devices again within `bluetoothctl`:
 
-    ```sh
+    ```
     scan on
     ```
 
 4. Pair with the device by specifying its MAC address:
 
-    ```sh
+    ```
     pair XX:XX:XX:XX:XX:XX
     ```
 
@@ -119,19 +119,19 @@ Once you have the device's MAC address, you can initiate pairing using `bluetoot
 
 5. To connect after pairing, use:
 
-    ```sh
+    ```
     connect XX:XX:XX:XX:XX:XX
     ```
 
 6. Trust the device for automatic connections in the future:
 
-    ```sh
+    ```
     trust XX:XX:XX:XX:XX:XX
     ```
 
 7. Finally, exit `bluetoothctl`:
 
-    ```sh
+    ```
     exit
     ```
 
@@ -139,7 +139,7 @@ Once you have the device's MAC address, you can initiate pairing using `bluetoot
 
 You can verify that the Bluetooth device is connected by running:
 
-```sh
+```
 hciconfig hci0
 ```