socket.7: Minor fixes to SO_BUSY_POLL text

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

diff --git a/man7/socket.7 b/man7/socket.7
index eb207f2eebdb47cdd10a32f1832a8657617f5265..568a6317f7adfdd22ab35996d014b83b55c8599d 100644 (file)
--- a/man7/socket.7
+++ b/man7/socket.7
@@ -42,7 +42,7 @@
 .\"            commit 3bdc0eba0b8b47797f4a76e377dd8360f317450f
 .\"            Author: Ben Greear <greearb@candelatech.com>
 .\"
-.TH SOCKET 7 2013-06-21 Linux "Linux Programmer's Manual"
+.TH SOCKET 7 2014-01-20 Linux "Linux Programmer's Manual"
 .SH NAME
 socket \- Linux socket interface
 .SH SYNOPSIS
@@ -697,7 +697,8 @@ This socket option is read-only.
 .TP
 .B SO_BUSY_POLL
 Sets the approximate time in microseconds to busy poll on a blocking receive
-when there is no data. Increasing this value requires
+when there is no data.
+Increasing this value requires
 .BR CAP_NET_ADMIN . 
 The default for this option is controlled by the
 .I /proc/sys/net/core/busy_read
@@ -713,12 +714,13 @@ will busy poll when they operate on sockets with
 .BR SO_BUSY_POLL
 set and no events to report are found.
 
-In both cases busy polling will only be done when the socket last received data
+In both cases,
+busy polling will only be done when the socket last received data
 from a network device that supports this option.
 
-While busy polling may improve latency of some applications, care must be
-taken when using it since this will increase both CPU utilization and power usage.
-
+While busy polling may improve latency of some applications,
+care must be taken when using it since this will increase
+both CPU utilization and power usage.
 .SS Signals
 When writing onto a connection-oriented socket that has been shut down
 (by the local or the remote end)