summaryrefslogtreecommitdiff
path: root/docs/textdocs
diff options
context:
space:
mode:
authorAndrew Bartlett <abartlet@samba.org>2002-06-27 14:23:48 +0000
committerAndrew Bartlett <abartlet@samba.org>2002-06-27 14:23:48 +0000
commit675a108c65834f9402d967926b30e50e811843c1 (patch)
tree1a27d670860e69981732be47f90f8db8ddf3d871 /docs/textdocs
parentb1fd1177aef97e867f7da9fe66093404baa6992c (diff)
downloadsamba-675a108c65834f9402d967926b30e50e811843c1.tar.gz
samba-675a108c65834f9402d967926b30e50e811843c1.tar.bz2
samba-675a108c65834f9402d967926b30e50e811843c1.zip
Jelmer has been keeping on top of the typos.
(This used to be commit 1e36b7e9620f616590dd9f4f44384272b62605ff)
Diffstat (limited to 'docs/textdocs')
-rw-r--r--docs/textdocs/HINTS.txt3
-rw-r--r--docs/textdocs/Printing.txt2
-rw-r--r--docs/textdocs/Tracing.txt2
-rw-r--r--docs/textdocs/UNIX_SECURITY.txt2
4 files changed, 6 insertions, 3 deletions
diff --git a/docs/textdocs/HINTS.txt b/docs/textdocs/HINTS.txt
index 75114557fe..877640108c 100644
--- a/docs/textdocs/HINTS.txt
+++ b/docs/textdocs/HINTS.txt
@@ -49,6 +49,9 @@ windows. Just drag your file onto the icon and it converts the file.
Get it from
ftp://samba.org/pub/samba/contributed/fixcrlf.zip
+The utilities unix2dos and dos2unix(in the mtools package) should do
+the job under unix.
+
----------------------
HINT: Use the "username map" option
diff --git a/docs/textdocs/Printing.txt b/docs/textdocs/Printing.txt
index b47120eaba..2c50e5f4fe 100644
--- a/docs/textdocs/Printing.txt
+++ b/docs/textdocs/Printing.txt
@@ -3,7 +3,7 @@ Revised by: Patrick Powell <papowell@lprng.org>
Date: August 11, 2000
Status: Current
-Subject: Dubugging Printing Problems
+Subject: Debugging Printing Problems
=============================================================================
This is a short description of how to debug printing problems with
diff --git a/docs/textdocs/Tracing.txt b/docs/textdocs/Tracing.txt
index fd65045abd..6cc1d69258 100644
--- a/docs/textdocs/Tracing.txt
+++ b/docs/textdocs/Tracing.txt
@@ -70,7 +70,7 @@ Once you are attached you then can do whatever it is on the client
that is causing problems and you will capture all the system calls
that smbd makes.
-So how do you interpret the results? Generally I search thorugh the
+So how do you interpret the results? Generally I search through the
output for strings that I know will appear when the problem
happens. For example, if I am having touble with permissions on a file
I would search for that files name in the strace output and look at
diff --git a/docs/textdocs/UNIX_SECURITY.txt b/docs/textdocs/UNIX_SECURITY.txt
index d6a0a01acc..38705f018a 100644
--- a/docs/textdocs/UNIX_SECURITY.txt
+++ b/docs/textdocs/UNIX_SECURITY.txt
@@ -32,7 +32,7 @@ directory and do an ls, the UNIX security solution is to
change the UNIX file permissions on the users home directories
such that the cd and ls would be denied.
-Samba tries very had not to second guess the UNIX administrators
+Samba tries very hard not to second guess the UNIX administrators
security policies, and trusts the UNIX admin to set
the policies and permissions he or she desires.