@item
Variable-size characters are not supported in Emacs 20. You cannot use
fonts which contain oversized characters, and using italics fonts can
-results in illegible display. However, text which uses variable-size
+result in illegible display. However, text which uses variable-size
fonts is unreadable anyway. With all characters in a frame layed out on
a regular grid, each character having the same height and width, text is
much easier to read.
strike-through, and overline, have been eliminated.
@item
-Emacs now provides its own ``lean and mean'' scroll bars instead using
+Emacs now provides its own ``lean and mean'' scroll bars instead of using
those from the X toolkit. Toggle buttons and radio buttons in menus now
look just like any other menu item, which simplifies them, and prevents
them from standing out and distracting your attention from the other
explicit words, their meaning is more self-evident.
@item
-Colors are not available on character terminals. If you @emph{must}
+Colors are not available on text-only terminals. If you @emph{must}
have colors, but cannot afford running X, you can now use the MS-DOG
version of Emacs inside a DOS emulator.
when the menu bar is not displayed.
@item
-For uniformity, @key{delete} function key in Emacs 20 works exactly like
+For uniformity, the @key{delete} function key in Emacs 20 works exactly like
the @key{DEL} key, on both text-only terminals and window systems---it
always deletes backward. This eliminates the inconsistency of Emacs 21,
where the key labeled @key{delete} deletes forward when you are using a
CC Mode now enforces identical values for some customizable options,
such as indentation style, for better consistency. In particular, if
you select an indentation style for Java, the same style is used
-for C and C@t{++} buffer as well.
+for C and C@t{++} buffers as well.
@item
Isearch does not highlight other possible matches; it shows only the
this feature.
@item
-The @code{field} property does not exist in Emasc 20, so various
+The @code{field} property does not exist in Emacs 20, so various
packages that run subsidiary programs in Emacs buffers cannot in general
distinguish which text was user input and which was output from the
subprocess. If you need to try to do this nonetheless, Emacs 20