Minor wording fixes

man2/ptrace.2

@@ -390,7 +390,7 @@ The layout of the contents of memory and the USER area are quite OS- and
 architecture-specific.
 .LP
 The size of a "word" is determined by the OS variant
-(e.g., for 32-bit Linux it's 32 bits, etc.).
+(e.g., for 32-bit Linux it is 32 bits, etc.).
 .LP
 Tracing causes a few subtle differences in the semantics of
 traced processes.

man3/ecvt.3

@@ -55,8 +55,8 @@ is stored in *\fIdecpt\fP.
 A negative value for *\fIdecpt\fP means that
 the decimal point is to the left of the start of the string.
 If the sign of
-\fInumber\fP is negative, *\fIsign\fP is set to a non-zero value, otherwise
-it's set to 0.
+\fInumber\fP is negative, *\fIsign\fP is set to a non-zero value,
+otherwise it is set to 0.
 If
 .I number
 is zero, it is unspecified whether *\fIdecpt\fP is 0 or 1.

man3/logb.3

@@ -45,7 +45,7 @@ is two,
 .BI logb( x )
 is equal to
 .BI floor(log2( x ))\fR,
-except it's probably faster.
+except that it is probably faster.
 .LP
 If
 .I x

man4/rtc.4

@@ -62,12 +62,12 @@ The system clock reports seconds and microseconds since a start point,
 defined to be the POSIX Epoch: Jan 1, 1970, 0:00 UTC.
 (One common implementation counts timer interrupts, once
 per "jiffy", at a frequency of 100, 250, or 1000 Hz.)
-That is, it's supposed to report wall clock time, which RTCs also do.
+That is, it is supposed to report wall clock time, which RTCs also do.
 
 A key difference between an RTC and the system clock is that RTCs
 run even when the system is in a low power state (including "off"),
 and the system clock can't.
-Until it's initialized, the system clock can only report time since
+Until it is initialized, the system clock can only report time since
 system boot ... not since the POSIX Epoch.
 So at boot time, and after resuming from a system low power state, the
 system clock will often be set to the current wall clock time using an RTC.

man4/wavelan.4

@@ -139,7 +139,7 @@ and standard deviation of the signal level.
 This driver will fail to detect some
 .B non NCR/ATT&T/Lucent
 Wavelan cards.
-If it's your case, you must look in the source code on
+If this happens for you, you must look in the source code on
 how to add your card to the detection routine.
 .PP
 Some of the mentioned features are optional.