From 78b3827181ca9706aa472c0b36ce1cb3319d65c3 Mon Sep 17 00:00:00 2001
From: TimTheBig <132001783+TimTheBig@users.noreply.github.com>
Date: Thu, 9 Nov 2023 12:13:23 -0500
Subject: [PATCH] Update CONTRIBUTING.md

Signed-off-by: TimTheBig <132001783+TimTheBig@users.noreply.github.com>
---
 CONTRIBUTING.md | 24 ++++++++++++------------
 1 file changed, 12 insertions(+), 12 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index b7777a67..7bf2f809 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -9,9 +9,9 @@ Please read and understand the contribution guide before creating an issue or pu
 <h3>Etiquette</h3>
 
   Our goal for Pi-hole is stability before features. This means we focus on squashing critical bugs before adding new features. Often, we can do both in tandem, but bugs will take priority over a new feature.
-  
+
   Pi-hole is open source and [powered by donations](https://pi-hole.net/donate/), and as such, we give our free time to build, maintain, and provide user support for this project. It would be extremely unfair for us to suffer abuse or anger for our hard work, so please take a moment to consider that.
-  
+
   Please be considerate towards the developers and other users when raising issues or presenting pull requests.
   Respect our decision(s), and do not be upset or abusive if your submission is not used.
 
@@ -24,36 +24,36 @@ When requesting or submitting new features, first consider whether it might be u
  <h4>Before filing an issue:</h4>
 <ul>
   <li>Attempt to replicate and document the problem, to ensure that it wasn't a coincidental incident.</li>
-  
+
   <li>Check to make sure your feature suggestion isn't already present within the project.</li>
-  
+
   <li>Check the pull requests tab to ensure that the bug doesn't have a fix in progress.</li>
-  
+
   <li>Check the pull requests tab to ensure that the feature isn't already in progress.</li>
 </ul>
 
 <h4>Before submitting a pull request:</h4>
 <ul>
   <li>Check the codebase to ensure that your feature doesn't already exist.</li>
-  
+
   <li>Check the pull requests to ensure that another person hasn't already submitted the feature or fix.</li>
-  
+
   <li>Read and understand the [DCO guidelines](https://docs.pi-hole.net/guides/github/dco/) for the project.</li>
 </ul>
 
 <h4>Technical Requirements:</h4>
 <ul>
   <li>Submit Pull Requests to the development branch only.</li>
-  
+
   <li>Before Submitting your Pull Request, merge development with your new branch and fix any conflicts. (Make sure you don't break anything in development!)</li>
   
   <li>Please use the [Google Style Guide](https://google.github.io/styleguide/shellguide.html) for Shell for your code submission styles.</li>
-  
+
   <li>Commit Unix line endings.</li>
-  
+
   <li>Please use the Pi-hole brand: Pi-hole (Take a special look at the capitalized 'P' and a low 'h' with a hyphen)</li>
-  
+
   <li>For Beginners: see here [how to forking and clone from GitHub](https://docs.pi-hole.net/guides/github/how-to-fork-rebase/)</li>
-  
+
   <li>(Optional fun) keep to the theme of Star Trek/black holes/gravity.</li>
 </ul>