Skip to content
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.

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

Fixed typo in ReadMe #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Fixed typo in ReadMe #1

wants to merge 1 commit into from

Conversation

fredrir
Copy link

@fredrir fredrir commented Sep 22, 2024

No description provided.

@jotjern
Copy link
Member

jotjern commented Oct 3, 2024

This pull request includes a small change to the profile/README.md file. The change corrects a typographical error in the word "komité".

@fredrir
Copy link
Author

fredrir commented Oct 3, 2024

This pull request includes a small change to the profile/README.md file. The change corrects a typographical error in the word "komité".

Thank you for taking the time to review the pull request! The change I made to the profile/README.md file is indeed small but addresses an important typographical error in the word "komité." Consistency and accuracy in documentation, even down to the smallest details, can significantly improve the clarity and professionalism of a committee.

In this case, "komité" is a Norwegian word meaning "committee," and ensuring its correct spelling is essential for maintaining the quality of the documentation, especially when addressing an audience that includes native speakers or others familiar with the term. Correcting these minor errors not only helps avoid confusion but also ensures that your project's documentation maintains a high standard of accuracy and attention to detail.

While this may seem like a small edit, ensuring that our documentation is free from typographical errors contributes to a more polished user experience. It reflects a commitment to maintaining quality throughout all aspects of the project, including the supporting documents. Thank you again for your attention to this change—it's great to have a team that values even the minor details that collectively make the project better.

If there are any further issues or suggestions for this or other parts of the documentation, feel free to let me know! I'm happy to make additional revisions or discuss improvements.

Let me know if you'd like any modifications to this response!

@fredrir
Copy link
Author

fredrir commented Oct 4, 2024

@Terbau noen innspill her?

Copy link

@Terbau Terbau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me👍

@fredrir
Copy link
Author

fredrir commented Oct 4, 2024

Looks good to me👍

I'm not afraid, to merge this branch,
Everybody, come take my hand,
We’ll push this code, together as one team,
We’ll review it all, squash the bugs and make it clean.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants