Merge pull request #2412 from MicrosoftDocs/repo_sync_working_branch

Confirm merge from repo_sync_working_branch to master to sync with https://github.com/MicrosoftDocs/powerapps-docs (branch live)

Author: KumarVivek

powerapps-docs/developer/common-data-service/appendix-app-certification-checklist.md

@@ -27,10 +27,10 @@ The following checklist provides the list of validations performed by Microsoft
 <th>Certification checklist</th>
 </tr>
 <tr>
-<td rowspan=5><a href="https://docs.microsoft.com/powerapps/maker/model-driven-apps/model-driven-app-overview">Model-driven apps</a>, <a href="https://docs.microsoft.com/powerapps/maker/canvas-apps/getting-started">canvas apps</a>, and <a href="https://docs.microsoft.com/flow/getting-started">flows</a> that connect to Common Data Service<br/></td>
+<td rowspan=5><a href="https://docs.microsoft.com/powerapps/maker/model-driven-apps/model-driven-app-overview">Model-driven apps</a>, <a href="https://docs.microsoft.com/powerapps/maker/canvas-apps/getting-started">canvas apps</a>, and <a href="https://docs.microsoft.com/power-automate/getting-started">flows</a> that connect to Common Data Service<br/></td>
 <td>Sanity Check</td>
 <td><ul>
-<li>Check for app registration type: Free, Trial or Contact me. If registered in Contact me then publisher need to enable test drive.</li>
+<li>Check for app registration type: Free, Trial or Contact me.</li>
 <li>Verify the submitted <a href="https://docs.microsoft.com/powerapps/developer/common-data-service/create-package-app-appsource">package</a> contains all the artifacts required to publish on AppSource.</li>
 <li>Download the end-to-end (E2E) functional document from <a href="https://partner.microsoft.com/dashboard">Partner Center</a> and validate if document is updated with functional scenarios and user/admin journey.</li>
 </ul>
@@ -46,8 +46,9 @@ The following checklist provides the list of validations performed by Microsoft
 <li>Runtime errors: May occur once the app is opened in Run mode to view. Any issues found will be reported through email.</li>
 <li>Accessibility errors and warnings: All Accessibility errors should be resolved as per Solution Checker guidelines.</li>
 </ul></li>
-<li>Code Validation for Common Data Service solution will be done through <a href="https://experienceisv.microsoftcrmportals.com/precertification/#/">OnDemand Code Analysis (ODCA)</a> tool.</li>
-<li>Issues reported from ODCA will be manually validated for correctness and false positive issues will be reduced to low severity.</li>
+<li>Code Validation for Common Data Service solution will be done utilizing <a href="https://docs.microsoft.com/powerapps/developer/common-data-service/checker/webapi/overview">Power Apps Checker</a>.</li>
+<li>Issues reported from Power Apps Checker will be manually validated for correctness and false positive issues will be reduced to low severity.</li>
+<li>The quality of the solution and packages are validated against the AppSource certification <a href="https://docs.microsoft.com/powerapps/developer/common-data-service/checker/webapi/retrieve-rulesets">ruleset</a>. 
 <li>Generated report is shared with the publisher through email.</li>
 </ul>
 </td>
@@ -84,7 +85,7 @@ The following checklist provides the list of validations performed by Microsoft
 </td>
 </tr>
 <tr>
-<td rowspan=5><a href="https://docs.microsoft.com/powerapps/maker/canvas-apps/getting-started">canvas apps</a> and <a href="https://docs.microsoft.com/flow/getting-started">flows</a> that connect to data sources <i>other</i> than Common Data Service
+<td rowspan=5><a href="https://docs.microsoft.com/powerapps/maker/canvas-apps/getting-started">Canvas apps</a> and <a href="https://docs.microsoft.com/power-automate/getting-started">flows</a> that connect to data sources <i>other</i> than Common Data Service
 </td>
 <td>Sanity Check</td>
 <td><ul>

powerapps-docs/developer/common-data-service/package-deployer/create-packages-package-deployer.md

@@ -143,7 +143,7 @@ Common Data Service provides you with a Visual Studio template for creating thes
 
    ```  
 
-    `<filestoimportnode>` node  
+    `<filestoimport>` node  
     Contains an array of `<configimportfile>` and `<zipimportdetails>` nodes that are used to describe individual files and zip files respectively to be imported.  
 
     `<configimportfile>` node