diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index cf4a44e6ee..3f64f93d9c 100644
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -238,13 +238,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>
diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index 745fa24a70..b0b7fd7b6d 100644
--- 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>
diff --git a/doc/guide/install.xml b/doc/guide/install.xml
index 8bc17fba37..edfb374a98 100644
--- a/doc/guide/install.xml
+++ b/doc/guide/install.xml
@@ -388,7 +388,7 @@ Debian and Ubuntu:
 
     <section id="dhcp-config-backend">
       <title>Selecting the Configuration Backend</title>
-      <para>Kea 0.9 introduces configuration backends that are
+      <para>Kea 0.9 has introduced configuration backends that are
       switchable during the compilation phase. The backend is chosen using
       the --with-kea-config switch when running the configure script. It
       currently supports two values: BUNDY and JSON. JSON is the default.
diff --git a/src/bin/dhcp4/dhcp4.dox b/src/bin/dhcp4/dhcp4.dox
index 1ef2d5bf2a..6638328c86 100644
--- a/src/bin/dhcp4/dhcp4.dox
+++ b/src/bin/dhcp4/dhcp4.dox
@@ -203,7 +203,7 @@ becoming more and more popular among various projects. There are unofficial patc
 ISC-DHCP that keep parts of the configuration in LDAP. It was also suggested that in some
 cases it would be convenient to keep configuration in XML files.
 
-Kea 0.9 introduces configuration backends that are switchable during compilation phase.
+Kea 0.9 has introduced configuration backends that are switchable during compilation phase.
 There is a new parameter for configure script: --with-kea-config. It currently supports
 two values: BUNDY and JSON.
 
diff --git a/src/bin/dhcp6/dhcp6.dox b/src/bin/dhcp6/dhcp6.dox
index 40e5cae1ab..890414234b 100644
--- a/src/bin/dhcp6/dhcp6.dox
+++ b/src/bin/dhcp6/dhcp6.dox
@@ -239,7 +239,7 @@ becoming more and more popular among various projects. There are unofficial patc
 ISC-DHCP that keep parts of the configuration in LDAP. It was also suggested that in some
 cases it would be convenient to keep configuration in XML files.
 
-Kea 0.9 introduces configuration backends that are switchable during compilation phase.
+Kea 0.9 has introduced configuration backends that are switchable during compilation phase.
 There is a new parameter for configure script: --with-kea-config. It currently supports
 two values: BUNDY and JSON.