os/signal: clarify that non-Go thread may change signal mask

Fixes #67773

Change-Id: I05c9934a5b2719d22884c8546f4fadaa9978ac67
Reviewed-on: https://go-review.googlesource.com/c/go/+/589755
Auto-Submit: Ian Lance Taylor <iant@golang.org>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Commit-Queue: Ian Lance Taylor <iant@google.com>
Reviewed-by: Michael Pratt <mpratt@google.com>
Reviewed-by: Ian Lance Taylor <iant@google.com>
Auto-Submit: Ian Lance Taylor <iant@google.com>

diff --git a/src/os/signal/doc.go b/src/os/signal/doc.go
index 07ed9ce524ebc6c99f634dde498d99f7a1b37933..900704a1a9937dbbd8b6543db0ef3b2ad63e75ac 100644 (file)
--- a/src/os/signal/doc.go
+++ b/src/os/signal/doc.go
@@ -146,8 +146,8 @@ Go behavior described above will not occur. This can be an issue with
 the SIGPROF signal in particular.
 
 The non-Go code should not change the signal mask on any threads
-created by the Go runtime. If the non-Go code starts new threads of
-its own, it may set the signal mask as it pleases.
+created by the Go runtime. If the non-Go code starts new threads
+itself, those threads may set the signal mask as they please.
 
 If the non-Go code starts a new thread, changes the signal mask, and
 then invokes a Go function in that thread, the Go runtime will