Fix UUF items (424036, 430131)

Author: rwestMSFT

docs/database-engine/install-windows/validate-a-sql-server-installation.md

@@ -11,15 +11,15 @@ helpviewer_keywords:
   - "validating installations [SQL Server]"
 monikerRange: ">=sql-server-2016"
 ---
-# Validate a SQL Server Installation
+# Validate a SQL Server installation
 
 [!INCLUDE [SQL Server -Windows Only](../../includes/applies-to-version/sql-windows-only.md)]
 
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report can be used to verify the version of [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] and the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features installed on the computer. The **Installed SQL Server features discovery report** displays a report of all products and features installed on the local server, for [!INCLUDE [ssVersion2000](../../includes/ssversion2000-md.md)] and later versions. The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report is available on the **Tools** page on the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center.
 
 ## Run SQL Server features discovery report
 
-Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, point to **Configuration Tools**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
+Launch the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] Installation center, using the **Start** menu, point to **All Programs**, point to **Microsoft SQL Server \<Version Name>**, and select **SQL Server Installation Center**. To run the [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] features discovery report, select **Tools** in the left-hand navigation area of **SQL Server Installation Center**, and then select **Installed SQL Server features discovery report**.
 
 The [!INCLUDE [ssNoVersion](../../includes/ssnoversion-md.md)] discovery report is saved to `%ProgramFiles%\Microsoft SQL Server\<nnn>\Setup Bootstrap\Log\<last Setup Session>`.
 

docs/integration-services/change-data-capture/the-oracle-cdc-databases.md

@@ -79,7 +79,7 @@ ms.topic: conceptual
 
  For the Oracle CDC, the LSN values stored in this table are based on the Oracle System Change Number (SCN) value associated with the change. The first 6 bytes of the LSN value is the original Oracle SCN number.  
 
- Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight savings time changes do not impact the data stored in the lsn_time_mapping.  
+ Also when using the Oracle CDC, the time columns (`tran_begin_time` and `tran_end_time`) store the UTC time of the change rather than the local time as it does with the regular SQL Server CDC. This ensures that daylight saving time changes do not impact the data stored in the lsn_time_mapping.  
 
 ### cdc.xdbcdc_config
 

docs/relational-databases/system-catalog-views/sys-time-zone-info-transact-sql.md

@@ -28,7 +28,7 @@ monikerRange: "=azure-sqldw-latest || >=sql-server-2016 || >=sql-server-linux-20
 | --- | --- | --- |
 | `name` | **sysname** | Name of the time zone in Windows standard format. For example, `Cen. Australia Standard Time` or `Central European Standard Time`. |
 | `current_utc_offset` | **nvarchar(12)** | Current offset to UTC. For example, `+01:00` or `-07:00`. |
-| `is_currently_dst` | **bit** | True if currently observing daylight savings time. |
+| `is_currently_dst` | **bit** | True if currently observing daylight saving time. |
 
 ## Remarks
 

docs/t-sql/data-types/datetimeoffset-transact-sql.md

@@ -160,9 +160,9 @@ First, verify the time zone name from the [sys.time_zone_info](../../relational-
 SELECT * FROM sys.time_zone_info WHERE name = 'Pacific Standard Time';
 ```
 
-The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight savings time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
+The following example uses the [AT TIME ZONE](../queries/at-time-zone-transact-sql.md) syntax twice. The sample code creates a table `dbo.Audit`, adds data that spans multiple daylight saving time changes, and adds a new **datetimeoffset** column. We assume that the `AuditCreated` column is a ***datetime2** data type without offsets, and was written using the UTC time zone.
 
-In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight savings time range in the United States.
+In the `UPDATE` statement, the `AT TIME ZONE` syntax first adds UTC time zone offset to the existing `AuditCreated` column data, then converts the data from UTC to `Pacific Standard Time`, correctly adjusting the historical data for each past daylight saving time range in the United States.
 
 ```sql
 CREATE TABLE dbo.Audit (AuditCreated DATETIME2(0) NOT NULL);