-glossing over a distinction that is irrelevant in ordinary use but is vital
-in understanding how to customize Emacs. It is the command
-@code{next-line} that is programmed to move down vertically. @kbd{C-n} has
-this effect @emph{because} it is bound to that command. If you rebind
-@kbd{C-n} to the command @code{forward-word} then @kbd{C-n} will move
-forward by words instead. Rebinding keys is a common method of
-customization.@refill
-
- In the rest of this manual, we usually ignore this subtlety to keep
-things simple. To give the information needed for customization, we
-state the name of the command which really does the work in parentheses
-after mentioning the key that runs it. For example, we will say that
-``The command @kbd{C-n} (@code{next-line}) moves point vertically
-down,'' meaning that @code{next-line} is a command that moves vertically
-down, and @kbd{C-n} is a key that is normally bound to it.
-
- While we are on the subject of information for customization only,
-it's a good time to tell you about @dfn{variables}. Often the
-description of a command will say, ``To change this, set the variable
-@code{mumble-foo}.'' A variable is a name used to remember a value.
-Most of the variables documented in this manual exist just to facilitate
-customization: some command or other part of Emacs examines the variable
-and behaves differently according to the value that you set. Until you
-are interested in customizing, you can ignore the information about
-variables. When you are ready to be interested, read the basic
-information on variables, and then the information on individual
-variables will make sense. @xref{Variables}.
+glossing over a subtle distinction that is irrelevant in ordinary use,
+but vital for Emacs customization. The command @code{next-line} does
+a vertical move downward. @kbd{C-n} has this effect @emph{because} it
+is bound to @code{next-line}. If you rebind @kbd{C-n} to the command
+@code{forward-word}, @kbd{C-n} will move forward one word instead.
+Rebinding keys is an important method of customization.
+
+ In the rest of this manual, we usually ignore this distinction to
+keep things simple. We will often speak of keys like @kbd{C-n} as
+commands, even though strictly speaking the key is bound to a command.
+Usually we state the name of the command which really does the work in
+parentheses after mentioning the key that runs it. For example, we
+will say that ``The command @kbd{C-n} (@code{next-line}) moves point
+vertically down,'' meaning that the command @code{next-line} moves
+vertically down, and the key @kbd{C-n} is normally bound to it.
+
+ Since we are discussing customization, we should tell you about
+@dfn{variables}. Often the description of a command will say, ``To
+change this, set the variable @code{mumble-foo}.'' A variable is a
+name used to store a value. Most of the variables documented in this
+manual are meant for customization: some command or other part of
+Emacs examines the variable and behaves differently according to the
+value that you set. You can ignore the information about variables
+until you are interested in customizing them. Then read the basic
+information on variables (@pxref{Variables}) and the information about
+specific variables will make sense.