summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEdward Thomson <ethomson@github.com>2017-02-26 16:08:00 +0000
committerGitHub <noreply@github.com>2017-02-26 16:08:00 +0000
commit55d911d69a1e4d5f9845cadf13dc73acde926be9 (patch)
treeb62689ea93f846007d18da3d79e9e2e626936191
parent6313a20855bf4a32bd5f3b8e1b35e81ba5d709ad (diff)
parentc1239e33273db65b09660ff0efd4b58df0e97af0 (diff)
downloadlibgit2-55d911d69a1e4d5f9845cadf13dc73acde926be9.tar.gz
Merge pull request #4142 from pblesi/patch-1
Fix minor typos in CONVENTIONS.md
-rw-r--r--CONVENTIONS.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/CONVENTIONS.md b/CONVENTIONS.md
index 0be4b33cc..ffb696a4d 100644
--- a/CONVENTIONS.md
+++ b/CONVENTIONS.md
@@ -18,11 +18,11 @@ other's toes.
- If a function returns an object as a return value, that function is
a getter and the object's lifetime is tied to the parent
object. Objects which are returned as the first argument as a
- pointer-to-pointer are owned by the caller and it is repsponsible
+ pointer-to-pointer are owned by the caller and it is responsible
for freeing it. Strings are returned via `git_buf` in order to
allow for re-use and safe freeing.
- - Most of what libgit2 does relates to I/O so you as a general rule
+ - Most of what libgit2 does relates to I/O so as a general rule
you should assume that any function can fail due to errors as even
getting data from the filesystem can result in all sorts of errors
and complex failure cases.