From d09734610c7ae33b3da49d9ff41ea79805cf5cfa Mon Sep 17 00:00:00 2001 From: Mark McGranaghan Date: Thu, 11 Oct 2012 11:03:13 -0700 Subject: [PATCH] fixed #4 --- examples/signals/signals.sh | 2 +- examples/spawning-processes/spawning-processes.go | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/examples/signals/signals.sh b/examples/signals/signals.sh index 9e5ff96..6fd2581 100644 --- a/examples/signals/signals.sh +++ b/examples/signals/signals.sh @@ -1,6 +1,6 @@ # When we run this program it will block waiting for a # signal. By typing `ctrl-C` (which the -# terminal shows as `^C`) we cand send a `SIGNIT` signal, +# terminal shows as `^C`) we cand send a `SIGINT` signal, # causing the program to print `interrupt` and then exit. $ go run signals.go awaiting signal diff --git a/examples/spawning-processes/spawning-processes.go b/examples/spawning-processes/spawning-processes.go index 26b1110..b7b708a 100644 --- a/examples/spawning-processes/spawning-processes.go +++ b/examples/spawning-processes/spawning-processes.go @@ -56,7 +56,7 @@ func main() { fmt.Println(string(grepBytes)) // Note that when spawning commands we need to - // provide an explicitly deliniated command and + // provide an explicitly delineated command and // argument array, vs. being able to just pass in one // command line string. If you want to spawn a full // command with a string, you can use `bash`'s `-c`