See if Netlify likes these links better

Author: stefanv

_index.md

@@ -15,5 +15,5 @@ Community discussions take place on the
 SPEC development takes place in the [SPEC repository](https://github.com/scientific-python/specs).
 
 If you want to **contribute a SPEC**, start by reading [SPEC Purpose and Process](/specs/purpose-and-process).
-Core projects may also want to [endorse a SPEC](/specs/purpose-and-process#endorsing-a-spec).
+Core projects may also want to [endorse a SPEC](/specs/purpose-and-process/#endorsing-a-spec).
 Contributors must adhere to our [code of conduct](https://scientific-python.org/code_of_conduct/).

core-projects/_index.md

@@ -71,7 +71,7 @@ The 3-clause (also called "modified" or "new") BSD license is by far the most co
 
 ### How does a Core Project endorse a SPEC?
 
-See [purpose and process](/specs/purpose-and-process#endorsing-a-spec).
+See [purpose and process](/specs/purpose-and-process/#endorsing-a-spec).
 
 ### How many Core Projects should there be?
 

steering-committee/_index.md

@@ -49,7 +49,7 @@ to consensus-seeking and voting.
 <!-- This is a focused distillation of purpose-and-process#decision-points for the SPEC committee. -->
 
 Also refer to [SPEC Purpose and Process: New
-Proposals](/specs/purpose-and-process#new-spec-proposals), a summary
+Proposals](/specs/purpose-and-process/#new-spec-proposals), a summary
 of steps for SPEC authors.
 
 To accept a SPEC requires two members of the Steering Committee to