ldb: Fix code spelling

Signed-off-by: Joseph Sutton <josephsutton@catalyst.net.nz>
Reviewed-by: Andrew Bartlett <abartlet@samba.org>

diff --git a/lib/ldb/common/ldb.c b/lib/ldb/common/ldb.c
index fe7c4d18f5cc2418839fe14e4fe86db333ecef8c..c1c33d8ad9cd8b008aa8fc01ba815c53ee2a59ff 100644 (file)
--- a/lib/ldb/common/ldb.c
+++ b/lib/ldb/common/ldb.c
@@ -986,7 +986,7 @@ struct ldb_db_lock_context {
 };
 
 /*
- * We have to have a the unlock on a destructor so that we unlock the
+ * We have to have the unlock on a destructor so that we unlock the
  * DB if a caller calls talloc_free(req).  We trust that the ldb
  * context has not already gone away.
  */

diff --git a/lib/ldb/common/ldb_msg.c b/lib/ldb/common/ldb_msg.c
index 8ffbced940a9e1e5693f0d807cd74352c4e92ffd..a9f59006173d8b4573f631f53edd1fb3b386b2d4 100644 (file)
--- a/lib/ldb/common/ldb_msg.c
+++ b/lib/ldb/common/ldb_msg.c
@@ -1576,7 +1576,7 @@ char *ldb_timestring(TALLOC_CTX *mem_ctx, time_t t)
                return NULL;
        }
 
-       /* we now exactly how long this string will be */
+       /* we know exactly how long this string will be */
        ts = talloc_array(mem_ctx, char, 18);
 
        /* formatted like: 20040408072012.0Z */
@@ -1692,7 +1692,7 @@ char *ldb_timestring_utc(TALLOC_CTX *mem_ctx, time_t t)
                return NULL;
        }
 
-       /* we now exactly how long this string will be */
+       /* we know exactly how long this string will be */
        ts = talloc_array(mem_ctx, char, 14);
 
        /* formatted like: 20040408072012.0Z => 040408072012Z */

diff --git a/lib/ldb/include/ldb.h b/lib/ldb/include/ldb.h
index 154671bc3a6f0524c9aa8c2dddb17ce09957fc41..825df7401bb760f69015a53f858fa93fdee06375 100644 (file)
--- a/lib/ldb/include/ldb.h
+++ b/lib/ldb/include/ldb.h
@@ -1471,7 +1471,7 @@ int ldb_extended_default_callback(struct ldb_request *req, struct ldb_reply *are
   \param ldb the context associated with the database (from ldb_init())
   \param mem_ctx a talloc memory context (used as parent of ret_req)
   \param oid the OID of the extended operation.
-  \param data a void pointer a the extended operation specific parameters,
+  \param data a void pointer to the extended operation specific parameters,
   it needs to be NULL or a valid talloc pointer! talloc_get_type() will be used on it
   \param controls an array of controls
   \param context the callback function context
@@ -1495,7 +1495,7 @@ int ldb_build_extended_req(struct ldb_request **ret_req,
 
   \param ldb the context associated with the database (from ldb_init())
   \param oid the OID of the extended operation.
-  \param data a void pointer a the extended operation specific parameters,
+  \param data a void pointer to the extended operation specific parameters,
   it needs to be NULL or a valid talloc pointer! talloc_get_type() will be used on it
   \param res the result of the extended operation
 

diff --git a/lib/ldb/ldb_key_value/ldb_kv.c b/lib/ldb/ldb_key_value/ldb_kv.c
index 875061c98b8327218b52ed6678c4bf77563dd0e8..347b4fbfd8ad0462f3efa62ea18d60a178433024 100644 (file)
--- a/lib/ldb/ldb_key_value/ldb_kv.c
+++ b/lib/ldb/ldb_key_value/ldb_kv.c
@@ -861,7 +861,7 @@ static int ldb_kv_find_element(const struct ldb_message *msg, const char *name)
 
 /*
   add an element to an existing record. Assumes a elements array that we
-  can call re-alloc on, and assumed that we can re-use the data pointers from
+  can call re-alloc on, and assumes that we can reuse the data pointers from
   the passed in additional values. Use with care!
 
   returns 0 on success, -1 on failure (and sets errno)

diff --git a/lib/ldb/ldb_key_value/ldb_kv_index.c b/lib/ldb/ldb_key_value/ldb_kv_index.c
index bcbd903f6fb2b17a331c92d3138774ade1904929..f76087de6afd5b5aff75dcacffe0d7ead3d963ad 100644 (file)
--- a/lib/ldb/ldb_key_value/ldb_kv_index.c
+++ b/lib/ldb/ldb_key_value/ldb_kv_index.c
@@ -55,7 +55,7 @@ dn: @INDEX:NAME:DNSUPDATEPROXY
 
 In this format, @IDX is multi-valued, one entry for each match
 
-The corrosponding entry is stored in a TDB record with key:
+The corresponding entry is stored in a TDB record with key:
 
 DN=CN=DNSUPDATEPROXY,CN=USERS,DC=ADDOM,DC=SAMBA,DC=EXAMPLE,DC=COM
 
@@ -79,7 +79,7 @@ by the @IDXGUID attribute on @INDEXLIST.
 If there are multiple values the @IDX value simply becomes longer,
 in multiples of 16.
 
-The corrosponding entry is stored in a TDB record with key:
+The corresponding entry is stored in a TDB record with key:
 
 GUID=<binary GUID>