Refactor prose

Author: wooorm

.github/ISSUE_TEMPLATE/1-bug.yml

@@ -3,9 +3,9 @@ body:
       value: |
         Some general tips:
 
-        * Is this really a problem?
-        * Is this a problem here?
-        * Can this be solved in a different way?
+        * is this really a problem?
+        * is this a problem here?
+        * can this be solved in a different way?
     type: markdown
   - attributes:
       label: Initial checklist
@@ -32,7 +32,7 @@ body:
   - attributes:
       description: |
         Link to repository or sandbox with runnable example of the issue.
-        Alternatively, use the next section *Steps to reproduce*.
+        Alternatively use the next section *Steps to reproduce*.
       label: Link to runnable example
     id: runnable-example
     type: input
@@ -41,7 +41,7 @@ body:
   - attributes:
       description: |
         How did this happen?
-        Please provide a [minimal, reproducible example](https://stackoverflow.com/help/minimal-reproducible-example).
+        Please provide a [minimal and reproducible example](https://stackoverflow.com/help/minimal-reproducible-example).
       label: Steps to reproduce
     id: steps-to-reproduce
     type: textarea
@@ -64,7 +64,7 @@ body:
   - attributes:
       label: Affected runtime and version
       description: |
-        What runtime are you using (such as `[email protected]`, `[email protected]`)?
+        What runtime are you using (such as `[email protected]` or `[email protected]`)?
         Please test using the latest version.
     id: runtime
     type: input
@@ -90,7 +90,7 @@ body:
       required: false
   - attributes:
       description: |
-        What, if any, tools are used to build or bundle the project?
+        What tools are used to build or bundle the project?
         Please test using the latest version.
       label: Build and bundle tools
       multiple: true

.github/ISSUE_TEMPLATE/2-feature.yml

@@ -3,8 +3,8 @@ body:
       value: |
         Some general tips:
 
-        * Is this really a problem?
-        * Is this a problem here?
+        * is this really a problem?
+        * is this a problem here?
     type: markdown
   - attributes:
       label: Initial checklist

.github/pull-request-template.md

@@ -1,9 +1,9 @@
 <!--
   Please check the needed checkboxes ([ ] -> [x]).
-  Leave the comments as they are, they won’t show on GitHub.
-  We are excited about pull requests, but please try to limit the scope,
-  provide a general description of the changes, and remember, it’s up to you to
-  convince us to land it.
+  Leave the comments as they are: they won’t show on GitHub.
+  We are excited about pull requests but please try to limit the scope,
+  provide a general description of the changes,
+  and remember it’s up to you to convince us to land it.
 -->
 
 ### Initial checklist
@@ -12,7 +12,7 @@
 * [ ] I read the contributing guide <!-- https://github.com/syntax-tree/.github/blob/main/contributing.md -->
 * [ ] I agree to follow the code of conduct <!-- https://github.com/syntax-tree/.github/blob/main/code-of-conduct.md -->
 * [ ] I searched issues and couldn’t find anything (or linked relevant results below) <!-- https://github.com/search?q=user%3Asyntax-tree&type=Issues -->
-* [ ] If applicable, I’ve added docs and tests
+* [ ] I’ve added docs and tests or that’s not applicable
 
 ### Description of changes
 

.github/workflows/bb.yml

@@ -1,13 +1,13 @@
-name: bb
-on:
-  issues:
-    types: [opened, reopened, edited, closed, labeled, unlabeled]
-  pull_request_target:
-    types: [opened, reopened, edited, closed, labeled, unlabeled]
 jobs:
   main:
     runs-on: ubuntu-latest
     steps:
       - uses: unifiedjs/beep-boop-beta@main
         with:
           repo-token: ${{secrets.GITHUB_TOKEN}}
+name: bb
+on:
+  issues:
+    types: [closed, edited, labeled, opened, reopened, unlabeled]
+  pull_request_target:
+    types: [closed, edited, labeled, opened, reopened, unlabeled]

code-of-conduct.md

@@ -2,33 +2,47 @@
 
 ## Our pledge
 
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our collective
-and our community a harassment-free experience for everyone, regardless of age,
-body size, disability, ethnicity, sex characteristics, gender identity and
-expression, level of experience, education, socio-economic status, nationality,
-personal appearance, race, religion, or sexual identity and orientation.
+In the interest of fostering an open and welcoming environment,
+we as contributors and maintainers pledge to making participation in our
+collective and our community a harassment-free experience for everyone,
+regardless of age,
+body size,
+disability,
+ethnicity,
+sex characteristics,
+gender identity and expression,
+level of experience,
+education,
+socio-economic status,
+nationality,
+personal appearance,
+race,
+religion,
+or sexual identity and orientation.
 
 ## Our standards
 
 Examples of behavior that contributes to creating a positive environment
 include:
 
-* 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 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
 
 Examples of unacceptable behavior by participants include:
 
-* The use of sexualized language or imagery and unwelcome sexual attention or
+* 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
+* 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
 
 ## Our responsibilities
@@ -37,29 +51,46 @@ 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.
 
-Maintainers have the right and responsibility to edit, delete, hide, or lock
-code, comments, commits, edits, issues, posts, pull requests, 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 have the right and responsibility to edit,
+delete,
+hide,
+or lock code,
+comments,
+commits,
+edits,
+issues,
+posts,
+pull requests,
+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.
 
 ## Scope
 
 This code of conduct applies both within collective spaces and in public spaces
 when an individual is representing the collective or its community.
 Examples of representing a collective or community include using an official
-collective email address, posting via an official social media account, or
-acting as an appointed representative at an online or offline event.
+collective email address,
+posting via an official social media account,
+or acting as an appointed representative at an online or offline event.
 Representation of the collective may be further defined and clarified by
 maintainers.
 
 ## Enforcement
 
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported via the collective email address, `[email protected]`, which
-will go to all moderators, or by contacting individual moderators via
-`[email protected]`, which will go only to Richard Littauer, or to
-`[email protected]`, which will go only to Olivia Hugger.
+Instances of abusive,
+harassing,
+or otherwise unacceptable behavior may be reported via the collective email
+address,
+`[email protected]`,
+which will go to all moderators,
+or by contacting individual moderators via `[email protected]`,
+which will go only to Richard Littauer,
+or to `[email protected]`,
+which will go only to Olivia Hugger.
 All complaints will be reviewed and investigated and will result in a response
 that is deemed necessary and appropriate to the circumstances.
 The moderation team is obligated to maintain confidentiality with regard to the
@@ -71,28 +102,32 @@ face temporary or permanent repercussions as determined by other members of the
 collective leadership.
 
 In cases where community members transgress against the values in the code of
-conduct, members of the moderation team will use a three-strike warning system,
+conduct,
+members of the moderation team will use a three-strike warning system,
 where the aggressor will be warned twice before they are permanently excluded
 from our community spaces.
-This code applies to GitHub, Twitter, and any other space that this community
-uses for communication.
-For interactions between community members outside of this space, the code also
-applies if the interactions are reported and deemed to be interfering with
-community members safely working on the collective together.
+This code applies to GitHub,
+Twitter,
+and any other space that this community uses for communication.
+For interactions between community members outside of this space,
+the code also applies if the interactions are reported and deemed to be
+interfering with community members safely working on the collective together.
 Conversations between moderators (when they are more serious than discussing
-simple warnings) will occur in private repositories or through email, to ensure
-both anonymity for reporters and the safety of the moderators.
+simple warnings) will occur in private repositories or through email,
+to ensure both anonymity for reporters and the safety of the moderators.
 
 For more information on how to report violations and how the code of conduct is
-enforced, see our [moderation policy][moderation].
+enforced,
+see our [moderation policy][moderation].
 
 ## 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 1.4,
+available at <https://www.contributor-covenant.org/version/1/4/code-of-conduct.html>
 
-For answers to common questions about this code of conduct, see
-<https://www.contributor-covenant.org/faq>
+For answers to common questions about this code of conduct,
+see <https://www.contributor-covenant.org/faq>
 
 [homepage]: https://www.contributor-covenant.org