diff -up firewalld-0.3.9/doc/xml/firewall-cmd.xml.RHBZ#1112742 firewalld-0.3.9/doc/xml/firewall-cmd.xml
--- firewalld-0.3.9/doc/xml/firewall-cmd.xml.RHBZ#1112742	2014-09-30 01:31:08.211565878 +0200
+++ firewalld-0.3.9/doc/xml/firewall-cmd.xml	2014-09-30 01:41:41.986770639 +0200
@@ -647,6 +647,10 @@
 	    <para>
 	      Bind interface <replaceable>interface</replaceable> to zone <replaceable>zone</replaceable>. If zone is omitted, default zone will be used.
 	    </para>
+	    <para>
+	      As a end user you don't need this in most cases, because NetworkManager adds interfaces into zones automatically.
+	      For permanent association of interface with a zone, see 'How to set or change a zone for a connection?' in <citerefentry><refentrytitle>firewalld.zones</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
+	    </para>
 	  </listitem>
 	</varlistentry>
 
diff -up firewalld-0.3.9/doc/xml/firewalld.zone.xml.RHBZ#1112742 firewalld-0.3.9/doc/xml/firewalld.zone.xml
--- firewalld-0.3.9/doc/xml/firewalld.zone.xml.RHBZ#1112742	2013-12-05 15:52:01.000000000 +0100
+++ firewalld-0.3.9/doc/xml/firewalld.zone.xml	2014-09-30 01:41:41.986770639 +0200
@@ -152,7 +152,11 @@
     <refsect2 id="interface">
       <title>interface</title>
       <para>
-	Is an optional empty-element tag and can be used several times. It can be used to bind an interface to a zone. An interface entry has exactly one attribute:
+	Is an optional empty-element tag and can be used several times. It can be used to bind an interface to a zone.
+	You don't need this for NetworkManager-managed interfaces, because NetworkManager binds interfaces to zones automatically.
+	See also 'How to set or change a zone for a connection?' in <citerefentry><refentrytitle>firewalld.zones</refentrytitle><manvolnum>5</manvolnum></citerefentry>.
+	You can use it as a fallback mechanism for interfaces that can't be managed via NetworkManager.
+	An interface entry has exactly one attribute:
       </para>
       <variablelist>
 	<varlistentry>