From 54e25e1fbfcb0141c866d9811da883b4f8197f43 Mon Sep 17 00:00:00 2001 From: Karolin Seeger Date: Sun, 3 May 2009 09:35:55 +0200 Subject: [PATCH] s3/docs: Fix typo. This fixes bug #4245. Thanks to David McNeill for reporting! Karolin (cherry picked from commit 579c91581f5b6d5341a12923fe6cde377223caff) (cherry picked from commit 49caab4044e47236594c6688f202aed555b9da61) (cherry picked from commit 139f95c85f96e7ccba024283608f9ee5990f6676) (cherry picked from commit 148aa12c89df78718addd7b72c79a8005e680509) (cherry picked from commit c36d3dae4740529427ea5ee5b77ad687de371d9c) --- docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml index 6331d2fd4e3..b5da92d5b7e 100644 --- a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml +++ b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml @@ -38,7 +38,7 @@ know, why are you doing a standard? A good standard 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 -- 2.34.1