Slight changes to reporting bugs and features

as recommended by @gundalow in review for #27911

docs/docsite/rst/community/reporting_bugs_and_features.rst

@@ -6,11 +6,11 @@ I'd Like To Report A Bug
 
 Ansible practices responsible disclosure - if this is a security related bug, email `security@ansible.com <mailto:security@ansible.com>`_ instead of filing a ticket or posting to the Google Group and you will receive a prompt response.
 
-Ansible bugs should be reported to `github.com/ansible/ansible <https://github.com/ansible/ansible>`_ after
+Ansible bugs should be reported to `github.com/ansible/ansible/issues <https://github.com/ansible/ansible/issues>`_ after
 signing up for a free GitHub account.  Before reporting a bug, please use the bug/issue search
 to see if the issue has already been reported. This is listed on the bottom of the docs page for any module.
 
-Knowing your ansible version and the exact commands you are running, and what you expect, saves time and helps us help everyone with their issues more quickly.
+Knowing your Ansible version and the exact commands you are running, and what you expect, saves time and helps us help everyone with their issues more quickly. For that reason, we provide an issue template; please fill it out as completely and as accurately as possible. 
 
 Do not use the issue tracker for "how do I do this" type questions.  These are great candidates for IRC or the mailing list instead where things are likely to be more of a discussion.
 
@@ -29,4 +29,4 @@ Requesting a feature
 
 The best way to get a feature into Ansible is to submit a pull request.
 
-The next best way of getting a feature into Ansible is to submit a proposal through the Ansible proposal process: https://github.com/ansible/proposals
+The next best way of getting a feature into Ansible is to submit a proposal through the `Ansible proposal process: <https://github.com/ansible/proposals>`.