diff options
| -rw-r--r-- | docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml | 2 |
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 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</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 |