From b885164ce6167966841d2bb695d5deb3c211e0b8 Mon Sep 17 00:00:00 2001
From: Henrik Lissner <henrik@lissner.net>
Date: Mon, 4 Dec 2017 13:43:04 -0500
Subject: [PATCH] Update comments in core-packages

---
 core/core-packages.el | 16 +++++++---------
 1 file changed, 7 insertions(+), 9 deletions(-)

diff --git a/core/core-packages.el b/core/core-packages.el
index 2776f0984..88e45f319 100644
--- a/core/core-packages.el
+++ b/core/core-packages.el
@@ -158,9 +158,9 @@ startup."
        (package-refresh-contents)
        (setq doom--refreshed-p t)
        (package-initialize t)))
-    ;; We could let `package-initialize' fill `load-path', but it costs precious
-    ;; milliseconds and does other stuff I don't need (like load autoload
-    ;; files). My premature optimization quota isn't filled yet.
+    ;; We could let `package-initialize' fill `load-path', but it does more than
+    ;; that alone (like load autoload files). If you want something prematurely
+    ;; optimizated right, ya gotta do it yourself.
     ;;
     ;; Also, in some edge cases involving package initialization during a
     ;; non-interactive session, `package-initialize' fails to fill `load-path'.
@@ -556,9 +556,8 @@ This should be run whenever init.el or an autoload file is modified. Running
   ;; This function must not use autoloaded functions or external dependencies.
   ;; It must assume nothing is set up!
   (if (not noninteractive)
-      ;; This is done "asynchroniously" to protect the current session's state.
-      ;; This is because `doom-initialize-packages' rereads your emacs config,
-      ;; which has side effects.
+      ;; This is done in another instance to protect the current session's
+      ;; state. `doom-initialize-packages' will have side effects otherwise.
       (and (doom-packages--async-run 'doom//reload-autoloads)
            (load doom-autoload-file))
     (doom-initialize-packages)
@@ -627,9 +626,8 @@ If RECOMPILE-P is non-nil, only recompile out-of-date files."
         (recompile-p (or recompile-p
                          (and (member "-r" (cdr argv)) t))))
     (if (not noninteractive)
-        ;; This is done "asynchroniously" to protect the current session's
-        ;; state. This is because `doom-initialize-packages' rereads your emacs
-        ;; config, which has side effects.
+        ;; This is done in another instance to protect the current session's
+        ;; state. `doom-initialize-packages' will have side effects otherwise.
         (doom-packages--async-run 'doom//byte-compile)
       (let ((total-ok   0)
             (total-fail 0)