fixing blocking/non-blocking issues before merge

Author: Qian Wen

articles/marketplace/gtm-offer-listing-best-practices.md

@@ -48,11 +48,11 @@ Categories and subcategories applicable to each Storefront are listed [here](gtm
 
 Industry selection applies only for offers published to AppSource and Consulting Services published in Azure Marketplace. Select industries and/or verticals if your offer addresses industry-specific needs, calling out industry-specific capabilities in your offer description. You can select up to two (2) industries and two (2) verticals per industry selected.
 
-### Applicable Products
+### Applicable products
 
 Select the applicable products your app works with for the offer to show up under selected products in AppSource.
 
-### Search Keywords
+### Search keywords
 
 Keywords can help customers find your offer when they search. Identify the top search keywords for your offer, incorporate them in your offer summary and description as well as in the keyword section of the offer listing details section.
 

articles/marketplace/marketplace-criteria-content-validation.md

@@ -24,7 +24,7 @@ All offers must meet the [All Listing Requirements](https://docs.microsoft.com/a
 |:--- |:--- |:--- |:--- |
 | 1 | Lead destination | Have a lead destination configured| OCP Catalog has the lead destination CRM info also listed in partner solution tab | 
 | 2 | Offer title | Descriptive of solution offering. Matches online promotion of solution in partner's website | Contains key search words |
-| 3 | Logo | Logo displays correctly | Logo displays correctly and includes [hero image that is the large-format image in the Azure Portal |
+| 3 | Logo | Logo displays correctly | Logo displays correctly and includes [hero image that is the large-format image in the Azure portal |
 | 4 |  Offer description | <br>• 2-3 paragraphs <br>• Solution offering is easily understood at a glance <br>• Offer description is free of spelling and grammar mistakes <br>• Offer description is comprehensive and captures: target audience, type of user, why it's valuable (value prop) <br>• Offer description is in paragraph narrative form with short sentences that is easy to comprehend | <br>• Target industry is outlined (if relevant) <br>• Good style formatting with each paragraph header having a one-sentence or phrase summarizing content that follows and inclusive of bullet points (when appropriate) to emphasize key benefits. The objective here is for the reader to understand the offering at a glance in an easy to view format and not have to read paragraphs. <br>• There is spacing between each paragraph and reads like a car brochure. Meaning not technical features or code lingo but descriptive of the offering in simple terms and is comprehensive. | 
 | 5 | Categories & Industries | <br>• Categories match solution offering capabilities <br>• Do not extend to categories that solution does not fit <br>• Optimal industry, or all industries selected (if not optimal industries) | <br>• Max. 3 categories <br>• Max. 3 industries |
 | 6 | Images | <br>• No image required, but if provided must display and a high-resolution image. <br>• Image requirements are listed in CPP and also here <br>• Text included in the screenshot is legible with clear image | Solution offering is easily understood at a glance |
@@ -45,7 +45,7 @@ All offers must meet the [All Listing Requirements](https://docs.microsoft.com/a
 ---
 ## SaaS app requirements
 
-Your offer’s transaction capabilities and the category/subcategory selection will determine the storefront where your offer will be published. Depending on your category selection, offers targeted to a technical (IT/Dev) audience will be published to [Azure Marketplace](https://azuremarketplace.microsoft.com/en-us/marketplace/apps), and offers intended for a business audience will be published to [Microsoft AppSource](https://appsource.microsoft.com/en-us/marketplace/apps). View [categories](gtm-offer-listing-best-practices-categories.md) applicable to each storefront to determine your offer placement. If you intend to cross-list your offer, the value proposition should address both storefront [audiences](https://docs.microsoft.com/azure/marketplace/comparing-appsource-azure-marketplace). The table below summarizes how publishing across each storefront is determined for SaaS listings:
+Your offer’s transaction capabilities and the category/subcategory selection will determine the storefront where your offer will be published. Depending on your category selection, offers targeted to a technical (IT/Dev) audience will be published to [Azure Marketplace](https://azuremarketplace.microsoft.com/marketplace/apps), and offers intended for a business audience will be published to [Microsoft AppSource](https://appsource.microsoft.com/marketplace/apps). View [categories](gtm-offer-listing-best-practices-categories.md) applicable to each storefront to determine your offer placement. If you intend to cross-list your offer, the value proposition should address both storefront [audiences](https://docs.microsoft.com/azure/marketplace/comparing-appsource-azure-marketplace). The table below summarizes how publishing across each storefront is determined for SaaS listings:
 
 <!---
 | SaaS Offer    |     |          |           |    |    |     | Applicable Storefront |              |
@@ -64,7 +64,7 @@ Your offer’s transaction capabilities and the category/subcategory selection w
 ![SaaS offer storefronts](./media/marketplace-publishers-guide/saas-storefronts.png)
 
 <sup>1</sup> Depending on category/subcategory and industry selection. <br>
-<sup>2</sup> Offers with private plans will be published to the Azure Portal.
+<sup>2</sup> Offers with private plans will be published to the Azure portal.
 
 <br>
 
@@ -76,7 +76,7 @@ Your offer’s transaction capabilities and the category/subcategory selection w
 | 4 | Storefront details: Offer Summary | This will appear on your app's search page with a maximum of 100 characters | |
 | 5 | Storefront details: Industries | Industries (Max 2): Select the industries that your app is best aligned and applicable to. | |
 | 6 | Offer Description | <br>•	Simple HTML is allowed, including p, em, ul, li, ol and header tags. Maximum of 3000 characters. <br>•	2-3 paragraphs <br>•	Solution offering is easily understood at a glance <br>•	Description is comprehensive and captures: target audience*, type of user, why it's valuable (value prop) <br>•	Offer description is in paragraph narrative form with short sentences that is easy to comprehend. | <br>•	Target industry is outlined (if relevant) <br>•	Good style formatting with each paragraph header having a one-sentence or phrase summarizing content that follows and inclusive of bullet points (when appropriate) to emphasize key benefits. The objective here is for the reader to understand the offering at a glance in an easy to view format and not have to read paragraphs. <br>•	There is spacing between each paragraph and reads like a car brochure. Meaning not technical features or code lingo but descriptive of the offering in simple terms and is comprehensive. | 
-| 7 | Marketing Artifacts | Logos display correctly | <br>•	Logo  includes "hero image," which is the large-format image in the Azure Portal <br>•	Logos: Small (48x48) & Large (216x216) are requirements <br>•	Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish <br>•	Screenshot (Max 5):  CPP requires a .png image with resolution 1280 x 720. |
+| 7 | Marketing Artifacts | Logos display correctly | <br>•	Logo  includes "hero image," which is the large-format image in the Azure portal <br>•	Logos: Small (48x48) & Large (216x216) are requirements <br>•	Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish <br>•	Screenshot (Max 5):  CPP requires a .png image with resolution 1280 x 720. |
 | 8 | Categories & Industries | • Categories/subcategories match offer capabilities <br> • Do not select categories/subcategories that do not fit with your offer capabilities <br> • Target industry and verticals if offer is industry-specific. If it is not industry-specific, do not select an industry | • Select up to two (2) categories, including a primary and a secondary category (optional). <br> • Select up to two (2) subcategories for each primary and/or secondary category. If no subcategory is selected, you offer will still be discoverable on the selected category only. <br> • Select up to two (2) industries and two verticals per industry selected |
 | 9 | Lead Management | Select the system where your leads will be stored. Learn how to connect your CRM system [here](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-get-customer-leads) |  |
 | 10 | Contacts: Solution Support & Help | <br>•	Engineering contact name: Enter the name of the engineering contact for your app. This contact will receive technical communications from Microsoft.<br>•	Engineering contact email:  Enter the email address of the engineering contact for your app.<br>•	Engineering contacts Phone: Enter the phone number of the engineering contact. ISO phone number notations are supported; for details, see https://en.wikipedia.org/wiki/E.123.<br>•	Support contact Name: Enter the name of the support contact for your app. This contact will receive support-related communications from Microsoft.<br>•	Support contact email: Enter the email address of the support contact for your app. <br>•	Support contact phone: Enter the phone number of the support contact. ISO phone number notations are supported; for details, see https://en.wikipedia.org/wiki/E.123. <br>•	Support URL: Enter the URL to your support page. | <br>•	All support methods listed: telephone & email support. <br>•	Paid support offered free during trial or test drive period |
@@ -90,7 +90,7 @@ Your offer’s transaction capabilities and the category/subcategory selection w
 |:--- |:--- |:--- |:--- |
 |1 |Offer Settings | <br>• Offer ID: Max 50 Character <br>• Publisher ID: Select from drop-down <br>•	Name: Max 50 characters | Mirrors the title style already available in the description- do not want long titles. | 
 | 2 | SKUs | Partner clicks on new SKUs| Mirrors the title style already available in the description- do not want long titles.  |
-| 3 | Marketplace Artifacts | Logos display correctly |<br>• Logo includes "hero image," which is the large-format image in the Azure Portal <br>• Logos: Small (48x48) & Large (216x216) are requirements <br>• Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish<br>• Screenshot (Max 5):  CPP requires a .png image with resolution 1280 x 720.|
+| 3 | Marketplace Artifacts | Logos display correctly |<br>• Logo includes "hero image," which is the large-format image in the Azure portal <br>• Logos: Small (48x48) & Large (216x216) are requirements <br>• Hero image requirements: https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-solution-template-offer-publish<br>• Screenshot (Max 5):  CPP requires a .png image with resolution 1280 x 720.|
 | 4 | Lead Management |<br>•	Lead Management: Select the system where your leads will be stored. <br>•	Learn how to connect your CRM system [here](https://docs.microsoft.com/azure/marketplace/cloud-partner-portal-orig/cloud-partner-portal-get-customer-leads) | |
 
 ---