diff options
| -rw-r--r-- | _content/blog/allocation-optimizations.md | 2 | ||||
| -rw-r--r-- | _content/blog/testing-time.md | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/_content/blog/allocation-optimizations.md b/_content/blog/allocation-optimizations.md index 507541da..d69e4ced 100644 --- a/_content/blog/allocation-optimizations.md +++ b/_content/blog/allocation-optimizations.md @@ -287,7 +287,7 @@ operated on a stack-backed slice up to the return point. We do pay the cost for a copy, but that cost is almost completely offset by the copies in the startup phase that we no longer have to -do. (In fact, the the new scheme at worst has to copy one more element +do. (In fact, the new scheme at worst has to copy one more element than the old scheme.) ## Wrapping up diff --git a/_content/blog/testing-time.md b/_content/blog/testing-time.md index 387f925b..6b18c956 100644 --- a/_content/blog/testing-time.md +++ b/_content/blog/testing-time.md @@ -360,7 +360,7 @@ So we asked ourselves what we can do to make this better. As we saw earlier, the two fundamental features required to write testable concurrent code are fake time and a way to wait for quiescence. -We need a better way to to wait for quiescence. +We need a better way to wait for quiescence. We should be able to ask the runtime when background goroutines have finished their work. We also want to be able to limit the scope of this query to a single test, so that unrelated tests do not interfere with each other. |