From e8af249b4d872656be151c624c786136f5669437 Mon Sep 17 00:00:00 2001 From: pdxlocations Date: Sat, 24 Jun 2023 22:02:14 -0700 Subject: [PATCH] most likely back to probably --- docs/about/contributing.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/about/contributing.mdx b/docs/about/contributing.mdx index 8140dbe7..2778674d 100644 --- a/docs/about/contributing.mdx +++ b/docs/about/contributing.mdx @@ -33,7 +33,7 @@ The [firmware repo](https://github.com/meshtastic/firmware) is where all of the ### Firmware Modules -[Modules](/docs/settings/moduleconfig) extend device and mesh functionality beyond core functions. These are also implemented mainly in the firmware repo above. Typically, you would add definitions in the protobufs repo and the device repo to implement module functionality. You most likely also want to have some client or device, use or interact with the module. This is where Device Interface support comes into play. +[Modules](/docs/settings/moduleconfig) extend device and mesh functionality beyond core functions. These are also implemented mainly in the firmware repo above. Typically, you would add definitions in the protobufs repo and the device repo to implement module functionality. You probably also want to have some client or device, use or interact with the module. This is where Device Interface support comes into play. ### CLI Apps (Device Interface)