From 36c7b73ba78f0939ed4baa049d33fa78ce3faa22 Mon Sep 17 00:00:00 2001
From: Shireesh Anjal <shireesh@gluster.com>
Date: Wed, 31 Aug 2011 15:13:22 +0530
Subject: Latest help files

---
 .../html/tasks/remove_brick.html                                     | 5 +----
 1 file changed, 1 insertion(+), 4 deletions(-)

(limited to 'src/com.gluster.storage.management.console.help/html/tasks/remove_brick.html')

diff --git a/src/com.gluster.storage.management.console.help/html/tasks/remove_brick.html b/src/com.gluster.storage.management.console.help/html/tasks/remove_brick.html
index a05c83ec..fbbfb89e 100644
--- a/src/com.gluster.storage.management.console.help/html/tasks/remove_brick.html
+++ b/src/com.gluster.storage.management.console.help/html/tasks/remove_brick.html
@@ -13,10 +13,7 @@ type="text/css" media="screen" />
 You can shrink volumes, as needed, while the cluster is online and
 available. For example, you might need to remove a brick that has become
 inaccessible in a distributed volume due to hardware or network failure.
-<p><b>Note:</b> Data residing on the brick that you are removing
-will no longer be accessible; only the configuration information is
-removed - you can continue to access the data directly from the brick,
-as necessary.
+
 <p>To remove bricks from an existing volume, perform the following
 steps.</p>
 <ol>
-- 
cgit