chore: update repository templates to ory/meta@19eed81

Author: aeneasr

.github/ISSUE_TEMPLATE/DESIGN-DOC.yml

@@ -6,7 +6,7 @@ name: "Design Document"
 body:
   - attributes:
       value: |
-        Thank you for writing this design document.
+        Thank you for writing this design document. 
 
         One of the key elements of Ory's software engineering culture is the use of defining software designs through design docs. These are relatively informal documents that the primary author or authors of a software system or application create before they embark on the coding project. The design doc documents the high level implementation strategy and key design decisions with emphasis on the trade-offs that were considered during those decisions.
 

.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 approval (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 the 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 approval (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 the necessary documentation within the code base (if appropriate).
 
 ## Further comments
 

CONTRIBUTING.md

@@ -47,9 +47,11 @@ contributions and don't 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 with Ory Examples's direction. A great way to do this is via
-[Ory Examples Discussions](https://github.com/orgs/ory/discussions) or the
-[Ory Chat](https://www.ory.sh/chat).
+won't clash with Ory
+Examples's direction. A great way to
+do this is via
+[Ory Examples Discussions](https://github.com/orgs/ory/discussions)
+or the [Ory Chat](https://www.ory.sh/chat).
 
 ## FAQ
 
@@ -66,7 +68,8 @@ won't clash with Ory Examples's direction. A great way to do this is via
 - I want to talk to other Ory Examples 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 Examples.
+- I would like to know what I am agreeing to when I contribute to Ory
+  Examples.
   Does Ory have
   [a Contributors License Agreement?](https://cla-assistant.io/ory/examples)
 
@@ -116,9 +119,8 @@ to help out:
 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 Examples 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 Examples 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 calls if you want to speak to the Ory team
 directly or ask some questions. You can find more info and participate in