edits per @betatim @choldgraf review

pull/262/head
Carol Willing 2018-03-15 11:34:39 -07:00
rodzic 8c832d8fae
commit d0d84fdc65
2 zmienionych plików z 5 dodań i 5 usunięć

Wyświetl plik

@ -38,7 +38,7 @@ Example Contents
``requirements.txt``
^^^^^^^^^^^^^^^^^^^^
This specifies a list of Python packages that would be installed in a virtualenv (or conda environment).
This specifies a list of Python packages that should be installed in a virtualenv (or conda environment).
Example Contents
````````````````

Wyświetl plik

@ -86,14 +86,14 @@ The simplest invocation of ``repo2docker`` performs two steps:
1. builds a Docker image from a git repo
2. runs a Jupyter server within the image
This two step process enable you to build an image and run it so you can
This two step process enables you to build an image and run it so you can
explore the repository's contents.
The **command** used is::
juptyer-repo2docker <URL to repo>
juptyer-repo2docker <URL-or-path to repo>
where ``<URL to repo>`` provides a URL to the source repository.
where ``<URL-or-path to repo>`` provides a URL or path to the source repository.
For example, use the following to build an image and launch a Jupyter Notebook
server::
@ -124,7 +124,7 @@ This will print the generated ``Dockerfile``, build it, and run it.
To see the generated ``Dockerfile`` without actually building it,
pass ``--no-build`` to the commandline. This ``Dockerfile`` output
is for **debugging purposes** for ``repo2docker`` only - it can not
is for **debugging purposes** of ``repo2docker`` only - it can not
be used by docker directly.
.. code-block:: bash