docs: remark that dropping an Evdev can take a while

Author: SludgePhD

src/evdev.rs

@@ -55,6 +55,19 @@ use crate::{
 /// Since multiple [`Evdev`]s can refer to the same file handle, none of the methods require a
 /// mutable reference, again mirroring the API of [`TcpStream`].
 ///
+/// # Blocking Drop
+///
+/// When an [`Evdev`] is dropped, the underlying file descriptor is closed, which can block for a
+/// considerable amount of time (50-100 ms).
+/// This is happening in the evdev subsystem in the kernel, so there is not much userspace can do
+/// about that.
+///
+/// If this delay is a problem for your application, there are several options:
+///
+/// - Send the [`Evdev`] to another thread and drop it there.
+/// - [`mem::forget`][std::mem::forget] the [`Evdev`] and leak the file descriptor, if that leak is
+///   acceptable for your application.
+///
 /// # Device Lifecycle
 ///
 /// (the observations here were made on Linux, the behavior on FreeBSD may differ a bit)

src/ff.rs

@@ -410,7 +410,7 @@ impl Effect<'_> {
     /// By default, effects use ID `-1`, which is appropriate when uploading a new effect to a
     /// device (the input subsystem will allocate an ID for the effect).
     ///
-    /// The ID can be set to a existing [`EffectId`] in order to reconfigure an already uploaded
+    /// The ID can be set to an existing [`EffectId`] in order to reconfigure an already uploaded
     /// effect.
     #[inline]
     pub fn with_id(mut self, id: EffectId) -> Self {