_content/doc/go1.26: fix typo in WithDataIndependentTiming doc For golang/go#75005 Change-Id: Iab27e2227f81759f1c2912ad2f09a8375050214e Reviewed-on: https://go-review.googlesource.com/c/website/+/741242 Reviewed-by: Ian Lance Taylor <iant@golang.org> LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com> Reviewed-by: Dmitri Shuralyov <dmitshur@google.com> Auto-Submit: Rhys Hiltner <rhys.hiltner@gmail.com> Auto-Submit: Michael Knyszek <mknyszek@google.com> Reviewed-by: Michael Knyszek <mknyszek@google.com>
diff --git a/_content/doc/go1.26.md b/_content/doc/go1.26.md index a12c30e..706112e 100644 --- a/_content/doc/go1.26.md +++ b/_content/doc/go1.26.md
@@ -416,13 +416,13 @@ The [`WithDataIndependentTiming`](/pkg/crypto/subtle#WithDataIndependentTiming) function no longer locks the calling goroutine to the OS thread while executing the passed function. Additionally, any goroutines which are spawned during the -executed of the passed function and their descendents now inherit the properties of +execution of the passed function and their descendants now inherit the properties of WithDataIndependentTiming for their lifetime. This change also affects cgo in the following ways: - Any C code called via cgo from within the function passed to WithDataIndependentTiming, or from a goroutine spawned by the function passed - to WithDataIndependentTiming and its descendents, will also have data + to WithDataIndependentTiming and its descendants, will also have data independent timing enabled for the duration of the call. If the C code disables data independent timing, it will be re-enabled on return to Go. - If C code called via cgo, from the function passed to