fix: typos in content folder #407
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
lterrac
force-pushed
the
fix/typos-in-content-folder
branch
from
4e4984d to
7c592d1
Compare
lterrac
changed the title
Signed-off-by: Luca Terracciano <[email protected]>
Signed-off-by: Luca Terracciano <[email protected]>
Signed-off-by: Luca Terracciano <[email protected]>
Signed-off-by: Luca Terracciano <[email protected]>
Signed-off-by: Luca Terracciano <[email protected]>
StefanJum
force-pushed
the
fix/typos-in-content-folder
branch
from
7c592d1 to
f9846a2
Compare
StefanJum
approved these changes
Jul 20, 2024
There was a problem hiding this comment.
Thanks @lterrac
Reviewed-by: Stefan Jumarea [email protected]
Approved-by: Stefan Jumarea [email protected]
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes typo in the content folder in the subfolders
community,docs/cli,docs/contributing,docs/internal, andguides.This is my first PR, so every suggestion on how to improve in the future the review process, how to correctly describe the issue and what has been done is well accepted 😄