1 files changed, 20 insertions, 21 deletions
diff --git a/man3/lseek64.3 b/man3/lseek64.3
index aee84ed..9e2801f 100644
--- a/man3/lseek64.3
+++ b/man3/lseek64.3
@@ -4,7 +4,7 @@
 .\"
 .\" SPDX-License-Identifier: Linux-man-pages-copyleft
 .\"
-.TH lseek64 3 2023-07-20 "Linux man-pages 6.05.01"
+.TH lseek64 3 2023-10-31 "Linux man-pages 6.7"
 .SH NAME
 lseek64 \- reposition 64-bit read/write file offset
 .SH LIBRARY
@@ -15,7 +15,7 @@ Standard C library
 .BR "#define _LARGEFILE64_SOURCE" "     /* See feature_test_macros(7) */"
 .B #include <sys/types.h>
 .B #include <unistd.h>
-.PP
+.P
 .BI "off64_t lseek64(int " fd ", off64_t " offset ", int " whence );
 .fi
 .SH DESCRIPTION
@@ -35,10 +35,10 @@ has the value
 or
 .BR SEEK_END ,
 respectively.
-.PP
+.P
 For more details, return value, and errors, see
 .BR lseek (2).
-.PP
+.P
 Four interfaces are available:
 .BR lseek (),
 .BR lseek64 (),
@@ -51,36 +51,36 @@ and
 .\"
 .SS lseek()
 Prototype:
-.PP
+.P
 .in +4n
 .EX
 .BI "off_t lseek(int " fd ", off_t " offset ", int " whence );
 .EE
 .in
-.PP
+.P
 The C library's
 .BR lseek ()
 wrapper function uses the type
 .IR off_t .
 This is a 32-bit signed type on 32-bit architectures, unless one
 compiles with
-.PP
+.P
 .in +4n
 .EX
 #define _FILE_OFFSET_BITS 64
 .EE
 .in
-.PP
+.P
 in which case it is a 64-bit signed type.
 .SS lseek64()
 Prototype:
-.PP
+.P
 .in +4n
 .EX
 .BI "off64_t lseek64(int " fd ", off64_t " offset ", int " whence );
 .EE
 .in
-.PP
+.P
 The
 .BR lseek64 ()
 library function uses a 64-bit type even when
@@ -89,13 +89,13 @@ is a 32-bit type.
 Its prototype (and the type
 .IR off64_t )
 is available only when one compiles with
-.PP
+.P
 .in +4n
 .EX
 #define _LARGEFILE64_SOURCE
 .EE
 .in
-.PP
+.P
 The function
 .BR lseek64 ()
 .\" in glibc 2.0.94, not in glibc 2.0.6
@@ -103,13 +103,13 @@ is available since glibc 2.1.
 .\"
 .SS llseek()
 Prototype:
-.PP
+.P
 .in +4n
 .EX
 .BI "loff_t llseek(int " fd ", loff_t " offset ", int " whence );
 .EE
 .in
-.PP
+.P
 The type
 .I loff_t
 is a 64-bit signed type.
@@ -122,14 +122,14 @@ the above prototype, or something equivalent, to their own source.
 When users complained about data loss caused by a miscompilation of
 .BR e2fsck (8),
 glibc 2.1.3 added the link-time warning
-.PP
+.P
 .in +4n
 "the \`llseek\' function may be dangerous; use \`lseek64\' instead."
 .in
-.PP
+.P
 This makes this function unusable if one desires a warning-free
 compilation.
-.PP
+.P
 Since glibc 2.28,
 .\" glibc commit 5c5c0dd747070db624c8e2c43691cec854f114ef
 this function symbol is no longer available to newly linked applications.
@@ -139,17 +139,17 @@ On 32-bit architectures,
 this is the system call that is used (by the C library wrapper functions)
 to implement all of the above functions.
 The prototype is:
-.PP
+.P
 .in +4n
 .EX
 .BI "int _llseek(int " fd ", off_t " offset_hi ", off_t " offset_lo ,
 .BI "            loff_t *" result ", int " whence );
 .EE
 .in
-.PP
+.P
 For more details, see
 .BR llseek (2).
-.PP
+.P
 64-bit systems don't need an
 .BR _llseek ()
 system call.
@@ -182,7 +182,6 @@ T{
 .BR lseek64 ()
 T}	Thread safety	MT-Safe
 .TE
-.sp 1
 .SH NOTES
 .BR lseek64 ()
 is one of the functions that was specified in the Large File Summit (LFS)