[master] Unfortunate paragraph about config validation removed.

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index cf4a44e6eef171521f2bb2b8fea134ab5130794e..1e278a6af77fa26ef1a5f98e296c5a4f3f155a4d 100644 (file)
--- a/doc/guide/dhcp4-srv.xml
+++ b/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
 components defined such as Logging or DhcpDdns, so the closing brace would
 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>

diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index 745fa24a70401abdc030b7bcaccee4a2fe721c46..b0b7fd7b6d8e000f22b0beff6d339bf6d44e1ca5 100644 (file)
--- a/doc/guide/dhcp6-srv.xml
+++ b/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
 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>