nrfconnect · nordicjm · May 21, 2025 · May 21, 2025
@@ -24,7 +24,7 @@ Configuration
 *************
 
 In the |NCS|, you can enable the GZLL library using the :kconfig:option:`CONFIG_GZLL` Kconfig option.
-Look for the menu item "Enable Gazell Link Layer".
+Look for the menu item :guilabel:`Enable Gazell Link Layer`.
 The build system will link in the appropriate library for your SoC.
 
 .. _gzll_glue_layer:

@@ -187,7 +187,7 @@ nrf_modem 2.6.1
 Sockets
 =======
 
-* Fixed a bug where the :c:func:`nrf_recv` and :c:func:`nrf_recvfrom` functions erroneously returned ``-1`` and set ``errno`` to ``NRF_EAGAIN`` instead of returning ``0`` when these three conditions were met:
+* Fixed a bug where the :c:func:`nrf_recv` and :c:func:`nrf_recvfrom` functions erroneously returned ``–1`` and set ``errno`` to ``NRF_EAGAIN`` instead of returning ``0`` when these three conditions were met:
 
   * The :c:func:`nrf_recv` and :c:func:`nrf_recvfrom` functions were called with the :c:macro:`NRF_MSG_DONTWAIT` flag or when the socket is non-blocking (``NRF_O_NONBLOCK`` is set on the socket).
   * The socket was closed by the server.
@@ -547,7 +547,7 @@ nrf_modem 1.5.0
 nrf_modem 1.4.1
 ***************
 
-* Fixed a bug in :c:func:`nrf_send` which could result in the function incorrectly returning -1 and setting the errno to ``NRF_EINPROGRESS``.
+* Fixed a bug in :c:func:`nrf_send` which could result in the function incorrectly returning –1 and setting the errno to ``NRF_EINPROGRESS``.
 
 nrf_modem 1.4.0
 ***************
@@ -570,7 +570,7 @@ nrf_modem 1.4.0
 * Fixed a potential concurrency issue in :c:func:`nrf_getaddrinfo` that would cause the output ``hints`` structure to contain no address upon successful completion.
 * Fixed a bug in :c:func:`nrf_getsockopt` that would let the function return an incorrect value in case of error when called on TLS and DTLS sockets.
 * Added a parameter to :c:func:`nrf_setdnsaddr` to specify the size of the supplied address.
-* Updated :c:func:`nrf_setdnsaddr` to return -1 and set errno on error.
+* Updated :c:func:`nrf_setdnsaddr` to return –1 and set errno on error.
 * The :c:func:`nrf_modem_os_application_irq_handler` and :c:func:`nrf_modem_os_trace_irq_handler` functions have been renamed to :c:func:`nrf_modem_application_irq_handler` and :c:func:`nrf_modem_trace_irq_handler` respectively, and their definition has been moved to :file:`nrf_modem.h`.
 * Added support for APN rate control feature of modem firmware v1.3.1.
 * The glue layer now defines a few new functions used for logging.
@@ -747,7 +747,7 @@ bsdlib 0.7.0
 
 * Major rewrite of the lower transport layer to fix an issue where packages were lost in a high bandwidth application.
 * Added support for GPS priority setting to give the GPS module priority over LTE to generate a fix.
-* Added parameter checking and only return -1 on error for the PDN set socket option function.
+* Added parameter checking and only return –1 on error for the PDN set socket option function.
 * Added support for send timeout on TCP, UDP (including secure sockets), and AT sockets.
 * Added support for MSG_TRUNC on AT, GNSS, TCP, and UDP sockets.
 * Allocating more sockets than available will now return ENOBUFS instead of ENOMEM.

@@ -350,7 +350,7 @@ NRF_SO_SEC_DTLS_CONN_SAVE
    This option require a DTLS v1.2 connection with renegotiation disabled.
    The socket option is supported from modem firmware v1.3.x, where x is greater than or equal to 5, and v2.x.x.
 
-   Once the DTLS context is saved, the socket can't be used before the DTLS context is loaded with :c:macro:`NRF_SO_SEC_DTLS_CONN_LOAD`.
+   Once the DTLS context is saved, the socket cannot be used before the DTLS context is loaded with :c:macro:`NRF_SO_SEC_DTLS_CONN_LOAD`.
 
    This option fails with ``errno`` set to ``NRF_EAGAIN`` if an error happened during serialization of the SSL context.
    This can occur, for instance, when the modem cannot allocate enough memory or if the socket is busy sending or receiving data.

@@ -73,7 +73,7 @@ Bug fixes
 * Fixed an issue where disconnect could happen if multiple peripheral links were active and encrypted. (DRGN-24784)
 * Fixed an issue where the controller would fail to synchronize with a BIS Broadcaster. (DRGN-24670)
   This would occur when the Broadcaster has set ``Num_Bis=1``, ``NSE > 1``, and ``Sub_Interval == BIS_Spacing``.
