Editorial: s/PWA/website/

As annevk@ suggested in privacycg/proposals#39.

index.bs

@@ -198,8 +198,8 @@ origin, as is storage, and potential server-side interrelations between pages ar
 user. Site operators are encouraged to make such a global policy available.
 
 It's important to note, however, that websites might host privacy policies for applications that
-run outside the context of the web platform. `https://amazing-mobile-app.example` might offer a PWA
-alongside native apps on multiple platforms with differing data collection and usage
+run outside the context of the web platform. `https://amazing-mobile-app.example` might offer a
+website alongside native apps on multiple platforms with differing data collection and usage
 characteristics. In this case, clients should expect `/.well-known/privacy-policy` to represent the
 privacy policy that applies to the web origin.
 

index.html

@@ -8,7 +8,7 @@
   <meta content="Bikeshed version 63e66730b, updated Tue Oct 25 12:35:05 2022 -0700" name="generator">
   <link href="https://mikewest.github.io/privacy-policy-discovery/" rel="canonical">
   <link href="https://www.w3.org/2008/site/images/favicon.ico" rel="icon">
-  <meta content="347bd6b004e3f93f2744499375e5bbe5edefdf8e" name="document-revision">
+  <meta content="6a56f1c06aea43d2a4f4d8933f1cf2ab319f3d88" name="document-revision">
 <style>/* style-autolinks */
 
 .css.css, .property.property, .descriptor.descriptor {
@@ -781,8 +781,8 @@ <h3 class="heading settled" data-level="4.1" id="scope"><span class="secno">4.1.
 origin, as is storage, and potential server-side interrelations between pages are opaque to the
 user. Site operators are encouraged to make such a global policy available.</p>
    <p>It’s important to note, however, that websites might host privacy policies for applications that
-run outside the context of the web platform. <code>https://amazing-mobile-app.example</code> might offer a PWA
-alongside native apps on multiple platforms with differing data collection and usage
+run outside the context of the web platform. <code>https://amazing-mobile-app.example</code> might offer a
+website alongside native apps on multiple platforms with differing data collection and usage
 characteristics. In this case, clients should expect <code>/.well-known/privacy-policy</code> to represent the
 privacy policy that applies to the web origin.</p>
    <p class="note" role="note"><span>Note:</span> It would be possible to extend this proposal with specific well-known links for privacy