reword stale hive-domain discovery claims

nix/host-modules/hive-c0re/vhosts.nix

@@ -2,8 +2,8 @@
 # like every service's: the dashboard's vhost (`swarm.dashboardDomain`), which
 # carries the dashboard behind authelia, per-agent routing and the swagger UI;
 # and the vhost named for the hive domain, which redirects everything to the
-# dashboard's name. Matrix discovery on the hive domain is added by
-# ../glue-matrix-hive-discovery.nix.
+# dashboard's name. The matrix redirect, and discovery for a server name pinned to
+# the hive domain, are added by ../glue-matrix-hive-discovery.nix.
 {
   lib,
   config,

nix/host-modules/hive-gateway/vhosts.nix

@@ -4,7 +4,7 @@
 #
 # Scope: a service declares its own vhost and dns name in its own module,
 # the same way — the hive's dashboard and hive domain in
-# ../hive-c0re/vhosts.nix, matrix discovery in
+# ../hive-c0re/vhosts.nix, pinned-hive discovery in
 # ../glue-matrix-hive-discovery.nix. That keeps a service's gateway surface
 # next to the service, and keeps this file to what the gateway itself
 # serves.

nix/host-modules/swarm-ui.nix

@@ -104,8 +104,8 @@ in
   config = lib.mkIf deployCfg.swarm-controller.enable {
     assertions = [
       {
-        # The hive domain has its own vhost (matrix discovery, the redirect
-        # to the dashboard). A second vhost claiming the same
+        # The hive domain has its own vhost (the redirect to the dashboard, and
+        # discovery for a pinned server name). A second vhost claiming the same
         # server_name is not an error to nginx — it picks one and logs a
         # conflict — so the failure would surface as "the swarm UI is
         # sometimes a redirect", which is far harder to read than an
@@ -114,8 +114,8 @@ in
         message = ''
           services.hyperhive.swarm.domain (${apex}) must differ from
           services.hyperhive.domain (${hiveDomain}) — the hive domain is
-          already served by the gateway's own vhost for it (matrix
-          discovery, the redirect to the dashboard), and two vhosts
+          already served by the gateway's own vhost for it (the redirect to
+          the dashboard, and discovery for a pinned server name), and two vhosts
           claiming one server_name silently resolve to whichever nginx
           picks.