From 048235cb51b7ebf41f76e86ea158d621ba34dcf5 Mon Sep 17 00:00:00 2001 From: jonniebigodes Date: Fri, 18 Oct 2024 11:46:51 +0100 Subject: [PATCH] Minor tweak --- src/content/snapshotOptions/font-loading.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/content/snapshotOptions/font-loading.md b/src/content/snapshotOptions/font-loading.md index 395f0571..c3e26633 100644 --- a/src/content/snapshotOptions/font-loading.md +++ b/src/content/snapshotOptions/font-loading.md @@ -9,7 +9,7 @@ sidebar: { order: 2 } Browsers can decide to render HTML in multiple passes when custom fonts are used. They do this to speed up the time-to-first-meaningful-paint. -Unfortunately, this behavior can cause your story to render without the custom font. Or worse, render inconsistently. That triggers font rendering changes that you have to accept again and again. Here are ways to prevent that. +Unfortunately, this behavior can cause your tests to render without the custom font or, worse, render inconsistently. That triggers font rendering changes that you have to accept again and again. Here are ways to prevent that. ## Best practice: Fallback to web-safe fonts