Minor refactors & comment revision

core/core-editor.el

@@ -220,17 +220,18 @@ or file path may exist now."
         revert-without-query (list "."))
 
   ;; `auto-revert-mode' and `global-auto-revert-mode' would, normally, abuse the
-  ;; heck out of inotify handles _or_ aggresively poll your buffer list every X
-  ;; seconds. Too many inotify handles can grind Emacs to a halt if you preform
+  ;; heck out of file watchers _or_ aggressively poll your buffer list every X
+  ;; seconds. Too many watchers can grind Emacs to a halt if you preform
   ;; expensive or batch processes on files outside of Emacs (e.g. their mtime
   ;; changes), and polling your buffer list is terribly inefficient as your
-  ;; buffer list grows into the tens or hundreds.
+  ;; buffer list grows into the hundreds.
   ;;
-  ;; So Doom uses a different strategy: we lazily auto revert buffers when the
-  ;; user a) saves a file, b) switches to a buffer (or its window), or c) you
-  ;; focus Emacs (after using another program). This way, Emacs only ever has to
-  ;; operate on, at minimum, a single buffer and, at maximum, X buffers, where X
-  ;; is the number of open windows (which is rarely, if ever, over 10).
+  ;; Doom does this lazily instead. i.e. All visible buffers are reverted
+  ;; immediately when a) a file is saved or b) Emacs is refocused (after using
+  ;; another app). Meanwhile, buried buffers are reverted only when they are
+  ;; switched to. This way, Emacs only ever has to operate on, at minimum, a
+  ;; single buffer and, at maximum, ~10 buffers (after all, when do you ever
+  ;; have more than 10 windows in any single frame?).
   (defun doom-auto-revert-buffer-h ()
     "Auto revert current buffer, if necessary."
     (unless (or auto-revert-mode (active-minibuffer-window))