Fixing broken links

Author: msftrobiro

articles/sap/workloads/businessobjects-deployment-guide.md

@@ -213,7 +213,7 @@ For data tier, Azure Database as a Service (DBaaS) service provides high availab
 
 ### Availability sets
 
-Availability set is a logical grouping capability for isolating Virtual Machine (VM) resources from each other on being deployed. Azure makes sure of the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches. If a hardware or software failure happens, only a subset of your VMs is affected and your overall solution stays operational. So when virtual machines are placed in availability sets, Azure Fabric Controller distributes the VMs over different [Fault](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide.md#fault-domains) and [Upgrade](https://github.com/MicrosoftDocs/azure-docs/blob/main/articles/sap/workloads/planning-guide.md#upgrade-domains) domains to prevent all VMs from being inaccessible because of infrastructure maintenance or failure within one Fault domain.
+Availability set is a logical grouping capability for isolating Virtual Machine (VM) resources from each other on being deployed. Azure makes sure of the VMs you place within an Availability Set run across multiple physical servers, compute racks, storage units, and network switches. If a hardware or software failure happens, only a subset of your VMs is affected and your overall solution stays operational. So when virtual machines are placed in availability sets, Azure Fabric Controller distributes the VMs over different [Fault](./planning-guide.md#fault-domains) and Update domains to prevent all VMs from being inaccessible because of infrastructure maintenance or failure within one Fault domain.
 
 SAP BI Platform contains many different components and while designing the architecture you have to make sure that each of this component is resilient of any disruption. It can be achieved by placing Azure virtual machines of each component within availability sets. Keep in mind, when you mix VMs of different VM families within one availability set, you may come across problems that prevent you to include a certain VM type into such availability set. So have separate availability set for Web Application, BI Application for SAP BI Platform as highlighted in Architecture Overview.
 

articles/sap/workloads/planning-guide.md

@@ -479,7 +479,7 @@ Many Azure PaaS services are accessed by default through a public endpoint. Whil
 
 Use of private endpoints allows to easier protect against data leakage, often simplifies access from on-premises and peered networks. Also in many situations the network routing and process to open firewall ports, often needed for public endpoints, is simplified since the resources are inside your chosen network already with private endpoint use.
 
-See [available services](/azure/private-link/availability) to find which Azure services offer the usage of private endpoints. For NFS or SMB with Azure Files, the usage of private endpoints is always recommended for SAP workloads. See [private endpoint pricing](https://azure.microsoft.com/en-us/pricing/details/private-link/) about charges incurred with use of the service. Some Azure services might optionally include the cost with the service. Such case will be identified in each of those service's pricing information.
+See [available services](/azure/private-link/availability) to find which Azure services offer the usage of private endpoints. For NFS or SMB with Azure Files, the usage of private endpoints is always recommended for SAP workloads. See [private endpoint pricing](https://azure.microsoft.com/pricing/details/private-link/) about charges incurred with use of the service. Some Azure services might optionally include the cost with the service. Such case will be identified in each of those service's pricing information.
 
 ### Encryption
 
@@ -609,7 +609,7 @@ With large variety of SAP products, version dependencies and native OS and DBMS
 - **Using Azure services for SAP migration**
   Some VM based workloads are migrated without change to Azure using services such as [Azure Migrate](/azure/migrate/) or [Azure Site Recovery](/azure/site-recovery/physical-azure-disaster-recovery) or 3rd party tools. Diligently confirm the OS version and running workload is supported by the service. Very often any database workload is intentionally not supported as the service cannot guarantee database consistency. Should the DBMS type be supported by migration service, the database change / churn rate is often too high and most busy SAP systems will not meet the change rate the migration tools are allowing, with issues noticed only during production migration. In many situations, these Azure services are not suitable for migration of SAP systems. No validation of Azure Site Recovery or Azure Migrate for large scale SAP migration was performed and proven SAP migration methodology is to rely on DBMS replication or SAP migration tools.
 
-  A deployment in Azure instead of plain VM migration is preferable and easier to accomplish than on premise. Automated deployment frameworks such as [Azure Center for SAP solutions](../center-sap-solutions/overview) and [Azure deployment automation framework](../automation) allow for quick execution of automated tasks. Migration of SAP landscapes using DBMS native replication technologies such as HANA system replication, DBMS backup & restore or SAP migration tools onto the new deployed infrastructure uses established SAP know-how.
+  A deployment in Azure instead of plain VM migration is preferable and easier to accomplish than on premise. Automated deployment frameworks such as [Azure Center for SAP solutions](../center-sap-solutions/overview.md) and [Azure deployment automation framework](../automation/deployment-framework.md) allow for quick execution of automated tasks. Migration of SAP landscapes using DBMS native replication technologies such as HANA system replication, DBMS backup & restore or SAP migration tools onto the new deployed infrastructure uses established SAP know-how.
 
 - **Infrastructure up-sizing**
   During an SAP migration, additional infrastructure capacity can lead to quicker execution. The project team should consider up-sizing the [VM's size](/azure/virtual-machines/sizes) to provide more CPU and memory, as well as VM aggregate storage and network throughput. Similarly, on VM level, storage elements such as individual disks should be considered to increase throughput with [on-demand bursting](/azure/virtual-machines/disks-enable-bursting), [performance tiers](/azure/virtual-machines/disks-performance-tiers-portal) for Premium SSD v1. Increase IOPS and throughput values if using [Premium SSD v2](/azure/virtual-machines/disks-deploy-premium-v2?tabs=azure-cli#adjust-disk-performance) above configured values. Enlarge NFS / SMB file shares to increase performance limits. Keep in mind that Azure manage disks cannot be reduced in size and reduction in size, performance tiers and throughput KPIs can have various cooldown times.