Updated Protocol and compatibility (markdown)

Protocol-and-compatibility.md

@@ -3,7 +3,7 @@
 - **Normal/Client mode** should be interoperable with other clients, which transmit raw text APRS messages if KISS client sends them in this format to the modem
   - NB! For interoperability with other APRS LoRa implementations, which do not use AX.25 frames, but use text based messages, need to use **TNC (plaintext TNC2)** APRSDroid connection protocol and set `cfg.EnableTextPackets/CFG_TEXT_PACKETS` to `true`, this way KISS will be disabled and TNC2 compatible mode will be activated
 - **Server iGate** by default supports only classical `AX25` frames over LoRa (as defined in http://www.aprs.org/doc/APRS101.PDF page 12, see section below). It should enable interoperability with classical Linux APRS software, such as Xastir with `kissattach`. 
-  - NB! Some popular LoRa ARPS implementations transfer plain text APRS messages over LoRa, for this mode operations need to set `cfg.EnableTextPackets/CFG_TEXT_PACKETS` to `true`, in this case iGate will transmit, receive and digirepeat text based APRS messages instead of classical AX25 frames.
+  - NB! Some popular LoRa ARPS implementations transfer plain text APRS messages over LoRa, for this mode operation need to set `cfg.EnableTextPackets/CFG_TEXT_PACKETS` to `true`, in this case iGate will transmit, receive and digirepeat text based APRS messages instead of classical AX25 frames.
 
 # APRS AX.25 binary protocol
 At the link level, APRS uses the AX.25 protocol, as defined in AmateurPacket-Radio Link-Layer Protocol, utilizing Unnumbered Information (UI) frames exclusively. This means that APRS runs in connection less mode, whereby AX.25 frames are transmitted without expecting any response, and reception at the other end is not guaranteed.At a higher level, APRS supports a messaging protocol that allows users tos end short messages (one line of text) to nominated stations, and expects to receive acknowledgements from those stations.