diff --git a/docs/design/design-reviews/recipes/high-level-design-recipe.md b/docs/design/design-reviews/recipes/high-level-design-recipe.md
index cbf04f21f..a19f48a10 100644
--- a/docs/design/design-reviews/recipes/high-level-design-recipe.md
+++ b/docs/design/design-reviews/recipes/high-level-design-recipe.md
@@ -6,7 +6,7 @@ Design at macroscopic level shows the interactions between systems and services
 
 ## Things to keep in mind
 
-* As with all other aspects of the project, design reviews must provide a friendly and safe environment so that any team member feels comfortable proposing a design for review and can use the opportunity to grow and learn from the constructive / non-judgemental feedback from peers and subject-matter experts (see [Team Agreements](../../../agile-development/team-agreements/README.md)).
+* As with all other aspects of the project, design reviews must provide a friendly and safe environment so that any team member feels comfortable proposing a design for review and can use the opportunity to grow and learn from the constructive / non-judgemental feedback from peers and subject-matter experts (see [Team Agreements](../../../agile-development/team-agreements/)).
 * Attempt to illustrate different personas involved in the use cases and how/which boxes are their entry points.
 * Prefer pictures over paragraphs. The diagrams aren't intended to generate code, so they should be fairly high level.
   * Artifacts should indicate the direction of calls (are they outbound, inbound, or bidirectional?) and call out system boundaries where ports might need to be opened or additional infrastructure work may be needed to allow calls to be made.
diff --git a/docs/documentation/guidance/project-and-repositories.md b/docs/documentation/guidance/project-and-repositories.md
index c4a736493..2e5d51ef7 100644
--- a/docs/documentation/guidance/project-and-repositories.md
+++ b/docs/documentation/guidance/project-and-repositories.md
@@ -31,7 +31,7 @@ Some sections in the documentation of the repository might point to the project
 - [Onboarding](../../developer-experience/onboarding-guide-template.md)
 - Repository guide
   - Production, Spikes
-- [Team agreements](../../agile-development/team-agreements/README.md)
+- [Team agreements](../../agile-development/team-agreements/)
   - [Team Manifesto](../../agile-development/team-agreements/team-manifesto.md)
     - Short summary of expectations around the technical way of working and supported mindset in the team.
     - E.g., ownership, respect, collaboration, transparency.
@@ -55,9 +55,9 @@ Some sections in the documentation of the repository might point to the project
   - [High Level / Game Plan](../../design/design-reviews/recipes/high-level-design-recipe.md)
   - [Milestone / Epic Design Review](../../design/design-reviews/recipes/milestone-epic-design-review-recipe.md)
 - [Design Review Recipes](../../design/design-reviews/README.md#Recipes)
-  - [Milestone / Epic Design Review Template](../../design/design-reviews/recipes/milestone-epic-design-review-template.md)
-  - [Feature / Story Design Review Template](../../design/design-reviews/recipes/feature-story-design-review-template.md)
-  - [Task Design Review Template](../../design/design-reviews/recipes/task-design-review-template.md)
+  - [Milestone / Epic Design Review Template](../../design/design-reviews/recipes/templates/milestone-epic-design-review.md)
+  - [Feature / Story Design Review Template](../../design/design-reviews/recipes/templates/feature-story-design-review.md)
+  - [Task Design Review Template](../../design/design-reviews/recipes/templates/template-task-design-review.md)
   - [Decision Log Template](../../design/design-reviews/decision-log/doc/decision-log.md)
   - [Architecture Decision Record (ADR) Template](../../design/design-reviews/decision-log/README.md#architecture-decision-record-(ADR)) ([Example 1](../../design/design-reviews/decision-log/doc/adr/0001-record-architecture-decisions.md),
     [Example 2](../../design/design-reviews/decision-log/doc/adr/0002-app-level-logging.md))