From 28408d9171a291be97eab1fcd927e8b2164e9b1c Mon Sep 17 00:00:00 2001
From: msamylea <44280406+msamylea@users.noreply.github.com>
Date: Wed, 7 Nov 2018 08:59:39 -0500
Subject: [PATCH] Fixed typo on Line #13 (#21221)

---
 .../10-steps-on-how-to-conquer-a-hackathon/index.md             | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/guide/english/miscellaneous/10-steps-on-how-to-conquer-a-hackathon/index.md b/guide/english/miscellaneous/10-steps-on-how-to-conquer-a-hackathon/index.md
index 324d374764..bccfa16dcd 100644
--- a/guide/english/miscellaneous/10-steps-on-how-to-conquer-a-hackathon/index.md
+++ b/guide/english/miscellaneous/10-steps-on-how-to-conquer-a-hackathon/index.md
@@ -10,7 +10,7 @@ Sometimes, some of the hackathons send out acceptances in batches. If you apply
 
 2.  **Don't be afraid.** 
 
-I recently competed in my first hackathon, and I was completely scared with a major case of <a href='https://guide.freecodecamp.org/working-in-tech/imposter-syndrome/' target='_blank' rel='nofollow'>imposter syndrome</a>. The key for hackathons is to just got for it without any fear, you are indeed a great asset to a team.
+I recently competed in my first hackathon, and I was completely scared with a major case of <a href='https://guide.freecodecamp.org/working-in-tech/imposter-syndrome/' target='_blank' rel='nofollow'>imposter syndrome</a>. The key for hackathons is to just go for it without any fear, you are indeed a great asset to a team.
 
 3.  **Just keep pushing.**