diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md
index 8e69b66..57fd474 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.md
+++ b/.github/ISSUE_TEMPLATE/bug_report.md
@@ -16,48 +16,42 @@ assignees: ''
   ⚠️ ⚠️ ⚠️ ⚠️ ⚠️ ⚠️
 -->
 
-#### Support plan
+### Support plan
 
 <!--
-We are here to help!
+  We are here to help!
 
-You do not need to pay to receive support. The free Community support plan is,
-by its nature, limited to community members available to help.
-Most community support issues are resolved within 2 weeks.
-
-Before submitting an issue, please review the various support plans available
-at https://hapi.dev/support/. That page includes useful information about
-faster and free channels to ask questions,
-as well as priority support options to meet your needs.
+  You do not need to pay to receive support. The free Community support plan is,
+  by its nature, limited to community members available to help.
+  Most community support issues are resolved within 2 weeks.
 -->
 
-- _which support plan is this issue covered by?_ (e.g. Community, Sponsor, or
-  Enterprise):
-- _is this issue currently blocking your project?_ (yes/no):
-- _is this issue affecting a production system?_ (yes/no):
+- Which support plan is this issue covered by? (Community, Sponsor, Enterprise):
+- Currently blocking your project/work? (yes/no):
+- Affecting a production system? (yes/no):
 
-#### Context
+### Context
 
-- _node version_:
-- _module version_:
-- _environment_ (e.g. node, browser, native):
-- _used with_ (i.e. popular names of modules):
-- _any other relevant information_:
+- Node.js version:
+- [Release Line](https://github.com/node-formidable/formidable/issues/769) of Formidable (Legacy, Current, Next):
+- Formidable exact version:
+- Environment (node, browser, native, OS):
+- Used with (popular names of modules):
 
-#### What are you trying to achieve or the steps to reproduce?
+### What are you trying to achieve or the steps to reproduce?
 
 <!--
-Describe your issue in detail, including full steps to reproduce the issue,
-any configuration, schemas, code samples, or inputs needed.
-Make sure to wrap all code examples in backticks so that they display correctly.
-Before submitting an issue, make sure to click on the Preview tab above to
-verify everything is formatted correctly.
+  Describe your issue in detail, including use cases, examples, and alternative
+  solutions you have already tried. Make sure to wrap all code examples
+  in backticks so that they display correctly. Before submitting an issue,
+  make sure to click on the Preview tab above to verify everything
+  is formatted correctly.
 -->
 
 ```js
 const some = 'properly formatted code example';
 ```
 
-#### What was the result you got?
+### What was the result you got?
 
-#### What result did you expect?
+### What result did you expect?
diff --git a/.github/ISSUE_TEMPLATE/feature_request.md b/.github/ISSUE_TEMPLATE/feature_request.md
index f33097f..0c4f0c1 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.md
+++ b/.github/ISSUE_TEMPLATE/feature_request.md
@@ -19,16 +19,11 @@ assignees: ''
 #### Support plan
 
 <!--
-We are here to help!
+  We are here to help!
 
-You do not need to pay to receive support. The free Community support plan is,
-by its nature, limited to community members available to help.
-Most community support issues are resolved within 2 weeks.
-
-Before submitting an issue, please review the various support plans available
-at https://hapi.dev/support/. That page includes useful information about
-faster and free channels to ask questions,
-as well as priority support options to meet your needs.
+  You do not need to pay to receive support. The free Community support plan is,
+  by its nature, limited to community members available to help.
+  Most community support issues are resolved within 2 weeks.
 -->
 
 - _which support plan is this issue covered by?_ (e.g. Community, Sponsor, or
@@ -39,15 +34,19 @@ as well as priority support options to meet your needs.
 #### Context
 
 - _node version_:
-- _module version_:
-- _environment_ (e.g. node, browser, native):
+- _module (formidable) version_:
+- _environment_ (e.g. node, browser, native, OS):
 - _used with_ (i.e. popular names of modules):
 - _any other relevant information_:
 
 #### What problem are you trying to solve?
 
 <!--
-Describe your issue in detail, including use cases, examples, and alternative solutions you have already tried. Make sure to wrap all code examples in backticks so that they display correctly. Before submitting an issue, make sure to click on the Preview tab above to verify everything is formatted correctly.
+  Describe your issue in detail, including use cases, examples, and alternative
+  solutions you have already tried. Make sure to wrap all code examples
+  in backticks so that they display correctly. Before submitting an issue,
+  make sure to click on the Preview tab above to verify everything
+  is formatted correctly.
 -->
 
 ```js
diff --git a/FUNDING.yml b/FUNDING.yml
index 9380a54..dd44fa8 100644
--- a/FUNDING.yml
+++ b/FUNDING.yml
@@ -1,3 +1,4 @@
+tidelift: npm/formidable
 ko_fi: tunnckoCore
 patreon: tunnckoCore
 github:
diff --git a/SECURITY.md b/SECURITY.md
index b60dbfe..f707355 100644
--- a/SECURITY.md
+++ b/SECURITY.md
@@ -69,7 +69,7 @@ HTTPS?"
 Any new code pushed to production is first thoroughly tested in a staging
 environment. Mechanisms are in place for rolling back any changes that are
 pushed to production. If a schema-change is involved, an inverse migration is
-first tested in staging (we want to be confident that we should role things
+first tested in staging (we want to be confident that we can roll things
 back).
 
 ### Unit Testing
@@ -102,7 +102,7 @@ life-cycle:
 
 This is a living document and may be updated from time to time. Please refer to
 the
-[git history](https://github.com/tunnckoCore/hela/commits/master/.github/SECURITY.md)
+[git history](https://github.com/node-formidable/.github/commits/master/SECURITY.md)
 for this document to view the changes.
 
 ### License