[Refactor] Fixes some be typo part 2

[yangzhg]

Proposed changes

Fix some typo in be code

Types of changes

What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

• [] Bugfix (non-breaking change which fixes an issue)
• [] New feature (non-breaking change which adds functionality)
• [] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [] Documentation Update (if none of the other choices apply)
• Code refactor (Modify the code structure, format the code, etc...)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• [] I have create an issue on (Fix #ISSUE), and have described the bug/feature there in detail
• Compiling and unit tests pass locally with my changes
• [] I have added tests that prove my fix is effective or that my feature works
• [] If this change need a document change, I have updated the document
• [] Any dependent changes have been merged

Further comments

If this is a relatively large or complex change, kick off the discussion at dev@doris.apache.org by explaining why you chose the solution you did and what alternatives you considered, etc...

[kangkaisen]

@yangzhg Why all checks failed?

[yangzhg]

@yangzhg Why all checks failed?

maybe need rebase

[kangkaisen]

+1