readme fix

README.md

@@ -4,7 +4,7 @@ This is a [Zephyr](https://www.zephyrproject.org/) implementation of the [BLE-MI
 
 To minimize latency, a connection interval of 7.5 ms is requested, which is the smallest interval allowed by the Bluetooth low energy specification. Note that a central may or may not accept this value. 
 
-By default, outgoing MIDI messages are sent in separate BLE packets. When building for nRF SoCs, outgoing messages can optionally be buffered and transmitted in a single BLE packet the start of the next connection event to reduce latency, see `CONFIG_BLE_MIDI_TX_MODE_NRF_RADIO_NOTIF`. This technique uses the [MPSL radio notifications API](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.3/nrfxlib/mpsl/doc/radio_notification.html) of the [nRF Connect SDK](https://github.com/nrfconnect/sdk-nrf) as described in [this post](https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/optimizing-ble-midi-with-regards-to-timing-1293631358).
+By default, outgoing MIDI messages are sent in separate BLE packets. When building for nRF SoCs, outgoing non-sysex messages can optionally be buffered and transmitted in a single BLE packet the start of the next connection event to reduce latency, see `CONFIG_BLE_MIDI_TX_MODE_NRF_RADIO_NOTIF`. This technique uses the [MPSL radio notifications API](https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.4.3/nrfxlib/mpsl/doc/radio_notification.html) of the [nRF Connect SDK](https://github.com/nrfconnect/sdk-nrf) as described in [this post](https://devzone.nordicsemi.com/nordic/nordic-blog/b/blog/posts/optimizing-ble-midi-with-regards-to-timing-1293631358).
 
 ## Usage