From b58b672d77479ef95129acac880b8379aeeda42b Mon Sep 17 00:00:00 2001
From: Anthony <anthony.russo@hashicorp.com>
Date: Thu, 13 Jan 2022 17:04:19 -0500
Subject: [PATCH] Apply suggestions from code review

---
 website/content/docs/agent/sentinel.mdx | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/website/content/docs/agent/sentinel.mdx b/website/content/docs/agent/sentinel.mdx
index ec6510f12d..8344ee9957 100644
--- a/website/content/docs/agent/sentinel.mdx
+++ b/website/content/docs/agent/sentinel.mdx
@@ -23,7 +23,7 @@ An optional `sentinel` field specifying code and enforcement level can be added
 
 <CodeBlockConfig heading="Ensure values written during KV updates end in 'dc1'">
 
-```sentinel
+```go
 key "datacenter_name" {
   policy = "write"
   sentinel {
@@ -64,7 +64,7 @@ The following are two examples of ACL policies with Sentinel rules.
 
 <CodeBlockConfig heading="Any values stored under the key 'dc1' end with 'dev'">
 
-```sentinel
+```go
 key "dc1" {
     policy = "write"
     sentinel {
@@ -82,7 +82,7 @@ EOF
 
 <CodeBlockConfig heading="The key 'haproxy_version' can only be updated during business hours">
 
-```sentinel
+```go
 key "haproxy_version" {
     policy = "write"
     sentinel {