diff --git a/content/posts/code-complete-summations-pre-requisets-part-3.md b/content/posts/code-complete-summations-pre-requisets-part-3.md
index b9b28b3..e3bbc84 100644
--- a/content/posts/code-complete-summations-pre-requisets-part-3.md
+++ b/content/posts/code-complete-summations-pre-requisets-part-3.md
@@ -8,7 +8,7 @@ draft: false
 
 Prerequisites are incredibly important to any development project and was the [OWASP Top 10, Number 4, Insecure Design](https://owasp.org/Top10/A04_2021-Insecure_Design/). For the purpose of this document we will talk about it in context of *security implications*.
 
-This ended up being too big of a topic for just two posts, so here is part 3. In {{< ref "code-complete-summations-pre-requisets-part-1.md" >}}, we looked at why pre-reqs are needed in general and how they apply to types of projects. In {{< ref "code-complete-summations-pre-requisets-part-2.md" ? }} we looked at how various pre-reqs for architecture helps with security. In part 3 we'll look at resource and error management pre-reqs.
+This ended up being too big of a topic for just two posts, so here is part 3. In {{< ref "code-complete-summations-pre-requisets-part-1.md" >}}, we looked at why pre-reqs are needed in general and how they apply to types of projects. In {{< ref "code-complete-summations-pre-requisets-part-2.md" >}} we looked at how various pre-reqs for architecture helps with security. In part 3 we'll look at resource and error management pre-reqs.
 
 # Planning Comes First