General code and comment cleanup

README.md

@@ -21,8 +21,8 @@ Each relay channel consists of 2 output relays controlled by 2 GPIO pins. The co
 
 The run limit feature provides an additional layer of protection by automatically stopping channels after a configurable time period. This is particularly useful for motor-driven applications where continuous operation beyond a certain duration could cause damage or safety issues. Each channel can have its own run limit setting, and when enabled, the component will automatically stop the channel once it has been running for the specified duration.
 
-It also provides an optional tilting interface per channel base. Tilting makes a channel move with a specific pattern moving with small steps at a time. Tilting is specifically designed for controlling some types of curtains that need to be adjusted to let enter specific amount of day light.  
-Since it operates on relays, the switching frequency is limited to 10Hz which complies with the most of the general purpose relays' requirements. The minimum frequency is 2Hz and the duty cycle is about 10% in all ranges.  
+It also provides an optional tilting interface per channel base. Tilting makes a channel move with a specific pattern moving with small steps at a time. Tilting is specifically designed for controlling some types of curtains that need to be adjusted to let enter specific amount of day light.
+Since it operates on relays, the switching frequency is limited to 10Hz which complies with the most of the general purpose relays' requirements. The minimum frequency is 2Hz and the duty cycle is about 10% in all ranges.
 
 Another optional feature is NVS storage, which saves the configuration permanently across reboots of the device. These configurations are:
 
@@ -31,7 +31,7 @@ Another optional feature is NVS storage, which saves the configuration permanent
 - Tilt sensitivity
 - Last tilt position
 
-### NVS Operation Details 
+### NVS Operation Details
 When NVS storage is enabled (CONFIG_RELAY_CHN_ENABLE_NVS=y), the component creates a dedicated background task to manage all NVS write operations. This design has important implications for how you use the NVS-related functions:
 - **Asynchronous Writes:** All `set` operations (e.g., `relay_chn_flip_direction()`, `relay_chn_set_run_limit()`) are asynchronous. They add the write request to a queue and return immediately, preventing the calling task from being blocked.
 - **Synchronous Reads:** All get operations (e.g., `relay_chn_get_direction()`) are synchronous. They read the value directly from the NVS storage and will block the calling task until the read is complete.
@@ -145,7 +145,7 @@ Depending on the mode, the component will be built selectively, so the signature
 ```c
 relay_chn_run_forward(); // No channel ID parameter for single channel mode
 // or
-relay_chn_run_forward(2); // Channel ID parameters will be needed in multi channel mode 
+relay_chn_run_forward(2); // Channel ID parameters will be needed in multi channel mode
 ```
 
 See the examples for further reference
@@ -197,9 +197,9 @@ relay_chn_run_reverse(1);
 // Run all channels reverse
 relay_chn_run_reverse_all();
 
-// Stop channel #1 
+// Stop channel #1
 relay_chn_stop(1);
-// Stop all channels 
+// Stop all channels
 relay_chn_stop_all();
 
 // Flip direction of channel #0