diff --git a/blog/2023-01-13-cwtch-stable-api-design.md b/blog/2023-01-13-cwtch-stable-api-design.md
index 7cf205df..031103a4 100644
--- a/blog/2023-01-13-cwtch-stable-api-design.md
+++ b/blog/2023-01-13-cwtch-stable-api-design.md
@@ -16,9 +16,9 @@ Cwtch grew out of a prototype and has been allowed to evolve over time as we dis
 
 As we grew, we inserted experimental functionality where it was most accessible to place - not, necessarily, where it was ultimately best to place it -  this has led to some degree of overlapping, and inconsistent, responsibilities across Cwtch software packages.
 
-As we move out of Beta and towards Cwtch Stable it is time to revisit these previous decisions with both the benefit of hindsight, and years of real-world testing.
+As we move out of Beta and [towards Cwtch Stable](https://docs.cwtch.im/blog/path-to-cwtch-stable) it is time to revisit these previous decisions with both the benefit of hindsight, and years of real-world testing.
 
-In this post we will outline planned new changes to the Cwtch API that realign responsibilities, and explicitly enable new functionality to be built in a modular, controlled, and secure way.  In preparation [for Cwtch Stable](https://docs.cwtch.im/blog/path-to-cwtch-stable), and beyond.
+In this post we will outline our plans for the Cwtch API that realign responsibilities, and explicitly enable new functionality to be built in a modular, controlled, and secure way.  In preparation for Cwtch Stable, and beyond.
 
 ![](/img/devlog2.png)