Skip to content

#1918: fix typos in contributing documentation #1925

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
tineff96 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

#1918: fix typos in contributing documentation #1925

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
158c070
#1918: fix typos in contributing documentation
tineff96 May 12, 2026
7e680bb
Merge branch 'main' into docs/1918-improve-docs
tineff96 May 13, 2026
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 documentation/contributing/cla.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Please **open the link**, **read the agreement**, and **confirm it**.

NOTE: Pay attention to provide the proper email-address to the CLA form.
You need to provide the email address that you have configured in git for your commits that should also be the email address you have configured in your GitHub profile (as primary email address).
If possible avoid mixing multiple email addresses (e.g. private and corporate email).
If possible, avoid mixing multiple email addresses (e.g. private and corporate email).
Once you have filled the CLA with the "wrong" email address, it gets really hard to fix this.
So really be careful to provide the correct email address, when you fill out the CLA.

Expand Down
2 changes: 1 addition & 1 deletion documentation/contributing/issue.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Once, you are now the assigned person working on the issue, you can start your i

== Feedback on an Issue

If you reported and issue, we try to give our best to value your feedback and also report back via comments.
If you reported an issue, we try to give our best to value your feedback and also report back via comments.
If you see link:commit.adoc[commits] being associated in your issue, a link:pull-request.adoc[pull-request] gets linked in your issue under `Development`, or a release is assigned as link:milestone.adoc[milestone] you can see that we are working on your issue.
If your issue gets `closed` it was either implemented and is `done` or it was somehow rejected (e.g. closed as duplicate or invalid).
In most cases it was implemented, and you will see a release assigned as link:milestone.adoc[milestone].
Expand Down
2 changes: 1 addition & 1 deletion documentation/contributing/project-board.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ They should have the key metadata set:
Issues with higher `Priority` should typically be addressed first.
- **Size**: Represents the estimated complexity or effort (e.g., Small, Medium, Large).
Issues with higher `Size` are typically more complex.
Depending on your experience consider if you want to deal with the story or check if easier tasks are therefore you to work on first.
Depending on your experience, consider if you want to deal with the story or check if easier tasks are there for you to work on first.
* `Research`:
**link:issue.adoc[Issues]** or **link:pull-request.adoc[PRs]** that are blocked or require deeper analysis before implementation can continue.
These items often involve unclear requirements or technical challenges.
Expand Down
Loading