@@ -11,8 +11,7 @@ On Windows a local named pipe is used to listen for
runtime management
commands. A file is created in the absolute path as pointed by \fIsocket\fR
or if \fB\-\-unixctl\fR is not used at all, a file is created as
\fB\*(PN.ctl\fR in the configured \fIOVS_RUNDIR\fR directory.
-The file exists just to mimic the behavior of a Unix socket domain
-socket.
+The file exists just to mimic the behavior of a Unix domain socket.
.IP
Specifying \fBnone\fR for \fIsocket\fR disables the control socket
feature.
@@ -14,5 +14,5 @@ square brackets, e.g.: \fBtcp:[::1]:6640\fR.
.IP "\fBunix:\fIfile\fR"
On POSIX, connect to the Unix domain server socket named \fIfile\fR.
.IP
-On Windows, connect to a local named pipe and a file is created in the
-path \fIfile\fR to mimic the behavior of a Unix domain socket.
+On Windows, connect to a local named pipe that is represented by a file
created
+in the path \fIfile\fR to mimic the behavior of a Unix domain socket.
@@ -22,5 +22,5 @@ an IPv6 address, then wrap \fIip\fR with square brackets,
e.g.:
On POSIX, listen on the Unix domain server socket named \fIfile\fR for a
connection.
.IP
-On Windows, listen on a local named pipe. A file is created in the
+On Windows, listen on a local named pipe. A file is created in the