diff --git a/Configuration-Procedure-for-New-Devices.md b/Configuration-Procedure-for-New-Devices.md
index ce35255f..bfd2a059 100644
--- a/Configuration-Procedure-for-New-Devices.md
+++ b/Configuration-Procedure-for-New-Devices.md
@@ -10,9 +10,7 @@ If your device is similar to the existing built-in module (e.g., a particular MC
 
       - If you are unable to control some of the relays or LEDs on the device, they may be attached to the "dedicated" GPIO. Assign those GPIO to an unused `Relay<x>` and repeat step _1a_.
 
-   _b._ Once you have found which GPIO control which relays and LEDs, set these "active" GPIO to associate them with the corresponding `Relay<x>` or `LED<x>`. Proper operation may dictate the use regular or inverted (`Relay<x>i`/`LED<x>i`) settings.
-
-   _c._ Currently, Tasmota only supports up two GPIO configured as LEDs to indicate relay state and connectivity status. If only one LED is configured it will act as both the Wi-Fi/MQTT status LED (see [`SetOption31`](Commands#SetOption31)) and/or the LED that indicates relay power (see [`LedState`](Commands#LedState)/[`LedMask`](Commands#LedMask)). If two LEDs are defined, LED1 will act as the Wi-Fi/MQTT status LED and LED2 will act as the LED that indicates relay power.
+   _b._ Once you have found which GPIO control which relays and LEDs, set these "active" GPIO to associate them with the corresponding `Relay<x>`, `LED<x>`, or `LEDLink`. Proper operation may dictate the use regular or inverted (`Relay<x>i`/`LED<x>i`/`LEDLinki`) settings.
 
 2. Now, assign every remaining GPIO (excluding, once again, remaining "dedicated" like Tx/Rx & GPIO0/GPIO2, etc.) to `Switch`es.