API Doc Direct-BT: Move HCI prioritization segment to main namespace section.

2 files changed, 11 insertions, 8 deletions

diff --git a/api/direct_bt/ATTPDUTypes.hpp b/api/direct_bt/ATTPDUTypes.hpp
index a2fbb033..a4bf71c7 100644
--- a/api/direct_bt/ATTPDUTypes.hpp
+++ b/api/direct_bt/ATTPDUTypes.hpp
@@ -74,6 +74,17 @@
  *
  * - - - - - - - - - - - - - - -
  *
+ * BT Core Spec v5.2:  Vol 3, Part A L2CAP Spec: 7.9 PRIORITIZING DATA OVER HCI
+ *
+ * > In order for guaranteed channels to meet their guarantees,
+ * > L2CAP should prioritize traffic over the HCI transport in devices that support HCI.
+ * > Packets for Guaranteed channels should receive higher priority than packets for Best Effort channels.
+ *
+ * *As we have experience slower GATT communication w/o HCI connection,
+ * Direct-BT enforces the HCI connection.*
+ *
+ * - - - - - - - - - - - - - - -
+ *
  * - BT Core Spec v5.2: Vol 3, Part F Attribute Protocol (ATT)
  */
 namespace direct_bt {
diff --git a/api/direct_bt/BTTypes.hpp b/api/direct_bt/BTTypes.hpp
index ac3e2192..7a21b9ef 100644
--- a/api/direct_bt/BTTypes.hpp
+++ b/api/direct_bt/BTTypes.hpp
@@ -111,14 +111,6 @@ namespace direct_bt {
     };
 
     /**
-     * BT Core Spec v5.2:  Vol 3, Part A L2CAP Spec: 7.9 PRIORITIZING DATA OVER HCI
-     *
-     * In order for guaranteed channels to meet their guarantees,
-     * L2CAP should prioritize traffic over the HCI transport in devices that support HCI.
-     * Packets for Guaranteed channels should receive higher priority than packets for Best Effort channels.
-     */
-
-    /**
      * ​​Assigned numbers are used in Generic Access Profile (GAP) for inquiry response,
      * EIR data type values, manufacturer-specific data, advertising data,
      * low energy UUIDs and appearance characteristics, and class of device.