Merge pull request #112364 from dannyevers/patch-5

Removed two bad links

Author: PRMerger6

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

@@ -25,7 +25,7 @@ All offers must meet the [All Listing Requirements](https://docs.microsoft.com/a
 | 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 |
+| 6 | Images | <br>* No image required, but if provided must display and a high-resolution image. <br>* Image requirements are listed in Partner Center and also here <br>* Text included in the screenshot is legible with clear image | Solution offering is easily understood at a glance |
 | 7 | Videos | <br>* No videos required, but if provided must play back without any errors. <br>* If provided, may not refer to competitor companies UNLESS demonstrating a migration solution |<br>* Ideally 3 mins or more <br>* Solution offering easily understood through video content <br>* Demo of solution capabilities |
 | 8 | List Status (Call to action) | <br>Must be labeled one of the following types: <ul>o Contact Me</ul><ul>o Trial/Get Trial Now/Start Trial/Test Drive</ul><ul>o    Buy Now/Get it Now</ul> | Customer can readily understand what next steps available are: <ul>1. Try the Trial</ul> <ul>2. Buy Now</ul><ul>3. Contact via e-mail or phone number to arrange for PoC, Assessment, or Briefing.</ul> | 
 | 9 | Solution Pricing | Must have solution pricing tab/details and in the local currency of the partner solution offering | Multiple billing options available with tier-pricing for customer to have options |    
@@ -51,11 +51,11 @@ All offers must meet the [All Listing Requirements](https://docs.microsoft.com/a
 | 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," in the Azure portal. Must be 815 x 290 pixels. <br>*    Logos: Small (48x48) & Large (216x216) are requirements <br> *    Screenshot (Max 5):  Requires a .png image (1280 x 720 pixels). |
 | 8 | Categories & Industries | <br>*    Categories match solution offering capabilities <br>*    At least 1 item(s) should be chosen from pop-up box <br>*    Do not extend to categories that solution does not fit <br>*    Optimal industry, or all industries selected (if not optimal industries <br>*    Do not extend to categories that solution does not fit <br>*    Optimal industry, or all industries selected (if not optimal industries) | Max. 3 categories selected if applicable. |
 | 9 | Lead Management | Select the system where your leads will be stored. See [get customer leads](./partner-center-portal/commercial-marketplace-get-customer-leads.md) to connect your CRM system. |  |
 | 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 |
-| 11 | Legal |<br>*    Privacy policy URL: Enter the URL to your app's privacy policy in the Privacy policy URL field in CPP. <br>*    Terms of use: Enter the terms of use of your app. Customers are required to accept these terms before they can try your app. |    Policies or terms available via a public URL site |
+| 11 | Legal |<br>*    Privacy policy URL: Enter the URL to your app's privacy policy in the Privacy policy URL field in Partner Center. <br>*    Terms of use: Enter the terms of use of your app. Customers are required to accept these terms before they can try your app. |    Policies or terms available via a public URL site |
 
 ---
 
@@ -65,7 +65,7 @@ All offers must meet the [All Listing Requirements](https://docs.microsoft.com/a
 |:--- |:--- |:--- |:--- |
 |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: 815 x 290 pixels <br>* Screenshot (Max 5):  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>*    See [get customer leads](./partner-center-portal/commercial-marketplace-get-customer-leads.md) to connect your CRM system. | |
 
 ---