From 5ea676bd4bf5f7215fbc59b28a0a6db6277512e0 Mon Sep 17 00:00:00 2001 From: Jon Skeet Date: Thu, 17 Aug 2023 16:59:30 +0100 Subject: [PATCH] Fix lock statement reference --- standard/classes.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/standard/classes.md b/standard/classes.md index ff1c9103f..1c99fcb75 100644 --- a/standard/classes.md +++ b/standard/classes.md @@ -3897,7 +3897,7 @@ Within the program text of the class or struct that contains the declaration of > > *end example* -When compiling a field-like event, the compiler automatically creates storage to hold the delegate, and creates accessors for the event that add or remove event handlers to the delegate field. The addition and removal operations are thread safe, and may (but are not required to) be done while holding the lock ([§9.4.4.19](variables.md#94419-lock-statements)) in the containing object for an instance event, or the `System.Type` object ([§12.8.17](expressions.md#12817-the-typeof-operator)) for a static event. +When compiling a field-like event, the compiler automatically creates storage to hold the delegate, and creates accessors for the event that add or remove event handlers to the delegate field. The addition and removal operations are thread safe, and may (but are not required to) be done while holding the lock ([§13.13](statements.md#1313-the-lock-statement)) on the containing object for an instance event, or the `System.Type` object ([§12.8.17](expressions.md#12817-the-typeof-operator)) for a static event. > *Note*: Thus, an instance event declaration of the form: >