Fix links

src/content/basics/resources/faq.mdx

@@ -197,6 +197,6 @@ Apollo Client comes with everything needed to test a client app that makes queri
 
 ### How can I safely make changes to my schema?
 
-Schemas naturally evolve over time. GraphQL schemas are more resilient to change than other APIs, but there are still occasions where breaking changes are necessary to support new functionality. [This section](/graphos/delivery/schema-checks#types-of-schema-changes) explains in more detail which kinds of changes are always safe to make, and which kinds might break existing clients.
+Schemas naturally evolve over time. GraphQL schemas are more resilient to change than other APIs, but there are still occasions where breaking changes are necessary to support new functionality. [This section](/graphos/delivery/checks-reference#types-of-schema-changes) explains in more detail which kinds of changes are always safe to make, and which kinds might break existing clients.
 
 The [schema checks](/graphos/delivery/schema-checks) feature of Apollo GraphOS helps you identify potentially breaking schema changes before you make them.

src/content/graphos/delivery/check-configurations.mdx

@@ -91,7 +91,7 @@ Compared 1 schema changes against 24 operations
 View full details at https://studio.apollographql.com/service/docs-example-graph/checks/<DETAILS>
 ```
 
-Each change to the schema is labeled either `PASS` or `FAIL`. For a complete list of schema change codes, see the [Reference](./checks-reference#schema-change-types).
+Each change to the schema is labeled either `PASS` or `FAIL`. For a complete list of schema change codes, see the [Reference](./checks-reference#types-of-schema-changes).
 
 <Note>
 

src/content/graphos/delivery/checks-reference.mdx

@@ -87,7 +87,7 @@ A user has chosen to [ignore](#overriding-flagged-changes) schema change(s) for
 </table>
 
 
-## Schema change types
+## Types of schema changes
 
 When you run a schema check, the check response classifies each schema change with the following codes.
 

src/content/graphos/delivery/schema-proposals/implementation.mdx

@@ -32,7 +32,7 @@ A proposal's ID is always prefixed with `p-` and followed by a number. You can f
 
 ## Validate changes with checks
 
-GraphOS provides [schema checks](../schema-checks) to help you identify breaking changes. You [run checks on local changes](../schema-checks#the-checks-lifecycle) before publishing them.
+GraphOS provides [schema checks](../schema-checks) to help you identify breaking changes. You [run checks on local changes](../check-configurations#the-checks-lifecycle) before publishing them.
 
 Since schema checks [run automatically on every revision](./creation#schema-checks) in a proposal, if your last revision's checks pass, any changes you implement locally from a proposal should pass too.
 Regardless, it's best to run checks before publishing changes to make sure errors haven't crept in.