From 7bfaf32312c1dbb81cb4095fb92c1d2118a0ea5c Mon Sep 17 00:00:00 2001 From: Zearin Date: Mon, 31 Mar 2014 10:46:28 -0400 Subject: [PATCH] =?UTF-8?q?notes/styleguide.rst:=20Add=20comma=20after=20?= =?UTF-8?q?=E2=80=9Ce.g.=E2=80=9D?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit To any style-obsessed writers or editors reading this commit: The comma (or lack of one) after “e.g.” or “i.e.” has always bugged me. I finally looked it up! Here’s what I found: http://english.stackexchange.com/questions/16172/should-i-always-use-a-comma-after-e-g-or-i-e --- docs/notes/styleguide.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/notes/styleguide.rst b/docs/notes/styleguide.rst index 887a7bb..366c1ae 100644 --- a/docs/notes/styleguide.rst +++ b/docs/notes/styleguide.rst @@ -30,7 +30,7 @@ Strive to keep any contributions relevant to the :ref:`purpose of The Guide * `Cite `_ references where needed. * If a subject isn't directly relevant to Python, but useful in conjunction - with Python (e.g. Git, GitHub, Databases), reference by linking to useful + with Python (e.g., Git, GitHub, Databases), reference by linking to useful resources, and describe why it's useful to Python. * When in doubt, ask.