Fix some typos/misspellings in docs

diff --git a/doc/guide/config.xml b/doc/guide/config.xml
index d9bad8debd1bb1f267ed439b5fad4300359b3b28..e1d4d7e34c0873a98e4ebc77be0d8ec396a1ea8c 100644 (file)
--- a/doc/guide/config.xml
+++ b/doc/guide/config.xml
@@ -8,7 +8,7 @@
 
   <para>Depending on configuration backend chosen (see <xref
   linkend="dhcp-config-backend"/>), configuration mechanisms are different. The
-  following sections describe details of the differeent configuration backends. Note
+  following sections describe details of the different configuration backends. Note
   that only one configuration backend can be used and its selection is
   made when the configure script is run.</para>
 

diff --git a/doc/guide/ddns.xml b/doc/guide/ddns.xml
index f6dc2adff4510615e17ae7ab6c163d90a9b300b7..08d45b7832451e16145ec3cf3ee3fc2ae5991978 100644 (file)
--- a/doc/guide/ddns.xml
+++ b/doc/guide/ddns.xml
@@ -213,7 +213,7 @@ corresponding values in the DHCP servers' "dhcp-ddns" configuration section.
         name in that domain's configuration entry.  When D2 matches a
         change request to a domain, it checks whether the domain has
         a TSIG key associated with it.  If so, D2 will use that key to
-        sign DNS update messages sent to and verify repsonses received
+        sign DNS update messages sent to and verify responses received
         from the domain's DNS server(s). For each TSIG key required by
         the DNS servers that D2 will be working with there must be a
         corresponding TSIG key in the TSIG Key list.</para>

diff --git a/doc/guide/dhcp4-srv.xml b/doc/guide/dhcp4-srv.xml
index 6060a1fb40eada76823cf704131871fe93c285c3..d7e3b6b14265be6930a733df3dd7d4369862f0ca 100644 (file)
--- a/doc/guide/dhcp4-srv.xml
+++ b/doc/guide/dhcp4-srv.xml
@@ -737,7 +737,7 @@ temporarily override a list of interface names and listen on all interfaces.
             <row><entry>record</entry><entry>Structured data that may comprise any types (except "record" and "empty")</entry></row>
             <row><entry>string</entry><entry>Any text</entry></row>
             <row><entry>uint8</entry><entry>8 bit unsigned integer with allowed values 0 to 255</entry></row>
-            <row><entry>uint16</entry><entry>16 bit unsinged integer with allowed values 0 to 65535</entry></row>
+            <row><entry>uint16</entry><entry>16 bit unsigned integer with allowed values 0 to 65535</entry></row>
             <row><entry>uint32</entry><entry>32 bit unsigned integer with allowed values 0 to 4294967295</entry></row>
           </tbody>
           </tgroup>
@@ -1412,7 +1412,7 @@ temporarily override a list of interface names and listen on all interfaces.
       <listitem><para>
       If the REQUEST contains the client FQDN option, the candidate
       name is taken from there, otherwise it is taken from the Host Name option.
-      The candiate name may then be modified:
+      The candidate name may then be modified:
       <orderedlist>
       <listitem><para>
       If the candidate name is a fully qualified domain name, use it.

diff --git a/doc/guide/dhcp6-srv.xml b/doc/guide/dhcp6-srv.xml
index 58bce84b9d3139c0612cf08802b2caea5c6393dd..7f3acd3d97bfde494b397f50b216b21393fe927d 100644 (file)
--- a/doc/guide/dhcp6-srv.xml
+++ b/doc/guide/dhcp6-srv.xml
@@ -984,7 +984,7 @@ should include options from the isc option space:
     <section id="dhcp6-subnet-class">
       <title>Limiting access to IPv6 subnet to certain classes</title>
       <para>
-        In certain cases it beneficial to restrict access to certains subnets
+        In certain cases it beneficial to restrict access to certain subnets
         only to clients that belong to a given subnet. For details on client
         classes, see <xref linkend="dhcp6-client-classifier"/>. This is an
         extension of a previous example from <xref linkend="dhcp6-address-config"/>.

diff --git a/doc/guide/intro.xml b/doc/guide/intro.xml
index 2843e6a1af003526d4d5ab63393ae3c67a09709b..d2825f11656eecf2ae2250ae3f8af85ae097cf97 100644 (file)
--- a/doc/guide/intro.xml
+++ b/doc/guide/intro.xml
@@ -114,9 +114,9 @@
 
         <listitem>
             <simpara>
-       In order to store lease information in a PostgresSQL database, Kea requires PostgresSQL
+       In order to store lease information in a PostgreSQL database, Kea requires PostgreSQL
     headers and libraries.  This is an optional dependency in that Kea can be
-    built without PostgresSQL support.
+    built without PostgreSQL support.
             </simpara>
         </listitem>
       </itemizedlist>

diff --git a/doc/guide/keactrl.xml b/doc/guide/keactrl.xml
index 02e01a4624e29560c0a0f17b54a5875d2e155409..7a587c89f5920341f2a96636e101ffe79db1b1a7 100644 (file)
--- a/doc/guide/keactrl.xml
+++ b/doc/guide/keactrl.xml
@@ -168,7 +168,7 @@ INFO/keactrl: Starting kea-dhcp-ddns -c /usr/local/etc/kea/kea.conf
 INFO/keactrl: Skip sending signal 15 to process kea-dhcp6: process is not running
 </screen>
       Note that the <command>stop</command> will attempt to stop all servers
-      regrdless of whether they are "enabled" in the <filename>keactrl.conf</filename>.
+      regardless of whether they are "enabled" in the <filename>keactrl.conf</filename>.
       If any of the servers is not running, an informational message
       is displayed as in the <command>stop</command> command output above.
       </para>