diff --git a/docs/source/data/resolvers.mdx b/docs/source/data/resolvers.mdx
index a83cacae122..7e55c07ea4a 100644
--- a/docs/source/data/resolvers.mdx
+++ b/docs/source/data/resolvers.mdx
@@ -5,6 +5,8 @@ description: How Apollo Server processes GraphQL operations
 
 import TopLevelAwait from "../shared/top-level-await.mdx"
 
+> If you learn best by doing, check out the [tutorial on writing resolvers](https://www.apollographql.com/tutorials/lift-off-part2?referrer=docs-content).
+
 Apollo Server needs to know how to populate data for every field in your schema so that it can respond to requests for that data. To accomplish this, it uses resolvers.
 
 **A resolver is a function that's responsible for populating the data for a single field in your schema.** It can populate that data in any way you define, such as by fetching data from a back-end database or a third-party API.
diff --git a/docs/source/getting-started.mdx b/docs/source/getting-started.mdx
index b012a5f0211..d1ac9009f0b 100644
--- a/docs/source/getting-started.mdx
+++ b/docs/source/getting-started.mdx
@@ -352,6 +352,6 @@ If you want to use Apollo Server with a specific web framework, see our [list of
 
 If you learn best by doing, Apollo's learning platform offers the following courses:
 
-- [Intro to GraphQL with TypeScript & Apollo Server](https://www.apollographql.com/tutorials/intro-typescript)
-- [Lift-off I: Basics - Implement a GraphQL API with Apollo Server (Node.js) & Apollo Client](https://www.apollographql.com/tutorials/lift-off-part1)
-- [Lift-off II: Resolvers - Learn how to use resolvers](https://www.apollographql.com/tutorials/lift-off-part2)
+- [Intro to GraphQL with TypeScript & Apollo Server](https://www.apollographql.com/tutorials/intro-typescript?referrer=docs-content)
+- [Lift-off I: Basics - Implement a GraphQL API with Apollo Server (Node.js) & Apollo Client](https://www.apollographql.com/tutorials/lift-off-part1?referrer=docs-content)
+- [Lift-off II: Resolvers - Learn how to use resolvers](https://www.apollographql.com/tutorials/lift-off-part2?referrer=docs-content)
diff --git a/docs/source/migration.mdx b/docs/source/migration.mdx
index 3008fcac0a5..c0aa57a49b1 100644
--- a/docs/source/migration.mdx
+++ b/docs/source/migration.mdx
@@ -5,7 +5,7 @@ title: Migrating to Apollo Server 4
 import TopLevelAwait from "./shared/top-level-await.mdx"
 import IntegrationTable from "./shared/integration-table.mdx"
 
-> 📣 **Apollo Server 4 is [generally available](/resources/product-launch-stages#general-availability)!**
+> 📣 **Apollo Server 4 is [generally available](/resources/product-launch-stages#general-availability)!** If you learn best by doing, check out the [tutorial for migrating from Apollo Server 3](https://www.apollographql.com/tutorials/side-quest-as4?referrer=docs-content).
 
 Apollo Server 4 focuses on improving Apollo Server's extensibility and making it simpler to use, maintain, and document. To learn more about the inspiration behind this release, see the [Apollo Server Roadmap](https://github.com/apollographql/apollo-server/blob/24a841bc68d/ROADMAP.md).
 
diff --git a/docs/source/schema/schema.md b/docs/source/schema/schema.md
index d7139ad11ec..65761f77249 100644
--- a/docs/source/schema/schema.md
+++ b/docs/source/schema/schema.md
@@ -2,6 +2,8 @@
 title: GraphQL Schema Basics
 ---
 
+> If you learn best by doing, check out the [intro tutorial to GraphQL with TypeScript & Apollo Server](https://www.apollographql.com/tutorials/intro-typescript?referrer=docs-content).
+
 Your GraphQL server uses a **schema** to describe the shape of your available data. This schema defines a hierarchy of **types** with **fields** that are populated from your back-end data stores. The schema also specifies exactly which **queries** and **mutations** are available for clients to execute.
 
 This article describes the fundamental building blocks of a schema and how to create one for your GraphQL server.