CHA-1427 Fix links to suspension policy in event platform documentation (#1019)

Author: Vlaquit

content/event-platform/best-practices.md

@@ -43,7 +43,7 @@ If your 429 responses contains a `Retry-after` header, the platform **will not t
 
 ## Suspending and Resuming Subscriptions
 
-If you are unable to guarantee a positive response when events are sent (e.g. during infrastructure maintenance) you may decide to **`suspend/resume`** your subscription to avoid it being suspended in accordance with our [suspension policy](/event-platform/concepts.html#suspension-policy).
+If you are unable to guarantee a positive response when events are sent (e.g. during infrastructure maintenance) you may decide to **`suspend/resume`** your subscription to avoid it being suspended in accordance with our [suspension policy](/event-platform/key-platform-behaviors.html#suspension-policy).
 During the **suspension period**, events in the pipeline and new events generated by the PIM **`can't be recovered`**.
 You'll be able to receive new events as soon as you resume the subscription.
 
@@ -67,4 +67,4 @@ You must be prepared to ingest events from the event platform with a significant
     - example: you receive 9 product update events in your PubSub Topic, and your background process pulls 10 messages every second from the PubSub queue. You make 1 API call on the get list of products endpoint instead of 9 unitary calls.
 
 ::: panel-link Let's see some integration examples ! [Next](/event-platform/integration-examples.html)
-:::
+:::

content/event-platform/key-platform-behaviors.md

@@ -18,7 +18,7 @@ Our delivery engine will try to deliver events as fast as possible but will adap
 
 If your subscription has an HTTPS destination, please respond with `429 Too Many Requests` when your system is overloaded: this way, the delivery engine will slow down, retry undelivered events, and gradually increase the throughput when your system gets back to recovers (i.e., when it responds `200 OK` again).
 
-Please note that if the throughput drops too significantly, the suspension policy will be triggered ([see bellow](/event-platform/concepts.html#suspension-policy.html)).
+Please note that if the throughput drops too significantly, the suspension policy will be triggered ([see bellow](/event-platform/key-platform-behaviors.html#suspension-policy)).
 
 ## Delivery timeout
 
@@ -37,7 +37,7 @@ If your destination is unable to ingest an event, we will retry deliver as follo
  - Third retry: 20 minutes after the previous attempt.
 
 These retries are on a best-effort basis and apply only to transient errors or timeouts. After **three retry attempts**, the message is dropped.
-This type of failure may trigger the suspension policy ([see bellow](/event-platform/concepts.html#suspension-policy.html)).
+This type of failure may trigger the suspension policy ([see bellow](/event-platform/key-platform-behaviors.html#suspension-policy)).
 
 ## Suspension policy
 
@@ -65,4 +65,4 @@ Here are the errors type that decrease the success rate:
 When the platform suspends your subscription, a notification will be sent to the technical email address you provided, along with contextual information about the suspension.
 
 ::: panel-link Let's see the API reference! [Next](/event-platform/api-reference.html)
-:::
+:::