Fix typo: should't -> shouldn't

Author: changeworld

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

@@ -48,7 +48,7 @@ There's some SQL Server in IaaS specific information you should know before cont
 
 
 ## New M-series VMs and SQL Server
-Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family should't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accommodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16&preserve-view=true#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
+Azure released a few new families of M-series SKUs under the family of Mv3. Some of the VM types in this family shouldn't be used for SQL Server, including SQL Server 2022 without disabling SMT (Hyperthreading) in the Windows Server guest OS. Reason is the number of NUMA nodes presented into the Windows Server guest OS which with larger than 64 vCPUs is too large for SQL Server to accommodate. By disabling SMT in the Windows Server guest OS, the number of vCPUs is getting reduced. So, that the number of vCPUs is less than 64 in each NUMA node. The way how to disable SMT is described [here](/sql/sql-server/compute-capacity-limits-by-edition-of-sql-server?view=sql-server-ver16&preserve-view=true#disable-smt-in-an-azure-virtual-machine). The specific VM types are:
 - M176(d)s_3_v3 - disable SMT or use M176bds_4_v3 or M176bds_4_v3 as alternative
 - M176(d)s_4_v3 - disable SMT or use M176bds_4_v3 as alternative
 - M624(d)s_12_v3 - disable SMT or use M416ms_v2 as alternative