Github user jtstorck commented on a diff in the pull request:
https://github.com/apache/nifi/pull/3080#discussion_r225654613
--- Diff: nifi-docs/src/main/asciidoc/user-guide.adoc ---
@@ -636,21 +637,24 @@ For example:
For additional information and examples, see the
link:http://www.quartz-scheduler.org/documentation/quartz-2.x/tutorials/crontrigger.html[Chron
Trigger Tutorial^] in the Quartz documentation.
+===== Concurrent Tasks
Next, the Scheduling Tab provides a configuration option named 'Concurrent
Tasks'. This controls how many threads the Processor
will use. Said a different way, this controls how many FlowFiles should be
processed by this Processor at the same time. Increasing
this value will typically allow the Processor to handle more data in the
same amount of time. However, it does this by using system
resources that then are not usable by other Processors. This essentially
provides a relative weighting of Processors -- it controls
how much of the system's resources should be allocated to this Processor
instead of other Processors. This field is available for
most Processors. There are, however, some types of Processors that can
only be scheduled with a single Concurrent task.
+===== Run Schedule
The 'Run Schedule' dictates how often the Processor should be scheduled to
run. The valid values for this field depend on the selected
Scheduling Strategy (see above). If using the Event driven Scheduling
Strategy, this field is not available. When using the Timer driven
Scheduling Strategy, this value is a time duration specified by a number
followed by a time unit. For example, `1 second` or `5 mins`.
The default value of `0 sec` means that the Processor should run as often
as possible as long as it has data to process. This is true
for any time duration of 0, regardless of the time unit (i.e., `0 sec`, `0
mins`, `0 days`). For an explanation of values that are
applicable for the CRON driven Scheduling Strategy, see the description of
the CRON driven Scheduling Strategy itself.
-When configured for clustering, an Execution setting will be available.
This setting is used to determine which node(s) the Processor will be
+===== Execution
+The Execution setting is used to determine which node(s) the Processor
will be
--- End diff --
```suggestion
The Execution setting is used to determine on which node(s) the Processor
will be
```
---
