doc: nft.8: Highlight "hook" in flowtable description

commit 9da7b00aa886012c0e59e73aa19e05a8d1568540 upstream.

Lacking an explicit description of possible hook values, emphasising the
word in the description text should draw readers' attention in the right
direction.

Signed-off-by: Phil Sutter <phil@nwl.cc>

diff --git a/doc/nft.txt b/doc/nft.txt
index eb8df1d95e53ad3a0815087c229c4efd21abf98e..7a99f65b1407e0771918ccd718caa01466e44fa3 100644 (file)
--- a/doc/nft.txt
+++ b/doc/nft.txt
@@ -702,8 +702,8 @@ protocols. Each entry also caches the destination interface and the gateway
 address - to update the destination link-layer address - to forward packets.
 The ttl and hoplimit fields are also decremented. Hence, flowtables provides an
 alternative path that allow packets to bypass the classic forwarding path.
-Flowtables reside in the ingress hook that is located before the prerouting
-hook. You can select which flows you want to offload through the flow
+Flowtables reside in the ingress *hook* that is located before the prerouting
+*hook*. You can select which flows you want to offload through the flow
 expression from the forward chain. Flowtables are identified by their address
 family and their name. The address family must be one of ip, ip6, or inet. The inet
 address family is a dummy family which is used to create hybrid IPv4/IPv6