Update 202203210001_14_09.yml

data/whats_new/202203210001_14_09.yml

@@ -25,7 +25,7 @@
 - title: "Deployment Approval on the Environments page"
   body: |
     We are excited to introduce the Deployment Approval capability in the GitLab interface. In GitLab 14.8, we introduced the ability to approve deployments via the [API](https://docs.gitlab.com/ee/ci/environments/deployment_approvals.html#using-the-api). Now, deployment approvers can view a pending deployment and approve or reject it conveniently directly in the Environments page. This update continues our work to enable teams to create workflows for approving software to go to production or other protected environments. With this update, we are now upgrading the feature to beta.
-  stage: release
+  stage: "Release"
   self-managed: true
   gitlab-com: true
   packages: [Premium, Ultimate]
@@ -36,7 +36,7 @@
 - title: "New design for the Environments Page"
   body: |
     Previously, the Environments page enabled you to operate and understand deployments but the design hid some important information and was difficult to read. In GitLab 14.9, we made a comprehensive update to the page so that you can answer key questions about your environments and deployments. Now, you can easily see the status of the latest deployment, the status for various environments, and which commits have been deployed.
-  stage: release
+  stage: "Release"
   self-managed: true
   gitlab-com: true
   packages: [Free, Premium, Ultimate]
@@ -46,7 +46,7 @@
   release: 14.9
 - title: "Project Level Time to restore service API"
   body: |
-    In this release, we added API support for Time to Restore Service. This is the 3rd of the 4 [DORA Metrics](https://docs.gitlab.com/ee/user/analytics/ci_cd_analytics.html#devops-research-and-assessment-dora-key-metrics). This data helps teams continuously improve in their stability metrics. 
+    In this release, we added API support for Time to Restore Service. This is the 3rd of the 4 [DORA Metrics](https://docs.gitlab.com/ee/user/analytics/ci_cd_analytics.html#devops-research-and-assessment-dora-key-metrics). This data helps teams continuously improve in their stability metrics.
   stage: manage
   self-managed: true
   gitlab-com: true
@@ -66,12 +66,12 @@
     anyone not familiar with the specific security issue identified. This increases
     the time and friction involved in assessing and ultimately fixing security issues — especially
     in developer workflows.
-    
+
     We’re pleased to announce the launch of our new
     integrated security training functionality. Two new partners are providing the
     training content. GitLab is already where many developers are working, so we
     designed a solution to provide context-aware security training options from
-    inside the GitLab experience. 
+    inside the GitLab experience.
     Simply enable security training for your projects, select your preferred content sources, and view the results from a security scan. In the vulnerability finding, you'll find a direct link to the security training that most closely matches the particular security issue, and the specific language or framework in which it was detected. Now developers can spend a few quick minutes reviewing targeted, context-relevant training to address security issues as part of their
     normal development workflow.
@@ -83,4 +83,3 @@
   image_url: 'https://about.gitlab.com/images/14_9/secure-enable-security-training.png'
   published_at: 2022-03-22
   release: 14.9
-