docs: switch back to GitHub-style note callouts

lucasmelin · lucasmelin · commit 225c08b99a0a · 2025-03-05T12:15:57.000-05:00
This reverts commit c2aa359.
diff --git a/docs/admin/provisioners.md b/docs/admin/provisioners.md
@@ -166,13 +166,10 @@ inside the Terraform. See the
 [workspace tags documentation](../admin/templates/extending-templates/workspace-tags.md)
 for more information.
 
-<blockquote class="admonition note">
-
-Workspace tags defined with the `coder_workspace_tags` data source
-template **do not** automatically apply to the template import job! You may
-need to specify the desired tags when importing the template.
-
-</blockquote>
+> [!NOTE]
+> Workspace tags defined with the `coder_workspace_tags` data source
+> template **do not** automatically apply to the template import job! You may
+> need to specify the desired tags when importing the template.
 
 A provisioner can run a given build job if one of the below is true:
 
@@ -194,17 +191,14 @@ However, it will not pick up any build jobs that do not have either of the
 from templates with the tag `scope=user` set, or build jobs from templates in
 different organizations.
 
-<blockquote class="admonition note">
-
-If you only run tagged provisioners, you will need to specify a set of
-tags that matches at least one provisioner for _all_ template import jobs and
-workspace build jobs.
-
-You may wish to run at least one additional provisioner with no additional
-tags so that provisioner jobs with no additional tags defined will be picked
-up instead of potentially remaining in the Pending state indefinitely.
-
-</blockquote>
+> [!NOTE]
+> If you only run tagged provisioners, you will need to specify a set of
+> tags that matches at least one provisioner for _all_ template import jobs and
+> workspace build jobs.
+>
+> You may wish to run at least one additional provisioner with no additional
+> tags so that provisioner jobs with no additional tags defined will be picked
+> up instead of potentially remaining in the Pending state indefinitely.
 
 This is illustrated in the below table:
 
diff --git a/docs/admin/templates/extending-templates/parameters.md b/docs/admin/templates/extending-templates/parameters.md
@@ -79,34 +79,31 @@ data "coder_parameter" "security_groups" {
 }
 ```
 
-<blockquote class="admonition note">
-
-Overriding a `list(string)` on the CLI is tricky because:
-
-- `--parameter "parameter_name=parameter_value"` is parsed as CSV.
-- `parameter_value` is parsed as JSON.
-
-So, to properly specify a `list(string)` with the `--parameter` CLI argument,
-you will need to take care of both CSV quoting and shell quoting.
-
-For the above example, to override the default values of the `security_groups`
-parameter, you will need to pass the following argument to `coder create`:
-
-```shell
---parameter "\"security_groups=[\"\"DevOps Security Group\"\",\"\"Backend Security Group\"\"]\""
-```
-
-Alternatively, you can use `--rich-parameter-file` to work around the above
-issues. This allows you to specify parameters as YAML. An equivalent parameter
-file for the above `--parameter` is provided below:
-
-```yaml
-security_groups:
-  - DevOps Security Group
-  - Backend Security Group
-```
-
-</blockquote>
+> [!NOTE]
+> Overriding a `list(string)` on the CLI is tricky because:
+>
+> - `--parameter "parameter_name=parameter_value"` is parsed as CSV.
+> - `parameter_value` is parsed as JSON.
+>
+> So, to properly specify a `list(string)` with the `--parameter` CLI argument,
+> you will need to take care of both CSV quoting and shell quoting.
+>
+> For the above example, to override the default values of the `security_groups`
+> parameter, you will need to pass the following argument to `coder create`:
+>
+> ```shell
+> --parameter "\"security_groups=[\"\"DevOps Security Group\"\",\"\"Backend Security Group\"\"]\""
+> ```
+>
+> Alternatively, you can use `--rich-parameter-file` to work around the above
+> issues. This allows you to specify parameters as YAML. An equivalent parameter
+> file for the above `--parameter` is provided below:
+>
+> ```yaml
+> security_groups:
+>   - DevOps Security Group
+>   - Backend Security Group
+> ```
 
 ## Options
 
