doc: links to latest videos

* manage blocking
* cqrs

akka-docs/src/main/paradox/persistence-query.md

@@ -27,6 +27,10 @@ side of an application, however it can help to migrate data from the write side
 simple scenarios Persistence Query may be powerful enough to fulfill the query needs of your app, however we highly
 recommend (in the spirit of CQRS) of splitting up the write/read sides into separate datastores as the need arises.
 
+
+The [CQRS with Akka 2.6 video](https://akka.io/blog/news/2020/02/05/akka-cqrs-video) is a good starting point for
+learning how to use `eventsByTag` to implement CQRS with Akka.
+
 ## Design overview
 
 Akka persistence query is purposely designed to be a very loosely specified API.

akka-docs/src/main/paradox/typed/dispatchers.md

@@ -142,6 +142,10 @@ to sleep for an indeterminate time, waiting for an external event to occur.
 Examples are legacy RDBMS drivers or messaging APIs, and the underlying reason
 is typically that (network) I/O occurs under the covers.
 
+The [Managing Blocking in Akka video](https://akka.io/blog/news/2020/01/22/managing-blocking-video)
+explains why it is bad to block inside an actor, and how you can use custom dispatchers to manage
+blocking when you cannot avoid it.
+
 ### Problem: Blocking on default dispatcher
 
 Simply adding blocking calls to your actor message processing like this is problematic:

akka-docs/src/main/paradox/typed/persistence.md

@@ -31,7 +31,8 @@ events to the actor, allowing it to rebuild its state. This can be either the fu
 or starting from a checkpoint in a snapshot which can dramatically reduce recovery times.
 
 The [Event Sourcing with Akka 2.6 video](https://akka.io/blog/news/2020/01/07/akka-event-sourcing-video)
-is a good starting point for learning Event Sourcing.
+is a good starting point for learning Event Sourcing, and then followed by the
+[CQRS with Akka 2.6 video](https://akka.io/blog/news/2020/02/05/akka-cqrs-video).
 
 @@@ note