Update doc

doc/BUG-REPORT

@@ -1,5 +1,5 @@
 =====================================================================
-              Eggheads Eggdrop 1.9 Bug Report Form
+              Eggheads Eggdrop 1.10 Bug Report Form
 =====================================================================
 
 By reporting bugs, you help to improve the quality of Eggdrop which
@@ -26,7 +26,7 @@ DO NOT SEND HTML E-MAIL TO THE LISTS.
 1) INFORMATION ABOUT YOUR EGGDROP
 
 1.1) Eggdrop version:
-     1.9._
+     1.10._
 
 1.2) Make type:
      ( ) dynamic
@@ -44,6 +44,7 @@ DO NOT SEND HTML E-MAIL TO THE LISTS.
 2.1) Tcl library version:
      ( ) 8.5._
      ( ) 8.6._
+     ( ) 9.0._
      ( ) Other - Which? ____
 
 2.2) Tcl scripts used:

doc/Changes0.7

@@ -148,7 +148,7 @@ Eggdrop Changes (since version 0.6)
     are stored in -- if not defined, the standard one line responses are
     used -- otherwise, the file "help" is shown for default help, and all
     other help requests are displayed only if there is a corresponding file
-    in the directory (error message ortherwise)
+    in the directory (error message otherwise)
 
   - Default help responses are done through the helpbot if available
 

doc/Changes1.10

@@ -217,7 +217,7 @@ Eggdrop v1.10.0rc1 (2024-08-08):
              * Additional internals doc tweaks
   2024-01-18 * Switch autoscripts to GitHub
   2024-01-15 * change py init from Isolated to Python
-  2024-01-14 * Add Python intpreter to Eggdrop
+  2024-01-14 * Add Python interpreter to Eggdrop
                  [Patch by: Geo, thommey]
              * Update docs
              * Update copyright

doc/Changes1.6

@@ -113,7 +113,7 @@ Eggdrop Changes (since version 1.6.0)
   - Added a new bind LOG triggered when text is sent to the logs.
     Patch by: pseudo
 
-  - Fixed a bug in checking user priviledges for .chaddr on sharebots.
+  - Fixed a bug in checking user privileges for .chaddr on sharebots.
     Patch by: thommey
 
   - Added a new bind CRON as a crontab-like alternative to bind TIME.

doc/Changes1.8

@@ -1184,7 +1184,7 @@ Eggdrop v1.8.1rc1 (2017-03-01):
   - Made some corrections to the contributors list, removed a duplicate entry.
     Patch by: pseudo
 
-  - Fixed bind cron html documention to be in sync with non-html one.
+  - Fixed bind cron html documentation to be in sync with non-html one.
     Found by: 64MAAMVDH / Patch by: thommey
 
   - Replaced most dns.mod preprocessor definitions with config variables.

doc/sphinx_source/_themes/agogo/layout.html

@@ -22,7 +22,7 @@
         <div class="headertitle"><a
           href="{{ pathto(master_doc) }}">{{ shorttitle|e }}</a></div>
         {%- endblock %}
-        <div class="rel" role="navigation" aria-label="related navigation">
+        <div class="rel" role="navigation" aria-label="Related">
           {%- for rellink in rellinks|reverse %}
           <a href="{{ pathto(rellink[0]) }}" title="{{ rellink[1]|striptags|e }}"
              {{ accesskey(rellink[2]) }}>{{ rellink[3] }}</a>
@@ -76,7 +76,7 @@ <h3 style="margin-top: 1.5em;">{{ _('Search') }}</h3>
     <div class="footer-wrapper">
       <div class="footer">
         <div class="left">
-          <div role="navigation" aria-label="related navigaton">
+          <div role="navigation" aria-label="Related">
             {%- for rellink in rellinks|reverse %}
             <a href="{{ pathto(rellink[0]) }}" title="{{ rellink[1]|striptags|e }}"
               {{ accesskey(rellink[2]) }}>{{ rellink[3] }}</a>

doc/sphinx_source/about/about.rst

@@ -1,6 +1,3 @@
-About Eggdrop
-Last revised: July 27, 2010
-
 =============
 About Eggdrop
 =============
@@ -38,10 +35,10 @@ About Eggdrop
   for information on setting up a botnet.
 
   Eggdrop is always being improved and adjusted because there are bugs to
