Add a high-level description of changes

Author: MariaShaposhnikova

content/en/docs/refguide/modeling/menus/version-control-menu/commit-dialog.md

@@ -37,6 +37,22 @@ Tick the boxes next to the stories that are related to your commit. Mendix recom
 
 If there are changes in the model this tab shows a summary of those changes. For more information on how changes are reported in Studio Pro, see [Changes Pane](/refguide/changes-pane/).
 
+There are several scenarios and options that you can choose when committing. 
+
+#### Commit and Push
+
+Your changes are committed and pushed to the server.
+
+#### Commit Locally
+
+Changes are committed to your local working copy and are not pushed to the sever.
+
+#### Commit and Combine {#combine}
+
+If someone else committed a change since the last time you pulled your branch, you will have to pull first. This process is called **Commit and Combine** in the [Commit](/refguide/commit-dialog/) dialog box. **Commit and Combine** will update your local working copy. 
+
+After you reviewed the changes, you will need to push your changes, as **Commit and Combine** only updates your local copy and does not push your changes to the server. 
+
 ### Changes on Disk
 
 {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/commit-dialog/commit-dialog-disk-changes.png" alt="Version Control Menu" class="no-border" width="400" >}}

content/en/docs/refguide/version-control/using-version-control-in-studio-pro/_index.md

@@ -143,7 +143,7 @@ A tool you can consider using is TortoiseGitMerge, shipped as part of [TortoiseG
 Comparing files on disk with the original is currently not supported on macOS.
 {{% /alert %}}
 
-Committing is only allowed if your working copy is up to date with the repository. If someone else committed a change since the last time you pulled, you will have to pull first. This is because the revision you create with the commit should incorporate both your changes and the changes by the other person. Updating will combine the latest changes in the repository with your changes. After reviewing the result and fixing any conflicts, you can commit again.
+Committing is only allowed if your working copy is up to date with the repository. If someone else committed a change since the last time you pulled, you will have to pull first (this process is called **Commit and Combine** in the [Commit](/refguide/commit-dialog/#combine) dialog box). This is because the revision you create with the commit should incorporate both your changes and the changes by the other person. Updating will combine the latest changes in the repository with your changes. After reviewing the result and fixing any conflicts, you can commit again. 
 
 ### Pushing {#pushing}