Suggest a rename

Author: MariaShaposhnikova

…ion-control-in-studio-pro/peer-review.md …n-control-in-studio-pro/using-history.mdcontent/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md renamed to content/en/docs/refguide/version-control/using-version-control-in-studio-pro/using-history.md content/en/docs/refguide/version-control/using-version-control-in-studio-pro/peer-review.md renamed to content/en/docs/refguide/version-control/using-version-control-in-studio-pro/using-history.md

@@ -25,4 +25,4 @@ The [Name and Email settings](/refguide/preferences-dialog/#name) can be adjuste
 
 Select a revision to see additional details, such as related stories, changed documents, Studio Pro version, and changes on disk. Icons summarize the kinds of changes that happened in the app.
 
-{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/modeling/menus/version-control-menu/history-dialog/revisions.png" >}}

content/en/docs/refguide/version-control/version-control-troubleshooting/repository-size.md

@@ -79,7 +79,7 @@ This tool is executed on a Mendix Git repository. If your Mendix app is still on
 
 The cleanup tool will reduce the size of the repository to a minimum, by only retaining the latest commit of the main branch. This means that all work on branches that have been merged to main branch are kept, but the commits themselves (author, changes per commit, ...) are not.
 
-{{< figure src="/attachments/refguide/version-control/troubleshoot-version-control-issues/git_fixer_mode.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/version-control/troubleshoot-version-control-issues/git_fixer_mode.png"  >}}
 
 {{% alert color="info" %}}
 Uncommitted work, or work committed to branches that have not been merged to the main branch, will be permanently removed from the repository.
@@ -207,7 +207,7 @@ If you are still on SVN in Studio Pro 9, see the [Recommendation on Avoiding Git
 
 Follow the decision tree in the image below to troubleshoot Git-related performance issues:
 
-{{< figure src="/attachments/refguide/version-control/troubleshoot-version-control-issues/migration-advice-mx11.png" class="no-border" >}}
+{{< figure src="/attachments/refguide/version-control/troubleshoot-version-control-issues/migration-advice-mx11.png"  >}}
 
 \* In case your *.git* folder is  less than 2GB but you are having performance issues when cloning, please see the [Verify Full Clone Through Git CLI](/refguide/troubleshoot-team-server-issues/#verify-full-clone-through-git-cli) section in *Troubleshooting Team Server Issues* and contact Support with the relevant information.