From 2e46dff72cff5acb411bf26dd8a8c25c63854982 Mon Sep 17 00:00:00 2001 From: Dan Srebnick Date: Sat, 16 Sep 2017 07:59:53 -0400 Subject: [PATCH] Fix typo in README --- README | 2 +- noaacap/usr/local/share/noaacap/README | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/README b/README index 77e0a88..bf0bdd7 100644 --- a/README +++ b/README @@ -30,7 +30,7 @@ beacon via WIDE2-1 \ The timeout was needed on my older and slower single core Raspberry Pi Model B. The aprx default timeout is 10 seconds and the timeout may not be needed on a -RPi 2 or newer. If you need lots of "BEACON EXEC abnormal close" messages in +RPi 2 or newer. If you see lots of "BEACON EXEC abnormal close" messages in aprx.log, then you likely need to add the timeout. The program will check for a new alert or update every 2 minutes, but only diff --git a/noaacap/usr/local/share/noaacap/README b/noaacap/usr/local/share/noaacap/README index 8beec3e..9006014 100644 --- a/noaacap/usr/local/share/noaacap/README +++ b/noaacap/usr/local/share/noaacap/README @@ -25,7 +25,7 @@ beacon via WIDE2-1 \ The timeout was needed on my older and slower single core Raspberry Pi Model B. The aprx default timeout is 10 seconds and the timeout may not be needed on a -RPi 2 or newer. If you need lots of "BEACON EXEC abnormal close" messages in +RPi 2 or newer. If you see lots of "BEACON EXEC abnormal close" messages in aprx.log, then you likely need to add the timeout. The program will check for a new alert or update every 2 minutes, but only