Fix tooltip (#3175)

locales/en/messages.json

@@ -3135,7 +3135,7 @@
         "message": "Select or auto-detect your board to see available online firmware releases - Select the correct firmware appropriate for your board."
     },
     "firmwareFlasherOnlineSelectBoardHint": {
-        "message": "Starting with Betaflight 4.1, Betaflight is introducing support for <strong>Unified Targets</strong>. The concept of Unified Targets means that the same firmware .hex file can be used for all boards using the same MCU (F4, F7). To make the different boards work with the same firmware, a specific configuration file is deployed alongside the firmware when a Unified Target is flashed.<br>This version of Betaflight configurator supports flashing of Unified Targets with the respective board specific configurations in one step. The different firmware types that are available for each board are shown in the drop-down as follows:<br /><br /><strong>&lt;board name&gt;</strong> or<br><strong>&lt;board name&gt; (Legacy)</strong>:<br>non-unified target, or pre-4.1 versions of the firmware for Unified Targets.<br /><br /><strong>&lt;board name&gt; (&lt;manufacturer id&gt;)</strong>:<br>(4 character manufacturer id)<br>Unified Target.<br /><br /><strong>Please use Unified Targets where available.</strong> If you encounter problems using a Unified Target, please open an <a href=\"https://github.com/betaflight/betaflight/issues\" target=\"_blank\" rel=\"noopener noreferrer\">issue</a> and then use the non-unified target until the issue has been resolved."
+        "message": "Betaflight configurator supports flashing of Unified Targets with the respective board specific configurations in one step.<br><br>The concept of Unified Targets means that the same firmware .hex file can be used for all boards using the same MCU.<br><br>Betaflight 4.4 introduces <strong>Cloud Build</strong><br><br>With <strong>Cloud Build</strong> we need to define hardware options present on your build.<br><br>To make the different boards work with the same firmware, a specific configuration file is deployed alongside the firmware when a Unified Target is flashed.<br><br>With Local build you can load a unified target configuration file or chose a board before loading a firmware .hex file.<br><br>If you encounter problems using the firmware, please consider joining Discord or open an <a href=\"https://github.com/betaflight/betaflight/issues\" target=\"_blank\" rel=\"noopener noreferrer\">issue</a>."
     },
     "firmwareFlasherOnlineSelectFirmwareVersionDescription": {
         "message": "Select firmware version for your board."
@@ -6856,6 +6856,6 @@
         "message": "Classic Mode"
     },
     "classicBuildModeDescription": {
-        "message": "This mode ignores all the parameters here (except for the commit when in expert mode). This essentially achieves the same as the classic nightlies, and is provided for convenience."
+        "message": "This mode ignores all the parameters here. This essentially achieves the same as the classic nightlies, and is provided for convenience."
     }
 }

src/js/utils/common.js

@@ -98,7 +98,6 @@ $.fn.sortSelect = function(text = "") {
     const op = this.children("option");
 
     op.sort((a, b) => {
-        console.log(a.value, a.text);
         if (a.text === text) {
             return -1;
         }

src/tabs/firmware_flasher.html

@@ -1,5 +1,9 @@
 <div class="tab-firmware_flasher toolbar_fixed_bottom">
     <div class="content_wrapper">
+        <div class="tab_title" i18n="tabFirmwareFlasher"></div>
+        <div class="cf_doc_version_bt">
+            <a id="button-documentation" href="https://github.com/betaflight/betaflight/wiki/Flashing-firmware" target="_blank" rel="noopener noreferrer"></a>
+        </div>
         <div class="options gui_box" style="float: left; width: 460px; ">
             <div class="spacer" style="margin-bottom: 10px;">
                 <div class="margin-bottom">