[NAntC-cvs] NAntContrib readme.txt,1.8,1.9

[<dri...@us...>]

Update of /cvsroot/nantcontrib/NAntContrib
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2030

Modified Files:
	readme.txt 
Log Message:
minor corrections

Index: readme.txt
===================================================================
RCS file: /cvsroot/nantcontrib/NAntContrib/readme.txt,v
retrieving revision 1.8
retrieving revision 1.9
diff -C2 -d -r1.8 -r1.9
*** readme.txt	10 Dec 2004 07:36:00 -0000	1.8
--- readme.txt	10 Dec 2004 07:39:57 -0000	1.9
***************
*** 22,26 ****
  </project>
  
! In order to avoid updating all build file when you move the NAnt.Contrib.Tasks assembly to another
  directory, you could register the directory containing the NAnt.Contrib.Tasks assembly in an 
  environment variable and then use the value of that environment variable in your build files.
--- 22,26 ----
  </project>
  
! In order to avoid updating all build files when you move the NAnt.Contrib.Tasks assembly to another
  directory, you could register the directory containing the NAnt.Contrib.Tasks assembly in an 
  environment variable and then use the value of that environment variable in your build files.
***************
*** 54,60 ****
  3. Modify NAnt configuration file (not recommended)
  
! An <include> element can be added to the <task-assemblies> node in the <framework> node of all
! .NET Framework versions that you intend to use. The "name" attribute of the <include> element 
! would hold the full path to NAnt.Contrib.Tasks.dll.
  
  For example:
--- 54,60 ----
  3. Modify NAnt configuration file (not recommended)
  
! An <include> element can be added to the <task-assemblies> node in the <framework> node for the
! .NET Framework version that you intend to use. The "name" attribute of the <include> element 
! should hold the absolute path to NAnt.Contrib.Tasks.dll.
  
  For example: