remove dashes

Author: lucacome

.github/labels.yml

@@ -3,7 +3,7 @@
   name: backlog
 - color: A90EA3
   description: Pull requests/issues that are candidates to be backlog items
-  name: backlog-candidate
+  name: backlog candidate
 - color: fc2929
   description: An issue reporting a potential bug
   name: bug
@@ -60,7 +60,7 @@
   name: question
 - color: FEF2C0
   description: Pull requests that don't need to be added to the changelog
-  name: skip-changelog
+  name: skip changelog
 - color: 8E7888
   description: Pull requests/issues with no activity
   name: stale

.github/release.yml

@@ -1,7 +1,7 @@
 changelog:
   exclude:
     labels:
-      - skip-changelog
+      - skip changelog
   categories:
     - title: 🚀 Features
       labels:

ISSUE_LIFECYCLE.md

@@ -21,14 +21,14 @@ To ensure a balance between work carried out by the NGINX engineering team while
 
 4. Determine milestone: The owner, in collaboration with the wider team (PM & engineering), determines what milestone to attach to an issue. Generally, milestones correspond to product releases - however there are two 'magic' milestones with special meanings (not tied to a specific release):
 
-   - Issues assigned to backlog: Our team is in favour of implementing the feature request/fixing the issue, however the implementation is not yet assigned to a concrete release. If and when a `backlog` issue aligns well with our roadmap, it will be scheduled for a concrete iteration. We review and update our roadmap at least once every quarter. The `backlog` list helps us shape our roadmap, but it is not the only source of input. Therefore, some `backlog` items may eventually be closed as `out of scope`, or relabelled as `backlog-candidate` once it becomes clear that they do not align with our evolving roadmap.
+   - Issues assigned to backlog: Our team is in favour of implementing the feature request/fixing the issue, however the implementation is not yet assigned to a concrete release. If and when a `backlog` issue aligns well with our roadmap, it will be scheduled for a concrete iteration. We review and update our roadmap at least once every quarter. The `backlog` list helps us shape our roadmap, but it is not the only source of input. Therefore, some `backlog` items may eventually be closed as `out of scope`, or relabelled as `backlog candidate` once it becomes clear that they do not align with our evolving roadmap.
 
-   - Issues assigned to `backlog-candidate`: Our team does not intend to implement the feature/fix request described in the issue and wants the community to weigh in before we make our final decision.
+   - Issues assigned to `backlog candidate`: Our team does not intend to implement the feature/fix request described in the issue and wants the community to weigh in before we make our final decision.
 
     `backlog` issues can be labeled by the owner as `help wanted` and/or `good first issue` as appropriate.
 
 
-5. Promotion of `backlog-candidate` issue to `backlog` issue: If an issue labelled `backlog-candidate` receives more than 30 upvotes within 60 days, we promote the issue by applying the `backlog` label. While issues promoted in this manner have not been committed to a particular release, we welcome PRs from the community on them.
+5. Promotion of `backlog candidate` issue to `backlog` issue: If an issue labelled `backlog candidate` receives more than 30 upvotes within 60 days, we promote the issue by applying the `backlog` label. While issues promoted in this manner have not been committed to a particular release, we welcome PRs from the community on them.
 
    If an issue does not make our roadmap and has not been moved to a discussion, it is closed with the label `out of scope`. The goal is to get every issue in the issues list to one of the following end states: