2 files changed, 10 insertions, 10 deletions
diff --git a/doc/skadns/index.html b/doc/skadns/index.html
index 23d8226..f54db2c 100644
--- a/doc/skadns/index.html
+++ b/doc/skadns/index.html
@@ -6,14 +6,14 @@
     <title>s6-dns: the skadns library interface</title>
     <meta name="Description" content="s6-dns: the skadns library interface" />
     <meta name="Keywords" content="s6-dns skadns library asynchronous resolution resolver client C interface" />
-    <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> -->
+    <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
   </head>
 <body>
 
 <p>
 <a href="../index.html">s6-dns</a><br />
-<a href="http://skarnet.org/software/">Software</a><br />
-<a href="http://skarnet.org/">skarnet.org</a>
+<a href="//skarnet.org/software/">Software</a><br />
+<a href="//skarnet.org/">skarnet.org</a>
 </p>
 
 <h1> The <tt>skadns</tt> library interface </h1>
@@ -58,7 +58,7 @@ exact function prototypes.
 know it has. This means paying some attention to the SIGCHLD handler,
 if any, and to the way you perform <tt>waitpid()</tt>s. The best
 practice is to use a
-<a href="http://skarnet.org/software/skalibs/libstddjb/selfpipe.html">self-pipe</a>
+<a href="//skarnet.org/software/skalibs/libstddjb/selfpipe.html">self-pipe</a>
 to handle SIGCHLD (as well as other signals the application needs to trap),
 and to <em>always</em> use <tt>wait_nohang()</tt> to reap children,
 simply ignoring pids you don't know.
diff --git a/doc/skadns/skadnsd.html b/doc/skadns/skadnsd.html
index 0a11297..951dfb8 100644
--- a/doc/skadns/skadnsd.html
+++ b/doc/skadns/skadnsd.html
@@ -6,14 +6,14 @@
     <title>s6-dns: the skadnsd internal program</title>
     <meta name="Description" content="s6-dns: the skadnsd internal program" />
     <meta name="Keywords" content="s6-dns skadnsd asynchronous dns daemon" />
-    <!-- <link rel="stylesheet" type="text/css" href="http://skarnet.org/default.css" /> -->
+    <!-- <link rel="stylesheet" type="text/css" href="//skarnet.org/default.css" /> -->
   </head>
 <body>
 
 <a href="index.html">libskadns</a><br />
 <a href="../index.html">s6-dns</a><br />
-<a href="http://skarnet.org/software/">Software</a><br />
-<a href="http://skarnet.org/">skarnet.org</a><p />
+<a href="//skarnet.org/software/">Software</a><br />
+<a href="//skarnet.org/">skarnet.org</a><p />
 
 <h1> The <tt>skadnsd</tt> program </h1>
 
@@ -80,7 +80,7 @@ that it requires support from the system administrator.
 <p>
 skadnsd has no "standalone" mode: it is designed to work with a Unix
 domain superserver, like
-<a href="http://skarnet.org/software/s6/s6-ipcserver.html">s6-ipcserver</a>.
+<a href="//skarnet.org/software/s6/s6-ipcserver.html">s6-ipcserver</a>.
 skadnsd follows the <a href="http://cr.yp.to/proto/ucspi.txt">UCSPI</a>
 interface, it can be directly executed from the superserver.
 </p>
@@ -98,14 +98,14 @@ to run it under a specific account.
 <ul>
  <li> Users should never invoke <tt>skadnsd</tt> directly. It's an
 internal program designed to be spawned by the skadns library.
-It follows <a href="http://skarnet.org/software/skalibs/">skalibs</a>'
+It follows <a href="//skarnet.org/software/skalibs/">skalibs</a>'
 "skaclient" protocol and is unusable unless spawned by the right client
 library also using that protocol. </li>
  <li> If a poorly designed client sends a lot of queries and never reads the
 answers, those will indefinitely queue up in the daemon, eating up
 memory. You should run your process (or your Unix superserver, if you're
 using a skadnsd service) under a program like
-<a href="http://skarnet.org/software/s6/s6-softlimit.html">s6-softlimit</a> to
+<a href="//skarnet.org/software/s6/s6-softlimit.html">s6-softlimit</a> to
 set a memory limit to every skadnsd instance. If skadnsd runs out of
 allowed memory, it will simply die. </li>
  <li> If you're using a skadnsd service: you should configure your