From 9490f075c9683ed6931414536e84235f13258c16 Mon Sep 17 00:00:00 2001
From: iainDe <96153057+iainDe@users.noreply.github.com>
Date: Thu, 6 Jan 2022 05:17:09 -0600
Subject: [PATCH] Update PULL-EXAMPLE.md

Changes made as suggested by @chelsgr
---
 PULL-EXAMPLE.md | 4 +---
 1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/PULL-EXAMPLE.md b/PULL-EXAMPLE.md
index 8da8ee7..a9eccd5 100644
--- a/PULL-EXAMPLE.md
+++ b/PULL-EXAMPLE.md
@@ -5,7 +5,7 @@ Thank you for contributing to CISA's Log4j-affected-db GitHub Repository! Please
 
 **Step 2:** Click the file edit button.
 
-**Step 3:** Add the blank template to the **.yml** file for new entries and fill it out with the correct data.  Note: we are tracking multiple CVEs on the backend but are currently only displaying all the CVE-2021-44228. The multiple CVEs will not be listed in the table per the current request, instead the logic will determine and present a single status based on the available data in the template. 
+**Step 3:** Add the blank template to the **.yml** file for new entries and fill it out with the correct data.  
 
 Blank template:
 ```
@@ -37,7 +37,6 @@ Blank template:
   notes: ''
   references:
   - ''
-  reporter: cisagov
   last_updated: ''
 ```
 **Step 3:** Verify the new entry was entered before and/or after the prior and next entries.
@@ -83,7 +82,6 @@ Entry example:
   unauthenticated user input to the log4j component.
   references:
   - ''
-  reporter: cisagov
   last_updated: '2021-12-14T00:00:00'
 ```
 **Step 5:** Validate that your data follows the appropriate format and proceed with submitting the pull request.