From: Rical Jasan <ricaljasan@pacific.net>
Date: Thu, 6 Oct 2016 06:48:05 +0000 (+0530)
Subject: Manual typos: Signal Handling
X-Git-Tag: glibc-2.25~453
X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=16c7d1ec26ecf4cbd3a128a23cf2a8ab495a89b8;p=thirdparty%2Fglibc.git

Manual typos: Signal Handling

2016-05-06  Rical Jasan  <ricaljasan@pacific.net>

	* manual/signal.texi: Fix typos in the manual.
---

diff --git a/ChangeLog b/ChangeLog
index a79d684bc62..d155ba2c017 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,7 @@
 2016-10-06  Rical Jasan  <ricaljasan@pacific.net>
 
+	* manual/signal.texi: Fix typos in the manual.
+
 	* manual/setjmp.texi: Fix typos in the manual.
 
 	* manual/resource.texi: Fix typos in the manual.
diff --git a/manual/signal.texi b/manual/signal.texi
index 77f3d7cfda6..79e190dc152 100644
--- a/manual/signal.texi
+++ b/manual/signal.texi
@@ -1207,7 +1207,7 @@ the signal.  These are described in more detail in @ref{Flags for Sigaction}.
 @safety{@prelim{}@mtsafe{}@assafe{}@acsafe{}}
 The @var{action} argument is used to set up a new action for the signal
 @var{signum}, while the @var{old-action} argument is used to return
-information about the action previously associated with this symbol.
+information about the action previously associated with this signal.
 (In other words, @var{old-action} has the same purpose as the
 @code{signal} function's return value---you can check to see what the
 old action in effect for the signal was, and restore it later if you
@@ -2092,7 +2092,7 @@ it can also handle a signal in the middle of clearing the flag.  (This
 is an example of the sort of reasoning you need to do to figure out
 whether non-atomic usage is safe.)
 
-Sometimes you can insure uninterrupted access to one object by
+Sometimes you can ensure uninterrupted access to one object by
 protecting its use with another object, perhaps one whose type
 guarantees atomicity.  @xref{Merged Signals}, for an example.
 
@@ -3371,7 +3371,7 @@ signals.  The return value is the previous set of blocked signals.
 @c The exception are BSD systems other than 4.4, where it is a syscall.
 @c sigsetmask @asulock/hurd @aculock/hurd
 @c  sigprocmask(SIG_SETMASK) dup @asulock/hurd @aculock/hurd [no @mtasurace:sigprocmask/bsd(SIG_UNBLOCK)]
-This function equivalent to @code{sigprocmask} (@pxref{Process
+This function is equivalent to @code{sigprocmask} (@pxref{Process
 Signal Mask}) with a @var{how} argument of @code{SIG_SETMASK}: it sets
 the calling process's signal mask to @var{mask}.  The return value is
 the previous set of blocked signals.