1 files changed, 9 insertions, 8 deletions

diff --git a/slack_last_update.sh b/slack_last_update.sh
index 1f04cb6..eb32b23 100755
--- a/slack_last_update.sh
+++ b/slack_last_update.sh
@@ -1,7 +1,7 @@
 #!/bin/sh
 
-# Get last update time from Slackware ChangeLog, print the date to
-# stdout in the form used by the ##slackware /topic. For now anyway,
+# Get last update time from Slackware ChangeLog, print the date to stdout
+# in the form used by the ##slackware /topic (YYYY-MM-DD). For now anyway,
 # we assume everything in the ChangeLog is a security fix.
 
 # Also, the output is compared to $DATEFILE if it exists. Exit
@@ -15,10 +15,10 @@
 # it depends on what the error actually was.
 
 # This script can be tested from the command line, but in production it
-# will be executed from an irssi script, so it's got no need for options
-# or verbose output. Actually, the irssi script currently doesn't even
-# look at the exit status (other than to check for an error), so even
-# that could be removed to simplify things.
+# was intended to be executed from an irssi script, so it's got no need
+# for options or verbose output. Actually, the irssi script no longer
+# uses this, it's kept around purely for reference, or in case it might
+# be useful for some other project.
 
 # For the morbidly curious: I intend this to be executed by bash,
 # but it also works with Slackware 14.2's ash and ksh, and dash from
@@ -28,9 +28,10 @@
 # and quite properly complains:
 #   curl: option --range 0-28: is unknown
 # I'm not a zsh guy, but I did some research... either have to use the
-# syntax $=range (zsh-specific) or check for ZSH_* in the environment
+# syntax $=RANGE (zsh-specific) or check for ZSH_* in the environment
 # and do 'setopt shwordsplit'. Pretty sure this means I shall never
-# again care whether one of my shell scripts fails on zsh.
+# again care whether one of my shell scripts fails on zsh. Pretty sure
+# this means zsh isn't POSIX compliant, and isn't trying to be.
 
 ### Config stuff.