Reviewed and refreshed

Author: VanMSFT

azure-sql/database/recovery-using-backups.md

@@ -5,7 +5,7 @@ description: Learn about point-in-time restore, which enables you to roll back a
 author: SudhirRaparla
 ms.author: nvraparl
 ms.reviewer: wiassaf, mathoma, danil
-ms.date: 07/20/2022
+ms.date: 08/21/2023
 ms.service: sql-database
 ms.subservice: backup-restore
 ms.topic: how-to
@@ -96,7 +96,7 @@ You generally restore a database to an earlier point for recovery purposes. You
 
   If you plan to retrieve data from the restored database to recover from a user or application error, you need to write and run a data recovery script that extracts data from the restored database and applies to the original database. Although the restore operation might take a long time to complete, the restoring database is visible in the database list throughout the restore process. 
 
-  If you delete the database during the restore, the restore operation will be canceled. You won't be charged for the database that did not complete the restore.
+  If you delete the database during the restore, the restore operation will be canceled. You won't be charged for the database that didn't complete the restore.
 
 ### [Azure portal](#tab/azure-portal)
 
@@ -138,7 +138,7 @@ To restore a database by using the REST API:
 
 ## Long-term backup restore
 
-To perform a restore operation on a long-term backup, you can use the Azure portal, the Azure CLI, Azure PowerShell, or the REST API. For more information, see [Restore a long-term backup](long-term-backup-retention-configure.md#view-backups-and-restore-from-a-backup). Long-term retention is not applicable to Hyperscale databases. 
+To perform a restore operation on a long-term backup, you can use the Azure portal, the Azure CLI, Azure PowerShell, or the REST API. For more information, see [Restore a long-term backup](long-term-backup-retention-configure.md#view-backups-and-restore-from-a-backup). Long-term retention isn't applicable to Hyperscale databases. 
 
 ### [Azure portal](#tab/azure-portal)
 
@@ -283,7 +283,7 @@ For more information on using geo-restore, see [Recovery using Geo-restore](reco
 > [!NOTE]
 > For detailed information about recover from an outage, see [Azure SQL Database disaster recovery guidance](disaster-recovery-guidance.md) and the [Azure SQL Database high availability and disaster recovery checklist](high-availability-disaster-recovery-checklist.md). 
 
-Geo-restore is the most basic disaster-recovery solution available in SQL Database. It relies on automatically created geo-replicated backups with a recovery point objective (RPO) of up to 1 hour and an estimated recovery time objective (RTO) of up to 12 hours. It doesn't guarantee that the target region will have the capacity to restore your databases after a regional outage, because a sharp increase of demand is likely. If your application uses relatively small databases and is not critical to the business, geo-restore is an appropriate disaster-recovery solution. 
+Geo-restore is the most basic disaster-recovery solution available in SQL Database. It relies on automatically created geo-replicated backups with a recovery point objective (RPO) of up to 1 hour and an estimated recovery time objective (RTO) of up to 12 hours. It doesn't guarantee that the target region will have the capacity to restore your databases after a regional outage, because a sharp increase of demand is likely. If your application uses relatively small databases and isn't critical to the business, geo-restore is an appropriate disaster-recovery solution. 
 
 For business-critical applications that require large databases and must ensure business continuity, use [auto-failover groups](auto-failover-group-sql-db.md). That feature offers a much lower RPO and RTO, and the capacity is always guaranteed. 
 

docs/relational-databases/indexes/columnstore-indexes-overview.md

@@ -3,7 +3,7 @@ title: "Columnstore indexes: Overview"
 description: "An overview on columnstore indexes. Columnstore indexes are the standard for storing and querying large data warehousing fact tables."
 author: MikeRayMSFT
 ms.author: mikeray
-ms.date: 07/25/2022
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: table-view-index
 ms.topic: conceptual
@@ -61,7 +61,7 @@ A column segment is a column of data from within the rowgroup.
 
 - Each rowgroup contains one column segment for every column in the table.  
 - Each column segment is compressed together and stored on physical media.
-- There is metadata with each segment to allow for fast elimination of segments without reading them.
+- There's metadata with each segment to allow for fast elimination of segments without reading them.
 
 ![Column segment](../../relational-databases/indexes/media/sql-server-pdw-columnstore-columnsegment.png "Column segment")  
 
@@ -80,7 +80,7 @@ A delta rowgroup is a clustered B-tree index that's used only with columnstore i
 
 When a delta rowgroup reaches the maximum number of rows, it transitions from an OPEN to CLOSED state. A background process named the tuple-mover checks for closed row groups. If the process finds a closed rowgroup, it compresses the delta rowgroup and stores it into the columnstore as a COMPRESSED rowgroup. 
 
-When a delta rowgroup has been compressed, the existing delta rowgroup transitions into TOMBSTONE state to be removed later by the tuple-mover when there is no reference to it. 
+When a delta rowgroup has been compressed, the existing delta rowgroup transitions into TOMBSTONE state to be removed later by the tuple-mover when there's no reference to it. 
 
 For more information about rowgroup statuses, see [sys.dm_db_column_store_row_group_physical_stats (Transact-SQL)](../../relational-databases/system-dynamic-management-views/sys-dm-db-column-store-row-group-physical-stats-transact-sql.md). 
 
@@ -134,7 +134,7 @@ Beginning with [!INCLUDE[sql-server-2022](../../includes/sssql22-md.md)], ordere
 ### Can I combine rowstore and columnstore on the same table?  
 Yes. Beginning with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], you can create an updatable nonclustered columnstore index on a rowstore table. The columnstore index stores a copy of the selected columns, so you need extra space for this data, but the selected data is compressed on average 10 times. You can run analytics on the columnstore index and transactions on the rowstore index at the same time. The columnstore is updated when data changes in the rowstore table, so both indexes work against the same data.  
 
-Beginning with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], you can have one or more nonclustered rowstore indexes on a columnstore index and perform efficient table seeks on the underlying columnstore. Other options become available too. For example, you can enforce a primary key constraint by using a UNIQUE constraint on the rowstore table. Because a non-unique value fails to insert into the rowstore table, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can't insert the value into the columnstore.  
+Beginning with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], you can have one or more nonclustered rowstore indexes on a columnstore index and perform efficient table seeks on the underlying columnstore. Other options become available too. For example, you can enforce a primary key constraint by using a UNIQUE constraint on the rowstore table. Because a nonunique value fails to insert into the rowstore table, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] can't insert the value into the columnstore.  
 
 ## Metadata  
 All of the columns in a columnstore index are stored in the metadata as included columns. The columnstore index doesn't have key columns.  
