-# longer form spelling out the positions. these are optionally plural because cron allows for multiple entries in different forms.
-# minute(s) hour(s) dayOfMonth(s) month(s) dayOfWeek(s) command
-
-# set a user name for writing unique log files. this is important because crontab doesn't have USER defined,
-# although we can count on HOME being defined, luckily.
-# you may want to use a more appropriate user name than mine, which is "fred".
-USER=fred
-
-# the guts of the crontab would go here. it would spell out some time or times for the command to be executed.
-# it's actually okay to have a really long command with multiple sub-commands; just put it inside parentheses to group
-# a bunch of commands together. there are many examples of doing this in the other files.
-# also, it's often important to send the output someplace. /dev/null works if you don't ever want to see it, but i
-# prefer to write log files in the /tmp directory which include the user name defined above.
+# the wildcard '*' indicates that every valid value is okay for that field.
+# the wildcard form of a crontab line is this: "* * * * * command"
+# that "command" will execute every single minute.
+
+# the guts of the crontab would follow below. this usually is a set of valid
+# crontab lines that spell the time or times for commands to be executed. my
+# crontabs usually have from 3 to 8 entries because i tend to atomicize the
+# tasks, rather than writing big complicated multi-purpose scripts. not saying
+# that's always better, it's just how i roll (my crontabs)...
+#
+# also, it is fine to have a really long command with multiple sub-commands;
+# just put it inside parentheses to group a bunch of commands together. there
+# are many examples of doing this in the other crontab examples in this folder.
+#
+# further, it's often important to send the output from the cron job to an
+# output location. doing this keeps cron from sending you a lot of emails
+# with cron job output on some systems. you can use the normal output
+# redirection operators to do this (e.g. '>', '2>', '&>', '>>' and '&>>').
+# /dev/null works as an output target if you don't ever want to see the
+# results from your cron jobs. i usually prefer to write log files in the
+# /tmp directory with the ${CRONUSER} variable added in the file name.
+# below is a live example which we almost always include, so it's embedded
+# here for convenience.
+
+##############