Fixed links in performance docs (#3637)

website/src/docs/hotchocolate/performance/index.md

@@ -15,7 +15,7 @@ There are two flavors of persisted queries that Hot Chocolate server supports.
 The first approach is to store queries ahead of time (ahead of deployment).
 This can be done by extracting the queries from your client application at build time. This will reduce the size of the requests and the bundle size of your application since queries can be removed from the client code at build time and are replaced with query hashes. Apart from performance, persisted queries can also be used for security by configuring Hot Chocolate to only accept persisted queries on production.
 
-Strawberry Shake, [Relay](https://relay.dev/docs/en/persisted-queries), and Apollo client all support this approach.
+Strawberry Shake, [Relay](https://relay.dev/docs/guides/persisted-queries/), and [Apollo](https://www.apollographql.com/docs/react/api/link/persisted-queries/) client all support this approach.
 
 Read more on how to set up your server for persisted queries [here](persisted-queries).
 
@@ -25,6 +25,6 @@ Automatic persisted queries allow us to store queries dynamically on the server
 
 However, we do not have the option to seal our server from queries that we do not know, so this approach has **no** security benefits. We do not have any bundle size improvements for our application since the query is still needed at runtime.
 
-Both Strawberry Shake and Apollo client support this approach.
+Both Strawberry Shake and [Apollo](https://www.apollographql.com/docs/apollo-server/performance/apq/) client support this approach.
 
 Read more on how to set up your server for automatic persisted queries [here](automatic-persisted-queries).