summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarkus Mittendrein <git@maxmitti.tk>2020-04-20 21:02:54 +0200
committerMarkus Mittendrein <git@maxmitti.tk>2020-04-20 21:02:54 +0200
commit1f495f38c2842886421847d212b824cc22ac535b (patch)
tree3ebc3ea80124dcc2aec401553a78876adff7315e
parent1476ebc481a01949b6324a1eee65fb302444c83f (diff)
downloadcc4group-1f495f38c2842886421847d212b824cc22ac535b.tar.gz
cc4group-1f495f38c2842886421847d212b824cc22ac535b.zip
Fix grammar
-rw-r--r--src/cc4group.h2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/cc4group.h b/src/cc4group.h
index a7d2dcc..c08bad8 100644
--- a/src/cc4group.h
+++ b/src/cc4group.h
@@ -32,7 +32,7 @@
// - all functions, except cc4group.new, cc4group.setLazy, cc4group.openAsChild, cc4group.delete, cc4group.setWarningCallback and cc4group.setTmpMemoryStrategy (where the latter three can't fail) follow the same scheme
// all of them can fail, either caused by wrong arguments or by things outside of the applications control
// they all return _true_ if everything went well and _false_ if any error occured
-// information about the error (incredibly useful for debugging or asking for help with problems) can be obtained by using one the cc4group.getError* functions
+// information about the error (incredibly useful for debugging or asking for help with problems) can be obtained by using one of the cc4group.getError* functions
// for starters, cc4group.getErrorMessage should contain more than enough information
// just make sure that the returned string is consumed before calling it again
// only errors in the initialization functions (create and open) are seriously critical and make it impossible to continue using the group object