diff --git a/NEWS.md b/NEWS.md
index e9450c6..14e07ca 100644
--- a/NEWS.md
+++ b/NEWS.md
@@ -1,4 +1,4 @@
-# mousetrap 3.1.3
+# mousetrap 3.1.4
 
 ## Announcements
 * A book chapter on the mousetrap software packages has been published. It covers many common analyses using the mousetrap R package. Please cite it as follows when using mousetrap in your research:
@@ -6,6 +6,17 @@
 * Besides, if you use functions for clustering and mapping trajectories, please also include the following reference:
 * Wulff, D. U., Haslbeck, J. M. B., Kieslich, P. J., Henninger, F., & Schulte-Mecklenbeck, M. (2019). Mouse-tracking: Detecting types in movement trajectories. In M. Schulte-Mecklenbeck, A. Kühberger, & J. G. Johnson (Eds.), _A Handbook of Process Tracing Methods_ (pp. 131-145). New York, NY: Routledge.
 
+## Changes in specific functions
+* `mt_measures`: Introduced `hover_incl_intial` argument to make inclusion of a potential initial phase without movement optional when calculating hovers. By default, this initial phase is included (as in previous versions).
+* `mt_measures`: Multiple values can now be specified in the `hover_threshold` argument. If this is done, hovers and hover_time will be returned in separate variables for each threshold value (the variable name will be suffixed with the threshold value).
+* `mt_measures`: Multiple values can now be specified in the `flip_threshold` argument. If this is done, flips (e.g., xpos_flips) will be returned in separate variables for each threshold value (the variable name will be suffixed with the threshold value).
+
+## Internal changes
+* When checking the class of an object, `inherits` is now used consistently instead of the `class` function to avoid problems with future R releases (>=4.0.0).
+
+
+# mousetrap 3.1.3
+
 ## Changes in specific functions
 * `mt_sample_entropy`: By default, sample entropy is calculated based on the differences of the position values (following Hehman et al., 2015). An optional argument `use_diff` now has been introduced to allow users to override this behavior and use the untransformed values instead, by setting `use_diff=FALSE`.
 * `mt_align_start_end`: Now checks, if start and end points are equal for a trial (separately per dimension). If so, returns a warning message as the aligned trajectory values for the respective dimension will be `NaN`/`Inf`/`-Inf`.