diff --git a/front/plugins/omada_sdn_imp/config.json b/front/plugins/omada_sdn_imp/config.json
index 76b1a95e..531ba07f 100755
--- a/front/plugins/omada_sdn_imp/config.json
+++ b/front/plugins/omada_sdn_imp/config.json
@@ -125,7 +125,7 @@
       "description": [
         {
           "language_code": "en_us",
-          "string": "Enter full URL with protocol <code>https://CHANGEME_omada.mylocaldomain</code>."
+          "string": "Enter full URL with protocol <code>https://CHANGEME_omada.mylocaldomain:PORT</code>."
         }
       ]
     },
@@ -200,7 +200,7 @@
       "description": [
         {
           "language_code": "en_us",
-          "string": "Omada SDN site IDs. You can get it by..."
+          "string": "Omada SDN site IDs. For now, we only process the first site listed since NetAlertX's other probes won't traverse across NAT and routers. But if needed please submit an issue in github with your specific use case for consideration:  <code>https://github.com/jokob-sk/NetAlertX/issues </code> "
         }
       ]
     },
@@ -282,7 +282,7 @@
       "description": [
         {
           "language_code": "en_us",
-          "string": "The plugin synchronizes names from NetAlertX to OMADA. By default NetAlertX will only populate missing names in OMADASDN devices (i.e.: where the name is defaulting to the device MAC address); with this setting toggled, it will overwrite existing values regardless."
+          "string": "The plugin synchronizes names from NetAlertX to OMADA Clietnts. By default NetAlertX will only populate missing names in OMADASDN devices (i.e.: where the name is defaulting to the device MAC address); with this setting toggled, it will overwrite existing values regardless."
         }
       ]
     },