chore(docs): update docs for correct use of shell and console and enforce linewidth (#9245)

docs/templates/modules.md

@@ -1,8 +1,12 @@
 # Template inheritance
 
-In instances where you want to reuse code across different Coder templates, such as common scripts or resource definitions, we suggest using [Terraform Modules](https://developer.hashicorp.com/terraform/language/modules).
+In instances where you want to reuse code across different Coder templates, such
+as common scripts or resource definitions, we suggest using
+[Terraform Modules](https://developer.hashicorp.com/terraform/language/modules).
 
-These modules can be stored externally from Coder, like in a Git repository or a Terraform registry. Below is an example of how to reference a module in your template:
+These modules can be stored externally from Coder, like in a Git repository or a
+Terraform registry. Below is an example of how to reference a module in your
+template:
 
 ```hcl
 data "coder_workspace" "me" {}
@@ -25,36 +29,52 @@ resource "coder_agent" "dev" {
 }
 ```
 
-> Learn more about [creating modules](https://developer.hashicorp.com/terraform/language/modules) and [module sources](https://developer.hashicorp.com/terraform/language/modules/sources) in the Terraform documentation.
+> Learn more about
+> [creating modules](https://developer.hashicorp.com/terraform/language/modules)
+> and
+> [module sources](https://developer.hashicorp.com/terraform/language/modules/sources)
+> in the Terraform documentation.
 
 ## Git authentication
 
-If you are importing a module from a private git repository, the Coder server [or provisioner](../admin/provisioners.md) needs git credentials. Since this token will only be used for cloning your repositories with modules, it is best to create a token with limited access to repositories and no extra permissions. In GitHub, you can generate a [fine-grained token](https://docs.github.com/en/rest/overview/permissions-required-for-fine-grained-personal-access-tokens?apiVersion=2022-11-28) with read only access to repos.
+If you are importing a module from a private git repository, the Coder server
+[or provisioner](../admin/provisioners.md) needs git credentials. Since this
+token will only be used for cloning your repositories with modules, it is best
+to create a token with limited access to repositories and no extra permissions.
+In GitHub, you can generate a
+[fine-grained token](https://docs.github.com/en/rest/overview/permissions-required-for-fine-grained-personal-access-tokens?apiVersion=2022-11-28)
+with read only access to repos.
 
-If you are running Coder on a VM, make sure you have `git` installed and the `coder` user has access to the following files
+If you are running Coder on a VM, make sure you have `git` installed and the
+`coder` user has access to the following files
 
-```sh
+```toml
 # /home/coder/.gitconfig
 [credential]
   helper = store
 ```
 
-```sh
+```toml
 # /home/coder/.git-credentials
 
 # GitHub example:
 https://your-github-username:your-github-pat@github.com
 ```
 
-If you are running Coder on Docker or Kubernetes, `git` is pre-installed in the Coder image. However, you still need to mount credentials. This can be done via a Docker volume mount or Kubernetes secrets.
+If you are running Coder on Docker or Kubernetes, `git` is pre-installed in the
+Coder image. However, you still need to mount credentials. This can be done via
+a Docker volume mount or Kubernetes secrets.
 
 ### Passing git credentials in Kubernetes
 
-First, create a `.gitconfig` and `.git-credentials` file on your local machine. You may want to do this in a temporary directory to avoid conflicting with your own git credentials.
+First, create a `.gitconfig` and `.git-credentials` file on your local machine.
+You may want to do this in a temporary directory to avoid conflicting with your
+own git credentials.
 
-Next, create the secret in Kubernetes. Be sure to do this in the same namespace that Coder is installed in.
+Next, create the secret in Kubernetes. Be sure to do this in the same namespace
+that Coder is installed in.
 
-```sh
+```shell
 export NAMESPACE=coder
 kubectl apply -f - <<EOF
 apiVersion: v1
@@ -90,8 +110,8 @@ coder:
 
 ## Artifactory
 
-JFrog Artifactory can serve as a Terraform module registry, allowing you to simplify
-a Coder-stored template to a `module` block and input variables.
+JFrog Artifactory can serve as a Terraform module registry, allowing you to
+simplify a Coder-stored template to a `module` block and input variables.
 
 With this approach, you can:
 
@@ -114,7 +134,7 @@ Remember to replace `cdr.jfrog.io` with your Artifactory instance URL.
 
 You can upload the underlying module to Artifactory with:
 
-```console
+```shell
 # one-time setup commands
 # run this on the coder server (or external provisioners, if you have them)
 terraform login cdr.jfrog.io; jf tfc --global
@@ -125,12 +145,16 @@ jf tf p --namespace=main --provider=docker --tag=v0.0.1
 
 ### Example template
 
-We have an example template [here](https://github.com/coder/coder/tree/main/examples/templates/jfrog/remote) that uses our [JFrog Docker](../platforms/jfrog.md) template
-as the underlying module.
+We have an example template
+[here](https://github.com/coder/coder/tree/main/examples/templates/jfrog/remote)
+that uses our [JFrog Docker](../platforms/jfrog.md) template as the underlying
+module.
 
 ### Next up
 
 Learn more about
 
-- JFrog's Terraform Registry support [here](https://jfrog.com/help/r/jfrog-artifactory-documentation/terraform-registry).
-- Configuring the JFrog toolchain inside a workspace [here](../platforms/jfrog.md).
+- JFrog's Terraform Registry support
+  [here](https://jfrog.com/help/r/jfrog-artifactory-documentation/terraform-registry).
+- Configuring the JFrog toolchain inside a workspace
+  [here](../platforms/jfrog.md).