-editing. First, however, Emacs might prompt you for confirmation, in
-case you entered the wrong buffer name. Emacs asks for confirmation
-only if the last key you typed, before submitting the minibuffer input
-with @key{RET}, was @key{TAB} (@code{minibuffer-complete}). This
-catches a common mistake, in which one types @key{RET} before
-realizing that @key{TAB} did not complete far enough to yield the
-desired buffer name (@pxref{Completion}). Emacs asks for confirmation
-by putting the message @samp{[Confirm]} in the minibuffer; type
-@key{RET} again to confirm and visit the buffer.
-
-@vindex confirm-nonexistent-file-or-buffer
- The variable @code{confirm-nonexistent-file-or-buffer} controls
-whether Emacs asks for confirmation before visiting a buffer that did
-not previously exist. The default value, @code{after-completion},
-gives the behavior we have just described. If the value is
-@code{nil}, Emacs never asks for confirmation; for any other
-non-@code{nil} value, Emacs always asks for confirmation. This
-variable also affects the @code{find-file} command (@pxref{Visiting}).
-
- One reason to create a new buffer is to use it for making temporary
-notes. If you try to save it, Emacs asks for the file name to use.
-The default value of the variable @code{major-mode} determines the new
-buffer's major mode; the default value is Fundamental mode. @xref{Major
-Modes}.
+editing. The default value of the variable @code{major-mode}
+determines the new buffer's major mode; the default value is
+Fundamental mode. @xref{Major Modes}. One reason to create a new
+buffer is to use it for making temporary notes. If you try to save
+it, Emacs asks for the file name to use, and the buffer's major mode
+is re-established taking that file name into account (@pxref{Choosing
+Modes}).