Reword the watchdog changelog entry

CHANGELOG.md

@@ -32,16 +32,17 @@ Versioning](https://semver.org/spec/v2.0.0.html).
   issues](https://github.com/robbert-vdh/yabridge#runtime-dependencies-and-known-issues)
   section of the readme for more information on when this may be useful.
 - Yabridge would always try to gracefully shut down the Wine plugin host
-  processes when the native host crashes for whatever reason, but this did not
+  processes when the native host crashes or gets killed for whatever reason, but
-  always happen if the crash occurred before the plugin has finished
+  this did not always happen if the crash occurred before the bridged plugin has
-  initializing because of the way Unix Domain Sockets work. In that specific
+  finished initializing because of the way Unix Domain Sockets work. In that
-  situation a `yabridge-host.exe` process would be left running, and you might
+  specific situation the `yabridge-host.exe` process would be left running
-  not even be able to start your DAW anymore depending on the DAW. To prevent
+  indefinitely, and that might have also prevented you from being able to start
-  any more dangling processes, yabridge's Wine plugin hosts now have a watchdog
+  your DAW depending on the DAW. To prevent any more dangling processes,
-  that periodically checks whether the original process that spawned the bridges
+  yabridge's Wine plugin hosts now have a watchdog that periodically checks
-  is still running. If it detects that the process is no longer alive, yabridge
+  whether the original process that spawned the bridges is still running. If it
-  will close the sockets and shut down the bridged plugin to prevent any
+  detects that the process is no longer alive, yabridge will close the sockets
-  dangling processes from staying around.
+  and shut down the bridged plugin to prevent any dangling processes from
+  sticking around.
 
 ### Changed