; Fix doc typos related to indefinite articles
This commit is contained in:
parent
a06a8ed5b6
commit
35e5c57db3
12 changed files with 17 additions and 17 deletions
|
@ -1585,7 +1585,7 @@ use it, add the @samp{--tls} flag to @code{rmail-movemail-flags}.
|
|||
If your incoming mail is stored on a local machine in a format other
|
||||
than Unix mailbox, you will need the Mailutils @command{movemail} to
|
||||
retrieve it. @xref{Movemail}, for the detailed description of
|
||||
@command{movemail} versions. For example, to access mail from a inbox in
|
||||
@command{movemail} versions. For example, to access mail from an inbox in
|
||||
@code{maildir} format located in @file{/var/spool/mail/in}, you would
|
||||
include the following in the Rmail inbox list:
|
||||
|
||||
|
|
|
@ -11799,7 +11799,7 @@ Uses recursion."
|
|||
@end group
|
||||
@end smallexample
|
||||
|
||||
What happens when we call this function with a argument of 7?
|
||||
What happens when we call this function with an argument of 7?
|
||||
|
||||
The first instance of the @code{triangle-recursively} function adds
|
||||
the number 7 to the value returned by a second instance of
|
||||
|
@ -20821,7 +20821,7 @@ The function @code{1+} which adds one to its argument, is executed on
|
|||
|
||||
Contrast this with @code{apply}, which applies its first argument to
|
||||
all the remaining.
|
||||
(@xref{Readying a Graph, , Readying a Graph}, for a explanation of
|
||||
(@xref{Readying a Graph, , Readying a Graph}, for an explanation of
|
||||
@code{apply}.)
|
||||
|
||||
@need 1250
|
||||
|
|
|
@ -191,7 +191,7 @@ standard keyword from the @code{finder-known-keywords} list.
|
|||
as explained in @ref{Packaging Basics}. In the above example, a magic
|
||||
comment autoloads @code{superfrobnicator-mode}.
|
||||
|
||||
@xref{Package Archives}, for a explanation of how to add a
|
||||
@xref{Package Archives}, for an explanation of how to add a
|
||||
single-file package to a package archive.
|
||||
|
||||
@node Multi-file Packages
|
||||
|
|
|
@ -2980,7 +2980,7 @@ optional argument @var{append} is non-@code{nil}, @var{face} is
|
|||
appended to the end of the list instead. Note that in a face list,
|
||||
the first occurring value for each attribute takes precedence.
|
||||
|
||||
For example, the following code would assign a italicized green face
|
||||
For example, the following code would assign an italicized green face
|
||||
to the text between @var{start} and @var{end}:
|
||||
|
||||
@example
|
||||
|
|
|
@ -862,7 +862,7 @@ If the optional argument @var{pixelwise} is non-@code{nil},
|
|||
A positive @var{delta} moves the edge downwards or to the right; a
|
||||
negative @var{delta} moves it upwards or to the left. If the edge
|
||||
cannot be moved as far as specified by @var{delta}, this function
|
||||
moves it as far as possible but does not signal a error.
|
||||
moves it as far as possible but does not signal an error.
|
||||
|
||||
This function tries to resize windows adjacent to the edge that is
|
||||
moved. If this is not possible for some reason (e.g., if that adjacent
|
||||
|
|
|
@ -243,7 +243,7 @@ Interesting point. When wrapping skeletons around successive regions, they are
|
|||
put at these places. Point is left at first @code{_} where nothing is wrapped.
|
||||
@item @code{>}
|
||||
Indent line according to major mode. When following element is @code{_}, and
|
||||
there is a interregion that will be wrapped here, indent that interregion.
|
||||
there is an interregion that will be wrapped here, indent that interregion.
|
||||
@item @code{&}
|
||||
Logical and. If preceding element moved point, i.e., usually inserted
|
||||
something, do following element.
|
||||
|
|
|
@ -2408,7 +2408,7 @@ could achieve this with code like this in your @file{.emacs}:
|
|||
@end group
|
||||
@end example
|
||||
|
||||
In a programming team, a hook is a also a good place for each member
|
||||
In a programming team, a hook is also a good place for each member
|
||||
to put his own personal preferences. For example, you might be the
|
||||
only person in your team who likes Auto-newline minor mode. You could
|
||||
have it enabled by default by placing the following in your
|
||||
|
|
|
@ -753,7 +753,7 @@ privileges, you have several options:
|
|||
Info files don't actually need to be installed before being used.
|
||||
You can use a prefix argument for the @code{info} command and specify
|
||||
the name of the Info file in the minibuffer. This goes to the node
|
||||
named @samp{Top} in that file. For example, to view a Info file named
|
||||
named @samp{Top} in that file. For example, to view an Info file named
|
||||
@file{@var{info-file}} in your home directory, you can type this:
|
||||
|
||||
@example
|
||||
|
@ -3389,7 +3389,7 @@ version of Emacs, and see @ref{Current GNU distributions}, for a list of
|
|||
archive sites that make GNU software available.
|
||||
|
||||
@node Finding a package with particular functionality
|
||||
@section How do I find a Emacs Lisp package that does XXX?
|
||||
@section How do I find an Emacs Lisp package that does XXX?
|
||||
@cindex Package, finding
|
||||
@cindex Finding an Emacs Lisp package
|
||||
@cindex Functionality, finding a particular package
|
||||
|
|
|
@ -1022,7 +1022,7 @@ So that the user can enter @samp{info chmod}, for example.
|
|||
|
||||
@item Create a mode @code{eshell-browse}
|
||||
|
||||
It would treat the Eshell buffer as a outline. Collapsing the outline
|
||||
It would treat the Eshell buffer as an outline. Collapsing the outline
|
||||
hides all of the output text. Collapsing again would show only the
|
||||
first command run in each directory
|
||||
|
||||
|
|
|
@ -441,7 +441,7 @@ machine news.yourprovider.net login YourUserName password YourPassword
|
|||
@noindent
|
||||
.
|
||||
Make sure that the file isn't readable to others if you
|
||||
work on a OS which is capable of doing so. (Under Unix
|
||||
work on an OS which is capable of doing so. (Under Unix
|
||||
say
|
||||
@example
|
||||
chmod 600 ~/.authinfo
|
||||
|
@ -2012,7 +2012,7 @@ server by typing @samp{J a}. If you
|
|||
make a mistake, or change your mind, you can undo this
|
||||
action by typing @samp{J r}. When
|
||||
you're done, type 'q' to return to the group buffer.
|
||||
Now the next time you enter a group on a agentized
|
||||
Now the next time you enter a group on an agentized
|
||||
server, the headers will be stored on disk and read from
|
||||
there the next time you enter the group.
|
||||
|
||||
|
@ -2293,7 +2293,7 @@ When the term Emacs is used in this FAQ, it means either GNU
|
|||
Emacs or XEmacs.
|
||||
|
||||
@item Message
|
||||
In this FAQ message means a either a mail or a posting to a
|
||||
In this FAQ message means either a mail or a posting to a
|
||||
Usenet Newsgroup or to some other fancy back end, no matter
|
||||
of which kind it is.
|
||||
|
||||
|
|
|
@ -12991,7 +12991,7 @@ of these examples works:
|
|||
|
||||
@subsubheading Embedding clickable images
|
||||
For clickable images, provide a link whose description is another link to an
|
||||
image file. For example, to embed a image @file{org-mode-unicorn.png} which
|
||||
image file. For example, to embed an image @file{org-mode-unicorn.png} which
|
||||
when clicked jumps to @uref{http://Orgmode.org} website, do the following
|
||||
|
||||
@example
|
||||
|
|
|
@ -1340,7 +1340,7 @@ currently part of Supercite, but contributions are welcome!
|
|||
|
||||
Regi works by interpreting frames with the function
|
||||
@code{regi-interpret}. A frame is a list of arbitrary size where each
|
||||
element is a entry of the following form:
|
||||
element is an entry of the following form:
|
||||
|
||||
@example
|
||||
(@var{pred} @var{func} [@var{negate-p} [@var{case-fold-search}]])
|
||||
|
@ -1709,7 +1709,7 @@ of information from the info alist.
|
|||
@item @code{sc-mail-field-query} (@kbd{C-c C-p f})
|
||||
Allows you to interactively view, modify, add, and delete info alist
|
||||
key-value pairs. With no argument, you are prompted (with completion)
|
||||
for a info key. The value associated with that key is displayed in the
|
||||
for an info key. The value associated with that key is displayed in the
|
||||
minibuffer. With an argument, this command will first ask if you want
|
||||
to view, modify, add, or delete an info key. Viewing is identical to
|
||||
running the command with no arguments.
|
||||
|
|
Loading…
Add table
Reference in a new issue