[gentoo-catalyst] [PATCH] Fix mis-spelling of 'received' in chroot-functions.sh

[M. J. Everitt]

From 58119dd43d6c1f28a6c0dd935a262d9da8e941b4 Mon Sep 17 00:00:00 2001
From: Michael Everitt <m.j.everitt@×××.org>
Date: Sun, 9 Sep 2018 18:17:27 +0100
Subject: [PATCH] Fix mis-spelling of 'received' in chroot-functions.sh

---
 targets/support/chroot-functions.sh | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/targets/support/chroot-functions.sh
b/targets/support/chroot-functions.sh
index 84d90fe..ceef21c 100755
--- a/targets/support/chroot-functions.sh
+++ b/targets/support/chroot-functions.sh
@@ -3,19 +3,19 @@
 # Set the profile
 eselect profile set ${clst_target_profile}
 -# Trap these signals and kill ourselves if recieved
-# Force ourselves to die if any of these signals are recieved
+# Trap these signals and kill ourselves if received
+# Force ourselves to die if any of these signals are received
 # most likely our controlling terminal is gone
-trap "echo SIGTERM signal recieved killing $0 with pid $$;kill -9 $$"
SIGTERM
-trap "echo SIGHUP signal recieved killing $0 with pid $$;kill -9 $$" SIGHUP
-trap "echo SIGKILL signal recieved killing $0 with pid $$;kill -9 $$"
SIGKILL
+trap "echo SIGTERM signal received killing $0 with pid $$;kill -9 $$"
SIGTERM
+trap "echo SIGHUP signal received killing $0 with pid $$;kill -9 $$" SIGHUP
+trap "echo SIGKILL signal received killing $0 with pid $$;kill -9 $$"
SIGKILL
  #SIGINT interrupt character (usually Ctrl-C)
 #	* example: high-level sequence of events
 #	* my process (call it "P") is running
 #	* user types ctrl-c
 #	* kernel recognizes this and generates SIGINT signal
-trap "echo SIGINT signal recieved killing $0 with pid $$;kill -9 $$" SIGINT
+trap "echo SIGINT signal received killing $0 with pid $$;kill -9 $$" SIGINT
  # test if CHOST was set on the python side
 if [[ -z "${clst_CHOST}" ]] ; then
-- 
2.13.6