@@ -201,7 +201,7 @@ All relational tables, unless you specify them as a clustered columnstore index,
 
 When you create a table with the `CREATE TABLE` statement, you can create the table as a columnstore by specifying the `WITH CLUSTERED COLUMNSTORE INDEX` option. If you already have a rowstore table and want to convert it to a columnstore, you can use the `CREATE COLUMNSTORE INDEX` statement.  
 
-|Task|Reference topics|Notes|  
+|Task|Reference articles|Notes|  
 |----------|----------------------|-----------|  
 |Create a table as a columnstore.|[CREATE TABLE (Transact-SQL)](../../t-sql/statements/create-table-transact-sql.md)|Beginning with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], you can create the table as a clustered columnstore index. You don't have to first create a rowstore table and then convert it to columnstore.|  
 |Create a memory table with a columnstore index.|[CREATE TABLE (Transact-SQL)](../../t-sql/statements/create-table-transact-sql.md)|Beginning with [!INCLUDE[sssql16-md](../../includes/sssql16-md.md)], you can create a memory-optimized table with a columnstore index. The columnstore index can also be added after the table is created by using the `ALTER TABLE ADD INDEX` syntax.|  
@@ -221,7 +221,7 @@ When you create a table with the `CREATE TABLE` statement, you can create the ta
 
 ## Next steps
 
- [What's new in columnstore indexes](columnstore-indexes-what-s-new.md)
+ [What's new in columnstore indexes](columnstore-indexes-what-s-new.md)   
  [Columnstore indexes data loading](~/relational-databases/indexes/columnstore-indexes-data-loading-guidance.md)   
  [Columnstore indexes versioned feature summary](~/relational-databases/indexes/columnstore-indexes-what-s-new.md)   
  [Columnstore indexes query performance](~/relational-databases/indexes/columnstore-indexes-query-performance.md)   

docs/relational-databases/tables/create-foreign-key-relationships.md

@@ -4,7 +4,7 @@ description: "Create Foreign Key Relationships"
 author: WilliamDAssafMSFT
 ms.author: wiassaf
 ms.reviewer: vanto, randolphwest
-ms.date: 07/25/2022
+ms.date: 08/21/2023
 ms.service: sql
 ms.subservice: table-view-index
 ms.topic: conceptual