From: Alejandro Colomar <alx@kernel.org>
Date: Sun, 17 Nov 2024 11:45:14 +0000 (+0100)
Subject: man/: tfix
X-Git-Tag: man-pages-6.10~99
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=a7d7ce179d6ea6d310789395f3e4ffc8a85cb47a;p=thirdparty%2Fman-pages.git

man/: tfix

Reported-by: Helge Kreutzmann <debian@helgefjell.de>
Signed-off-by: Alejandro Colomar <alx@kernel.org>
---

diff --git a/man/man3/arc4random.3 b/man/man3/arc4random.3
index d3180442f..3bb3916ce 100644
--- a/man/man3/arc4random.3
+++ b/man/man3/arc4random.3
@@ -101,7 +101,7 @@ less than
 .IR upper_bound .
 In some cases,
 such as accessing an array,
-using that value could result in Undefined Behavior.
+using that value could result in undefined behavior.
 .SH SEE ALSO
 .BR getrandom (3),
 .BR rand (3),
diff --git a/man/man3/setjmp.3 b/man/man3/setjmp.3
index 4aca8df4a..762a89c82 100644
--- a/man/man3/setjmp.3
+++ b/man/man3/setjmp.3
@@ -272,7 +272,7 @@ calls may not even be in the same source code module.
 In summary, nonlocal gotos can make programs harder to understand
 and maintain, and an alternative should be used if possible.
 .\"
-.SS Undefined Behavior
+.SS Undefined behavior
 If the function which called
 .BR setjmp ()
 returns before
diff --git a/man/man3/sscanf.3 b/man/man3/sscanf.3
index 3fe10739b..8eec9c20a 100644
--- a/man/man3/sscanf.3
+++ b/man/man3/sscanf.3
@@ -635,7 +635,7 @@ floating-point conversion specifier (and is unaffected by
 etc.).
 .SH BUGS
 .SS Numeric conversion specifiers
-Use of the numeric conversion specifiers produces Undefined Behavior
+Use of the numeric conversion specifiers produces undefined behavior
 for invalid input.
 See
 .UR https://port70.net/\:%7Ensz/\:c/\:c11/\:n1570.html\:#7.21.6.2p10
diff --git a/man/man3type/sockaddr.3type b/man/man3type/sockaddr.3type
index 10659ca45..674c1450d 100644
--- a/man/man3type/sockaddr.3type
+++ b/man/man3type/sockaddr.3type
@@ -121,7 +121,7 @@ See also
 These structures were invented before modern ISO C strict-aliasing rules.
 If aliasing rules are applied strictly,
 these structures would be extremely difficult to use
-without invoking Undefined Behavior.
+without invoking undefined behavior.
 POSIX Issue 8 will fix this by requiring that implementations
 make sure that these structures
 can be safely used as they were designed.