♻️ refactor(project): apply the house style

.github/ISSUE_TEMPLATE/pyproject-fmt-bug.yml

@@ -1,51 +1,46 @@
-name: "🐛 pyproject-fmt: Bug Report"
+name: "pyproject-fmt bug"
 description: Report a bug in pyproject-fmt
 labels: ["bug", "pyproject-fmt"]
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for taking the time to report a bug in pyproject-fmt.
-        Please fill out the sections below to help us understand and reproduce the issue.
   - type: textarea
     id: description
     attributes:
-      label: 📝 Description
-      description: A clear and concise description of what the bug is.
-      placeholder: Describe the issue you encountered...
+      label: Description
+      description: Describe the failure and how to reproduce it.
+      placeholder: What command did you run, and what happened?
     validations:
       required: true
   - type: textarea
     id: input
     attributes:
-      label: 📄 Input pyproject.toml
-      description: The pyproject.toml content that triggers the bug.
-      placeholder: Paste the relevant portion of your pyproject.toml here
+      label: Input pyproject.toml
+      description: Include the smallest file that reproduces the failure.
+      placeholder: Paste TOML here
       render: toml
     validations:
       required: true
   - type: textarea
     id: expected
     attributes:
-      label: ✅ Expected output
-      description: What you expected the formatted output to look like.
+      label: Expected output
+      description: Show the expected TOML.
       render: toml
   - type: textarea
     id: actual
     attributes:
-      label: ❌ Actual output
-      description: What actually happened (formatted output or error message).
+      label: Actual output
+      description: Show the resulting TOML or error.
       render: toml
   - type: input
     id: version
     attributes:
-      label: 🏷️ Version
-      description: Output of `pyproject-fmt --version`
+      label: Version
+      description: Paste the output of `pyproject-fmt --version`.
       placeholder: "pyproject-fmt 2.x.x"
     validations:
       required: true
   - type: textarea
     id: additional
     attributes:
-      label: 📎 Additional context
-      description: Any other relevant context (OS, Python version, configuration options used).
+      label: Environment
+      description: Include the operating system, Python version, and relevant formatter settings.

.github/ISSUE_TEMPLATE/pyproject-fmt-feature.yml

@@ -1,36 +1,31 @@
-name: "✨ pyproject-fmt: Feature Request"
+name: "pyproject-fmt feature"
 description: Suggest an enhancement for pyproject-fmt
 labels: ["enhancement", "pyproject-fmt"]
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for suggesting an improvement to pyproject-fmt.
-        Please describe your idea so we can understand the use case and potential implementation.
   - type: textarea
     id: description
     attributes:
-      label: 📝 Description
-      description: A clear and concise description of the feature you'd like.
-      placeholder: Describe the feature or improvement...
+      label: Proposal
+      description: Describe the requested formatter behavior.
+      placeholder: What should pyproject-fmt do?
     validations:
       required: true
   - type: textarea
     id: use-case
     attributes:
-      label: 🎯 Use case
-      description: Explain the problem this would solve or the workflow it would improve.
-      placeholder: This would help when...
+      label: Use case
+      description: Explain the current problem and who encounters it.
+      placeholder: Include a concrete workflow or file.
     validations:
       required: true
   - type: textarea
     id: example
     attributes:
-      label: 📄 Example
-      description: If applicable, show an example of the desired input/output behavior.
+      label: Example
+      description: Show input and expected output when possible.
       render: toml
   - type: textarea
     id: alternatives
     attributes:
-      label: 🔄 Alternatives considered
-      description: Any alternative solutions or workarounds you've considered.
+      label: Alternatives
+      description: List current workarounds or other designs you considered.

.github/ISSUE_TEMPLATE/tox-toml-fmt-bug.yml

@@ -1,51 +1,46 @@
-name: "🐛 tox-toml-fmt: Bug Report"
+name: "tox-toml-fmt bug"
 description: Report a bug in tox-toml-fmt
 labels: ["bug", "tox-toml-fmt"]
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for taking the time to report a bug in tox-toml-fmt.
-        Please fill out the sections below to help us understand and reproduce the issue.
   - type: textarea
     id: description
     attributes:
-      label: 📝 Description
-      description: A clear and concise description of what the bug is.
-      placeholder: Describe the issue you encountered...
+      label: Description
+      description: Describe the failure and how to reproduce it.
+      placeholder: What command did you run, and what happened?
     validations:
       required: true
   - type: textarea
     id: input
     attributes:
-      label: 📄 Input tox.toml
-      description: The tox.toml content that triggers the bug.
-      placeholder: Paste the relevant portion of your tox.toml here
+      label: Input tox.toml
+      description: Include the smallest file that reproduces the failure.
+      placeholder: Paste TOML here
       render: toml
     validations:
       required: true
   - type: textarea
     id: expected
     attributes:
-      label: ✅ Expected output
-      description: What you expected the formatted output to look like.
+      label: Expected output
+      description: Show the expected TOML.
       render: toml
   - type: textarea
     id: actual
     attributes:
-      label: ❌ Actual output
-      description: What actually happened (formatted output or error message).
+      label: Actual output
+      description: Show the resulting TOML or error.
       render: toml
   - type: input
     id: version
     attributes:
-      label: 🏷️ Version
-      description: Output of `tox-toml-fmt --version`
+      label: Version
+      description: Paste the output of `tox-toml-fmt --version`.
       placeholder: "tox-toml-fmt 1.x.x"
     validations:
       required: true
   - type: textarea
     id: additional
     attributes:
-      label: 📎 Additional context
-      description: Any other relevant context (OS, Python version, configuration options used).
+      label: Environment
+      description: Include the operating system, Python version, and relevant formatter settings.

