bpf.2: Minor fixes

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/bpf.2

@@ -42,7 +42,7 @@ For both cBPF and eBPF programs,
 the kernel statically analyzes the programs before loading them,
 in order to ensure that they cannot harm the running system.
 .P
-eBPF extends cBPF in multiple ways including the ability to call
+eBPF extends cBPF in multiple ways, including the ability to call
 in-kernel helper functions (via the
 .B BPF_CALL
 opcode extension provided by eBPF)
@@ -83,8 +83,8 @@ A new event triggers execution of the eBPF program, which
 may store information about the event in the maps.
 Beyond storing data, eBPF programs may call a fixed set of
 in-kernel helper functions.
-The same program can be attached to multiple events and different programs can
-access the same map:
+The same program can be attached to multiple events and different
+eBPF programs can access the same map:
 .\" FIXME Can maps be shared between processes? (E.g., what happens
 .\"       when fork() is called?)
 
@@ -345,7 +345,7 @@ bpf_lookup_elem(int fd, void *key, void *value)
 
 If an element is found,
 the operation returns zero and stores the element's value into
-.I value.
+.IR value .
 .\" FIXME Here, I think we need some statement about what 'value' must
 .\"       point to. Presumable, it must be a buffer at least as large as
 .\"       the map's 'value_size' attribute?
@@ -885,7 +885,8 @@ commands require the caller to have the
 capability.
 .SH SEE ALSO
 .BR seccomp (2),
-.BR socket (7)
+.BR socket (7),
+.BR tc (8)
 
 Both classic and extended BPF are explained in the kernel source file
 .IR Documentation/networking/filter.txt .