[Bacula-commits] docs/manual spooling.tex,1.1.1.1,1.2

[Jo S. <pol...@us...>]

Update of /cvsroot/bacula/docs/manual
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv16414/docs/manual

Modified Files:
	spooling.tex 
Log Message:
changed a sentence attempting to make it clearer


Index: spooling.tex
===================================================================
RCS file: /cvsroot/bacula/docs/manual/spooling.tex,v
retrieving revision 1.1.1.1
retrieving revision 1.2
diff -u -d -r1.1.1.1 -r1.2
--- spooling.tex	13 May 2005 17:22:53 -0000	1.1.1.1
+++ spooling.tex	15 May 2005 11:00:40 -0000	1.2
@@ -28,8 +28,8 @@
 \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 @@
 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