A correction (#4111)

* A correction

* Sorry, the word was 'most'

Author: stevewhims

hub/apps/desktop/modernize/desktop-to-uwp-supported-api.md

@@ -1,7 +1,7 @@
 ---
 description: This article describes WinRT APIs that aren't supported for use in desktop apps, or that have restrictions.
 title: Windows Runtime APIs not supported in desktop apps
-ms.date: 09/16/2022
+ms.date: 02/27/2024
 ms.topic: article
 keywords: windows 10, uwp
 ms.assetid: 142b9c9b-3f7d-41b6-80da-1505de2810f9
@@ -125,7 +125,7 @@ The following classes are supported in desktop apps, except for the specified me
 
 #### Methods that use the Request naming pattern
 
-Methods that follow the **Request** naming pattern—such as [**AppCapability.RequestAccessAsync**](/uwp/api/windows.security.authorization.appcapabilityaccess.appcapability.requestaccessasync) and [**StoreContext.RequestPurchaseAsync**](/uwp/api/windows.services.store.storecontext.requestpurchaseasync)—aren't supported in desktop apps. Internally, these methods use the [**Windows.UI.Popups**](/uwp/api/windows.ui.popups) class. That class requires that the thread have a [**CoreWindow**](/uwp/api/Windows.UI.Core.CoreWindow) object, which isn't supported in desktop apps.
+Most methods that follow the **Request** naming pattern—such as [**AppCapability.RequestAccessAsync**](/uwp/api/windows.security.authorization.appcapabilityaccess.appcapability.requestaccessasync) and [**StoreContext.RequestPurchaseAsync**](/uwp/api/windows.services.store.storecontext.requestpurchaseasync)—aren't supported in desktop apps. Internally, these methods use the [**Windows.UI.Popups**](/uwp/api/windows.ui.popups) class. That class requires that the thread have a [**CoreWindow**](/uwp/api/Windows.UI.Core.CoreWindow) object, which isn't supported in desktop apps.
 
 The full list of methods that follow the **Request** naming pattern is very long, and this article doesn't provide a comprehensive list of those methods.