diff --git a/README.md b/README.md
index c32e19b..4947c59 100644
--- a/README.md
+++ b/README.md
@@ -24,6 +24,7 @@ Having said that, we can't have absolute anarchy.  There must be some kind of a
 Outside of these listed areas, if someone puts in the effort to build and test a package against Rocky Linux, and it helps users in some way, it is welcome to be included in this SIG.
 
 <br />
+
 ## Submitting New Packages
 
 To fill in.
@@ -33,6 +34,7 @@ TLDR:  open an issue in https://git.resf.org/sig_fasttrack/meta/issues
 Always great to talk about things, plans, challenges, etc. in https://chat.rockylinux.org/rocky-linux/channels/sig-fasttrack
 
 <br />
+
 ## Git Storage and Branching
 
 To fill in
@@ -52,6 +54,7 @@ TLDR:
 - Fedora packaging guidelines followed as close as is practical.  With the understanding that much of the Rocky community is still learning packaging best practices, and nothing is perfect first try.  Iterative package improvements will happen as our community gains more experience.
 
 <br />
+
 ## Pull Requests
 
 Pull requests are always welcome against package sources (git.rockylinux.org/sig/fasttrack/src/PKG/ ).  It's up to maintainer(s) or SIG admins to accept/deny requests and maintain quality.  
@@ -59,6 +62,7 @@ Pull requests are always welcome against package sources (git.rockylinux.org/sig
 Pull requests should never violate the guidelines listed above (like introduce a massive security hole, or conflict with stock Rocky Linux packages).
 
 <br />
+
 ## Builds
 
 Builds done in Peridot, can test locally in Mock, against BaseOS+AppStream+CRB+Devel.  Mock configs matching what is done in Peridot should be provided, so contributors can easily develop/test.