Improve Consistency in Terminology #160
Closed
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.
Description:
This update addresses a small but important inconsistency in the terminology used in the documentation and method names. The term "batched" has been replaced with "batch" in phrases like "batch open" and "batch check". While "batched" is grammatically correct, "batch" aligns better with the standard naming convention seen in Rust codebases and documentation, particularly when referring to batch operations or methods.
This change ensures greater clarity and consistency across the project, improving both the code readability and user experience. Consistent terminology is crucial for maintaining clarity, especially when users and developers interact with the methods and documentation.