From seki@localhost.seki.net Wed Dec  1 08:11:36 1999
Return-Path: <seki@localhost.seki.net>
Received: from localhost.seki.net (UTUcd-02p36.ppp.odn.ad.jp [210.228.199.36])
	by hub.freebsd.org (Postfix) with ESMTP id 84D1515191
	for <FreeBSD-gnats-submit@freebsd.org>; Wed,  1 Dec 1999 08:11:21 -0800 (PST)
	(envelope-from seki@localhost.seki.net)
Received: (from seki@localhost)
	by localhost.seki.net (8.9.3/8.9.2) id BAA50957;
	Thu, 2 Dec 1999 01:11:00 +0900 (JST)
	(envelope-from seki)
Message-Id: <199912011611.BAA50957@localhost.seki.net>
Date: Thu, 2 Dec 1999 01:11:00 +0900 (JST)
From: seki@is.utsunomiya-u.ac.jp
Sender: seki@localhost.seki.net
Reply-To: seki@is.utsunomiya-u.ac.jp
To: FreeBSD-gnats-submit@freebsd.org
Subject: simple typo in manual page le.4
X-Send-Pr-Version: 3.2

>Number:         15207
>Category:       docs
>Synopsis:       There is a simple typo in manual pages le.4.
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    freebsd-doc
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          doc-bug
>Submitter-Id:   current-users
>Arrival-Date:   Wed Dec  1 08:20:01 PST 1999
>Closed-Date:    Mon Dec 6 19:19:26 PST 1999
>Last-Modified:  Mon Dec  6 19:20:23 PST 1999
>Originator:     Kazuo Seki
>Release:        FreeBSD 3.3-STABLE i386
>Organization:
Utsunomiya University
>Environment:
FreeBSD kss1.seki.net 3.3-STABLE FreeBSD 3.3-STABLE #17: Sun Nov 28 11:43:57 JST 1999 

>Description:

There is a simple typo in manual pages le.4.


>How-To-Repeat:
>Fix:
	
--- le.4.orig	Sun Nov 28 00:39:49 1999
+++ le.4.new	Thu Dec  2 00:37:15 1999
@@ -67,7 +67,7 @@
 .It "le%d: fatal RXD error, attempting recovery"
 .It "le%d: recovery failed -- board disabled"
 A receive error occurred.  The driver will attempt to recover from this
-error.  However it it cannot, the driver will shut the card down.
+error.  However it cannot, the driver will shut the card down.
 .It "le%d: lance: warning: excessive collisions: TDR%dns (%d-%dm)"
 An overly high number of Ethernet collisions were detected.  It may be the
 case that the network is overly busy.  Or this may suggest a problem with

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->closed 
State-Changed-By: chris 
State-Changed-When: Mon Dec 6 19:19:26 PST 1999 
State-Changed-Why:  
Modified patch applied (the first ``it'' should be an ``if'') 
>Unformatted:
