--- a/doku/source/functionality.txt	Fri Jul 29 07:41:29 2011 +0200
+++ b/doku/source/functionality.txt	Fri Jul 29 17:33:19 2011 +0200
@@ -77,8 +77,9 @@
 
 MXD2map currently supportes the following features:
 
- * Datasources
-   * ArcSDE database connections (requires MapServer built against ArcSDE, Client-dlls needed)
+ * Datasources:
+
+   * ArcSDE vector database connections (requires MapServer built against ArcSDE, Client-dlls needed)
    * ESRI-Shapefiles
 
  * Symbols:
@@ -97,7 +98,9 @@
    * Featurelayer (vectors) as POINT, LINESTRING and POLYGON
    * Classifications with unique values
    * Classifications with class breaks
-   * Grouplayers with one grouplevel (as MapServer does not support more than one nested level)
+   * Group-members are concatinated to group.layername. This ensures having discrete layernames
+   * ArcGIS-layergroups are represented as WMS Named layers, which are WMS-layers without a title (so not requestable throuhg GetMap)
+   * all definition-queries for filtering the data on Layer- and classification-level
 
  * Further map attributes:
 
@@ -108,10 +111,12 @@
    * Filter and expressions
    * ArcSDE Jointables
    * Mapfile-Templating for OGC-related stuff
+   * Simple Labeling-syntax (a subset of ArcGISs VBScript-labels)
 
  * Other features
 
-   * Umlauts are translated into its equivalents within LAYERnames,
-   CLASSnames and also mapfile-names. Though it is good standard not to
+   * Umlauts are translated into its equivalents within LAYER-names,
+   CLASS-names and also mapfile-names. Though it is good standard not to
    use them since they mostly cause problems when using them within
    OWS-related services.
+   *