[2/4] flink git commit: [FLINK-8849][docs] Fix links to chaining docs

[ch...@apache.org]

[FLINK-8849][docs] Fix links to chaining docs

This closes #5630.


Project: http://git-wip-us.apache.org/repos/asf/flink/repo
Commit: http://git-wip-us.apache.org/repos/asf/flink/commit/5aa481d5
Tree: http://git-wip-us.apache.org/repos/asf/flink/tree/5aa481d5
Diff: http://git-wip-us.apache.org/repos/asf/flink/diff/5aa481d5

Branch: refs/heads/release-1.4
Commit: 5aa481d5aa2a22755959fdc48e3449535f2b44e9
Parents: f58ade2
Author: Ken Krugler <ke...@transpac.com>
Authored: Sun Mar 4 09:27:11 2018 -0800
Committer: zentol <ch...@apache.org>
Committed: Mon Mar 5 17:58:42 2018 +0100

----------------------------------------------------------------------
 docs/concepts/runtime.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/5aa481d5/docs/concepts/runtime.md
----------------------------------------------------------------------
diff --git a/docs/concepts/runtime.md b/docs/concepts/runtime.md
index cb6d58f..1c7c281 100644
--- a/docs/concepts/runtime.md
+++ b/docs/concepts/runtime.md
@@ -31,7 +31,7 @@ under the License.
 For distributed execution, Flink *chains* operator subtasks together into *tasks*. Each task is executed by one thread.
 Chaining operators together into tasks is a useful optimization: it reduces the overhead of thread-to-thread
 handover and buffering, and increases overall throughput while decreasing latency.
-The chaining behavior can be configured; see the [chaining docs](../dev/datastream_api.html#task-chaining-and-resource-groups) for details.
+The chaining behavior can be configured; see the [chaining docs](../dev/stream/operators/#task-chaining-and-resource-groups) for details.
 
 The sample dataflow in the figure below is executed with five subtasks, and hence with five parallel threads.
 
@@ -98,7 +98,7 @@ job. Allowing this *slot sharing* has two main benefits:
 
 <img src="../fig/slot_sharing.svg" alt="TaskManagers with shared Task Slots" class="offset" width="80%" />
 
-The APIs also include a *[resource group](../dev/datastream_api.html#task-chaining-and-resource-groups)* mechanism which can be used to prevent undesirable slot sharing. 
+The APIs also include a *[resource group](../dev/stream/operators/#task-chaining-and-resource-groups)* mechanism which can be used to prevent undesirable slot sharing. 
 
 As a rule-of-thumb, a good default number of task slots would be the number of CPU cores.
 With hyper-threading, each slot then takes 2 or more hardware thread contexts.