Index: 07_devmap.html
===================================================================
--- 07_devmap.html	(revision 263)
+++ 07_devmap.html	(revision 264)
@@ -43,8 +43,15 @@
 
 <p>{des7:0}
 The input is a array is an unordered list of (terminal name + slot name)
--&gt (attribute_name + value) pairs.
+-&gt; (attribute_name + value) pairs, each specified in the following syntax:
+<pre>
+slot/termname -&gt; attribkey=value
+<pre>
 
+<p>{des7:0} E.g. "A/out -&gt; pcb/pin=1" means "terminal with 
+<i>name=out</i> in symbol tagged as <i>slot=A</i> shall get attribute
+<i>pcb/pin</i> set to <i>1</i>".
+
 <p>{des7:0}
 The pin mapper iterates over all
 ports of the abstract component and traces back the concrete symbol
@@ -54,23 +61,24 @@
 The map is then searched for the terminal+slot pair; if it is found, the
 terminal name is <a href="02_data#des2:77"> translated </a> (so that the
 right amount of ports are created in the abstract component for the
-slots) and attribute_name+value is set on the resulting port.
+slots) and attribute_name=value is set on the resulting port.
 
 <p>{des7:0}
-If a terminal+slot pair is not found in the map, an error message is
+If a slot/terminal pair is not found in the map, an error message is
 emitted. This happens when the schematics symbol uses a terminal that
 has no physical pin with the given device.
 
 <p>{des7:0}
-If a terminal+slot pair of the map is not used in the mapping, no error
+If a slot/terminal pair of the map is not used in the mapping, no error
 is generated. A typical example when this happens is when a logic circuit
 has 4 identical slots but the schematics uses only 3. If this is considered
 an error, a DRC plugin shall check for it.
 
+
 <p>{des7:0}
 TODO: table of symbol attributes: pinmap
-TODO: invent the actual format
 
+
 <h2> 7.2. Device mapping </h2>
 
 <p>{des7:0}