RangefuncExperiment: fix typo
Change-Id: I3df8210e7b8debd5de9ce3c4e5df8883bdb0596a
GitHub-Last-Rev: e95196639e18922fa82abbe60a7016b21bc77fdf
GitHub-Pull-Request: golang/wiki#15
Reviewed-on: https://go-review.googlesource.com/c/wiki/+/577335
Reviewed-by: Ian Lance Taylor <iant@golang.org>
Auto-Submit: Ian Lance Taylor <iant@golang.org>
Commit-Queue: Ian Lance Taylor <iant@golang.org>
diff --git a/RangefuncExperiment.md b/RangefuncExperiment.md
index d141fcb..2be91fe 100644
--- a/RangefuncExperiment.md
+++ b/RangefuncExperiment.md
@@ -282,5 +282,5 @@
Running the iterator in a separate coroutine or goroutine is more expensive and harder to debug than having everything on one stack. Since we're going to have everything on one stack, that fact will change certain visible details. We just saw the first: stack traces show the calling function and the iterator function interleaved, as well as showing the explicit yield function that does not exist on the page in the program.
-It can be helpful to think about running the iterator function in its own coroutine or gorotine as an analogy or mental model, but in some cases the mental model doesn't give the best answer, because it uses two stacks, and the real implementation is defined to use one.
+It can be helpful to think about running the iterator function in its own coroutine or goroutine as an analogy or mental model, but in some cases the mental model doesn't give the best answer, because it uses two stacks, and the real implementation is defined to use one.
