Index: trunk/doc/pslib/psLibSDRS.tex
===================================================================
--- trunk/doc/pslib/psLibSDRS.tex	(revision 3653)
+++ trunk/doc/pslib/psLibSDRS.tex	(revision 3654)
@@ -1,3 +1,3 @@
-%%% $Id: psLibSDRS.tex,v 1.195 2005-04-04 23:19:51 jhoblitt Exp $
+%%% $Id: psLibSDRS.tex,v 1.196 2005-04-04 23:23:04 jhoblitt Exp $
 \documentclass[panstarrs,spec]{panstarrs}
 
@@ -3938,5 +3938,5 @@
 On error, the function shall return \code{NULL}.
 
-\subsubsection{Comments}
+\paragraph{Comments}
 
 The configuration file shall consist of plain text with
@@ -3951,6 +3951,6 @@
 which should not form part of the key.
 
-\subsubsection{Types}
-\paragraph{Scalar \& Vector}
+\paragraph{Types}
+\subparagraph{Scalar \& Vector}
 
 Next, to assist the casting of the value, shall be a string identifying the
@@ -3994,5 +3994,5 @@
 and/or +/-infinity values for selected types.}
 
-\paragraph{MULTI}
+\subparagraph{MULTI}
 
 An additional hurdle is the specification of keys that may be non-unique (such
@@ -4047,6 +4047,6 @@
 files.
 
-\subsubsection{Complex Types}
-\paragraph{TYPE}
+\paragraph{Complex Types}
+\subparagraph{TYPE}
 
 We support a modest tree structure by defining a reserved keyword \code{TYPE}.
@@ -4075,5 +4075,5 @@
 Figure~\ref{fig:metadata}.
 
-\paragraph{METADATA}
+\subparagraph{METADATA}
 
 Another way to form a tree-like structure is to directly define a
@@ -4093,5 +4093,5 @@
 \end{verbatim}
 
-\subsubsection{Scoping Rules}
+\paragraph{Scoping Rules}
 
 A simple set of ``Scoping Rules'' are required to properly parse a