Revise metadata for consistency

Revise metadata for consistency

Revise metadata for consistency
bad19fc0 · Evan Read · Craig Norris · ff53a49b · bad19fc0 · bad19fc0
Commit bad19fc0 authored Jan 13, 2022 by Evan Read Committed by Craig Norris Jan 13, 2022
11 changed files
--- a/data/removals/14_0/remove_optimize_api.yml
+++ b/data/removals/14_0/remove_optimize_api.yml
- name: "Segments removed from DevOps Adoption API "
+- name: "Segments removed from DevOps Adoption API"
  removal_date: "2021-06-22"
  removal_milestone: "14.0"
  reporter: ljlane

--- a/doc/administration/logs.md
+++ b/doc/administration/logs.md
--- a/doc/administration/package_information/defaults.md
+++ b/doc/administration/package_information/defaults.md
 ---
 stage: Enablement
 group: Distribution
-info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#designated-technical-writers
+info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---

 # Package defaults **(FREE SELF)**

--- a/doc/administration/sidekiq.md
+++ b/doc/administration/sidekiq.md
@@ -2,7 +2,6 @@
 stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference
 ---

 # Configuring Sidekiq **(FREE SELF)**

--- a/doc/administration/sidekiq_health_check.md
+++ b/doc/administration/sidekiq_health_check.md
--- a/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md
+++ b/doc/administration/troubleshooting/gitlab_rails_cheat_sheet.md
@@ -2,7 +2,6 @@
 stage: Enablement
 group: Distribution
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference
 ---

 # GitLab Rails Console Cheat Sheet **(FREE SELF)**

--- a/doc/api/members.md
+++ b/doc/api/members.md
--- a/doc/ci/cloud_services/aws/index.md
+++ b/doc/ci/cloud_services/aws/index.md
--- a/doc/ci/cloud_services/index.md
+++ b/doc/ci/cloud_services/index.md
--- a/doc/ci/runners/configure_runners.md
+++ b/doc/ci/runners/configure_runners.md
@@ -2,7 +2,6 @@
 stage: Verify
 group: Runner
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
-type: reference
 ---

 # Configuring runners **(FREE)**

--- a/doc/development/database_review.md
+++ b/doc/development/database_review.md
@@ -140,7 +140,7 @@ of error that would result in corruption or loss of production data.
 Include in the MR description:

 - If the migration itself is not reversible, details of how data changes could be reverted in the event of an incident. For example, in the case of a migration that deletes records (an operation that most of the times is not automatically revertable), how _could_ the deleted records be recovered.
- If the migration deletes data apply the label `~data-deletion` 
+- If the migration deletes data, apply the label `~data-deletion`.
 - Concise descriptions of possible user experience impact of an error; for example, "Issues would unexpectedly go missing from Epics".
 - Relevant data from the [query plans](#query-plans) that indicate the query works as expected; such as the approximate number of records that will be modified/deleted.