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
This commit is contained in:
Antonio Murdaca 2016-03-05 13:30:07 +01:00 committed by Stef Walter
parent 7da8c2b70e
commit 43cac02864
5 changed files with 8 additions and 8 deletions

View File

@ -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:

View File

@ -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>

View File

@ -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);
}

View File

@ -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,

View File

@ -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.