Add latest changes from gitlab-org/gitlab@14-2-stable-eev14.2.0-rc42

2 files changed, 9 insertions, 8 deletions

diff --git a/doc/user/analytics/index.md b/doc/user/analytics/index.md
index 8c67163c4b0..7cb5db4379a 100644
--- a/doc/user/analytics/index.md
+++ b/doc/user/analytics/index.md
@@ -11,25 +11,26 @@ info: To determine the technical writer assigned to the Stage/Group associated w
 When we describe GitLab analytics, we use the following terms:
 
 - **Cycle time:** The duration of only the execution work alone. Often displayed in combination with "lead time," which is longer. GitLab measures cycle time from issue first merge request creation to issue close. This approach underestimates lead time because merge request creation is always later than commit time. GitLab displays cycle time in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md).
-- **Deploys:** The total number of successful deployments to production in the given time frame (across all applicable projects). GitLab displays deploys in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md).
+- **Deploys:** The total number of successful deployments to production in the given time frame (across all applicable projects). GitLab displays deploys in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md) and [project-level Value Stream Analytics](value_stream_analytics.md).
 - **DORA (DevOps Research and Assessment)** ["Four Keys"](https://cloud.google.com/blog/products/devops-sre/using-the-four-keys-to-measure-your-devops-performance):
   - **Speed/Velocity**
 
-    - **Deployment frequency:** The average number of successful deployments to production per period.
+    - **Deployment frequency:** The relative frequency of successful deployments to production
+      (hourly, daily, weekly, monthly, or yearly).
       This effectively measures how often you are delivering value to end users. A higher deployment
       frequency means you are able to get feedback and iterate more quickly in delivering
       improvements and features faster. GitLab measures this as the number of deployments to a
       [production environment](../../ci/environments/index.md#deployment-tier-of-environments) in
       the given time period.
-      GitLab displays deployment frequency in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md).
+      GitLab displays deployment frequency in [group-level Value Stream Analytics](../group/value_stream_analytics/index.md) and [project-level Value Stream Analytics](value_stream_analytics.md).
     - **Lead Time for Changes:** The time it takes for a commit to get into production. (1) GitLab
       measures this as the median duration between merge request merge and deployment to a
       [production environment](../../ci/environments/index.md#deployment-tier-of-environments) for
       all MRs deployed in the given time period. This measure under-estimates lead time because
       merge time is always later than commit time. The
-      [standard definition](https://github.com/GoogleCloudPlatform/fourkeys/blob/main/METRICS.md#lead-time-for-changes) uses median commit time. We plan to start
-      [measuring from "issue first commit"](https://gitlab.com/gitlab-org/gitlab/-/issues/328459)
-      as a better proxy, although still imperfect.
+      [standard definition](https://github.com/GoogleCloudPlatform/fourkeys/blob/main/METRICS.md#lead-time-for-changes) uses median commit time.
+      [An issue exists](https://gitlab.com/gitlab-org/gitlab/-/issues/328459) to start
+      measuring from "issue first commit" as a better proxy, although still imperfect.
 
   - **Stability**
     - **Change Failure Rate:** The percentage of deployments causing a failure in production.
diff --git a/doc/user/analytics/value_stream_analytics.md b/doc/user/analytics/value_stream_analytics.md
index 4ad3a03a5b0..9a1aed9c39f 100644
--- a/doc/user/analytics/value_stream_analytics.md
+++ b/doc/user/analytics/value_stream_analytics.md
@@ -124,9 +124,9 @@ From the previous example we see the time used for each stage:
 - **Issue**: 2 hrs (09:00 to 11:00)
 - **Plan**: 1 hr (11:00 to 12:00)
 - **Code**: 2 hrs (12:00 to 14:00)
-- **Test**: 5 mins
+- **Test**: 5 minutes
 - **Review**: 5 hrs (14:00 to 19:00)
-- **Staging**: 30 mins (19:00 to 19:30)
+- **Staging**: 30 minutes (19:00 to 19:30)
 
 More information: