From 4f4b2169a3f376c077e0bfd42947010c5b7ddea8 Mon Sep 17 00:00:00 2001 From: Mark McGranaghan Date: Wed, 22 Jan 2014 15:49:28 -0800 Subject: [PATCH] Rebuild --- examples/signals/signals.hash | 4 ++-- public/signals | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/examples/signals/signals.hash b/examples/signals/signals.hash index f5a3787..b445924 100644 --- a/examples/signals/signals.hash +++ b/examples/signals/signals.hash @@ -1,2 +1,2 @@ -42ec8f6064228f89f97e2798150d741317d2bf05 -d42wO1q1oh +9720d747e3ab2893df508a70cbb341c90fdd7ca1 +BlkqAtKsxo diff --git a/public/signals b/public/signals index e7b5272..7a1b2d0 100644 --- a/public/signals +++ b/public/signals @@ -25,7 +25,7 @@ -

Sometines we’d like our Go programs to intelligently +

Sometimes we’d like our Go programs to intelligently handle Unix signals. For example, we might want a server to gracefully shutdown when it receives a SIGTERM, or a command-line @@ -44,7 +44,7 @@ Here’s how to handle signals in Go with channels.

- + 
package main
@@ -83,7 +83,7 @@ Here’s how to handle signals in Go with channels.

Go signal notification works by sending os.Signal values on a channel. We’ll create a channel to receive these notifications (we’ll also make one to -notify us when the program can exit.)

+notify us when the program can exit).