aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--NEWS2
-rw-r--r--camel/CODING.STYLE12
-rw-r--r--devel-docs/camel/README_AND_TODO.txt10
3 files changed, 12 insertions, 12 deletions
diff --git a/NEWS b/NEWS
index df2c37094d..5b9f6e1c60 100644
--- a/NEWS
+++ b/NEWS
@@ -1,7 +1,7 @@
01/Jun/1999
-----------
-New developpement document from Giao Nguyen :
+New development document from Giao Nguyen :
TITLE: An in-depth look at the virtual folder mechanism
(see devel-docs/query)
diff --git a/camel/CODING.STYLE b/camel/CODING.STYLE
index df1bf5c874..a236f0060f 100644
--- a/camel/CODING.STYLE
+++ b/camel/CODING.STYLE
@@ -6,12 +6,12 @@ be sure to follow the same coding style as the intial authors.
Please read the file HACKING in gnumeric and follow the
general guidelines explained in it.
-Please take a look at camel source files and try to
-imitate the coding style the best possible. We are perfectly
-aware that this is not the best and unique style, but it
-is absolutely mandatory that Camel is homogeneous.
-If you find the current coding style to have some weaknesses,
-please contact the authors to discuss this matter.
+Please take a look at camel source files and try to exactly
+imitate the coding style. We are perfectly aware that this
+is not the best and unique style, but it is absolutely
+mandatory that Camel is homogeneous. If you find the current
+coding style to have some weaknesses, please contact the
+authors to discuss this matter.
Thanks.
diff --git a/devel-docs/camel/README_AND_TODO.txt b/devel-docs/camel/README_AND_TODO.txt
index a842e57bd1..5feeb1e4e9 100644
--- a/devel-docs/camel/README_AND_TODO.txt
+++ b/devel-docs/camel/README_AND_TODO.txt
@@ -1,4 +1,4 @@
-Camel is currently (conceptually) separated in four parts:
+Camel is currently (conceptualy) separated in four parts:
* the session handling
* the storage mechanism.
@@ -15,13 +15,13 @@ CamelSession is an object used to store some parameters on a user
basis. This can be a permanent (fs based) or volatile
(ram only) storage depending on user preferences.
The session object is, for example, responsible for
-remmbering authentication datas during application lifetime.
+remembering authentication datas during application lifetime.
It is also responsible for selecting and loading providers
corresponding to protocols. In the case where only one
-provider exists for a given protocols, the task is trivial,
+provider exists for a given protocol, the task is trivial,
but when multiple providers exist for a given protocol, the
-user can choose its prefered one. Given its relationship
-with providers, the session objects is also used to instanciate
+user can choose their prefered one. Given its relationship
+with providers, the session object is also used to instanciate
a store given an URL.
Associated Classes: