[2/3] flink git commit: [hotfix] [docs] Fix typos in State Backends doc

[tz...@apache.org]

[hotfix] [docs] Fix typos in State Backends doc

This closes #5075.


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

Branch: refs/heads/master
Commit: a246205cd48d881752f385329d6d564868e41922
Parents: 9fc3c71
Author: Cristian <me...@cristian.io>
Authored: Sun Nov 26 19:45:22 2017 -0800
Committer: Tzu-Li (Gordon) Tai <tz...@apache.org>
Committed: Thu Nov 30 16:04:12 2017 +0800

----------------------------------------------------------------------
 docs/ops/state/state_backends.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/flink/blob/a246205c/docs/ops/state/state_backends.md
----------------------------------------------------------------------
diff --git a/docs/ops/state/state_backends.md b/docs/ops/state/state_backends.md
index b32ad9f..4cda94f 100644
--- a/docs/ops/state/state_backends.md
+++ b/docs/ops/state/state_backends.md
@@ -96,9 +96,9 @@ The FsStateBackend is encouraged for:
 
 The *RocksDBStateBackend* is configured with a file system URL (type, address, path), such as "hdfs://namenode:40010/flink/checkpoints" or "file:///data/flink/checkpoints".
 
-The RocksDBStateBackend holds in-flight data in a [RocksDB](http://rocksdb.org) data base
+The RocksDBStateBackend holds in-flight data in a [RocksDB](http://rocksdb.org) database
 that is (per default) stored in the TaskManager data directories. Upon checkpointing, the whole
-RocksDB data base will be checkpointed into the configured file system and directory. Minimal
+RocksDB database will be checkpointed into the configured file system and directory. Minimal
 metadata is stored in the JobManager's memory (or, in high-availability mode, in the metadata checkpoint).
 
 The RocksDBStateBackend always performs asynchronous snapshots.
@@ -113,7 +113,7 @@ The RocksDBStateBackend is encouraged for:
   - Jobs with very large state, long windows, large key/value states.
   - All high-availability setups.
 
-Note that the amount of state that you can keep is only limited by the amount of disc space available.
+Note that the amount of state that you can keep is only limited by the amount of disk space available.
 This allows keeping very large state, compared to the FsStateBackend that keeps state in memory.
 This also means, however, that the maximum throughput that can be achieved will be lower with
 this state backend.