docs: format and use term 'bleeding edge' for mainline releases

michaelbrewer · michaelbrewer · commit 8d10cfc3e070 · 2024-04-20T02:48:25.000-07:00
diff --git a/docs/install/releases.md b/docs/install/releases.md
@@ -8,9 +8,10 @@ their infrastructure on a staging environment before upgrading a production
 deployment.
 
 We support two release channels:
-[mainline](https://github.com/coder/coder/releases/tag/v2.10.1) for the edge version 
-of Coder and [stable](https://github.com/coder/coder/releases/latest) for those with
-lower tolerance for fault. We field our mainline releases publicly for one month
+[mainline](https://github.com/coder/coder/releases/tag/v2.10.1) for the bleeding
+edge version of Coder and
+[stable](https://github.com/coder/coder/releases/latest) for those with lower
+tolerance for fault. We field our mainline releases publicly for one month
 before promoting them to stable.
 
 ### Mainline releases
