Merge pull request mendix#10903 from nikolai-paramonov/off/846-clarify-text-about-service-worker-registration

[OFF-846]: Clarify text about service worker and HTTPS limitations

Author: ConnorLand

content/en/docs/refguide/mobile/introduction-to-mobile-technologies/progressive-web-app.md

@@ -34,7 +34,7 @@ Within the navigation profiles the following PWA features can be configured:
 
 {{< figure src="/attachments/refguide/mobile/progressive-web-app/settings.png" alt="PWA settings"   width="350"  class="no-border" >}}
 
-To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because the service worker is only enabled in the cloud over HTTPS.
+To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because some PWA features are only available over HTTPS protocol. For more information, see [Accessing Device Features](#accessing-device-features) below.
 
 ### Publishing as a Progressive Web App
 
@@ -130,7 +130,7 @@ Offline-first PWAs use an authentication token by default to keep the session ac
 
 For more information on the session and authentication tokens, see [Session Management](/refguide/session-management/)
 
-## Accessing Device Features
+## Accessing Device Features {#accessing-device-features}
 
 Browsers offer access to device features through APIs that can be leveraged in PWAs. These device features can be used by available widgets and nanoflow actions. It is also possible to leverage additional device features by extending the platform using [JavaScript Actions](/refguide/javascript-actions/) or [Pluggable Widgets](/howto/extensibility/pluggable-widgets/).
 

content/en/docs/refguide10/mobile/introduction-to-mobile-technologies/progressive-web-app.md

@@ -44,7 +44,7 @@ Within the navigation profiles the following PWA features can be configured:
 
 {{< figure src="/attachments/refguide10/mobile/progressive-web-app/settings.png" alt="PWA settings"   width="350"  class="no-border" >}}
 
-To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because the service worker is only enabled in the cloud over HTTPS.
+To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because some PWA features are only available over HTTPS protocol. For more information, see [Accessing Device Features](#accessing-device-features) below.
 
 ### Publishing as a Progressive Web App
 
@@ -148,7 +148,7 @@ Offline-first PWAs use long-lived sessions, which keep users logged in for a lon
 
 For more information on sessions and how to customize the timeout, see the [Session Duration](/refguide10/tricky-custom-runtime-settings/#session-duration) section of the *Advanced Custom Settings in Mendix Runtime Reference Guide*.
 
-## Accessing Device Features
+## Accessing Device Features {#accessing-device-features}
 
 Browsers offer access to device features through APIs that can be leveraged in PWAs. These device features can be used by available widgets and nanoflow actions. It is also possible to leverage additional device features by extending the platform using [JavaScript Actions](/refguide10/javascript-actions/) or [Pluggable Widgets](/howto10/extensibility/pluggable-widgets/).
 

content/en/docs/refguide9/mobile/introduction-to-mobile-technologies/progressive-web-app.md

@@ -38,7 +38,7 @@ Within the navigation profiles the following PWA features can be configured:
 
 {{< figure src="/attachments/refguide9/mobile/progressive-web-app/settings.png" alt="PWA settings"   width="350"  class="no-border" >}}
 
-To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because the service worker is only enabled in the cloud over HTTPS.
+To be able to fully test PWA functionalities, the app needs to be deployed to the cloud. This is because some PWA features are only available over HTTPS protocol. For more information, see [Accessing Device Features](#accessing-device-features) below.
 
 ### Publishing as a Progressive Web App
 
@@ -130,7 +130,7 @@ Offline-first PWAs use long-lived sessions, which keep users logged in for a lon
 
 For more information on sessions and how to customize the timeout, see the [Session Duration](/refguide9/tricky-custom-runtime-settings/#session-duration) section of the *Advanced Custom Settings in Mendix Runtime Reference Guide*.
 
-## Accessing Device Features
+## Accessing Device Features {#accessing-device-features}
 
 Browsers offer access to device features through APIs that can be leveraged in PWAs. These device features can be used by available widgets and nanoflow actions. It is also possible to leverage additional device features by extending the platform using [JavaScript Actions](/refguide9/javascript-actions/) or [Pluggable Widgets](/howto9/extensibility/pluggable-widgets/).