diff --git a/docs/tutorials/best-practices/scale-coder.md b/docs/tutorials/best-practices/scale-coder.md
index 7fbb55c10aa20..e961a8873a73c 100644
--- a/docs/tutorials/best-practices/scale-coder.md
+++ b/docs/tutorials/best-practices/scale-coder.md
@@ -17,15 +17,15 @@ deployment.
 
 - Log output
   - Capture log output from from Coder Server instances and external provisioner daemons
-  and store them in a searchable log store like Loki, CloudWatch logs, or other tools.
+    and store them in a searchable log store like Loki, CloudWatch logs, or other tools.
   - Retain logs for a minimum of thirty days, ideally ninety days.
   This allows you investigate when anomalous behaviors began.
 
 - Metrics
   - Capture infrastructure metrics like CPU, memory, open files, and network I/O for all
-  Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances.
+    Coder Server, external provisioner daemon, workspace proxy, and PostgreSQL instances.
   - Capture Coder Server and External Provisioner daemons metrics
-  [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus).
+    [via Prometheus](#how-to-capture-coder-server-metrics-with-prometheus).
 
 Retain metric time series for at least six months. This allows you to see
 performance trends relative to user growth.
@@ -47,7 +47,7 @@ they affect the end-user experience.
 
 - Tail latency of Coder Server API requests
   - High tail latency can indicate Coder Server or the PostgreSQL database is underprovisioned
-  for the load.
+    for the load.
   - Use the `coderd_api_request_latencies_seconds` metric.
 
 - Tail latency of database queries