hiero-ledger / hiero-ledger/hiero-sdk-java

[Good First Issue]: Fix typo in README.md

Open Beginner friendly
#2,821 5 comments 0 reactions 0 assignees View on GitHub
Good First Issue
Dominant language
Java
Stars
264
Forks
192
Avg merge
2d
Merged PRs (30d)
39

Description

### 🆕🐥 First Timers Only

This issue is reserved for people who have never contributed or have made minimal contributions to [Hiero](https://hiero.org).
We know that creating a pull request (PR) is a major barrier for new contributors.
The goal of this issue and all other issues in [**find a good first issue**](https://github.com/issues?q=is%3Aopen+is%3Aissue+org%3Ahiero-ledger+archived%3Afalse+label%3A%22good+first+issue%22+) is to help you make your first contribution to the Hiero.

### 👾 Description of the issue

Fix typo on line 49 in README.md
guidelies→guidelines

### 💡 Proposed Solution

Fix typo on line 49 in README.md
guidelies→guidelines

### 👩‍💻 Implementation Steps

Fix typo on line 49 in README.md
guidelies→guidelines

### ✅ Acceptance Criteria

To be able to merge a pull request for this issue, we need:
- [ ] **Signed commits:** commits must be DCO and GPG key signed
- [ ] **All Tests Pass:** our workflow checks like unit and integration tests must pass
- [ ] **Issue is Solved:** The implementation fully addresses the issue requirements as described above
- [ ] **No Further Changes are Made:** Code review feedback has been addressed and no further changes are requested

### 📋 Step-by-Step Contribution Guide

If you have never contributed to an open source project at GitHub, the following step-by-step guide will introduce you to the workflow.
More information and concrete samples for shell commands for each step can be found in our [CONTRIBUTING.md](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md) file.
A more detailed general documentation of the GitHub PR workflow can be found [here](https://github.com/firstcontributions/first-contributions/blob/master/README.md).

- [ ] **Claim this issue:** Comment below that you are interested in working on the issue
- [ ] **Wait for assignment:** A community member with the given rights will add you as an assignee of the issue
- [ ] **Work on the issue:** Follow the detailed description in our [CONTRIBUTING.md](https://github.com/hiero-ledger/.github/blob/main/CONTRIBUTING.md) file.
- [ ] **You did it 🎉:** We will merge the fix in the main branch. Thanks for being part of the Hiero community as an open-source contributor!

***IMPORTANT*** Your pull request CANNOT BE MERGED until your commits are each with `git commit -S -s -m "chore: your commit message"` with a GPG key setup.

### 🤔 Additional Information

If you have any questions about the topic of this issue, please ask us directly by adding a comment below.
Additionally, we invite you to join our community on our [Discord](https://discord.gg/hyperledger) server or attend our [public community calls](https://zoom-lfx.platform.linuxfoundation.org/meetings/hiero?view=week).

A general manual about open-source contributions can be found [here](https://github.com/firstcontributions/first-contributions/blob/master/README.md).

------

Contributor guide

Open the contributing guide

Research direction

Open README.md and go to line 49, where the issue identifies the misspelling “guidelies.” Change it to “guidelines,” then review the diff to confirm that no other content changed.

Written by the indexing model from the issue text.

Assessment

Domain
documentation
Issue type
Documentation
Difficulty
1/5
Estimated time
Under an hour
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
85/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.