From 6295e10c080955246c9c71caddbc2ae05e59ea63 Mon Sep 17 00:00:00 2001 From: Andrew Welker Date: Mon, 28 Apr 2025 11:24:34 -0500 Subject: [PATCH] docs: correct spelling Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com> --- docs/docs/Communication-Basics.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/docs/docs/Communication-Basics.md b/docs/docs/Communication-Basics.md index 604e7159..449c2dfe 100644 --- a/docs/docs/Communication-Basics.md +++ b/docs/docs/Communication-Basics.md @@ -9,8 +9,7 @@ In networked A/V systems, devices can use many different methods of communicatio * `PepperDash.Core.GenericSshClient` * `PepperDash.Core.GenericSecureTcpIpClient` * `PepperDash.Essentials.Core.ComPortController` -* `PepperDash.Essentilas.Core.StatusMonitorBase` - +* `PepperDash.Essentials.Core.StatusMonitorBase` ## IBasicCommunication and ISocketStatus All common communication controllers will implement the `IBasicCommunication` interface, which is an extension of `ICommunicationReceiver`. This defines receive events, connection state properties, and send methods. Devices that need to use COM port, TCP, SSh or other similar communication will require an `IBasicCommunication` type object to be injected at construction time.