design/24543: clarify use of signal for stack/reg maps
Change-Id: I0322e2bdcd5e12394e411e9ed8d127c4208c504f
Reviewed-on: https://go-review.googlesource.com/c/161537
Reviewed-by: Keith Randall <khr@golang.org>
diff --git a/design/24543/safe-points-everywhere.md b/design/24543/safe-points-everywhere.md
index 85e7f80..ad9053f 100644
--- a/design/24543/safe-points-everywhere.md
+++ b/design/24543/safe-points-everywhere.md
@@ -29,8 +29,8 @@
addition to stack maps, and to emit these for as many program counters
as possible.
The runtime would use a signal (or `GetThreadContext` on Windows, or a
-note on Plan9) to retrieve each thread's register state, including the
-stack and register map at the interrupted PC.
+note on Plan9) to retrieve each thread's register state, from which it
+could get the stack and register map for the interrupted PC.
The garbage collector would then treat live pointers in registers just
as it treats live pointers on the stack.
