documentation: Windows supports multiple VTEP/NICs now.

Multiple VTEP and multiple physical NICs are supported on Hyper-V now.
Update the documentation

Signed-off-by: Alin Gabriel Serdean <aserdean@cloudbasesolutions.com>
Signed-off-by: Ben Pfaff <blp@ovn.org>
Acked-by: Sairam Venugopal <vsairam@vmware.com>

Documentation/faq/releases.rst

@@ -118,18 +118,14 @@ Q: Are all features available with all datapaths?
     sFlow                 YES            YES            YES       NO
     IPFIX                 3.10           YES            YES       NO
     Set action            YES            YES            YES       PARTIAL
-    NIC Bonding           YES            YES            YES       NO
-    Multiple VTEPs        YES            YES            YES       NO
+    NIC Bonding           YES            YES            YES       YES
+    Multiple VTEPs        YES            YES            YES       YES
     ===================== ============== ============== ========= =======
 
     Do note, however:
 
     * Only a limited set of flow fields is modifiable via the set action by the
       Hyper-V datapath.
-    * The Hyper-V datapath only supports one physical NIC per datapath. This is
-      why bonding is not supported.
-    * The Hyper-V datapath can have at most one IP address configured as a
-      tunnel endpoint.
 
     The following table lists features that do not *directly* impact an Open
     vSwitch user, e.g. because their absence can be hidden by the ofproto layer