From aaa61d68a4b7241c002f492bb382b957142cb3d2 Mon Sep 17 00:00:00 2001
From: Josh Soref <2119212+jsoref@users.noreply.github.com>
Date: Wed, 15 May 2024 09:56:03 -0400
Subject: [PATCH] Remove reference to case-sensitive repositories (#32962)

---
 .../troubleshooting-cloning-errors.md                           | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
index 074934a2ed..87e45ae465 100644
--- a/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
+++ b/content/repositories/creating-and-managing-repositories/troubleshooting-cloning-errors.md
@@ -98,7 +98,7 @@ If you've previously set up SSH keys, you can use the SSH clone URL instead of H
 
 ### Check your spelling
 
-Typos happen, and repository names are case-sensitive.  If you try to clone `git@{% data variables.product.product_url %}:user/repo.git`, but the repository is really named `User/Repo` you will receive this error.
+Typos happen.  If you try to clone `git@{% data variables.product.product_url %}:owner/repotile.git`, but the repository is really named `owner/repoti1e` you will receive this error.
 
 To avoid this error, when cloning, always copy and paste the clone URL from the repository's page. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)."