From 77b8feff38b75fdf93591372b286f145233530c2 Mon Sep 17 00:00:00 2001
From: vincentlel <48972214+vincentlel@users.noreply.github.com>
Date: Fri, 3 May 2024 12:34:26 -0500
Subject: [PATCH] update link to support

---
 Lifecycle_management.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Lifecycle_management.md b/Lifecycle_management.md
index 80a9d2a..88e015e 100644
--- a/Lifecycle_management.md
+++ b/Lifecycle_management.md
@@ -87,9 +87,9 @@ In case of service outage, here is the troubleshooting process:
 - Select your cluster in the group and Click *"Run query"*
 
 ![CloudWatch_LogInsight](images/CloudWatch_LogInsight.png "CloudWatch_LogInsight")
-CloudWatch_LogInsight
+
 - Run your root cause analysis based traces
-- If a source code update is required, please create a ticket [here](/User%20guide.html#support)
+- If a source code update is required, please create a ticket [here](reflectance-datacube-processor/User%20guide.html#support)
 
 To restore service leveraging a previous task definition, please fo 
 
@@ -111,7 +111,7 @@ If you are using the ECS deployment model, it will leverage the following billab
  - Simple Storage Service (S3)
 
 
-To manage running cost, you can define service limits leveraging [AWS service quotas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html#service-quotas-fargate). For example you can control Fargate capacity like number of vCPUs running concurrently in the current region
+To manage running cost, you can define service limits leveraging [AWS service quotas](https://docs.aws.amazon.com/AmazonECS/latest/developerguide/service-quotas.html#service-quotas-fargate). For example you can control Fargate capacity like number of vCPUs running concurrently in the current region.
 
 
 ### Additional Information