Brad Fitzpatrick 5fea2ccc77 all: single space after period. ... The tree's pretty inconsistent about single space vs double space after a period in documentation. Make it consistently a single space, per earlier decisions. This means contributors won't be confused by misleading precedence. This CL doesn't use go/doc to parse. It only addresses // comments. It was generated with: $ perl -i -npe 's,^(\s*// .+[a-z]\.) +([A-Z]),$1 $2,' $(git grep -l -E '^\s*//(.+\.) +([A-Z])') $ go test go/doc -update Change-Id: Iccdb99c37c797ef1f804a94b22ba5ee4b500c4f7 Reviewed-on: https://go-review.googlesource.com/20022 Reviewed-by: Rob Pike <r@golang.org> Reviewed-by: Dave Day <djd@golang.org> Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org> TryBot-Result: Gobot Gobot <gobot@golang.org>		2016-03-02 00:13:47 +00:00
..
iotest	all: single space after period.	2016-03-02 00:13:47 +00:00
quick	all: single space after period.	2016-03-02 00:13:47 +00:00
allocs.go	all: single space after period.	2016-03-02 00:13:47 +00:00
allocs_test.go	all: make copyright headers consistent with one space after period	2016-03-01 23:34:33 +00:00
benchmark.go	all: single space after period.	2016-03-02 00:13:47 +00:00
benchmark_test.go	…
cover.go	…
example.go	testing: make the output of -v more uniform and aligned when using fixed-width fonts	2015-05-08 18:38:25 +00:00
export_test.go	…
testing.go	all: single space after period.	2016-03-02 00:13:47 +00:00
testing_test.go	all: make copyright headers consistent with one space after period	2016-03-01 23:34:33 +00:00