Github user greghogan commented on a diff in the pull request:
— Diff: docs/dev/best_practices.md —
@@ -31,13 +31,13 @@ This page contains a collection of best practices for Flink programmers on how t
- Parsing command line arguments and passing them around in your Flink application
-Almost all Flink applications, both batch and streaming rely on external configuration parameters.
-For example for specifying input and output sources (like paths or addresses), also system parameters (parallelism, runtime configuration) and application specific parameters (often used within the user functions).
+Almost all Flink applications, both batch and streaming, rely on external configuration parameters.
+For example, they are used to specify input and output sources (like paths or addresses), system parameters (parallelism, runtime configuration), and application specific parameters (typically used within user functions).
Since version 0.9 we are providing a simple utility called `ParameterTool` to provide at least some basic tooling for solving these problems.
— End diff –
I expect it has been long enough to remove this notice.