[create-pull-request] automated change (#1626)

Co-authored-by: jskeet <17011+jskeet@users.noreply.github.com>

Author: github-actions[bot]

standard/README.md

@@ -102,6 +102,9 @@
     - [§8.3.9](types.md#839-the-bool-type)  The Bool type
     - [§8.3.10](types.md#8310-enumeration-types)  Enumeration types
     - [§8.3.11](types.md#8311-tuple-types)  Tuple types
+      - [§8.3.11.1](types.md#83111-general)  General
+      - [§8.3.11.2](types.md#83112-eliding-intermediate-tuple-creation)  Eliding intermediate tuple creation
+      - [§8.3.11.3](types.md#83113-runtime-representation)  Runtime representation
     - [§8.3.12](types.md#8312-nullable-value-types)  Nullable value types
     - [§8.3.13](types.md#8313-boxing-and-unboxing)  Boxing and unboxing
   - [§8.4](types.md#84-constructed-types)  Constructed types
@@ -175,7 +178,7 @@
       - [§9.4.4.22](variables.md#94422-general-rules-for-simple-expressions)  General rules for simple expressions
       - [§9.4.4.23](variables.md#94423-general-rules-for-expressions-with-embedded-expressions)  General rules for expressions with embedded expressions
       - [§9.4.4.24](variables.md#94424-invocation-expressions-and-object-creation-expressions)  Invocation expressions and object creation expressions
-      - [§9.4.4.25](variables.md#94425-simple-assignment-expressions)  Simple assignment expressions
+      - [§9.4.4.25](variables.md#94425-simple-and-deconstructing-assignment-expressions)  Simple and deconstructing assignment expressions
       - [§9.4.4.26](variables.md#94426--expressions)  && expressions
       - [§9.4.4.27](variables.md#94427--expressions)  || expressions
       - [§9.4.4.28](variables.md#94428--expressions)  ! expressions
@@ -450,9 +453,12 @@
   - [§12.23](expressions.md#1223-assignment-operators)  Assignment operators
     - [§12.23.1](expressions.md#12231-general)  General
     - [§12.23.2](expressions.md#12232-simple-assignment)  Simple assignment
-    - [§12.23.3](expressions.md#12233-ref-assignment)  Ref assignment
-    - [§12.23.4](expressions.md#12234-compound-assignment)  Compound assignment
-    - [§12.23.5](expressions.md#12235-event-assignment)  Event assignment
+    - [§12.23.3](expressions.md#12233-deconstructing-assignment)  Deconstructing assignment
+      - [§12.23.3.1](expressions.md#122331-general)  General
+      - [§12.23.3.2](expressions.md#122332-abridged-deconstructors)  Abridged deconstructors
+    - [§12.23.4](expressions.md#12234-ref-assignment)  Ref assignment
+    - [§12.23.5](expressions.md#12235-compound-assignment)  Compound assignment
+    - [§12.23.6](expressions.md#12236-event-assignment)  Event assignment
   - [§12.24](expressions.md#1224-expression)  Expression
   - [§12.25](expressions.md#1225-constant-expressions)  Constant expressions
   - [§12.26](expressions.md#1226-boolean-expressions)  Boolean expressions

standard/classes.md

@@ -3851,7 +3851,7 @@ Once a particular non-ref-valued property or non-ref-valued indexer has been sel
 
 - If the usage is as a value ([§12.2.2](expressions.md#1222-values-of-expressions)), the get accessor shall exist and be accessible.
 - If the usage is as the target of a simple assignment ([§12.23.2](expressions.md#12232-simple-assignment)), the set accessor shall exist and be accessible.
-- If the usage is as the target of compound assignment ([§12.23.4](expressions.md#12234-compound-assignment)), or as the target of the `++` or `--` operators ([§12.8.16](expressions.md#12816-postfix-increment-and-decrement-operators), [§12.9.7](expressions.md#1297-prefix-increment-and-decrement-operators)), both the get accessors and the set accessor shall exist and be accessible.
+- If the usage is as the target of compound assignment ([§12.23.5](expressions.md#12235-compound-assignment)), or as the target of the `++` or `--` operators ([§12.8.16](expressions.md#12816-postfix-increment-and-decrement-operators), [§12.9.7](expressions.md#1297-prefix-increment-and-decrement-operators)), both the get accessors and the set accessor shall exist and be accessible.
 
 > *Example*: In the following example, the property `A.Text` is hidden by the property `B.Text`, even in contexts where only the set accessor is called. In contrast, the property `B.Count` is not accessible to class `M`, so the accessible property `A.Count` is used instead.
 >
@@ -4101,7 +4101,7 @@ An event can be used as the left operand of the `+=` and `-=` operators. These
 
 The only operations that are permitted on an event by code that is outside the type in which that event is declared, are `+=` and `-=`. Therefore, while such code can add and remove handlers for an event, it cannot directly obtain or modify the underlying list of event handlers.
 
-In an operation of the form `x += y` or `x –= y`, when `x` is an event the result of the operation has type `void` ([§12.23.5](expressions.md#12235-event-assignment)) (as opposed to having the type of `x`, with the value of `x` after the assignment, as for other the `+=` and `-=` operators defined on non-event types). This prevents external code from indirectly examining the underlying delegate of an event.
+In an operation of the form `x += y` or `x –= y`, when `x` is an event the result of the operation has type `void` ([§12.23.6](expressions.md#12236-event-assignment)) (as opposed to having the type of `x`, with the value of `x` after the assignment, as for other the `+=` and `-=` operators defined on non-event types). This prevents external code from indirectly examining the underlying delegate of an event.
 
 > *Example*: The following example shows how event handlers are attached to instances of the `Button` class:
 >

standard/conversions.md

@@ -402,7 +402,7 @@ The following conversions are classified as explicit conversions:
 - Explicit nullable conversions ([§10.3.4](conversions.md#1034-explicit-nullable-conversions))
 - Explicit tuple conversions ([§10.3.6](conversions.md#1036-explicit-tuple-conversions))
 - Explicit reference conversions ([§10.3.5](conversions.md#1035-explicit-reference-conversions))
-- Explicit interface conversions (§10.3.5)
+- Explicit interface conversions ([§10.3.5](conversions.md#1035-explicit-reference-conversions))
 - Unboxing conversions ([§10.3.7](conversions.md#1037-unboxing-conversions))
 - Explicit type parameter conversions ([§10.3.8](conversions.md#1038-explicit-conversions-involving-type-parameters))
 - User-defined explicit conversions ([§10.3.9](conversions.md#1039-user-defined-explicit-conversions))

standard/delegates.md

@@ -214,7 +214,7 @@ The set of methods encapsulated by a delegate instance is called an *invocation
 
 When a new delegate is created from a single delegate the resultant invocation list has just one entry, which is the source delegate ([§12.8.17.5](expressions.md#128175-delegate-creation-expressions)).
 
-Delegates are combined using the binary `+` ([§12.12.5](expressions.md#12125-addition-operator)) and `+=` operators ([§12.23.4](expressions.md#12234-compound-assignment)). A delegate can be removed from a combination of delegates, using the binary `-` ([§12.12.6](expressions.md#12126-subtraction-operator)) and `-=` operators ([§12.23.4](expressions.md#12234-compound-assignment)). Delegates can be compared for equality ([§12.14.9](expressions.md#12149-delegate-equality-operators)).
+Delegates are combined using the binary `+` ([§12.12.5](expressions.md#12125-addition-operator)) and `+=` operators ([§12.23.5](expressions.md#12235-compound-assignment)). A delegate can be removed from a combination of delegates, using the binary `-` ([§12.12.6](expressions.md#12126-subtraction-operator)) and `-=` operators ([§12.23.5](expressions.md#12235-compound-assignment)). Delegates can be compared for equality ([§12.14.9](expressions.md#12149-delegate-equality-operators)).
 
 > *Example*: The following example shows the instantiation of a number of delegates, and their corresponding invocation lists:
 >