docs: fix glossary links (#2114)

Updates glossary links

docs/source/commands/graphs.mdx

@@ -59,7 +59,7 @@ rover graph introspect http://example.com/graphql --header "Authorization: Beare
 
 ### Output format
 
-By default, both `graph fetch` and `graph introspect` output fetched [SDL](/resources/graphql-glossary/#schema-definition-language-sdl) to `stdout`. This is useful for providing the schema as input to other Rover commands:
+By default, both `graph fetch` and `graph introspect` output fetched [SDL](/resources/glossary#sdl) to `stdout`. This is useful for providing the schema as input to other Rover commands:
 
 ```shell
 rover graph introspect http://localhost:4000 | rover graph publish my-graph@dev --schema -
@@ -94,7 +94,7 @@ If the graph exists in GraphOS but the variant doesn't, a new variant is be crea
 
 ### Providing the schema
 
-You provide your schema to Rover commands via the `--schema` option. The value is usually the path to a local `.graphql` or `.gql` file in [SDL format](/resources/graphql-glossary/#schema-definition-language-sdl).
+You provide your schema to Rover commands via the `--schema` option. The value is usually the path to a local `.graphql` or `.gql` file in [SDL format](/resources/glossary#sdl).
 
 If your schema isn't stored in a compatible file, you can provide `-` as the value of the `--schema` flag to instead accept an SDL string from `stdin`. This enables you to pipe the output of another Rover command (such as `graph introspect`), like so:
 
@@ -166,7 +166,7 @@ Options include:
 </td>
 <td>
 
-**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/graphql-glossary/#schema-definition-language-sdl).
+**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/glossary#sdl).
 
 Alternatively, you can provide `-`, in which case the command uses an SDL string piped to `stdin` instead (see [Using `stdin`](../conventions#using-stdin)).
 

docs/source/commands/subgraphs.mdx

@@ -93,7 +93,7 @@ rover subgraph introspect http://localhost:4001\
   --routing-url https://my-running-subgraph.com/api
 ```
 
-By default, both `subgraph fetch` and `subgraph introspect` output fetched [SDL](/resources/graphql-glossary/#schema-definition-language-sdl) to `stdout`. This is useful for providing the schema as input to other Rover commands:
+By default, both `subgraph fetch` and `subgraph introspect` output fetched [SDL](/resources/glossary#sdl) to `stdout`. This is useful for providing the schema as input to other Rover commands:
 
 ```shell
 rover subgraph introspect http://localhost:4000 | rover subgraph check my-graph --schema -
@@ -184,7 +184,7 @@ Options include:
 </td>
 <td>
 
-**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/graphql-glossary/#schema-definition-language-sdl).
+**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/glossary#sdl).
 
 Alternatively, you can provide `-`, in which case the command uses an SDL string piped to `stdin` instead (see [Using `stdin`](../conventions#using-stdin)).
 
@@ -343,7 +343,7 @@ Options include:
 </td>
 <td>
 
-**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/graphql-glossary/#schema-definition-language-sdl).
+**Required.** The path to a local `.graphql` or `.gql` file, in [SDL format](/resources/glossary#sdl).
 
 Alternatively, you can provide `-`, in which case the command uses an SDL string piped to `stdin` instead (see [Using `stdin`](../conventions#using-stdin)).