Skip to content

Commit af91463

Browse files
committed
design: fix typos in 14313
Change-Id: Ifb9581f666364c000ede43a5cf63a83a7606bc16 Reviewed-on: https://go-review.googlesource.com/19491 Reviewed-by: Russ Cox <[email protected]>
1 parent 0358604 commit af91463

File tree

1 file changed

+3
-2
lines changed

1 file changed

+3
-2
lines changed

design/14313-benchmark-format.md

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ and likely more unpublished programs.
6868

6969
### Benchmark runners
7070

71-
Multiple tools have also been written that process this format.
71+
Multiple tools have also been written that generate this format.
7272
In addition to the standard Go testing package,
7373
[compilebench](https://godoc.org/rsc.io/compilebench)
7474
generates this data format based on runs of the Go compiler,
@@ -93,7 +93,7 @@ have semantic meaning in the reporting of benchmark results.
9393
All other lines in the data file, including but not limited to
9494
blank lines and lines beginning with a # character, are ignored.
9595
For example, the testing package prints test results above benchmark data,
96-
usually the text `PASS`. that line is neither a configuration line nor a benchmark
96+
usually the text `PASS`. That line is neither a configuration line nor a benchmark
9797
result line, so it is ignored.
9898

9999
### Configuration Lines
@@ -106,6 +106,7 @@ where key contains no space characters (as defined by `unicode.IsSpace`)
106106
nor upper case characters (as defined by `unicode.IsUpper`),
107107
and space characters separate “key:” from “value.”
108108
Conventionally, multiword keys are written with the words
109+
separated by hyphens, as in cpu-speed.
109110
There are no restrictions on value, except that it cannot contain a newline character.
110111
Value can be omitted entirely but the colon must still be present.
111112

0 commit comments

Comments
 (0)