From d048a222f51ebadb0ba34662dd4a58544309d5c2 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Cl=C3=A9ment=20Biron?= Date: Thu, 13 Jun 2024 16:25:16 +0200 Subject: [PATCH] Fix broken links --- content/terms/declarations-maintenance.en.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/terms/declarations-maintenance.en.md b/content/terms/declarations-maintenance.en.md index 47a323e..4f97830 100644 --- a/content/terms/declarations-maintenance.en.md +++ b/content/terms/declarations-maintenance.en.md @@ -105,4 +105,4 @@ If the service provider stops offering a service, the associated terms will beco ## 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](#handling-a-terminated-service) and adds a new [service declaration]({{< relref "terms/tracking-new-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `documents` 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](#how-to-terminate-a-service) and adds a new [service declaration]({{< relref "terms/tracking-new-terms#declaring-a-new-service" >}}) with the new service name. You can reuse the `documents` 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.