Merge pull request #50224 from CarlRabeler/patch-190

Update sql-database-service-tiers-vcore.md

Author: PRMerger20

articles/sql-database/sql-database-service-tiers-vcore.md

@@ -6,7 +6,7 @@ author: CarlRabeler
 ms.service: sql-database
 ms.custom: DBs & servers
 ms.topic: conceptual
-ms.date: 08/15/2018
+ms.date: 08/27/2018
 manager: craigg
 ms.author: carlrab
 
@@ -30,8 +30,8 @@ The following table helps you understand the differences between these two tiers
 |Best for|Most business workloads. Offers budget oriented balanced and scalable compute and storage options.|Business applications with high IO requirements. Offers highest resilience to failures using several isolated replicas.|
 |Compute|Gen4: 1 to 24 vCore<br/>Gen5: 1 to 80 vCore|Gen4: 1 to 24 vCore<br/>Gen5: 1 to 80 vCore|
 |Memory|Gen4: 7 GB per core<br>Gen5: 5.5 GB per core | Gen4: 7 GB per core<br>Gen5: 5.5 GB per core |
-|Storage|[Premium remote storage](../virtual-machines/windows/premium-storage.md),<br/>Singleton Database: 5 GB – 4 TB<br/>Managed Instance: 32 GB - 8 TB |Local SSD storage,<br/>Single Database: 5 GB – 4 TB<br/>Managed Instance: 32 GB - 4 TB |
-|IO throughput (approximate)|Singleton Database: 500 IOPS per vCore with 7000 maximum IOPS</br>Managed Instance: Depends on [size of file](../virtual-machines/windows/premium-storage-performance.md#premium-storage-disk-sizes)|5000 IOPS per core with 200000 maximum IOPS|
+|Storage|[Premium remote storage](../virtual-machines/windows/premium-storage.md),<br/>Single Database: 5 GB – 4 TB<br/>Managed Instance: 32 GB - 8 TB |Local SSD storage,<br/>Single Database: 5 GB – 1 TB<br/>Managed Instance: 32 GB - 4 TB |
+|IO throughput (approximate)|Single Database: 500 IOPS per vCore with 7000 maximum IOPS</br>Managed Instance: Depends on [size of file](../virtual-machines/windows/premium-storage-performance.md#premium-storage-disk-sizes)|5000 IOPS per core with 200000 maximum IOPS|
 |Availability|1 replica, no read-scale|3 replicas, 1 [read-scale replica](sql-database-read-scale-out.md),<br/>zone redundant HA|
 |Backups|[RA-GRS](../storage/common/storage-designing-ha-apps-with-ragrs.md), 7-35 days (7 days by default)|[RA-GRS](../storage/common/storage-designing-ha-apps-with-ragrs.md), 7-35 days (7 days by default)|
 |In-Memory|N/A|Supported|
@@ -48,10 +48,10 @@ See [SQL Database FAQ](sql-database-faq.md) for answers to frequently asked ques
 
 Consider the following:
 - The allocated storage is used by data files (MDF) and log files (LDF) files.
-- Each Singleton Database performance level supports a maximum database size, with a default max size of 32 GB.
-- When you configure the required Singleton database size (size of MDF), 30% of additional storage is automatically added to support LDF
+- Each single database performance level supports a maximum database size, with a default max size of 32 GB.
+- When you configure the required single database size (size of MDF), 30% of additional storage is automatically added to support LDF
 - Storage size in Managed Instance must be specified in multiples of 32 GB.
-- You can select any Singleton database size between 10 GB and the supported maximum
+- You can select any singleton database size between 10 GB and the supported maximum
  - For Standard storage, increase or decrease size in 10-GB increments
  - For Premium storage, increase or decrease size in 250-GB increments
 - In the General Purpose service tier, `tempdb` uses an attached SSD and this storage cost is included in the vCore price.