repo sync public>private

Author: jwmsft

windows.applicationmodel.store/currentapp_getproductreceiptasync_1023308114.md

@@ -14,7 +14,7 @@ Requests the receipt for the specified product ID. For examples of how receipt i
 
 ## -parameters
 ### -param productId
-The unique identifier for the product that you specified this identifier when you submitted the app to the Microsoft Store
+The unique identifier for the product that you specified when you submitted the app to the Microsoft Store
 
 ## -returns
 An XML-formatted string that contains the receipt for the specified *productId.*

windows.networking.connectivity/dataplanstatus.md

@@ -56,41 +56,6 @@ If `DataPlanStatus` is null or critical fields are missing:
 > to sensible minimums before applying heuristics.
 
 
-### Null handling
-> [!IMPORTANT]  
-> Always null‑check the returned **DataPlanStatus**. Some profiles (for example unmanaged Wi‑Fi hotspots) do not expose
-> plan information and return null.
-
-### Core elements
-| Property | Meaning / Guidance |
-| -- | -- |
-| [DataPlanUsage](dataplanusage.md) | Current measured usage (may lag real traffic) |
-| DataLimitInMegabytes | Plan cap (nullable). Null => unspecified limit (do not assume unlimited) |
-| MaxTransferSizeInMegabytes | Recommended maximum size for a single transfer (chunk large sync into segments) |
-| NextBillingCycle | Start of next cycle (nullable). Do not assume calendar month boundaries |
-
-### Quota logic guidelines
-- Interpret **DataPlanUsage** together with **DataLimitInMegabytes**. A missing limit means you cannot enforce a hard cap safely.
-- Use both percentage consumed and time remaining before throttling; early-cycle high usage does not always justify restriction.
-- Treat missing **DataLimitInMegabytes** as "unspecified" rather than "unlimited".
-
-### Transfer optimization
-- Honor **MaxTransferSizeInMegabytes** by batching work into chunks at or below the recommendation.
-- For background sync on metered or limited plans, schedule incremental commits instead of monolithic uploads.
-
-### Billing cycle handling
-- **NextBillingCycle** may be absent; fall back to rolling usage display without reset logic.
-- When present, derive remaining quota window precisely; operators define custom cycle boundaries.
-
-### Fallback behavior
-If **DataPlanStatus** is null or critical fields are missing:
-- Present generic usage UI without enforcement.
-- Allow user override for "treat as metered" or "treat as unrestricted" preferences if your app supports it.
-
-> [!NOTE]  
-> Defensive coding: Providers can report unexpected values (like zero or very small **MaxTransferSizeInMegabytes**). Clamp
-> to sensible minimums before applying heuristics.
-
 
 ## -examples
 ### Example (C#):

windows.storage/pathio_writebytesasync_1599878576.md

@@ -10,7 +10,8 @@ public Windows.Foundation.IAsyncAction WriteBytesAsync(System.String absolutePat
 # Windows.Storage.PathIO.WriteBytesAsync
 
 ## -description
-Writes a single byte of data to the file at the specified path or Uniform Resource Identifier (URI).
+
+Writes an array of bytes of data to the file at the specified path or Uniform Resource Identifier (URI).
 
 ## -parameters
 ### -param absolutePath

windows.system.profile/analyticsinfo_getsystempropertiesasync_364490553.md

@@ -26,7 +26,8 @@ Supported values for the *attributeNames* parameter are potentially endless. The
 * AppVer  
 * DeviceFamily  
 * FlightRing  
-* OSVersionFull  
+* OSVersionFull
+* n:TriggeredFlightIds
 
 The intention of this method is to use this information only for analytics and not rely on a particular value on the client. Support for these values will change over time.