DG facelift

diff --git a/org.glite.lb.doc/src/LBDG-Introduction.tex b/org.glite.lb.doc/src/LBDG-Introduction.tex
index 80248d0..ea272b6 100644 (file)
--- a/org.glite.lb.doc/src/LBDG-Introduction.tex
+++ b/org.glite.lb.doc/src/LBDG-Introduction.tex
@@ -79,7 +79,7 @@ These bring in other gLite dependencies:
 \begin{itemize}
 \item \verb'glite-lb-client-interface' (\LBver{1.x} only)
 \item \verb'glite-security-gsoap-plugin' (\LBver{1.x} only)
-\item \verb'glite-security-gss' (\LBver{2.x} only)
+\item \verb'glite-security-gss' (only \LBver{2.0} and higher)
 \end{itemize}
 and external dependencies:
 \begin{itemize}

diff --git a/org.glite.lb.doc/src/notification_api.tex b/org.glite.lb.doc/src/notification_api.tex
index 6a1717e..0543e62 100644 (file)
--- a/org.glite.lb.doc/src/notification_api.tex
+++ b/org.glite.lb.doc/src/notification_api.tex
@@ -79,12 +79,12 @@ funcions.
   notification the same encoding of conditions as for the \LB
   query/response API is used (sec.~\ref{s:queryrec}). 
 
-  \marginpar{\LB 2.0 only}%
+  \marginpar{\LB 2 and higher}%
   In version 1.x there is a restriction that at least one particular
-  JobId must be defined. In \LB 2.0 you can make a registration based
+  JobId must be defined. Since \LB 2.0 you can make a registration based
   on other attributes without referencing a particular JobId (you can
   select owner, VO, network server).  It is also a feature of \LB 2.0
-  only, that you can use attributes derived from JDL (VO).
+  and higer versions, that you can use attributes derived from JDL (VO).
 
  \item \emph {Refresh of a notification}. When a new notification is
   created using \verb'edg_wll_NotifNew' call, the notification
@@ -150,7 +150,7 @@ the whole set of registrations. Will receive a first notification from
 any of registations.
 
 \subsubsection{Operator CHANGED}
-\marginpar{\LB 2.0 only}%
+\marginpar{\LB 2 and higher}%
 The notification events are generated by LB server based on primary
 events send by grid components. Each of the primary events (called LB
 events) generates one notification event to be possibly sent to the
@@ -161,10 +161,10 @@ want to receive all job status changes you need to setup a condition
 on job status attribute using special unary operator
 \verb'CHANGED'. Otherwise (without any condition) you will receive
 more events that you want -- even events where job state was not
-changed. Operator \verb'CHANGED' is available only in \LB 2.0.
+changed. Operator \verb'CHANGED' is available since \LB 2.0.
 
 \subsubsection{Returned attributes}
-\marginpar{\LB 2.0 only}%
+\marginpar{\LB 2 and higher}%
 Each LB notification contains a structure describing job state
 including job's JDL. For optimization purposes the API user can set
 the JDL flag in \verb'edg_wll_NotifNew' flags parameter to prevent