Skip to content

Commit c377d76

Browse files
authored
Enhanced formatting
1 parent c53a76c commit c377d76

1 file changed

Lines changed: 1 addition & 1 deletion

File tree

  • microsoft-edge/progressive-web-apps-chromium/how-to

microsoft-edge/progressive-web-apps-chromium/how-to/widgets.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ An existing PWA cannot simply be placed into the widget dashboard as-is, like yo
2727
See also:
2828
* [Build a PWA for the sidebar in Microsoft Edge](./sidebar.md)
2929

30-
To build a PWA-driven widget and deliver it via the Microsoft store, no C++/C# code is required. Once you've produced the widget, and can successfully install and run the widget from a public endpoint, you can package the app by using [PWABuilder.com](https://www.pwabuilder.com) and ship the app to the Microsoft store without requiring any additional code. The PWA backing the widget must be installable from a public endpoint, because PWABuilder.com doesn't support packing apps from localhost.
30+
To build a PWA-driven widget and deliver it via the Microsoft Store, no C++/C# code is required. Once you've produced the widget, and can successfully install and run the widget from a public endpoint, you can package the app by using [PWABuilder.com](https://www.pwabuilder.com) and ship the app to the Microsoft Store without requiring any additional code. The PWA backing the widget must be installable from a public endpoint, because PWABuilder doesn't support packing apps from `localhost`.
3131
<!-- The PWA (not the widget) is what is installable and packaged, because it's a standalone entity (unlike a widget). -->
3232

3333
See also:

0 commit comments

Comments
 (0)