Update wording of the serverOffline message.

[KZeni]

The serverOffline message was being shown even though the site was online & working perfectly fine while it was an issue with the client's connection (while they weren't necessarily considered offline.) As such, it should mention both possibilities so people don't instantly blame the website when that might not be the cause for the issue.

[westonruter]

Thanks for.the PR. We tried to detect whether the user was offline in #190 and serve a clientOffline message in that case. Nevertheless, navigator.onLine is limited in it's effectiveness, such as to handle Lie-Fi scenarios. Is this what you experienced?

[KZeni]

I can't say for certain. I was forwarded a screenshot from a client where it was giving this message even though the site was verifiably still online & working properly for others.

[westonruter]

Were they able to access other websites successfully? Just wondering if we can also improve the Lie-Fi detection.

Can you inquire if they were trying to access the site and the request took a long time until finally it failed? One thing I want to explore is make use of service worker timeouts to short-circuit requests in these cases.

At the very least, it's true that the current onLine detection is not robust so your change makes sense.

[KZeni]

It appears they were having issues with other sites, based on their screenshot. I'll let you know if I hear any further details back.

Thanks for merging 👍