fixed the documentation of sendBinaryMessage function.

NEWS.md

@@ -77,6 +77,8 @@
 
 * Closed #2955: Input and output bindings previously attempted to use `el['data-input-id']`, but that never worked. They now use `el.getAttribute('data-input-id')` instead. (#3538)
 
+* fixed the documentation of `sendBinaryMessage` function.
+
 ### Minor improvements
 
 * When taking a test snapshot, the sort order of the json keys of the `input`, `output`, and `export` fields is currently sorted using the locale of the machine. This can lead to inconsistent test snapshot results. To opt-in to a consistent ordering of snapshot fields with `{shinytest}`, please set the global option `options(shiny.snapshotsortc = TRUE)`. `{shinytest2}` users do not need to set this value. (#3515)

R/shiny.R

@@ -220,11 +220,11 @@ workerId <- local({
 #'   `sendCustomMessage` is called on the server.
 #' }
 #' \item{sendBinaryMessage(type, message)}{
-#'   Similar to `sendCustomMessage`, but the message must be a raw vector
-#'   and the registration method on the client is
-#'   \code{Shiny.addBinaryMessageHandler(type, function(message){...})}. The
-#'   message argument on the client will be a
-#'   [DataView](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/DataView).
+#'   Similar to sendCustomMessage, but the message must be a raw vector.
+#'   The registration method on the client is the same as for other custom messages:
+#'   \code{Shiny.addCustomMessageHandler(type, function(message){...})}. The
+#'   message argument on the client will be an
+#'   [ArrayBuffer](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/ArrayBuffer).
 #' }
 #' \item{sendInputMessage(inputId, message)}{
 #'   Sends a message to an input on the session's client web page; if the input