diff --git a/Known-issues.md b/Known-issues.md
index 2beeece..142467a 100644
--- a/Known-issues.md
+++ b/Known-issues.md
@@ -380,10 +380,7 @@ Spicetools was never designed to provide support for games based on the Unity en
     * Some games won't boot into windowed mode.
     * Image resize and window resize options don't work.
     * Companion streaming doesn't work.
- * Input:
-    * Most Unity games register for raw input for mouse, preventing spice's I/O stack from using raw mouse data. Most of them take over the mouse input for touch.
-    * This is a Windows limitation (only one window handle can register for rawinput for a category of devices)
-    * As a result, in some Unity games, you cannot use the mouse wheel in the overlay, or bind mouse in Buttons / Analogs.
+ * Input: some games register for mouse rawinput, so you can't use mouse wheel in overlay, can't use `Bind` for mouse buttons, and can't map mouse movement for analogs.
  * They seem to have a set of default debug key binds that always work; e.g., WASD for directional input. You'll need to map keys through spice that do not conflict with these, or use a controller.
  * In general, patches are not supported. Spice's patch system is built to make small modifications to small number of binaries. Most of the game logic is in managed code for Unity-based games, so the patches aren't trivial. Please look to binary replacements and third party tools for patching.
  * If you encounter a crash, check Windows Event Viewer. Spice can't capture the stack for managed code.