summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAntonio Murdaca <runcom@redhat.com>2016-03-05 13:30:07 +0100
committerStef Walter <stefw@redhat.com>2016-03-08 13:32:07 +0100
commit43cac02864eb183d71877b7425e0a6ec0c9fc01e (patch)
tree6cbc5306f57d566754f1820fb8973aa703564a79
parent7da8c2b70ed47acf59854406ca931d00f3ff9a90 (diff)
downloadlibsecret-43cac02864eb183d71877b7425e0a6ec0c9fc01e.tar.gz
Fix typos
Signed-off-by: Antonio Murdaca <runcom@redhat.com> Signed-off-by: Stef Walter <stefw@redhat.com> * Fix one spelling of 'succeeded' https://bugzilla.gnome.org/show_bug.cgi?id=763143
-rw-r--r--build/valgrind/valgrind.h2
-rw-r--r--docs/reference/libsecret/migrating-libgnome-keyring.xml2
-rw-r--r--egg/egg-secure-memory.c2
-rw-r--r--libsecret/secret-item.c8
-rw-r--r--libsecret/secret-schema.c2
5 files changed, 8 insertions, 8 deletions
diff --git a/build/valgrind/valgrind.h b/build/valgrind/valgrind.h
index 4b8ef75..b5edc11 100644
--- a/build/valgrind/valgrind.h
+++ b/build/valgrind/valgrind.h
@@ -6826,7 +6826,7 @@ VALGRIND_PRINTF_BACKTRACE(const char *format, ...)
/* These requests allow control to move from the simulated CPU to the
- real CPU, calling an arbitary function.
+ real CPU, calling an arbitrary function.
Note that the current ThreadId is inserted as the first argument.
So this call:
diff --git a/docs/reference/libsecret/migrating-libgnome-keyring.xml b/docs/reference/libsecret/migrating-libgnome-keyring.xml
index cf8e34c..7f727ec 100644
--- a/docs/reference/libsecret/migrating-libgnome-keyring.xml
+++ b/docs/reference/libsecret/migrating-libgnome-keyring.xml
@@ -58,7 +58,7 @@
for lookup of items it's important that the string representations of
integers and booleans are always identical. Boolean values are stored
as the strings <literal>true</literal> and <literal>false</literal>.
- Integer values are stored in decimal, with a preceeding negative sign
+ Integer values are stored in decimal, with a preceding negative sign
for negative integers. libsecret facilitates this using the
secret_attributes_build() and secret_attributes_buildv() functions.</para>
diff --git a/egg/egg-secure-memory.c b/egg/egg-secure-memory.c
index 442a325..8d320f1 100644
--- a/egg/egg-secure-memory.c
+++ b/egg/egg-secure-memory.c
@@ -1299,7 +1299,7 @@ egg_secure_records (unsigned int *count)
if (records == NULL)
break;
- /* Make sure this actualy accounts for all memory */
+ /* Make sure this actually accounts for all memory */
ASSERT (total == block->n_words);
}
diff --git a/libsecret/secret-item.c b/libsecret/secret-item.c
index 2393dea..116e840 100644
--- a/libsecret/secret-item.c
+++ b/libsecret/secret-item.c
@@ -1259,7 +1259,7 @@ secret_item_load_secret (SecretItem *self,
* The newly loaded secret value can be accessed by calling
* secret_item_get_secret().
*
- * Returns: whether the secret item succesfully loaded or not
+ * Returns: whether the secret item successfully loaded or not
*/
gboolean
secret_item_load_secret_finish (SecretItem *self,
@@ -1292,7 +1292,7 @@ secret_item_load_secret_finish (SecretItem *self,
* This function may block indefinetely. Use the asynchronous version
* in user interface threads.
*
- * Returns: whether the secret item succesfully loaded or not
+ * Returns: whether the secret item successfully loaded or not
*/
gboolean
secret_item_load_secret_sync (SecretItem *self,
@@ -1486,7 +1486,7 @@ secret_item_load_secrets (GList *items,
*
* Items that are locked will not have their secrets loaded.
*
- * Returns: whether the operation succeded or not
+ * Returns: whether the operation succeeded or not
*/
gboolean
secret_item_load_secrets_finish (GAsyncResult *result,
@@ -1520,7 +1520,7 @@ secret_item_load_secrets_finish (GAsyncResult *result,
*
* Items that are locked will not have their secrets loaded.
*
- * Returns: whether the operation succeded or not
+ * Returns: whether the operation succeeded or not
*/
gboolean
secret_item_load_secrets_sync (GList *items,
diff --git a/libsecret/secret-schema.c b/libsecret/secret-schema.c
index 33522ef..5ba3a9f 100644
--- a/libsecret/secret-schema.c
+++ b/libsecret/secret-schema.c
@@ -83,7 +83,7 @@
* values. Even for values that defined as an integer or boolean in the schema,
* the attribute values in the #GHashTable are strings. Boolean values are stored
* as the strings 'true' and 'false'. Integer values are stored in decimal, with
- * a preceeding negative sign for negative integers.
+ * a preceding negative sign for negative integers.
*
* Schemas are handled entirely on the client side by this library. The name of the
* schema is automatically stored as an attribute on the item.