code review 53720043: doc: replace "private" with "unexported" in Effective Go.

doc: replace "private" with "unexported" in Effective Go.

[dsymonds, 2014-01-17 16:22:44]

Hello r (cc: golang-codereviews@googlegroups.com),

I'd like you to review this change to
https://code.google.com/p/go

[r, 2014-01-17 16:50:02]

https://codereview.appspot.com/53720043/diff/40001/doc/effective_go.html
File doc/effective_go.html (right):

https://codereview.appspot.com/53720043/diff/40001/doc/effective_go.html#newc...
doc/effective_go.html:291: Even for unexported names, grouping can also indicate
relationships between items,
the term isn't really used here. maybe s/private/local/

[r, 2014-01-17 16:52:11]

https://codereview.appspot.com/53720043/diff/40001/doc/effective_go.html
File doc/effective_go.html (right):

https://codereview.appspot.com/53720043/diff/40001/doc/effective_go.html#newc...
doc/effective_go.html:291: Even for unexported names, grouping can also indicate
relationships between items,
you could instead go with
Even for names that are not introduced by a comment, ...

or you could just drop it altogether:

Grouping can also indicate....

[dsymonds, 2014-01-17 17:04:13]

On 17 January 2014 08:52,  <r@golang.org> wrote:

> or you could just drop it altogether:
>
> Grouping can also indicate....

I went with this.

[dsymonds, 2014-01-17 17:06:43]

*** Submitted as https://code.google.com/p/go/source/detail?r=03ec05bfd116 ***

doc: replace "private" with "unexported" in Effective Go.

R=r
CC=golang-codereviews
https://codereview.appspot.com/53720043

[r, 2014-01-17 17:13:12]

LGTM
The usual protocol is to receive the LGTM before submitting.

[r, 2014-01-17 17:14:03]

It's also a good idea to update the CL when it becomes inaccurate.

[dsymonds, 2014-01-17 17:18:04]

Sorry, mixed up CLs. I thought you had LGTM'd. My mistake.