Fix links that are broken until other pages ship. (#1836)

mandiwise · benjie · web-flow · commit 96e2503b4fd2 · 2024-11-25T16:55:03.000Z
Co-authored-by: Benjie &lt;benjie@jemjie.com&gt;
diff --git a/src/pages/learn/security.mdx b/src/pages/learn/security.mdx
@@ -77,7 +77,7 @@ query {
 }
 ```
 
-Even when [the N+1 problem](/learn/performance/#the-n1-problem) has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance. 
+Even when the N+1 problem has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance. 
 
 For this reason, it's a good idea to limit the maximum depth of fields that a single operation can have. Many GraphQL implementations expose configuration options that allow you to specify a maximum depth for a GraphQL document and return an error to the client if a request exceeds this limit before execution begins.
 

Original file line number	Diff line number	Diff line change
`@@ -77,7 +77,7 @@ query {`
`77`	`77`	`}`
`78`	`78`	```
`79`	`79`
`80`		`-Even when [the N+1 problem](/learn/performance/#the-n1-problem) has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance.`
	`80`	`+Even when the N+1 problem has been remediated through batched requests to underlying data sources, overly nested fields may still place excessive load on server resources and impact API performance.`
`81`	`81`
`82`	`82`	`For this reason, it's a good idea to limit the maximum depth of fields that a single operation can have. Many GraphQL implementations expose configuration options that allow you to specify a maximum depth for a GraphQL document and return an error to the client if a request exceeds this limit before execution begins.`
`83`	`83`