--- loncom/html/adm/help/tex/Domain_Crontab_Entries.tex	2008/07/29 17:17:03	1.2
+++ loncom/html/adm/help/tex/Domain_Crontab_Entries.tex	2008/07/29 18:35:33	1.3
@@ -1,4 +1,4 @@
-\label{Domain_Crontab_Entries}
+\{Domain_Crontab_Entries}
 When LON-CAPA is installed a file named loncapa is written to /etc/cron.d.
 The frequency and timing of execution of scripts included in this
 loncapa crontab file can be modified to suit the needs of your domain.
@@ -22,13 +22,12 @@ LON-CAPA, is used to determine the Linux
 the server, which in turn dictates which utility (yum, up2date, you
 or rug) is called to perform the package check.
 \item \emph{/home/httpd/perl/searchcat.pl} run every other day at 1.10 am
-/home/httpd/perl/searchcat.pl This script traverses the LON-CAPA resource
-directory in a domain and gathers metadata which are entered into
-a SQL database. The script will repopulate and refresh the metadata
-database used for the searching the resource catalog. The script also
-refreshes and repopulates database tables used to store metadata for
-publicly accessible portfolio files, and user information needed for
-user searches in a LON-CAPA domain. 
+traverses the LON-CAPA resource directory in a domain and gathers
+metadata which are entered into a SQL database. The script will repopulate
+and refresh the metadata database used for the searching the resource
+catalog. The script also refreshes and repopulates database tables
+used to store metadata for publicly accessible portfolio files, and
+user information needed for user searches in a LON-CAPA domain. 
 \item \emph{/home/httpd/perl/cleanup\_database.pl} run daily at 2.13 am
 drops tables from the LON-CAPA MySQL database if their comment is
 'temporary' and they have not been modified in a given time (default
@@ -45,3 +44,4 @@ first name, last name etc. information s
 data available from an institutional directory. A conduit needs to
 have been established to the institutional data source. 
 \end{itemize}
+