Skip to content

[hotfix] [docs] Fix typo in state v2 docs #26890

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 2 commits into
base: release-2.1
Choose a base branch
from
+2 −2
Open

[hotfix] [docs] Fix typo in state v2 docs #26890

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7bd0fff
fix typo
ndrake Aug 11, 2025
4f24f57
Fix typo in Chinese translastions per PR comment
ndrake Aug 19, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/content.zh/docs/dev/datastream/fault-tolerance/state_v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ We only focus on the asynchronous ones here.
First of all, we should get familiar with the return value of those asynchronous state access methods.

`StateFuture<T>` is a future that will be completed with the result of the state access.
The return bype is T. It provides multiple methods to handle the result, listed as:
The return type is T. It provides multiple methods to handle the result, listed as:
* `StateFuture<Void> thenAccept(Consumer<T>)`: This method takes a `Consumer` that will be called with the result
when the state access is done. It returns a `StateFuture<Void>`, which will be finished when the
`Consumer` is done.
Expand Down
2 changes: 1 addition & 1 deletion docs/content/docs/dev/datastream/fault-tolerance/state_v2.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -105,7 +105,7 @@ We only focus on the asynchronous ones here.
First of all, we should get familiar with the return value of those asynchronous state access methods.

`StateFuture<T>` is a future that will be completed with the result of the state access.
The return bype is T. It provides multiple methods to handle the result, listed as:
The return type is T. It provides multiple methods to handle the result, listed as:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we should also correct the Chinese version

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

* `StateFuture<Void> thenAccept(Consumer<T>)`: This method takes a `Consumer` that will be called with the result
when the state access is done. It returns a `StateFuture<Void>`, which will be finished when the
`Consumer` is done.
Expand Down