From d39a4da1b9aca02db59a78f54d44cd906742a600 Mon Sep 17 00:00:00 2001
From: Megan McMahon <mcmahon.meganelizabeth@gmail.com>
Date: Tue, 17 Oct 2023 10:19:33 -0600
Subject: [PATCH] Update WritingGoodDocumentation.md

---
 module5/lessons/Week2/WritingGoodDocumentation.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/module5/lessons/Week2/WritingGoodDocumentation.md b/module5/lessons/Week2/WritingGoodDocumentation.md
index a1c6a25..f5170d2 100644
--- a/module5/lessons/Week2/WritingGoodDocumentation.md
+++ b/module5/lessons/Week2/WritingGoodDocumentation.md
@@ -73,10 +73,10 @@ Markdown, the language of READMEs, can be tricky at first. Here are some guides
 
 * [https://www.markdownguide.org/cheat-sheet/](https://www.markdownguide.org/cheat-sheet/)
 * [https://www.markdownguide.org/extended-syntax](https://www.markdownguide.org/cheat-sheet/)
-* [https://about.gitlab.com/handbook/markdown-guide/](https://www.markdownguide.org/cheat-sheet/)
+* [https://about.gitlab.com/handbook/markdown-guide/](https://about.gitlab.com/handbook/markdown-guide/)
 
 <section class="call-to-action">
   <h3>Updating a README</h3>
 
   Open up the README from your Mod 3 Message Logger project and make some updates to it based on what you've learned in this lesson. Be prepared to share the new version of your README with a small group.
-</section>
\ No newline at end of file
+</section>