Update pages/workflow/review.mdx

avohq · Oct 17, 2024 · af3d428 · af3d428
1 parent 1053d42
commit af3d428
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/pages/workflow/review.mdx b/pages/workflow/review.mdx
@@ -18,7 +18,7 @@ We typically see three types of reviewers:
 - **Data team:** Someone who validates that the changes made are according to the data standard of your company
 - **Engineering team:** The folks who will implement the suggested changes. If the changes made affect multiple sources (e.g. iOS, Android, Web, backend) we recommend to get reviews from the teams working on each source
 
-Additionally, if your changes impact [stakeholder domains](data-design/avo-tracking-plan/stakeholder-domains) in your organization that you are not a member of, we recommend pulling someone from the respective domain in to review the changes. See our guide on [managing changes impacting multiple stakeholders](data-design/guides/managing-changes-impacting-multiple-stakeholders).
+Additionally, if your changes impact [stakeholder domains](data-design/avo-tracking-plan/stakeholder-domains) in your organization that you are not a member of, we recommend pulling someone from the respective domain in to review the changes. See our guide on [managing changes impacting multiple stakeholders](/data-design/guides/managing-changes-impacting-multiple-stakeholders).
 
 **How to ask for a review?**
 The first step is to mark the branch as “Ready for review”. This is done at the bottom of the review screen as seen on the screenshot below.