@@ -28,7 +28,7 @@ For example, running 30 provisioner containers will allow 30 users to start
28
28
workspaces at the same time.
29
29
30
30
Provisioners are started with the
31
- [ ` coder provisioner start ` ] ( ../reference/cli/provisioner_start .md ) command in
31
+ [ ` coder provisioner start ` ] ( ../reference/cli/provisioners_start .md ) command in
32
32
the [ full Coder binary] ( https://github.com/coder/coder/releases ) . Keep reading
33
33
to learn how to start provisioners via Docker, Kubernetes, Systemd, etc.
34
34
@@ -235,7 +235,7 @@ This is illustrated in the below table:
235
235
236
236
Provisioners can broadly be categorized by scope: ` organization` or ` user` . The
237
237
scope of a provisioner can be specified with
238
- [` -tag=scope=< scope> ` ](../reference/cli/provisioner_start .md#-t---tag) when
238
+ [` -tag=scope=< scope> ` ](../reference/cli/provisioners_start .md#-t---tag) when
239
239
starting the provisioner daemon. Only users with at least the
240
240
[Template Admin](./users/index.md#roles) role or higher may create
241
241
organization-scoped provisioner daemons.
@@ -245,7 +245,7 @@ There are two exceptions:
245
245
- [Built-in provisioners](../reference/cli/server.md#--provisioner-daemons) are
246
246
always organization-scoped.
247
247
- External provisioners started using a
248
- [pre-shared key (PSK)](../reference/cli/provisioner_start .md#--psk) are always
248
+ [pre-shared key (PSK)](../reference/cli/provisioners_start .md#--psk) are always
249
249
organization-scoped.
250
250
251
251
# ## Organization-Scoped Provisioners
0 commit comments