summary refs log tree commit diff stats
diff options
context:
space:
mode:
authorAndreas Rumpf <rumpf_a@web.de>2016-06-26 12:45:26 +0200
committerGitHub <noreply@github.com>2016-06-26 12:45:26 +0200
commit1362b8bbc78f5c44118487346e50c20b5517367e (patch)
tree0e34db97f015a50855ae1484ee250788845ffa6c
parent90bae468397abafc3ca0b33affcf8a01743e6415 (diff)
parent4887bb2bef5a09fc6cbdeea68012807000eea42e (diff)
downloadNim-1362b8bbc78f5c44118487346e50c20b5517367e.tar.gz
Merge pull request #4404 from 0joshuaolson1/patch-1
Fix punctuation
-rw-r--r--doc/nep1.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/doc/nep1.rst b/doc/nep1.rst
index b4bd6309c..b5991ba9e 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