From 9fa89f86268fbce34537049baea225c7921c8dec Mon Sep 17 00:00:00 2001 From: Schalk Venter Date: Thu, 18 Mar 2021 20:57:37 +0200 Subject: [PATCH] Update making-a-progressive-web-app.md --- docusaurus/docs/making-a-progressive-web-app.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docusaurus/docs/making-a-progressive-web-app.md b/docusaurus/docs/making-a-progressive-web-app.md index 649fb9cb320..071b076336f 100644 --- a/docusaurus/docs/making-a-progressive-web-app.md +++ b/docusaurus/docs/making-a-progressive-web-app.md @@ -122,8 +122,7 @@ following into account: for more details about this behavior. 1. Users aren't always familiar with offline-first web apps. It can be useful to - [let the user know](https://developers.google.com/web/fundamentals/instant-and-offline/offline-ux#inform_the_user_when_the_app_is_ready_for_offline_consumption) - when the service worker has finished populating your caches (showing a "This web + [let the user know](https://web.dev/offline-ux-design-guidelines/#inform-the-user-when-the-app-is-ready-for-offline-consumption) when the service worker has finished populating your caches (showing a "This web app works offline!" message) and also let them know when the service worker has fetched the latest updates that will be available the next time they load the page (showing a "New content is available once existing tabs are closed." message). Showing