[master] spelling

doc/examples/kea4/backends.json

@@ -1,5 +1,5 @@
 # This is an example configuration file for the DHCPv4 server in Kea.
-# It is a basic scenario with one IPv4 subnet configured. It demnstrates
+# It is a basic scenario with one IPv4 subnet configured. It demonstrates
 # how to configure Kea to use various backends to store leases:
 # - memfile
 # - MySQL
@@ -27,9 +27,9 @@
 
 # 2. MySQL backend. Leases will be stored in MySQL database. Make sure it
 # is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type and name. If other parameters are not specified,
-# Kea will assume the database is avaiable on localhost, that user and
+# Kea will assume the database is available on localhost, that user and
 # password is not necessary to connect and that timeout is 5 seconds.
 # Kea must be compiled with --with-dhcp-mysql option to use this backend.
 #  "lease-database": {
@@ -43,9 +43,9 @@
 
 # 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make
 # sure it is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type and name. If other parameters are not specified,
-# Kea will assume the database is avaiable on localhost, that user and
+# Kea will assume the database is available on localhost, that user and
 # password is not necessary to connect and that timeout is 5 seconds.
 # Kea must be compiled with --with-dhcp-pgsql option to use this backend.
 #  "lease-database": {
@@ -58,7 +58,7 @@
 
 # 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make
 # sure it is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type, keyspace and contact_points. At least one contact point
 # must be specified, but more than one is required for redundancy. Make sure
 # you specify the contact points without spaces. Kea must be compiled with

doc/examples/kea6/backends.json

@@ -1,5 +1,5 @@
 # This is an example configuration file for the DHCPv6 server in Kea.
-# It is a basic scenario with one IPv6 subnet configured. It demnstrates
+# It is a basic scenario with one IPv6 subnet configured. It demonstrates
 # how to configure Kea to use various backends to store leases:
 # - memfile
 # - MySQL
@@ -26,9 +26,9 @@
 
 # 2. MySQL backend. Leases will be stored in MySQL database. Make sure it
 # is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type and name. If other parameters are not specified,
-# Kea will assume the database is avaiable on localhost, that user and
+# Kea will assume the database is available on localhost, that user and
 # password is not necessary to connect and that timeout is 5 seconds.
 # Kea must be compiled with --with-dhcp-mysql option to use this backend.
 #  "lease-database": {
@@ -42,9 +42,9 @@
 
 # 3. PostgreSQL backend. Leases will be stored in PostgreSQL database. Make
 # sure it is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type and name. If other parameters are not specified,
-# Kea will assume the database is avaiable on localhost, that user and
+# Kea will assume the database is available on localhost, that user and
 # password is not necessary to connect and that timeout is 5 seconds.
 # Kea must be compiled with --with-dhcp-pgsql option to use this backend.
 #  "lease-database": {
@@ -57,7 +57,7 @@
 
 # 4. CQL (Cassandra) backend. Leases will be stored in Cassandra database. Make
 # sure it is up, running and properly initialized. See kea-admin documentation
-# for details on how to intialize the database. The only strictly required
+# for details on how to initialize the database. The only strictly required
 # parameters are type, keyspace and contact_points. At least one contact point
 # must be specified, but more than one is required for redundancy. Make sure
 # you specify the contact points without spaces. Kea must be compiled with

doc/guide/admin.xml

@@ -72,7 +72,7 @@
         <listitem>
           <simpara>
             <command>lease-init</command> &mdash;
-            Initializes a new lease database. This is useful during a new 
+            Initializes a new lease database. This is useful during a new
             Kea installation. The database is initialized to the
             latest version supported by the version of the software being
             installed.

doc/guide/hooks.xml

@@ -271,7 +271,7 @@
           </itemizedlist>
         </para>
         <para>
-          Once loaded, the library allows segregating incomings requests into
+          Once loaded, the library allows segregating incoming requests into
           known and unknown clients. For known clients, the packets are
           processed mostly as usual, except it is possible to override certain
           options being sent. That can be done on a per host basis. Clients
@@ -306,7 +306,7 @@
             is "HW_ADDR" for IPv4 users or "DUID" for IPv6
             users</para></listitem>
             <listitem><para><command>id</command>, whose value is
-            either the hardware address or the DUID from the equest
+            either the hardware address or the DUID from the request
             formatted as a string of hex digits, with or without
             ":" delimiters.</para></listitem>
           </itemizedlist>