fix some spacing issues;

2 files changed, 7 insertions, 7 deletions

diff --git a/share/man/man4/man4.socppc/tsec.4 b/share/man/man4/man4.socppc/tsec.4
index e8ca6ad5028..b982912349e 100644
--- a/share/man/man4/man4.socppc/tsec.4
+++ b/share/man/man4/man4.socppc/tsec.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: tsec.4,v 1.2 2008/05/20 11:39:12 jmc Exp $
+.\"	$OpenBSD: tsec.4,v 1.3 2008/06/03 19:51:02 jmc Exp $
 .\"
 .\" Copyright (c) 2008 Mark Kettenis <kettenis@openbsd.org>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: May 20 2008 $
+.Dd $Mdocdate: June 3 2008 $
 .Dt TSEC 4 socppc
 .Os
 .Sh NAME
@@ -45,11 +45,11 @@ Attempt to autoselect the media type (default)
 Use 1000baseT on copper, full duplex
 .It media 1000baseT Op mediaopt half-duplex
 Use 1000baseT on copper, half duplex
-.It media 1000baseSX  mediaopt full-duplex
+.It media 1000baseSX mediaopt full-duplex
 Use 1000baseSX on fiber, full duplex
 .It media 1000baseSX Op mediaopt half-duplex
 Use 1000baseSX on fiber, half duplex
-.It media 100baseTX  mediaopt full-duplex
+.It media 100baseTX mediaopt full-duplex
 Use 100baseTX, full duplex
 .It media 100baseTX Op mediaopt half-duplex
 Use 100baseTX, half duplex
diff --git a/share/man/man4/pfsync.4 b/share/man/man4/pfsync.4
index 23503e68a6f..6387e682adb 100644
--- a/share/man/man4/pfsync.4
+++ b/share/man/man4/pfsync.4
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: pfsync.4,v 1.26 2007/09/20 20:50:07 mpf Exp $
+.\"	$OpenBSD: pfsync.4,v 1.27 2008/06/03 19:51:02 jmc Exp $
 .\"
 .\" Copyright (c) 2002 Michael Shalayeff
 .\" Copyright (c) 2003-2004 Ryan McBride
@@ -24,7 +24,7 @@
 .\" (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
 .\" THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 .\"
-.Dd $Mdocdate: September 20 2007 $
+.Dd $Mdocdate: June 3 2008 $
 .Dt PFSYNC 4
 .Os
 .Sh NAME
@@ -121,7 +121,7 @@ e.g.:
 It is important that the pfsync traffic be well secured
 as there is no authentication on the protocol and it would
 be trivial to spoof packets which create states, bypassing the pf ruleset.
-Either run the pfsync protocol on a trusted network \- ideally  a network
+Either run the pfsync protocol on a trusted network \- ideally a network
 dedicated to pfsync messages such as a crossover cable between two firewalls,
 or specify a peer address and protect the traffic with
 .Xr ipsec 4 .