diff --git a/src/collections/blog/2024/10-09-docker-build-warning/post.mdx b/src/collections/blog/2024/10-09-docker-build-warning/post.mdx
index 30e584bc59a8..f4594994e6ae 100644
--- a/src/collections/blog/2024/10-09-docker-build-warning/post.mdx
+++ b/src/collections/blog/2024/10-09-docker-build-warning/post.mdx
@@ -19,10 +19,7 @@ import { BlogWrapper } from "../../Blog.style.js";
 import { Link } from "gatsby";
 
 <BlogWrapper>
-While building a Docker image for one of <Link to="/projects">Layer5's open source projects</Link>, I recently ran into a build warning in one of the  multi-stage Dockerfiles. Until this time, I hadn't paid attention to a feature of `docker build` previously: <i><a href="https://docs.docker.com/reference/build-checks/">build checks</a></i>.
-
-
- In this blog post, I'll cover a handful of the more common delve into the importance of these checks and explore how to address some common warnings.
+While building a Docker image for one of <Link to="/projects">Layer5's open source projects</Link>, I recently ran into a build warning in one of the  multi-stage Dockerfiles. Until this time, I hadn't paid attention to a feature of `docker build` previously: <i><a href="https://docs.docker.com/reference/build-checks/">build checks</a></i>. In this blog post, I'll cover a handful of the more common delve into the importance of these checks and explore how to address some common warnings.
 
 
 ###  Why Use Docker Build Checks?