chore: revert breaking lines at 90 chars in markdown files

Author: TasoOneAsia

CONTRIBUTING.md

@@ -1,7 +1,6 @@
 # Contributing Guidelines
 
-The following is a set of guidelines for contributing to this project. We really appreciate that you are considering
-contributing!
+The following is a set of guidelines for contributing to this project. We really appreciate that you are considering contributing!
 
 #### Table Of Contents
 
@@ -15,57 +14,42 @@ contributing!
 
 ## Getting Started
 
-Refer to the [Getting Started Guide](docs/getting_started.md) for how to build
-and run the gateway.
+Refer to the [Getting Started Guide](docs/getting_started.md) for how to build and run the gateway.
 
 ## Contributing
 
 ### Report a Bug
 
-To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please
-ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using
-our [security policy](/SECURITY.md).**
+To report a bug, open an issue on GitHub with the label `bug` using the available bug report issue template. Please ensure the bug has not already been reported. **If the bug is a potential security vulnerability, please report it using our [security policy](/SECURITY.md).**
 
 ### Suggest a Feature or Enhancement
 
-To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the
-available [feature request template](/.github/feature_request_template.md). Please ensure the feature or enhancement has
-not already been suggested.
+To suggest a feature or enhancement, please create an issue on GitHub with the label `enhancement` using the available [feature request template](/.github/feature_request_template.md). Please ensure the feature or enhancement has not already been suggested.
 
 ### Open a Pull Request (PR)
 
-- Fork the repo, create a branch, implement your changes, add any relevant tests, and submit a PR when your changes are
-  **tested** and ready for review.
+- Fork the repo, create a branch, implement your changes, add any relevant tests, and submit a PR when your changes are **tested** and ready for review.
 - Fill in the [PR template](/.github/pull_request_template.md).
 
-**Note:** If you'd like to implement a new feature, please consider creating
-a [feature request issue](/.github/feature_request_template.md) first to start a discussion about the feature.
+**Note:** If you'd like to implement a new feature, please consider creating a [feature request issue](/.github/feature_request_template.md) first to start a discussion about the feature.
 
 #### F5 Contributor License Agreement (CLA)
 
-F5 requires all external contributors to agree to the terms of the F5 CLA (
-available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)) before any of their changes can be
-incorporated into an F5 Open Source repository.
+F5 requires all external contributors to agree to the terms of the F5 CLA (available [here](https://github.com/f5/.github/blob/main/CLA/cla-markdown.md)) before any of their changes can be incorporated into an F5 Open Source repository.
 
-If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and
-agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes
-can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs.
+If you have not yet agreed to the F5 CLA terms and submit a PR to this repository, a bot will prompt you to view and agree to the F5 CLA. You will have to agree to the F5 CLA terms through a comment in the PR before any of your changes can be merged. Your agreement signature will be safely stored by F5 and no longer be required in future PRs.
 
 ## Code Guidelines
 
 <!-- ### Go/Python/Bash/etc... Guidelines (OPTIONAL) -->
 
 ### Git Guidelines
 
-- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing
-  before submitting a PR.
-- If possible and/or relevant, use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format
-  when writing a commit message, so that changelogs can be automatically generated.
-- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/>
-  and summarized in the next few points:
-    - In the subject line, use the present tense ("Add feature" not "Added feature").
-    - In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
-    - Limit the subject line to 72 characters or less.
-    - Reference issues and pull requests liberally after the subject line.
-    - Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in
-      your text editor to write a good message instead of `git commit -am`).
+- Keep a clean, concise and meaningful git commit history on your branch (within reason), rebasing locally and squashing before submitting a PR.
+- If possible and/or relevant, use the [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/) format when writing a commit message, so that changelogs can be automatically generated.
+- Follow the guidelines of writing a good commit message as described here <https://chris.beams.io/posts/git-commit/> and summarized in the next few points:
+  - In the subject line, use the present tense ("Add feature" not "Added feature").
+  - In the subject line, use the imperative mood ("Move cursor to..." not "Moves cursor to...").
+  - Limit the subject line to 72 characters or less.
+  - Reference issues and pull requests liberally after the subject line.
+  - Add more detailed description in the body of the git message (`git commit -a` to give you more space and time in your text editor to write a good message instead of `git commit -am`).

SUPPORT.md

@@ -4,39 +4,30 @@
 
 We use GitHub for tracking bugs and feature requests related to this project.
 
-Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please
-open an issue on GitHub with the label `question`. Alternatively, start a GitHub discussion!
+Don't know how something in this project works? Curious if this project can achieve your desired functionality? Please open an issue on GitHub with the label `question`. Alternatively, start a GitHub discussion!
 
 ## NGINX Specific Questions and/or Issues
 
-This isn't the right place to get support for NGINX specific questions, but the following resources are available below.
-Thanks for your understanding!
+This isn't the right place to get support for NGINX specific questions, but the following resources are available below. Thanks for your understanding!
 
 ### Community Forum
 
-We have a community [forum](https://community.nginx.org/)! If you have any questions and/or issues, try checking out
-the [`Troubleshooting`](https://community.nginx.org/c/troubleshooting/8) and [
-`How do I...?`](https://community.nginx.org/c/how-do-i/9) categories. Both fellow community members and NGINXers might
-be able to help you! :)
+We have a community [forum](https://community.nginx.org/)! If you have any questions and/or issues, try checking out the [`Troubleshooting`](https://community.nginx.org/c/troubleshooting/8) and [`How do I...?`](https://community.nginx.org/c/how-do-i/9) categories. Both fellow community members and NGINXers might be able to help you! :)
 
 ### Documentation
 
 For a comprehensive list of all NGINX directives, check out <https://nginx.org>.
 
-For a comprehensive list of administration and deployment guides for all NGINX products, check
-out <https://docs.nginx.com>.
+For a comprehensive list of administration and deployment guides for all NGINX products, check out <https://docs.nginx.com>.
 
 ### Mailing List
 
-Want to get in touch with the NGINX development team directly? Try using the relevant mailing list found
-at <https://mailman.nginx.org/mailman3/lists/>!
+Want to get in touch with the NGINX development team directly? Try using the relevant mailing list found at <https://mailman.nginx.org/mailman3/lists/>!
 
 ## Contributing
 
-Please see the [contributing guide](/CONTRIBUTING.md) or the [Getting Started](/README.md#getting-started) guide, for
-guidelines on how to best contribute to this project.
+Please see the [contributing guide](/CONTRIBUTING.md) or the [Getting Started](/README.md#getting-started) guide, for guidelines on how to best contribute to this project.
 
 ## Community Support
 
-This project does **not** offer commercial support. Community support is offered on a best effort basis through either
-GitHub issues/PRs/discussions or through any of our active communities.
+This project does **not** offer commercial support. Community support is offered on a best effort basis through either GitHub issues/PRs/discussions or through any of our active communities.