Suggested text changes.

Author: mimischi

README.rst

@@ -35,7 +35,7 @@ resources. It tries to make it as easy as possible to set up systems on varying
 numbers of nodes and compare their performances to each other.
 
 You can also create a plot to get a quick overview of the possible performance
-(and also show of to your friends)! The plot below shows the performance of an
+(and also show of to your friends)! The plot below shows the performance of a
 molecular dynamics system on up to five nodes with and without GPUs.
 
 .. image:: https://raw.githubusercontent.com/bio-phys/MDBenchmark/master/docs/_static/runtimes.png
@@ -125,10 +125,11 @@ produce a ``.csv`` output file or a plot for direct usage (via the ``--plot``
 option).
 
 **Note:** The plotting function currently only allows to plot a CPU and GPU
-benchmark from the *same* module. This will be fixed in an upcoming version. If
-you want to compare different modules with each other, either use the
-``--directory`` option to generate separate plots or create your own plot from
-the provided CSV file.
+benchmark from the *same* module. This will be fixed in an upcoming version and
+is already implemented in the `develop
+<https://github.com/bio-phys/MDBenchmark/tree/develop>`_ branch. If you want to
+compare different modules with each other, either use the ``--directory`` option
+to generate separate plots or create your own plot from the provided CSV file.
 
 .. code::
 

docs/general.rst

@@ -80,7 +80,9 @@ Usage with multiple modules
 ---------------------------
 
 You can use this feature to compare multiple versions of one MD engine or
-different MD engines with each other::
+different MD engines with each other. Note that the base name for the GROMACS
+and NAMD files (see above) must to be the same, e.g., `protein.tpr` and
+`protein.namd`.
 
   mdbenchmark generate --name protein --module namd/2.12 --module gromacs/2016.4
 

docs/index.rst

@@ -46,7 +46,7 @@ Quick start
 
 Follow the next two paragraphs to get a quick start. Extended usage guides can
 be found below. You can install ``mdbenchmark`` with your favorite Python
-package manager. Afterwards you are ready to go and use ``mdbenchmark``.
+package manager. Afterwards you are ready to use ``mdbenchmark``.
 
 Install
 -------

docs/jobtemplates.rst

@@ -1,9 +1,13 @@
 Defining host templates
 =======================
 
-It is possible to define your own host templates in addition to the ones shipped
-with the package. A template file should have the same filename as the UNIX
-command ``hostname`` returns to be detected automatically. Otherwise you can
+You can create your own host templates in addition to the ones shipped with the
+MDBenchmark. We use the ``jinja2`` Python package for these host templates.
+Please refer to the `official Jinja2 documentation <http://jinja.pocoo.org/>`
+for further information on formatting and functionality.
+
+To be detected automatically, a template file must have the same filename as
+returned by the UNIX command ``hostname``. If this is not the case, you can
 point MDBenchmark to a specific template by providing its name via the
 ``--host`` option.
 

docs/submit.rst

@@ -13,6 +13,12 @@ current directory, use::
 
   mdbenchmark submit
 
+.. note::
+
+   ``mdbenchmark submit`` will currently submit all benchmarks in the current
+   folder and its subdirectory without confirmation. Use the ``--directory``
+   option to limit this behavior.
+
 Submitting specific benchmarks separately
 -----------------------------------------