From 012faccf040344360801b0fa77e85f9c8a3a4b2c Mon Sep 17 00:00:00 2001
From: eregon <eregon@b2dd03c8-39d4-4d8f-98ff-823fe69b080e>
Date: Sun, 7 Apr 2019 11:26:27 +0000
Subject: [PATCH] doc/signals.rdoc: Clarify a bit where Signal.trap handlers
 are executed

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@67465 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
---
 doc/signals.rdoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/signals.rdoc b/doc/signals.rdoc
index fdd9206afb..403eb66549 100644
--- a/doc/signals.rdoc
+++ b/doc/signals.rdoc
@@ -18,7 +18,7 @@ for data structures in YOUR code.  Ruby implements deferred signal
 handling by registering short C functions with only
 {async-signal-safe functions}[http://man7.org/linux/man-pages/man7/signal-safety.7.html] as
 signal handlers.  These short C functions only do enough tell the VM to
-run callbacks registered via Signal.trap later in the main VM loop.
+run callbacks registered via Signal.trap later in the main Ruby Thread.
 
 == Unsafe methods to call in Signal.trap blocks