Use quarto link format.

docs/admins/howto/calendar-scaler.qmd

@@ -131,8 +131,7 @@ functions.
 When you're ready, create a PR. The deployment workflow is as follows:
 
 1.  Get all authed-up for `chartpress` by performing the
-    steps listed
-    [here](https://docs.datahub.berkeley.edu/en/latest/admins/howto/rebuild-hub-image.html#).
+    [documented steps](rebuild-hub-image.qmd).
 2.  Run `chartpress --push` from the root
     `datahub/` directory. If this succeeds, check your `git
     status` and add
@@ -155,8 +154,7 @@ to change/add/update any packages, you'll need to do the following:
 5.  Check your git status and diffs, and create a pull request if
     necessary.
 6.  Get all authed-up for `chartpress` by performing the
-    steps listed
-    [here](https://docs.datahub.berkeley.edu/en/latest/admins/howto/rebuild-hub-image.html#).
+    [documented steps](rebuild-hub-image.qmd).
 7.  Run `chartpress --push` from the root
     `datahub/` directory. If this succeeds, check your `git
     status` and add

docs/admins/howto/new-hub.qmd

@@ -386,7 +386,7 @@ prometheus-node-exporter
 
 Besides setting defaults, we can dynamically change the placeholder
 counts by either adding new, or editing existing, [calendar
-events](https://docs.datahub.berkeley.edu/en/latest/admins/howto/calendar-scaler.html).
+events](calendar-scaler.qmd).
 This is useful for large courses which can have placeholder nodes set
 aside for predicatable periods of heavy ramp up.