fix(post): fixed typos

_posts/2024-01-19-pikvm-tesmart.md

@@ -80,7 +80,7 @@ I retrained the devices per the video, and sure enough after powering the first
 
 When I think about the solution, it's challenging to know how and why this is working.  As I understand it, EDID emulators are meant to override a device's EDID, basically telling the connected device which capabilities it supports.  You would think that my devices were sending the proper EDID to the TESmart switch, however as I experienced with 4 devices (2 unique), this was not the case.  
 
-Some people have mentioned that this happens more often when running Linux, and I even experienced that myself too. When one of my Intel NUCs was running Windows it seemed to work fine but when running Proxmox (Debian Linux) it seemed to experience these issues.  This could be a Windows vs. Linux issue, or it could be chalked up to my other experience where 1 device would work fine but none of the others.  I've tested quite a bit over the span of a year and it's challenging to know for sure.  Oddly enough, this doesn't happen to everyone who uses TESmart switches.  I do think it's a combination of TESmart + Device + OS/driver that triggers the problem, because again, it works with my with EZCOO switch.  I also have a hunch that these emulators might be instructing the device's GPU to stay powered on even when a device isn't plugged into it (just like HDMI dummy plugs), however I don't know if that's true.
+Some people have mentioned that this happens more often when running Linux, and I even experienced that myself too. When one of my Intel NUCs was running Windows it seemed to work fine but when running Proxmox (Debian Linux) it seemed to experience these issues.  This could be a Windows vs. Linux issue, or it could be chalked up to my other experience where 1 device would work fine but none of the others.  I've tested quite a bit over the span of a year and it's challenging to know for sure.  Oddly enough, this doesn't happen to everyone who uses TESmart switches.  I do think it's a combination of TESmart + Device + OS/driver that triggers the problem, because again, it works with my with EZCOO switch.  I also have a hunch that these emulators might be instructing the device's GPU to stay powered on even when a device isn't plugged into it (just like HDMI dummy plugs), however I don't know if that's true.  If you know, let me know in the comments below!
 
 I am considering this "fixed" now even though technically this is a "workaround."  A huge thanks to Max from PiKVM, Ray from TESmart (and the TESmart team), and juristoeckli and NateDiTo in the comments because without all of you I would have given up.  Each new idea or additional troubleshooting step motivated me to keep going.  I can finally use this switch and recommend it to those who want something rackmountable (with workarounds).