From 79e0e1ec025b1ef8691f14178cd1d35f2edd4de5 Mon Sep 17 00:00:00 2001
From: EskCresh <167920287+EskCresh@users.noreply.github.com>
Date: Tue, 18 Nov 2025 21:13:35 -0500
Subject: [PATCH] Fix typo

---
 docs/dev-guide/writing-buttplug-applications/device-enum.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/dev-guide/writing-buttplug-applications/device-enum.mdx b/docs/dev-guide/writing-buttplug-applications/device-enum.mdx
index a4c8d2c..dcbf8fe 100644
--- a/docs/dev-guide/writing-buttplug-applications/device-enum.mdx
+++ b/docs/dev-guide/writing-buttplug-applications/device-enum.mdx
@@ -39,7 +39,7 @@ There are 2 events related to device connections that the client may fire:
       this device, and that the device can take commands.
 - DeviceRemoved (Event/Callback)
     - This event will fire when a device disconnects from the server for some reason. It should
-      contain and instance of the device that disconnected.
+      contain an instance of the device that disconnected.
     
 While the events are handy for updating UI, Client implementations usually also hold a list of
 currently connected devices that can be used for iteration if needed.