From aef457e8717de492a469772996e9a3634470df09 Mon Sep 17 00:00:00 2001
From: David Shrewsbury <shrewsbury.dave@gmail.com>
Date: Fri, 16 Dec 2016 09:43:10 -0500
Subject: [PATCH] Correct bad image delete example

Example should use dib-image-delete to delete the build. The
image-delete option only deletes an upload from a provider.

Change-Id: I9b267a536eb05d491ad20ceadc686f301ac50d50
---
 doc/source/nodepool.rst | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/source/nodepool.rst b/doc/source/nodepool.rst
index ad556b3668..be5fdb4173 100644
--- a/doc/source/nodepool.rst
+++ b/doc/source/nodepool.rst
@@ -89,13 +89,13 @@ so, add ``paused: True`` to the ``diskimage`` section for
 
 Then delete the problematic image with::
 
-  $ sudo nodepool image-delete ubuntu-precise-0000000002
+  $ sudo nodepool dib-image-delete ubuntu-precise-0000000002
 
-All uploads corresponding to that image build will be deleted and the
-previous image will become the current image and nodepool will use it
-when creating new nodes.  When nodepool next creates an image, it will
-still retain build #1 since it will still be considered the
-next-most-recent image.
+All uploads corresponding to that image build will be deleted from providers
+before the image DIB files are deleted. The previous image will become the
+current image and nodepool will use it when creating new nodes. When nodepool
+next creates an image, it will still retain build #1 since it will still be
+considered the next-most-recent image.
 
 vhd-util
 ========