LUDOC-440 lsom: Update examples description

This patch updates the introductory sentence to LSoM to state that
it can be used in various vender offerings, rather than calling
out specific vendor tools.

Signed-off-by: Joseph Gmitter <jgmitter@whamcloud.com>
Change-Id: I678c4f15ebe6781785cd8e8251cc9858358ef674
Reviewed-on: https://review.whamcloud.com/35142
Tested-by: Jenkins
Reviewed-by: Peter Jones <pjones@whamcloud.com>

diff --git a/LazySizeOnMDT.xml b/LazySizeOnMDT.xml
index 8862f14..9032341 100644 (file)
--- a/LazySizeOnMDT.xml
+++ b/LazySizeOnMDT.xml
@@ -24,9 +24,9 @@
     the MDTs. We expect this feature to be initially used by Lustre policy
     engines that scan the backend MDT storage, make decisions based on broad
     size categories, and do not depend on a totally accurate file size.
-    Examples include Lester, Robinhood, Zester, and DDN’s Lustre Integrated
-    Policy Engine (LiPE). Future improvements will allow the LSoM data to be
-    accessed by tools such as <literal>lfs find</literal>.</para>
+    Examples include Lester, Robinhood, Zester, and various vendor offerings.
+    Future improvements will allow the LSoM data to be accessed by tools such
+    as <literal>lfs find</literal>.</para>
   </section>
   <section xml:id="dbdoclet.enablelsom">
     <title><indexterm><primary>lsom</primary>