2-Guides/review-guide.md

@@ -5,7 +5,7 @@ Thanks for donating your time and brain capacity for this. Highly appreciated.
 
 # The Scope
 
-By your review you'll assess whether a certain piece of hardware qualifies as open source hardware according to [DIN SPEC 3105-1](https://osegermany.gitlab.io/OHS/din/DIN_SPEC_3105-1.pdf). See [CAB overview](/2-Guides/CAB.md) or [DIN SPEC 3105-1](https://osegermany.gitlab.io/OHS/din/DIN_SPEC_3105-1.pdf) for more general information.
+By your review you'll assess whether a certain piece of hardware qualifies as open source hardware according to [DIN SPEC 3105-1](https://osegermany.gitlab.io/OHS/din/DIN_SPEC_3105-1.pdf). See [CAB overview](/2-Guides/CAB) or [DIN SPEC 3105-1](https://osegermany.gitlab.io/OHS/din/DIN_SPEC_3105-1.pdf) for more general information.
 
 # The Procedure
 
@@ -31,7 +31,7 @@ All relevant discussions & decisions are directly documented in the issue as com
 2. Perform review:
 	- Check if all mandatory information is there,
 	- state misalignments otherwise and
-	- wait until misalignments are fixed (most likely by developers of the applying OSH project) or quickly fix it yourself (please refer to the [application guide](/2-Guides/application-guide.md) before!).
+	- wait until misalignments are fixed (most likely by developers of the applying OSH project) or quickly fix it yourself (please refer to the [application guide](/2-Guides/application-guide) before!).
 3. Check the update:
 	- Fixes by the applicants (applying project developers) in reply to your comments are commited as **merge requests**, ideally each one linked to the relevant issue.
 	- Check the merge request and see if all relevant issues are tagged,
@@ -55,7 +55,7 @@ What makes open source hardware different from prorietary hardware is it's techn
 **In short:**
 
 - license must be compliant to the [OSHWA definition](https://www.oshwa.org/definition)
-  - we maintain a [list of compliant licenses](osh-licenses.md); ask a CAB Admin for help if needed
+  - we maintain a [list of compliant licenses](osh-licenses); ask a CAB Admin for help if needed
 - documentation must be permanently and publicly accessible
   - when you are seeing this OSH project on <https://gitlab.opensourceecology.de/> this is already the case
 - engineers shall be enabled to fully understand, build and modify the design only by the given documentation