md fixes

EdwardAngert · EdwardAngert · commit 40a94f19eda9 · 2024-12-06T18:48:11.000Z
diff --git a/docs/admin/networking/workspace-proxies.md b/docs/admin/networking/workspace-proxies.md
@@ -14,11 +14,11 @@ connecting with their workspace over SSH, a workspace app, port forwarding, etc.
 Dashboard connections and API calls (e.g. the workspaces list) are not served
 over workspace proxies.
 
-# Deploy a workspace proxy
+## Deploy a workspace proxy
 
-Each workspace proxy should be a unique instance. At no point should 2 workspace
-proxy instances share the same authentication token. They only require port 443
-to be open and are expected to have network connectivity to the coderd
+Each workspace proxy should be a unique instance. At no point should two
+workspace proxy instances share the same authentication token. They only require
+port 443 to be open and are expected to have network connectivity to the coderd
 dashboard. Workspace proxies **do not** make any database connections.
 
 Workspace proxies can be used in the browser by navigating to the user
diff --git a/docs/admin/provisioners.md b/docs/admin/provisioners.md
@@ -227,7 +227,7 @@ This is illustrated in the below table:
 > **Note to maintainers:** to generate this table, run the following command and
 > copy the output:
 >
-> ```
+> ```go
 > go test -v -count=1 ./coderd/provisionerdserver/ -test.run='^TestAcquirer_MatchTags/GenTable$'
 > ```
 
diff --git a/docs/admin/security/secrets.md b/docs/admin/security/secrets.md
@@ -1,15 +1,17 @@
 # Secrets
 
-<blockquote class="info">
+<blockquote class="admonition note">
+
 This article explains how to use secrets in a workspace. To authenticate the
-workspace provisioner, see <a href="../users">this</a>.
+workspace provisioner, see the [provisioners](../provisioners.md) documentation.
+
 </blockquote>
 
 Coder is open-minded about how you get your secrets into your workspaces.
 
-## Wait a minute...
+## Before you begin
 
-Your first stab at secrets with Coder should be your local method. You can do
+Your first attempt at secrets with Coder should be your local method. You can do
 everything you can locally and more with your Coder workspace, so whatever
 workflow and tools you already use to manage secrets may be brought over.
 
diff --git a/docs/admin/templates/extending-templates/parameters.md b/docs/admin/templates/extending-templates/parameters.md
@@ -90,7 +90,7 @@ data "coder_parameter" "security_groups" {
 > 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\"\"]\""
 > ```
 >
diff --git a/docs/admin/templates/extending-templates/variables.md b/docs/admin/templates/extending-templates/variables.md
@@ -53,15 +53,15 @@ variables, you can employ a straightforward solution:
 
 1. Create a `terraform.tfvars` file in in the template directory:
 
-```tf
-coder_image = newimage:tag
-```
+   ```tf
+   coder_image = newimage:tag
+   ```
 
-2. Push the new template revision using Coder CLI:
+1. Push the new template revision using Coder CLI:
 
-```
-coder templates push my-template -y # no need to use --var
-```
+   ```shell
+   coder templates push my-template -y # no need to use --var
+   ```
 
 This file serves as a mechanism to override the template settings for variables.
 It can be stored in the repository for easy access and reference. Coder CLI
diff --git a/docs/admin/templates/managing-templates/devcontainers/add-devcontainer.md b/docs/admin/templates/managing-templates/devcontainers/add-devcontainer.md
@@ -144,7 +144,3 @@ Lifecycle scripts are managed by project developers.
 ## Next steps
 
 - [Dev container security and caching](./devcontainer-security-caching.md)
-
-```
-
-```
diff --git a/docs/admin/templates/managing-templates/devcontainers/devcontainer-security-caching.md b/docs/admin/templates/managing-templates/devcontainers/devcontainer-security-caching.md
@@ -3,7 +3,7 @@
 Ensure Envbuilder can only pull pre-approved images and artifacts by configuring
 it with your existing HTTP proxies, firewalls, and artifact managers.
 
-### Configure registry authentication
+## Configure registry authentication
 
 You may need to authenticate to your container registry, such as Artifactory, or
 Git provider such as GitLab, to use Envbuilder. See the
diff --git a/docs/changelogs/v0.25.0.md b/docs/changelogs/v0.25.0.md
@@ -23,9 +23,11 @@
   [--block-direct-connections](https://coder.com/docs/cli/server#--block-direct-connections)
   (#7936)
 - Search for workspaces based on last activity (#2658)
+
   ```text
   last_seen_before:"2023-01-14T23:59:59Z" last_seen_after:"2023-01-08T00:00:00Z"
   ```
+
 - Queue position of pending workspace builds are shown in the dashboard (#8244)
   <img width="1449" alt="Queue position" src="https://github.com/coder/coder/assets/22407953/44515a19-ddfb-4431-8c2a-203487c4efe8">
 - Enable Terraform debug mode via deployment configuration (#8260)

Original file line number	Diff line number	Diff line change
`@@ -227,7 +227,7 @@ This is illustrated in the below table:`
`227`	`227`	`> Note to maintainers: to generate this table, run the following command and`
`228`	`228`	`> copy the output:`
`229`	`229`	`>`
`230`		-> ```
	`230`	+> ```go
`231`	`231`	`> go test -v -count=1 ./coderd/provisionerdserver/ -test.run='^TestAcquirer_MatchTags/GenTable$'`
`232`	`232`	> ```
`233`	`233`
Original file line number	Diff line number	Diff line change
`@@ -90,7 +90,7 @@ data "coder_parameter" "security_groups" {`
`90`	`90`	> For the above example, to override the default values of the `security_groups`
`91`	`91`	> parameter, you will need to pass the following argument to `coder create`:
`92`	`92`	`>`
`93`		-> ```
	`93`	+> ```shell
`94`	`94`	`> --parameter "\"security_groups=[\"\"DevOps Security Group\"\",\"\"Backend Security Group\"\"]\""`
`95`	`95`	> ```
`96`	`96`	`>`