From ea9ea6ac4a894ff76e22cb531d340b14ec62c56b Mon Sep 17 00:00:00 2001 From: Patrick Steinhardt Date: Mon, 31 Oct 2016 13:49:52 +0100 Subject: [PATCH] Documentation: fix small typos --- PROJECTS.md | 2 +- THREADING.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/PROJECTS.md b/PROJECTS.md index 87ce78f02..a6885e38b 100644 --- a/PROJECTS.md +++ b/PROJECTS.md @@ -5,7 +5,7 @@ So, you want to start helping out with `libgit2`? That's fantastic! We welcome contributions and we promise we'll try to be nice. This is a list of libgit2 related projects that new contributors can take -on. It includes a number of good starter projects and well as some larger +on. It includes a number of good starter projects as well as some larger ideas that no one is actively working on. ## Before You Start diff --git a/THREADING.md b/THREADING.md index 0b9e50286..e9be8b99f 100644 --- a/THREADING.md +++ b/THREADING.md @@ -88,7 +88,7 @@ of libssh2 as described above, `git_openssl_set_locking()` is a no-op. If your programming language offers a package/bindings for OpenSSL, you should very strongly prefer to use that in order to set up -locking, as they provide a level of coördination which is impossible +locking, as they provide a level of coordination which is impossible when using this function. See the @@ -102,7 +102,7 @@ if there are alternatives provided by the system. libssh2 may be linked against OpenSSL or libgcrypt. If it uses OpenSSL, see the above paragraphs. If it uses libgcrypt, then you need to set up its locking before using it multi-threaded. libgit2 has no -direct connection to libgcrypt and thus has not convenience functions for +direct connection to libgcrypt and thus has no convenience functions for it (but libgcrypt has macros). Read libgcrypt's [threading documentation for more information](http://www.gnupg.org/documentation/manuals/gcrypt/Multi_002dThreading.html)