PLD-doc: devel-hints-en.txt - cleanups in "Naming files in SOURCES"

[saq]

Author: saq                          Date: Wed Oct  5 13:46:30 2005 GMT
Module: PLD-doc                       Tag: HEAD
---- Log message:
- cleanups in "Naming files in SOURCES"

---- Files affected:
PLD-doc:
   devel-hints-en.txt (1.21 -> 1.22) 

---- Diffs:

================================================================
Index: PLD-doc/devel-hints-en.txt
diff -u PLD-doc/devel-hints-en.txt:1.21 PLD-doc/devel-hints-en.txt:1.22
--- PLD-doc/devel-hints-en.txt:1.21	Sun Oct  2 17:30:28 2005
+++ PLD-doc/devel-hints-en.txt	Wed Oct  5 15:46:25 2005
@@ -596,11 +596,11 @@
 
 Naming files in SOURCES.
 
-few unexplained conventions:
+A few unjustified conventions:
 - NAME-foo.patch - patches
 - NAME.cron - cron fragments which go to /etc/cron.d dir
-- NAME.logrotate - logrotate config whichgoes to /etc/logrotate.d
-- NAME.sysconfig - application cofing which goes to /etc/sysconfig
+- NAME.logrotate - logrotate config which goes to /etc/logrotate.d
+- NAME.sysconfig - application config which goes to /etc/sysconfig
 - NAME.init - initscript which goes to /etc/rc.d/init.d
 
 NAME could be package %{name} or real name of package if it's prefixed with
@@ -608,11 +608,11 @@
 patches sources prefixed with package name also avoids file collisions between
 different packages.
 
-one of the reasons is because it's convinient to vi ../SOURCES/NAME-<TAB> to
+One of the reasons is because it's convinient to vi ../SOURCES/NAME-<TAB> to
 get list of patches and vi ../SOURCES/NAME.<TAB> to get your shell expand
 config files.
 
-please try to follow this, as then if there's planned massive changes to all
+Please try to follow this, as then if there's planned massive changes to all
 crontab, initscript or sysconfig files, then the files are easily located from
 CVS.
 
================================================================

---- CVS-web:
    http://cvs.pld-linux.org/PLD-doc/devel-hints-en.txt?r1=1.21&r2=1.22&f=u