zap some wacky Eo/Ec stuff, and start sentences on new lines; ok schwarze

1 files changed, 27 insertions, 33 deletions

diff --git a/lib/libc/sys/ptrace.2 b/lib/libc/sys/ptrace.2
index 598f91a098c..3af57a3967e 100644
--- a/lib/libc/sys/ptrace.2
+++ b/lib/libc/sys/ptrace.2
@@ -1,8 +1,8 @@
-.\"	$OpenBSD: ptrace.2,v 1.29 2014/03/18 22:36:30 miod Exp $
+.\"	$OpenBSD: ptrace.2,v 1.30 2014/11/16 18:52:27 jmc Exp $
 .\"	$NetBSD: ptrace.2,v 1.3 1996/02/23 01:39:41 jtc Exp $
 .\"
 .\" This file is in the public domain.
-.Dd $Mdocdate: March 18 2014 $
+.Dd $Mdocdate: November 16 2014 $
 .Dt PTRACE 2
 .Os
 .Sh NAME
@@ -60,9 +60,7 @@ All the other arguments are ignored.
 (If the parent process does not expect to trace the child, it will
 probably be rather confused by the results; once the traced process stops,
 it cannot be made to continue except via
-.Eo \&
-.Fn ptrace
-.Ec \&.)
+.Fn ptrace . )
 When a process has used this request and calls
 .Xr execve 2
 or any of the routines built on it
@@ -95,9 +93,7 @@ argument specifies the address (in the traced process' virtual address
 space) at which the read is to be done.
 This address does not have to meet any alignment constraints.
 The value read is returned as the return value from
-.Eo \&
-.Fn ptrace
-.Ec .
+.Fn ptrace .
 .It Dv PT_WRITE_I , Dv PT_WRITE_D
 These requests parallel
 .Dv PT_READ_I
@@ -110,15 +106,14 @@ argument supplies the value to be written.
 .\" .It Dv PT_READ_U
 .\" This request reads an
 .\" .Li int
-.\" from the traced process' user structure.  The
+.\" from the traced process' user structure.
+.\" The
 .\" .Fa addr
 .\" argument specifies the location of the int relative to the base of the
 .\" user structure; it will usually be an integer value cast to
 .\" .Li caddr_t
 .\" either explicitly or via the presence of a prototype for
-.\" .Eo \&
-.\" .Fn ptrace
-.\" .Ec .
+.\" .Fn ptrace .
 .\" Unlike
 .\" .Dv PT_READ_I
 .\" and
@@ -126,10 +121,9 @@ argument supplies the value to be written.
 .\" .Fa addr
 .\" must be aligned on an
 .\" .Li int
-.\" boundary.  The value read is returned as the return value from
-.\" .Eo \&
-.\" .Fn ptrace
-.\" .Ec .
+.\" boundary.
+.\" The value read is returned as the return value from
+.\" .Fn ptrace .
 .\" .It Dv PT_WRITE_U
 .\" This request writes an
 .\" .Li int
@@ -330,17 +324,19 @@ pointed to by
 .\" This request is like
 .\" .Dv PT_CONTINUE
 .\" except that the process will stop next time it executes any system
-.\" call.  Information about the system call can be examined with
+.\" call.
+.\" Information about the system call can be examined with
 .\" .Dv PT_READ_U
 .\" and potentially modified with
 .\" .Dv PT_WRITE_U
 .\" through the
 .\" .Li u_kproc.kp_proc.p_md
-.\" element of the user structure (see below).  If the process is continued
-.\" with another
+.\" element of the user structure (see below).
+.\" If the process is continued with another
 .\" .Dv PT_SYSCALL
 .\" request, it will stop again on exit from the syscall, at which point
-.\" the return values can be examined and potentially changed.  The
+.\" the return values can be examined and potentially changed.
+.\" The
 .\" .Li u_kproc.kp_proc.p_md
 .\" element is of type
 .\" .Dq Li struct mdproc ,
@@ -368,7 +364,8 @@ pointed to by
 .\" .Li syscall_nargs
 .\" holds the number of arguments it expects, and
 .\" .Li syscall_args
-.\" holds the arguments themselves.  (Only the first
+.\" holds the arguments themselves.
+.\" (Only the first
 .\" .Li syscall_nargs
 .\" elements of
 .\" .Li syscall_args
@@ -376,9 +373,7 @@ pointed to by
 .\" syscall,
 .\" .Li syscall_num
 .\" is
-.\" .Eo \&
-.\" .Li -1
-.\" .Ec ,
+.\" .Li -1 ,
 .\" .Li syscall_err
 .\" holds the error number
 .\" .Po
@@ -387,9 +382,11 @@ pointed to by
 .\" .Pc ,
 .\" or 0 if no error occurred, and
 .\" .Li syscall_rv
-.\" holds the return values.  (If the syscall returns only one value, only
+.\" holds the return values.
+.\" (If the syscall returns only one value, only
 .\" .Li syscall_rv[0]
-.\" is useful.)  The tracing process can modify any of these with
+.\" is useful.)
+.\" The tracing process can modify any of these with
 .\" .Dv PT_WRITE_U ;
 .\" only some modifications are useful.
 .\" .Pp
@@ -400,16 +397,15 @@ pointed to by
 .\" in
 .\" .Li syscall_args
 .\" appropriately for the new call, but there is no need to modify
-.\" .Eo \&
-.\" .Li syscall_nargs
-.\" .Ec ).
+.\" .Li syscall_nargs ) .
 .\" If the new syscall number is 0, no syscall is actually performed;
 .\" instead,
 .\" .Li syscall_err
 .\" and
 .\" .Li syscall_rv
 .\" are passed back to the traced process directly (and therefore should be
-.\" filled in).  If the syscall number is otherwise out of range, a dummy
+.\" filled in).
+.\" If the syscall number is otherwise out of range, a dummy
 .\" syscall which simply produces an
 .\" .Er ENOSYS
 .\" error is effectively performed.
@@ -577,9 +573,7 @@ and
 to modify the PC, passing
 .Li (caddr_t)1
 to
-.Eo \&
-.Fn ptrace
-.Ec ,
+.Fn ptrace ,
 should be able to sidestep this.
 .\" .Pp
 .\" When using