-  Previously, the controller would raise the LE BIG Sync Established event with status set to "Unsupported Feature or Parameter value (0x11)".
+  Previously, the controller would raise the LE BIG Sync Established event with status set to ``Unsupported Feature or Parameter value (0x11)``.
 * Fixed an issue where ACL connections could not be created if a Periodic Advertiser was configured when the :kconfig:option:`CONFIG_BT_CTLR_SDC_PAWR_ADV` Kconfig option was selected. (DRGN-24148)
 * Fixed a rare issue where the scanner would assert when scanning and initiating at the same time. (DRGN-24198)
 
@@ -83,7 +83,7 @@ Bug fixes
     * :kconfig:option:`BT_CTLR_SDC_SCAN_BUFFER_COUNT` is set to the non-default value 2.
     * The initiator has received a connectable ``ADV_EXT_IND``.
     * The initiator is canceled.
-* Fixed an issue where the central device would disconnect 40 s after responding to a ``LL_SUBRATE_REQ`` with reason "LMP Response Timeout (0x22)".
+* Fixed an issue where the central device would disconnect 40 s after responding to a ``LL_SUBRATE_REQ`` with reason ``LMP Response Timeout (0x22)``.
   This would only occur on nRF52 Series and nRF53 Series devices. (DRGN-24310)
 * Fixed a very rare issue where the scanner would assert, hang or stop producing reports when scanning and initiating at the same time. (DRGN-24370)
 
@@ -220,7 +220,7 @@ Changes
 * Generating the Number of Completed Packets event is now prioritized above all other events.
   The event is generated irrespective of the state of the Controller to Host data flow control. (DRGN-23284)
 * When a link disconnects, the controller will now raise one or more Number Of Completed Packets events for data packets not ACKed by the peer device. (DRGN-23302)
-* Isochronous roles may now produce HCI ISO data with SDUs containing the ``0b01`` packet status flag which indicates "possibly invalid data".
+* Isochronous roles may now produce HCI ISO data with SDUs containing the ``0b01`` packet status flag which indicates possibly invalid data.
   This is the case if the peer sends invalid data. (DRGN-23420)
 
 Bug fixes
@@ -338,7 +338,7 @@ Bug fixes
   This could happen with both the LL Create BIG and LL Create BIG Test commands (DRGN-21912).
 * Fixed an issue with the controller-initiated autonomous LE Power Control Request procedure for Coded PHY that could lead to a disconnection. (DRGN-21923)
 * Fixed an issue where the |controller| could assert if a BIS Receiver stops receiving packets from the BIS Broadcaster. (DRGN-21949)
-* Fixed an issue where the |controller| could in some rare cases generate an LE Periodic Advertising Subevent Data Request for a subevent it didn't have the memory capacity for. (DRGN-21839)
+* Fixed an issue where the |controller| could in some rare cases generate an LE Periodic Advertising Subevent Data Request for a subevent it did not have the memory capacity for. (DRGN-21839)
 * Fixed an issue where an assert could happen if the peripheral received a connection update indication.
   This happened when the central used a wide receive window for the connection update, and both sent at the end of the receive window and sent a lot of data in the connection event with the connection update instant (DRGN-22024).
 * Fixed an issue where the |controller| could assert when scanning or advertising on Coded PHY using SPI FEM on the nRF53 series. (DRGN-21962)
@@ -385,7 +385,7 @@ Changes
   :c:func:`sdc_hci_cmd_vs_set_power_control_apr_handling` have been replaced by
   :c:func:`sdc_hci_cmd_vs_set_power_control_request_params` (DRGN-17355).
 * The controller now always returns the error code ``0x0D`` if a connection attempt is made while another is still pending.
-  Previously, this wasn't the case if one connection attempt was through periodic advertising with responses while the other was through the initiator. (DRGN-20823)
+  Previously, this was not the case if one connection attempt was through periodic advertising with responses while the other was through the initiator. (DRGN-20823)
 * The scheduling priority for initiator events where the scan window is equal to the scan interval is lowered to the third scheduling priority.
   For other configurations of scan window and scan interval the priority is unchanged. (DRGN-20831)
 * The vendor-specific Set event length for ACL connections HCI command now accepts values lower than 1250 us. (DRGN-20796)
@@ -723,8 +723,8 @@ Bug fixes
 
 * Fixed an issue where Advertiser Address Type in the LE Periodic Advertising Sync Established event was never set to 0x02 or 0x03, even if the advertiser's address was resolved (DRGN-17110).
 * Fixed an issue where Advertiser Address Type was not set in the LE Periodic Advertising Sync Established event when using the Periodic Advertiser List (DRGN-17110).
