Fix broken links (#191)

clementbiron · web-flow · commit c46f716e9fd7 · 2025-07-11T12:44:06.000+02:00
diff --git a/content/terms/how-to/rename-a-service.md b/content/terms/how-to/rename-a-service.md
@@ -6,4 +6,4 @@ weight: 5
 
 # How to rename a service
 
-The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service](#how-to-terminate-a-service) and adds a new [service declaration]({{< relref "terms/how-to/track-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.
+The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service]({{< relref "terminate-a-service" >}}) and adds a new [service declaration]({{< relref "terms/how-to/track-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.
diff --git a/content/terms/how-to/terminate-a-service.md b/content/terms/how-to/terminate-a-service.md
@@ -8,7 +8,7 @@ weight: 6
 
 If the service provider stops offering a service, the associated terms will become unavailable. To mark that service termination in Open Terms Archive and ensure tracking attempts are stopped, while maintaining the possibility to explore the history:
 
-1. Move the existing terms declaration to the service [history file](#terms-declaration-history).
+1. Move the existing terms declaration to the service [history file]({{< relref "declarations-maintenance#service-history-reference" >}}).
 2. Update the declaration to stop tracking all terms, by removing every `<terms type>` entries from the  `terms` key in the declaration:
 
 ```json

Original file line number	Diff line number	Diff line change
`@@ -6,4 +6,4 @@ weight: 5`
`6`	`6`
`7`	`7`	`# How to rename a service`
`8`	`8`
`9`		-The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service](#how-to-terminate-a-service) and adds a new [service declaration]({{< relref "terms/how-to/track-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.
	`9`	+The consensus is to consider that a service provider renaming a service (for example, `Twitter` to `X`) is akin to terminating the previous service and opening a new one. Therefore, to apply a service renaming, open a pull request that both [terminates the previous service]({{< relref "terminate-a-service" >}}) and adds a new [service declaration]({{< relref "terms/how-to/track-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `terms` part of the original declaration, but should double-check that the selectors and URLs still match, as a service rename is most often accompanied by a new page layout, a new domain name, and sometimes entirely new terms.