1 files changed, 51 insertions, 17 deletions

diff --git a/doc/book-enea-edge-getting-started/doc/net_config_options.xml b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
index ff513c9..a9faf0a 100644
--- a/doc/book-enea-edge-getting-started/doc/net_config_options.xml
+++ b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="UTF-8"?>
+<?xml version="1.0" encoding="ISO-8859-1"?>
 <chapter id="net_config_operations">
   <title>Network Configuration Options</title>
 
@@ -218,9 +218,9 @@
 
           <listitem>
             <para>In order to edit an already configured interface, (as in the
-            example popup shown below, a WAN interface) double click on the
-            desired one and a popup will appear. A different popup appears for
-            each type of interface. From the <emphasis role="bold">Host
+            example pop-up shown below, a WAN interface) double click on the
+            desired one and a pop-up will appear. A different pop-up appears
+            for each type of interface. From the <emphasis role="bold">Host
             Interface</emphasis> window, a user can change the networking type
             and the IP address assignment:</para>
 
@@ -240,9 +240,10 @@
         <note>
           <para>When changing the <literal>address-assignment</literal> from
           static to DHCP, if any of the <literal>ip-address</literal>,
-          <literal>netmask</literal> or <literal>gateway</literal> fields have
-          invalid values a validation error will be triggered. These fields
-          must be empty or have the valid values for their respective address
+          <literal>netmask</literal>, <literal>gateway</literal> or
+          <literal>dns-servers</literal> fields have invalid values a
+          validation error will be triggered. These fields must be empty or
+          have the valid values for their respective address
           assignment.</para>
         </note>
       </section>
@@ -270,7 +271,7 @@
 
           <listitem>
             <para>In order to edit an already configured interface, (as in the
-            example popup shown below, a WAP interface) double click on the
+            example pop-up shown below, a WAP interface) double click on the
             desired one and a pop-up will appear. A different pop-up appears
             for each type of interface. From the <literal>Host
             Interface</literal> window, the following parameters are
@@ -385,7 +386,7 @@
       </note>
 
       <para>There are three types of bridges which can be created, each one
-      fulfiling a different role.</para>
+      fulfilling a different role.</para>
 
       <section id="inband_mg_bridge">
         <title>uCPE In-band Management bridge</title>
@@ -580,9 +581,9 @@
 
         <listitem>
           <para>DeviceVersion: <xi:include
-          href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+          href="../../eltf_params_updated.xml"
           xmlns:xi="http://www.w3.org/2001/XInclude"
-          xpointer="element(EneaLinux_REL_VER/1)" /></para>
+          xpointer="element(EneaEdge_REL_VER/1)" /></para>
         </listitem>
 
         <listitem>
@@ -651,10 +652,15 @@
     <title>Custom Scripts for Custom Networking Configurations</title>
 
     <para>The custom scripts feature allows users to execute user-defined
-    scripts on the uCPE device at various times.This allows for more flexible
+    scripts on the uCPE device at various times. This allows for more flexible
     and advanced configurations such as a LTE modem configuration, advanced
     network configurations or OVS flow rule programming at any time.</para>
 
+    <note>
+      <para>In the current Enea Edge Management application version custom 
+        scripts are not supported as part of the offline config.</para>
+    </note>
+
     <section id="upload_scripts">
       <title>Uploading Scripts</title>
 
@@ -678,8 +684,8 @@
         </listitem>
 
         <listitem>
-          <para><literal>Once-after-startup</literal>. The script will always
-          execute after the system has rebooted, after all device
+          <para><literal>Once-after-startup</literal>. The script will only
+          execute once after the system has rebooted, after all device
           configuration processes have completed.</para>
         </listitem>
 
@@ -720,6 +726,16 @@
           role="bold">Send</emphasis>.</para>
         </listitem>
       </orderedlist>
+
+      <note>
+        <para>If two scripts are uploaded one at a time, the Enea Edge
+        Management application will delete the first script already added from 
+          the device and apply the new one. In order for both scripts to be available on
+        the device, both scripts must be uploaded at once.</para>
+      
+        <para>If multiple custom scripts of the same type are uploaded at the
+        same time, they are executed in alphabetical order.</para>
+      </note>
     </section>
 
     <section id="remove_scripts">
@@ -900,14 +916,32 @@
       </mediaobject>
     </figure>
 
-    <note>
-      <para>Only a single Wireless AP is allowed on a physical interface. The
+    <para>Only a single Wireless AP is allowed on a physical interface. The
       validation of the <literal>wap-capable</literal> interface is done when
       adding the Wireless AP, so, in case of an error, the parameters of the
       <literal>wap-capable</literal> interface must be rechecked. This can be
       done by accessing the <emphasis role="bold">Configuration</emphasis>
       menu and selecting <emphasis role="bold">External
       Interfaces</emphasis>.</para>
+
+    <note>
+      <para>For the 2.4GHz band, the <literal>802.11 g/n</literal> wireless
+      mode will use a 40MHz channel width by default. For regulatory
+      requirements compliance, channels are scanned in order to avoid
+      overlapping with existing networks. If overlaps are detected, primary
+      and secondary Wireless AP channels will be swapped, resulting in an
+      effective channel width of 20MHz instead of 40Mhz being used.
+      To avoid this, select another wireless channel.</para>
+
+      <para>For the 5GHz band, the <literal>802.11 n</literal> and the 
+        <literal>802.11 ac/n</literal> wireless modes can be configured
+      explicitly to use a specific channel number, even when Automatic
+      Channel Selection (<literal>ACS</literal>) is available. For regulatory
+      requirements compliance, channels are scanned in order to avoid
+      overlapping with existing networks. If overlaps are detected,
+      <literal>ACS</literal> will try to find another free channel,
+      resulting in a different channel number being used instead of the one
+      explicitly configured. To avoid this, select another wireless channel.</para>
     </note>
   </section>
-</chapter>
\ No newline at end of file
+</chapter>