diff --git a/src/content/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx b/src/content/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx
index 9e63d0f66b2..244a25f899a 100644
--- a/src/content/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx
+++ b/src/content/docs/data-apis/convert-to-metrics/analyze-monitor-data-trends-metrics.mdx
@@ -229,7 +229,7 @@ Mutation operations for events to metrics, logs to metrics, or spans to metrics
             {
               "id": "12",
               "name": "Test Rule",
-              "nrql": "select summary(duration) as 'server.responseTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+              "nrql": "SELECT summary(duration) AS 'server.responseTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
             }
           ]
         }
@@ -484,14 +484,14 @@ Query operations include:
                     "enabled": true,
                     "id": "1",
                     "name": "Total Time Tx",
-                    "nrql": "select summary(totalTime) as 'server.totalTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(totalTime) AS 'server.totalTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   },
                   {
                     "description": "Metric for duration",
                     "enabled": true,
                     "id": "2",
                     "name": "Duration Rule",
-                    "nrql": "select summary(duration) as 'server.responseTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(duration) AS 'server.responseTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   }
                 ]
               }
@@ -554,7 +554,7 @@ Query operations include:
                     "enabled": true,
                     "id": "36",
                     "name": "Total Time Tx",
-                    "nrql": "select summary(totalTime) as 'server.totalTime' from Transaction where appName = 'Data Points Staging' facet name, appName, host"
+                    "nrql": "SELECT summary(totalTime) AS 'server.totalTime' FROM Transaction WHERE appName = 'Data Points Staging' FACET name, appName, host"
                   }
                 ]
               }
diff --git a/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx b/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx
index 978660f7fbd..151f0a6397c 100644
--- a/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx
+++ b/src/content/docs/data-apis/convert-to-metrics/create-metrics-other-data-types.mdx
@@ -282,8 +282,13 @@ The available [NRQL aggregator functions](/docs/insights/nrql-new-relic-query-la
   >
     If you created a summary metric type, you can use the `count`, `sum`, `max`, `min`, and `average` aggregator functions, as shown in the following query:
 
-    ```
-    SELECT count(appStartResponseTime), sum(appStartResponseTime), max(appStartResponseTime), min(appStartResponseTime),  average(appStartResponseTime) FROM Metric
+    ```sql
+    SELECT count(appStartResponseTime), 
+      sum(appStartResponseTime), 
+      max(appStartResponseTime), 
+      min(appStartResponseTime), 
+      average(appStartResponseTime) 
+    FROM Metric
     ```
   </Collapser>
 
diff --git a/src/content/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx b/src/content/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx
index b95e65d0546..fb5ba7a3203 100644
--- a/src/content/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx
+++ b/src/content/docs/infrastructure/install-infrastructure-agent/linux-installation/tarball-manual-install-infrastructure-agent-linux.mdx
@@ -149,10 +149,10 @@ Before you proceed to install the service script, you need to determine which se
       <Callout variant="tip">
         For example, run the following sequence:
 
-        ```
-        $ command -v systemctl
-        $ command -v initctl
-        /sbin/initctl
+        ```sh
+        command -v systemctl
+        command -v initctl
+        [output] /sbin/initctl
         ```
 
         Based on this output, Upstart is the service manager, since it's the command that obtained a return.