From 4d23b94bdab653c4b0fc59adf2804a9f929d846f Mon Sep 17 00:00:00 2001
From: Rob Pike <r@golang.org>
Date: Thu, 17 Dec 2009 12:12:47 +1100
Subject: make it more explicit that design discussions should happen before
 code reviews

R=rsc
CC=golang-dev
http://codereview.appspot.com/180075
---
 doc/code.html | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

(limited to 'doc/code.html')

diff --git a/doc/code.html b/doc/code.html
index 6e32a3d30..5c60222aa 100644
--- a/doc/code.html
+++ b/doc/code.html
@@ -12,10 +12,11 @@ It assumes you have installed Go using the
 <p>
 Before embarking on a change to an existing
 package or the creation of a new package,
-it's a good idea to send mail to the <a href="http://groups.google.com/group/golang-nuts">mailing list</a>
+be sure to send mail to the
+<a href="http://groups.google.com/group/golang-nuts">mailing list</a>
 to let people know what you are thinking of doing.
 Doing so helps avoid duplication of effort and
-enables discussions about design before much code
+enables discussions about design before any code
 has been written.
 </p>
 
-- 
cgit v1.2.3