From e759a3d3b28c75317798f73a153f596cf1afdb00 Mon Sep 17 00:00:00 2001
From: Laurent Bercot <ska-skaware@skarnet.org>
Date: Mon, 26 Jan 2026 01:11:33 +0000
Subject:  Doc typo fixes

---
 doc/cgiwrapper-nollmcrawler.html | 4 ++--
 doc/tipidee.conf.html            | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/doc/cgiwrapper-nollmcrawler.html b/doc/cgiwrapper-nollmcrawler.html
index 3fa5d2b..2b2104c 100644
--- a/doc/cgiwrapper-nollmcrawler.html
+++ b/doc/cgiwrapper-nollmcrawler.html
@@ -114,14 +114,14 @@ efficiency is important. Implementing a ban with just a <tt>symlink()</tt> is ef
 <ul>
  <li> cgiwrapper-nollmcrawler expects to be run by tipideed as a CGI program,
 as a wrapper around <em>realcgi...</em>.
- <li> e.g. if the URL you want to protect is <tt>https://example.com/cgit.cgi</tt>,
+ <li> E.g. if the URL you want to protect is <tt>https://example.com/cgit.cgi</tt>,
 and <tt>cgit.cgi</tt> is a direct cgit binary, then the way to protect it is:
  <ul>
   <li> Move <tt>cgit.cgi</tt> to <tt>cgit.cgi-real</tt> and <em>never link this resource anywhere</em>. </li>
   <li> Write a script (shell, execline, whatever language you want) standing in for <tt>cgit.cgi</tt>
 that execs into cgiwrapper-nollmcrawler with <tt>cgit.cgi-real</tt> as its last argument. Make it executable. </li>
  </ul> </li>
- <li> cgiwrapper-nollmcrawler is typically be used to protect cgit, but it can
+ <li> cgiwrapper-nollmcrawler is typically used to protect cgit, but it can
 protect any backend that uses CGI as its interface and has deep URLs with easily
 identifiable query strings. </li>
 </ul>
diff --git a/doc/tipidee.conf.html b/doc/tipidee.conf.html
index 581b05f..0fa6ac7 100644
--- a/doc/tipidee.conf.html
+++ b/doc/tipidee.conf.html
@@ -914,7 +914,7 @@ should generally only be used when tipideed is <em>not</em> chrooted. </li>
 domain socket at address <em>ip</em>, port <em>port</em>. <em>ip</em> can be IPv4
 or IPv6. </li>
   </ul> </li>
- <li> Just like with the <code>redirection</code> directive,
+ <li> Just like with the <code>redirect</code> directive,
 <em>resource</em> does not need to exist in the filesystem. The same caveats apply. </li>
 </ul>
 
-- 
cgit v1.3.1