[hotfix][docs] Fix some typos and sample codes syntax issues in sever…

[paul8263]

…al sections

What is the purpose of the change

Fix some typos and sample codes syntax issues in several chapters.

Brief change log

Correct the issues in the following files:

• docs/content/docs/internals/filesystems.md
• docs/content/docs/learn-flink/datastream_api.md
• docs/content/docs/libs/gelly/graph_algorithms.md
• docs/content/docs/libs/cep.md
• docs/content/docs/libs/state_processor_api.md
• docs/content/docs/ops/metrics.md
• docs/content/docs/try-flink/datastream.md
• docs/content/docs/try-flink/flink-operations-playground.md
• docs/content/docs/try-flink/table_api.md

Verifying this change

This change is a trivial rework / code cleanup without any test coverage.

Does this pull request potentially affect one of the following parts:

• Dependencies (does it add or upgrade a dependency): no
• The public API, i.e., is any changed class annotated with @Public(Evolving): no
• The serializers: no
• The runtime per-record code paths (performance sensitive): no
• Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn/Mesos, ZooKeeper: no
• The S3 file system connector: no

Documentation

• Does this pull request introduce a new feature? no
• If yes, how is the feature documented? not applicable

[flinkbot]

Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community
to review your pull request. We will use this comment to track the progress of the review.

Automated Checks

Last check on commit b123394 (Fri May 28 09:12:47 UTC 2021)

✅no warnings

_{Mention the bot in a comment to re-run the automated checks.}

Review Progress

• ❓ 1. The [description] looks good.
• ❓ 2. There is [consensus] that the contribution should go into to Flink.
• ❓ 3. Needs [attention] from.
• ❓ 4. The change fits into the overall [architecture].
• ❓ 5. Overall code [quality] is good.

Please see the Pull Request Review Guide for a full explanation of the review process.

The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot approve description to approve one or more aspects (aspects: description, consensus, architecture and quality)
• @flinkbot approve all to approve all aspects
• @flinkbot approve-until architecture to approve everything until architecture
• @flinkbot attention @username1 [@username2 ..] to require somebody's attention
• @flinkbot disapprove architecture to remove an approval you gave earlier

[flinkbot]

CI report:

• b123394 Azure: SUCCESS

Bot commands

The @flinkbot bot supports the following commands:

• @flinkbot run travis re-run the last Travis build
• @flinkbot run azure re-run the last Azure build

[zentol]

This isn't really a typo; its ust an abbreviation for nonDeterministic

[paul8263]

Thanks zentol. I have just rolled back those commits in cep.md.

[zentol]

Could you also fix the code-related issues in the chinese version of the docs? (under docs/content.zh)

[paul8263]

Could you also fix the code-related issues in the chinese version of the docs? (under docs/content.zh)

Those corresponding typos and syntax issues were fixed in docs/content.zh folder. Is there anything else I can help?

[zentol]

@paul8263 Thanks, this will do 👍