From 4887bb2bef5a09fc6cbdeea68012807000eea42e Mon Sep 17 00:00:00 2001
From: Joshua Olson <0joshua.olson1@gmail.com>
Date: Thu, 23 Jun 2016 17:26:22 -0600
Subject: [PATCH] Fix punctuation

Not sure if any lines became too long...
---
 doc/nep1.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/nep1.rst b/doc/nep1.rst
index b4bd6309cc..b5991ba9ee 100644
--- a/doc/nep1.rst
+++ b/doc/nep1.rst
@@ -125,8 +125,8 @@ changed in the future.
 Coding Conventions
 ------------------
 
-- The 'return' statement should only be used when it's control-flow properties
-  are required. Use a procedures implicit 'result' variable instead. This
+- The 'return' statement should only be used when its control-flow properties
+  are required. Use a procedure's implicit 'result' variable instead. This
   improves readability.
 
 - Prefer to return `[]` and `""` instead of `nil`, or throw an exception if
@@ -150,7 +150,7 @@ Conventions for multi-line statements and expressions
 
 - Any tuple type declarations that are longer than one line should use the
   regular object type layout instead. This enhances the readability of the
-  tuple declaration by splitting its members information across multiple lines.
+  tuple declaration by splitting its members' information across multiple lines.
 
   .. code-block:: nim
     type