In D22708#499697, @jwb wrote:

Barring any typos that escaped my notice, looks fine to me. Thanks for your work on this!

Thanks for reviewing it. Now to wait for a committer, since I'm not one.

I'm currently only a ports committer, so this will have to fall on someone else.

Didn't know that was possible. I'm going to be swamped for the next week or two, but I'll look into it ASAP after that.

I'm trying to build-test per https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html and I'm getting nothing but '#' symbols for the text. Anybody seen this issue before?

In D22708#502624, @jwb wrote:

I'm trying to build-test per https://www.freebsd.org/doc/en_US.ISO8859-1/books/fdp-primer/overview.html and I'm getting nothing but '#' symbols for the text. Anybody seen this issue before?

During compilation or as the resulting text?
Do a "make clean" in the handbook's directory first to clean up all leftovers from previous runs, then run "make" again in that same dir (not in the subdir for the article).
Also, check the encoding of the patch, the patched file, and the result.

In the resulting text:

Part IV. Network Communication

. # ## ###

I already tried a make clean in the "handbook" directory and in "doc".

This occurs throughout the handbook, with or without the patch.

Only the PDF output is screwy and I can verify using the HTML, so I'll go ahead with the commit shortly. I made one small change, adding a note to inform the reader why we should change the Ethernet MAC rather than the WiFi:

<note>
  <para>In theory, either the Ethernet or wireless MAC address can
  be changed to match the other.  However, some popular wireless
  interfaces lack support for overriding the MAC address.  We
  therefore recommend overriding the Ethernet MAC address for this
  purpose.</para>
</note>

If there are no other suggestions, I'll proceed with the commit.

If the note is below the example, consider that approved as well (remember the blank line in between).

But the <para>'s text in the <note> need a bit more indentation. Other than that, it's good.

I actually put the note right after the statement it's clarifying:

<para>This is achieved by overriding the Ethernet interface's
  <acronym>MAC</acronym> address with that of the wireless
  interface.</para>

<note>
  <para>In theory, either the Ethernet or wireless MAC address can
    be changed to match the other.  However, some popular wireless
    interfaces lack support for overriding the MAC address.  We
    therefore recommend overriding the Ethernet MAC address for this
    purpose.</para>
</note>

<para>In this example, the Ethernet interface,
  <replaceable>re0</replaceable>, is the master and the
  wireless interface, <replaceable>wlan0</replaceable>, is
  the failover.  The <replaceable>wlan0</replaceable>

Good catch on the indentation.