From e4c57d703460b9b43a15ffba8386b5d25d66ca74 Mon Sep 17 00:00:00 2001
From: Kenichi Yamamoto <kc-yamamoto@kddi.com>
Date: Tue, 12 Nov 2024 18:04:42 +0900
Subject: [PATCH] Update the link of the figures in the description for merge.

Co-authored-by: Eric Murray <eric.murray@vodafone.com>
---
 code/API_definitions/number-recycling.yaml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code/API_definitions/number-recycling.yaml b/code/API_definitions/number-recycling.yaml
index d044bee..0523d14 100644
--- a/code/API_definitions/number-recycling.yaml
+++ b/code/API_definitions/number-recycling.yaml
@@ -34,7 +34,7 @@ info:
           * ASP A decides to stop sending the SMS message to User A and contacts User A by mail.
         * By following these steps, ASP A ensures that a phone number is not linked to User A and prevents the mis-delivery of the SMS message.
 
-    <img width="4000" alt="Number_Recycling_scenario_2" src="https://raw.githubusercontent.com/yamamoto0104/NumberRecycling/refs/heads/yamamoto_initial-yaml_r1/documentation/API_documentation/assets/Number_Recycling_scenario_2.png">
+    <img width="4000" alt="Number_Recycling_scenario_2" src="https://raw.githubusercontent.com/camaraproject/NumberRecycling/main/documentation/API_documentation/assets/Number_Recycling_scenario_2.png">
 
     Note:
     * When the API receives a request with specified date during which there is no contract with MNO for the phone number, the API respond sets to 'true'(e.g., the period between 2024-02-25 and 2024-09-21 in the Scenario 2 of the figure above).