chore: update repository templates

[skip ci] - updated repository templates to ory/meta@9a12e12

Author: aeneasr

.github/ISSUE_TEMPLATE/config.yml

@@ -1,7 +1,7 @@
 blank_issues_enabled: false
 contact_links:
   - name: Ory Documentation Forum
-    url: https://github.com/ory/docs/discussions
+    url: https://github.com/orgs/ory/discussions
     about:
       Please ask and answer questions here, show your implementations and
       discuss ideas.

.github/pull_request_template.md

@@ -34,20 +34,14 @@ Put an `x` in the boxes that apply. You can also fill these out after creating t
 them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
 -->
 
-- [ ] I have read the [contributing guidelines](../blob/master/CONTRIBUTING.md)
-      and signed the CLA.
-- [ ] I have referenced an issue containing the design document if my change
-      introduces a new feature.
+- [ ] I have read the [contributing guidelines](../blob/master/CONTRIBUTING.md) and signed the CLA.
+- [ ] I have referenced an issue containing the design document if my change introduces a new feature.
 - [ ] I have read the [security policy](../security/policy).
-- [ ] I confirm that this pull request does not address a security
-      vulnerability. If this pull request addresses a security vulnerability, I
-      confirm that I got green light (please contact
-      [[email protected]](mailto:[email protected])) from the maintainers to push
-      the changes.
-- [ ] I have added tests that prove my fix is effective or that my feature
-      works.
-- [ ] I have added necessary documentation within the code base (if
-      appropriate).
+- [ ] I confirm that this pull request does not address a security vulnerability. If this pull request addresses a security
+      vulnerability, I confirm that I got green light (please contact [[email protected]](mailto:[email protected])) from the
+      maintainers to push the changes.
+- [ ] I have added tests that prove my fix is effective or that my feature works.
+- [ ] I have added necessary documentation within the code base (if appropriate).
 
 ## Further comments
 

CONTRIBUTING.md

@@ -31,8 +31,8 @@ https://github.com/ory/meta/blob/master/templates/repository/common/CONTRIBUTING
 There are many ways in which you can contribute, beyond writing code. The goal of this document is to provide a high-level
 overview of how you can get involved.
 
-_Please note_: We take Ory Documentation's security and our users' trust very seriously. If you believe you have found a security
-issue in Ory Documentation, please responsibly disclose by contacting us at [email protected].
+_Please note_: We take Ory Documentation's security and our users' trust very seriously. If you believe you have found a security issue
+in Ory Documentation, please responsibly disclose by contacting us at [email protected].
 
 First: As a potential contributor, your changes and ideas are welcome at any hour of the day or night, weekdays, weekends, and
 holidays. Please do not ever hesitate to ask a question or send a pull request.
@@ -42,8 +42,11 @@ The worst that can happen is that you'll be politely asked to change something.
 want a wall of rules to get in the way of that.
 
 That said, if you want to ensure that a pull request is likely to be merged, talk to us! You can find out our thoughts and ensure
-that your contribution won't clash or be obviated by Ory Documentation's normal direction. A great way to do this is via
-[Ory Documentation Discussions](https://github.com/orgs/ory/discussions) or the [Ory Chat](https://www.ory.sh/chat).
+that your contribution won't clash or be obviated by Ory
+Documentation's normal direction. A great way to
+do this is via
+[Ory Documentation Discussions](https://github.com/orgs/ory/discussions) or the
+[Ory Chat](https://www.ory.sh/chat).
 
 ## FAQ
 
@@ -57,7 +60,9 @@ that your contribution won't clash or be obviated by Ory Documentation's normal
 
 - I want to talk to other Ory Documentation users. [How can I become a part of the community?](#communication)
 
-- I would like to know what I am agreeing to when I contribute to Ory Documentation. Does Ory have
+- I would like to know what I am agreeing to when I contribute to Ory
+  Documentation.
+  Does Ory have
   [a Contributors License Agreement?](https://cla-assistant.io/ory/docs)
 
 - I would like updates about new versions of Ory Documentation.
@@ -77,10 +82,9 @@ There are many other ways you can contribute without writing any code. Here are
   perspective. Join our Slack, have a look at discussions in the forum and take part in our weekly hangout. More info on this in
   [Communication](#communication).
 
-- **Helping with open issues.** We have a lot of open issues for Ory Documentation and some of them may lack necessary
-  information, some are duplicates of older issues. You can help out by guiding people through the process of filling out the
-  issue template, asking for clarifying information, or pointing them to existing issues that match their description of the
-  problem.
+- **Helping with open issues.** We have a lot of open issues for Ory Documentation and some of them may lack necessary information,
+  some are duplicates of older issues. You can help out by guiding people through the process of filling out the issue template,
+  asking for clarifying information, or pointing them to existing issues that match their description of the problem.
 
 - **Reviewing documentation changes.** Most documentation just needs a review for proper spelling and grammar. If you think a
   document can be improved in any way, feel free to hit the `edit` button at the top of the page. More info on contributing to
@@ -94,22 +98,22 @@ There are many other ways you can contribute without writing any code. Here are
 We use [Slack](https://www.ory.sh/chat). You are welcome to drop in and ask questions, discuss bugs and feature requests, talk to
 other users of Ory, etc.
 
-Check out [Ory Documentation Discussions](https://github.com/orgs/ory/discussions). This is a great place for in-depth discussions
-and lots of code examples, logs and similar data.
+Check out [Ory Documentation Discussions](https://github.com/orgs/ory/discussions). This is a great place for in-depth discussions and lots of code examples, logs
+and similar data.
 
 You can also join our community hangout, if you want to speak to the Ory team directly or ask some questions. You can find more
 info on the hangouts in [Slack](https://www.ory.sh/chat).
 
-If you want to receive regular notifications about updates to Ory Documentation, consider joining the mailing list. We will _only_
-send you vital information on the projects that you are interested in.
+If you want to receive regular notifications about updates to Ory Documentation, consider joining the mailing list. We will _only_ send
+you vital information on the projects that you are interested in.
 
 Also [follow us on twitter](https://twitter.com/orycorp).
 
 ## Contributing Code
 
 Unless you are fixing a known bug, we **strongly** recommend discussing it with the core team via a GitHub issue or
-[in our chat](https://www.ory.sh/chat) before getting started to ensure your work is consistent with Ory Documentation's roadmap
-and architecture.
+[in our chat](https://www.ory.sh/chat) before getting started to ensure your work is consistent with Ory Documentation's roadmap and
+architecture.
 
 All contributions are made via pull requests. To make a pull request, you will need a GitHub account; if you are unclear on this
 process, see GitHub's documentation on [forking](https://help.github.com/articles/fork-a-repo) and
@@ -130,7 +134,8 @@ Before creating a pull request, go through this checklist:
 If a pull request is not ready to be reviewed yet
 [it should be marked as a "Draft"](https://docs.github.com/en/github/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/changing-the-stage-of-a-pull-request).
 
-Before your contributions can be reviewed you need to sign our [Contributor License Agreement](https://cla-assistant.io/ory/docs).
+Before your contributions can be reviewed you need to sign our
+[Contributor License Agreement](https://cla-assistant.io/ory/docs).
 
 This agreement defines the terms under which your code is contributed to Ory. More specifically it declares that you have the
 right to, and actually do, grant us the rights to use your contribution. You can see the Apache 2.0 license under which our