[5/5] flink git commit: [FLINK-7670][doc] fix typo in docs runtime section

[tz...@apache.org]

[FLINK-7670][doc] fix typo in docs runtime section


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

Branch: refs/heads/release-1.3
Commit: 9437f7f489424e3b206769c4acd2ac03ab27b726
Parents: 5b78caf
Author: Kewei Shang <ke...@gmail.com>
Authored: Fri Sep 22 15:40:41 2017 +0200
Committer: Tzu-Li (Gordon) Tai <tz...@apache.org>
Committed: Tue Sep 26 18:11:11 2017 +0200

----------------------------------------------------------------------
 docs/concepts/runtime.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/9437f7f4/docs/concepts/runtime.md
----------------------------------------------------------------------
diff --git a/docs/concepts/runtime.md b/docs/concepts/runtime.md
index c598b12..508e64c 100644
--- a/docs/concepts/runtime.md
+++ b/docs/concepts/runtime.md
@@ -120,7 +120,7 @@ take a point-in-time snapshot of the key/value state and store that snapshot as
 
 Programs written in the Data Stream API can resume execution from a **savepoint**. Savepoints allow both updating your programs and your Flink cluster without losing any state. 
 
-[Savepoints](..//setup/savepoints.html) are **manually triggered checkpoints**, which take a snapshot of the program and write it out to a state backend. They rely on the regular checkpointing mechanism for this. During execution programs are periodically snapshotted on the worker nodes and produce checkpoints. For recovery only the last completed checkpoint is needed and older checkpoints can be safely discarded as soon as a new one is completed.
+[Savepoints](../setup/savepoints.html) are **manually triggered checkpoints**, which take a snapshot of the program and write it out to a state backend. They rely on the regular checkpointing mechanism for this. During execution programs are periodically snapshotted on the worker nodes and produce checkpoints. For recovery only the last completed checkpoint is needed and older checkpoints can be safely discarded as soon as a new one is completed.
 
 Savepoints are similar to these periodic checkpoints except that they are **triggered by the user** and **don't automatically expire** when newer checkpoints are completed. Savepoints can be created from the [command line](../setup/cli.html#savepoints) or when cancelling a job via the [REST API](../monitoring/rest_api.html#cancel-job-with-savepoint).