Fix typo

README.md

@@ -143,7 +143,7 @@ will automatically pick up any of your Windows VST2 plugins.
   You'll likely have to log out and back in again for this to take effect for
   applications not launched through a terminal. To check whether everything's
   set up correctly you could run `which yabridge-host.exe` in a terminal. If it
-  is, then that should print a path to `yabridge-hsot.exe`.
+  is, then that should print a path to `yabridge-host.exe`.
 
 - If you're using the symlink installation method and you're seeing multiple
   duplicate instances of the same plugin, or after opening one plugin every
@@ -387,7 +387,7 @@ as the _Windows VST plugin_. The whole process works as follows:
      `process()` function, then the Wine VST host will emulate the behavior of
      `processReplacing()` instead.
    - The Windows VST plugin's `AEffect` object. A copy of this is sent over a
-     socket from the Wine VST hsot to the plugin after the Windows VST plugin
+     socket from the Wine VST host to the plugin after the Windows VST plugin
      has finished initializing. Whenever this struct gets updated by the Windows
      VST plugin, the Windows VST plugin will call the `audioMasterIOChanged()`
      host callback and we'll repeat the process.

meson.build

@@ -17,7 +17,7 @@ endif
 
 # Depending on the `use-bitbridge` flag we'll enable building a second 32-bit
 # host application that can act as a bit bridge for using 32-bit Windows plugins
-# in 64-bit Linux VST hsots. The plugin will determine which host application to
+# in 64-bit Linux VST hosts. The plugin will determine which host application to
 # use based on the `.dll` file it's trying to load.
 # This setup is necessary until Meson provides a way to have multiple
 # cross-builds for a single build directory:

src/common/events.h

@@ -126,7 +126,7 @@ class DefaultDataConverter {
  *   contains either a string or a null pointer while `dispatch()` calls might
  *   contain opcode specific structs. See the documentation for `EventPayload`
  *   for more information. The `DefaultDataConverter` defined above handles the
- *   basic behavior that's sufficient for hsot callbacks.
+ *   basic behavior that's sufficient for host callbacks.
  * @param logging A pair containing a logger instance and whether or not this is
  *   for sending `dispatch()` events or host callbacks. Optional since it
  *   doesn't have to be done on both sides.
@@ -312,7 +312,7 @@ auto passthrough_event(AEffect* plugin, F callback) {
                 // This is a bit of a special case! Instead of writing some
                 // return value, we will update values on the native VST
                 // plugin's `AEffect` object. This is triggered by the
-                // `audioMasterIOChanged` callback from the hsoted VST plugin.
+                // `audioMasterIOChanged` callback from the hosted VST plugin.
 
                 // These are the same fields written by bitsery in the
                 // initialization of `PluginBridge`. I can't think of a way to

src/plugin/plugin-bridge.cpp

@@ -553,7 +553,7 @@ void PluginBridge::process_replacing(AEffect* /*plugin*/,
 
     // Plugins are allowed to send MIDI events during processing using a host
     // callback. These have to be processed during the actual
-    // `processReplacing()` function or else the hsot will ignore them. To
+    // `processReplacing()` function or else the host will ignore them. To
     // prevent these events from getting delayed by a sample we'll process them
     // after the plugin is done processing audio rather than during the time
     // we're still waiting on the plugin.

src/plugin/plugin-bridge.h

@@ -96,7 +96,7 @@ class PluginBridge {
     AEffect plugin;
 
     /**
-     * The VST hsot can query a plugin for arbitrary binary data such as
+     * The VST host can query a plugin for arbitrary binary data such as
      * presets. It will expect the plugin to write back a pointer that points to
      * that data. This vector is where we store the chunk data for the last
      * `effGetChunk` event.

src/plugin/utils.h

@@ -69,7 +69,7 @@ std::string create_logger_prefix(const boost::filesystem::path& socket_path);
 PluginArchitecture find_vst_architecture(boost::filesystem::path);
 
 /**
- * Finds the Wine VST hsot (either `yabridge-host.exe` or `yabridge-host.exe`
+ * Finds the Wine VST host (either `yabridge-host.exe` or `yabridge-host.exe`
  * depending on the plugin). For this we will search in two places:
  *
  *   1. Alongside libyabridge.so if the file got symlinked. This is useful