diff --git a/.gitlab/issue_templates/Web IDE Category - issue.md b/.gitlab/issue_templates/Web IDE Category - issue.md
index 09cb51cf0699ee4a6f0bb165abc2f9690a12f369..4271cbf96edf97881332ba27af97235706183712 100644
--- a/.gitlab/issue_templates/Web IDE Category - issue.md	
+++ b/.gitlab/issue_templates/Web IDE Category - issue.md	
@@ -1,4 +1,5 @@
 MR: Pending
+
 <!--
 The first line of this issue description must be one of the following:
 
@@ -13,7 +14,7 @@ The first line of this issue description must be one of the following:
    ```
 4. `MR: No MR`
 
-...and the first description line of the MR should be `Issue: <Issue link with trailing +>` 
+...and the first description line of the MR should be `Issue: <Issue link with trailing +>`
 
 For more context, see:
 https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#relationship-of-issues-to-mrs
@@ -37,6 +38,7 @@ As a [user or stakeholder], I want [goal or objective] so that [reason or benefi
 ## Acceptance Criteria
 
 TODO: Fill out (required)
+
 - [ ] [Describe what must be achieved to complete this issue.]
 - [ ] [Describe another requirement needed to complete this issue.]
 - [ ] [Add additional acceptance criteria as needed.]
@@ -61,19 +63,23 @@ TODO: Fill out or delete (optional)
 TODO: Fill out or delete (optional)
 [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.]
 
-
 /label ~"Category:Web IDE"
-/label  ~"section::dev"
-/label  ~"devops::create"
-/label  ~"group::ide"
+/label ~"section::dev"
+/label ~"devops::create"
+/label ~"group::ide"
 
 <!-- Replace with other type, e.g. bug or maintenance, if appropriate -->
+
 /label ~"type::feature"
+
 <!-- Replace with other subtype if appropriate -->
+
 /label ~"feature::addition"
 
 <!-- By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process -->
-/label  ~"rd-workflow::unprioritized"
 
-<!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase --> 
+/label ~"webide-workflow::unprioritized"
+
+<!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->
+
 /label ~"workflow::refinement"