Date: Sun, 28 Oct 2012 00:22:52 +0000 (UTC) From: Warren Block <wblock@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r39823 - head/en_US.ISO8859-1/books/handbook/advanced-networking Message-ID: <201210280022.q9S0Mq1I090231@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: wblock Date: Sun Oct 28 00:22:52 2012 New Revision: 39823 URL: http://svn.freebsd.org/changeset/doc/39823 Log: Remove a few redundant uses of "file", expand contractions, remove duplicate words. Fix title capitalization, spelling, and simplify wording in a few sentences. 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 Sat Oct 27 21:45:15 2012 (r39822) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Sun Oct 28 00:22:52 2012 (r39823) @@ -390,8 +390,8 @@ host2.example.com link#1 UC </tgroup> </informaltable> - <para>You can easily define the default route via the - <filename>/etc/rc.conf</filename> file. In our example, on + <para>The default route can be easily defined in + <filename>/etc/rc.conf</filename>. In our example, on the <hostid>Local2</hostid> machine, we added the following line in <filename>/etc/rc.conf</filename>:</para> @@ -403,7 +403,7 @@ host2.example.com link#1 UC <screen>&prompt.root; <userinput>route add default 10.20.30.1</userinput></screen> <para>For more information on manual manipulation of network - routing tables, consult &man.route.8; manual page.</para> + routing tables, consult the &man.route.8; manual page.</para> </sect2> <sect2 id="network-dual-homed-hosts"> @@ -573,9 +573,8 @@ default 10.0.0.1 UG <para>The above example is perfect for configuring a static route on a running system. However, one problem is that the routing information will not persist if you reboot your &os; - machine. The way to handle the addition of a static route - is to put it in your <filename>/etc/rc.conf</filename> - file:</para> + machine. Additional static routes can be + entered in <filename>/etc/rc.conf</filename>:</para> <programlisting># Add Internal Net 2 as a static route static_routes="internalnet2" @@ -834,8 +833,8 @@ route_net2="-net 192.168.1.0/24 192.168. <para>The first thing you need is a wireless device. The most commonly used devices are those that use parts made by Atheros. These devices are supported by the &man.ath.4; - driver and require the following line to be added to the - <filename>/boot/loader.conf</filename> file:</para> + driver and require the following line to be added to + <filename>/boot/loader.conf</filename>:</para> <programlisting>if_ath_load="YES"</programlisting> @@ -879,7 +878,7 @@ route_net2="-net 192.168.1.0/24 192.168. <literal>wlan_scan_sta</literal> modules; the &man.wlan.4; module is automatically loaded with the wireless device driver, the remaining modules must be loaded at boot time - via the <filename>/boot/loader.conf</filename> file:</para> + in <filename>/boot/loader.conf</filename>:</para> <programlisting>wlan_scan_ap_load="YES" wlan_scan_sta_load="YES"</programlisting> @@ -2776,7 +2775,7 @@ Bluetooth Profile Descriptor List: <title>OBEX Object Push (OPUSH) Profile</title> <indexterm><primary>OBEX</primary></indexterm> - <para>OBEX is a widely used protocol for simple file transfers between + <para>OBEX is a widely used protocol for simple file transfers between mobile devices. Its main use is in infrared communication, where it is used for generic file transfers between notebooks or PDAs, and for sending business cards or @@ -3628,7 +3627,7 @@ bge0: flags=8843<UP,BROADCAST,RUNNING <screen>&prompt.root; <userinput>ifconfig <replaceable>iwn0</replaceable> ether <replaceable>00:21:70:da:ae:37</replaceable></userinput></screen> - <para>Bring up the wireless interface but don't set up any IP + <para>Bring the wireless interface up, but do not set an IP address on it:</para> <screen>&prompt.root; <userinput>ifconfig <replaceable>wlan0</replaceable> create wlandev <replaceable>iwn0</replaceable> ssid <replaceable>my_router</replaceable> up</userinput></screen> @@ -4647,7 +4646,7 @@ myhost.example.com:/b/tftpboot/FreeBSD/i severs can be on separate machines.</para> <figure> - <title>PXE Booting process with NFS root mount</title> + <title>PXE Booting Process with NFS Root Mount</title> <mediaobjectco> <imageobjectco> @@ -4865,7 +4864,7 @@ Received 264951 bytes in 0.1 seconds</sc <para>The main advantage of using a TA to connect to an Internet Provider is that you can do Dynamic PPP. As IP address space becomes more and more scarce, most providers are not willing - to provide you with a static IP anymore. Most stand-alone + to provide you with a static IP any more. Most stand-alone routers are not able to accommodate dynamic IP allocation.</para> @@ -4921,7 +4920,7 @@ Received 264951 bytes in 0.1 seconds</sc stand-alone router, and with a simple 386 FreeBSD box driving it, probably more flexible.</para> - <para>The choice of synchronous card/TA v.s. stand-alone router + <para>The choice of synchronous card/TA versus stand-alone router is largely a religious issue. There has been some discussion of this in the mailing lists. We suggest you search the <ulink url="&url.base;/search/index.html">archives</ulink> for @@ -5665,7 +5664,7 @@ round-trip min/avg/max/stddev = 2.530/2. <itemizedlist> <listitem> <para>Running out of addresses. Today this is not so much of - a concern anymore since RFC1918 private address space + a concern any more, since RFC1918 private address space (<hostid role="ipaddr">10.0.0.0/8</hostid>, <hostid role="ipaddr">172.16.0.0/12</hostid>, and <hostid role="ipaddr">192.168.0.0/16</hostid>) and Network
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201210280022.q9S0Mq1I090231>