corrects the links

Author: varun-dhawan

articles/postgresql/flexible-server/how-to-cost-optimization.md

@@ -29,15 +29,15 @@ This article provides a list of recommendations for optimizing Azure Postgres Fl
 
 Azure Postgres reserved capacity pricing allows committing to a specific capacity for 1-3 years, saving costs for customers using Azure Database for PostgreSQL service. The cost savings compared to pay-as-you-go pricing can be significant, depending on the amount of capacity reserved and the length of the term. Customers can purchase reserved capacity in increments of vCores and storage. Reserved capacity can cover costs for Azure Database for PostgreSQL servers in the same region, applied to the customer's Azure subscription. Reserved Pricing for Azure Postgres Flexible Server offers cost savings up to 40% for 1 year and up to 60% for 3-year commitments, for customers who reserve capacity. For more details, please refer Pricing Calculator | Microsoft Azure
 
-To learn more, refer [What are Azure Reservations?](https://learn.microsoft.com/en-us/azure/cost-management-billing/reservations/save-compute-costs-reservations)
+To learn more, refer [What are Azure Reservations?](../../cost-management-billing/reservations/save-compute-costs-reservations.md)
 
 ## 2. Scale compute Up/Down
 
 Scaling up or down the resources of an Azure Database for PostgreSQL server can help you optimize costs. Adjust the vCores and storage as needed to only pay for necessary resources. Scaling can be done through the Azure portal, Azure CLI, or Azure REST API. Scaling compute resources up or down can be done at any time and requires server restart. It's good practice to monitor your database usage patterns and adjust the resources accordingly to optimize costs and ensure performance. For more details, please refer Compute and Storage options in Azure Database for PostgreSQL - Flexible Server.
 
 Configure Non-prod environments conservatively - Configure idle dev/test/stage environments to have cost-efficient SKUs. Choosing Burstable SKUs is ideal for workloads that don't need continuous full capacity.
 
-To learn more, refer [Scale operations in Flexible Server.](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-scale-compute-storage-portal)
+To learn more, refer [Scale operations in Flexible Server](how-to-scale-compute-storage-portal.md)
 
 ## 3. Using Azure advisor recommendations
 
@@ -47,7 +47,7 @@ For Azure Database for PostgreSQL, Azure Advisor can provide recommendations on
 
 You can access the recommendations provided by Azure Advisor through the Azure portal, where you can view and implement the recommendations with just a few clicks. Implementing Azure Advisor recommendations can help you optimize your Azure resources and reduce costs. For more details, refer Azure Advisor for PostgreSQL - Flexible Server.
 
-To learn more, refer [Azure Advisor for PostgreSQL.](https://learn.microsoft.com/en-us/azure/advisor/advisor-reference-performance-recommendations#postgresql)
+To learn more, refer [Azure Advisor for PostgreSQL](concepts-azure-advisor-recommendations.md)
 
 ## 4. Evaluate HA (high availability) and DR (disaster recovery) requirements
 
@@ -57,7 +57,7 @@ If your workload requires AZ resiliency and lower RTO, you can enable High Avail
 
 Key take away is to evaluate the requirement of your full application stack and then choose the right configuration for the Flexible Server. For example, if your application isn't AZ resilient, there's nothing to be gained by configuring Flexible Server in AZ resilient configuration.
 
-To learn more, refer [High availability architecture in Flexible Server.](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/concepts-high-availability)
+To learn more, refer [High availability architecture in Flexible Server](concepts-high-availability.md)
 
 ## 5. Consolidate databases and servers
 
@@ -71,7 +71,7 @@ Consolidating databases can be a cost-saving strategy for Azure Database for Pos
 
 Consolidating databases can help you save costs by reducing the number of Flexible Server instances you need to run and by enabling you to use larger instances that are more cost-effective than smaller instances. It is important to evaluate the impact of consolidation on your databases' performance and ensure that the consolidated Flexible Server instance is appropriately sized to meet all database needs.
 
-To learn more, refer [Improve the performance of Azure applications by using Azure Advisor.](https://learn.microsoft.com/en-us/azure/advisor/advisor-performance-recommendations)
+To learn more, refer [Improve the performance of Azure applications by using Azure Advisor](../../advisor/advisor-reference-performance-recommendations.md#postgresql)
 
 ## 6. Place test servers in cost-efficient geo-regions
 
@@ -84,7 +84,7 @@ Creating a test server in a cost-efficient Azure region can be a cost-saving str
 
 By creating a test server in a cost-efficient Azure region, you can reduce the cost of running your test server and minimize the cost of running Azure Database for PostgreSQL. It is important to evaluate the impact of the region on your test server's performance and your organization's specific regional requirements. This ensures that network latency and data transfer costs are acceptable for your use case. For more details, refer Azure Database for PostgreSQL pricing.
 
-To learn more, refer [Azure regions](https://learn.microsoft.com/en-us/azure/architecture/framework/cost/design-regions)
+To learn more, refer [Azure regions](/azure/architecture/framework/cost/design-regions)
 
 ## 7. Starting and Stopping servers
 
@@ -97,7 +97,7 @@ Starting and stopping servers can be a cost-saving strategy for Azure Database f
 
 By starting and stopping the server as needed, you can reduce the cost of running Azure Database for PostgreSQL. To ensure smooth database performance, it is crucial to evaluate the impact of starting and stopping the server and have a reliable process in place for these actions as required. To learn more, refer Stop/Start an Azure Database for PostgreSQL - Flexible Server.
 
-To learn more, refer [Stop/Start Flexible Server Instance.](https://learn.microsoft.com/en-us/azure/postgresql/flexible-server/how-to-stop-start-server-portal)
+To learn more, refer [Stop/Start Flexible Server Instance](how-to-stop-start-server-portal.md)
 
 ## 8. Archive old data for cold storage
 
@@ -112,7 +112,7 @@ Archiving infrequently accessed data to Azure archive store (while still keeping
 
 You can also use Azure Data Factory to automate this process.
 
-To learn more, refer [Migrate your PostgreSQL database by using dump and restore.](https://learn.microsoft.com/en-us/azure/postgresql/migrate/how-to-migrate-using-dump-and-restore)
+To learn more, refer [Migrate your PostgreSQL database by using dump and restore](../migrate/how-to-migrate-using-dump-and-restore.md)
 
 ## Tradeoffs for cost
 
@@ -134,7 +134,7 @@ As you design your application database on Azure Database for PostgerSQL Flexibl
 
 To learn more about Cost optimization, see:
 
-* [Overview of the cost optimization pillar](https://learn.microsoft.com/en-us/azure/architecture/framework/cost/overview)
-* [Tradeoffs for cost](https://learn.microsoft.com/en-us/azure/architecture/framework/cost/tradeoffs)
-* [Checklist - Optimize cost](https://learn.microsoft.com/en-us/azure/architecture/framework/cost/optimize-checklist?source=recommendations)
-* [Checklist - Monitor cost](https://learn.microsoft.com/en-us/azure/architecture/framework/cost/monitor-checklist)git 
+* [Overview of the cost optimization pillar](/azure/architecture/framework/cost/overview)
+* [Tradeoffs for cost](/azure/architecture/framework/cost/tradeoffs)
+* [Checklist - Optimize cost](/azure/architecture/framework/cost/optimize-checklist)
+* [Checklist - Monitor cost](/azure/architecture/framework/cost/monitor-checklist)