add PWA wrapper improvement

Author: ConnorLand

content/en/docs/releasenotes/studio-pro/11/11.12.md

@@ -71,26 +71,30 @@ The **Module ID** and **checksum** are stored in a new *manifest.json* file insi
 - We fixed memory leaks that could cause increased memory consumption over time when using the App Explorer.
 - We improved the performance of several editors (Page Editor, Workflow Editor, Microflow Editor and the new Domain Model Editor)
 
+#### Progressive Web App Wrappers
+
+* Progressive web app (PWA) wrappers are now in GA. This feature allows you to package a PWA as a native app, and is especially useful when you want to keep a web-based application architecture while distributing the app through app stores. For more information, see [PWA Wrapper](/refguide/mobile/pwa-wrapper/). 
+
 #### Other Improvements
-            
+          
 - The **History** pane now shows the author name instead of the author email for each commit. The email address is still visible by hovering over the author name.
 - We added the `forRemoval` and `since` attributes to the public Java API deprecated annotations.
 - We improved performance of Studio Pro especially for App Explorer operations such as right mouse click, double click to open, etc.
 - We updated the .NET Runtime to version 10.0.7.
 - We added a confirmation dialog when enabling anonymous user access in App Security, warning that unrestricted anonymous roles may expose data unintentionally.
-- Allow Microflow and Entity parameters to be optional for Java actions.
+- We now allow microflow and entity parameters to be optional for Java actions.
 - We renamed the Tracing tab to OpenTelemetry in the configurations in Studio Pro.
 - We added the option to enable logs to be sent via OpenTelemetry in the OpenTelemetry configuration in Studio Pro.
 - The endpoint in the OpenTelemetry configuration is now used for both traces and logs and should not end in "/v1/traces" anymore. It will be automatically updated during migration.
 - Maia can now use system member properties of entities
 - We reorganized AI preferences into separate tabs for better clarity. Maia settings and MCP Server settings are now displayed in their own dedicated tabs, making it easier to find and configure AI-related features.
 - We improved the published REST service editor in Studio Pro. Form parameters cannot be a List, so Studio Pro no longer shows that as an option.
 - **Find Advanced** now displays widgets grouped by platform type and ordered by name.
-- The modernized JavaScript Action Editor is now enabled by default in Studio Pro. If you encounter any issues, you can revert to the legacy editor via `Preferences` > `New Features` > `Use the legacy JavaScript Action editor`.
+- The modernized JavaScript Action Editor is now enabled by default in Studio Pro. If you encounter any issues, you can revert to the legacy editor via **Preferences** > **New Features** > **Use the legacy JavaScript Action editor**.
 - We improved cleanup of queued tasks that are owned by missing nodes.
 - We improved observability for retrieve and other runtime operations by including XPath constraints, entity paths, object types, and microflow names in OpenTelemetry span names.
 - Runtime nodes now automatically shut down when heartbeat updates fail or when the node's database entry is missing, improving cluster reliability and preventing orphaned nodes.
-- Studio Pro will now always overwrite files from the vendorlib directory when importing modules.
+- Studio Pro will now always overwrite files from the `vendorlib` directory when importing modules.
 - We improved the Comparison pane toolbar to show the compared revision hashes as clickable links for version-controlled apps, allowing you to navigate directly to the corresponding commit in the History pane.
 - We added the `com.mendix.metrics.Metric.Builder.withTags(Map<String,String>)` method to the public Java API. Using this method you can add multiple tags at once to a metric builder.
 - You can now compare two revisions directly from the History Pane by selecting two commits and using the new Compare submenu in the context menu or the Compare toolbar dropdown.