I would simplify this sentences. Something like:

The text before the '@' symbol is the name of the driver controlling the device.

In this case are man:em[4] and... --> In this case these are man:em[4] and...

I would clarify as this:

...followed by the order in which... --> ...followed by a number representing the order in which...

This paragraph should probably be shown after the actual example.

We can use here Configuring Static IPv4 Address since in the next paragraph we use IPv6 instead of IP Version 6

I would use IPv6 here too.

s/folloing/following/

Join the last two sentence (fragments).

FreeBSD also includes support for a number of software network interfaces such as the loopback, man:lo[4].

For example, to load the man:alc[4] module, execute the following command:

Shouldn't this just be if_alc (no _load appended)?

I still find this sentence cumbersome. Also, I'd use "adapter" rather than "card", as not all interfaces are on cards, and there are cards with multiple interfaces.

s/card/interface/

s/card/interface/, here and later

Should we be modern and show CIDR notation too (ifconfig em0 inet 192.168.1.150/24)? I'd show both.

Would it be worthwhile mentioning how to run dhclient manually (just "dhclient interface_name"? That way, you can see if it succeeds. But it goes into background if it times out, and may need to be killed.

This seems like too much detail; things like site-local don't really need to be here. We could label the table something like "Example IPv6 Reserved Addresses" to make it clear that it is incomplete. Or these could be called something else, like types of addresses.

I don't understand this entry; 16 bits are shown, or 14 if you omit the always-0 bits. And with the ::, the examples are 128 bits. Should this be /16?

Why is rtsol needed for a static IPv6? I don't use it. I thought it was just for SLAAC. I think dynamic addressing should be a separate section. Also, I'd put a comma after "static IP address", and refer to rtsold(8).

s/stepp/step/

I took the example from alc[4] and says:

     Alternatively, to load the	driver as a module at boot time, place the
     following line in loader.conf(5):

	   if_alc_load="YES"

Much better!

Good idea, I like it

That's correct for loader.conf, but not for the manual command above. Try it.

you're right :)

TBH, I took this table from the advanced networking chapter, I don't know if the info is right or not

We should add links between network/ and advanced-networking/ chapters.

Add a new topic here:

• Understand basic network configuration on FreeBSD (Network[link]).

Virtual hosts with several IPs is an outdated approach to implementing SSL/TLS, I don't know if it's only with me, but this chapter bothers me for being here.
Maybe move this to the Advanced Networking chapter?
Or rewrite it, saying only how to add aliases. But I don't have a strong opinion about what is better here.

We should add links between network/ and advanced-networking/ chapters.

Maybe adding this on the bottom here.

• Advanced topics
  
  See the Advanced Networking(link) chapter for more details and advanced networking topics.

Here and a couple of lines down are two remaining references to NIC; I prefer just "interface".

I don't think dhcient supports IPv6. I'm not sure of the state of play on DHCPv6. rtsold implements SLAAC (Stateless Address Auto-Configuration) as a daemon, or if invoked as rtsol, it runs in foreground and accepts an interface name. I think DHCP can just be removed from the rc line.

This should be done only on a router, and advertises the network prefix as well as default route.

Maybe show an FQDN. maybe freebsdhostname.example.com?

Similarly, use an FQDN.

s/who/that/