Update synapse-workspace-access-control-overview.md

Correcting permissions required for committing in Git mode (this was an inconsistency introduced in PR # 189517).

Author: meenalsri

articles/synapse-analytics/security/synapse-workspace-access-control-overview.md

@@ -99,7 +99,7 @@ To simplify managing access control, you can use security groups to assign roles
 
 Synapse Studio will behave differently based on your permissions and the current mode:
 - **Synapse live mode:** Synapse Studio will prevent you from seeing published content, publishing content, or taking other actions if you don't have the required permission.  In some cases, you'll be prevented from creating code artifacts that you can't use or save. 
-- **Git-mode:** If you have Git permissions that let you commit changes to the current branch, then the commit action will be permitted if you have permission to publish changes to the live service (Synapse Artifact Publisher role), and the Azure Contributor role on the workspace.  
+- **Git-mode:** If you have Git permissions that let you commit changes to the current branch, then the commit action will be permitted if you have permission to publish changes to the live service (Synapse Artifact Publisher role).  
 
 In some cases, you're allowed to create code artifacts even without permission to publish or commit. This allows you to execute code (with the required execution permissions). For more information on the roles required for common tasks, see [Understand the roles required to perform common tasks in Azure Synapse](./synapse-workspace-understand-what-role-you-need.md).