Link missing features

docs/about/MISSING_FEATURES.md

@@ -6,6 +6,8 @@ Have a feature request you don't see here? File an issue!
 
 We don't have a formal guide on how to deploy a production instance of Rivet yourself.
 
+#45
+
 ## Multiple clouds
 
 The open source version of Rivet only supports Linode at the moment. As we progress, we'll be bringing our other cloud providers to open source soon.
@@ -14,18 +16,29 @@ The open source version of Rivet only supports Linode at the moment. As we progr
 
 Rivet does not support bringing your own job servers (regardless of cloud) at the moment. This will eventually let you run your own hardware, including that toaster sitting in your basement.
 
+#44
+
 ## Slow development setup times
 
 It takes a long time to bootstrap a standalone Rivet cluster for development. Like _really_ long. Trust us, we get it.
 
-## ClickHouse failover & sharding
+#43
+
+## Distributed ClickHouse
 
 Self-hosted ClickHouse doesn't have a failover or sharding mechanism at the moment.
 
+#42
+
 ## Traffic Server `consistent_hash` routing
 
-SVC-824
+Rivet heavily uses pull-through caching. At the moment, efficient caching is done through the good old throw-more-hardware-at-the-problem solution. Traffic Server has mechanics built in to make this work better.
+
+#31
 
 ## Sharable Grafana dashboards
 
 Rivet exposes metrics and logs for everything, but we don't publish Grafana internal dashboards.
+
+#41
+