Fix casing: use lowercase 'dnsmasq' for consistency

Co-authored-by: tuanductran <69758022+tuanductran@users.noreply.github.com>

Author: Copilot

skills/nextdns-cli/SKILL.md

@@ -20,7 +20,7 @@ metadata:
 | [advanced-features](rules/advanced-features.md) | conditional forwarder, MAC address, subnet | Advanced routing and filtering |
 | [monitoring](rules/monitoring.md) | log, cache-stats, discovered clients | Monitor and debug DNS queries |
 | [platform-specific](rules/platform-specific.md) | router, OpenWrt, pfSense, Synology | Platform-specific configurations |
-| [ddwrt-installation](rules/ddwrt-installation.md) | DD-WRT, JFFS, NTP, router, time sync, DNSMasq | DD-WRT router installation and setup |
+| [ddwrt-installation](rules/ddwrt-installation.md) | DD-WRT, JFFS, NTP, router, time sync, dnsmasq | DD-WRT router installation and setup |
 | [troubleshooting](rules/troubleshooting.md) | diagnostic, connection test, DNS leak | Troubleshoot DNS issues |
 
 ## Efficiency Rules

skills/nextdns-cli/rules/ddwrt-installation.md

@@ -3,7 +3,7 @@ title: DD-WRT Installation
 impact: HIGH
 impactDescription: Without proper JFFS setup and installation procedures, NextDNS CLI will fail to persist on DD-WRT routers, causing DNS configuration loss after reboots and potential certificate errors due to time sync issues.
 type: capability
-tags: DD-WRT, JFFS, router, NTP, time sync, DNSMasq, SSH, router installation
+tags: DD-WRT, JFFS, router, NTP, time sync, dnsmasq, SSH, router installation
 ---
 
 # DD-WRT Installation
@@ -47,7 +47,7 @@ The installer will:
 - Detect DD-WRT as the platform
 - Install NextDNS CLI to `/jffs/nextdns/`
 - Configure the service to start automatically
-- Set up integration with DNSMasq
+- Set up integration with dnsmasq
 
 ### Upgrading
 
@@ -69,28 +69,28 @@ DD-WRT may experience x509 certificate errors during boot due to incorrect syste
 
 This ensures that NTP queries for `2.pool.ntp.org` are forwarded to your upstream DNS, preventing certificate validation failures during the boot sequence when the system clock hasn't synchronized yet.
 
-## DNSMasq Persistence
+## dnsmasq Persistence
 
-NextDNS CLI modifies the default DNSMasq configuration. To protect custom DNSMasq settings and ensure they persist across NextDNS updates:
+NextDNS CLI modifies the default dnsmasq configuration. To protect custom dnsmasq settings and ensure they persist across NextDNS updates:
 
-1. Create a persistent DNSMasq configuration file:
+1. Create a persistent dnsmasq configuration file:
 
     ```bash
     mkdir -p /jffs/etc
     touch /jffs/etc/dnsmasq.conf
     ```
 
-2. Add your custom DNSMasq settings to `/jffs/etc/dnsmasq.conf`:
+2. Add your custom dnsmasq settings to `/jffs/etc/dnsmasq.conf`:
 
     ```conf
     # Example custom settings
     dhcp-option=option:router,192.168.1.1
     dhcp-option=option:dns-server,127.0.0.1
     ```
 
-3. This file will be preserved when NextDNS CLI updates or modifies the main DNSMasq configuration
+3. This file will be preserved when NextDNS CLI updates or modifies the main dnsmasq configuration
 
-**Why this matters**: NextDNS CLI edits the default DNSMasq configuration during installation and updates. Using a separate persistent file ensures your custom settings are not overwritten.
+**Why this matters**: NextDNS CLI edits the default dnsmasq configuration during installation and updates. Using a separate persistent file ensures your custom settings are not overwritten.
 
 ## Troubleshooting
 
@@ -105,7 +105,7 @@ Common issues and solutions:
 - **JFFS not mounted**: Verify JFFS is enabled in Administration > Management and reboot the router
 - **Installation fails**: Ensure you have sufficient JFFS storage space using `df -h /jffs`
 - **Certificate errors**: Apply the NTP forwarder workaround described above
-- **DNSMasq conflicts**: Check `/tmp/dnsmasq.conf` for conflicts with existing rules
+- **dnsmasq conflicts**: Check `/tmp/dnsmasq.conf` for conflicts with existing rules
 
 ## Reference