From 4cc91169d0c1ad3fe49d7363ec943d6f1c7d12ba Mon Sep 17 00:00:00 2001 From: Alejandro Colomar Date: Sun, 9 May 2021 23:39:07 +0200 Subject: [PATCH] sched_get_priority_max.2, open_memstream.3: tfix Signed-off-by: Alejandro Colomar Signed-off-by: Michael Kerrisk --- man2/sched_get_priority_max.2 | 2 +- man3/open_memstream.3 | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/man2/sched_get_priority_max.2 b/man2/sched_get_priority_max.2 index 8a857f6e7..2afd88681 100644 --- a/man2/sched_get_priority_max.2 +++ b/man2/sched_get_priority_max.2 @@ -80,7 +80,7 @@ thus it is a good idea for portable applications to use a virtual priority range and map it to the interval given by .BR sched_get_priority_max () and -.BR sched_get_priority_min +.BR sched_get_priority_min () POSIX.1 requires .\" POSIX.1-2001, POSIX.1-2008 (XBD 2.8.4) a spread of at least 32 between the maximum and the minimum values for diff --git a/man3/open_memstream.3 b/man3/open_memstream.3 index ba6cbfa75..ea1489cb8 100644 --- a/man3/open_memstream.3 +++ b/man3/open_memstream.3 @@ -110,7 +110,7 @@ l l l. Interface Attribute Value T{ .BR open_memstream (), -.BR open_wmemstream +.BR open_wmemstream () T} Thread safety MT-Safe .TE .hy