[SCM] Samba Shared Repository - branch v3-4-test updated - release-4-0-0alpha7-864-g49caab4

Karolin Seeger kseeger at samba.org
Sun May 3 07:40:11 GMT 2009

The branch, v3-4-test has been updated
       via  49caab4044e47236594c6688f202aed555b9da61 (commit)
      from  e178c02a216fefc8295a7fd2d623c888c81f8734 (commit)


- Log -----------------------------------------------------------------
commit 49caab4044e47236594c6688f202aed555b9da61
Author: Karolin Seeger <kseeger at samba.org>
Date:   Sun May 3 09:35:55 2009 +0200

    s3/docs: Fix typo.
    This fixes bug #4245. Thanks to David McNeill <davemc [at] mcpond.co.nz>
    for reporting!
    (cherry picked from commit 579c91581f5b6d5341a12923fe6cde377223caff)


Summary of changes:
 docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

Changeset truncated at 500 lines:

diff --git a/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml b/docs-xml/Samba3-HOWTO/TOSHARG-foreword-cargill.xml
index 6331d2f..b5da92d 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?
 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

Samba Shared Repository

More information about the samba-cvs mailing list