Documentation - fix link for Wagtail community support

CHANGELOG.txt

@@ -11,6 +11,7 @@ Changelog
  * Fix: Ensure authentication forms (login, password reset) have a visible border in Windows high-contrast mode (Loveth Omokaro)
  * Fix: Ensure visual consistency between buttons and links as buttons in Windows high-contrast mode (Albina Starykova)
  * Fix: references extraction for ChooserBlock (Alex Tomkins)
+ * Fix: Incorrectly formatted link in the documentation for Wagtail community support (Bolarinwa Comfort Ajayi)
 
 
 4.1 LTS (xx.xx.xxxx) - IN DEVELOPMENT

CONTRIBUTORS.rst

@@ -645,6 +645,7 @@ Contributors
 * Dokua Asiedu
 * Darrel O'Pry
 * Mary Ayobami
+* Bolarinwa Comfort Ajayi
 
 Translators
 ===========

docs/contributing/issue_tracking.md

@@ -6,7 +6,7 @@ We welcome bug reports, feature requests and pull requests through Wagtail's [Gi
 
 An issue must always correspond to a specific action with a well-defined completion state: fixing a bug, adding a new feature, updating documentation, or cleaning up code. Open-ended issues where the end result is not immediately clear ("come up with a way of doing translations" or "Add more features to rich text fields.") are better suited to [Github discussions](https://github.com/wagtail/wagtail/discussions), so that there can be feedback on clear way to progress the issue and identify when it has been completed through separate issues created from the discussion.
 
-Do not use issues for support queries or other questions ("How do I do X?" - although "Implement a way of doing X" or "Document how to do X" could well be valid issues). These should be asked on [Stack Overflow](https://stackoverflow.com/questions/tagged/wagtail) instead. For discussions that do not fit Stack Overflow's question-and-answer format, see the other (Wagtail community support options)[https://github.com/wagtail/wagtail#community-support].
+Do not use issues for support queries or other questions ("How do I do X?" - although "Implement a way of doing X" or "Document how to do X" could well be valid issues). These questions should be asked on [Stack Overflow](https://stackoverflow.com/questions/tagged/wagtail) instead. For discussions that do not fit Stack Overflow's question-and-answer format, see the other [Wagtail community support options](https://github.com/wagtail/wagtail#community-support).
 
 As soon as a ticket is opened - ideally within one day - a member of the core team will give it an initial classification, by either closing it due to it being invalid or updating it with the relevant labels. When a bug is opened, it will automatically be assigned the [`type:Bug`](https://github.com/wagtail/wagtail/labels/type%3ABug) and [`status:Unconfirmed`](https://github.com/wagtail/wagtail/labels/status%3AUnconfirmed) labels, once confirmed the bug can have the unconfirmed status removed. A member of the team will potentially also add a release milestone to help guide the priority of this issue. Anyone is invited to help Wagtail with reproducing `status:Unconfirmed` bugs and commenting if it is a valid bug or not with additional steps to reproduce if needed.
 

docs/releases/4.2.md

@@ -24,6 +24,7 @@ depth: 1
  * Ensure authentication forms (login, password reset) have a visible border in Windows high-contrast mode (Loveth Omokaro)
  * Ensure visual consistency between buttons and links as buttons in Windows high-contrast mode (Albina Starykova)
  * Ensure `ChooserBlock.extract_references` uses the model class, not the model string (Alex Tomkins)
+ * Incorrectly formatted link in the documentation for Wagtail community support (Bolarinwa Comfort Ajayi)
 
 ## Upgrade considerations