From e65096d42bfaa139260cdbc0bcdc4d910c1d7821 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Charly=20Chac=C3=B3n?=
 <107764250+Charlytoc@users.noreply.github.com>
Date: Mon, 6 May 2024 10:24:49 -0500
Subject: [PATCH] Update how-to-review-code.md

---
 src/content/how-to/how-to-review-code.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/src/content/how-to/how-to-review-code.md b/src/content/how-to/how-to-review-code.md
index c37d82301..5f416a0d4 100644
--- a/src/content/how-to/how-to-review-code.md
+++ b/src/content/how-to/how-to-review-code.md
@@ -1,4 +1,5 @@
-# Guide to Effective Code Reviews
+
+# Guide to Write Effective Code Reviews
 
 Code Reviews are one of the most interesting features of 4Geeks.com. They provide mentors with a quick tool to review code, and students with additional feedback to improve as developers. A Code Review, as the name suggests, is simply a comment regarding a portion of code. In this article, we will analyze the desirable characteristics that a Code Review should have to be effective for the student.