Documentation update

Author: github-actions

docs/migrations/migration8/index.html

@@ -67,7 +67,7 @@ <h2 id="overview" style="position:relative;"><a href="#overview" aria-label="ove
 <li><code class="language-text">ComplexScalarGraphType</code> added, allowing flexible input/output types</li>
 <li><code class="language-text">IMetadataWriter</code> and similar interfaces added to allow better intellisense</li>
 <li>List converter enhancements and AOT support</li>
-<li>OneOf Input Object support (based on draft spec)</li>
+<li>OneOf Input Object support</li>
 <li>Infer nullability by default for <code class="language-text">Field</code> methods</li>
 <li>Add Persisted Document support (based on draft spec)</li>
 <li>Better error handling of GraphQL.NET pipeline; add timeout support</li>
@@ -575,16 +575,13 @@ <h3 id="16-oneof-input-object-support-added" style="position:relative;"><a href=
 asserts that exactly one of the fields must be set and non-null, all others
 being omitted. This is useful for representing situations where an input may be
 one of many different options.</p>
-<p>See: <a href="https://github.com/graphql/graphql-spec/pull/825">https://github.com/graphql/graphql-spec/pull/825</a></p>
+<p>See: <a href="https://spec.graphql.org/draft/#sec-OneOf-Input-Objects">https://spec.graphql.org/draft/#sec-OneOf-Input-Objects</a></p>
 <p>To use this feature:</p>
 <ul>
 <li><strong>Code-First</strong>: Set the <code class="language-text">IsOneOf</code> property on your <code class="language-text">InputObjectGraphType</code> to <code class="language-text">true</code>.</li>
 <li><strong>Schema-First</strong>: Use the <code class="language-text">@oneOf</code> directive on the input type in your schema definition.</li>
 <li><strong>Type-First</strong>: Use the <code class="language-text">[OneOf]</code> directive on the CLR class.</li>
 </ul>
-<p>Note: the feature is still a draft and has not made it into the official GraphQL spec yet.
-It is expected to be added once it has been implemented in multiple libraries and proven to be useful.
-It is not expected to change from the current draft.</p>
 <h3 id="17-federation-entity-resolver-configuration-methods-and-attributes-added-for-code-first-and-type-first-schemas" style="position:relative;"><a href="#17-federation-entity-resolver-configuration-methods-and-attributes-added-for-code-first-and-type-first-schemas" aria-label="17 federation entity resolver configuration methods and attributes added for code first and type first schemas permalink" class="anchor before"><svg aria-hidden="true" focusable="false" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>17. Federation entity resolver configuration methods and attributes added for code-first and type-first schemas</h3>
 <p>Extension methods have been added for defining entity resolvers in code-first and type-first schemas
 for GraphQL Federation.</p>