summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarolin Seeger <kseeger@samba.org>2009-05-03 09:35:55 +0200
committerKarolin Seeger <kseeger@samba.org>2009-05-03 09:37:35 +0200
commit579c91581f5b6d5341a12923fe6cde377223caff (patch)
tree5230c2089b5c70c0ae8e44aefe52bdfda0abd878
parent8f3a9b3c0f32573508424b5480ca077450322ebd (diff)
downloadsamba-579c91581f5b6d5341a12923fe6cde377223caff.tar.gz
samba-579c91581f5b6d5341a12923fe6cde377223caff.tar.bz2
samba-579c91581f5b6d5341a12923fe6cde377223caff.zip
s3/docs: Fix typo.
This fixes bug #4245. Thanks to David McNeill <davemc [at] mcpond.co.nz> for reporting! Karolin
-rw-r--r--docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
index 6331d2fd4e..b5da92d5b7 100644
--- a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
+++ b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
@@ -38,7 +38,7 @@ know</emphasis>, why are you doing a standard?
<para>
A <emphasis>good standard</emphasis> survives because people know how to use it. People know how to use a
-standard when it is so transparent, so obvious, and so easy that it become invisible. And a standard becomes
+standard when it is so transparent, so obvious, and so easy that it becomes invisible. And a standard becomes
invisible only when the documentation describing how to deploy it is clear, unambiguous, and correct. These
three elements must be present for a standard to be useful, allowing communication and interaction between two
separate and distinct entities to occur without obvious effort. As you read this book, look for the evidence