From: "Štěpán Němec" <stepnem@gmail.com>
To: binutils@sourceware.org
Subject: [PATCH] gas: Fix some typos in the Info manual
Date: Mon, 8 Aug 2022 19:38:24 +0200 [thread overview]
Message-ID: <20220808173824.2233856-1-stepnem@gmail.com> (raw)
* gas/doc/as.texi: Fix some typos.
---
gas/doc/as.texi | 23 ++++++++++++-----------
1 file changed, 12 insertions(+), 11 deletions(-)
diff --git a/gas/doc/as.texi b/gas/doc/as.texi
index 09b0ca5f565c..e915893da869 100644
--- a/gas/doc/as.texi
+++ b/gas/doc/as.texi
@@ -2885,9 +2885,9 @@
If the first line of an input file is @code{#NO_APP} or if you use the
@samp{-f} option, whitespace and comments are not removed from the input file.
Within an input file, you can ask for whitespace and comment removal in
-specific portions of the by putting a line that says @code{#APP} before the
+specific portions of the file by putting a line that says @code{#APP} before the
text that may contain whitespace or comments, and putting a line that says
-@code{#NO_APP} after this text. This feature is mainly intend to support
+@code{#NO_APP} after this text. This feature is mainly intended to support
@code{asm} statements in compilers whose output is otherwise free of comments
and whitespace.
@@ -2923,12 +2923,13 @@
@cindex line comment character
Anything from a @dfn{line comment} character up to the next newline is
considered a comment and is ignored. The line comment character is target
-specific, and some targets multiple comment characters. Some targets also have
-line comment characters that only work if they are the first character on a
-line. Some targets use a sequence of two characters to introduce a line
-comment. Some targets can also change their line comment characters depending
-upon command-line options that have been used. For more details see the
-@emph{Syntax} section in the documentation for individual targets.
+specific, and some targets support multiple comment characters. Some targets
+also have line comment characters that only work if they are the first
+character on a line. Some targets use a sequence of two characters to
+introduce a line comment. Some targets can also change their line comment
+characters depending upon command-line options that have been used. For more
+details see the @emph{Syntax} section in the documentation for individual
+targets.
If the line comment character is the hash sign (@samp{#}) then it still has the
special ability to enable and disable preprocessing (@pxref{Preprocessing}) and
@@ -3649,7 +3650,7 @@
@cindex expr (internal section)
@item expr section
-The assembler stores complex expression internally as combinations of
+The assembler stores complex expressions internally as combinations of
symbols. When it needs to represent an expression as a symbol, it puts
it in the expr section.
@c FIXME item debug
@@ -4356,7 +4357,7 @@
@dfn{Is Less Than Or Equal To}
The comparison operators can be used as infix operators. A true result has a
-value of -1 whereas a false result has a value of 0. Note, these operators
+value of -1 whereas a false result has a value of 0. Note, these operators
perform signed comparisons.
@end table
@@ -4371,7 +4372,7 @@
These two logical operations can be used to combine the results of sub
expressions. Note, unlike the comparison operators a true result returns a
-value of 1 but a false results does still return 0. Also note that the logical
+value of 1 but a false result does still return 0. Also note that the logical
or operator has a slightly lower precedence than logical and.
@end table
base-commit: e441b55e94c905c6ee4417be3e5d88021d9c5aa6
--
2.37.1
next reply other threads:[~2022-08-08 17:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-08 17:38 Štěpán Němec [this message]
2022-08-09 14:39 ` Nick Clifton
2022-08-09 15:06 ` Štěpán Němec
2022-08-09 15:33 ` Nick Clifton
2022-08-09 21:36 ` Štěpán Němec
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220808173824.2233856-1-stepnem@gmail.com \
--to=stepnem@gmail.com \
--cc=binutils@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).