[5-netconf-doc-config] typo (comment)

diff --git a/doc/guide/netconf.xml b/doc/guide/netconf.xml
index 89afcb01562fc37a87a8e8a192852a9040a6c45c..99fcf24401f22c55c020ae8a465e70e4df0274e9 100644 (file)
--- a/doc/guide/netconf.xml
+++ b/doc/guide/netconf.xml
@@ -297,7 +297,7 @@ ietf-dhcpv6-types          | 2018-01-30 | Imported    |                     |
             is subscribed for both validation and application, when false
             it is subscribed only for application.
 
-<--! Incorrect change:
+<!-- Incorrect change:
             is subscribed for both validation and application. This means
             that the kea-netconf will call config-test first and then,
             if it is successful, will call config-set to actually apply
@@ -330,7 +330,7 @@ ietf-dhcpv6-types          | 2018-01-30 | Imported    |                     |
       Note the alternative to boot with full configurations does not
       allow an easy track of changes, so it not really compatible with
       the YANG / Netconf configuration management paradigm.
-<--! spurious statement
+<!-- spurious statement
       However, the
       solution attempts to provide maximum flexibility.
 -->
@@ -377,7 +377,7 @@ ietf-dhcpv6-types          | 2018-01-30 | Imported    |                     |
           <simpara>
             It can fail to be translated from YANG to JSON, e.g.
             invalid user context.
-<--! need another example but this one falls in the next case
+<!-- need another example but this one falls in the next case
  or unsupported database type. -->
           </simpara>
         </listitem>
@@ -428,7 +428,7 @@ ietf-dhcpv6-types          | 2018-01-30 | Imported    |                     |
         <listitem>
           <simpara>
             <command>model</command> specifies the YANG model / module name.
-<--! Two bad proposals
+<!-- Two bad proposals
 (default the corresponding service Kea one).
 
 Unless explicitly specified, each Kea daemon has its own YANG model. -->