bug#12144: 24.1; (elisp) `Initial Parameters' misleading about minibuffer-only

[Chong Yidong]

"Drew Adams" <drew.adams@oracle.com> writes:

> In this node, the text tries to say that if `initial-frame-alist'
> contains (minbuffer), i.e., (minibuffer . nil) then that means that you
> also want to create another, minibuffer-only frame, which has the
> parameter value (minbuffer . only).  And so Emacs creates that
> standalone minibuffer frame for you automatically.
>  
> The existing text that tries to say this is highly misleading.  It
> actually suggests that (minibuffer . nil) specifies a separate
> minibuffer-only frame, whereas it is (minibuffer . only) that specifies
> that.

Fixed, thanks.