Update docs to use `pex $(pip freeze)`
As mentioned in `pex $(pip freeze)` should be used instead of `pex -r <(pip freeze)`. The README was updated, but the docs site was not.
@@ -95,12 +95,17 @@ You can then import and manipulate modules like you would otherwise:
>>> import psutil
>>> ...
-Requirements can also be specified using the requirements.txt format, using ``pex -r``. This can be a handy
-way to freeze a virtualenv into a PEX file:
+Conveniently, the output of ``pip freeze`` (a list of pinned dependencies) can be passed directly to ``pex``. This provides a handy way to freeze a virtualenv into a PEX file.
.. code-block:: console
- $ pex -r <(pip freeze) -o my_application.pex
+ $ pex $(pip freeze) -o my_application.pex
+
+A ``requirements.txt`` file may also be used, just as with ``pip``.
+
+.. code-block:: console
+
+ $ pex -r requirements.txt -o my_application.pex
Specifying entry points
