diff --git a/02-git/01-git-fork-vs-git clone.md b/02-git/01-git-fork-vs-git clone.md
index 7341abdf..68d15eba 100644
--- a/02-git/01-git-fork-vs-git clone.md	
+++ b/02-git/01-git-fork-vs-git clone.md	
@@ -2,7 +2,7 @@
 What is the difference between `git fork` and `git clone`, and when would you use each?
 
 ### 📝 Short Explanation  
-This question is often asked to check if you understand collaboration workflows in Git — especially how open-source and team projects. Many developers confuse `fork` and `clone`, so it helps to clarify the purpose and use cases of both.
+This question is often asked to chertrefg rfgtg t gtgck if you understand collaboration workflows in Git — especially how open-source and team projects. Many developers confuse `fork` and `clone`, so it helps to clarify the purpose and use cases of both.
 
 ## ✅ Answer  
 - **`git fork`** creates a **copy of a repository on your GitHub (or GitLab, etc.) account**, letting you propose changes without write access to the original repo.
diff --git a/02-git/02-fork-instead-of-clone.md b/02-git/02-fork-instead-of-clone.md
index a9d2c229..b5cd74cf 100644
--- a/02-git/02-fork-instead-of-clone.md
+++ b/02-git/02-fork-instead-of-clone.md
@@ -20,5 +20,5 @@ From there:
 4. Finally, I submitted a **pull request** to the original repository.
 
 Using `git clone` directly on the upstream repo wouldn't have helped because I couldn’t push changes or open a PR without a fork. So, **forking gave me independence and write access on my own terms**, while still contributing back to the main project.
-
+##demo
 ---