design: fix minor typos in percpu.Sharded proposal
Change-Id: I28fe6008527eae926350165baa9f1734461ba800
GitHub-Last-Rev: 632f9a4e46d297919d5b4d9debbbacbca6bfd77e
GitHub-Pull-Request: golang/proposal#14
Reviewed-on: https://go-review.googlesource.com/118537
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
diff --git a/design/18802-percpu-sharded.md b/design/18802-percpu-sharded.md
index 69347e4..902d735 100644
--- a/design/18802-percpu-sharded.md
+++ b/design/18802-percpu-sharded.md
@@ -1,4 +1,4 @@
-# Proposal: percpu.Sharder, an API for reducing cache contention
+# Proposal: percpu.Sharded, an API for reducing cache contention
Discussion at https://golang.org/issue/18802
@@ -110,8 +110,8 @@
// A Sharded is a container of homogenously typed values.
//
// On a best effort basis, the runtime will strongly associate a given value
-// with a CPU core. That is to say, retrieving a value twice on the CPU core
-// will return the same value with high probablity. Note that the runtime
+// with a CPU core. That is to say, retrieving a value twice on the same CPU
+// core will return the same value with high probablity. Note that the runtime
// cannot guarantee this fact, and clients must assume that retrieved values
// can be shared between concurrently executing goroutines.
//
