changes based on repolinter output

CONTRIBUTING.md

@@ -17,14 +17,14 @@
  ### Workflow and Branching 
 <!--- TODO: Workflow Example
 We follow the [GitHub Flow Workflow](https://guides.github.com/introduction/flow/)
-1.  Fork the project
-2.  Check out the `main` branch
-3.  Create a feature branch
-4.  Write code and tests for your change
-5.  From your branch, make a pull request against `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
-6.  Work with repo maintainers to get your change reviewed
-7.  Wait for your change to be pulled into `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
-8.  Delete your feature branch
+1. Fork the project
+2. Check out the `main` branch
+3. Create a feature branch
+4. Write code and tests for your change
+5. From your branch, make a pull request against `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
+6. Work with repo maintainers to get your change reviewed
+7. Wait for your change to be pulled into `{{ cookiecutter.project_org }}/{{ cookiecutter.project_repo_name }}/main`
+8. Delete your feature branch
 -->
 
  ### Testing Conventions 

README.md

@@ -1,10 +1,8 @@
-# Repolinter Test 1
+# {name_of_project_here} 
 <!-- This should be 1-3 sentence short description of the project that can be used as a 'one-liner' to describe the repo. A best practice is using this same language as the official 'description' on a GitHub repo landing page. --> 
-This is a quick test project.
 
  ## About the Project 
 <!-- This should be a longer-form description of the project. It can include history, background, details, problem statements, links to design documents or other supporting materials, or any other information/context that a user or contributor might be interested in. --> 
-This is a real quick test project for Repolinter PR testing the actual flow of using this action.
 
  ## Project Mission 
 <!-- Provide the core mission and objectives driving this project. --> 
@@ -90,4 +88,4 @@ All contributions to this project will be released under the CC0 dedication. By
  ### Software Bill of Materials (SBOM) 
 A Software Bill of Materials (SBOM) is a formal record containing the details and supply chain relationships of various components used in building software.
 In the spirit of [Executive Order 14028 - Improving the Nation's Cyber Security](https://www.gsa.gov/technology/it-contract-vehicles-and-purchasing-programs/information-technology-category/it-security/executive-order-14028), a SBOM for this repository is provided here: https://github.com/{repo_org}/{repo_name}/network/dependencies.
-For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.
+For more information and resources about SBOMs, visit: https://www.cisa.gov/sbom.