diff --git a/docs/USB Flashing.md b/docs/USB Flashing.md
index fab52df63c..0ba82aa95b 100644
--- a/docs/USB Flashing.md	
+++ b/docs/USB Flashing.md	
@@ -29,7 +29,7 @@ sudo systemctl stop ModemManager.service
 
 If your system lacks the systemctl command, use any equivalent command that works on your system to disable services. You can likely add your device ID to a blacklist configuration file to stop ModemManager from touching the device, if you need it for cellural networking, but that is beyond the scope of cleanflight documentation.
 
-If you see the ttyUSB device appear and immediately disappear from the list in Cleanflight Configurator when you plug in your flight controller via USB, chances are that NetworkManager thinks your board is a GSM modem and hands it off to the ModemManager daemon as the flight controllers are not known to the blacklisted.
+If you see the ttyUSB device appear and immediately disappear from the list in Betaflight Configurator when you plug in your flight controller via USB, chances are that NetworkManager thinks your board is a GSM modem and hands it off to the ModemManager daemon as the flight controllers are not known to the blacklisted.
 
 
 ## Platform Specific: Windows