Apply suggestions from code review

Co-authored-by: Cem Aksoylar <[email protected]>

docs/docs/troubleshooting/hardware-issues.mdx

@@ -148,24 +148,24 @@ Once you have done so, you will need to adjust the `kscan` of your keyboard slig
 
 ```dts
 &kscan0 {
-        input-gpios
-        = <&pro_micro  7 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
-        , <&pro_micro  6 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
-        , <&pro_micro  9 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+    input-gpios
+        = <&pro_micro 7 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+        , <&pro_micro 6 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+        , <&pro_micro 9 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
         ;
-    };
+};
 ```
 
-could have the pin `pro_micro 6` replaced with `gpio0 8`.
+could have the pin `&pro_micro 6` (D6 in the [Pro Micro pinout](../development/hardware-integration/new-shield.mdx#shield-overlays)) replaced with `&gpio0 8` (P0.08 for nRF MCUs).
 
 ```dts title="<my_keyboard>.overlay"
 &kscan0 {
-        input-gpios
-        = <&pro_micro  7 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
-        , <&gpio0  8 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
-        , <&pro_micro  9 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+    input-gpios
+        = <&pro_micro 7 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+        , <&gpio0 8 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
+        , <&pro_micro 9 (GPIO_ACTIVE_LOW | GPIO_PULL_UP)>
         ;
-    };
+};
 ```
 
 You can then build and flash using your config as usual.
@@ -178,22 +178,22 @@ If the affected pin is not in your `kscan`, you will want to copy over and overw
 
 Under ideal conditions, a Bluetooth connection can be stable at even a 100 meter distance. However, there are many things which can affect the effective range of the antenna. In no particular order, the most common issues you will encounter are:
 
-- Solid material near an antenna or between the two communicating antennas (Metal is _particularly_ bad)
+- Solid material near an antenna or between the two communicating antennas (metal is _particularly_ bad)
 - Interference from other nearby 2.4GHz connections
 - The antenna makes use of malfunctioning hardware such as a [faulty oscillator](connection-issues.mdx#mitigating-a-faulty-oscillator)
 - Not enough [power being provided to the antenna](connection-issues.mdx#unreliableweak-connection)
-- A missing external antenna
+- A missing external antenna for motherboard-integrated or PCIe wireless adapters
 - Interference from [USB 3 devices](https://www.bluetoothandusb3.com/the-explanation)
 
-It is expected that your antenna will have some interference - hence why most household devices using Bluetooth have an effective range of 5-10 meters.
+It is expected that your antenna will have some interference -- hence why most household devices using Bluetooth have an effective range of 5-10 meters.
 
 ### Identifying & Resolving Issues
 
 Troubleshooting antenna issues can only really be done via trial and error.
 
 A good initial approach is:
 
-1. Make sure you have firmware flashed to your device that has BLE enabled, with at least one Bluetooth profile free.
+1. Make sure you have firmware flashed to your device that has BLE enabled, with at least one [Bluetooth profile](../features/bluetooth.md#profiles) free and no uncleared profiles previously paired to the host device.
 2. Select the free profile.
 3. Remove as many physical objects between your ZMK device and a host device as possible.
 4. Switch off as many other nearby wireless devices as possible.