diff --git a/1.5%29-GitHub-Guidelines-2.md b/1.5%29-GitHub-Guidelines-2.md
index 9663d24..f755756 100644
--- a/1.5%29-GitHub-Guidelines-2.md
+++ b/1.5%29-GitHub-Guidelines-2.md
@@ -26,16 +26,20 @@ Updated unit tests for new authentication flow.
 
 6. Be Specific and Descriptive
 
-```Be specific about the changes: If you're fixing a bug, adding a feature, or refactoring code, be specific about what was modified and how it impacts the project.
+```
+Be specific about the changes: If you're fixing a bug, adding a feature, or refactoring code, be specific about what was modified and how it impacts the project.
 
 Example:
 Good: "Fix image upload issue on mobile devices"
-Bad: "Fix bugs"```
+Bad: "Fix bugs"
+```
 
 7. Avoid Large, Unfocused Commits
 
+```
 Focus each commit on one change: A commit should ideally contain a single logical change, like fixing a bug, adding a feature, or refactoring a part of the codebase. Large commits that combine unrelated changes make it harder to understand the history of the project.
 
 Example:
 Good: "Add unit tests for user registration module"
-Bad: "Add unit tests and refactor login page"
\ No newline at end of file
+Bad: "Add unit tests and refactor login page"
+```
\ No newline at end of file