From f64a4d0f06aa5e68dbe3ad565f610c79cc5114bf Mon Sep 17 00:00:00 2001 From: Garth Vander Houwen Date: Thu, 30 Jun 2022 12:00:06 -0700 Subject: [PATCH] delete removed link --- docs/developers/Firmware/mesh-alg.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developers/Firmware/mesh-alg.mdx b/docs/developers/Firmware/mesh-alg.mdx index 65113f7f..a291315b 100644 --- a/docs/developers/Firmware/mesh-alg.mdx +++ b/docs/developers/Firmware/mesh-alg.mdx @@ -10,7 +10,7 @@ The routing protocol for Meshtastic is really quite simple (and suboptimal). If ### A Note About Protocol Buffers -Because we want our devices to work across various vendors and implementations, we use [Protocol Buffers](https://github.com/meshtastic/Meshtastic-protobufs) pervasively. For information on how the protocol buffers are used with respect to API clients see [sw-design](/docs/software/other/sw-design), for purposes of this document you mostly only +Because we want our devices to work across various vendors and implementations, we use [Protocol Buffers](https://github.com/meshtastic/Meshtastic-protobufs) pervasively. For purposes of this document you mostly only need to consider the MeshPacket and Subpacket message types. ### Layer 0: LoRa Radio