[FLINK-21930][DOC]fix hive dim doc replace o to order

[hehuiyuan]

What is the purpose of the change

doc error

[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 1d534b9 (Fri Mar 19 14:27:47 UTC 2021)

Warnings:

• Invalid pull request title: No valid Jira ID provided

_{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.

Details

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:

• b838378 UNKNOWN
• d5ad0ee 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

[hehuiyuan]

@flinkbot re-run

[hehuiyuan]

Hi @lirui-apache ,
please have a look this.

[lirui-apache]

Thanks @hehuiyuan for fixing the doc. It looks good to me, but you need a jira ticket to associate with your PR.

[hehuiyuan]

Thanks @hehuiyuan for fixing the doc. It looks good to me, but you need a jira ticket to associate with your PR.

Hi @lirui-apache , okay i do it.

I have changed some documents before, and then others said that simple doc changes do not need to create jira.

[hehuiyuan]

Hi @lirui-apache , done

[lirui-apache]

+1

[wuchong]

LGTM.