From c80098ab2e881373fa1f84b3401dee3263d4b27a Mon Sep 17 00:00:00 2001
From: Ryan Tharp <neuro@interx.net>
Date: Wed, 29 Jan 2020 02:51:32 -0800
Subject: [PATCH] update note

---
 js/views/app_view.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/js/views/app_view.js b/js/views/app_view.js
index 1dc1fb90d..9b62d9a06 100644
--- a/js/views/app_view.js
+++ b/js/views/app_view.js
@@ -130,8 +130,8 @@
       //   so its loading screen doesn't stick around forever.
 
       // Two primary techniques at play for this situation:
-      //   - background.js has two openInbox() calls, and passes initalLoadComplete
-      //     directly via the options parameter.
+      //   - background.js has X number of openInbox() calls,
+      //      and passes initalLoadComplete directly via the options parameter.
       //   - in other situations openInbox() will be called with no options. So this
       //     view keeps track of whether onEmpty() has ever been called with
       //     this.initialLoadComplete. An example of this: on a phone-pairing setup.