diff --git a/src/content/account/billing.md b/src/content/account/billing.md
index 9ff4d1ab..4df51bef 100644
--- a/src/content/account/billing.md
+++ b/src/content/account/billing.md
@@ -35,9 +35,9 @@ If you use our free [Publish Storybook](/docs/setup) service only you will not b
 
 Chromatic's default behavior is to capture new a snapshot for every story in every build.
 
-With [TurboSnap](/docs/turbosnap) enabled, Chromatic first analyzes the Git history and the dependency graph of your project to identify which story files or any of their dependencies have changed and only captures new snapshots for those stories. It reuses the existing snapshot for the remaining stories, which we call **TurboSnaps**.
+With [TurboSnap](/docs/turbosnap) enabled, Chromatic first analyzes the Git history and the dependency graph of your project to identify stories that have no code changes within them or their dependencies. Instead of capturing new snapshots, it intelligently reuses existing ones for these cases. These checks are referred to as **TurboSnaps**, billed at 1/5th the cost of a regular snapshot.
 
-For TurboSnaps, Chromatic doesn't have to spin up the full Capture Cloud, requiring less infrastructure resources. Therefore, they are billed at 1/5th the cost of a regular snapshot.
+For the remaining stories, Chromatic captures new snapshots as usual and bills them at the regular rate.
 
 | Story count | Browsers | Viewports | Stories w/ changes | Snapshots | TurboSnaps | Billed snapshots |
 | ----------- | -------- | --------- | ------------------ | --------- | ---------- | ---------------- |
diff --git a/src/content/turbosnap/turbosnap.mdx b/src/content/turbosnap/turbosnap.mdx
index 2bd28f5d..5e2dc028 100644
--- a/src/content/turbosnap/turbosnap.mdx
+++ b/src/content/turbosnap/turbosnap.mdx
@@ -45,9 +45,11 @@ In this case, it will search the existing builds until it finds a suitable "repl
 
 ## Pricing
 
-When TurboSnap is enabled, Chromatic performs a check to determine if there are any code changes that could affect a story. If no changes are detected, it avoids spinning up cloud browsers to capture a new snapshot. Instead, it reuses the existing snapshot, which we refer to as **TurboSnaps**.
+By enabling TurboSnap, Chromatic performs a check to identify stories that have no code changes associated with them. Instead of capturing new snapshots, it intelligently reuses existing ones for these cases. These checks are referred to as **TurboSnaps**.
 
-TurboSnaps not only speed up the test runs, they also require less infrastructure resources. We pass these savings on to you by billing TurboSnaps at only 1/5th of the cost of a regular snapshot. That's 80% savings.
+TurboSnaps not only speed up the test runs, they also require less infrastructure resources. We pass these savings on to you by billing them at 1/5th of the cost of a regular snapshot.
+
+For the remaining stories, Chromatic captures new snapshots as usual and bills them at the regular rate.
 
 For example, consider a Storybook with 50 stories. If your code changes impact 10 stories, Chromatic will capture new snapshots for those 10 stories. The cost of that build will be 18 snapshots: