diff options
author | Sijawusz Pur Rahnama <sija@sija.pl> | 2020-05-25 17:49:22 +0200 |
---|---|---|
committer | Sijawusz Pur Rahnama <sija@sija.pl> | 2020-05-25 17:55:09 +0200 |
commit | fd0be84db57825472483432390fc4b87d29b4fbe (patch) | |
tree | 24b6a09976a57c208369ab75246cf75356f8c5bb /doc/camlib_devel.txt | |
parent | acafc3324695b6f51ada104af461fdf8905b03cd (diff) | |
download | libgphoto2-fd0be84db57825472483432390fc4b87d29b4fbe.tar.gz |
Fix typos throughout the codebase
Diffstat (limited to 'doc/camlib_devel.txt')
-rw-r--r-- | doc/camlib_devel.txt | 4 |
1 files changed, 2 insertions, 2 deletions
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 |