Merge pull request #7906 from apollographql/docs/update-links

docs: update links

Author: Meschreiber

docs/source/using-federation/api/apollo-gateway.mdx

@@ -125,7 +125,7 @@ const gateway = new ApolloGateway({
 
 You provide your supergraph schema to the gateway with this option. You can provide it as a `string`, via a `SupergraphSdlHook`, or via a `SupergraphManager`.
 
-**When `supergraphSdl` is a `string`:** A [supergraph schema](/federation/federated-types/overview/#supergraph-schema) ([generated with the Rover CLI](/rover/commands/supergraphs/#composing-a-supergraph-schema)) that's composed from your subgraph schemas. The supergraph schema includes directives that specify routing information for each subgraph.
+**When `supergraphSdl` is a `string`:** A [supergraph schema](/federation/federated-schemas/#supergraph-schema) ([generated with the Rover CLI](/rover/commands/supergraphs/#composing-a-supergraph-schema)) that's composed from your subgraph schemas. The supergraph schema includes directives that specify routing information for each subgraph.
 
 **When `supergraphSdl` is a `SupergraphSdlHook`:** This is an `async` function that returns an object containing a `supergraphSdl` string as well as a `cleanup` function. The hook accepts an object containing the following properties:
 

docs/source/using-federation/apollo-gateway-setup.mdx

@@ -61,9 +61,9 @@ console.log(`🚀  Server ready at ${url}`);
 
 ### Composing the supergraph schema
 
-In the above example, we provide the `supergraphSdl` option to the `ApolloGateway` constructor. This is the string representation of our [supergraph schema](/federation/federated-types/overview/#supergraph-schema), which is composed from all of our subgraph schemas.
+In the above example, we provide the `supergraphSdl` option to the `ApolloGateway` constructor. This is the string representation of our [supergraph schema](/federation/federated-schemas/#supergraph-schema), which is composed from all of our subgraph schemas.
 
-To learn how to compose your supergraph schema, see [Supported methods](/federation/federated-types/composition/#supported-methods).
+To learn how to compose your supergraph schema, see [Supported methods](/federation/federated-schemas/composition/#supported-methods).
 
 > In production, we strongly recommend running the gateway in a **managed mode** with Apollo Studio, which enables your gateway to update its configuration without a restart. For details, see [Setting up managed federation](/federation/managed-federation/setup/).
 
@@ -428,7 +428,7 @@ type ExampleType {
 }
 ```
 
-The gateway strips all definitions _and_ uses of type system directives from your graph's [API schema](/federation/federated-types/overview/#api-schema). This has no effect on your subgraph schemas, which retain this information.
+The gateway strips all definitions _and_ uses of type system directives from your graph's [API schema](/federation/federated-schemas/#api-schema). This has no effect on your subgraph schemas, which retain this information.
 
 Effectively, the gateway supports type system directives by _ignoring_ them, making them the responsibility of the subgraphs that define them.
 

docs/source/using-federation/apollo-subgraph-setup.mdx

@@ -107,7 +107,7 @@ const typeDefs = gql`
 
 This definition enables the schema to use Federation 2 features. Without it, Federation 2 composition assumes that a subgraph is using Federation 1, which sets certain defaults for backward compatibility.
 
-> As you begin using more [federation-specific directives](/federation/federated-types/federated-directives) beyond `@key` and `@shareable`, you'll need to add those directives to the `import` array shown above.
+> As you begin using more [federation-specific directives](/federation/federated-schemas/federated-directives) beyond `@key` and `@shareable`, you'll need to add those directives to the `import` array shown above.
 
 ### 3. Define an entity