.github/ISSUE_TEMPLATE/tox-toml-fmt-feature.yml

@@ -1,36 +1,31 @@
-name: "✨ tox-toml-fmt: Feature Request"
+name: "tox-toml-fmt feature"
 description: Suggest an enhancement for tox-toml-fmt
 labels: ["enhancement", "tox-toml-fmt"]
 body:
-  - type: markdown
-    attributes:
-      value: |
-        Thank you for suggesting an improvement to tox-toml-fmt.
-        Please describe your idea so we can understand the use case and potential implementation.
   - type: textarea
     id: description
     attributes:
-      label: 📝 Description
-      description: A clear and concise description of the feature you'd like.
-      placeholder: Describe the feature or improvement...
+      label: Proposal
+      description: Describe the requested formatter behavior.
+      placeholder: What should tox-toml-fmt do?
     validations:
       required: true
   - type: textarea
     id: use-case
     attributes:
-      label: 🎯 Use case
-      description: Explain the problem this would solve or the workflow it would improve.
-      placeholder: This would help when...
+      label: Use case
+      description: Explain the current problem and who encounters it.
+      placeholder: Include a concrete workflow or file.
     validations:
       required: true
   - type: textarea
     id: example
     attributes:
-      label: 📄 Example
-      description: If applicable, show an example of the desired input/output behavior.
+      label: Example
+      description: Show input and expected output when possible.
       render: toml
   - type: textarea
     id: alternatives
     attributes:
-      label: 🔄 Alternatives considered
-      description: Any alternative solutions or workarounds you've considered.
+      label: Alternatives
+      description: List current workarounds or other designs you considered.

.github/SECURITY.md

@@ -2,12 +2,9 @@
 
 ## Supported Versions
 
-| Version | Supported          |
-| ------- | ------------------ |
-| 1.0 +   | :white_check_mark: |
-| < 1.0   | :x:                |
+Version 1.0 and later receives security updates. Earlier releases do not.
 
 ## Reporting a Vulnerability
 
-To report a security vulnerability, please use the [Tidelift security contact](https://tidelift.com/security). Tidelift
-will coordinate the fix and disclosure.
+Report vulnerabilities through the [Tidelift security contact](https://tidelift.com/security). Tidelift coordinates the
+fix and disclosure.

CODE_OF_CONDUCT.md

@@ -1,60 +1,50 @@
 # Contributor Covenant Code of Conduct
 
-## Our Pledge
+## Pledge
 
-In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making
-participation in our project and our community a harassment-free experience for everyone, regardless of age, body size,
-disability, ethnicity, gender identity and expression, level of experience, nationality, personal appearance, race,
-religion, or sexual identity and orientation.
+Contributors and maintainers commit to a harassment-free community without regard to age, body size, disability,
+ethnicity, gender identity or expression, experience, nationality, appearance, race, religion, sexual identity, or
+sexual orientation.
 
-## Our Standards
+## Standards
 
-Examples of behavior that contributes to creating a positive environment include:
+Expected conduct includes:
 
-- Using welcoming and inclusive language
-- Being respectful of differing viewpoints and experiences
-- Gracefully accepting constructive criticism
-- Focusing on what is best for the community
-- Showing empathy towards other community members
+- using inclusive language;
+- respecting different viewpoints and experiences;
+- accepting constructive criticism;
+- putting the community's interests first;
+- showing empathy toward other community members.
 
-Examples of unacceptable behavior by participants include:
+Unacceptable conduct includes:
 
-- The use of sexualized language or imagery and unwelcome sexual attention or advances
-- Trolling, insulting/derogatory comments, and personal or political attacks
-- Public or private harassment
-- Publishing others' private information, such as a physical or electronic address, without explicit permission
-- Other conduct which could reasonably be considered inappropriate in a professional setting
+- sexualized language, imagery, attention, or advances;
+- trolling, insults, derogatory comments, or personal and political attacks;
+- public or private harassment;
+- publishing another person's private information without permission;
+- conduct that a professional setting would reject.
 
-## Our Responsibilities
+## Maintainer responsibilities
 
-Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take
-appropriate and fair corrective action in response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits,
-issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any
-contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
+Maintainers clarify these standards and respond to violations under this code. They may remove or reject comments,
+commits, code, wiki edits, issues, or other contributions that violate this code. They may also ban contributors whose
+conduct is threatening, offensive, or harmful.
 
 ## Scope
 
-This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the
-project or its community. Examples of representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed representative at an online or offline
-event. Representation of a project may be further defined and clarified by project maintainers.
+This code applies in project spaces and when someone represents the project in public. Representation includes using a
+project email address or social account and acting as an appointed representative at an event. Maintainers may define
+other forms of representation.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at
-gaborbernat@python.org. The project team will review and investigate all complaints, and will respond in a way that it
-deems appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the
-reporter of an incident. Further details of specific enforcement policies may be posted separately.
+Report abusive, harassing, or unacceptable conduct to gaborbernat@python.org. The project team will investigate and
+respond according to the circumstances while protecting the reporter's identity.
 
-Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent
-repercussions as determined by other members of the project's leadership.
+Maintainers who fail to enforce this code in good faith may face consequences set by other project leaders.
 
 ## Attribution
 
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4, available at
-[https://www.contributor-covenant.org/version/1/4/code-of-conduct.html][version]
+Adapted from [Contributor Covenant 1.4][version].
 
-[homepage]: https://www.contributor-covenant.org/
-[version]: https://www.contributor-covenant.org/version/1/4/
+[version]: https://www.contributor-covenant.org/version/1/4/code-of-conduct.html