Parcourir la source

[master] Unfortunate paragraph about config validation removed.

Tomek Mrugalski il y a 10 ans
Parent
commit
75361d975c
2 fichiers modifiés avec 0 ajouts et 14 suppressions
  1. 0 8
      doc/guide/dhcp4-srv.xml
  2. 0 6
      doc/guide/dhcp6-srv.xml

+ 0 - 8
doc/guide/dhcp4-srv.xml

@@ -237,14 +237,6 @@ global and Dhcp4, hence we need two closing curly brackets to close them.
 In a real life configuration file there most likely would be additional
 In a real life configuration file there most likely would be additional
 components defined such as Logging or DhcpDdns, so the closing brace would
 components defined such as Logging or DhcpDdns, so the closing brace would
 be followed by a comma and another object definition.</para>
 be followed by a comma and another object definition.</para>
-
-<para>Kea 0.9 does not have configuration syntax validation
-implemented yet. Such a feature is planned for the near future. For
-the time being, it is convenient to use on-line JSON validators and/or
-viewers to check whether the syntax is correct. One example of such a
-JSON validator is available at <ulink
-url="http://jsonviewer.stack.hu/"/>.
-</para>
 </section>
 </section>
 
 
 <section>
 <section>

+ 0 - 6
doc/guide/dhcp6-srv.xml

@@ -243,12 +243,6 @@ In a real life configuration file there most likely would be additional
 components defined such as Logging or DhcpDdns, so the closing brace would
 components defined such as Logging or DhcpDdns, so the closing brace would
 be followed by a comma and another object definition.</para>
 be followed by a comma and another object definition.</para>
 
 
-<para>Kea 0.9 does not have configuration syntax validation
-implemented yet. Such a feature is planned for the near future. For
-the time being, it is convenient to use on-line JSON validators and/or
-viewers to check whether the syntax is correct. One example of such a
-JSON validator is available at <ulink url="http://jsonviewer.stack.hu/"/>.
-</para>
 </section>
 </section>
 
 
 <section>
 <section>