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

Co-authored-by: BillWagner <493969+BillWagner@users.noreply.github.com>

Author: github-actions[bot]

standard/README.md

@@ -650,6 +650,8 @@
     - [§16.2.5](structs.md#1625-struct-interfaces)  Struct interfaces
     - [§16.2.6](structs.md#1626-struct-body)  Struct body
   - [§16.3](structs.md#163-struct-members)  Struct members
+    - [§16.3.1](structs.md#1631-general)  General
+    - [§16.3.2](structs.md#1632-readonly-members)  Readonly members
   - [§16.4](structs.md#164-class-and-struct-differences)  Class and struct differences
     - [§16.4.1](structs.md#1641-general)  General
     - [§16.4.2](structs.md#1642-value-semantics)  Value semantics

standard/conversions.md

@@ -722,7 +722,7 @@ A user-defined explicit conversion from an expression `E` to a type `T` is pro
   - Otherwise, the conversion is ambiguous and a compile-time error occurs.
 - Finally, determine the runtime conversions required, in order:
   - If `E` does not already have the type `Sₓ`, then a standard explicit conversion from `E` to `Sₓ` is required.
-    - If this added standard explicit conversion is an explicit numeric (§10.3.2) or enumeration (§10.3.3) one which may result in information loss (§10.3.2), and the context is `unchecked` (§12.8.20, §13.12), then a compile-time warning shall be issued.<br>*Note*: In a `checked` context information loss would result in a runtime exception, hence no warning is required. If information loss is intended adding an explicit cast to the source will document this and silence the warning. *end note*
+    - If this added standard explicit conversion is an explicit numeric ([§10.3.2](conversions.md#1032-explicit-numeric-conversions)) or enumeration ([§10.3.3](conversions.md#1033-explicit-enumeration-conversions)) one which may result in information loss ([§10.3.2](conversions.md#1032-explicit-numeric-conversions)), and the context is `unchecked` ([§12.8.20](expressions.md#12820-the-checked-and-unchecked-operators), [§13.12](statements.md#1312-the-checked-and-unchecked-statements)), then a compile-time warning shall be issued.<br>*Note*: In a `checked` context information loss would result in a runtime exception, hence no warning is required. If information loss is intended adding an explicit cast to the source will document this and silence the warning. *end note*
   - The most-specific user-defined conversion operator is required to convert from `Sₓ` to `Tₓ`.
   - If `Tₓ` is not `T`, then a standard explicit conversion from `Tₓ` to `T` is required.
 

standard/grammar.md

@@ -2175,7 +2175,7 @@ ref_method_modifier
     | 'override'
     | 'abstract'
     | 'extern'
-    | 'readonly'        // direct struct members only
+    | 'readonly'        // struct members only
     | unsafe_modifier   // unsafe code support
     ;
 
@@ -2259,7 +2259,7 @@ property_modifier
     | 'override'
     | 'abstract'
     | 'extern'
-    | 'readonly'        // direct struct members only
+    | 'readonly'        // struct members only
     | unsafe_modifier   // unsafe code support
     ;
     
@@ -2299,7 +2299,7 @@ accessor_modifier
     | 'internal' 'protected'
     | 'protected' 'private'
     | 'private' 'protected'
-    | 'readonly'        // direct struct members only
+    | 'readonly'        // struct members only
     ;
 
 accessor_body
@@ -2337,7 +2337,7 @@ event_modifier
     | 'override'
     | 'abstract'
     | 'extern'
-    | 'readonly'        // direct struct members only
+    | 'readonly'        // struct members only
     | unsafe_modifier   // unsafe code support
     ;
 
@@ -2371,7 +2371,7 @@ indexer_modifier
     | 'override'
     | 'abstract'
     | 'extern'
-    | 'readonly'        // direct struct members only
+    | 'readonly'        // struct members only
     | unsafe_modifier   // unsafe code support
     ;
 
@@ -2535,7 +2535,7 @@ struct_body
     : '{' struct_member_declaration* '}'
     ;
 
-// Source: §16.3 Struct members
+// Source: §16.3.1 General
 struct_member_declaration
     : constant_declaration
     | field_declaration

standard/structs.md

@@ -114,7 +114,7 @@ struct_body
 
 ## 16.3 Struct members
 
-### §struct_general General
+### 16.3.1 General
 
 The members of a struct consist of the members introduced by its *struct_member_declaration*s and the members inherited from the type `System.ValueType`.
 
@@ -140,20 +140,20 @@ struct_member_declaration
 
 Except for the differences noted in [§16.4](structs.md#164-class-and-struct-differences), the descriptions of class members provided in [§15.3](classes.md#153-class-members) through [§15.12](classes.md#1512-static-constructors) apply to struct members as well.
 
-### §struct_readonly Readonly members
+### 16.3.2 Readonly members
 
 An instance member definition or accessor of an instance property, indexer, or event that includes the `readonly` modifier has the following restrictions:
 
 - The `this` parameter is a `ref readonly` reference.
 - The member shall not reassign the value of `this` or an instance field of the receiver.
-- The member shall not reassign the value of an instance field-like event (§15.8.2) of the receiver.
+- The member shall not reassign the value of an instance field-like event ([§15.8.2](classes.md#1582-field-like-events)) of the receiver.
 - If a readonly member invokes a non-readonly member, the structure referred to by `this` must be copied to use a writable reference for the `this` argument.
 
-> *Note:* Instance fields include the hidden backing field used for automatically implemented properties (§15.7.4). *end note*
+> *Note:* Instance fields include the hidden backing field used for automatically implemented properties ([§15.7.4](classes.md#1574-automatically-implemented-properties)). *end note*
 <!-- markdownlint-disable MD028 -->
 
 <!-- markdownlint-enable MD028 -->
-> *Example*: A readonly member can modify the state of an object referred to by an instance field, even though the readonly member can't reassign that instance member. The following code demonstrates the reassigning and modifying an instance field:
+> *Example*: A readonly member can modify the state of an object referred to by an instance field, even though the readonly member can’t reassign that instance member. The following code demonstrates the reassigning and modifying an instance field:
 >
 > <!-- Example: {template:"standalone-lib-without-using", name:"ReadonlyMember" } -->
 > ```csharp