diff --git a/zc.recipe.egg_/README.txt b/zc.recipe.egg_/README.txt
index 5b53fb986824b8fe920d055c4529963553a90850..7ed986a0d2b5e34c11127a4eec91d058a89dc8e6 100644
--- a/zc.recipe.egg_/README.txt
+++ b/zc.recipe.egg_/README.txt
@@ -26,12 +26,6 @@ index
 python
     The name of a section defining the Python executable to use.
     This defaults to buildout.
-    
-unzip
-   The value of this option must be either true or false. If the value
-   is true, then the installed egg will be unzipped. Note that this is
-   only effective when an egg is installed.  If a zipped egg already 
-   exists in the eggs directory, it will not be unzipped.
 
 scripts
    Control which scripts are generated.  The value should be a list of
diff --git a/zc.recipe.egg_/src/zc/recipe/egg/README.txt b/zc.recipe.egg_/src/zc/recipe/egg/README.txt
index edff0c6820e536414c57c5c136cd28341f402813..2eecea3509ee25a2f007bea1537ab3941df3d794 100644
--- a/zc.recipe.egg_/src/zc/recipe/egg/README.txt
+++ b/zc.recipe.egg_/src/zc/recipe/egg/README.txt
@@ -29,12 +29,6 @@ python
    Python executable is found in the executable option of the named
    section. 
 
-unzip
-   The value of this option must be either true or false. If the value
-   is true, then the installed egg will be unzipped. Note that this is
-   only effective when an egg is installed.  If a zipped egg already 
-   exists in the eggs directory, it will not be unzipped.
-
 scripts
    Control which scripts are generated.  The value should be a list of
    zero or more tokens.  Each token is either a name, or a name
@@ -141,20 +135,16 @@ specification. For example, We remove the restriction on demo:
     ... recipe = zc.recipe.egg
     ... find-links = %(server)s
     ... index = %(server)s/index
-    ... unzip = true
     ... """ % dict(server=link_server))
 
-We also used the unzip uption to request a directory, rather than
-a zip file.
-
     >>> print system(buildout),
 
 Then we'll get a new demo egg:
 
     >>> ls(sample_buildout, 'eggs')
     -  demo-0.2-py2.3.egg
-    d  demo-0.3-py2.3.egg
-    d  demoneeded-1.0-py2.3.egg
+    -  demo-0.3-py2.3.egg
+    -  demoneeded-1.0-py2.3.egg
 
 Note that we removed the eggs option, and the eggs
 defaulted to the part name.
diff --git a/zc.recipe.egg_/src/zc/recipe/egg/api.txt b/zc.recipe.egg_/src/zc/recipe/egg/api.txt
index 31143beb70b2d2cf2368af30cd78219b981529f5..9735c61cecd0a9cc45c866f1f26d55b603749a32 100644
--- a/zc.recipe.egg_/src/zc/recipe/egg/api.txt
+++ b/zc.recipe.egg_/src/zc/recipe/egg/api.txt
@@ -6,7 +6,7 @@ and generate scripts based on the resulting working sets.  The egg
 recipe provides an API that other recipes can use.
 
 A recipe can reuse the egg recipe, supporting the eggs, find-links,
-index, python, and unzip options.  This is done by creating an egg
+index, and pythonoptions.  This is done by creating an egg
 recipe instance in a recipes's contructor.  In the recipe's install
 script, the egg-recipe instance's working_set method to collect the
 requested eggs and working set.