Fix wording: ReleaseV2 -> Releases V2

Author: iangmaia

.buildkite/release-pipelines/complete-code-freeze.yml

@@ -27,7 +27,7 @@ steps:
       bundle exec fastlane complete_code_freeze skip_confirm:true
     retry:
       manual:
-        # If failed, we prefer retrying via ReleaseV2 rather than Buildkite.
-        # Rationale: ReleaseV2 is the source of truth for the process and track links to the various builds.
-        reason: If release jobs fail, you should always re-trigger the task from ReleaseV2 rather than retrying the individual job from Buildkite
+        # If failed, we prefer retrying via Releases V2 rather than Buildkite.
+        # Rationale: Releases V2 is the source of truth for the process and track links to the various builds.
+        reason: If release jobs fail, you should always re-trigger the task from Releases V2 rather than retrying the individual job from Buildkite
         allowed: false

.buildkite/release-pipelines/finalize-release.yml

@@ -20,6 +20,6 @@ steps:
         queue: tumblr-metal
     retry:
       manual:
-        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
-        reason: If release jobs fail, you should always re-trigger the task from ReleaseV2 rather than retrying the individual job from Buildkite
+        # If those jobs fail, one should always prefer re-triggering a new build from Releases V2 rather than retrying the individual job from Buildkite
+        reason: If release jobs fail, you should always re-trigger the task from Releases V2 rather than retrying the individual job from Buildkite
         allowed: false

.buildkite/release-pipelines/new-beta-release.yml

@@ -23,7 +23,7 @@ steps:
         queue: tumblr-metal
     retry:
       manual:
-        # If failed, we prefer retrying via ReleaseV2 rather than Buildkite.
-        # Rationale: ReleaseV2 is the source of truth for the process and track links to the various builds.
-        reason: If release jobs fail, you should always re-trigger the task from ReleaseV2 rather than retrying the individual job from Buildkite
+        # If failed, we prefer retrying via Releases V2 rather than Buildkite.
+        # Rationale: Releases V2 is the source of truth for the process and track links to the various builds.
+        reason: If release jobs fail, you should always re-trigger the task from Releases V2 rather than retrying the individual job from Buildkite
         allowed: false

.buildkite/release-pipelines/publish-release.yml

@@ -20,6 +20,6 @@ steps:
       queue: tumblr-metal
     retry:
       manual:
-        # If those jobs fail, one should always prefer re-triggering a new build from ReleaseV2 rather than retrying the individual job from Buildkite
-        reason: If release jobs fail, you should always re-trigger the task from ReleaseV2 rather than retrying the individual job from Buildkite
+        # If those jobs fail, one should always prefer re-triggering a new build from Releases V2 rather than retrying the individual job from Buildkite
+        reason: If release jobs fail, you should always re-trigger the task from Releases V2 rather than retrying the individual job from Buildkite
         allowed: false

.buildkite/release-pipelines/start-code-freeze.yml

@@ -20,7 +20,7 @@ steps:
       bundle exec fastlane start_code_freeze version:"${RELEASE_VERSION}" skip_confirm:true
     retry:
       manual:
-        # If failed, we prefer retrying via ReleaseV2 rather than Buildkite.
-        # Rationale: ReleaseV2 is the source of truth for the process and track links to the various builds.
-        reason: If release jobs fail, you should always re-trigger the task from ReleaseV2 rather than retrying the individual job from Buildkite
+        # If failed, we prefer retrying via Releases V2 rather than Buildkite.
+        # Rationale: Releases V2 is the source of truth for the process and track links to the various builds.
+        reason: If release jobs fail, you should always re-trigger the task from Releases V2 rather than retrying the individual job from Buildkite
         allowed: false