From c618ec2303e7d578b011cc89c57b323680eee4ae Mon Sep 17 00:00:00 2001 From: Mark deVilliers Date: Tue, 16 Feb 2016 12:32:34 +0000 Subject: [PATCH] Tweaks to Flocker description --- docs/user-guide/volumes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/user-guide/volumes.md b/docs/user-guide/volumes.md index b59c1381448..404f991c3dc 100644 --- a/docs/user-guide/volumes.md +++ b/docs/user-guide/volumes.md @@ -319,8 +319,8 @@ See the [iSCSI example](../../examples/iscsi/) for more details. and orchestration of data volumes backed by a variety of storage backends. A `flocker` volume allows a Flocker dataset to be mounted into a pod. If the -dataset does not already exist in Flocker, it needs to be created with Flocker -CLI or the using the Flocker API. If the dataset already exists it will +dataset does not already exist in Flocker, it needs to be first created with the Flocker +CLI or by using the Flocker API. If the dataset already exists it will reattached by Flocker to the node that the pod is scheduled. This means data can be "handed off" between pods as required.