diff --git a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-dtr.md b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
index 58d203e04f..a8318eaa20 100644
--- a/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
+++ b/datacenter/dtr/2.5/guides/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
@@ -67,9 +67,11 @@ On a healthy cluster the output will be `[]`.
 
 Starting in DTR 2.5.5, you can run RethinkCLI from a separate image. First, set an environment variable for your DTR replica ID:
 
+{% raw %}
 ```bash
 REPLICA_ID=$(docker inspect -f '{{.Name}}' $(docker ps -q -f name=dtr-rethink) | cut -f 3 -d '-')
 ```
+{% endraw %}
 
 RethinkDB stores data in different databases that contain multiple tables. Run the following command to get into interactive mode
 and query the contents of the DB:
diff --git a/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-dtr.md b/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
index 58d203e04f..a8318eaa20 100644
--- a/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
+++ b/ee/dtr/admin/monitor-and-troubleshoot/troubleshoot-dtr.md
@@ -67,9 +67,11 @@ On a healthy cluster the output will be `[]`.
 
 Starting in DTR 2.5.5, you can run RethinkCLI from a separate image. First, set an environment variable for your DTR replica ID:
 
+{% raw %}
 ```bash
 REPLICA_ID=$(docker inspect -f '{{.Name}}' $(docker ps -q -f name=dtr-rethink) | cut -f 3 -d '-')
 ```
+{% endraw %}
 
 RethinkDB stores data in different databases that contain multiple tables. Run the following command to get into interactive mode
 and query the contents of the DB: