aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKjartan Maraas <kmaraas@src.gnome.org>2006-08-17 21:19:54 +0800
committerKjartan Maraas <kmaraas@src.gnome.org>2006-08-17 21:19:54 +0800
commit58c928d92dc975b777bd8a40bea5945a47f3570b (patch)
treeeaf110ba186456a9b1453ab9e89268b60074d899
parent32cf31fe733aa62c3da284bf2c0dcc47c861dd7e (diff)
downloadgsoc2013-evolution-58c928d92dc975b777bd8a40bea5945a47f3570b.tar.gz
gsoc2013-evolution-58c928d92dc975b777bd8a40bea5945a47f3570b.tar.zst
gsoc2013-evolution-58c928d92dc975b777bd8a40bea5945a47f3570b.zip
Fix som typos
svn path=/trunk/; revision=32567
-rw-r--r--devel-docs/camel/tmpl/camel-store.sgml4
-rw-r--r--devel-docs/misc/ref_and_id_proposition.txt4
2 files changed, 4 insertions, 4 deletions
diff --git a/devel-docs/camel/tmpl/camel-store.sgml b/devel-docs/camel/tmpl/camel-store.sgml
index 2882c09986..792bd2be39 100644
--- a/devel-docs/camel/tmpl/camel-store.sgml
+++ b/devel-docs/camel/tmpl/camel-store.sgml
@@ -7,9 +7,9 @@ A class representing a message (local or distant) repository
<!-- ##### SECTION Long_Description ##### -->
<para>
-The store class models a place where messages can be stored and retreived. It can be a local
+The store class models a place where messages can be stored and retrieved. It can be a local
store (for example an mbox-style store) or a distant server (for example an POP3 server). Messages are
-not retreived or stored directly with a CamelStore object. Instead, a CamelFolder object must be
+not retrieved or stored directly with a CamelStore object. Instead, a CamelFolder object must be
obtained from the store first.
</para>
diff --git a/devel-docs/misc/ref_and_id_proposition.txt b/devel-docs/misc/ref_and_id_proposition.txt
index 2127b45a57..9d790ffd8e 100644
--- a/devel-docs/misc/ref_and_id_proposition.txt
+++ b/devel-docs/misc/ref_and_id_proposition.txt
@@ -56,7 +56,7 @@ folder caching or message referencing if messages are referenced only
by their position within their parent folder.
-We thus have to find a general way to identify and retreive a message
+We thus have to find a general way to identify and retrieve a message
within its folder. One thing is sure, however: all folders
implementation won't allow this method. Pop3 stores will always access
messages using their rank on the server. MUA using Camel will thus
@@ -181,7 +181,7 @@ gboolean camel_folder_uid_is_reference (CamelFolder *folder, gchar *uid)
Then all usual operations on the folder act if the message was
actually physically stored in this folder. For example, when the mailer
uses camel_folder_get_message_by_uid onto the (v)folder, the actual
-message is retreived from its physical store.
+message is retrieved from its physical store.
As you can see, the uid of the message within its physical parent
folder is different than its uid within the (v)folder. This is because