[ 
https://issues.apache.org/jira/browse/FLINK-6513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16003060#comment-16003060
 ] 

ASF GitHub Bot commented on FLINK-6513:
---------------------------------------

Github user greghogan commented on a diff in the pull request:

    https://github.com/apache/flink/pull/3858#discussion_r115538538
  
    --- 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.


> various typos and grammatical flaws
> -----------------------------------
>
>                 Key: FLINK-6513
>                 URL: https://issues.apache.org/jira/browse/FLINK-6513
>             Project: Flink
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 1.3.0
>            Reporter: David Anderson
>
> I want to propose small changes to several pages to fix some typos and 
> grammatical flaws.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to