1 files changed, 13 insertions, 13 deletions
diff --git a/documentation/content/en/books/handbook/advanced-networking/_index.adoc b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
index 57ddfe3d75..6bade200be 100644
--- a/documentation/content/en/books/handbook/advanced-networking/_index.adoc
+++ b/documentation/content/en/books/handbook/advanced-networking/_index.adoc
@@ -54,7 +54,7 @@ endif::[]
 
 This chapter covers a number of advanced networking topics.
 
-After reading this chapter, you will know:
+Read this chapter to learn:
 
 * The basics of gateways and routes.
 * How to set up USB tethering.
@@ -63,9 +63,9 @@ After reading this chapter, you will know:
 * How to set up network PXE booting.
 * How to enable and utilize the features of the Common Address Redundancy Protocol (CARP) in FreeBSD.
 * How to configure multiple VLANs on FreeBSD.
-* Configure bluetooth headset.
+* How to configure a bluetooth headset.
 
-Before reading this chapter, you should:
+Before reading this chapter:
 
 * Understand the basics of the [.filename]#/etc/rc# scripts.
 * Be familiar with basic network terminology.
@@ -1325,7 +1325,7 @@ cu -l $PTS
 
 By default, when FreeBSD is accepting a new connection, it tries to perform a role switch and become master.
 Some older Bluetooth devices which do not support role switching will not be able to connect.
-Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching. 
+Since role switching is performed when a new connection is being established, it is not possible to ask the remote device if it supports role switching.
 However, there is a HCI option to disable role switching on the local side:
 
 [source,shell]
@@ -1454,7 +1454,7 @@ The STP protocol detects loops and puts redundant links into a blocked state.
 Should one of the active links fail, STP calculates a different tree and enables one of the blocked paths to restore connectivity to all points in the network.
 
 The Rapid Spanning Tree Protocol (RSTP or 802.1w) provides backwards compatibility with legacy STP.
-RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops. 
+RSTP provides faster convergence and exchanges information with neighboring switches to quickly transition to forwarding mode without creating loops.
 FreeBSD supports RSTP and STP as operating modes, with RSTP being the default mode.
 
 STP can be enabled on member interfaces using man:ifconfig[8].
@@ -1527,7 +1527,7 @@ Sticky entries are never aged out of the cache or replaced, even if the address
 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 cannot roam to another segment.
 +
-An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space. 
+An example of using sticky addresses is to combine the bridge with VLANs in order to isolate customer networks without wasting IP address space.
 Consider that `CustomerA` is on `vlan100`, `CustomerB` is on `vlan101`, and the bridge has the address `192.168.0.1`:
 +
 [source,shell]
@@ -1558,7 +1558,7 @@ The following example sets the maximum number of Ethernet devices for `CustomerA
 # ifconfig bridge0 ifmaxaddr vlan100 10
 ....
 
-Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further. 
+Bridge interfaces also support monitor mode, where the packets are discarded after man:bpf[4] processing and are not processed or forwarded further.
 This can be used to multiplex the input of two or more interfaces into a single man:bpf[4] stream.
 This is useful for reconstructing the traffic for network taps that transmit the RX/TX signals out through two separate interfaces.
 For example, to read the input from four network interfaces as one stream:
@@ -1688,7 +1688,7 @@ Each LAG is composed of ports of the same speed, set to full-duplex operation, a
 Typically, there is only one LAG which contains all the ports.
 In the event of changes in physical connectivity, LACP will quickly converge to a new configuration.
 +
-LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port. 
+LACP balances outgoing traffic across the active ports based on hashed protocol header information and accepts incoming traffic from any active port.
 The hash includes the Ethernet source and destination address and, if available, the VLAN tag, and the IPv4 or IPv6 source and destination address.
 
 roundrobin::
@@ -1844,7 +1844,7 @@ ifconfig_lagg0="laggproto failover laggport fxp0 laggport fxp1 10.0.0.15/24"
 [example]
 ====
 
-For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available. 
+For laptop users, it is usually desirable to configure the wireless device as a secondary which is only used when the Ethernet connection is not available.
 With man:lagg[4], it is possible to configure a failover which prefers the Ethernet connection for both performance and security reasons, while maintaining the ability to transfer data over the wireless connection.
 
 This is achieved by overriding the Ethernet interface's MAC address with that of the wireless interface.
@@ -1859,13 +1859,13 @@ We therefore recommend overriding the Ethernet MAC address for this purpose.
 [NOTE]
 ****
 If the driver for the wireless interface is not loaded in the `GENERIC` or custom kernel, and the computer is running FreeBSD {rel121-current}, load the corresponding [.filename]#.ko# in [.filename]#/boot/loader.conf# by adding `*driver_load="YES"*` to that file and rebooting.
-Another, better way is to load the driver in [.filename]#/etc/rc.conf# by adding it to `kld_list` (see man:rc.conf[5] for details) in that file and rebooting. 
+Another, better way is to load the driver in [.filename]#/etc/rc.conf# by adding it to `kld_list` (see man:rc.conf[5] for details) in that file and rebooting.
 This is needed because otherwise the driver is not loaded yet at the time the man:lagg[4] interface is set up.
 ****
 
 In this example, the Ethernet interface, _re0_, is the master and the wireless interface, _wlan0_, is the failover.
 The _wlan0_ interface was created from the _ath0_ physical wireless interface, and the Ethernet interface will be configured with the MAC address of the wireless interface.
-First, bring the wireless interface up (replacing _FR_ with your own 2-letter country code), but do not set an IP address.
+First, bring the wireless interface up (replacing _FR_ with the local 2-letter country code), but do not set an IP address.
 Replace _wlan0_ to match the system's wireless interface name:
 
 [source,shell]
@@ -1873,7 +1873,7 @@ Replace _wlan0_ to match the system's wireless interface name:
 # ifconfig wlan0 create wlandev ath0 country FR ssid my_router up
 ....
 
-Now you can determine the MAC address of the wireless interface:
+Determine the MAC address of the wireless interface like this:
 
 [source,shell]
 ....
@@ -2095,7 +2095,7 @@ In this case, [.filename]#/etc# and [.filename]#/var# need to be memory backed f
 
 When the system boots, memory file systems for [.filename]#/etc# and [.filename]#/var# will be created and mounted and the contents of the [.filename]#cpio.gz# files will be copied into them.
 By default, these file systems have a maximum capacity of 5 megabytes.
-If your archives do not fit, which is usually the case for [.filename]#/var# when binary packages have been installed, request a larger size by putting the number of 512 byte sectors needed (e.g., 5 megabytes is 10240 sectors) in [.filename]#${NFSROOTDIR}/conf/base/etc/md_size# and [.filename]#${NFSROOTDIR}/conf/base/var/md_size# files for [.filename]#/etc# and [.filename]#/var# file systems respectively.
+If the archives do not fit, which is usually the case for [.filename]#/var# when binary packages have been installed, request a larger size by putting the number of 512 byte sectors needed (e.g., 5 megabytes is 10240 sectors) in [.filename]#${NFSROOTDIR}/conf/base/etc/md_size# and [.filename]#${NFSROOTDIR}/conf/base/var/md_size# files for [.filename]#/etc# and [.filename]#/var# file systems respectively.
 
 [[network-pxe-setting-up-dhcp]]
 === Configuring the DHCP Server