Add hana shared considerations

Author: rdeltcheva

articles/sap/workloads/get-started.md

@@ -55,6 +55,7 @@ In the SAP workload documentation space, you can find the following areas:
 
 ## Change Log
 
+- March 18, 2024: Added considerations for sizing the HANA shared file system in [SAP HANA Azure virtual machine storage configurations](./hana-vm-operations-storage.md)
 - February 07, 2024: Clarified disk allocation when using PPGs to bind availability set in specific Availability Zone in [Configuration options for optimal network latency with SAP applications](./proximity-placement-scenarios.md#combine-availability-sets-and-availability-zones-with-proximity-placement-groups)
 - February 01, 2024: Added guidance for [SAP front-end printing to Universal Print](./universal-print-sap-frontend.md).
 - January 24, 2024: Split [SAP RISE integration documentation](./rise-integration.md) into multiple segments for improved legibility, additional overview information added.

articles/sap/workloads/hana-vm-operations-storage.md

@@ -112,8 +112,8 @@ The SAP guidelines for **/hana/shared** recommended  sizes would look like:
 | /hana/shared scale-out | 1 x RAM of worker node<br /> per four worker nodes  |
 
 Consult the following SAP notes for more details: 
-[3288971 - FAQ: SUSE HAE/RedHat HAA Pacemaker Cluster Resource Manager in SAP HANA System Replication Environments](https://me.sap.com/notes/3288971)
-[1999930 - FAQ: SAP HANA I/O Analysis](https://me.sap.com/notes/1999930)
+[3288971 - FAQ: SUSE HAE/RedHat HAA Pacemaker Cluster Resource Manager in SAP HANA System Replication Environments](https://me.sap.com/notes/3288971)  
+[1999930 - FAQ: SAP HANA I/O Analysis](https://me.sap.com/notes/1999930)  
 
 As a best practice, size **/hana/shared** to avoid performance bottlenecks. 
 Remember that a well-sized **/hana/shared** file system contributes to the stability and reliability of your SAP HANA system, especially in HA scenarios.