[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-commits
Subject:    [ksecrets] src/runtime/ksecrets_backend: Spelling check
From:       Valentin Rusu <kde () rusu ! info>
Date:       2015-08-06 16:00:05
Message-ID: E1ZNNaP-0000oh-8n () scm ! kde ! org
[Download RAW message or body]

Git commit 7bd1036e5bb37ce5830cada3d2dc33bbbe7e8572 by Valentin Rusu.
Committed on 06/08/2015 at 15:59.
Pushed by vrusu into branch 'master'.

Spelling check

M  +3    -3    src/runtime/ksecrets_backend/ksecrets_backend.h

http://commits.kde.org/ksecrets/7bd1036e5bb37ce5830cada3d2dc33bbbe7e8572

diff --git a/src/runtime/ksecrets_backend/ksecrets_backend.h b/src/runtime/ksecrets_backend/ksecrets_backend.h
index d7378a3..489a842 100644
--- a/src/runtime/ksecrets_backend/ksecrets_backend.h
+++ b/src/runtime/ksecrets_backend/ksecrets_backend.h
@@ -36,7 +36,7 @@
  * state between calls. So, even if your application crashes, the file won't get corrupted.
  * FIXME is that OK? Further tests should be confirm if a background sync should be introduced
  *       in order to get operations faster. However, today computing power do not justify
- *       Ã  priori optimisations, so this first version would modify the file with eatch API call.
+ *       Ã  priori optimizations, so this first version would modify the file with each API call.
  *       That guarantee client applications that edits are always synced to disk/storage.
  *
  * The API calls are organized in classes, following the structure of data in the backend.
@@ -108,7 +108,7 @@ public:
     /* Holds a secret value.
      *
      * The Item class let applications associate metadata with secret values.
-     * These matadata could simply be the label or other custom attributes.
+     * These metadata could simply be the label or other custom attributes.
      * Items are organized in Collections.
      *
      * @see Collection
@@ -129,7 +129,7 @@ public:
     using ItemPtr = std::shared_ptr<Item>;
 
     /**
-     * Each application organises it's secrets in collections.
+     * Each application organizes it's secrets in collections.
      *
      * Typical applications will only use one collection. A collection can store
      * an arbitrary amount of Items. Each Item has a label, custom attributes and
[prev in list] [next in list] [prev in thread] [next in thread]