fix: add parallel structure

docs/community/100-days-of-oss.md

@@ -18,13 +18,17 @@ There are numerous ways to participate in the #100DaysOfOSS challenge, including
 - write issues to identify bugs or suggest new features;
 - triage existing issues to help with prioritization;
 - submit pull requests to contribute code changes;
-- engage in the community by sharing your insights and knowledge;
-- create or participate in discussions related to OSS topics;
-- write a blog post or create content that supports an OSS project; 
-- update or write documentation to improve clarity and usability
-- create content: give a talk or presentation on OSS, participate in or even start a Twitter Space write a blog post or create a video;  
-- maintain a project: review pull requests, triage issues, and respond to questions;
+- engage in the community by sharing your insights and knowledge; 
 - support contributors working on OSS projects, providing guidance and support.
+### Content creation
+Love creating content? Here's how you can use this skill for the challenge:
+  - Give a talk or presentation on OSS.
+  - Participate in or even start a Twitter Space.
+  - Write a blog post or create a video.
+### Project management
+Want to improve your project management skills? Need to get better at communicating or giving feedback to others? Here's how you can use this skill for the challenge:
+  - Review pull requests.
+  - Triage issues.
 
 To keep track of your progress, post on social media, your blog, or any other platform you prefer with what progress you made, the day of the challenge indicated by 'D'and include the hashtag #100DaysOfOSS. For example, if you're on day one, you could say, "Today, I reviewed the documentation for the [OpenSauced/Insights](https://github.com/open-sauced/insights) repository. D1 #100daysOfOSS." Then, on day two, you would continue with D2, and so on.