Remove old references to ESP IDF from the docu

src/netif.rs

@@ -3,7 +3,7 @@ use core::net::{Ipv4Addr, Ipv6Addr};
 
 use rs_matter::error::Error;
 
-/// Async trait for accessing the `EspNetif` network interface (netif) of a driver.
+/// Async trait for accessing the network interface (netif) of a driver.
 ///
 /// Allows sharing the network interface between multiple tasks, where one task
 /// may be waiting for the network interface to be ready, while the other might

src/wifi/comm.rs

@@ -315,7 +315,9 @@ where
     ) -> Result<(), Error> {
         // TODO: Check failsafe status
 
-        // Non-concurrent commissioning scenario (i.e. only BLE is active, and the ESP IDF co-exist mode is not enabled)
+        // Non-concurrent commissioning scenario
+        // (i.e. only BLE is active, and the device BLE+Wifi co-exist
+        // driver is not running, or does not even exist)
 
         let ssid = core::str::from_utf8(req.network_id.0).unwrap();
 

src/wifible.rs

@@ -40,9 +40,8 @@ pub const MAX_WIFI_NETWORKS: usize = 2;
 ///
 /// The supported commissioning is of the non-concurrent type (as per the Matter Core spec),
 /// where the device - at any point in time - either runs Bluetooth or Wifi, but not both.
-/// This is done to save memory and to avoid the usage of the ESP IDF Co-exist driver.
-///
-/// The BLE implementation used is the ESP IDF Bluedroid stack (not NimBLE).
+/// This is done to save memory and to avoid the usage of BLE+Wifi co-exist drivers on
+/// devices which share a single wireless radio for both BLE and Wifi.
 pub struct WifiBle<M: RawMutex, E = ()> {
     btp_context: BtpContext<M>,
     wifi_context: WifiContext<MAX_WIFI_NETWORKS, M>,