> For the complete documentation index, see [llms.txt](https://docs.projectcatalyst.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/milestone-reviewers-guides/faq.md).

# FAQ

**How many Milestone Reviewers are assigned to each project?**

There are 2 Milestone Reviewers assigned to general categories and 3 Milestone Reviewers assigned to Cardano Partners category.

**Should I reset my password and create a new one in the Milestone Module if I have been Milestone Reviewer in previous fund(s)?**

If you have been Reviewer in previous fund(s), you should only log in to your account in the Milestone Module.

**May I not verify SoM/PoA if the other Reviewer refused it already?**

Each Reviewer verifies SoM/PoA seperately and should provide own opinion why SoM/PoA was approved/refused, even if the other Reviewer refused it already.

**Is it possible to turn off email notifications with pending reviews assigned to me in the Milestone Module?**

It is impossible to turn it off.

**What to do if I have assigned technical project to review and I don't have knowledge to review it properly.**

Please submit a ticket [here](https://catalystiog.zendesk.com/hc/en-us/requests/new).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.projectcatalyst.io/previous-funds/fund13-docs/project-onboarding/milestone-reviewers-guides/faq.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.