diff --git a/documentation/qsrvpage.dox b/documentation/qsrvpage.dox
index 41ea4c0..5850368 100644
--- a/documentation/qsrvpage.dox
+++ b/documentation/qsrvpage.dox
@@ -87,7 +87,6 @@ record(...) {
     info(Q:group, {
         "<group_name>":{
             +id:"some/NT:1.0",  # top level ID
-            +meta:"FLD",        # map top level alarm/timeStamp
             +atomic:true,       # whether monitors default to multi-locking atomicity
             "<field.name>":{
                 +type:"scalar", # controls how map VAL mapped onto <field.name>
@@ -95,7 +94,8 @@ record(...) {
                 +id:"some/NT:1.0",
                 +trigger:"*",   # "*" or comma seperated list of <field.name>s
                 +putorder:0,    # set for fields where put is allowed, processing done in increasing order
-            }
+            },
+            "": {+type:"meta", +channel:"VAL"} # special case adds meta-data fields at top level
         }
     })
 }
@@ -118,7 +118,7 @@ The "any" mapping places a variant union into which the "value" is placed.
 
 The "meta" mapping ignores the "value" and places only the alarm and time
 meta-data as sub-fields.
-The special group level tag 'meta:""' allows these meta-data fields to be
+Placing an entry in a blank field name '"": {+type:"meta"}' allows these meta-data fields to be
 placed in the top-level structure.
 
 The "proc" mapping uses neither "value" nor meta-data.