Or omit the autolinking entirely.

Also, get rid of the FTP link to the USENIX paper, as 1) Markdown won't
treat ftp: URLs as URLs and 2) that link is broken anyway.

1 files changed, 4 insertions, 8 deletions

diff --git a/README.md b/README.md
index 0eb60096..37a8b9ab 100644
--- a/README.md
+++ b/README.md
@@ -39,19 +39,15 @@ Winter Usenix paper ``The BSD Packet Filter: A New Architecture for
 User-level Packet Capture''.  A compressed PostScript version can be
 found at
 
-<ftp://ftp.ee.lbl.gov/papers/bpf-usenix93.ps.Z>
-
-or
-
-<https://www.tcpdump.org/papers/bpf-usenix93.ps.Z>
+https://www.tcpdump.org/papers/bpf-usenix93.ps.Z
 
 and a gzipped version can be found at
 
-<https://www.tcpdump.org/papers/bpf-usenix93.ps.gz>
+https://www.tcpdump.org/papers/bpf-usenix93.ps.gz
 
 A PDF version can be found at
 
-<https://www.tcpdump.org/papers/bpf-usenix93.pdf>
+https://www.tcpdump.org/papers/bpf-usenix93.pdf
 
 Although most packet capture interfaces support in-kernel filtering,
 libpcap utilizes in-kernel filtering only for the BPF interface.
@@ -68,7 +64,7 @@ interface but has been extended to accept BPF filters (which libpcap
 utilizes).  Also, you can add BPF filter support to Ultrix using the
 kernel source and/or object patches available in:
 
-<https://www.tcpdump.org/other/bpfext42.tar.Z>
+https://www.tcpdump.org/other/bpfext42.tar.Z
 
 Linux has a number of BPF based systems, and libpcap does not support
 any of the eBPF mechanisms as yet, although it supports many of the