diff --git a/src/data/question-groups/full-stack/content/code-splitting.md b/src/data/question-groups/full-stack/content/code-splitting.md
index 14a4271e2..428d67cda 100644
--- a/src/data/question-groups/full-stack/content/code-splitting.md
+++ b/src/data/question-groups/full-stack/content/code-splitting.md
@@ -14,4 +14,5 @@ function App() {
);
-}
\ No newline at end of file
+}
+```
\ No newline at end of file
diff --git a/src/data/question-groups/golang/content/string-literals.md b/src/data/question-groups/golang/content/string-literals.md
index ac3745da2..22e1a89af 100644
--- a/src/data/question-groups/golang/content/string-literals.md
+++ b/src/data/question-groups/golang/content/string-literals.md
@@ -1,4 +1,4 @@
-Raw string literals in Go are enclosed in backticks (`` ` ``) and preserve all formatting exactly as written. This is different from interpreted string literals, which process escape sequences like \n. This distinction is particularly useful when you need to process data exactly as it is written.
+Raw string literals in Go are enclosed in backticks (\`) and preserve all formatting exactly as written. This is different from interpreted string literals, which process escape sequences like \n. This distinction is particularly useful when you need to process data exactly as it is written.
Consider a scenario where you need to embed an HTML template directly into your Go code. With raw string literals, you can include the HTML exactly as written without worrying about escaping characters or preserving the formatting. For example:
@@ -11,7 +11,7 @@ htmlTemplate := `
Hello, World!
-