From af4e910d0c3c1df3996e3442398fd1b5a11679e4 Mon Sep 17 00:00:00 2001 From: winkerVSbecks Date: Mon, 29 Jan 2024 21:36:48 -0500 Subject: [PATCH] adjust phrasing --- src/content/account/billing.md | 4 ++-- src/content/turbosnap/turbosnap.mdx | 4 ++-- 2 files changed, 4 insertions(+), 4 deletions(-) diff --git a/src/content/account/billing.md b/src/content/account/billing.md index 4df51bef..6612e85d 100644 --- a/src/content/account/billing.md +++ b/src/content/account/billing.md @@ -35,7 +35,7 @@ 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 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. +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 copies over the snapshots from existing baselines that didn't change. These duplicated snapshots are referred to as **TurboSnaps**, 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. @@ -47,7 +47,7 @@ For the remaining stories, Chromatic captures new snapshots as usual and bills t | 50 stories | 2 | 1 | 10 | 20 | 80 | 36 | | 50 stories | 2 | 2 | 10 | 40 | 160 | 72 | -Note: your monthly [usage reports](/docs/billing/#usage-reports) will include a breakdown of regular snapshots vs TurboSnaps. +Note: your [billing page](/docs/billing#view-current-months-usage) will include a breakdown of regular snapshots vs TurboSnaps. ### How we count snapshots diff --git a/src/content/turbosnap/turbosnap.mdx b/src/content/turbosnap/turbosnap.mdx index 5e2dc028..1174cfa7 100644 --- a/src/content/turbosnap/turbosnap.mdx +++ b/src/content/turbosnap/turbosnap.mdx @@ -7,7 +7,7 @@ sidebar: { order: 1 } # Introduction to TurboSnap -TurboSnap is an advanced Chromatic feature that speeds up [UI Tests](/docs/test). It analyzes your project's Git history and Webpack's [dependency graph](https://webpack.js.org/concepts/dependency-graph/) to identify which components and their dependencies have changed. It intelligently snapshots only the stories associated with those changes. +TurboSnap is an advanced Chromatic feature that speeds up [UI Tests](/docs/test). It analyzes your project's Git history and Webpack's [dependency graph](https://webpack.js.org/concepts/dependency-graph/) to identify which components and their dependencies have changed. It intelligently snapshots only the stories associated with those changes. For the rest, it copies over the snapshots from baselines that didn't change. ![TurboSnap tracks dependencies](../../images/turbosnap-dep-tracking.gif) @@ -45,7 +45,7 @@ In this case, it will search the existing builds until it finds a suitable "repl ## Pricing -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**. +By enabling TurboSnap, Chromatic performs a check to identify stories that have no code changes associated with them. Instead of capturing new snapshots, it duplicates snapshots from existing baselines in such cases. We refer to these duplicated snapshots 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 them at 1/5th of the cost of a regular snapshot.