Standardize Token Name to $aHONEY Across Documentation
#330
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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
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.
Description
During a review of the
BERACHAINproject docs, inconsistencies were found in the naming of the token. In some files, the token was written asa$HONEY, while in others it appeared as$aHONEY. The correct, standardized name for the token is $aHONEY.• Replaced all occurrences of
a$HONEYwith the correct form$aHONEYthroughout the documentation to ensure consistency and improve readability.• These changes aim to prevent confusion and maintain a uniform reference to the token name for users and developers.
The documentation now follows a consistent naming standard for
$aHONEY, enhancing clarity and cohesion.Does it close a specific issue?
No
Example:
Contribution
I have followed the Development Workflow
I have read the CODE OF CONDUCT
I HAVE MADE SURE TO ALLOW MAINTAINERS TO EDIT THIS PULL REQUEST
I have synced my fork so that it is up to date with the latest changes
Let us know your wallet address/ENS: