diff --git a/docs/source/data/fetching-data.mdx b/docs/source/data/fetching-data.mdx
index 2ffc0aebe83..f1d82044479 100644
--- a/docs/source/data/fetching-data.mdx
+++ b/docs/source/data/fetching-data.mdx
@@ -26,6 +26,12 @@ flowchart LR;
client --Sends query--> ApolloServer;
```
+
+
+[Learn how Apollo Connectors](/graphos/schema-design/connectors/) simplify incorporating REST APIs into your graph.
+
+
+
Because your server can use multiple various data sources, keeping your [resolvers](./resolvers) tidy becomes _even more_ important.
For this reason, we recommend creating individual data source classes to encapsulate the logic of fetching data from a particular source, providing methods that resolvers can use to access data neatly. You can additionally customize your data source classes to help with caching, deduplication, or errors while resolving operations.
diff --git a/docs/source/data/fetching-rest.mdx b/docs/source/data/fetching-rest.mdx
index 8963290cc26..4d092d51d9b 100644
--- a/docs/source/data/fetching-rest.mdx
+++ b/docs/source/data/fetching-rest.mdx
@@ -5,6 +5,12 @@ description: Using RESTDataSource to fetch data from REST APIs
import TopLevelAwait from "../shared/top-level-await.mdx"
+
+
+[Learn how Apollo Connectors](/graphos/schema-design/connectors/) simplify incorporating REST APIs into your graph.
+
+
+
> See the [`@apollo/datasource-rest` README](https://github.com/apollographql/datasource-rest) for the full details of the `RESTDataSource` API.
The `RESTDataSource` class simplifies fetching data from REST APIs and helps handle caching, request deduplication, and errors while resolving operations.