From 4d9b3b181a88212eeef17f3d5507035706ef4ce3 Mon Sep 17 00:00:00 2001 From: Emmanuel Lucius <58217705+Emmaccen@users.noreply.github.com> Date: Sat, 27 Jul 2024 01:27:41 +0100 Subject: [PATCH] Fixed a typo in `Offline Fallbacks` README.md section ### Description Fixed a typo in `Offline Fallbacks` README.md section by correcting: * "fetch failed from both cache and network" to "fetching from both the cache and the network fails" for better readability and correct verb tense. * "present an error from browser" to "presenting an error from the browser" to maintain parallel structure and correct the article usage. ### Motivation This change improves the readability and accuracy of the documentation, ensuring that users have a clear and correct understanding of the content. ### Additional details Direct ref can be found here: https://github.com/shadowwalker/next-pwa#offline-fallbacks --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 5fa5c72c..92b67db7 100644 --- a/README.md +++ b/README.md @@ -206,7 +206,7 @@ Add the following into `_document.jsx` or `_app.tsx`, in ``: ## Offline Fallbacks -Offline fallbacks are useful when the fetch failed from both cache and network, a precached resource is served instead of present an error from browser. +Offline fallbacks are useful when fetching from both the cache and the network fails; a precached resource is served instead of presenting an error from the browser. To get started simply add a `/_offline` page such as `pages/_offline.js` or `pages/_offline.jsx` or `pages/_offline.ts` or `pages/_offline.tsx`. Then you are all set! When the user is offline, all pages which are not cached will fallback to '/\_offline'.