Update Add-ons documentation (Submit your app)

hub/apps/publish/publish-your-app/add-on/app-certification-process.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # The app certification process for add-on
 
-When you finish creating your app's submission and click **Submit to the Store**, the submission enters the certification step. This process usually is completed within a few hours, though in some cases it may take up to three business days. After your submission passes certification, it can take up to 24 hours for customers to see the app’s listing for a new submission, or for an updated submission with changes to packages. If your update only changes Store listing details, the publishing process will be completed in less than an hour. You'll be notified when your submission is published, and the app's status in the dashboard will be **In the Store**.
+When you finish creating your app's submission and click **Submit to the Store**, the submission enters the certification step. This process is usually completed within a few hours, though in some cases it may take up to three business days. After your submission passes certification, it can take up to 24 hours for customers to see the app’s listing for a new submission, or for an updated submission with packages changes. If you update only changes Store listing details, the publishing process will be completed in less than an hour. You'll be notified when your submission is published, and the app's status in the dashboard will be **In the Store**.
 
 ## Preprocessing
 
@@ -22,7 +22,7 @@ During this phase, several tests are conducted:
 - **Technical compliance tests:** Technical compliance is tested by the Windows App Certification Kit. (You should always make sure to [test your app with the Windows App Certification Kit](/windows/uwp/debug-test-perf/windows-app-certification-kit) before you submit it to the Store.)
 - **Content compliance:** The amount of time this takes varies depending on how complex your app is, how much visual content it has, and how many apps have been submitted recently. Be sure to provide any info that testers should be aware of in the [Notes for certification](./manage-submission-options.md#notes-for-certification) page.
 
-After the certification process is complete, you'll get a certification report telling you whether or not your app passed certification. If it didn't pass, the report will indicate which test failed or which [policy](../../store-policies.md) was not met. After you fix the problem, you can create a new submission for your app to start the certification process again.
+After the certification process is complete, you'll get a certification report telling you whether or not your app passed certification. If it didn't pass, the report will indicate which test failed or which [policy](../../store-policies.md) was not met. Once you fix the problem, you can create a new submission for your app and start the certification process again.
 
 ## Release
 
@@ -37,13 +37,13 @@ When your app passes certification, it's ready to move to the **Publishing** pro
 
 Your app's packages are digitally signed to protect them against tampering after they have been released. Once this phase has begun, you can no longer cancel your submission or change its release date.
 
-For new apps and updates which include changes to the app's packages, the publishing process will be completed within 24 hours. For updates that only change options such as Store listing details, but don't change the app's packages, the publishing process will take less than one hour.
+For new apps and updates that include changes to the app's packages, the publishing process will be completed within 24 hours. For updates that only change options such as Store listing details, but don't change the app's packages, the publishing process will take less than one hour.
 
 While your app is in the publishing phase, the **Show details** link in the Status column for your app’s submission lets you know when your new packages and Store listing details are available to customers on each of your supported OS versions. Steps that have not yet completed will show **Pending**. Your app will remain in the publishing phase until the process has completed, meaning that the new packages and/or listing details are available to all of your app’s potential customers.
 
 ## In the Store
 
-After successfully going through the steps above, the submission's status will change from **Publishing** to **In the Store**. Your submission will then be available in the Microsoft Store for customers to download (unless you have chosen another [Discoverability](./visibility-options.md#discoverability) option).
+After successfully completing the steps above, the submission's status will change from **Publishing** to **In the Store**. Your submission will then be available in the Microsoft Store for customers to download (unless you have chosen another [Discoverability](./visibility-options.md#discoverability) option).
 
 > [!NOTE]
 > We also conduct spot checks of apps after they've been published so we can identify potential problems and ensure that your app complies with all of the [Microsoft Store Policies](../../store-policies.md). If we find any problems, you'll be notified about the issue and how to fix it, if applicable, or if it has been removed from the Store.

hub/apps/publish/publish-your-app/add-on/create-app-store-listing.md

@@ -8,7 +8,7 @@ ms.localizationpriority: medium
 
 # Create add-on store listings
 
-When submitting an add-on in [Partner Center](https://partner.microsoft.com/dashboard), the info you provide in the **Store listings** step will be displayed to your customers when they see the option to acquire your add-on. Make sure to consider the Store listing info carefully in order to represent your add-on accurately in a way that makes it appealing to customers. You can provide customized Store listings for different languages.
+When submitting an add-on in [Partner Center](https://partner.microsoft.com/dashboard), the info you provide in the **Store listings** step will be displayed to your customers when they see the option to acquire your add-on. Be sure to consider the Store listing info carefully in order to represent your add-on accurately in a way that makes it appealing to customers. You can provide customized Store listings in different languages.
 
 > [!TIP]
 > You can also [import and export Store listings](./import-and-export-store-listings.md) for your add-on if you'd like to enter your listing info offline in a .csv file, rather than providing this info directly in Partner Center. This may be especially convenient when creating listings in many languages. However, you can always enter your info directly in [Partner Center](https://partner.microsoft.com/dashboard) rather than using the import/export feature.
@@ -22,3 +22,19 @@ Under the **Store listing** section of your add-on's submission, click **Add/rem
 To remove a language, click **Remove** (or click **Manage languages** and uncheck the box for languages you’d like to remove).
 
 When you have finished making your selections, click **Save** to return to the submission overview page.
+
+## Add and edit Store listing info for add-on
+
+To edit a Store listing, click the language name from the add-on submission overview page. The info you can enter for each language is described below.
+
+### Product name
+
+You must provide a title here, which is the name your customers will see for this add-on. Your title can be up to 100 characters.
+
+### Description
+
+You must provide a description, up to 200 characters. This information will be displayed to customers along with the title.
+
+### Icon
+
+You also have the option to provide an image that may be displayed to the customer. This icon must be a .png file that measures exactly 300 x 300 pixels. This icon is optional.

hub/apps/publish/publish-your-app/add-on/create-app-submission.md

@@ -42,60 +42,61 @@ Here's a list of the info that you provide when creating your add-on submission.
 | **Pricing**      | Required                                                                |
 | **Sale pricing** | Optional                                                                |
 
+### Age ratings
+
+To publish a product in the Microsoft Store, you must provide accurate answers to the age ratings questions and receive age ratings.
+
+> [!NOTE]
+> You only need to provide age ratings information if your add-on has a **Durable** product type.
+
 ### Store listings
 
-One Store listing required. We recommend providing Store listings for every language your app supports.
+At least one Store listing is required. We recommend that you provide Store listings for every language your app supports.
 
 | Field name      | Notes                           |
 | --------------- | ------------------------------- |
-| **Title**       | Required (100 character limit)  |
-| **Description** | Optional (200 character limit)  |
+| **Product name**| Required (100 character limit)  |
+| **Description** | Required (200 character limit)  |
 | **Icon**        | Optional (.png, 300x300 pixels) |
 
 When you've finished entering this info, click **Submit to the Store**. In most cases, the certification process takes about an hour. After that, your add-on will be published to the Store and ready for customers to purchase.
 
 > [!NOTE]
 > The add-on must also be implemented in your app's code. For more info, see [In-app purchases and trials](/windows/uwp/monetize/in-app-purchases-and-trials).
 
-## Set your add-on product type and product ID
-
-An add-on must be associated with an app that you've created in Partner Center (even if you haven't submitted it yet). You can find the button to Create a new add-on on your app's Overview page or on its Add-ons page.
-
-After you select Create a new add-on, you'll be prompted to specify a product type and assign a product ID for your add-on.
-
 ### Product type
 
 First, you'll need to indicate which type of add-on you are offering. This selection refers to how the customer can use your add-on.
 
 > [!NOTE]
 > You won't be able to change the product type after you save this page to create the add-on. If you choose the wrong product type, you can always delete your in-progress add-on submission and start over by creating a new add-on.
 
-<span id="durable"></span>
-
-#### Durable
-
-Select **Durable** as your product type if your add-on is typically purchased only once. These add-ons are often used to unlock additional functionality in an app.
-
-The default **Product lifetime** for a durable add-on is **Forever**, which means the add-on never expires. You have the option to set the **Product lifetime** to a different duration in the [Properties](./enter-app-properties.md) step of the add-on submission process. If you do so, the add-on will expire after the duration you specify (with options from 1-365 days), in which case a customer could purchase it again after it expires.
-
 #### Consumable
 
 If the add-on can be purchased, used (consumed), and then purchased again, you'll want to select one of the **consumable** product types. Consumable add-ons are often used for things like in-game currency (gold, coins, etc.) which can be purchased in set amounts and then used up by the customer. For more info, see [Enable consumable add-on purchases](/windows/uwp/monetize/enable-consumable-add-on-purchases).
 
 There are two types of consumable add-ons:
 
 - **Developer-managed consumable**: Balance and fulfillment must be managed within your app. Supported on all OS versions.
-- **Store-managed consumable:** Balance will be tracked by Microsoft across all of the customer’s devices running Windows 10, version 1607 or later; not supported on any earlier OS versions. To use this option, the parent product must be compiled using Windows 10 SDK version 14393 or later. Also note that you can't submit a Store-managed consumable add-on to the Store until the parent product has been published (though you can create the submission in Partner Center and begin working on it at any time). You'll need to enter the quantity for your Store-managed consumable add-on in the **Properties** step of your submission.
+- **Store-managed consumable**: Balance will be tracked by Microsoft across all of the customer’s devices running Windows 10, version 1607 or later; not supported on any earlier OS versions. To use this option, the parent product must be compiled using Windows 10 SDK version 14393 or later. Also note that you can't submit a Store-managed consumable add-on to the Store until the parent product has been published (though you can create the submission in Partner Center and begin working on it at any time). You'll need to enter the quantity for your Store-managed consumable add-on in the **Properties** step of your submission.
+
+<span id="durable"></span>
+
+#### Durable
+
+Select **Durable** as your product type if your add-on is typically purchased only once. These add-ons are often used to unlock additional functionality in an app.
+
+The default **Product lifetime** for a durable add-on is **Forever**, which means the add-on never expires. You have the option to set the **Product lifetime** to a different duration in the [Properties](./enter-app-properties.md) step of the add-on submission process. If you do so, the add-on will expire after the duration you specify (with options from 1-365 days), in which case a customer could purchase it again after it expires.
 
 #### Subscription
 
-If your want to charge customers on a recurring basis for your add-on, choose **Subscription**.
+If you want to charge customers on a recurring basis for your add-on, select **Subscription**.
 
 After a subscription add-on is initially acquired by a customer, they will continue to be charged at recurring intervals in order to keep using the add-on. The customer can cancel the subscription at any time to avoid further charges. You'll need to specify the subscription period, and whether or not to offer a free trial, in the **Properties** step of your submission.
 
 Subscription add-ons are only supported for customers running Windows 10, version 1607 or later. The parent app must be compiled using Windows 10 SDK version 14393 or later and it must use the in-app purchase API in the **Windows.Services.Store** namespace instead of the **Windows.ApplicationModel.Store** namespace. For more info, see [Enable subscription add-ons for your app](/windows/uwp/monetize/enable-subscription-add-ons-for-your-app).
 
-You must submit the parent product before you can publish subscription add-ons to the Store (though you can create the submission in Partner Center and begin working on it at any time).
+You must submit the parent product before you can publish subscription add-ons to the Store, although you can create the submission in Partner Center and begin working on it at any time.
 
 ### Product ID
 
@@ -104,11 +105,11 @@ Regardless of the product type you choose, you will need to enter a unique produ
 Here are a few things to keep in mind when choosing a product ID:
 
 - A product ID must be unique within the parent product.
-- You can’t change or delete an add-on's product ID after it's been published.
+- You can’t change or delete an add-on’s product ID after it's been published.
 - A product ID can't be more than 100 characters in length.
 - A product ID cannot include any of the following characters: **&lt; &gt; \* % & : \\ ? + ,**
 - Customers won't see the product ID. (Later, you can enter a [title and description](./create-app-store-listing.md) to be displayed to customers.)
-- If your previously-published app supports Windows Phone 8.1 or earlier, you must only use alphanumeric characters, periods, and/or underscores in your product ID. If you use any other types of characters, the add-on will not be available for purchase to customers running Windows Phone 8.1 or earlier.
+- If your previously published app supports Windows Phone 8.1 or earlier, you must only use alphanumeric characters, periods, or underscores in your product ID. If you use any other types of characters, the add-on will not be available for purchase to customers running Windows Phone 8.1 or earlier.
 
 ## Notifications