Apply suggestions from code review

Co-authored-by: Léo Colombaro <LeoColomb@users.noreply.github.com>

Author: ozh

.github/ISSUE_TEMPLATE/PULL_REQUEST_TEMPLATE.md

@@ -1,9 +1,10 @@
-Pre-requisites :
-- [ ] I have read CONTRIBUTING.md 
-- [ ] I am using AI and have read AI_POLICY.md
+## Pre-requisites
 
+- [ ] I have read the [Contributing Guidelines](https://github.com/YOURLS/.github/blob/main/CONTRIBUTING.md)
+- [ ] I am using AI and have read the [AI Policy](https://github.com/YOURLS/.github/blob/main/AI_POLICY.md)
 
-## Description of your PR
+
+## Change Description
 <!--- Describe IN YOUR OWN WORDS your changes in detail. Why is this change required? What problem does it solve? --->
 
 

CONTRIBUTING.md

@@ -2,27 +2,33 @@
 
 ## Issue tracker
 
-Use it for bug reports, feature requests, and pull requests - but **not** for personal support (use [Discussions](https://github.com/YOURLS/YOURLS/discussions) instead).
+Use the issue tracker for bug reports, feature requests, and pull requests.
+Personal support must be discussed using [discussions space](https://github.com/orgs/YOURLS/discussions).
 
 ## Bug reports
 
-Before reporting: search existing issues (open and closed) and test against the latest `master`. A good report includes YOURLS/MySQL/PHP versions, expected vs actual output, and steps to reproduce the problem.
+Search existing issues (open and closed) before reporting.
+Ensure the alleged behavior is observed on the latest version.
+A good report includes YOURLS/MySQL/PHP versions, expected and actual behavior, and steps to reproduce the problem.
 
 ## Feature requests
 
-YOURLS aims to stay lean and cover the needs of the vast majority of users - if a feature wouldn't be useful to nearly everyone, it probably belongs in a plugin rather than core. The plugin architecture is specifically designed for that.
+YOURLS aims to stay lean and cover the needs of the vast majority of users.
+If a feature wouldn't be useful to nearly everyone, it probably belongs in a plugin rather than core.
+The [plugin architecture](https://yourls.org/docs/development/plugins) is designed to extend core behavior for the custom use cases.
 
 Make sure your idea fits the project's scope, and provide context to make a strong case.
 
 ## Pull requests
 
 - It's better to ask before starting any significant work.
-- Using AI ? Read our [AI_POLICY.md](AI_POLICY.md)
-- Keep PRs focused - one concern per PR, and avoid unrelated changes such as whitespace fixes or rewording comments elsewhere in the codebase.
+- AI use must follow our [AI Policy](AI_POLICY.md).
+- Keep pull requests focused. 
+- Limit pull requests to a single concern.
+- Avoid unrelated changes such as whitespace fixes or rewording comments elsewhere in the codebase.
 - Follow existing coding conventions.
 - Unit tests are very welcome.
 - Your code will be licensed under the [MIT License](https://github.com/YOURLS/YOURLS/blob/master/LICENSE).
 
-Standard flow: fork → branch off `master` → commit in logical chunks → push → open PR and fill the template.
 
-## ❤️ Thank you !
+❤️ Thank you !