Merge branch 'feature.support_share/bin_and_share/lib' of github.com:wxtim/cylc-doc into feature.support_share/bin_and_share/lib

* 'feature.support_share/bin_and_share/lib' of github.com:wxtim/cylc-doc:
  Update src/user-guide/writing-workflows/runtime.rst
  Update src/user-guide/installing-workflows.rst
  Apply suggestions from code review
  Update src/user-guide/writing-workflows/runtime.rst
  Update src/user-guide/writing-workflows/runtime.rst
  Update src/user-guide/writing-workflows/runtime.rst
  Apply suggestions from code review
  add some extra links
  Update src/user-guide/writing-workflows/configuration.rst

Author: wxtim

src/user-guide/installing-workflows.rst

@@ -398,6 +398,12 @@ The run directory now looks as follows:
    │       └── <time-stamp>-reinstall.log
    └── .service
 
+.. note::
+
+   If your workflow needs to create or install scripts or executables at runtime
+   and you don't want Cylc to delete them on re-installation, you can use
+   ``bin`` and ``lib/python`` directories in the :ref:` workflow share directory <WorkflowShareDirectories>`.
+
 
 Expected Errors
 ---------------

src/user-guide/writing-workflows/configuration.rst

@@ -55,9 +55,11 @@ Other files and folders may be placed in the :term:`source directory` too:
 documentation, configuration files, etc. When the workflow is :ref:`installed
 <Installing-workflows>` these will be copied over to the :term:`run directory`.
 
-If your workflow needs to create or install scripts or executables at runtime
-and you don't want Cylc to delete them on re-installation, you can create
-equivalent directories in the :ref:`WorkflowShareDirectories`.
+.. note::
+
+   If your workflow needs to create or install scripts or executables at runtime
+   and you don't want Cylc to delete them on re-installation, you can use
+   equivalent directories in the :ref:`WorkflowShareDirectories`.
 
 
 .. _SyntaxHighlighting:

src/user-guide/writing-workflows/runtime.rst

@@ -319,15 +319,21 @@ output files are typically held in cycle point sub-directories of this.
 The top level share directory location can be changed, e.g. to a large data
 area, by global config settings under :cylc:conf:`global.cylc[install][symlink dirs]`.
 
-If your workflow creates or installs executables or python libraries
+If your workflow creates or installs executables or Python libraries
 as it is running, these can be placed in:
 
-* ``share/bin`` - for executables.
-* ``share/lib/python`` - for Python modules.
+* ``share/bin/`` - for executables. This location is automatically added to ``PATH``
+  (before the top-level ``bin/`` in the run dir).
+* ``share/lib/python/`` - for Python modules. This location is automatically added
+  to ``PYTHONPATH`` (before the top-level ``lib/python/`` in the run dir).
 
-These folders will be added to ``PATH`` and ``PYTHONPATH`` so they can be
-used by jobs in the same way as
-:ref:`top level "bin/" and "lib/python/" directories <WorkflowDefinitionDirectories>`.
+.. note::
+
+   Cylc will not create these folders.
+   
+.. seealso::
+
+   :ref:`Top level "bin/" and "lib/python/" directories <WorkflowDefinitionDirectories>`.
 
 
 Task Work Directories