pepperdash/Essentials
1
0
Fork 0
mirror of https://github.com/PepperDash/Essentials.git synced 2026-04-13 12:37:07 +00:00
Code Issues Projects Releases Packages Wiki Activity

docs: correct spelling

Browse source 
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
This commit is contained in:
Andrew Welker 2025-04-28 11:24:34 -05:00 • committed by GitHub
parent b9553f486a
commit 6295e10c08
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 2 deletions
Download patch file Download diff file Expand all files Collapse all files

3
docs/docs/Communication-Basics.md
View file

@ -9,8 +9,7 @@ In networked A/V systems, devices can use many different methods of communicatio
* `PepperDash.Core.GenericSshClient` * `PepperDash.Core.GenericSshClient`
* `PepperDash.Core.GenericSecureTcpIpClient` * `PepperDash.Core.GenericSecureTcpIpClient`
* `PepperDash.Essentials.Core.ComPortController` * `PepperDash.Essentials.Core.ComPortController`
* `PepperDash.Essentilas.Core.StatusMonitorBase` * `PepperDash.Essentials.Core.StatusMonitorBase`
## IBasicCommunication and ISocketStatus ## 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. 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.