Merge branch '2021_tiersplit' of https://github.com/MashaMSFT/azure-docs-pr into 2021_tiersplit

Author: MashaMSFT

articles/azure-sql/database/service-tier-hyperscale.md

@@ -98,7 +98,6 @@ The vCore-based service tiers are differentiated based on database availability
 | **IOPS** | 500 IOPS per vCore with 7000 maximum IOPS | Hyperscale is a multi-tiered architecture with caching at multiplelevels. Effective IOPS will depend on the workload. | 5000 IOPS with 200,000 maximum IOPS|
 |**Availability**| 1 replica, no Read Scale-out, zone-redundant HA (preview), no local cache | Multiple replicas, up to 4 Read Scale-out, partiallocal cache | 3 replicas, 1 Read Scale-out, zone-redundant HA, full local storage |
 |**Backups** | A choice of geo-redundant, zone-redundant <sup>2</sup> , or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) | A choice of geo-redundant, zone-redundant <sup>3</sup>, or locally-redundant<sup>3</sup> backup storage, 7 day retention. | A choice of geo-redundant,zone-redundant<sup>2</sup>, or locally-redundant<sup>2</sup> backup storage, 1-35 day retention (default 7 days) |
-||||
 
 <sup>1</sup> Elastic pools are not supported in the Hyperscale service tier   
 <sup>2</sup> In preview