6 files changed, 26 insertions, 26 deletions
diff --git a/man2/adjtimex.2 b/man2/adjtimex.2
index 02a1d19bbc..7915d24a7e 100644
--- a/man2/adjtimex.2
+++ b/man2/adjtimex.2
@@ -44,7 +44,7 @@ structure, updates kernel parameters from field values,
 and returns the same structure with current kernel values.
 This structure is declared as follows:
 .PP
-.RS 4
+.in +4n
 .nf
 struct timex {
     int modes;           /* mode selector */
@@ -61,7 +61,7 @@ struct timex {
     long tick;           /* usecs between clock ticks */
 };
 .fi
-.RE
+.in
 .PP
 The
 .I modes
@@ -70,7 +70,7 @@ It may contain a
 .RI bitwise- or
 combination of zero or more of the following bits:
 .PP
-.RS 4
+.in +4n
 .nf
 #define ADJ_OFFSET            0x0001 /* time offset */
 #define ADJ_FREQUENCY         0x0002 /* frequency offset */
@@ -81,7 +81,7 @@ combination of zero or more of the following bits:
 #define ADJ_TICK              0x4000 /* tick value */
 #define ADJ_OFFSET_SINGLESHOT 0x8001 /* old-fashioned adjtime() */
 .fi
-.RE
+.in
 .PP
 Ordinary users are restricted to a zero value for
 .IR mode .
@@ -93,7 +93,7 @@ On success,
 .BR adjtimex ()
 returns the clock state:
 .PP
-.RS 4
+.in +4n
 .nf
 #define TIME_OK   0 /* clock synchronized */
 #define TIME_INS  1 /* insert leap second */
@@ -102,7 +102,7 @@ returns the clock state:
 #define TIME_WAIT 4 /* leap second has occurred */
 #define TIME_BAD  5 /* clock not synchronized */
 .fi
-.RE
+.in
 .PP
 On failure,
 .BR adjtimex ()
diff --git a/man2/sigaction.2 b/man2/sigaction.2
index cc09395073..41dfaba5f0 100644
--- a/man2/sigaction.2
+++ b/man2/sigaction.2
@@ -77,7 +77,7 @@ The
 .I sigaction
 structure is defined as something like
 .sp
-.RS 4
+.in +4n
 .nf
 struct sigaction {
     void     (*sa_handler)(int);
@@ -87,7 +87,7 @@ struct sigaction {
     void     (*sa_restorer)(void);
 }
 .fi
-.RE
+.in
 .PP
 On some architectures a union is involved: do not assign to both
 .I sa_handler
@@ -140,7 +140,7 @@ flag is used.
 specifies a set of flags which modify the behavior of the signal handling
 process.
 It is formed by the bitwise OR of zero or more of the following:
-.RS
+.RS 4
 .TP
 .B SA_NOCLDSTOP
 If
@@ -206,7 +206,7 @@ parameter to
 .I sa_sigaction
 is a struct with the following elements
 .sp
-.RS 4
+.in +4n
 .nf
 siginfo_t {
 .\" FIXME si_tid and si_overrun are not documented.
@@ -227,7 +227,7 @@ siginfo_t {
     int      si_fd;       /* File descriptor */
 }
 .fi
-.RE
+.in
 
 .IR si_signo ", " si_errno " and " si_code
 are defined for all signals.
diff --git a/man2/sigaltstack.2 b/man2/sigaltstack.2
index 92672fa828..895b9430bd 100644
--- a/man2/sigaltstack.2
+++ b/man2/sigaltstack.2
@@ -75,7 +75,7 @@ If we are interested in performing just one
 of these tasks then the other argument can be specified as NULL.
 Each of these arguments is a structure of the following type:
 .sp
-.RS 4
+.in +4n
 .nf
 typedef struct {
     void  *ss_sp;     /* Base address of stack */
@@ -83,7 +83,7 @@ typedef struct {
     size_t ss_size;   /* Number of bytes in stack */
 } stack_t;
 .fi
-.RE
+.in
 
 To establish a new alternate signal stack,
 \fIss.ss_flags\fP is set to zero, and \fIss.ss_sp\fP and
@@ -202,7 +202,7 @@ had to know the direction of stack growth.
 The following code segment demonstrates the use of
 .BR sigaltstack ():
 
-.RS
+.in +4n
 .nf
 stack_t ss;
 
@@ -214,7 +214,7 @@ ss.ss_flags = 0;
 if (sigaltstack(&ss, NULL) == \-1)
     /* Handle error */;
 .fi
-.RE
+.in
 .SH "SEE ALSO"
 .BR execve (2),
 .BR setrlimit (2),
diff --git a/man2/stat.2 b/man2/stat.2
index 63ee87c7e1..42b713617a 100644
--- a/man2/stat.2
+++ b/man2/stat.2
@@ -96,7 +96,7 @@ All of these system calls return a
 .I stat
 structure, which contains the following fields:
 .PP
-.RS 4
+.in +4n
 .nf
 struct stat {
     dev_t     st_dev;     /* ID of device containing file */
@@ -114,7 +114,7 @@ struct stat {
     time_t    st_ctime;   /* time of last status change */
 };
 .fi
-.RE
+.in
 .PP
 The
 .I st_dev
@@ -194,7 +194,7 @@ is changed by writing or by setting inode information
 The following POSIX macros are defined to check the file type using the
 .I st_mode
 field:
-.RS
+.RS 4
 .TP 1.2i
 .BR S_ISREG (m)
 is it a regular file?
@@ -221,7 +221,7 @@ socket? (Not in POSIX.1-1996.)
 The following flags are defined for the
 .I st_mode
 field:
-.RS 4
+.in +4n
 .TS
 lB l l.
 S_IFMT	0170000	bit mask for the file type bit fields
@@ -248,7 +248,7 @@ S_IROTH	00004	others have read permission
 S_IWOTH	00002	others have write permission
 S_IXOTH	00001	others have execute permission
 .TE
-.RE
+.in
 .P
 The set-group-ID bit
 .RB ( S_ISGID )
diff --git a/man2/statfs.2 b/man2/statfs.2
index 591d634cd4..0b795d6b19 100644
--- a/man2/statfs.2
+++ b/man2/statfs.2
@@ -43,7 +43,7 @@ is a pointer to a
 .I statfs
 structure defined approximately as follows:
 
-.RS 4
+.in +4n
 .nf
 struct statfs {
    long    f_type;     /* type of filesystem (see below) */
@@ -104,7 +104,7 @@ File system types:
    XFS_SUPER_MAGIC       0x58465342
    _XIAFS_SUPER_MAGIC    0x012FD16D
 .fi
-.RE
+.in
 .PP
 Nobody knows what
 .I f_fsid
diff --git a/man2/utime.2 b/man2/utime.2
index 2963e6245d..413a6a24c8 100644
--- a/man2/utime.2
+++ b/man2/utime.2
@@ -70,14 +70,14 @@ The
 .I utimbuf
 structure is:
 
-.RS 4
+.in +4n
 .nf
 struct utimbuf {
     time_t actime;       /* access time */
     time_t modtime;      /* modification time */
 };
 .fi
-.RE
+.in
 
 The function
 .BR utime ()
@@ -92,14 +92,14 @@ The
 .I timeval
 structure is:
 
-.RS 4
+.in +4n
 .nf
 struct timeval {
     long tv_sec;        /* seconds */
     long tv_usec;       /* microseconds */
 };
 .fi
-.RE
+.in
 .PP
 .IR times [0]
 specifies the new access time, and