From e749c0302fb3a1c9c84803ad5cf9825951485e74 Mon Sep 17 00:00:00 2001 From: Martin Alix Date: Sat, 8 Jul 2017 15:22:56 -0400 Subject: [PATCH] Orthographic corrections (#35) --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index ad4370f..6f7be9c 100644 --- a/README.md +++ b/README.md @@ -83,8 +83,8 @@ Having a good guideline for creating commits and sticking to it makes working wi * For projects with more than one repository, provide links to them in their respective `README.md` files. * Keep `README.md` updated as project evolves. * Comment your code. Try to make it as clear as possible what you are intending with each major section. -* If there an open discussion on gthub or stackoverflow about the code or approch you're using, include the link in your comment, -* Don't use commenting as an excuse for a bad code. Keep your code clean +* If there is an open discussion on github or stackoverflow about the code or approach you're using, include the link in your comment, +* Don't use commenting as an excuse for a bad code. Keep your code clean. * Don't use clean code as an excuse to not comment at all. * Comment even small sections of code if you think it's not self explanatory. * Keep comments relevant as your code evolves.