Merge pull request #232222 from msjuergent/pv2

add storage block size

Author: prmerger-automator[bot]

articles/sap/workloads/dbms-guide-sapase.md

@@ -214,7 +214,7 @@ There are two supported High Availability configurations for SAP ASE on Azure:
 
 
 > [!NOTE]
-> The failover times and other characteristics of either HA Aware or Floating IP solutions are similar.  When deciding between these two solutions customers should perform their own testing and evaluation including factors such as planned and unplanned failover times and other operational procedures. High Availability Clusters based on Pacemaker are **NOT** supported at this point in time on Azure. 
+> The failover times and other characteristics of either HA Aware or Floating IP solutions are similar.  When deciding between these two solutions customers should perform their own testing and evaluation including factors such as planned and unplanned failover times and other operational procedures. 
 
 ### Third node for disaster recovery
 Beyond using SAP ASE Always-On for local high availability, you might want to extend the configuration to an asynchronously replicated node in another Azure region. For more information, see [Installation Procedure for Sybase 16. 3 Patch Level 3 Always-on + DR on Suse 12.3](https://techcommunity.microsoft.com/t5/running-sap-applications-on-the/installation-procedure-for-sybase-16-3-patch-level-3-always-on/ba-p/368199).