fix doc links

f0ssel · f0ssel · commit b00820d438a8 · 2024-09-27T14:50:53.000Z
diff --git a/docs/admin/provisioners.md b/docs/admin/provisioners.md
@@ -26,7 +26,7 @@ For example, running 30 provisioner containers will allow 30 users to start
 workspaces at the same time.
 
 Provisioners are started with the
-[coder provisionerd start](../reference/cli/provisionerd_start.md) command.
+[coder provisionerd start](../reference/cli/provisioner_start.md) command.
 
 ## Authentication
 
@@ -49,7 +49,7 @@ the [Helm example](#example-running-an-external-provisioner-with-helm) below.
 
 Provisioners can broadly be categorized by scope: `organization` or `user`. The
 scope of a provisioner can be specified with
-[`-tag=scope=<scope>`](../reference/cli/provisionerd_start.md#t---tag) when
+[`-tag=scope=<scope>`](../reference/cli/provisioner_start.md#t---tag) when
 starting the provisioner daemon. Only users with at least the
 [Template Admin](../admin/users.md#roles) role or higher may create
 organization-scoped provisioner daemons.
@@ -59,7 +59,7 @@ There are two exceptions:
 - [Built-in provisioners](../reference/cli/server.md#provisioner-daemons) are
   always organization-scoped.
 - External provisioners started using a
-  [pre-shared key (PSK)](../reference/cli/provisionerd_start.md#psk) are always
+  [pre-shared key (PSK)](../reference/cli/provisioner_start.md#psk) are always
   organization-scoped.
 
 ### Organization-Scoped Provisioners
