MSIX app submission doc fixes (#4113)

* fixes for MSIX docs

* Additional fixes

* Additional fixes

Author: AnkurSinganjude

hub/apps/publish/package-flights.md

@@ -15,7 +15,7 @@ With package flights, only the packages are different; the Store listing details
 
 Note that the [certification process](publish-your-app/app-certification-process.md?pivots=store-installer-msix) is applied to package flights just the same as any submission, however some WACK failures are reported as **passing with notes** and will allow submission for flighting. This relaxation of the WACK checks is only while the package is flighting to a limited audience and is intended  to assist with package testing and preparation for release. WACK failures must be fixed before general release.   
 
-When you set up package flights, you can specify the people who should get specific packages by adding them to a **known user group** (sometimes referred to as flight group). Anyone in a flight group who is using a device running a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later; Windows.Mobile build 10586.63 or later; or Xbox One) will get the packages from the package flight(s) that you designate for that particular group. (Your package flights can include packages targeting any OS version, including Windows 8.1/Windows Phone 8.1 or earlier if your previously-published app already supports them.) Anyone who has not been added to one of your flight groups, or is using a device that doesn’t support package flights, will get packages from the non-flighted submission.
+When you set up package flights, you can specify the people who should get specific packages by adding them to a **known user group** (sometimes referred to as flight group). Anyone in a flight group who is using a device running a version of Windows 10 or Windows 11 that supports package flights (Windows.Desktop build 10586 or later; or Xbox One) will get the packages from the package flight(s) that you designate for that particular group. Anyone who has not been added to one of your flight groups, or is using a device that doesn’t support package flights, will get packages from the non-flighted submission.
 
 > [!IMPORTANT] 
 > On desktop and mobile devices, people in your flight groups will get the packages in your flight automatically whenever you provide updates. However, **people in your flight groups who are using Xbox devices will need to check for updates manually** in order to get the latest packages, making sure they are signed into their device using their Microsoft account (with the associated email address that you included in your known user group).

hub/apps/publish/publish-your-app/reserve-your-apps-name.md

