lint

coder · mafredri · Dec 19, 2024 · Dec 19, 2024 · Dec 19, 2024 · Dec 19, 2024
commit b57bc8c9108c95d785879ae8d4dbd5440ff386d8
diff --git a/coderd/database/dbmem/dbmem.go b/coderd/database/dbmem/dbmem.go
@@ -3749,7 +3749,7 @@ func (q *FakeQuerier) GetProvisionerDaemonsByOrganization(_ context.Context, arg
 	return daemons, nil
 }
 
-func (q *FakeQuerier) GetProvisionerDaemonsWithStatusByOrganization(ctx context.Context, arg database.GetProvisionerDaemonsWithStatusByOrganizationParams) ([]database.GetProvisionerDaemonsWithStatusByOrganizationRow, error) {
+func (q *FakeQuerier) GetProvisionerDaemonsWithStatusByOrganization(_ context.Context, arg database.GetProvisionerDaemonsWithStatusByOrganizationParams) ([]database.GetProvisionerDaemonsWithStatusByOrganizationRow, error) {
 	err := validateDatabaseType(arg)
 	if err != nil {
 		return nil, err

diff --git a/docs/admin/monitoring/logs.md b/docs/admin/monitoring/logs.md
@@ -25,7 +25,7 @@ Connect logs are all captured in the `coderd` logs.
 ## `provisionerd` Logs
 
 Logs for [external provisioners](../provisioners.md) are structured
-[and configured](../../reference/cli/provisioner_start.md#--log-human) similarly
+[and configured](../../reference/cli/provisioners_start.md#--log-human) similarly
 to `coderd` logs. Use these logs to troubleshoot and monitor the Terraform
 operations behind workspaces and templates.
 

diff --git a/docs/admin/provisioners.md b/docs/admin/provisioners.md
@@ -28,7 +28,7 @@ For example, running 30 provisioner containers will allow 30 users to start
 workspaces at the same time.
 
 Provisioners are started with the
-[`coder provisioner start`](../reference/cli/provisioner_start.md) command in
+[`coder provisioner start`](../reference/cli/provisioners_start.md) command in
 the [full Coder binary](https://github.com/coder/coder/releases). Keep reading
 to learn how to start provisioners via Docker, Kubernetes, Systemd, etc.
 
@@ -235,7 +235,7 @@ This is illustrated in the below table:
 
 Provisioners can broadly be categorized by scope: `organization` or `user`. The
 scope of a provisioner can be specified with
-[`-tag=scope=<scope>`](../reference/cli/provisioner_start.md#-t---tag) when
+[`-tag=scope=<scope>`](../reference/cli/provisioners_start.md#-t---tag) when
 starting the provisioner daemon. Only users with at least the
 [Template Admin](./users/index.md#roles) role or higher may create
 organization-scoped provisioner daemons.
@@ -245,7 +245,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/provisioner_start.md#--psk) are always
+  [pre-shared key (PSK)](../reference/cli/provisioners_start.md#--psk) are always
   organization-scoped.
 
 ### Organization-Scoped Provisioners