Apply suggestions from code review

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

Author: wirecat

CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 We’d love you to help us improve this project. To help us keep this collection
 high quality, we request that contributions adhere to the following guidelines.
-Any contributions that don't meet any of these guidelines will be closed.
+Any contributions that don't meet these guidelines will be closed.
 
 - **Provide a link to the application or project’s homepage**. Unless it’s
   extremely popular, there’s a chance the maintainers don’t know about or use
@@ -28,8 +28,9 @@ Any contributions that don't meet any of these guidelines will be closed.
 - **Only modify *one template* per pull request**. This helps keep pull
   requests and feedback focused on a specific project or technology.
 
-- **Add new rules to the best section**. Please ensure your contribution does
-  not create duplicate sections or add rules in places unrelated.
+- **Add new rules to the most appropriate existing section**. Please ensure
+  your contribution does not create duplicate sections or add rules in
+  unrelated sections.
 
 - **No duplicate rules**. It's easy to do, but it creates confusion and
   introduces the risk of one or the other being missed in an update.

README.md

@@ -37,7 +37,7 @@ We support a collection of templates, organized in this way:
 ## What makes a good template?
 
 First and foremost, a template contribution must adhere to our
-[Contribution Guidelines](CONTRIBUTING.md).
+[Contributing Guidelines](CONTRIBUTING.md).
 
 A template should contain a set of rules to help Git repositories work with a
 specific programming language, framework, tool or environment.