From owner-svn-doc-head@FreeBSD.ORG  Mon Mar 31 13:57:13 2014
Return-Path: <owner-svn-doc-head@FreeBSD.ORG>
Delivered-To: svn-doc-head@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115])
 (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id 09347A29;
 Mon, 31 Mar 2014 13:57:13 +0000 (UTC)
Received: from svn.freebsd.org (svn.freebsd.org
 [IPv6:2001:1900:2254:2068::e6a:0])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id E9905FF7;
 Mon, 31 Mar 2014 13:57:12 +0000 (UTC)
Received: from svn.freebsd.org ([127.0.1.70])
 by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s2VDvCoX007070;
 Mon, 31 Mar 2014 13:57:12 GMT (envelope-from dru@svn.freebsd.org)
Received: (from dru@localhost)
 by svn.freebsd.org (8.14.8/8.14.8/Submit) id s2VDvCLU007069;
 Mon, 31 Mar 2014 13:57:12 GMT (envelope-from dru@svn.freebsd.org)
Message-Id: <201403311357.s2VDvCLU007069@svn.freebsd.org>
From: Dru Lavigne <dru@FreeBSD.org>
Date: Mon, 31 Mar 2014 13:57:12 +0000 (UTC)
To: doc-committers@freebsd.org, svn-doc-all@freebsd.org,
 svn-doc-head@freebsd.org
Subject: svn commit: r44394 -
 head/en_US.ISO8859-1/books/handbook/advanced-networking
X-SVN-Group: doc-head
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-BeenThere: svn-doc-head@freebsd.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: SVN commit messages for the doc tree for head
 <svn-doc-head.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/svn-doc-head>,
 <mailto:svn-doc-head-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/svn-doc-head/>
List-Post: <mailto:svn-doc-head@freebsd.org>
List-Help: <mailto:svn-doc-head-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/svn-doc-head>,
 <mailto:svn-doc-head-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 31 Mar 2014 13:57:13 -0000

Author: dru
Date: Mon Mar 31 13:57:12 2014
New Revision: 44394
URL: http://svnweb.freebsd.org/changeset/doc/44394

Log:
  As per discussion on freebsd-doc@, clarify wording of lagg definition.
  
  Sponsored by:	iXsystems

Modified:
  head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml

Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml	Mon Mar 31 00:32:09 2014	(r44393)
+++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml	Mon Mar 31 13:57:12 2014	(r44394)
@@ -3329,8 +3329,8 @@ BEGEMOT-BRIDGE-MIB::begemotBridgeDefault
     <para>&os; provides the &man.lagg.4; interface which can be used
       to aggregate multiple network interfaces into one virtual
       interface in order to provide failover and link aggregation.
-      Failover allows traffic to continue to flow even if an
-      interface becomes available.  Link aggregation works best on
+      Failover allows traffic to continue to flow as long as at least one
+      aggregated network interface has an established link.  Link aggregation works best on
       switches which support <acronym>LACP</acronym>, as this
       protocol distributes traffic bi-directionally while responding
       to the failure of individual links.</para>