diff --git a/website/content/docs/commands/job/run.mdx b/website/content/docs/commands/job/run.mdx
index d2ea4fa64..850853ff2 100644
--- a/website/content/docs/commands/job/run.mdx
+++ b/website/content/docs/commands/job/run.mdx
@@ -86,7 +86,7 @@ that volume.
 - `-consul-namespace`: <EnterpriseAlert inline/> If set, any services in the job will be registered into the
   specified Consul namespace. Any `template` stanza reading from Consul KV will
   scoped to the the specified Consul namespace. If Consul ACLs are enabled and the
-  [allow_unauthenticated] Nomad server Consul configuration is not enabled, then
+  [`allow_unauthenticated`] Nomad server Consul configuration is not enabled, then
   a Consul token must be supplied with appropriate service and kv Consul ACL policy
   permissions.
 
@@ -157,4 +157,4 @@ $ nomad job run failing.nomad
 [`job plan` command]: /docs/commands/job/plan
 [eval status]: /docs/commands/eval-status
 [job specification]: /docs/job-specification
-[allow_unauthenticated]: /docs/configuration/consul#allow_unauthenticated
+[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
diff --git a/website/content/docs/integrations/consul-integration.mdx b/website/content/docs/integrations/consul-integration.mdx
index 7e4678870..9b90999be 100644
--- a/website/content/docs/integrations/consul-integration.mdx
+++ b/website/content/docs/integrations/consul-integration.mdx
@@ -70,7 +70,7 @@ The Consul namespace used for a set of group or task service registrations withi
 a group, as well as `template` KV store access is determined from the following
 hierarchy from lowest to highest precedence:
 
-- consul default: If no Consul namespace options are configured, Consul will automatically
+- Consul default: If no Consul namespace options are configured, Consul will automatically
   make use of the `"default"` namespace.
 
 - agent configuration: If the [`namespace`][consul_agent_namespace] Nomad agent
@@ -85,7 +85,7 @@ hierarchy from lowest to highest precedence:
   Consul namespace is configured, this namespace will take precedence over all other
   options.
 
-If [Consul ACLs][consul_acls] are enabled, the [allow_unauthenticated] configuration parameter
+If [Consul ACLs][consul_acls] are enabled, the [`allow_unauthenticated`] configuration parameter
 will control whether a Consul token will be required when submitting a job with
 Consul namespace configured. The provided Consul token must belong to the correct
 namespace, and must be backed by a Consul ACL Policy with sufficient `service:write`
@@ -121,7 +121,7 @@ service_prefix "" {
   way is to run the container in the host networking mode, or make the Consul
   agent listen on an interface in the network namespace of the container.
 
-[allow_unauthenticated]: /docs/configuration/consul#allow_unauthenticated
+[`allow_unauthenticated`]: /docs/configuration/consul#allow_unauthenticated
 [consul]: https://www.consul.io/ 'Consul by HashiCorp'
 [consul_acls]: https://www.consul.io/docs/security/acl
 [consul_namespaces]: https://www.consul.io/docs/enterprise/namespaces