From 72eb395e1df9438f4f5b9e311086f6799506fbb5 Mon Sep 17 00:00:00 2001 From: Eric Theise Date: Sat, 10 Nov 2012 12:17:34 -0700 Subject: [PATCH] Fixing two typos --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index 4579b9b80..c59f9f0ef 100644 --- a/README.md +++ b/README.md @@ -63,7 +63,7 @@ helpful as a reference. ## Coding style When writing code it is generally a good idea to try and match your -formatting to hat of any existing code in the same file, or to other +formatting to that of any existing code in the same file, or to other similar files if you are writing new code. Consistency of layout is far more important that the layout itself as it makes reading code much easier. @@ -107,7 +107,7 @@ and why it should be the way it is. When you submit patches, the project maintainer has to read them and understand them. This is difficult enough at the best of times, and misunderstanding patches can lead to them being more difficult to -merge. To help wit this, when submitting you should: +merge. To help with this, when submitting you should: * Split up large patches into smaller units of functionality. * Keep your commit messages relevant to the changes in each individual -- 2.39.5