From 0b9ae2b39b10ea08b752e61d6be0254728f5b0c6 Mon Sep 17 00:00:00 2001
From: scottda <scott.dangelo@hpe.com>
Date: Thu, 26 May 2016 10:58:01 -0600
Subject: [PATCH] Clarify use of cinder manage-snapshot command

The snapshot in the 'cinder mansage-snapshot' command refers
to a snapshot of a volume, but the documentation mentions
"A snapshot is an image created from a running instance". This is
misleading since that indicates that it is a Nova snapshot.
Also, it should be explicit that the volume refered to in the command
is the parent of the snapshot.

Change-Id: Ia958b571cbb59d5046661ff85f8545f4f56a140b
---
 doc/common/cli_manage_volumes.rst | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/doc/common/cli_manage_volumes.rst b/doc/common/cli_manage_volumes.rst
index 33afd303b0..a647241b38 100644
--- a/doc/common/cli_manage_volumes.rst
+++ b/doc/common/cli_manage_volumes.rst
@@ -574,7 +574,7 @@ Delete a volume transfer
 Manage and unmanage a snapshot
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
-A snapshot is an image created from a running instance. As an administrator,
+A snapshot is a point in time version of a volume. As an administrator,
 you can manage and unmanage snapshots.
 
 Manage a snapshot
@@ -589,7 +589,8 @@ Manage a snapshot with the :command:`cinder snapshot-manage` command:
 The arguments to be passed are:
 
 ``VOLUME_ID``
- The ID of an already existent volume.
+ The ID of a volume that is the parent of the snapshot, and managed by the
+ Block Storage service.
 
 ``IDENTIFIER``
  Name, ID, or other identifier for an existing snapshot.
@@ -607,8 +608,8 @@ The arguments to be passed are:
 :option:`--metadata`
  Metadata key-value pairs. Defaults to ``None``.
 
-The following example manages the ``my-snapshot-id`` image in the
-``my-volume-id`` volume:
+The following example manages the ``my-snapshot-id`` snapshot with the
+``my-volume-id`` parent volume:
 
 .. code-block:: console