-  be fixed and features to be added (if the users demand  them, and they
-  make actually sense). In fact, it existed for several years as v0.7 -
-  v0.9 before finally going 1.0. This version of Eggdrop is part of the
-  1.9 tree. A valiant effort has been made to chase down and destroy bugs.
+  be fixed and features to be added (if the users demand them, and they
+  make actually sense). In fact, it existed for several years as v0.7 - v0.9
+  before finally going 1.0. This version of Eggdrop is part of the
+  1.10 tree. A valiant effort has been made to chase down and destroy bugs.
 
   To use Eggdrop, you need:
 
@@ -50,8 +47,8 @@ About Eggdrop
     * A pretty good knowledge of IRC and Unix, including how to compile
       programs, how to read, and what DCC chat is, at absolute minimum.
 
-    * About 5-7 MB of disk space. The Eggdrop tarball is about 5.4 MB
-      unpacked.
+    * About 8 MB of disk space for the installed Eggdrop. The Eggdrop
+      tarball is about 10 MB unpacked.
 
     * Tcl -- Eggdrop cannot compile without Tcl installed on your shell.
 

doc/sphinx_source/tutorials/firststeps.rst

@@ -150,15 +150,15 @@ Simple Authentication and Security Layer (SASL) is becoming a prevalant method o
 
 * **PLAIN**: To use this method, set sasl-mechanism to 0. This method passes the username and password (set in the sasl-username and sasl-password config file settings) to the IRC server in plaintext. If you only connect to the IRC server using a connection protected by SSL/TLS this is a generally safe method of authentication; however you probably want to avoid this method if you connect to a server on a non-protected port as the exchange itself is not encrypted.
 
-* **ECDSA-NIST256P-CHALLENGE**: To use this method, set sasl-mechanism to 1. This method uses a public/private keypair to authenticate, so no username/password is required. Not all servers support this method. If your server does support this, you you must generate a certificate pair using::
+* **ECDSA-NIST256P-CHALLENGE**: To use this method, set sasl-mechanism to 1. This method uses a public/private keypair to authenticate, so no username/password is required. Not all servers support this method. If your server does support this, you must generate a certificate pair using::
 
     openssl ecparam -genkey -name prime256v1 -out eggdrop-ecdsa.pem
 
   You will need to determine your public key fingerprint by using::
 
-    openssl ec -noout -text -conv_form compressed -in eggdrop-ecdsa.pem | grep '^pub:' -A 3 | tail -n 3 | tr -d ' \n:' | xxd -r -p | base64
+    openssl ec -noout -text -conv_form compressed -in eggdrop-ecdsa.pem 2>/dev/null | grep '^pub:' -A 3 | tail -n 3 | tr -d ' \n:' | xxd -r -p | base64
 
-  Then, authenticate with your NickServ service and register your public certificate with NickServ. You can view your public key  On Libera for example, it is done by::
+  Then, authenticate with your NickServ service and register your public certificate with NickServ. On Libera for example, it is done by::
 
     /msg NickServ set pubkey <fingerprint string from above goes here>
 
@@ -174,6 +174,10 @@ Then, ensure you have those keys loaded in the ssl-privatekey and ssl-certificat
 
     /msg NickServ cert add <fingerprint string from above goes here>
 
+Alternatively you could connect via ssl and if NickServ supports it, make it automatically determine and add your fingerprint in just the right format:
+
+    /msg NickServ cert add
+
 * **SCRAM-SHA-256**: To use this method, set sasl-mechanism to 3.
 
 * **SCRAM-SHA-512**: To use this method, set sasl-mechanism to 4.

doc/sphinx_source/tutorials/setup.rst

@@ -104,7 +104,7 @@ Below are some of the common settings used for Eggdrop:
 
 :set vhost4: you'll need to set this if you want your bot to use a vhost. This setting lets you choose which IP to use if your shell has multiple. Use vhost4 for an IPv4 address (ie, 1.2.3.4) See also: vhost6
 
-:set vhost6: the same as vhost4, only for IPv6 addresses (ie, 5254:dead:b33f::1337:f270).
+:set vhost6: the same as vhost4, only for IPv6 addresses (ie, 2001:db8:dead:b33f::1337:f270).
 
 :logfile: keeping logs is a good idea. Generally, you should have one log for bot stuff, and one log for each of your channels. To capture bot stuff, add the line ``logfile mcobxs * "botnick.log"`` to the config. To capture channel stuff, add ``logfile jkp #donkeys "#donkeys.log"``, ``logfile jkp #horses "#horses.log"``, etc. Make sure you remove the sample logfile lines for the channel #lamest. If you'd like to put your logfiles in their own directory, specify the directory in the log name (e.g. ``logfile jkp #donkeys "logs/#donkeys.log"`` to write the logfiles in the /logs directory).
 

