From faa2c9d2d7d6b6f66ac695fd5e51c46091a31376 Mon Sep 17 00:00:00 2001
From: boulais01 <89533621+boulais01@users.noreply.github.com>
Date: Tue, 19 Sep 2023 11:45:41 -0500
Subject: [PATCH] fix: Update reqs for pull_request_template.md

Uses feedback from reviewer to improve PR template
---
 pull_request_template.md | 12 ++++++++----
 1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/pull_request_template.md b/pull_request_template.md
index 2f5834ef..1042b748 100644
--- a/pull_request_template.md
+++ b/pull_request_template.md
@@ -1,13 +1,17 @@
 When creating a pull request to add a new feature or alter an existing one,
 there are some important elements to include to help our team review and process it more efficiently.
 
-1. Describe the contents and goal of the pull request.
+1. List the names of those who contributed to the project.
 
-2. Will coverge be maintained/increased? 
+2. Link the issue the pull request is meant to fix/resolve.
 
-3. What operating systems has this been tested on? How were these tests conducted?
+3. Describe the contents and goal of the pull request.
 
-4. Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible.
+4. Will coverge be maintained/increased? 
+
+5. What operating systems has this been tested on? How were these tests conducted?
+
+6. Include a code block and/or screenshots displaying the functionality of your feature, if applicable/possible.
 
 Mark as a draft until it is ready to begin the reviewing process, then tag our [Lead Software Architect, Lauren Nevill](https://github.com/laurennevill),
 our [Principal Software Engineer, Bergas Batara](https://github.com/bergasanargya), and our [Founding Engineer, Gregory Kapfhammer](https://github.com/gkapfham)