Merging changes synced from https://github.com/MicrosoftDocs/windows-dev-docs (branch docs)

Author: Learn Build Service GitHub App

hub/apps/publish/publish-your-app/msi/publish-update-to-your-app-on-store.md

@@ -18,11 +18,9 @@ You can make changes to a published app at any time. To submit updates, go to th
 
 Go to the required sections like [Pricing and availability](./price-and-availability.md), [Properties](./enter-app-properties.md), [Age ratings](./age-ratings.md), [Packages](./upload-app-packages.md) and [Store listing](./create-app-store-listing.md) to make the changes you'd like and save them. Then click  **Publish** on Manage Store listing page.
 
-> [!NOTE]
->
-> ## Update package details
->
-> After updating/adding the new package details, click on Save draft. You will be back on Manage Packages page. In the list of packages, you will see your existing package or the new package has been added. Now, click on **Save All**. You will see a message that your package is uploading and after a successful upload, you will get a message as Saved Successfully.
 
+## Update package details
+
+After updating/adding the new package details, click on Save draft. You will be back on Manage Packages page. In the list of packages, you will see your existing package or the new package has been added. Now, click on **Save All**. You will see a message that your package is uploading and after a successful upload, you will get a message as Saved Successfully.
 > [!NOTE]
 > Any updates to EXE or MSI apps are subject to [Application Developer Agreement](/legal/windows/agreements/app-developer-agreement) and the [Microsoft Store Policies](../../store-policies.md), which may be updated from time to time. To add new functionalities that require written customer consent via your app update, you must provide notice to customers and get their written consent as required by law in the markets where you choose to distribute your app.

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

@@ -46,3 +46,12 @@ Choosing the right name for your app is important. Pick a name that will capture
 If this is unavoidable, use different logos and app images to make it easier to differentiate one app from another.
 
 **Do not include emojis in your name**. You will not be able to reserve a name that includes emojis or other unsupported characters.
+
+## Next steps for MSI/EXE app development
+
+After reserving your app name, you may want to explore technical implementation topics for your MSI or EXE application:
+
+- **UI controls and accessibility**: Learn about implementing docking controls, drag and drop, and other UI patterns. See [Control patterns and interfaces](../../../design/accessibility/control-patterns-and-interfaces.md) for UI Automation patterns including docking functionality.
+- **App updates**: Plan how your application will handle updates after publication. See [Publish update to your MSI/EXE app on the Store](./publish-update-to-your-app-on-store.md) for Store update guidance.
+- **Desktop app development**: Find comprehensive guidance for building Windows desktop applications at [Build desktop apps for Windows](../../../desktop/index.yml).
+- **Continue with app submission**: Once your name is reserved, proceed to [Create your MSI/EXE app submission](./create-app-submission.md) to begin the publishing process.

hub/apps/publish/publish-your-app/msix/create-app-submission.md

@@ -115,7 +115,6 @@ To add or remove:
 3. On the Notification audience overview page, add or remove audience
 
 > [!NOTE]
->
 > - The owner of your developer account is always notified and can’t be removed from the audience list.
 > - The audience list is product specific and applied to all submissions of the product. To modify the notification recipients for a different product, follow the steps above for each product.
 > - Add-on inherits parent product’s audience list and can’t be managed separately.

hub/apps/publish/publish-your-app/pwa/create-app-submission.md

@@ -112,7 +112,6 @@ To add or remove:
 3. On the Notification audience overview page, add or remove audience
 
 > [!NOTE]
->
 > - The owner of your developer account is always notified and can’t be removed from the audience list.
 > - The audience list is product specific and applied to all submissions of the product. To modify the notification recipients for a different product, follow the steps above for each product.
 > - Add-on inherits parent product’s audience list and can’t be managed separately.

hub/apps/publish/store-policy-archive/store-policy-7-15.md

@@ -344,7 +344,6 @@ For products that are primarily gaming experiences or target Xbox consoles, the
 
 > [!NOTE]
 > Additional requirements for titles which use Xbox Live on PC/Mobile and/or the Creators program on Xbox consoles are available at https://aka.ms/xboxlivepolicy.
->
 > **February 10, 2022 Policy Note**: For game products targeting console developed through the Xbox Live Creators program, the requirement to integrate with XBL Services no longer applies. The specific policy (Policy 10.13.1) will be updated to reflect this change the next time the Store Policy document is updated, but effective as of this notice, the policy will no longer be enforced for the XBL Creators Program.
 
 **10.13.1**