svn commit: r49640 - head/en_US.ISO8859-1/books/handbook/advanced-networking

Sevan Janiyan <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
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&lt;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&lt;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>
 
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.