doc/sphinx_source/using/python.rst

@@ -93,7 +93,7 @@ bind <arguments>
 
 An important difference to note is that Eggdrop Python has its own ``bind`` command implemented. You will generally want to create binds using the Python ``bind`` command and not import bind from eggdrop.tcl because a Python bind will call a Python function, whereas using the Tcl bind will call a Tcl function (not one from the script you are writing).
 
-The python version of the bind command is used to create a bind that triggers a python function. The python bind takes the same arguments as the Tcl binds, but here each argument is passed individually. For example, a bind that would look like ``bind pub * !foo myproc`` in Tcl is written as ``bind("pub", "*", "!foo", myproc)``. For more information on Eggsrop bind argument syntax please see :ref:`bind_types`. The eggdrop.tcl.bind command should not be used as it will attempt to call a Tcl proc.
+The python version of the bind command is used to create a bind that triggers a python function. The python bind takes the same arguments as the Tcl binds, but here each argument is passed individually. For example, a bind that would look like ``bind pub * !foo myproc`` in Tcl is written as ``bind("pub", "*", "!foo", myproc)``. For more information on Eggdrop bind argument syntax please see :ref:`bind_types`. The eggdrop.tcl.bind command should not be used as it will attempt to call a Tcl proc.
 
 The ``bind`` command returns a PythonBind object that has an ``unbind`` method::
 

doc/sphinx_source/using/tcl-commands.rst

@@ -2801,7 +2801,7 @@ botnick
 botname
 ^^^^^^^
 
-  Value: the current nick!user\@host that the server sees (for example: "Valis!valis\@crappy.com")
+  Value: the current nick!user\@host that the server sees (for example: "Valis!valis\@example.net")
 
   Module: server
 

eggdrop-basic.conf

@@ -65,7 +65,7 @@ set username "lamest"
 
 ## This setting defines which contact person should be shown in .status,
 ## /msg help, and other places. You really should include this information.
-set admin "Lamer <email: lamer@lamest.lame.org>"
+set admin "Lamer <email: lamer@lame.example.org>"
 
 ## This setting is used only for info to share with others on your botnet.
 ## Set this to the IRC network your bot is connected to.
@@ -230,7 +230,7 @@ set help-path "help/"
 # a valid IP assigned to the host Eggdrop is running on in front of the port
 # (this replaces the listen-addr setting used prior to Eggdrop v1.9)
 #
-#   listen 1.2.3.4 3333 all
+#   listen 192.0.2.1 3333 all
 #
 # You need to un-comment this line and change the port number in order to open
 # the listen port. You should not keep this set to 3333.

eggdrop.conf

@@ -26,7 +26,7 @@ set username "lamest"
 
 # This setting defines which contact person should be shown in .status,
 # /msg help, and other places. You really should include this information.
-set admin "Lamer <email: lamer@lamest.lame.org>"
+set admin "Lamer <email: lamer@lame.example.org>"
 
 # This setting is used only for info to share with others on your botnet.
 # Set this to the IRC network your bot is connected to.
@@ -295,7 +295,7 @@ set userfile-perm 0600
 # a valid IP assigned to the host Eggdrop is running on in front of the port
 # (this replaces the listen-addr setting used prior to Eggdrop v1.9)
 #
-#   listen 1.2.3.4 3333 all
+#   listen 192.0.2.1 3333 all
 #
 # You need to un-comment this line and change the port number in order to open
 # the listen port. You should not keep this set to 3333.

ssl.conf

@@ -59,8 +59,8 @@ subjectAltName          	= @alt_names
 # Addresses could be hostnames or IPv4/v6 addresses.
 
 DNS.1   			=
-#DNS.2   			= this.bot.net
-#DNS.3   			= lamestbot.net
+#DNS.2   			= example.net
+#DNS.3   			= example.org
 #DNS.4   			= ...
-#IP.1 				= 99.99.0.0
+#IP.1 				= 192.0.2.0
 #IP.2 				= 2001:db8:618:5c0:263::