about summary refs log tree commit diff
diff options
context:
space:
mode:
authorColin Booth <colin@heliocat.net>2020-03-30 17:48:49 +0000
committerLaurent Bercot <ska-skaware@skarnet.org>2020-03-30 18:20:36 +0000
commit5a6cfb01304fc4a11d49db8e09ede330767ab9de (patch)
tree6927f51323cdbb77b63cb18dea751f138dd7de4b
parent0ea8684e5f3e4c09460788e0ac2e0a2a6c949511 (diff)
downloadskabus-5a6cfb01304fc4a11d49db8e09ede330767ab9de.tar.gz
skabus-5a6cfb01304fc4a11d49db8e09ede330767ab9de.tar.xz
skabus-5a6cfb01304fc4a11d49db8e09ede330767ab9de.zip
skabus: fix html errors
Signed-off-by: Colin Booth <colin@heliocat.net>
-rw-r--r--doc/libskabus/index.html2
-rw-r--r--doc/libskabus/rpc.html2
-rw-r--r--doc/skabus-rpcd.html4
3 files changed, 4 insertions, 4 deletions
diff --git a/doc/libskabus/index.html b/doc/libskabus/index.html
index 92a39ff..ccef295 100644
--- a/doc/libskabus/index.html
+++ b/doc/libskabus/index.html
@@ -95,7 +95,7 @@ functions taking a <em>deadline</em> and <em>stamp</em> argument also have a
 version with a name ending in <tt>_g</tt>, that does not take <em>stamp</em>, and
 assumes the <tt>STAMP</tt> variable always contains (an accurate
 enough approximation of) the current time.
-<p>
+</p>
 
 <p>
  Those synchronous function calls normally return almost instantly: there should
diff --git a/doc/libskabus/rpc.html b/doc/libskabus/rpc.html
index c9011c5..b48c295 100644
--- a/doc/libskabus/rpc.html
+++ b/doc/libskabus/rpc.html
@@ -64,7 +64,7 @@ receives a query. Its prototype is
 
 <ul>
  <li> <tt>a</tt> is the handle to the client, to be used when calling the <tt>skabus_rpc_reply()</tt> function
-to send a reply. </tt> </li>
+to send a reply. </li>
  <li> <tt>info</tt> is a pointer to a non-writable <tt>skabus_rpc_rinfo_t</tt> structure containing information
 on the query and the qclient. This structure contains at least the following fields:
   <ul>
diff --git a/doc/skabus-rpcd.html b/doc/skabus-rpcd.html
index 11fe596..0f06a01 100644
--- a/doc/skabus-rpcd.html
+++ b/doc/skabus-rpcd.html
@@ -225,12 +225,12 @@ doing anything. </li>
 should contain a regular expression. The client will be authorized to
 register itself using an identifier that matches that regular
 expression. If the file does not exist, the default behaviour is
-given by the <tt>-S</tt> or </tt>-s</tt> option to skabus-rpcd. </li>
+given by the <tt>-S</tt> or <tt>-s</tt> option to skabus-rpcd. </li>
  <li> The <tt>uid/<em>u</em>/env/SKABUS_RPC_INTERFACES_REGEX</tt> file
 should contain a regular expression. The client will be authorized to
 register interfaces with names that match that regular
 expression. If the file does not exist, the default behaviour is
-given by the <tt>-J</tt> or </tt>-j</tt> option to skabus-rpcd. </li>
+given by the <tt>-J</tt> or <tt>-j</tt> option to skabus-rpcd. </li>
  <li> If the <tt>uid/<em>u</em>/env/SKABUS_RPC_QSENDFDS</tt> file
 exists <em>and is not empty</em>, the client will be allowed to send
 queries containing open file descriptors. If the file exists and is