From 9cb3c47ebadcf8cab8b396711d59631751fb61d5 Mon Sep 17 00:00:00 2001
From: Jason Mulligan <jason.mulligan@avoidwork.com>
Date: Mon, 10 Apr 2017 07:39:43 -0400
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index c298fe6..034c483 100644
--- a/README.md
+++ b/README.md
@@ -64,7 +64,7 @@ Terminates the `Worker`
 ## FAQ
 1. I have an orphaned child process that lives on past the parent process' lifespan
   * Most likely a `SIGTERM` or `SIGINT` is not reaching the child process
-2. How do insure all process are terminated?
+2. How do I insure all process are terminated?
   * In your core script register a listener for `SIGTERM` or `SIGINT` via `process.on()` which terminates (all) worker process(es) and then gracefully shutdowns via `process.exit(0);`
 3. Why `SIGTERM` or `SIGINT`?
   * Unix/BSD will work with `SIGTERM`, but if you also need to support Windows use `SIGINT`
-- 
GitLab