From 7af8115a51e081185363c362d8609a6d2d9cc480 Mon Sep 17 00:00:00 2001
From: Esha Noronha <82437098+eshanrnh@users.noreply.github.com>
Date: Mon, 25 Nov 2024 09:45:47 +0100
Subject: [PATCH] Update
 13/umbraco-deploy/deployment-workflow/content-transfer.md

---
 13/umbraco-deploy/deployment-workflow/content-transfer.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/13/umbraco-deploy/deployment-workflow/content-transfer.md b/13/umbraco-deploy/deployment-workflow/content-transfer.md
index 0a5cdd73db5..7234a851331 100644
--- a/13/umbraco-deploy/deployment-workflow/content-transfer.md
+++ b/13/umbraco-deploy/deployment-workflow/content-transfer.md
@@ -67,6 +67,6 @@ This does not include entries submitted via the forms.
 
 Sometimes a content transfer might not be possible. For example if you add a new property to the HomePage Document type and you don’t have that property in both environments, you’ll get an error with a hint on how to fix this.
 
-![clone dialog](images/schema-mismatch.png)
+![Clone dialog](images/schema-mismatch.png)
 
 If you are seeing this type of issue when trying to transfer content, head over to our article about [Schema Mismatch errors](../troubleshooting.md), where you can read about how to resolve the issues.