diff --git a/0106-combine-schedulers-pt3/README.md b/0106-combine-schedulers-pt3/README.md
index 73841c27..5950d28f 100644
--- a/0106-combine-schedulers-pt3/README.md
+++ b/0106-combine-schedulers-pt3/README.md
@@ -1,5 +1,5 @@
 ## [Point-Free](https://www.pointfree.co)
 
-> #### This directory contains code from Point-Free Episode: [Combine Schedulers: Controlling Time](https://www.pointfree.co/episodes/ep105-combine-schedulers-controlling-time)
+> #### This directory contains code from Point-Free Episode: [Combine Schedulers: Erasing Time](https://www.pointfree.co/episodes/ep106-combine-schedulers-erasing-time)
 >
-> The `Scheduler` protocol of Combine is a powerful abstraction that unifies many ways of executing asynchronous work, and it can even control the flow of time through our code. Unfortunately Combine doesn't give us this ability out of the box, so let's build it from scratch.
+> We refactor our application’s code so that we can run it in production with a live dispatch queue for the scheduler, while allowing us to run it in tests with a test scheduler. If we do this naively we will find that generics infect many parts of our code, but luckily we can employ the technique of type erasure to make things much nicer.