Clarified adding a new app and re-submitting an app (#66)

msteams-platform/publishing/apps-publish.md

@@ -11,6 +11,7 @@ ms.date: 01/31/2018
 > **Your Microsoft Teams app *must* use the [latest schema](~/resources/schema/manifest-schema) and follow [current packaging guidelines](~/concepts/apps/apps-package).**
 >
 > [!NOTE]
+
 > Teams provides an in-app gallery for users to find or discover [high-quality Teams apps](~/resources/design/overview). To have your solution available in this gallery, you must publish your solution through AppSource.
 
 AppSource (formerly known as Office Store) provides a convenient location for you to distribute your Microsoft Teams app, as well as other Office 365 extensibility types such as Office add-ins and SharePoint add-ins. To include your solution in AppSource, you submit it to the Seller Dashboard. You need to create an individual or company account if you have not already done so for other Windows apps or Office extensibility types.
@@ -76,7 +77,7 @@ When the validation process is complete, you will receive a message to let you k
    * If the status is **changes requested**, your submission needs changes before approval. Select your submission; on the summary page, choose **View the add-in report** for details about the required changes.
    * If the status is **approved**, your submission will be listed in the appropriate marketplaces, typically within 24 hours.
 
-Failures are explained, with references to the specific policy violations. All failures must be addressed before resubmission.
+Failures are explained, with references to the specific policy violations. All failures must be addressed before resubmission. Be sure to resubmit your app using the tile on the Overview tab. Do not use the *Add a new app* button.
 
 > [!NOTE]
 > If you make changes to an approved Teams experience—specifically, changes to core functionality or the manifest—it must go through the approval process again. For all other changes to your service, such as addressing issues or adding new features, resubmission is not required.
@@ -92,3 +93,4 @@ Failures are explained, with references to the specific policy violations. All f
 * Ensure that metadata in the manifest roughly matches metadata in the Seller Dashboard (and, for bots, in the Bot Framework registration). Note that your Seller Dashboard entry should contain a more detailed and formatted description for use in the AppSource product page.
 * Check your manifest for completeness and accuracy. Then check it again.
 * Be sure to include detailed testing notes and a valid, working test account with appropriate prepopulated data.
+* Do not use the *Add a new app* button to resubmit your app.  Use the tile for your app on the Overview tab instead.

msteams-platform/publishing/office-store-guidance.md

@@ -2,8 +2,8 @@
 title: Publishing guidance
 description: Describes the process of publishing your Microsoft Teams app to AppSource
 keywords: teams publish store office publishing
+ms.date: 01/31/2018
 ---
-
 # Use the Seller Dashboard to submit your Microsoft Teams app
 
 For a general overview of the Microsoft Teams app submission flow, see [Publish your Microsoft Teams app to AppSource](~/publishing/apps-publish).
@@ -14,7 +14,7 @@ In the Seller Dashboard:
 
    ![Office Seller Dashboard entry point](~/assets/images/submission/sellerdashboardofficeentry.png)
 
-2. Choose **Add a new app** to initiate the submission process.
+2. Choose **Add a new app** to initiate the submission process. If you have an existing app its tile should be displayed on this page. Choose this tile for re-submitting an existing app. The following steps assume that you are creating a new app.
 
    ![Office Seller Dashboard Add an app button](~/assets/images/submission/sellerdashboardaddapp.png)
 
@@ -28,10 +28,11 @@ In the Seller Dashboard:
 
    * **App package** – Upload your properly formatted 1.0 manifest. Note that the manifest information prepopulates many of the following fields.
    * **Submission title** – The name of your app.
-   * **Version** – Autopopulated from the manifest.
+   * **Version** – Auto-populated from the manifest.
    * **Release date** – By default, today's date. This means that your app is eligible to be published as soon as it passes validation. If you want to delay publication, specify the date. Please note: Validation times vary, and there is no guarantee the validation process will be done by the specified date.
    * **Category** – You can select up to three categories in which to appear in AppSource. Please select ones that best match your experience.
    * **Testing notes** – Please ensure you provide enough information for our validation team to successfully load and test your experience. This includes providing sign-in instructions and test accounts, as well as any other notes that might assist in the review of your product.
+   * **My app calls, support, contains, or uses cryptography or encryption** – This checkbox helps to ensure that your product is not using cryptography in a way that would prohibit distribution through the Office Store. See [Export restrictions on cryptography](https://docs.microsoft.com/en-us/windows/uwp/security/export-restrictions-on-cryptography) for a detailed explanation.
    * **My app calls, support, contains, or uses cryptography or encryption** – This checkbox helps to ensure taht your product is not using cryptography in a way that would prohibit distribution through AppSource. See [Export restrictions on cryptography](https://docs.microsoft.com/en-us/windows/uwp/security/export-restrictions-on-cryptography) for a detailed explanation.
    * **App logo** – Use your full-color 96×96 icon.
    * **Support document link** – The URL for support content for your app.