diff --git a/content/docs/introduction/scale-to-zero.md b/content/docs/introduction/scale-to-zero.md
index 6fe3a41254..6bba08a11e 100644
--- a/content/docs/introduction/scale-to-zero.md
+++ b/content/docs/introduction/scale-to-zero.md
@@ -7,12 +7,12 @@ enableTableOfContents: true
 updatedOn: '2024-08-06T15:23:10.952Z'
 ---
 
-Neon's *Scale to Zero* feature suspends the Neon compute that runs your Postgres database after a period of inactivity, which minimizes costs for databases that aren’t always active, such as development or test environment databases — and even production databases that aren't used 24/7.
+Neon's _Scale to Zero_ feature suspends the Neon compute that runs your Postgres database after a period of inactivity, which minimizes costs for databases that aren’t always active, such as development or test environment databases — and even production databases that aren't used 24/7.
 
 - When your database is inactive, it automatically scales to zero after 5 minutes. This means you pay only for active time instead of 24/7 compute usage. No manual intervention is required.
 - Once you query the database again, it reactivates automatically within a few hundred milliseconds.
 
-The diagram below illustrates the *Scale to Zero* behavior alongside Neon's *Autoscaling* feature. The compute usage line highlights an _inactive_ period, followed by a period where the compute is automatically suspended until it's accessed again.
+The diagram below illustrates the _Scale to Zero_ behavior alongside Neon's _Autoscaling_ feature. The compute usage line highlights an _inactive_ period, followed by a period where the compute is automatically suspended until it's accessed again.
 
 ![Compute metrics graph](/docs/introduction/compute-usage-graph.jpg)