Fix typos in several manuals (Bug#31610)

Copyright-paperwork-exempt: yes
This commit is contained in:
Ville Skyttä 2018-05-27 19:03:10 +02:00 committed by Eli Zaretskii
parent e5471b2381
commit 6d2352594f
7 changed files with 10 additions and 10 deletions

View file

@ -484,7 +484,7 @@ Narrowing and Widening
@code{car}, @code{cdr}, @code{cons}: Fundamental Functions
* Strange Names:: An historical aside: why the strange names?
* Strange Names:: A historical aside: why the strange names?
* car & cdr:: Functions for extracting part of a list.
* cons:: Constructing a list.
* nthcdr:: Calling @code{cdr} repeatedly.
@ -6797,7 +6797,7 @@ will see @code{cons} as well as two variants on @code{cdr},
namely, @code{setcdr} and @code{nthcdr}. (@xref{copy-region-as-kill}.)
@menu
* Strange Names:: An historical aside: why the strange names?
* Strange Names:: A historical aside: why the strange names?
* car & cdr:: Functions for extracting part of a list.
* cons:: Constructing a list.
* nthcdr:: Calling @code{cdr} repeatedly.
@ -7678,7 +7678,7 @@ The first part of the code looks like this:
@end smallexample
@noindent
@code{char-table-p} is an hitherto unseen function. It determines
@code{char-table-p} is a hitherto unseen function. It determines
whether its argument is a character table. When it is, it sets the
character passed to @code{zap-to-char} to one of them, if that
character exists, or to the character itself. (This becomes important

View file

@ -1048,7 +1048,7 @@ commands operate as if that portion did not exist, allowing a single
@code{next-line} command to skip any number of hidden lines.
However, character movement commands (such as @code{forward-char}) do
not skip the hidden portion, and it is possible (if tricky) to insert
or delete text in an hidden portion.
or delete text in a hidden portion.
In the examples below, we show the @emph{display appearance} of the
buffer @code{foo}, which changes with the value of

View file

@ -11,7 +11,7 @@
by concept. The list includes each symbol's message and a cross reference
to a description of how the error can occur.
Each error symbol has an set of parent error conditions that is a
Each error symbol has a set of parent error conditions that is a
list of symbols. Normally this list includes the error symbol itself
and the symbol @code{error}. Occasionally it includes additional
symbols, which are intermediate classifications, narrower than

View file

@ -214,7 +214,7 @@ have been omitted.)
@cindex skeleton language
@findex skeleton-insert
Skeletons are an shorthand extension to the Lisp language, where various
Skeletons are a shorthand extension to the Lisp language, where various
atoms directly perform either actions on the current buffer or rudimentary
flow control mechanisms. Skeletons are interpreted by the function
@code{skeleton-insert}.

View file

@ -5136,7 +5136,7 @@ that Org can parse this line correctly:
In this example, @samp{GTD} is the @emph{group tag} and it is related to two
other tags: @samp{Control}, @samp{Persp}. Defining @samp{Control} and
@samp{Persp} as group tags creates an hierarchy of tags:
@samp{Persp} as group tags creates a hierarchy of tags:
@example
#+TAGS: [ Control : Context Task ]
@ -11180,7 +11180,7 @@ Org exports text in this block only when using ASCII back-end.
@cindex horizontal rules, in ASCII export
ASCII back-end recognizes only one attribute, @code{:width}, which specifies
the width of an horizontal rule in number of characters. The keyword and
the width of a horizontal rule in number of characters. The keyword and
syntax for specifying widths is:
@example

View file

@ -4330,7 +4330,7 @@ Same as @code{tabstop}, but affects all buffers.
@cindex auto fill
@cindex word wrap
wrapmargin: In append mode Vi automatically
puts a <lf> whenever there is a <sp> or <ht>
puts an <lf> whenever there is an <sp> or <ht>
within <wm> columns from the right margin.
@item wrapscan
@itemx ws

View file

@ -1937,7 +1937,7 @@ rule:
@end example
Set the @code{reparse-symbol} property of the expanded tag to
@samp{rule}. A important consequence is that:
@samp{rule}. An important consequence is that:
@strong{Every nonterminal having any rule that calls @code{EXPANDTAG}
in a semantic action, should be declared as a start symbol!}