changed a sentence attempting to make it clearer

diff --git a/docs/manual/spooling.tex b/docs/manual/spooling.tex
index 3bfc927195268c29616126b525a0d75755c566f4..6d1b2175017bb029b684e77bbcde360e5452a135 100644 (file)
--- a/docs/manual/spooling.tex
+++ b/docs/manual/spooling.tex
@@ -28,8 +28,8 @@ substantially improving the time needed  to restore files.
 \end{itemize}
 
 Data spooling is exactly that ``spooling''. It is not a way to first write a
-``backup'' to a disk file and then to a tape. When the backup spooled to disk,
-it is not complete and cannot be restored until it is written to tape. In a
+``backup'' to a disk file and then to a tape. When the backup has only been spooled to disk,
+it is not complete yet and cannot be restored until it is written to tape. In a
 future version, Bacula will support writing a backup to disk then later {\bf
 Migrating} or {\bf Copying} it to a tape. 
 
@@ -86,7 +86,7 @@ Please be very careful to exclude the spool directory from any backup,
 otherwise, your job will write enormous amounts of data to the Volume, and
 most probably terminate in error. This is because in attempting to backup the
 spool file, the backup data will be written a second time to the spool file,
-and so on ad infinum. 
+and so on ad infinitum. 
 
 Another advice is to always specify the maximum spool size so that your disk
 doesn't completely fill up. In principle, data spooling will properly detect a