documentation: pip2nix -> pip2nix generate

README.rst

@@ -39,11 +39,9 @@ Usage
 
 To generate python-packages.nix for a set of requirements::
 
-    $ pip2nix -r requirements.txt
+    $ pip2nix generate -r requirements.txt
 
-``pip2nix`` takes the same set of package specifications ``pip install`` does.
-
-At the moment the --help lies - it's not only showing the ``pip2nix`` options, but also ``pip`` ones (that are not always relevant). (TODO: `#14 <https://github.com/ktosiek/pip2nix/issues/14>`_)
+``pip2nix generate`` takes the same set of package specifications ``pip install`` does.
 
 Contact
 =======

bootstrap.sh

@@ -37,4 +37,4 @@ if [ "$FORCE_REBUILD" -o \
     touch ./_bootstrap_env/.done
 fi
 
-./_bootstrap_env/bin/pip2nix
+./_bootstrap_env/bin/pip2nix generate

docs/getting_started.rst

@@ -14,9 +14,9 @@ Ad-hoc python-packages.nix generation
 
 To generate python-packages.nix for a set of requirements::
 
-    $ pip2nix -r requirements.txt
+    $ pip2nix generate -r requirements.txt
 
-``pip2nix`` takes the same set of package specifications ``pip install`` does.
+``pip2nix generate`` takes the same set of package specifications ``pip install`` does.
 It understands ``-r``, git links, package specifications, and ``-e`` (which is just ignored).
 
 Using pip2nix in a project
@@ -28,5 +28,5 @@ To do that, you can create a ``pip2nix.ini`` file::
     [pip2nix]
     requirements = -r ./requirements.txt
 
-This way you can only run ``pip2nix`` in the project's root.
+This way you can just run ``pip2nix generate`` in the project's root.
 More about the configuration file in :doc:`configuration`.