Update rules/use-readme-templates/rule.md

Co-authored-by: Matt Wicks [SSW] <wicksipedia@users.noreply.github.com>

rules/use-readme-templates/rule.md

@@ -41,9 +41,7 @@ It's important to keep your README templates in a convenient place to ensure tha
 
 ## What does an awesome README template look like?
 
-The ideal README should foster contributions for a project organically. It should provide all the relevant information a contributor user would need to get the project up and
-running, make code changes, and deploy to production if necessary. It should also contain a number of clearly located social media links so followers of the project
-users can keep an ear to the ground for updates. Followers who see regular updates via social media are more likely to feel actively involved and will commit to the project's success.
+The ideal README should foster contributions for a project organically. It should provide all the relevant information a contributor user would need to get the project up and running, make code changes, and deploy to production if necessary. It should also contain a number of clearly located social media links so followers of the project users can keep an ear to the ground for updates. Followers who see regular updates via social media are more likely to feel actively involved and will commit to the project's success.
 
 We've created a README template with placeholders where you can add all of the relevant information for your project to ensure that it's a success. Bear in mind that not all of the information listed will be relevant to your particular project. For instance, closed-source projects more than likely won't contain social media or sponsorship links. Feel free to remove any placeholders that aren't relevant to your project.