Index: /trunk/doc/manual/en_US/user_AdvancedTopics.xml
===================================================================
--- /trunk/doc/manual/en_US/user_AdvancedTopics.xml	(revision 55142)
+++ /trunk/doc/manual/en_US/user_AdvancedTopics.xml	(revision 55143)
@@ -1791,16 +1791,16 @@
     "vboxvnic_template" (case-sensitive).</para>
  
-    <para>On Solaris 11 hosts (i.e. when the default Crossbow based bridged
-    networking is used), using a VNIC template is the only means of specifying
-    a VLAN ID to use while bridging over a link.</para>
-
-    <para>Here is an example of how to use a VNIC template to configure a VLAN
-    for VMs. Create a VirtualBox VNIC template, by executing as root:</para>
+    <para>On Solaris 11 hosts<footnote><para>When the default Crossbow based
+    bridged networking driver is used</para></footnote>, a VNIC template may
+    be used to specify the VLAN ID to use while bridging over a network link.</para>
+
+    <para>Here is an example of how to use a VNIC template to configure a VM
+    over a VLAN. Create a VirtualBox VNIC template, by executing as root:</para>
 
     <screen>dladm create-vnic -t -l nge0 -v 23 vboxvnic_template0</screen>
 
-    <para>This will create a temporary VNIC over interface "nge0" with the
-    VLAN ID 23. To create VNIC templates that are persistent across host
-    reboots, skip the <computeroutput>-t</computeroutput> parameter in the
+    <para>This will create a temporary VNIC template over interface "nge0"
+    with the VLAN ID 23. To create VNIC templates that are persistent across
+    host reboots, skip the <computeroutput>-t</computeroutput> parameter in the
     above command. You may check the current state of links using:</para>
 
@@ -1815,18 +1815,17 @@
 vboxvnic_template0 nge0   1000   2:8:20:25:12:75   random              23</screen></para>
 
-    <para>In the example above, once the VNIC template is created, any VMs
-    that need to be on VLAN 23 over the physical interface "nge0" can use
-    the VNIC template.</para>
-
-    <para>VNIC templates makes managing VMs on VLANs simpler and efficient, as
-    the VLAN details are not stored as part of every VM's configuration but
-    rather inherited from the VNIC template which can be modified anytime
-    using <computeroutput>dladm</computeroutput>.</para>
-
-    <para>Apart from the VLAN ID, VNIC templates can be created with
-    additional properties such as bandwidth limits, CPU fanout etc. Refer to
-    your Solaris network documentation on how to accomplish this.
-    These additional properties, if any, are also applied to VMs which use
-    the VNIC template.</para>
+    <para>Once the VNIC template is created, any VMs that need to be on VLAN
+    23 over the interface "nge0" can be configured to bridge using this VNIC
+    template.</para>
+
+    <para>VNIC templates makes managing VMs on VLANs simpler and efficient.
+    The VLAN details are not stored as part of every VM's configuration but
+    rather inherited from the VNIC template while starting the VM. The VNIC
+    template itself can be modified anytime using <computeroutput>dladm</computeroutput>.</para>
+
+    <para>VNIC templates can be created with additional properties such as
+    bandwidth limits, CPU fanout etc. Refer to your Solaris network
+    documentation on how to accomplish this. These additional properties,
+    if any, are also applied to VMs which bridge using the VNIC template.</para>
   </sect1>