📝 Clarify estimation note in documentation #14070
Conversation
|
Note: The tag was kept intentionally for styling consistency. |
saky-semicolon
left a comment
saky-semicolon
left a comment
There was a problem hiding this comment.
Both sentences read well, but the second one (“conducted by”) is a bit clearer and more formal than the first. I’d suggest going with the second version for better readability.
svlandeg
changed the title
It's always a good idea to go and read why the CI is failing 😉 In this case: 
What this means, is that |
|
I am new to contributions so |
This comment was marked as outdated.
This comment was marked as outdated.
svlandeg
left a comment
svlandeg
left a comment
There was a problem hiding this comment.
Thanks again for the PR @SaisakthiM! The rephrasing makes sense to me: IMO it's easier to parse & understand the sentence with this edit.
This comment was marked as outdated.
This comment was marked as outdated.
|
@SaisakthiM : as this is just a documentation PR, there's no need to merge in master when there are no conflicts. Thanks! |
can you explain it more clearly |
|
anyone here is the progress going on |
|
@YuriiMotov can you please review this |
It's already approved by Team member. Now we are waiting for final review by Sebastian |
* Sync with #14217 * Sync with #14359 * Sync with #13786 * Sync with #14070 * Sync with #14120 * Sync with #14211 * Sync with #14405 * "to deploy" -> "deployen" The LLM used that translation a lot ithis convinced me that "deployen" it is the better word. "bereitstellen" (or "ausliefern") is still used for "to serve". --------- Co-authored-by: Motov Yurii <[email protected]> Co-authored-by: Yurii Motov <[email protected]>
5 participants
Description
This PR improves the clarity of a documentation note inside a
<small>tag:Before:
* estimation based on tests on an internal development team, building production applications.
After:
* estimation based on tests conducted by an internal development team, building production applications.
The change corrects the wording to better describe the context while keeping the
<small>styling intact.Pull Request type
Notes
This is a minor documentation update and does not affect any code functionality.