diff --git a/share/man/man4/ipsec.4 b/share/man/man4/ipsec.4
index ff404ccfff19..f5a81dffd5f1 100644
--- a/share/man/man4/ipsec.4
+++ b/share/man/man4/ipsec.4
@@ -104,7 +104,7 @@ by using the above described APIs.
 The kernel implements experimental policy management code.
 You can manage the IPsec policy in two ways.
 One is to configure per-socket policy using
-.Xr setsockopt 3 .
+.Xr setsockopt 2 .
 The other is to configure kernel packet filter-based policy using
 .Dv PF_KEY
 interface, via
@@ -113,7 +113,7 @@ In both cases, IPsec policy must be specified with syntax described in
 .Xr ipsec_set_policy 3 .
 .Pp
 With
-.Xr setsockopt 3 ,
+.Xr setsockopt 2 ,
 you can define IPsec policy in per-socket basis.
 You can enforce particular IPsec policy onto packets that go through
 particular socket.
diff --git a/share/man/man4/ng_bpf.4 b/share/man/man4/ng_bpf.4
index 698e7c3869c8..eb8bbb005d9b 100644
--- a/share/man/man4/ng_bpf.4
+++ b/share/man/man4/ng_bpf.4
@@ -135,7 +135,7 @@ This node shuts down upon receipt of a
 control message, or when all hooks have been disconnected.
 .Sh EXAMPLES
 It is possible to configure a node from the command line, using
-.Xr tcpdump 8 
+.Xr tcpdump 1 
 to generate raw BPF instructions which are then fed into an
 .Xr awk 1
 script to create the ASCII form of a
diff --git a/usr.sbin/lpr/lpr/printcap.5 b/usr.sbin/lpr/lpr/printcap.5
index 092f9fc9e7aa..9c2d4394da4d 100644
--- a/usr.sbin/lpr/lpr/printcap.5
+++ b/usr.sbin/lpr/lpr/printcap.5
@@ -374,7 +374,7 @@ are sent to the corresponding
 .Cm lf
 file.
 The filters may, of course, use
-.Xr syslog 8
+.Xr syslogd 8
 themselves.
 .Pp
 Error messages sent to the console have a carriage return and a line