code review 5845059: doc: various typos, remove apostrophes from ordinals

doc: various typos, remove apostrophes from ordinals

[jnj, 2012-03-17 08:36:46]

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

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

[r, 2012-03-17 09:21:28]

http://codereview.appspot.com/5845059/diff/4001/doc/gccgo_install.html
File doc/gccgo_install.html (right):

http://codereview.appspot.com/5845059/diff/4001/doc/gccgo_install.html#newcod...
doc/gccgo_install.html:345: The C function naturally expects a null terminated
string, which in
it's actually NUL-terminated. it's not a null. the original is correct in that
regard, but spelled wrong.

s/nul /NUL-/

http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html
File doc/go_mem.html (right):

http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html#newcode286
doc/go_mem.html:286: the <i>n</i>th call to <code>l.Unlock()</code> happens
before the <i>m</i>th call to <code>l.Lock()</code> returns.
disappointed to learn there's no superscript th in unicode. given that, this is
probably the best we can do without a rewrite. so let's rewrite

call n of l.Unlock happens before call m of l.Lock returns

http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html#newcode321
doc/go_mem.html:321: before the (<i>n</i>+1)th call to <code>l.Lock</code>.
this (n+1)th isn't right.  nth is bad enough.   so rewrite again

the l.RLock happens (returns) after call n to l.Unlock and the matching call to
l.Runlock happens before call n+1 to l.Lock.

[jnj, 2012-03-17 09:45:35]

http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html
File doc/go_mem.html (right):

http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html#newcode286
doc/go_mem.html:286: the <i>n</i>th call to <code>l.Unlock()</code> happens
before the <i>m</i>th call to <code>l.Lock()</code> returns.
On 2012/03/17 09:21:28, r wrote:
> disappointed to learn there's no superscript th in unicode. given that, this
is
> probably the best we can do without a rewrite. so let's rewrite
> 
> call n of l.Unlock happens before call m of l.Lock returns

We could also use the <sup> HTML tag. It looks good here, and a search tells me
it is supported by all major browsers. Either way, "nth" appears a couple times
in the language specification page, shall I change those as well?

[r2, 2012-03-17 09:52:44]

On 17/03/2012, at 8:45 PM, jeremyjackins@gmail.com wrote:

> 
> http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html
> File doc/go_mem.html (right):
> 
> http://codereview.appspot.com/5845059/diff/4001/doc/go_mem.html#newcode286
> doc/go_mem.html:286: the <i>n</i>th call to <code>l.Unlock()</code>
> happens before the <i>m</i>th call to <code>l.Lock()</code> returns.
> On 2012/03/17 09:21:28, r wrote:
>> disappointed to learn there's no superscript th in unicode. given
> that, this is
>> probably the best we can do without a rewrite. so let's rewrite
> 
>> call n of l.Unlock happens before call m of l.Lock returns
> 
> We could also use the <sup> HTML tag. It looks good here, and a search
> tells me it is supported by all major browsers. Either way, "nth"
> appears a couple times in the language specification page, shall I
> change those as well?

Leave the spec for now. I feel nth by itself is ok, but n+1th is not and it's
worth keeping the document consistent.  Let's see how it works there; we can
tweak the spec later as part of another edit.

-rob

[jnj, 2012-03-17 20:04:38]

http://codereview.appspot.com/5845059/diff/4001/doc/gccgo_install.html
File doc/gccgo_install.html (right):

http://codereview.appspot.com/5845059/diff/4001/doc/gccgo_install.html#newcod...
doc/gccgo_install.html:345: The C function naturally expects a null terminated
string, which in
On 2012/03/17 09:21:28, r wrote:
> it's actually NUL-terminated. it's not a null. the original is correct in that
> regard, but spelled wrong.
> 
> s/nul /NUL-/

Done.

[jnj, 2012-03-17 20:05:09]

Hello golang-dev@googlegroups.com, r@golang.org, r@google.com (cc:
golang-dev@googlegroups.com),

Please take another look.

[r, 2012-03-18 00:45:25]

You didn't rewrite go_mem.html as suggested.

[jnj, 2012-03-18 19:43:48]

On 2012/03/18 00:45:25, r wrote:
> You didn't rewrite go_mem.html as suggested.

Sorry, I misread "Let's see how it works there" as "Let's see how <sup> works
there". Here it is again with the proper changes.

[jnj, 2012-03-18 19:45:35]

Hello golang-dev@googlegroups.com, r@golang.org, r@google.com (cc:
golang-dev@googlegroups.com),

Please take another look.

[r, 2012-03-18 21:26:15]

LGTM
thanks

[r, 2012-03-18 21:26:42]

*** Submitted as http://code.google.com/p/go/source/detail?r=0a5692d60e01 ***

doc: various typos, remove apostrophes from ordinals

R=golang-dev, r, r
CC=golang-dev
http://codereview.appspot.com/5845059

Committer: Rob Pike <r@golang.org>