Skip to content
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.

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

Remove usage of Hedera in markdown files #285

Open
hendrikebbers opened this issue Nov 21, 2024 · 0 comments · May be fixed by #286
Open

Remove usage of Hedera in markdown files #285

hendrikebbers opened this issue Nov 21, 2024 · 0 comments · May be fixed by #286
Assignees
Labels
Hiero Transfer Issues that are related to the transfer to Hiero
Milestone

Comments

@hendrikebbers
Copy link
Contributor

Today "Hedera" is used in several Markdown files. You can get a search result here: https://github.com/search?q=repo%3Ahiero-ledger%2Fhiero-sdk-tck+Hedera+language%3AMarkdown&type=code&l=Markdown

We need to change it to Hiero or just removed.

Examples:

The hedera network must support at least 4 nodes -> The Hiero network must support at least 4 nodes

...can be set for all Hedera transaction types -> ...can be set for all transaction types

Next to the usage in Text the files contains a lot of links to the Hedera doc or Hedera repositories like protobuf. Those links should not be changed for now. We will fix it once all repos are transfered to Hiero.

@hendrikebbers hendrikebbers added the Hiero Transfer Issues that are related to the transfer to Hiero label Nov 21, 2024
@rwalworth rwalworth added this to the Sprint 11 milestone Nov 21, 2024
@rwalworth rwalworth linked a pull request Nov 21, 2024 that will close this issue
@rwalworth rwalworth modified the milestones: Sprint 11, Sprint 12 Nov 26, 2024
@rwalworth rwalworth modified the milestones: Sprint 12, Sprint 13 Dec 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Hiero Transfer Issues that are related to the transfer to Hiero
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants