Some minor changes in the beginning. Some larger changes in the text

contributed by other people.

diff --git a/docs/manual/tips.tex b/docs/manual/tips.tex
index ec2c4a78f5ef39a5ddd21e28d76a69cf59f86d6a..2de0d06fd5695a422f04f9a2b1d9040ea4a223dd 100644 (file)
--- a/docs/manual/tips.tex
+++ b/docs/manual/tips.tex
@@ -23,7 +23,7 @@ distribution.
 \addcontentsline{toc}{subsection}{Upgrading Bacula Versions}
 
 The first thing to do before upgrading from one version to another is to
-ensure that don't overwrite or delete your production (current) version of Bacula until
+ensure that you don't overwrite or delete your production (current) version of Bacula until
 you have tested that the new version works. 
 
 If you have installed Bacula into a single directory, this is simple: simply
@@ -92,7 +92,7 @@ Messages {
 \normalsize
 
 You will need to ensure that the {\bf /home/bacula/bin} path on the {\bf
-mailcommand} and the {\bf operatorcommand} lines points to your {\bf Bacula}
+mailcommand} and the {\bf operatorcommand} lines point to your {\bf Bacula}
 binary directory where the {\bf bsmtp} program will be installed. You will
 also want to ensure that the {\bf your-email-address} is replaced by your
 email address, and finally, you will also need to ensure that the {\bf
@@ -233,7 +233,7 @@ get {\bf Watchdog} and referencing \$2 would get {\bf main-dir}. In this case,
 having the script know the Client and Director's name is not really useful,
 but in other situations it may be. 
 
-You can put anything in the watchdog scrip. In my case, I like to monitor the
+You can put anything in the watchdog script. In my case, I like to monitor the
 size of my catalog to be sure that {\bf Bacula} is really pruning it. The
 following is my watchdog script: 
 
@@ -562,7 +562,7 @@ Now lets consider the case:
 \normalsize
 
 Here the Bacula found fewer files on the volume than what is marked in the
-catalog. Now, in this case, you should hesitate lot before modifying the count
+catalog. Now, in this case, you should hesitate a lot before modifying the count
 in the catalog, because if you force the catalog from 12 to 10, Bacula will
 start writing after the file 10 on the tape, possibly overwriting valid data,
 and if you ever try to restore any of the files that the catalog has marked as
@@ -740,7 +740,7 @@ Pool: Default
 \normalsize
 
 Note, I have truncated the output for presentation purposes. What is
-significant for is that I can see that my current tape has almost 10 Gbytes of
+significant, is that I can see that my current tape has almost 10 Gbytes of
 data, and that the average amount of data I get on my tapes is about 60
 Gbytes. So if I go on vacation now, I don't need to worry about tape capacity
 (at least not for short absences). 
@@ -788,10 +788,10 @@ records, but the technique still could be useful.) First I thought the ``Run
 Before Job'' statement in the Job-resource is for executing a script on the
 remote machine(the machine to be backed up). It could be usefull to execute
 scripts on the remote machine e.g. for stopping databases or other services
-while doing the backup. (Of cause I have to start the services again when the
+while doing the backup. (Of course I have to start the services again when the
 backup has finished) I found the following solution: Bacula could execute
 scrips on the remote machine by using ssh. The authentication is done
-automatically using a private key. First You have to generate a keypair. I ve
+automatically using a private key. First You have to generate a keypair. I've
 done this by: 
 
 \footnotesize
@@ -801,7 +801,7 @@ ssh-keygen -b 4096 -t dsa -f Bacula_key
 \normalsize
 
 This statement may take a little time to run. It creates a public/private key
-pair with no pass phrase. You could save the keys in /etc/bacula. Now you have
+pair with no passphrase. You could save the keys in /etc/bacula. Now you have
 two new files : Bacula\_key which contains the private key and Bacula\_key.pub
 which contains the public key. 
 
@@ -819,7 +819,7 @@ to the sshd\_config file on the remote machine. Where the \%h stands for the
 home-directory of the user (root in this case). 
 
 Assuming that your sshd is already running on the remote machine, you can now
-enter the folloing on the machine where Bacula runs: 
+enter the following on the machine where Bacula runs: 
 
 \footnotesize
 \begin{verbatim}
@@ -855,7 +855,7 @@ in a single script.
 This tip comes from Phil Stracchino. 
 
 If you decide to blow away your catalog and start over, the simplest way to
-re-add all your prelabelled tapes with the minimum of fuss (provided you don't
+re-add all your prelabeled tapes with a minimum of fuss (provided you don't
 care about the data on the tapes) is to add the tape labels using the console
 {\bf add} command, then go into the catalog and manually set the VolStatus of
 every tape to {\bf Recycle}. 
@@ -960,8 +960,8 @@ Device {
 \normalsize
 
 As the script has to emulate the complete wisdom of a mtx-changer it has an
-internal ``database'' where which tape is stored, you can see this at that
-line:
+internal ``database'' containing where which tape is stored, you can see this on
+the following line:
 
 \footnotesize
 \begin{verbatim}