From 158c070ac37ea471933ca2d5b0905c47d6736c0f Mon Sep 17 00:00:00 2001 From: tineff96 Date: Tue, 12 May 2026 10:09:13 +0200 Subject: [PATCH] #1918: fix typos in contributing documentation --- documentation/contributing/cla.adoc | 2 +- documentation/contributing/issue.adoc | 2 +- documentation/contributing/project-board.adoc | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/documentation/contributing/cla.adoc b/documentation/contributing/cla.adoc index 2174b7965d..0d3ccc5c9c 100644 --- a/documentation/contributing/cla.adoc +++ b/documentation/contributing/cla.adoc @@ -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. diff --git a/documentation/contributing/issue.adoc b/documentation/contributing/issue.adoc index 7796ef8d69..21603e1fd8 100644 --- a/documentation/contributing/issue.adoc +++ b/documentation/contributing/issue.adoc @@ -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]. diff --git a/documentation/contributing/project-board.adoc b/documentation/contributing/project-board.adoc index d90a81584d..a235e032fa 100644 --- a/documentation/contributing/project-board.adoc +++ b/documentation/contributing/project-board.adoc @@ -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.