Fix typos throughout the codebase

5 files changed, 9 insertions, 9 deletions

diff --git a/doc/api/tmpl/gphoto2-abilities-list.sgml b/doc/api/tmpl/gphoto2-abilities-list.sgml
index ea7184eda..e09c74947 100644
--- a/doc/api/tmpl/gphoto2-abilities-list.sgml
+++ b/doc/api/tmpl/gphoto2-abilities-list.sgml
@@ -31,7 +31,7 @@ order to set up a #Camera, you need to call #gp_camera_set_abilities. The
       /* Scan the system for camera drivers */
       #gp_abilities_list_load (list);
 
-      /* Retreive the abilities of a specific model */
+      /* Retrieve the abilities of a specific model */
       n = #gp_abilities_list_lookup_model (list, "HP PhotoSmart C30");
       #gp_abilities_list_get_abilities (list, n, &abilities);
       #gp_abilities_list_free (list);
@@ -111,7 +111,7 @@ order to set up a #Camera, you need to call #gp_camera_set_abilities. The
   determine what library to load on #gp_camera_set_abilities.
   For retreiving abilities of a specific model, create a
   #CameraAbilitiesList and use #gp_abilities_list_load in order to scan
-  the system for drivers. Then, retreive the #CameraAbilities from this list.
+  the system for drivers. Then, retrieve the #CameraAbilities from this list.
 </para>
 
 @model: 
diff --git a/doc/build_OS2.txt b/doc/build_OS2.txt
index 2afb2b4c5..e0bfc2521 100644
--- a/doc/build_OS2.txt
+++ b/doc/build_OS2.txt
@@ -11,9 +11,9 @@ compile   : gcc version 2.8.1
             http://hobbes.nmsu.edu/cgi-bin/h-browse?sh=1&dir=/pub/os2/dev/emx/v0.9d
 
 libraries : pthreads
-            unfortunatly I don't know whih version I use here but the one from netlabs should be working
+            unfortunately I don't know whih version I use here but the one from netlabs should be working
             ftp://ftp.netlabs.org/pub/pthreads/
 
 make sure the emx\lib directory is added to your lib environment 'SET LIB=x:\EMX\LIB'
-alse the pthreads DLL's and LIB's should be in the EMX tree
+else the pthreads DLL's and LIB's should be in the EMX tree
 
diff --git a/doc/camlib_devel.lyx b/doc/camlib_devel.lyx
index 95e1cfd1e..ad8b6d4b1 100644
--- a/doc/camlib_devel.lyx
+++ b/doc/camlib_devel.lyx
@@ -644,7 +644,7 @@ Camera API
 
 The CAPI provides the full set of functions for doing various tasks with
  the camera.
- All CAPI functions return either GP_OK for succesful execution , or GP_ERROR
+ All CAPI functions return either GP_OK for successful execution , or GP_ERROR
  for a failure of execution
 \layout Standard
 
diff --git a/doc/camlib_devel.sgml b/doc/camlib_devel.sgml
index 505f19352..7f6720d8b 100644
--- a/doc/camlib_devel.sgml
+++ b/doc/camlib_devel.sgml
@@ -101,7 +101,7 @@ Cameras like to ping. This is the in the form of an &quot;ACK&quot;&quot;
  up a camera that has gone into power-save mode. It usually starts out the communications,
  as well as confirms each packet in any sort of &quot;mass&quot; transfer. The
  opposite, a &quot;NAK&quot;, is sent to basically say the last packet was not
- received, or an error has occured. Again, this is usually just a single byte
+ received, or an error has occurred. Again, this is usually just a single byte
  as well.
 
 Example:
@@ -388,7 +388,7 @@ Section 3.1 details the purpose of each of these functions, while Section
 Camera API
 <p>
 The CAPI provides the full set of functions for doing various tasks with
- the camera. All CAPI functions return either GP_OK for succesful execution
+ the camera. All CAPI functions return either GP_OK for successful execution
  , or GP_ERROR for a failure of execution
 </p>
 <p>
diff --git a/doc/camlib_devel.txt b/doc/camlib_devel.txt
index e875d03e3..8993de8a6 100644
--- a/doc/camlib_devel.txt
+++ b/doc/camlib_devel.txt
@@ -89,7 +89,7 @@ should demonstrate some commonalities between most camera protocols.
   mode. It usually starts out the communications, as well as confirms
   each packet in any sort of "mass" transfer. The opposite, a "NAK",
   is sent to basically say the last packet was not received, or an
-  error has occured. Again, this is usually just a single byte as
+  error has occurred. Again, this is usually just a single byte as
   well.
   
   Example:
@@ -337,7 +337,7 @@ Section 3.1 details the purpose of each of these functions, while Section
 3.1 Camera API
 
 The CAPI provides the full set of functions for doing various tasks
-with the camera. All CAPI functions return either GP_OK for succesful
+with the camera. All CAPI functions return either GP_OK for successful
 execution , or GP_ERROR for a failure of execution
 
 What follows is a listing of the functions, including prototypes and