--- a/doc/config-manual/generating_maps.tex	Wed May 12 11:35:25 2010 +0000
+++ b/doc/config-manual/generating_maps.tex	Wed May 12 11:56:36 2010 +0000
@@ -37,31 +37,29 @@
     requests the data from the database-backend and processes the data
     (see above).    
     
-    \item By requesting a map in the GNV-WebClient, the artifact-server writes a ESRI
-    shapefile with (clipped) geometries, attribute data, projection
-    information and a special file storing meta information (\texttt{
-    meta.xml}) for this artifact in the a corresponding directory in the
+    \item By requesting a map in the GNV-WebClient, the artifact-server writes
+    a ESRI shapefile with (clipped) geometries, attribute data, projection
+    information and a special file storing meta information (\texttt{meta.xml})
+    for this artifact in the a corresponding directory in the
     \texttt{shapefile-directory}.
     
-    \item After that the so called \texttt{map-generator}
-    is triggered. The map-generator searches the \texttt{shape-directory}
-    and its subfolders with all existing \texttt{meta.xml} files and
-    generates a central configuration file for the mapserver at \texttt{
-    map-generator/mapfile@path}. Each shapefile will be published as a WMS
-    layer. \\
-    The generated mapfile is constructed out of a base template from
-    \texttt{
-    map-generator/templates/maptemplate} and a parameter-/layer-specific
-    part generated from \texttt{map-generator/templates/path}. The
-    selection of the correct file-based templates is extracted out of
-    the \texttt{meta.xml}-file.
+    \item After that the so called \texttt{map-generator} is triggered. The
+    map-generator searches the \texttt{shape-directory} and its subfolders with
+    all existing \texttt{meta.xml} files and generates a central configuration
+    file for the mapserver at \texttt{ map-generator/mapfile@path}. Each
+    shapefile will be published as a WMS layer. \\
+    The generated mapfile is constructed out of a base template from \texttt{
+    map-generator/templates/maptemplate} and a parameter-/layer-specific part
+    generated from \texttt{map-generator/templates/path}. The selection of the
+    correct file-based templates is extracted out of the
+    \texttt{meta.xml}-file.
     
-    \item The matching between the generated geograpic data and the corresponding
-    style files is been done by the artifact-server, constructing
+    \item The matching between the generated geograpic data and the
+    corresponding style files is been done by the artifact-server, constructing
     filenames of maptemplates out of parameter-information. For
     horizontal-cross-sections the schema looks like this \texttt{
-    horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated
-    FIS like e.g. NAUTHIS and CONTIS like this \texttt{
+    horizontalcrosssection\_\$NAME-OF-PARAMETER}; for layer-orientated FIS like
+    e.g. NAUTHIS and CONTIS like this \texttt{
     layer\_\$ID\_MAPSERVICE\_\$ID\_LAYER}  e.g.
     \texttt{layer\_BSH\_IMS\_CONTIS\_Resources\_2}.
     %% FIXME@TE: Marine Feature? Name of WMS?
@@ -102,13 +100,14 @@
 \end{itemize}
 
 \paragraph*{velocity}
-{\em Function}: Templating language used in the maptemplates at \texttt{
-map-generator/templates/path} for accessing the parameters from
+{\em Function}: Templating language used in the maptemplates at 
+\texttt{map-generator/templates/path} for accessing the parameters from
 dynamically generated \texttt{meta.xml}-configuration of artifacts.
 
 \begin{itemize}
-    \item {\tt logfile}: Setting the path to write log files.
-    Preconfigured to \texttt{/var/log/artifacts/velocity.log}. {\bf Just
+    \item {\tt logfile}: Setting the path to write log files. \\
+    Preconfigured to \texttt{/var/log/artifacts/velocity.log}. 
+    {\bf Just
     absolute pathes are allowed here!}
 \end{itemize}