summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKarolin Seeger <kseeger@samba.org>2008-08-05 12:55:20 +0200
committerKarolin Seeger <kseeger@samba.org>2008-08-05 12:55:20 +0200
commit54d8b50904cf1f779f127549471a0ffa8bd97ca8 (patch)
tree10e37c669cdb7173b6cdaa425e0634e40f12cce3
parentd8ae40aa3c565d8e0aa5acfe3f9e58434ce74684 (diff)
downloadsamba-54d8b50904cf1f779f127549471a0ffa8bd97ca8.tar.gz
samba-54d8b50904cf1f779f127549471a0ffa8bd97ca8.tar.bz2
samba-54d8b50904cf1f779f127549471a0ffa8bd97ca8.zip
README.Coding: A few minor fixes.
Karolin (This used to be commit e61c6963cc25883c0b6e7e20596723397e294807)
-rw-r--r--README.Coding6
1 files changed, 3 insertions, 3 deletions
diff --git a/README.Coding b/README.Coding
index fd52dbe890..52ecf0e102 100644
--- a/README.Coding
+++ b/README.Coding
@@ -1,5 +1,5 @@
##
-## Coding conventions in the Samba 3.0 tree
+## Coding conventions in the Samba 3 tree
##
===========
@@ -7,11 +7,11 @@ Quick Start
===========
Coding style guidelines are about reducing the number of unnecessary
-reformatting patches and making things easier developers to work together.
+reformatting patches and making things easier for developers to work together.
You don't have to like them or even agree with them, but once put in place
we all have to abide by them (or vote to change them). However, coding
style should never outweigh coding itself and so the the guidelines
-described here are hopefully easier enough to follow as they are very
+described here are hopefully easy enough to follow as they are very
common and supported by tools and editors.
The basic style, also mentioned in the SAMBA_4_0/prog_guide.txt is the