[MINOR] fix(docs): Modify the document according to the README of playground #1243
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
qqqttt123
added
need backport
github-actions bot
pushed a commit
that referenced
this pull request
Dec 25, 2023
…yground (#1243) ### What changes were proposed in this pull request? Modify the document according to the pr apache/gravitino-playground#8 I will submit another pr to modify the document of website. ### Why are the changes needed? We should keep consistent. ### Does this PR introduce _any_ user-facing change? No. ### How was this patch tested? No. Co-authored-by: Heng Qin <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
Modify the document according to the pr apache/gravitino-playground#8
I will submit another pr to modify the document of website.
Why are the changes needed?
We should keep consistent.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
No.