Address Copilot review feedback on PR #6618

- push-quickstart.md: Clarify packaging intro — unpackaged is supported
  but package identity is required for background delivery/COM activation
- notifications/index.md: Align push bullet wording with quickstart
  (limited unpackaged path; packaging required for background delivery)
- wns-overview.md: Fix typo 'x-www-for-urlencoded' -> 'x-www-form-urlencoded'
- wns-overview.md: Fix grammar 'We recommended' -> 'We recommend'

Co-authored-by: Copilot <[email protected]>

Author: GrantMeStrength

hub/apps/develop/notifications/index.md

@@ -56,7 +56,7 @@ For a full breakdown of delivery methods, see [Choose a notification delivery me
 
 **Building a WPF or WinForms app?**
 - [App notifications quickstart](app-notifications/app-notifications-quickstart.md) — local toast notifications work packaged or unpackaged
-- [Push notifications quickstart](push-notifications/push-quickstart.md) — WNS push requires MSIX packaging or packaged with external location
+- [Push notifications quickstart](push-notifications/push-quickstart.md) — WNS push supports a limited truly unpackaged path, but packaging (MSIX or packaged with external location) is required for background delivery and COM activation
 
 > [!IMPORTANT]
 > Windows App SDK push notifications require an [Azure account](https://azure.microsoft.com/pricing/purchase-options/azure-account) and an **Azure AD app registration**. If your app is packaged, you also need to submit a Package Family Name (PFN) mapping request by email — allow for **up to one week** of processing time before launch. See the [push notifications quickstart](push-notifications/push-quickstart.md) for full prerequisites.

hub/apps/develop/notifications/push-notifications/push-quickstart.md

@@ -23,7 +23,7 @@ In this quickstart you will create a desktop Windows application that sends and
 
 ## Packaging requirements
 
-Push notifications in Windows App SDK require that your app has package identity. The following table summarizes what's required based on your packaging model:
+Push notifications in the Windows App SDK support both packaged and truly unpackaged desktop apps. However, **package identity is required for background delivery and COM activation** — the most common production scenario. The following table summarizes what's required based on your packaging model:
 
 | Packaging model | COM activator required | PFN mapping required | Unpackaged supported |
 |---|---|---|---|

hub/apps/develop/notifications/push-notifications/wns-overview.md

@@ -61,7 +61,7 @@ At a high level, the information chain is as follows:
 
 ![wns diagram for cloud service authentication](images/wns-diagram-02.jpg)
 
-In the authentication with WNS, the cloud service submits an HTTP request over Secure Sockets Layer (SSL). The parameters are supplied in the "application/x-www-for-urlencoded" format. Supply your Package SID in the "client\_id" field and your secret key in the "client\_secret" field as shown in the following example. For syntax details, see the [access token request](push-request-response-headers.md) reference.
+In the authentication with WNS, the cloud service submits an HTTP request over Secure Sockets Layer (SSL). The parameters are supplied in the "application/x-www-form-urlencoded" format. Supply your Package SID in the "client\_id" field and your secret key in the "client\_secret" field as shown in the following example. For syntax details, see the [access token request](push-request-response-headers.md) reference.
 
 > [!NOTE]
 > This is just an example, not cut-and-paste code that you can successfully use in your own code. 
@@ -103,7 +103,7 @@ The following example shows a successful authentication response, including the
 
 Using the channel URI, the cloud service can send a notification whenever it has an update for the user.
 
-The access token described above can be reused for multiple notification requests; the cloud server is not required to request a new access token for every notification. If the access token has expired, the notification request will return an error. We recommended that you do not try to re-send your notification more than once if the access token is rejected. If you encounter this error, you will need to request a new access token and resend the notification. For the exact error code, see [Push notification service request and response headers](push-request-response-headers.md).
+The access token described above can be reused for multiple notification requests; the cloud server is not required to request a new access token for every notification. If the access token has expired, the notification request will return an error. We recommend that you do not try to re-send your notification more than once if the access token is rejected. If you encounter this error, you will need to request a new access token and resend the notification. For the exact error code, see [Push notification service request and response headers](push-request-response-headers.md).
 
 1.  The cloud service makes an HTTP POST to the channel URI. This request must be made over SSL and contains the necessary headers and the notification payload. The authorization header must include the acquired access token for authorization.