From b0c605388d4124189c95216d94d8867223885cf3 Mon Sep 17 00:00:00 2001 From: Howard Chiam Date: Sun, 23 Jul 2023 23:32:00 -0600 Subject: [PATCH] minor grammar fix on service-workers page --- src/site/content/en/learn/pwa/service-workers/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/site/content/en/learn/pwa/service-workers/index.md b/src/site/content/en/learn/pwa/service-workers/index.md index da7e0165a1c..611cd2c240c 100644 --- a/src/site/content/en/learn/pwa/service-workers/index.md +++ b/src/site/content/en/learn/pwa/service-workers/index.md @@ -112,7 +112,7 @@ When updating your service worker, do so without renaming it. Do not even add fi {% endAside %} After a successful installation, the new service worker will wait to activate until the existing (old) service worker no longer controls any clients. This state is called "waiting", and it's how the browser ensures that only one version of your service worker is running at a time. -Refreshing a page or reopening the PWA won't make the new service worker take control. The user needs to close or navigate away from all tabs and windows using the current service worker and then navigate back. Only then will the new service worker to take control. +Refreshing a page or reopening the PWA won't make the new service worker take control. The user needs to close or navigate away from all tabs and windows using the current service worker and then navigate back. Only then will the new service worker take control. Visit this [service worker lifecycle article](/service-worker-lifecycle/) for more information. ## Service worker lifespan