docs: fix broken links in examples and implementation guide

content/en/docs/How to/create-a-score-implementation.md

@@ -102,5 +102,5 @@ To adapt this for your target platform, you should:
 2. Rename the go module by replacing all instances of `github.com/score-spec/score-implementation-sample` with your own module name.
 3. Replace all other instances of `score-implementation-sample` with your own `score-xyz` name including renaming the `cmd/score-implementation-sample` directory.
 4. Run the tests with `go test -v ./...` to ensure the renamed code works correctly.
-5. Change the `TODO` in [provisioning.go](./internal/provisioners/provisioning.go) to provision resources and set the resource outputs. The existing implementation resolves placeholders in the resource parameters but doesn't set any resource outputs.
-6. Change the `TODO` in [convert.go](./internal/convert/convert.go) to convert workloads into the target manifest form. The existing implementation resolves placeholders in the variables and files sections but just returns the workload spec as YAML content in the manifests.
+5. Change the `TODO` in [provisioning.go](https://github.com/score-spec/score-implementation-sample/blob/main/internal/provisioners/provisioning.go) to provision resources and set the resource outputs. The existing implementation resolves placeholders in the resource parameters but doesn't set any resource outputs.
+6. Change the `TODO` in [convert.go](https://github.com/score-spec/score-implementation-sample/blob/main/internal/convert/convert.go) to convert workloads into the target manifest form. The existing implementation resolves placeholders in the variables and files sections but just returns the workload spec as YAML content in the manifests.

content/en/docs/examples/backstage.md

@@ -75,7 +75,7 @@ From here, we will now see how to deploy this exact same Score file with either
 
 ## Next steps
 
-- [**Deploy this Backstage application into two different Frontend and Backend applications**](/docs/examples/frontend-and-backend.md): Follow the same example where this Backstage application is broken down into two containerized applications: Frontend & Backend.
+- [**Deploy this Backstage application into two different Frontend and Backend applications**]({{< relref "/docs/examples/frontend-and-backend" >}}): Follow the same example where this Backstage application is broken down into two containerized applications: Frontend & Backend.
 - [**Deep dive with the associated step-by-step guide**](https://medium.com/@mabenoit/deploy-backstage-with-score-45bb2d7c2d90): Go through the associated step-by-step guide to understand the different concepts with both: Backstage and Score.
 - [**Explore more examples**](/examples/): Check out more examples to dive into further use cases and experiment with different configurations.
 - [**Join the Score community**]({{< relref "/docs/community" >}}): Connect with fellow Score developers on our CNCF Slack channel or start find your way to contribute to Score.

content/en/docs/examples/included/backstage-score-compose.md

@@ -16,7 +16,7 @@ score-compose init --no-sample \
     --provisioners https://raw.githubusercontent.com/score-spec/community-provisioners/refs/heads/main/dns/score-compose/10-dns-with-url.provisioners.yaml
 ```
 
-The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-url/).
+The `init` command will create the `.score-compose` directory with the [default resource provisioners]({{< relref "/docs/score-implementation/score-compose/resources-provisioners/" >}}) available. We are also importing one external file to support the `dns` dependencies: [`dns` provisioner](https://docs.score.dev/examples/resource-provisioners/community/dns/score-compose/template/dns-with-route/).
 
 You can see the resource provisioners available by running this command: