Skip to content
This repository has been archived by the owner on Dec 12, 2024. It is now read-only.

Fix Typos in DIF Hackathon: Top 3 Winners! Blog Post #1560

Closed
2 tasks
Tracked by #1552
taniashiba opened this issue Aug 30, 2024 · 5 comments · Fixed by #1760
Closed
2 tasks
Tracked by #1552

Fix Typos in DIF Hackathon: Top 3 Winners! Blog Post #1560

taniashiba opened this issue Aug 30, 2024 · 5 comments · Fixed by #1760
Assignees
Labels
good first issue Good for newcomers hacktoberfest issues that are open/valid for hacktoberfest no-code no code needed to work on the issues small For smaller tasks that take max 1 hour to complete. (Hacktoberfest)

Comments

@taniashiba
Copy link
Contributor

taniashiba commented Aug 30, 2024

Fix Typos in DIF Hackathon: Top 3 Winners! Blog Post

🚀 Goal

We want to ensure our website's blog posts don't have any mistakes.

🤔 Background

This issue focuses specifically on fixing typos on one of our blog posts. Your contributions here make a difference!

🤝 How You Can Contribute

We've broken it down into specific typos for you to address. Every contribution counts!

🔑 Tasks and Acceptance Criteria

❗You must only assign yourself one task at a time to give everyone a chance to participate.❗

You may assign yourself your next task after your current task is reviewed & accepted.

  1. Fix typos in DIF Hackathon: Top 3 Winners! blog
    • Fix "sponor" to be "sponsor"
      image
    • Fix "Github" to be "GitHub"
      image
  2. Make sure all tests are passing.

🌟 Resources

Getting Started

  1. Comment ".take" on this issue to get assigned
  2. Fork the repository and create a new branch for this task
  3. Follow the tasks outlined above
  4. Submit a pull request with your changes
  5. Respond to any feedback during the review process

Questions?

If you have any questions or need clarification, please comment on this issue or join our Discord community.

Happy coding! 🎉

@taniashiba taniashiba added good first issue Good for newcomers hacktoberfest issues that are open/valid for hacktoberfest no-code no code needed to work on the issues labels Aug 30, 2024
@taniashiba taniashiba changed the title Fix Typos in Blogs on Developer Website Fix Typos in Developer Website's Blogs Aug 30, 2024
@taniashiba taniashiba added large For heavy tasks that take one day and up to complete. (Hacktoberfest) small For smaller tasks that take max 1 hour to complete. (Hacktoberfest) and removed good first issue Good for newcomers no-code no code needed to work on the issues large For heavy tasks that take one day and up to complete. (Hacktoberfest) labels Sep 4, 2024
@taniashiba taniashiba changed the title Fix Typos in Developer Website's Blogs Fix Typos in DIF Hackathon: Top 3 Winners! Blog Post Sep 5, 2024
@aniketh-varma
Copy link
Contributor

.take

Copy link

github-actions bot commented Oct 1, 2024

Thanks for taking this issue! Let us know if you have any questions!

@blackgirlbytes
Copy link
Contributor

Hey @aniketh-varma I noticed you're assigned to 8 issues and they're all typo issues. While we appreciate the enthusiasm, we kindly ask that you finish an issue before assigning yourself a new one. We want to give everyone a chance to be able to make their first contributions to open source. So, I'll leave you assigned to ticket #1578 , but I will unassign you from the rest.

If you finish that ticket, then you can assign yourself to a new one! Thank you

@taniashiba taniashiba added good first issue Good for newcomers no-code no code needed to work on the issues labels Oct 1, 2024
@Ankitv003
Copy link
Contributor

.take

Copy link

github-actions bot commented Oct 2, 2024

Thanks for taking this issue! Let us know if you have any questions!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
good first issue Good for newcomers hacktoberfest issues that are open/valid for hacktoberfest no-code no code needed to work on the issues small For smaller tasks that take max 1 hour to complete. (Hacktoberfest)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants