From a1214f2645eb917f2571fdb1c7eecc8a80e5fed9 Mon Sep 17 00:00:00 2001 From: CrNMGuy Date: Fri, 10 Aug 2018 19:02:51 +0200 Subject: [PATCH] typo in URL diagnotic --- extras/doc/Tradeoffs.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/extras/doc/Tradeoffs.md b/extras/doc/Tradeoffs.md index 7bcab21..8a58cf8 100644 --- a/extras/doc/Tradeoffs.md +++ b/extras/doc/Tradeoffs.md @@ -19,7 +19,7 @@ In general, using the fix-oriented methods `available` and `read` are atomically If you are using the advanced [character-oriented methods](/extras/doc/CharOriented.md): * You must wait to access the internal `gps.fix()` until after the entire sentence has been parsed. -* Only 3 example programs use these methods: NMEAblink, NMEAorder and NMEAdiagnostic. These examples simply `decode` until a sentence is COMPLETED. See `GPSloop()` in [NMEAdiagnostic.ino](/examples/NMEAdiagnostoc/NMEAdiagnostic.ino). +* Only 3 example programs use these methods: NMEAblink, NMEAorder and NMEAdiagnostic. These examples simply `decode` until a sentence is COMPLETED. See `GPSloop()` in [NMEAdiagnostic.ino](/examples/NMEAdiagnostic/NMEAdiagnostic.ino). * Member function `gps.is_safe()` can also be used to determine when it is safe to access the internal `gps.fix()`. * Received data errors can cause invalid field values to be set in the internal fix *before* the CRC is fully computed. The CRC will catch most of those, and the internal fix members will then be marked as invalid.