1 files changed, 10 insertions, 13 deletions

diff --git a/toxcore/tox.h b/toxcore/tox.h
index d23065ff..eb6b4f31 100644
--- a/toxcore/tox.h
+++ b/toxcore/tox.h
@@ -1645,11 +1645,11 @@ typedef enum TOX_ERR_FILE_SEND_CHUNK {
      */
     TOX_ERR_FILE_SEND_CHUNK_NOT_TRANSFERRING,
     /**
-     * Attempted to send more data than requested. The requested data size is
+     * Attempted to send more or less data than requested. The requested data size is
      * adjusted according to maximum transmission unit and the expected end of
-     * the file. Trying to send more will result in no data being sent.
+     * the file. Trying to send less or more than requested will return this error.
      */
-    TOX_ERR_FILE_SEND_CHUNK_TOO_LARGE,
+    TOX_ERR_FILE_SEND_CHUNK_INVALID_LENGTH,
     /**
      * Packet queue is full.
      */
@@ -1664,12 +1664,12 @@ typedef enum TOX_ERR_FILE_SEND_CHUNK {
  * Send a chunk of file data to a friend.
  *
  * This function is called in response to the `file_request_chunk` callback. The
- * length parameter should be equal to or less than the one received though the
- * callback. If it is zero, the transfer is assumed complete. For files with
- * known size, Core will know that the transfer is complete after the last byte
- * has been received, so it is not necessary (though not harmful) to send a
- * zero-length chunk to terminate. For streams, it is necessary for the last
- * chunk sent to be zero-length.
+ * length parameter should be equal to the one received though the callback. 
+ * If it is zero, the transfer is assumed complete. For files with known size, 
+ * Core will know that the transfer is complete after the last byte has been 
+ * received, so it is not necessary (though not harmful) to send a zero-length 
+ * chunk to terminate. For streams, core will know that the transfer is finished 
+ * if a chunk with length less than the length requested in the callback is sent.
  *
  * @return true on success.
  */
@@ -1694,10 +1694,7 @@ bool tox_file_send_chunk(Tox *tox, uint32_t friend_number, uint32_t file_number,
  * In response to receiving this callback, the client should call the function
  * `tox_file_send_chunk` with the requested chunk. If the number of bytes sent
  * through that function is zero, the file transfer is assumed complete. A
- * client may choose to send less than requested, if it is reading from a
- * stream that doesn't have more data, yet, and it still wants to send some
- * data to the other side. However, this will generally be less efficient than
- * waiting for a full chunk size of data to be ready.
+ * client must send the full length of data requested with this callback.
  *
  * @param friend_number The friend number of the receiving friend for this file.
  * @param file_number The file transfer identifier returned by tox_file_send.