This is an automated email from the ASF dual-hosted git repository. mergebot-role pushed a commit to branch mergebot in repository https://gitbox.apache.org/repos/asf/beam-site.git
commit bc27da2aca04440d38c21b4bfeb3b8b800a0e500 Author: Etienne Chauchot <[email protected]> AuthorDate: Fri Jul 20 10:53:43 2018 +0200 [BEAM-4827] Fix typos --- src/documentation/sdks/nexmark.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/documentation/sdks/nexmark.md b/src/documentation/sdks/nexmark.md index be96a58..bf96803 100644 --- a/src/documentation/sdks/nexmark.md +++ b/src/documentation/sdks/nexmark.md @@ -655,12 +655,12 @@ Submit to the cluster: --monitorJobs=true" ## Nexmark dashboards -Bellow dashboards are used as a CI mechanism to ensure no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because: +Below dashboards are used as a CI mechanism to detect no-regression on the Beam components. They are not supposed to be benchmark comparision of the runners or engines. Especially because: - Parameters of the runners are not the same - Nexmark is run with the runners in local (most of the time embedded) mode -- Nexmark run on a shared machine that also run all the CI and build. +- Nexmark runs on a shared machine that also run all the CI and build. - Runners have different support of the Beam model -- Runners have different strengths that make comparision difficult: +- Runners have different strengths that make comparison difficult: - Some runners were designed to be batch oriented, others streaming oriented - Some are designed towards sub-second latency, others support auto-scaling
