Minor changes

Author: abby-ql

src/community/start-contributing.md

@@ -1,39 +1,37 @@
 
 # Start Contributing to Typelevel
 
-Typelevel projects power a large part of the functional Scala ecosystem. They are also complex, long-lived codebases with active communities. Contributing can feel intimidating at first, but the path in is actually quite simple! A practical path that works well across most Typelevel repositories:
+Typelevel projects power a large part of the functional Scala ecosystem. They are also complex, long-lived codebases with active communities. Contributing can feel intimidating at first, but the path in is actually quite simple! 
+
+Build something small with Cats Effect. Try streaming something with FS2. Use http4s for a simple service. Build with [Typelevel Toolkit](https://typelevel.org/blog/). Build a static site with Laika.
+
+> Become a user of the ecosystem you want to contribute to.
+
+Also some tips that works well across most Typelevel repositories:
 
 #### Find something that can be improved
-   - Look for open issues, especially those labeled `good first issue` or `help wanted`.
-   - Browse the curated [good-first-issues board](https://github.com/orgs/typelevel/projects/1/)
-   - If you're already using the library, improve something that bothered you.
-   - Documentation and tests are excellent starting points too.
+- Look for open issues, especially those labeled `good first issue` or `help wanted`.
+- Browse the curated [good-first-issues board](https://github.com/orgs/typelevel/projects/1/).
+- If you're already using the library, improve something that bothered you.
+- Documentation and tests are excellent starting points too.
 
 #### Understand the problem first
-   - Read the issue carefully, understand the current implementation.
-   - Look for existing PRs or recent comments
-   - Check whether a solution was already proposed.
+- Read the issue carefully, understand the current implementation.
+- Look for existing PRs or recent comments.
+- Check whether a solution was already proposed.
 
 #### Communication is Key
-   - Comment on the issue saying you'd like to work on it and briefly describe your idea or approach.
-   - Ask clarifying questions if anything is unclear.
-   - If the change is small, you can open a draft PR early to get feedback.
+- Comment on the issue saying you'd like to work on it and briefly describe your idea or approach.
+- Ask clarifying questions if anything is unclear.
+- If the change is small, you can open a draft PR early to get feedback.
 
 #### Open a PR and iterate
-   - Fork the repo, create a branch, and implement the change. Add or update tests where appropriate.
-   - Open a PR with a clear description of the problem and your solution. Read the [Typelevel AI policy](https://typelevel.org/gsoc/ai.html).
-   - Expect review feedback, ask questions, adjust your changes, and iterate.
-
-#### Become a User First
-
-Build something small with Cats Effect. Try streaming something with FS2. Use http4s for a simple service. Build with [Typelevel Toolkit](https://typelevel.org/blog/). 
-A common piece of advice from the community is:
-
-> Become a user of the ecosystem you want to contribute to.
+- Fork the repo, create a branch, and implement the change. Add or update tests where appropriate.
+- Open a PR with a clear description of the problem and your solution. Read the [Typelevel AI policy](https://typelevel.org/gsoc/ai.html).
+- Expect review feedback, ask questions, adjust your changes, and iterate.
 
 #### Where to Ask for Help
-
-- Join the [Typelevel Discord](https://discord.gg/typelevel-632277896739946517)
+- Join the [Typelevel Discord](https://discord.gg/typelevel-632277896739946517).
 - Ask in `#starting-contributing` if you're new to contributing.
 - Use library-specific channels like `#cats`, `#cats-effect`, `#fs2`, or `#http4s` for more focused questions.
 - You can also ask directly on a GitHub issue if your question is specific to that issue.