content: write real summary for each article

The pre-Markdown blog invented a summary by copying
the first paragraph of text. Often this was nonsense or
at least useless.

The new Markdown-enabled present format adds an
explicit Summary line. The conversion populated these
with the same first paragraph that the old format would
have used implicitly.

This commit rewrites them all to be proper short summaries.

Change-Id: If2e1e101b95558d7ecd53c613f733a7f89c680f1
Reviewed-on: https://go-review.googlesource.com/c/blog/+/223598
Run-TryBot: Russ Cox <rsc@golang.org>
Reviewed-by: Andrew Bonventre <andybons@golang.org>

1 files changed, 1 insertions, 1 deletions

diff --git a/content/go-concurrency-patterns-timing-out-and.article b/content/go-concurrency-patterns-timing-out-and.article
index 09d2502..9bdc565 100644
--- a/content/go-concurrency-patterns-timing-out-and.article
+++ b/content/go-concurrency-patterns-timing-out-and.article
@@ -1,7 +1,7 @@
 # Go Concurrency Patterns: Timing out, moving on
 23 Sep 2010
 Tags: concurrency, technical
-Summary: Concurrent programming has its own idioms. A good example is timeouts. Although Go's channels do not support them directly, they are easy to implement. Say we want to receive from the channel `ch`, but want to wait at most one second for the value to arrive. We would start by creating a signalling channel and launching a goroutine that sleeps before sending on the channel:
+Summary: How to implement timeouts using Go's concurrency support.
 
 Andrew Gerrand