diff --git a/man4/cciss.4 b/man4/cciss.4
index 9600c8f6f..d5732f168 100644
--- a/man4/cciss.4
+++ b/man4/cciss.4
@@ -140,7 +140,7 @@ For example:
 .in +4n
 .EX
 $ \fBcd /proc/driver/cciss\fP
-$ \fBls -l\fP
+$ \fBls \-l\fP
 total 0
 -rw-r--r-- 1 root root 0 2010\-09\-10 10:38 cciss0
 -rw-r--r-- 1 root root 0 2010\-09\-10 10:38 cciss1
@@ -360,7 +360,7 @@ successfully reset or the tardy command is successfully aborted, the
 tape drive may still not allow I/O to continue until some command
 is issued that positions the tape to a known position.
 Typically you must rewind the tape (by issuing
-.I "mt -f /dev/st0 rewind"
+.I "mt \-f /dev/st0 rewind"
 for example) before I/O can proceed again to a tape drive that was reset.
 .SH SEE ALSO
 .BR hpsa (4),
diff --git a/man4/loop.4 b/man4/loop.4
index a2900d4e4..a3c59310d 100644
--- a/man4/loop.4
+++ b/man4/loop.4
@@ -43,7 +43,7 @@ You could do
 .EX
 $ \fBdd if=/dev/zero of=file.img bs=1MiB count=10\fP
 $ \fBsudo losetup /dev/loop4 file.img\fP
-$ \fBsudo mkfs -t ext4 /dev/loop4\fP
+$ \fBsudo mkfs \-t ext4 /dev/loop4\fP
 $ \fBsudo mkdir /myloopdev\fP
 $ \fBsudo mount /dev/loop4 /myloopdev\fP
 .EE
diff --git a/man4/veth.4 b/man4/veth.4
index 1cc473434..97f596844 100644
--- a/man4/veth.4
+++ b/man4/veth.4
@@ -91,7 +91,7 @@ network interface, using commands something like:
 .in +4n
 .EX
 # \fBip link add ve_A type veth peer name ve_B\fP   # Create veth pair
-# \fBethtool -S ve_A\fP         # Discover interface index of peer
+# \fBethtool \-S ve_A\fP         # Discover interface index of peer
 NIC statistics:
      peer_ifindex: 16
 # \fBip link | grep '^16:'\fP   # Look up interface