From: Kern Sibbald <kern@sibbald.com>
Date: Sun, 17 Feb 2013 12:05:33 +0000 (+0100)
Subject: Fix typos reported in bug #1968
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=9d33d79cc110f1e64238ef89e858ed00da64620d;p=bacula%2Fdocs

Fix typos reported in bug #1968
---

diff --git a/docs/manuals/en/main/critical.tex b/docs/manuals/en/main/critical.tex
index 48d4624c..65105434 100644
--- 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 2184da4c..283df4d9 100644
--- 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.