Updated documentation now that distutils-scripts are also supported

README.txt

@@ -86,8 +86,8 @@ path. If you run it with a script and script arguments, the script
 will run with the egg in its path.  Of course, you can specify as many
 eggs as you want in the eggs option.
 
-If the egg provides any scripts (console_scripts entry points), those
-will be installed in your bin directory too.
+If the egg provides any scripts (console_scripts entry points or old-style
+distutils scripts), those will be installed in your bin directory too.
 
 Work on a package
 =================

doc/tutorial.txt

@@ -861,9 +861,10 @@ Installing scripts
    If any of the named eggs have ``console_script`` entry
    points, then scripts will be generated for the entry points.
 
-   If a distribution doesn't use setuptools, it may not declare it's
-   entry points. In that case, you can specify entry points in the
-   recipe data.
+   If a distribution doesn't use setuptools, it may not declare it's entry
+   points. In that case, you can specify entry points in the recipe data.
+   Buildout *does attempt* to detect distutils-style scripts without an entry
+   point and will generate a script for them when found.
   
 Script initialization
 =====================

src/zc/buildout/easy_install.txt

@@ -945,6 +945,9 @@ sys.path like for the console_scripts:
     <BLANKLINE>
     print "distutils!"
 
+Due to the nature of distutils scripts, buildout cannot pass arguments as
+there's no specific method to pass them to.
+
 
 Handling custom build options for extensions provided in source distributions
 -----------------------------------------------------------------------------