more links

coder · matifali · Aug 13, 2024 · Aug 12, 2024 · Aug 12, 2024 · Aug 12, 2024
commit a358cc37270a130d163efd22389e582304aee89f
diff --git a/docs/cli.md b/docs/cli.md
diff --git a/docs/templates/agent-metadata.md b/docs/templates/agent-metadata.md
@@ -15,7 +15,7 @@ All of these examples use
 for the script declaration. With heredoc strings, you can script without messy
 escape codes, just as if you were working in your terminal.
 
-Some of the examples use the [`coder stat`](../cli/stat.md) command. This is
+Some of the examples use the [`coder stat`](../reference/cli/stat.md) command. This is
 useful for determining CPU and memory usage of the VM or container that the
 workspace is running in, which is more accurate than resource usage about the
 workspace's host.

diff --git a/docs/templates/change-management.md b/docs/templates/change-management.md
@@ -27,6 +27,6 @@ coder templates push --yes $CODER_TEMPLATE_NAME \
 ```
 
 To cap token lifetime on creation,
-[configure Coder server to set a shorter max token lifetime](../cli/server.md#--max-token-lifetime).
+[configure Coder server to set a shorter max token lifetime](../reference/cli/server.md#--max-token-lifetime).
 For an example, see how we push our development image and template
 [with GitHub actions](https://github.com/coder/coder/blob/main/.github/workflows/dogfood.yaml).
diff --git a/docs/workspaces.md b/docs/workspaces.md
@@ -131,7 +131,7 @@ to set the default quiet hours to a time when most users are not expected to be
 using Coder.
 
 Admins can force users to use the default quiet hours with the
-[CODER_ALLOW_CUSTOM_QUIET_HOURS](./cli/server.md#allow-custom-quiet-hours)
+[CODER_ALLOW_CUSTOM_QUIET_HOURS](./reference/cli/server.md#allow-custom-quiet-hours)
 environment variable. Users will still be able to see the page, but will be
 unable to set a custom time or timezone. If users have already set a custom
 quiet hours schedule, it will be ignored and the default will be used instead.