Date: Thu, 3 Nov 2016 19:48:36 +0000 (UTC) From: Sevan Janiyan <sevan@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r49640 - head/en_US.ISO8859-1/books/handbook/advanced-networking Message-ID: <201611031948.uA3Jmawj032540@repo.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: sevan Date: Thu Nov 3 19:48:36 2016 New Revision: 49640 URL: https://svnweb.freebsd.org/changeset/doc/49640 Log: Fix spelling mistakes picked up by igor. Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D8428 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 Thu Nov 3 19:41:54 2016 (r49639) +++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Thu Nov 3 19:48:36 2016 (r49640) @@ -3231,7 +3231,7 @@ bridge0: flags=8843<UP,BROADCAST,RUNN address is seen on a different interface. This gives the benefit of static address entries without the need to pre-populate the forwarding table. Clients learned - on a particular segment of the bridge can not roam to + on a particular segment of the bridge cannot roam to another segment.</para> <para>An example of using sticky addresses is to combine @@ -3251,7 +3251,7 @@ bridge0: flags=8843<UP,BROADCAST,RUNN <para>In this example, both clients see <systemitem class="ipaddress">192.168.0.1</systemitem> as their default gateway. Since the bridge cache is sticky, one - host can not spoof the <acronym>MAC</acronym> address of + host cannot spoof the <acronym>MAC</acronym> address of the other customer in order to intercept their traffic.</para>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201611031948.uA3Jmawj032540>