-loaded, and functions to be called, by giving Emacs arguments in the
-shell command line. @xref{Emacs Invocation}. But we don't recommend
-doing this. The feature exists mainly for compatibility with other
-editors.
-
- Many other editors are designed to be started afresh each time you
-want to edit. You edit one file and then exit the editor. The next
-time you want to edit either another file or the same one, you must run
-the editor again. With these editors, it makes sense to use a
-command-line argument to say which file to edit.
-
- But starting a new Emacs each time you want to edit a different file
-does not make sense. This would fail to take advantage of Emacs's
-ability to visit more than one file in a single editing session, and
-it would lose the other accumulated context, such as the kill ring,
-registers, undo history, and mark ring, that are useful for operating
-on multiple files or even one.
+loaded, and functions to be called through Emacs command-line
+arguments. @xref{Emacs Invocation}. The feature exists mainly for
+compatibility with other editors, and for scripts.
+
+ Many editors are designed to edit one file. When done with that
+file, you exit the editor. The next time you want to edit a file, you
+must start the editor again. Working this way, it is convenient to
+use a command-line argument to say which file to edit.
+
+ It's not smart to start Emacs afresh for every file you edit. Emacs
+can visit more than one file in a single editing session, and upon
+exit Emacs loses valuable accumulated context, such as the kill ring,
+registers, undo history, and mark ring. These features are useful for
+operating on multiple files, or even one. If you kill Emacs after
+each file, you don't take advantage of them.