-* Fixed an issue where setting advertiser radio output power using the vendor-specific HCI command Zephyr Write TX Power Level returned "Unknown Advertiser Identifier (0x42)".
-* Fixed an issue where reading advertiser radio output power using the vendor-specific HCI command Zephyr Read TX Power Level returned "Unknown Advertiser Identifier (0x42)".
+* Fixed an issue where setting advertiser radio output power using the vendor-specific HCI command Zephyr Write TX Power Level returned ``Unknown Advertiser Identifier (0x42)``.
+* Fixed an issue where reading advertiser radio output power using the vendor-specific HCI command Zephyr Read TX Power Level returned ``Unknown Advertiser Identifier (0x42)``.
 * Fixed an issue where an assert could occur if :c:func:`sdc_disable` was called while a Bluetooth role was running (DRGN-16515).
 * Fixed an issue where the advertiser would incorrectly set Offset Adjust in the SyncInfo when the offset to the ``AUX_SYNC_IND`` is large (DRGN-16887).
 * Fixed an issue where issuing a legitimate connection update could result in an ``BT_HCI_ERR_INVALID_PARAM`` error (DRGN-17324).
@@ -872,7 +872,7 @@ Bug fixes
 * Fixed an issue where, in rare cases, an assert could occur when receiving a packet as a slave.
   This could only occur after performing a data length procedure on Coded PHY (DRGN-15251).
 * Fixed an issue where "HCI Read RSSI" would always return a Command Disallowed (0x0C) error code (DRGN-15310).
-* Fixed an issue where setting radio output power using the vendor-specific HCI command Zephyr Write TX Power Level returned "Unsupported Feature or Parameter value (0x11)".
+* Fixed an issue where setting radio output power using the vendor-specific HCI command Zephyr Write TX Power Level returned ``Unsupported Feature or Parameter value (0x11)``.
   Now the controller will select an output power level that is lower or equal to the one requested.
   The command returns success and the selected power level (DRGN-15369).
 * Fixed an issue where an assert could occur when running an extended advertiser with maximum data length and minimum interval on Coded PHY.
@@ -917,7 +917,7 @@ Bug fixes
 * Fixed an issue where a directed advertiser used a resolvable address as the ``TargetA`` when the local device address was set to public or random device address (DRGN-13921).
 * Fixed an issue where "HCI LE Set Extended Advertising Parameters" should have returned "Packet Too Long (0x45)" when the advertising set was already configured with data that was longer than it could fit within the advertising interval.
   Previously, the advertising data was cleared every time the advertising set was configured (DRGN-14008).
-* Fixed an issue where the link would disconnect with reason "LMP Response Timeout (0x22)".
+* Fixed an issue where the link would disconnect with reason ``LMP Response Timeout (0x22)``.
   This would occur if the "HCI LE Long Term Key Request event" was disabled and the slave received an encryption request (DRGN-15226).
 * Fixed an issue where the LL control procedures LE start encryption and LE connection parameter update could not be initiated at the same time (DRGN-11963).
 * Fixed an issue where the generation of QoS Connection event was not disabled after an HCI reset (DRGN-15291).
@@ -1022,7 +1022,7 @@ Changes
 * The VersNr field in the LL_VERSION_IND packet now contains the value 0x0B to indicate Bluetooth Core Specification v5.2 compliance.
 * The previously implemented Vendor Specific HCI command opcodes are now offset with 0x100.
 * The previously implemented Vendor Specific HCI event codes are now offset with 0x80.
-* When the controller receives an unknown command, it will raise "Command Status event" instead of "Command Complete event".
+* When the controller receives an unknown command, it will raise ``Command Status event`` instead of ``Command Complete event``.
 * When in slave latency, the controller now picks up data from the host for transmission earlier than it used to.
 * In the LE Extended Advertising Report, the Direct Address Type values 0x02, 0x03, and 0xFE will only be used when the Scanning Filter Policy is equal to 0x02 or 0x03 and TargetA is a resolvable private address.
   If the address is resolved, then the Direct Address Type will contain the same value as the Own Address Type parameter of the command LE Set Extended Scan Parameters.

@@ -657,7 +657,7 @@ Scanner, observer, and initiator events can therefore cause connection packets t
 To reduce the chance of colliding connections, configure all connection intervals to have a common factor.
 This common factor should be greater than or equal to :math:`\mathsf{\sum{t_{event-Cx}}}`.
 For example, for eight connections with an event length of 2.5 ms, the lowest recommended connection interval is 20 ms.
-This means all connections would then have a connection interval of 20 ms or a multiple of 20 ms, such as 40 ms, 60 ms, and so on.
+This means all connections would then have a connection interval of 20 ms or a multiple of 20 ms, such as 40 ms or 60 ms.
 
 To summarize, when only Central roles are running, all central role intervals (such as connection interval and Scanner interval) should have a common factor.
 This common factor should be greater than or equal to :math:`\mathsf{\sum{t_{event-Cx}} + scanWindow}`.

@@ -39,7 +39,7 @@ The following table shows which soft peripherals and their versions are supporte
 
    * - soft peripheral
      - Hardware platform
-     - Version(s)
+     - Versions
    * - sQSPI
      - nRF54L15 SoC
      - v0.1.0