Fix typos reported in bug #1968

diff --git a/docs/manuals/en/main/critical.tex b/docs/manuals/en/main/critical.tex
index 48d4624cc425b324d2ce9ed6f7f171eb01c47e8f..65105434654dfc052e3579cdf75ba3bb85dcfdc4 100644 (file)
--- a/docs/manuals/en/main/critical.tex
+++ b/docs/manuals/en/main/critical.tex
@@ -78,8 +78,8 @@ production, use the checklist anyway).
    when saving the filenames to the catalog. For Win32 machine, Bacula will
    automatically convert from Unicode to UTF-8, but on Unix, Linux, *BSD,
    and MacOS X machines, you must explicitly ensure that your locale is set
-   properly. Typically this means that the {bf LANG} environment variable
-   must end in {\bf .UTF-8}. An full example is {\bf en\_US.UTF-8}. The
+   properly. Typically this means that the {\bf LANG} environment variable
+   must end in {\bf .UTF-8}. A full example is {\bf en\_US.UTF-8}. The
    exact syntax may vary a bit from OS to OS, and exactly how you define it
    will also vary.
 

diff --git a/docs/manuals/en/main/fileset.tex b/docs/manuals/en/main/fileset.tex
index 2184da4c2ee088ca24c95e5b6c2830f4785a4d90..283df4d96af569b55db0410ac3895c856c7a551e 100644 (file)
--- a/docs/manuals/en/main/fileset.tex
+++ b/docs/manuals/en/main/fileset.tex
@@ -26,7 +26,7 @@ On most modern Win32 machines, you can edit the conf files with {\bf
 notebook} and choose output encoding UTF-8.
 
 To ensure that Bacula configuration files can be correctly read including
-foreign characters the {bf LANG} environment variable
+foreign characters the {\bf LANG} environment variable
 must end in {\bf .UTF-8}. A full example is {\bf en\_US.UTF-8}. The
 exact syntax may vary a bit from OS to OS, and exactly how you define
 it will also vary.