From owner-svn-doc-projects@FreeBSD.ORG Mon May 20 14:17:50 2013 Return-Path: Delivered-To: svn-doc-projects@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 40698EA7; Mon, 20 May 2013 14:17:50 +0000 (UTC) (envelope-from dru@FreeBSD.org) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) by mx1.freebsd.org (Postfix) with ESMTP id 33045C39; Mon, 20 May 2013 14:17:50 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.6/8.14.6) with ESMTP id r4KEHonj005280; Mon, 20 May 2013 14:17:50 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.6/8.14.5/Submit) id r4KEHoi7005278; Mon, 20 May 2013 14:17:50 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201305201417.r4KEHoi7005278@svn.freebsd.org> From: Dru Lavigne Date: Mon, 20 May 2013 14:17:50 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-projects@freebsd.org Subject: svn commit: r41699 - projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking X-SVN-Group: doc-projects MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-projects@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: SVN commit messages for doc projects trees List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 20 May 2013 14:17:50 -0000 Author: dru Date: Mon May 20 14:17:49 2013 New Revision: 41699 URL: http://svnweb.freebsd.org/changeset/doc/41699 Log: This patch fixes some spelling errors and incorrect acronym tags. Approved by: bcr (mentor) Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Modified: projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml ============================================================================== --- projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Mon May 20 13:44:26 2013 (r41698) +++ projects/ISBN_1-57176-407-0/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Mon May 20 14:17:49 2013 (r41699) @@ -566,7 +566,7 @@ route_internalnet2="-net 192.168.2.0/24 internalnet2. The variable route_internalnet2 contains all of the configuration parameters to - &man.route.8;. This example is equivalen to the + &man.route.8;. This example is equivalent to the command: &prompt.root; route add -net 192.168.2.0/24 192.168.1.2 @@ -1060,7 +1060,7 @@ ifconfig_wlan0="mode 11gThis example will force the card to operate in 802.11g, which is defined only for 2.4GHz frequencies so any 5GHz channels will not be considered. This can - also be achieved witt the + also be achieved with the parameter, which locks operation to one specific frequency, and the parameter, to specify a list @@ -3116,7 +3116,7 @@ ifconfig_fxp1="up" STP is used to detect and remove loops in a network topology. RSTP provides faster convergence than legacy STP, the - protocol will exchange information with neighbouring switches + protocol will exchange information with neighboring switches to quickly transition to forwarding without creating loops. &os; supports RSTP and STP as operating modes, with @@ -4510,7 +4510,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/i configuration is shown where the DHCP, TFTP, and NFS servers are on the same machine. However, these - severs can be on separate machines. + servers can be on separate machines.
<acronym>PXE</acronym> Booting Process with @@ -4748,7 +4748,7 @@ ipdivert_load="YES"</programlisting> <primary>kernel</primary> <secondary>configuration</secondary> </indexterm> - <para>When modules are not an option or if it is preferrable to + <para>When modules are not an option or if it is preferable to build all the required features into a custom kernel, the following options must be in the custom kernel configuration file:</para> @@ -5755,15 +5755,15 @@ route_hostD="192.168.173.4 hatm0 0 102 l <para>One use of <acronym>CARP</acronym> is to provide server availability. This example configures failover support for - three hosts, all with unique <acronym><acronym>IP</acronym></acronym> + three hosts, all with unique <acronym>IP</acronym> addresses and providing the same web content. These machines act in conjunction with a Round Robin <acronym>DNS</acronym> configuration. The failover machine has two additional <acronym>CARP</acronym> interfaces, one for each of the content server's - <acronym><acronym>IP</acronym></acronym> addresses. When a + <acronym>IP</acronym> addresses. When a failure occurs, the failover server will pick up the failed - machine's <acronym><acronym>IP</acronym></acronym> address. + machine's <acronym>IP</acronym> address. This means that the failure should go completely unnoticed by the user. The failover server requires identical content and services as the other content servers it is expected to