From d34f8dca9594282c4772c8c8b5166ed8b4a3c808 Mon Sep 17 00:00:00 2001
From: Emily Burns <emjeburns@gmail.com>
Date: Wed, 29 Apr 2020 14:32:35 -0700
Subject: [PATCH] chore(PR): change wording to mark as bad

---
 _data/navigation.yml                          |  4 +--
 .../managed-delivery/marking-as-bad/index.md  | 29 +++++++++++++++++++
 guides/user/managed-delivery/vetoing/index.md | 29 -------------------
 3 files changed, 31 insertions(+), 31 deletions(-)
 create mode 100644 guides/user/managed-delivery/marking-as-bad/index.md
 delete mode 100644 guides/user/managed-delivery/vetoing/index.md

diff --git a/_data/navigation.yml b/_data/navigation.yml
index aea416c256..b568d4b320 100644
--- a/_data/navigation.yml
+++ b/_data/navigation.yml
@@ -462,8 +462,8 @@ guides:
           url: /guides/user/managed-delivery/artifacts/
         - title: Pinning an Environment
           url: /guides/user/managed-delivery/pinning/
-        - title: Vetoing an Artifact
-          url: /guides/user/managed-delivery/vetoing/
+        - title: Marking an Artifact as Bad
+          url: /guides/user/managed-delivery/marking-as-bad/
         - title: Resource Status
           url: /guides/user/managed-delivery/resource-status/
         - title: API
diff --git a/guides/user/managed-delivery/marking-as-bad/index.md b/guides/user/managed-delivery/marking-as-bad/index.md
new file mode 100644
index 0000000000..f509ceb7e7
--- /dev/null
+++ b/guides/user/managed-delivery/marking-as-bad/index.md
@@ -0,0 +1,29 @@
+---
+layout: single
+title: "Marking an Artifact as Bad"
+sidebar:
+  nav: guides
+---
+
+{% include toc %}
+
+You can mark a version of an artifact in an environment as bad to ensure that that version never gets deployed to the environment.
+If you mark an artifact as bad in the first in a series of environments (linked together by `depends-on` constraints) that version of the artifact will never be promoted into the later environments.
+
+### Marking via the API
+
+To mark the artifact via the API you'll need the application name, the name of the environment, the reference for your artifact (defined in your delivery config, defaulted to the artifact name), and the version that is bad.
+The request needs to have a body that contains [this information](https://github.com/spinnaker/gate/blob/master/gate-core/src/main/groovy/com/netflix/spinnaker/gate/model/manageddelivery/EnvironmentArtifactVeto.java). 
+Here's an example:
+
+`POST /managed/application/{application}/veto`
+
+with body: 
+```json
+
+{
+  "targetEnvironment": "test",
+  "reference" : "my-artifact",
+  "version" : "master-h10.62bbbd6"
+}
+```
diff --git a/guides/user/managed-delivery/vetoing/index.md b/guides/user/managed-delivery/vetoing/index.md
deleted file mode 100644
index 87af4253f6..0000000000
--- a/guides/user/managed-delivery/vetoing/index.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-layout: single
-title: "Vetoing a Version"
-sidebar:
-  nav: guides
----
-
-{% include toc %}
-
-You can veto a version in an environment to ensure that that version never gets deploy to the environment.
-If you veto an artifact in the first in a series of environments (linked together by `depends-on` constraints) the vetoed artifact will never be promoted into the later environments.
-
-### Vetoing via the API
-
-To veto via the API you'll need the application name, the name of the environment, the reference for your artifact (defined in your delivery config, defaulted to the artifact name), and the version you'd like to veto.
-The request needs to have a body that contains [this information](https://github.com/spinnaker/gate/blob/master/gate-core/src/main/groovy/com/netflix/spinnaker/gate/model/manageddelivery/EnvironmentArtifactVeto.java). 
-Here's an example:
-
-`POST /managed/application/{application}/veto`
-
-with body: 
-```json
-
-{
-  "targetEnvironment": "test",
-  "reference" : "my-artifact",
-  "version" : "master-h10.62bbbd6"
-}
-```