Many, many changes but no real changes to content nor formatting.

[bacula/docs] / docs / manual / catmaintenance.tex

diff --git a/docs/manual/catmaintenance.tex b/docs/manual/catmaintenance.tex
index 97d2e236069cf7a9e6996518e5a04a2fdb75f10e..17045f8edeeff21ebb1cc2b996644dc251372011 100644 (file)
--- a/docs/manual/catmaintenance.tex
+++ b/docs/manual/catmaintenance.tex
@@ -145,7 +145,7 @@ du bacula
 \normalsize
 
 I get {\bf 620,644} which means there are that many blocks containing 1024
-bytes each or approximately 635 MB of data. After doing the {\bf msqldump}, I
+bytes each or approximately 635 MB of data. After doing the {\bf mysqldump}, I
 had a bacula.sql file that had {\bf 174,356} blocks, and after doing the {\bf
 mysql} command to recreate the database, I ended up with a total of {\bf
 210,464} blocks rather than the original {\bf 629,644}. In other words, the
@@ -153,7 +153,7 @@ compressed version of the database took approximately one third of the space
 of the database that had been in use for about a year. 
 
 As a consequence, I suggest you monitor the size of your database and from
-time to time (once every 6 months or year), compress it. 
+time to time (once every six months or year), compress it. 
 
 \label{DatabaseRepair}
 \label{RepairingMySQL}
@@ -199,7 +199,7 @@ SHOW TABLE STATUS FROM bacula like "File";
 \end{verbatim}
 \normalsize
 
-If the column labeld "Max\_data\_length" is around 4Gb, this is likely
+If the column labeled "Max\_data\_length" is around 4Gb, this is likely
 to be the source of your problem, and you can modify it with:
 
 \footnotesize
@@ -314,7 +314,7 @@ The most important indexes for performance are the three indexes on the
 {\bf File} table.  The first index is on {\bf FileId} and is automatically
 made because it is the unique key used to access the table.  The other
 two are the JobId index and the (Filename, PathId) index.  If these Indexes
-are not present, your peformance may suffer a lot.
+are not present, your performance may suffer a lot.
 
 \subsubsection*{PostgreSQL Indexes}
 On PostgreSQL, you can check to see if you have the proper indexes using
@@ -632,7 +632,7 @@ database after a month can roughly be calculated as:
 \end{verbatim}
 \normalsize
 
-where we have assumed 4 weeks in a month and 26 incremental backups per month.
+where we have assumed four weeks in a month and 26 incremental backups per month.
 This would give the following: 
 
 \footnotesize
@@ -653,7 +653,7 @@ Below are some statistics for a MySQL database containing Job records for five
 Clients beginning September 2001 through May 2002 (8.5 months) and File
 records for the last 80 days. (Older File records have been pruned). For these
 systems, only the user files and system files that change are backed up. The
-core part of the system is assumed to be easily reloaded from the RedHat rpms.
+core part of the system is assumed to be easily reloaded from the Red Hat rpms.
 
 
 In the list below, the files (corresponding to Bacula Tables) with the