svn commit: r1821573 - /incubator/taverna/site/trunk/content/documentation/server/3.1/install.md

[st...@apache.org]

Author: stain
Date: Fri Jan 19 00:32:44 2018
New Revision: 1821573

URL: http://svn.apache.org/viewvc?rev=1821573&view=rev
Log:
hmm..

Modified:
    incubator/taverna/site/trunk/content/documentation/server/3.1/install.md

Modified: incubator/taverna/site/trunk/content/documentation/server/3.1/install.md
URL: http://svn.apache.org/viewvc/incubator/taverna/site/trunk/content/documentation/server/3.1/install.md?rev=1821573&r1=1821572&r2=1821573&view=diff
==============================================================================
--- incubator/taverna/site/trunk/content/documentation/server/3.1/install.md (original)
+++ incubator/taverna/site/trunk/content/documentation/server/3.1/install.md Fri Jan 19 00:32:44 2018
@@ -147,7 +147,8 @@ This is a list of all the properties tha
 
 - Those used to control how many runs exist and are operating at once. The default.runlimit and default.operatinglimit have reasonable initial values, but must be tuned according to the actual expected workload. They can be set at runtime via the administration web interface and via JMX.
 
-- Those used to enable optional notification mechanisms; those are all disabled by default unless the required extra properties are set (see below for instructions).
+- Those used to enable optional notification mechanisms; those are all disabled by default unless the required extra properties are set (see below).
+
 
     # Script in Taverna installation to run to actually execute workflows
     executeWorkflowScript:      /usr/taverna/executeworkflow.sh
@@ -250,6 +251,7 @@ This is a list of all the properties tha
     # Leave at false unless you have been specifically told otherwise.
     helio.cis.enableTokenPassing:   false
 
+
 #### Enabling Notification Options
 
 With the exception of the Atom feed, all the notification methods supported by Taverna Server are *disabled* by default. They require additional configuration in order to work correctly. This is done through configuration options. Only once all options for a particular notification method are set will Taverna Server enable that method for use. Note that many of these methods require additional services to be deployed or accounts with remote services to be created.