From 17e1916eb80f0cee0d9a394df6ef9b3a0c0fb446 Mon Sep 17 00:00:00 2001 From: Jason Cooke Date: Fri, 9 Aug 2019 09:57:04 +1200 Subject: [PATCH] docs: fix typo --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 7ec3ccd7..01091a74 100755 --- a/README.md +++ b/README.md @@ -282,7 +282,7 @@ if we disregard the miniscule constant term. The overhead of peak finding is the bottleneck - I experimented with mutlithreading and realtime matching, and alas, it wasn't meant to be in Python. An equivalent Java or C/C++ implementation would most likely have little trouble keeping up, applying FFT and peakfinding in realtime. -An important caveat is of course, the round trip time (RTT) for making matches. Since my MySQL instance was local, I didn't have to deal with the latency penalty of transfering fingerprint matches over the air. This would add RTT to the constant term in the overall calculation, but would not effect the matching process. +An important caveat is of course, the round trip time (RTT) for making matches. Since my MySQL instance was local, I didn't have to deal with the latency penalty of transferring fingerprint matches over the air. This would add RTT to the constant term in the overall calculation, but would not effect the matching process. ### Storage