Merge pull request #10517 from mendix/MvM-DuplicateMerges10498

Clarify Git handling during merge

Author: MarkvanMents

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

@@ -16,6 +16,10 @@ To access the **Merge** dialog box, open [Version Control](/refguide/version-con
 
 {{< figure src="/attachments/refguide/modeling/menus/version-control-menu/merge-dialog/merge-dialog.png" alt="Merge Dialog" class="no-border" >}}
 
+{{% alert color="info" %}}
+Git ensures that changes are applied in the correct order and are not duplicated. This may lead to unexpected results if your branch reverts a previous commit. See [Reverting Uncommitted Changes](/refguide/using-version-control-in-studio-pro/#revert-previous-commit) in *Using Version Control in Studio Pro* for more information.
+{{% /alert %}}
+
 Available scenarios are described in sections below.
 
 ## Cherry Pick

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

@@ -223,7 +223,7 @@ You can revert changes in the **Changes** pane, from **Version Control** > **Rev
 You can also **Revert All Changes** while [merging](#merge). This will restore your app to the most recent commit, discarding changes creating by the merging process.
 {{% /alert %}}
 
-### Reverting a Previous Commit
+### Reverting a Previous Commit {#revert-previous-commit}
 
 Changes that have been committed and pushed to the server can never be deleted from the history. However, you can make another commit to revert the changes. This is called **Reverse commit** in Studio Pro.