@@ -21,8 +21,14 @@ Follow the following steps to reserve your app's name:
 :::zone pivot="store-installer-msix,store-installer-pwa,store-installer-add-on"
 2. Navigate to the [Partner Center apps and games page](https://partner.microsoft.com/dashboard/apps-and-games/overview).
 3. Click **New product**.
-4. Choose your app's type.
+4. Click on MSIX or PWA app. If you want to submit MSIX game, click on Game.
+
+:::image type="content" source="../../../includes/store/msix/images/msix-new-product.png" lightbox="../../../includes/store/msix/images/msix-new-product.png" alt-text="A screenshot showing how to create a MSIX/PWA app.":::
+
 5. Enter the name you'd like to use and click **Check availability**. If the name is available, you'll see a green check mark. If the name is already in use, you'll see a message indicating so.
+
+:::image type="content" source="../../../includes/store/msix/images/msix-app-name-reservation.png" lightbox="../../../includes/store/msix/images/msix-app-name-reservation.png" alt-text="A screenshot showing how to reserve a name for MSIX/PWA app.":::
+
 6. Once you've selected an available name that you'd like to reserve, click **Reserve product name**.
 :::zone-end
 

hub/apps/publish/view-app-identity-details.md

@@ -7,13 +7,14 @@ ms.topic: article
 keywords: windows 10, uwp
 ms.localizationpriority: medium
 ---
-# View app identity details
+# View product identity details
 
 
-You can view details related to the unique identity assigned to your app by the Microsoft Store on its **App identity** pages. You can also get a link to your app's Store listing on this page.
+You can view details related to the unique identity assigned to your app by the Microsoft Store on its **Product identity** pages. You can also get a link to your app's Store listing on this page.
 
-To find this info, navigate to one of your apps, then expand **App management** in the left navigation menu. Select **App identity** to view these details.
+To find this info, navigate to one of your apps, then expand **Product management** in the left navigation menu. Select **Product identity** to view these details.
 
+:::image type="content" source="../../includes/store/msix/images/msix-product-identity.png" lightbox="../../includes/store/msix/images/msix-product-identity.png" alt-text="A screenshot showing the product identity section for MSIX/PWA app.":::
 
 ## Values to include in your app package manifest
 

hub/apps/toc.yml

@@ -267,7 +267,7 @@ items:
           - name: App management and services
             href: publish/app-management-and-services.md
             items:
-              - name: View app identity details
+              - name: View product identity details
                 href: publish/view-app-identity-details.md
               - name: Generate preinstall packages for OEMs
                 href: publish/generate-preinstall-packages-for-oems.md

hub/includes/store/msi/add-and-edit-store-listing-info.md

@@ -4,8 +4,6 @@ To edit a Store listing, select the language name from the Store listings overvi
 
 ### Product name
 
-*Required*
-
 Your app's name. Must be a name you've already reserved for your app.
 
 If you need to rename the app after it's already been published, you can select a different reserved name here when you create a new submission, after you've provided URLs to packages that use the new name.

hub/includes/store/msi/create-app-store-listing.md

@@ -11,11 +11,11 @@ Many of the fields in a Store listing are optional, but we suggest providing mul
 
 You must complete the Store listing page for at least one language. We recommend providing a Store listing in each language that your packages support, and you also have flexibility to create Store listings in additional languages which are not supported by your packages and not support languages for which you do not wish to provide a Store listing.
 
-To add or remove languages for your Store listings, click Add/remove languages from Manage Store listings page.
+To add or remove languages for your Store listings, click Add languages from Manage Store listings page.
 
 :::image type="content" source="images/msiexe-listings-select-languages.png" lightbox="images/msiexe-listings-select-languages.png" alt-text="A screenshot of the Store listings section where you can add a language for listing your app in Microsoft Store.":::
 
-When you have finished making your selections, click Save to return to the application overview page.
+When you have finished making your selections, click Save to return to the Manage Store listing page.
 
 :::image type="content" source="images/msiexe-listings-language-added.png" lightbox="images/msiexe-listings-language-added.png" alt-text="A screenshot of the Store listings section showing a language has been added for listing.":::
 

hub/includes/store/msi/images/msiexe-age-ratings-overview.png

@@ -1,5 +1,7 @@
 The items described below help customers discover and understand your product. (This section was formerly called **Shared fields**).
 
+:::image type="content" source="images/msix-additional-info.png" lightbox="images/msix-additional-info.png" alt-text="A screenshot showing additional information requirements for listing of a MSIX/PWA app.":::
+
 ### Search terms
 
 Search terms (formerly called keywords) are single words or short phrases that are not displayed to customers, but can help your make your app discoverable in the Store when customers search using those terms. You can include up to 7 search terms with a maximum of 40 characters each, and can use no more than 21 separate words across all search terms.

hub/includes/store/msix/add-additional-information.md

@@ -1,5 +1,7 @@
 To edit a Store listing, select the language name from the submission overview page. You must edit each language separately, unless you choose to export your Store listings and work offline, then import all of the listing data at once. For more about how that works, see [Import and export Store listings](../../../apps/publish/publish-your-app/import-and-export-store-listings.md).
 
+:::image type="content" source="images/msix-listing-overview.png" lightbox="images/msix-listing-overview.png" alt-text="A screenshot showing the overview of the listing page for MSIX/PWA app.":::
+
 The available fields are described below.
 
 ## Product name
@@ -41,7 +43,7 @@ For more info, see [App screenshots and images](../../../apps/publish/publish-yo
 Store logos are optional images that you can upload to enhance the way your app is displayed to customers. You can also optionally specify that only images you upload here should be used in your app’s Store listing for customers on Windows 10 or Windows 11 (including Xbox), rather than allowing the Store to use logo images from your app’s packages.
 
 > [!IMPORTANT]
-> If your app supports Xbox, or if it supports Windows Phone 8.1 or earlier, you must provide certain images here in order for the listing to appear properly in the Store.
+> If your app supports Xbox, you must provide certain images here in order for the listing to appear properly in the Store.
 
 For more info, see [Store logos](../../../apps/publish/publish-your-app/screenshots-and-images.md#store-logos).
 

hub/includes/store/msix/add-and-edit-store-listing-info.md

@@ -4,7 +4,7 @@ Learn how your app's packages are made available to your customers, and how to m
 
 Different operating systems can run different types of packages. If more than one of your packages can run on a customer's device, the Microsoft Store will provide the best available match.
 
-Generally speaking, later OS versions can run packages that target previous OS versions for the same device family. Windows 10 devices can run all previous supported OS versions (per device family). Windows 10 desktop devices can run apps that were built for Windows 8.1 or Windows 8; Windows 10 mobile devices can run apps that were built for Windows Phone 8.1, Windows Phone 8, and even Windows Phone 7.x. However, customers on Windows 10 or Windows 11 will only get those packages if the app doesn't include UWP packages targeting the applicable device family.
+Generally speaking, later OS versions can run packages that target previous OS versions for the same device family. Windows 10 devices can run all previous supported OS versions (per device family). Windows 10 desktop devices can run apps that were built for Windows 8.1 or Windows 8. However, customers on Windows 10 or Windows 11 will only get those packages if the app doesn't include UWP packages targeting the applicable device family.
 
 > [!IMPORTANT]
 > You can no longer upload new XAP packages built using the Windows Phone 8.x SDK(s). Apps that are already in Store with XAP packages will continue to work on Windows 10 Mobile devices. For more info, see this [blog post](https://blogs.windows.com/windowsdeveloper/2018/08/20/important-dates-regarding-apps-with-windows-phone-8-x-and-earlier-and-windows-8-8-1-packages-submitted-to-microsoft-store).
@@ -23,7 +23,7 @@ Note that any customers who already have the app will still be able to use it an
 After making the app unavailable, you'll still see it in Partner Center. If you decide to offer the app to customers again, you can click **Make app available** from the App overview page. After you confirm, the app will be available to new customers (unless restricted by the settings in your last submission) within a few hours.
 
 > [!NOTE]
-> If you want to keep your app available, but don't want to continuing offering it to new customers on a particular OS version, you can create a new submission and remove all packages for the OS version on which you want to prevent new acquisitions. For example, if you previously had packages for Windows Phone 8.1 and Windows 10, and you don't want to keep offering the app to new customers on Windows Phone 8.1, remove all of your Windows Phone 8.1 packages from the submission. After the update is published, no new customers on Windows Phone 8.1 will be able to acquire the app though customers who already have it can continue to use it). However, the app will still be available for new customers on Windows 10.
+> If you want to keep your app available, but don't want to continuing offering it to new customers on a particular OS version, you can create a new submission and remove all packages for the OS version on which you want to prevent new acquisitions.
 
 ## Removing packages for a previously-supported device family
 
@@ -35,11 +35,11 @@ Be aware that even if you remove all of the packages that support a certain devi
 
 ## Adding packages for Windows 10 to an existing app
 
-If you have an app in the Store that only included packages for Windows 8.x and/or Windows Phone 8.x, and you want to update your app for Windows 10, create a new submission and add your UWP .msixupload or .appxupload package(s) during the [Packages](../../../apps/publish/publish-your-app/upload-app-packages.md) step. After your app goes through the certification process, the UWP package will also be available for new acquisitions by customers on Windows 10.
+If you have an app in the Store that only included packages for Windows 8.x and you want to update your app for Windows 10 and 11, create a new submission and add your UWP .msixupload or .appxupload package(s) during the [Packages](../../../apps/publish/publish-your-app/upload-app-packages.md) step. After your app goes through the certification process, the UWP package will also be available for new acquisitions by customers on Windows 10 and 11.
 
 > [!NOTE]
-> Once a customer on Windows 10 gets your UWP package, you can't roll that customer back to using a package for any previous OS version.
+> Once a customer on Windows 10 or 11 gets your UWP package, you can't roll that customer back to using a package for any previous OS version.
 
-Note that the version number of your Windows 10 packages must be higher than those for any Windows 8, Windows 8.1, and/or Windows Phone 8.1 packages you have used. For more info, see [Package version numbering](../../../apps/publish/publish-your-app/package-version-numbering.md).
+Note that the version number of your Windows 10 and 11 packages must be higher than those for any Windows 8, Windows 8.1 packages you have used. For more info, see [Package version numbering](../../../apps/publish/publish-your-app/package-version-numbering.md).
 
 For more info about packaging UWP apps for the Store, see [Packaging apps](/windows/uwp/packaging/).