Index: trunk/doc/user/07_io/export_spice/auto_bride.html
===================================================================
--- trunk/doc/user/07_io/export_spice/auto_bride.html	(revision 7804)
+++ trunk/doc/user/07_io/export_spice/auto_bride.html	(revision 7805)
@@ -20,12 +20,19 @@
 and a new network segment is introduced to connect the other port of the
 converter and the original port.
 <p>
-What <i>instance</i> really means depends on the spice dialect. For ngspice
-it is enough to create one component per converter type and it acts as a
-multi-slot or multi-port converter array with vector input and vector output.
-For xyce a discrete converter needs to be placed. An user implemented converter
-may be either way. By default the code assumes ngspice and array/vector
-converters, but TODO.
+What <i>instance</i> really means depends on the config node
+plugins/target_spice/bridges, which should be one of the following
+string values:
+<ul>
+	<li> <b>vector</b>: for ngspice it is enough to create one component per
+	     converter type and it acts as a multi-slot or multi-port converter
+	     array with vector input and vector output.
+	<li> <b>scalar</b>: for xyce a discrete converter needs to be placed per
+	     port.
+	<li> <b>none</b>: ignore the spice/bridge attributes and do not create
+	     any converter or bridge; this assumes the models are all analog or
+	     the spice implementation handles conversion automatically.
+</ul>
 <p>
 The converter is assumed to have only 2 ports, one input and one output.
 Order of the connections, or in other words direction of the converter