Merge branch 'Branch-5.2' of bsweb:docs into Branch-5.2

diff --git a/docs/manuals/en/main/critical.tex b/docs/manuals/en/main/critical.tex
index ee0d225c0c7f665d5bb71c91c4e2088d81d7a58e..3636ed710deffe88d4364233705d5e46314f6962 100644 (file)
--- a/docs/manuals/en/main/critical.tex
+++ b/docs/manuals/en/main/critical.tex
@@ -77,8 +77,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 88c3170b9077b0f272742975793bb7c2455cdba3..cd9df3c71cb2c8ca096f5b1002431de256446953 100644 (file)
--- a/docs/manuals/en/main/fileset.tex
+++ b/docs/manuals/en/main/fileset.tex
@@ -29,7 +29,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.