Merge pull request MicrosoftDocs#4288 from MicrosoftDocs/main638167933485062275sync_temp

For protected CLA branch, push strategy should use PR and merge to target branch method to work around git push error

Author: learn-build-service-prod[bot]

powerapps-docs/maker/data-platform/why-dataverse-overview.md

@@ -3,16 +3,10 @@ title: "Why choose Microsoft Dataverse? | MicrosoftDocs"
 description: Understand how Microsoft Dataverse can help your business become more agile.
 ms.date: 06/16/2020
 ms.reviewer: "Mattp123"
-ms.suite: ""
-ms.tgt_pltfrm: ""
 ms.topic: overview
-applies_to: 
-  - "powerapps"
 author: "mmercuri"
 ms.subservice: dataverse-maker
-ms.author: "kvivek"
-search.audienceType: 
-  - maker
+ms.author: "matp"
 ---
 
 # Why choose Microsoft Dataverse?
@@ -120,7 +114,7 @@ At a high level, the following constitute Microsoft Power Platform requests:
 
 - **Power Automate**: All Power Automate step actions.
 
-- **Common Data Service**: All create, update, delete (CRUD) operations, in addition to special operations like "share" or "assign." These can come from any client or app, using any SOAP or REST endpoint. These include—but aren't limited to—plug-ins, asynchronous workflows, and custom controls making the abovementioned operations.
+- **Dataverse**: All create, update, delete (CRUD) operations, in addition to special operations like "share" or "assign." These can come from any client or app, using any SOAP or REST endpoint. These include—but aren't limited to—plug-ins, asynchronous workflows, and custom controls making the abovementioned operations.
 
 The specific number of allowed requests that a user can make in a 24-hour period is governed by the user's license.