From 66e5dad9d41e5e93a4985a09daa08a61e02ae2d9 Mon Sep 17 00:00:00 2001 From: kraem Date: Wed, 15 Jan 2020 11:02:44 +0000 Subject: content: fix typo in share-memory-by-communicating.article Change-Id: Iaece9dd6f465fe9538cc11653df4572616b23f4c GitHub-Last-Rev: 7ace8e3ed0a3276e7333baa421e3990a2fc62754 GitHub-Pull-Request: golang/blog#28 Reviewed-on: https://go-review.googlesource.com/c/blog/+/214860 Reviewed-by: Ian Lance Taylor --- content/share-memory-by-communicating.article | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/share-memory-by-communicating.article b/content/share-memory-by-communicating.article index 2d9e77a..bd3a37e 100644 --- a/content/share-memory-by-communicating.article +++ b/content/share-memory-by-communicating.article @@ -76,4 +76,4 @@ Let's take a look at the same functionality implemented using Go idiom. In this The delicate logic from the previous example is conspicuously absent, and our Resource data structure no longer contains bookkeeping data. In fact, all that's left are the important parts. This should give you an inkling as to the power of these simple language features. -There are many omissions from the above code snippets. For a walkthrough of a complete, idiomatic Go program that uses these ides, see the Codewalk [[https://golang.org/doc/codewalk/sharemem/][_Share_Memory_By_Communicating_]]. +There are many omissions from the above code snippets. For a walkthrough of a complete, idiomatic Go program that uses these ideas, see the Codewalk [[https://golang.org/doc/codewalk/sharemem/][_Share_Memory_By_Communicating_]]. -- cgit v1.2.3