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

---
 README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 9cc423b..1618706 100644
--- a/README.md
+++ b/README.md
@@ -63,9 +63,11 @@ Terminates the `Worker`
 
 ## FAQ
 1. I have an orphaned child process that lives on past the parent process' lifespan
-  * Most likely a `SIGTERM` is not reaching the child process
+  * Most likely a `SIGTERM` or `SIGINT` is not reaching the child process
 2. How do insure all process are terminated?
-  * In your core script register a listener for `SIGTERM` via `process.on()` which terminates (all) worker process(es) and then gracefully shutdowns via `process.exit(0);`
+  * 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`
 
 ## License
 Copyright (c) 2015 Jason Mulligan
-- 
GitLab