Use 'concurrent' instead of 'asynchronous'

While asynchronous is technically also correct, this makes it a bit
clearer what's going on.

CHANGELOG.md

@@ -11,17 +11,17 @@ Versioning](https://semver.org/spec/v2.0.0.html).
 ### Added
 
 - The way communication works in yabridge has been completely redesigned to be
-  asynchronous and to use additional threads as necessary. This was needed to
+  fully concurrent and to use additional threads as necessary. This was needed
-  allow yabridge to handle nested and mutually recursive function calls as well
+  to allow yabridge to handle nested and mutually recursive function calls as
-  as several other edge cases. What this boils down to is that yabridge became
+  well as several other edge cases. What this boils down to is that yabridge
-  even faster, more responsive, and can now handle a few edge case scenarios
+  became even faster, more responsive, and can now handle a few edge case
-  that would previously require workarounds. This means that yabridge no longer
+  scenarios that would previously require workarounds. This means that yabridge
-  requires the `hack_reaper_update_display` workaround for _REAPER_ and
+  no longer requires the `hack_reaper_update_display` workaround for _REAPER_
-  _Renoise_, that the loading issues in Bitwig Studio 3.3 beta 1 have also been
+  and _Renoise_, that the loading issues in Bitwig Studio 3.3 beta 1 have also
-  resolved, and that certain plugins like Kontakt no longer interrupt playback
+  been resolved, and that certain plugins like Kontakt no longer interrupt
-  in Bitwig while their editor is opening. I have been testing this extensively
+  playback in Bitwig while their editor is opening. I have been testing this
-  to make sure that the change does not introduce any regressions, but please
+  extensively to make sure that the change does not introduce any regressions,
-  let me know if this does break anything for you.
+  but please let me know if this does break anything for you.
 
   TODO: Expand on this  
   TODO: Remove known issue about opening Kontakt and certain other plugins

src/common/communication.h

@@ -557,12 +557,12 @@ class EventHandler {
     /**
      * This acceptor will be used once synchronously on the listening side
      * during `Sockets::connect()`. When `EventHandler::receive()` is then
-     * called, we'll recreate the acceptor asynchronously listen for new
+     * called, we'll recreate the acceptor to asynchronously listen for new
-     * incoming socket connections on `endpoint` using this same acceptor. This
+     * incoming socket connections on `endpoint` using. This is important,
-     * is important, because on the case of `vst_host_callback` the acceptor is
+     * because on the case of `vst_host_callback` the acceptor is first accepts
-     * first accepts an initial socket on the plugin side (like all sockets),
+     * an initial socket on the plugin side (like all sockets), but all
-     * but all additional incoming connections of course have to be listened for
+     * additional incoming connections of course have to be listened for on the
-     * on the plugin side.
+     * plugin side.
      */
     std::optional<boost::asio::local::stream_protocol::acceptor> acceptor;