proposal: without clear agreement, the arbiter decides

This is not a policy change,
but rather a clarification of the existing wording.

Fixes golang/go#17129

Change-Id: Ie9877b10ae3eed8ad5e5763d35e48d94c6f8f523
Reviewed-on: https://go-review.googlesource.com/29335
Reviewed-by: Russ Cox <rsc@golang.org>
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
Reviewed-by: Robert Griesemer <gri@golang.org>
Reviewed-by: Jaana Burcu Dogan <jbd@google.com>

README.md

diff --git a/README.md b/README.md
index c909a14..4e92db1 100644
--- a/README.md
+++ b/README.md
@@ -103,9 +103,9 @@
 	- The goal of the final discussion is to reach agreement on the next step:
 		(1) accept or (2) decline.
 	- The discussion is expected to be resolved in a timely manner.
-	- In Go development historically, a lack of agreement means decline.
-	- If there is disagreement about whether there is agreement,
-	  [rsc@](mailto:rsc@golang.org) is the arbiter.
+	- If clear agreement cannot be reached, the arbiter
+	  ([rsc@](mailto:rsc@golang.org)) reviews the discussion
+	  and makes the decision to accept or decline.
 
 - The author (and/or other contributors) do the work as described by the
   "Implementation" section of the proposal.