'Spool Data = Yes' sets 'Spool Attributes = Yes'

[bacula/docs] / docs / manual-fr / verify.tex

diff --git a/docs/manual-fr/verify.tex b/docs/manual-fr/verify.tex
index 9ae160adfc6a1145af10015baa8fc05ad602ac54..1c16850fa0f15a7e8aa5a743b6052c4f2ce2bbbb 100644 (file)
--- a/docs/manual-fr/verify.tex
+++ b/docs/manual-fr/verify.tex
@@ -21,7 +21,7 @@ Level = InitCatalog
 \end{verbatim}
 \normalsize
 
-The {\bf InitCatalog} level tells {\bf Bacula} simply get the information on
+The {\bf InitCatalog} level tells {\bf Bacula} simply to get the information on
 the specified files and to put it into the catalog. That is your database is
 initialized and no comparison is done. The {\bf InitCatalog} is normally run
 one time manually. 
@@ -39,7 +39,7 @@ the files on the Client to the last {\bf InitCatalog} that is stored in the
 catalog and to report any differences. See the example below for the format of
 the output. 
 
-You decide what files you want to form your ``snapshot'' by specifying them in
+You decide what files you want to form your "snapshot" by specifying them in
 a {\bf FileSet} resource, and normally, they will be system files that do not
 change, or that only certain features change. 
 
@@ -77,7 +77,7 @@ is cryptographically less secure.
 The {\bf verify=pins1} is ignored during the {\bf InitCatalog} Job, but is
 used during the subsequent {\bf Catalog} Jobs to specify what attributes of
 the files should be compared to those found in the catalog. {\bf pins1} is a
-reasonable set to begin with, but you may want to look at the details these
+reasonable set to begin with, but you may want to look at the details of these
 and other options. They can be found in the 
 \ilink{FileSet Resource}{FileSetResource} section of this manual.
 Briefly, however, the {\bf p} of the {\bf pins1} tells Verify to compare the
@@ -194,7 +194,7 @@ OK to run? (yes/mod/no): yes
 
 at which point you respond {\bf yes}, and the Job will begin. 
 
-There after the Job will automatically start according to the schedule you
+Thereafter the Job will automatically start according to the schedule you
 have defined. If you wish to immediately verify it, you can simply run a
 Verify {\bf Catalog} which will be the default. No differences should be
 found. 
@@ -296,7 +296,7 @@ normal operation of your system, you will get false matches, and you will need
 to modify the {\bf FileSet} to exclude that file (or not to Include it), and
 then re-run the {\bf InitCatalog}. 
 
-The FileSet that is show below is what I use on my RedHat 7.3 system. With a
+The FileSet that is shown below is what I use on my RedHat 7.3 system. With a
 bit more thought, you can probably add quite a number of additional files that
 should be monitored. 
 
@@ -371,4 +371,3 @@ Catalog {
 }
 \end{verbatim}
 \normalsize
-