Update README for ASIO v2.3.3

README.md

@@ -13,7 +13,7 @@ This library currently supports the following:
 - Get the current default input and output stream formats for a device.
 - Build and run input and output PCM streams on a chosen device with a given stream format.
 
-Currently supported backends include:
+Currently supported hosts include:
 
 - Linux (via ALSA)
 - Windows (via WASAPI by default, see ASIO instructions below)
@@ -39,10 +39,11 @@ WASAPI. To do so, follow these steps:
 1. **Download the ASIO SDK** `.zip` from [this
    link](https://www.steinberg.net/en/company/developers.html). The version as
    of writing this is 2.3.1.
-2. Extract the files and place the `ASIOSDK2.3.1` directory somewhere you are
-   happy for it to stay (e.g. `~/.asio`).
-3. Assign the full path of the `ASIOSDK2.3.1` directory to the `CPAL_ASIO_DIR`
-   environment variable. [How to set persisting Environment Variables on
+2. Extract the files and place the directory somewhere you are happy for it to stay
+   (e.g. `~/.asio`).
+3. Assign the full path of the directory (that contains the `readme`, `changes`,
+   `ASIO SDK 2.3` pdf, etc) to the `CPAL_ASIO_DIR` environment variable. [How to
+   set persisting Environment Variables on
    Windows](https://gist.github.com/mitchmindtree/92c8e37fa80c8dddee5b94fc88d1288b#file-windows_environment_variables-md).
    The existence of the `CPAL_ASIO_DIR` environment variable determines whether
    or not CPAL will attempt to build the ASIO SDK and generate bindings to it.
@@ -83,5 +84,8 @@ WASAPI. To do so, follow these steps:
    If you run into an error along the lines of "no variant `Asio` in `HostId`",
    make sure that `CPAL_ASIO_DIR` is set correctly and try `cargo clean`.
 
+
 In the future we would like to work on automating this process to make it
 easier, but we are not familiar enough with the ASIO license to do so yet.
+
+*Updated as of ASIO version 2.3.3.*