A few more caps and apostrophe fixes

newtzset.3

@@ -331,7 +331,7 @@ from the rest of the specification.
 .br
 /usr/share/zoneinfo/localtime	local timezone file
 .br
-/usr/share/zoneinfo/posixrules	used with POSIX-style TZ's
+/usr/share/zoneinfo/posixrules	used with POSIX-style TZ
 .br
 /usr/share/zoneinfo/GMT	for UTC leap seconds
 .sp

time2posix.3

@@ -1,4 +1,4 @@
-.TH TIME2POSIX 3
+.TH time2posix 3
 .SH NAME
 time2posix, posix2time \- convert seconds since the Epoch
 .SH SYNOPSIS
@@ -58,7 +58,7 @@ expression for directly computing a time_t value from a given date/time,
 and the same relationship is assumed by some
 (usually older)
 applications.
-Any programs creating/dissecting time_t's
+Any programs creating/dissecting time_t values
 using such a relationship will typically not handle intervals
 over leap seconds correctly.
 .PP
@@ -93,7 +93,7 @@ Both of these are good indicators of the inferiority of the
 POSIX representation.
 .PP
 The following table summarizes the relationship between a time
-T and it's conversion to,
+T and its conversion to,
 and back from,
 the POSIX representation over the leap second inserted at the end of June,
 1993.
@@ -117,8 +117,8 @@ DATE	TIME	T	X=time2posix(T)	posix2time(X)
 .fi
 .PP
 If leap-second support is not enabled,
-local time_t's and
-POSIX time_t's are equivalent,
+local time_t and
+POSIX time_t values are equivalent,
 and both
 .B time2posix
 and