[SCOPED] Spelling fixes - part 004 (PR 9986)

Author: rwestMSFT

docs/analytics-platform-system/understanding-admin-console-alerts.md

@@ -67,7 +67,7 @@ The following table lists alerts alphabetically by name. The list doesn't includ
 |External Storage Array has a NON-CRITICAL status.|Yes|Degraded|Warning|The external storage array reported a non-critical warning (vendor operational status: `3`, `4`, `5`, `11`, `14`, `15`, `17`). Vendor status is reported in the component's `storage_global_status` property. Values: `3-Degraded`, `4-Stressed`, `5-Predictive Failure`, `11-In Service`, `14-Aborted`, `15-Dormant`, `17-Completed Operation`.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |External Storage Array has a NON-RECOVERABLE status.|Yes|Failed|Error|The external storage array is indicating that it's down and non-recoverable (vendor operational status: `7`). Vendor status is reported in the component's `storage_global_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |External Storage Array has a NORMAL status.|No|Operational|Informational|The external storage array is working normally (vendor status: `ok`). Vendor status is reported in the component's `storage_global_status` property.||  
-|External Storage Array has an UNKNOWN status.|Yes|Degraded|Warning|The status of the external storage array couldn't be determined based on the vendor status (vendor operational status: `0`, `1`, `18`). Vendor status is reported in the component's `storage_global_status` property. Values: `0-Unkown`, `1-Other`, `18-Power Mode`.|Review the node's Windows event log for details, or contact the device manufacturer.|  
+|External Storage Array has an UNKNOWN status.|Yes|Degraded|Warning|The status of the external storage array couldn't be determined based on the vendor status (vendor operational status: `0`, `1`, `18`). Vendor status is reported in the component's `storage_global_status` property. Values: `0-Unknown`, `1-Other`, `18-Power Mode`.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |External Storage Array has an UNREACHABLE status.|Yes|Failed|Error|The external storage array is indicating that it's unreachable (vendor operational status: `8`, `9`, `10`, `12`, `13`). Vendor status is reported in the component's `storage_global_status` property. Values: `8-Starting`, `9-Stopping`, `10-Stopped`, `12-No Contact`, `13-Lost Communication`.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |External Storage has a CRITICAL status.|Yes|Failed|Error|The external storage is indicating there's a failure.|Troubleshooting is required. Review the Windows event log and the storage device's event log for details.|  
 |External Storage has a DEGRADED status.|Yes|Degraded|Warning|The storage system is degraded. You need to check the temperature status or power supply status of this storage system. Additionally, if the side panel for the storage system is removed, the air flow changes might result in improper cooling of the drives and affect the temperature status. Vendor status is reported in the component's `storage_global_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
@@ -128,7 +128,7 @@ The following table lists alerts alphabetically by name. The list doesn't includ
 |Storage Enclosure Fan has a DEGRADED status.|Yes|Degraded|Warning|The storage enclosure fan is reporting that it's degraded (vendor status: `10`, `15`). Vendor status is reported in the component's `storage_fan_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |Storage Enclosure Fan has a FAILED status.|Yes|Failed|Warning|The storage enclosure fan is reporting that it's in a failed state. This status requires a component to be replaced (vendor status: `20`, `25`). Vendor status is reported in the component's `storage_fan_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |Storage Enclosure Fan has a NON-RECOVERABLE status.|Yes|Failed|Warning|The storage enclosure fan is reporting that it's in a non-recoverable state. This alert requires a component to be replaced (vendor status: `30`). Vendor status is reported in the component's `storage_fan_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
-|Storage Enclosure Fan has an UNKOWN status.|Yes|Degraded|Error|The status of the storage enclosure fan couldn't be determined (vendor status: `0-Unknown`). Vendor status is reported in the component's `storage_fan_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
+|Storage Enclosure Fan has an UNKNOWN status.|Yes|Degraded|Error|The status of the storage enclosure fan couldn't be determined (vendor status: `0-Unknown`). Vendor status is reported in the component's `storage_fan_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |Storage Enclosure Fan has a NORMAL status.|No|Operational|Informational|The storage enclosure fan is operating normally (vendor status: `5`). Vendor status is reported in the component's `storage_fan_status` property.||  
 |Storage Enclosure Power Supply has a DEGRADED status.|Yes|Degraded|Warning|The storage enclosure power supply is reporting that it's degraded (vendor status: `10`, `15`). Vendor status is reported in the component's `storage_power_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  
 |Storage Enclosure Power Supply has a FAILED status.|Yes|Failed|Error|The storage enclosure power supply is reporting that it's in a failed state. This state requires a component to be replaced or power to be restored to the device (vendor status: `20`, `25`). Vendor status is reported in the component's `storage_power_status` property.|Review the node's Windows event log for details, or contact the device manufacturer.|  

docs/connect/oledb/ole-db-data-types/ssvariant-structure.md

@@ -63,7 +63,7 @@ V_SS_DATETIMEOFFSET(pssVar).bScale = bScale;
 |dDateVal|DBTYPE_DATE|**DBDATE**|**VT_SS_DATE**|Supports the **date**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type.|  
 |tsDateTimeVal|DBTYPE_DBTIMESTAMP|**DBTIMESTAMP**|**VT_SS_SMALLDATETIME VT_SS_DATETIME VT_SS_DATETIME2**|Supports the **smalldatetime**, **datetime**, and **datetime2**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data types.|  
 |Time2Val|DBTYPE_DBTIME2|**DBTIME2**|**VT_SS_TIME2**|Supports the **time**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type.<br /><br /> Includes the following members:<br /><br /> *tTime2Val* (**DBTIME2**)<br /><br /> *bScale* (**BYTE**) Specifies the scale for *tTime2Val* value.|  
-|DateTimeVal|DBTYPE_DBTIMESTAMP|**DBTIMESTAMP**|**VT_SS_DATETIME2**|Supports the **datetime2**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type.<br /><br /> Includes the following members:<br /><br /> *tsDataTimeVal* (DBTIMESTAMP)<br /><br /> *bScale* (**BYTE**) Specifies the scale for *tsDataTimeVal* value.|  
+|DateTimeVal|DBTYPE_DBTIMESTAMP|**DBTIMESTAMP**|**VT_SS_DATETIME2**|Supports the **datetime2**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type.<br /><br /> Includes the following members:<br /><br /> *tsDateTimeVal* (DBTIMESTAMP)<br /><br /> *bScale* (**BYTE**) Specifies the scale for *tsDateTimeVal* value.|  
 |DateTimeOffsetVal|DBTYPE_DBTIMESTAMPOFFSET|**DBTIMESTAMPOFFSET**|**VT_SS_DATETIMEOFFSET**|Supports the **datetimeoffset**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data type.<br /><br /> Includes the following members:<br /><br /> *tsoDateTimeOffsetVal* (**DBTIMESTAMPOFFSET**)<br /><br /> *bScale* (**BYTE**) Specifies the scale for *tsoDateTimeOffsetVal* value.|  
 |NCharVal|No corresponding OLE DB type indicator.|**struct _NCharVal**|**VT_SS_WVARSTRING,**<br /><br /> **VT_SS_WSTRING**|Supports the **nchar** and **nvarchar**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data types.<br /><br /> Includes the following members:<br /><br /> *sActualLength* (**SHORT**) Specifies the actual length for the string to which *pwchNCharVal* points. Does not include terminating zero.<br /><br /> *sMaxLength* (**SHORT**) Specifies the maximum length for the string to which *pwchNCharVal* points.<br /><br /> *pwchNCharVal* (**WCHAR** \*) Pointer to the string.<br /><br /> *rgbReserved* (**BYTE[5]**) Specifies the collation information.<br /><br /> Unused members: *dwReserved*, and *pwchReserved*.|  
 |CharVal|No corresponding OLE DB type indicator.|**struct _CharVal**|**VT_SS_STRING,**<br /><br /> **VT_SS_VARSTRING**|Supports the **char** and **varchar**[!INCLUDE[ssNoVersion](../../../includes/ssnoversion-md.md)] data types.<br /><br /> Includes the following members:<br /><br /> *sActualLength* (**SHORT**) Specifies the actual length for the string to which *pchCharVal* points. Does not include terminating zero.<br /><br /> *sMaxLength* (**SHORT**) Specifies the maximum length for the string to which *pchCharVal* points.<br /><br /> *pchCharVal* (**CHAR** \*) Pointer to the string.<br /><br /> *rgbReserved* (**BYTE[5]**) Specifies the collation information.<br /><br /> Unused members:<br /><br /> *dwReserved*, and *pwchReserved*.|  

docs/database-engine/availability-groups/windows/availability-group-lease-healthcheck-timeout.md

@@ -71,7 +71,7 @@ The failure condition level of the AG changes the failure conditions for the hea
 | 2: OnServerUnresponsive | If no data is received from `sp_server_diagnostics` for the HealthCheckTimeout
 | 3: OnCriticalServerError | (Default) If the system component reports an error
 | 4: OnModerateServerError | If the resource component reports an error  
-| 5: OnAnyQualifiedFailureConitions | If the query processing component reports an error
+| 5: OnAnyQualifiedFailureConditions | If the query processing component reports an error
 
 ## Updating cluster and Always On timeout values
 

docs/database-engine/availability-groups/windows/some-availability-replicas-are-not-synchronizing-data.md

@@ -23,15 +23,15 @@ helpviewer_keywords:
 - **Facet**: Availability group  
 
 ## Description  
- This policy rolls up the data synchronization state of all availability replicas in the availability group and checks if the synchronization of any availability replica is not operational. The policy is in an unhealthy state if any of the data synchronization states of the availability replica is NOT SYNCRONIZING.  
+ This policy rolls up the data synchronization state of all availability replicas in the availability group and checks if the synchronization of any availability replica is not operational. The policy is in an unhealthy state if any of the data synchronization states of the availability replica is NOT SYNCHRONIZING.  
 
  This policy is in a healthy state if none of the data synchronization states of the availability replica is NOT SYNCHRONIZING.  
 
 ## Possible Causes  
  In this availability group, at least one secondary replica has a NOT SYNCHRONIZING synchronization state and is not receiving data from the primary replica.  
 
 ## Possible Solution  
- Use the availability replica policy state to find the availability replica with a NOT SYNCHROINIZING state, and then resolve the issue at the availability replica.  
+ Use the availability replica policy state to find the availability replica with a NOT SYNCHRONIZING state, and then resolve the issue at the availability replica.  
 
 ## See Also  
  [Overview of Always On Availability Groups (SQL Server)](../../../database-engine/availability-groups/windows/overview-of-always-on-availability-groups-sql-server.md)   

docs/database-engine/configure-windows/certificate-overview.md

@@ -54,7 +54,7 @@ To prove that a certificate holder is who they claim to be, the certificate must
 | Method | Description | Advantages | Disadvantages |
 | --- | --- | --- | --- |
 | Certificate subject match | The certificate's **Subject** field contains the common name (CN) of the host. For example, the certificate that's issued to `www.contoso.com` can be used for the web site `https://www.contoso.com`. | - Compatible with all clients, devices, and services.<br /><br />- Compartmentalization. Revoking the certificate for a host doesn't affect other hosts. | - Number of certificates required. You can only use the certificate for the specified host. For example, you can't use the `www.contoso.com` certificate for `ftp.contoso.com`, even when the services are installed on the same server.<br /><br />- Complexity. On a web server, each certificate requires its own IP address binding. |
-| Certificate subject alternative name (SAN) match | In addition to the **Subject** field, the certificate's **Subject Alternative Name** field contains a list of multiple host names. For example:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`ftp.eu.fabirkam.net` | - Convenience. You can use the same certificate for multiple hosts in multiple, separate domains.<br /><br />- Most clients, devices, and services support SAN certificates.<br /><br />- Auditing and security. You know exactly which hosts are capable of using the SAN certificate. | - More planning required. You need to provide the list of hosts when you create the certificate.<br /><br />- Lack of compartmentalization. You can't selectively revoke certificates for some of the specified hosts without affecting all of the hosts in the certificate. |
+| Certificate subject alternative name (SAN) match | In addition to the **Subject** field, the certificate's **Subject Alternative Name** field contains a list of multiple host names. For example:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`ftp.eu.fabrikam.net` | - Convenience. You can use the same certificate for multiple hosts in multiple, separate domains.<br /><br />- Most clients, devices, and services support SAN certificates.<br /><br />- Auditing and security. You know exactly which hosts are capable of using the SAN certificate. | - More planning required. You need to provide the list of hosts when you create the certificate.<br /><br />- Lack of compartmentalization. You can't selectively revoke certificates for some of the specified hosts without affecting all of the hosts in the certificate. |
 | Wildcard certificate match | The certificate's **Subject** field contains the common name as the wildcard character (*) plus a single domain or subdomain. For example, `*.contoso.com` or `*.eu.contoso.com`. The `*.contoso.com` wildcard certificate can be used for:<br />`www.contoso.com`<br />`ftp.contoso.com`<br />`mail.contoso.com` | Flexibility. You don't need to provide a list of hosts when you request the certificate, and you can use the certificate on any number of hosts that you may need in the future. | - You can't use wildcard certificates with other top-level domains (TLDs). For example, you can't use the `*.contoso.com` wildcard certificate for `*.contoso.net` hosts.<br /><br />- You can only use wildcard certificates for host names at the level of the wildcard. For example, you can't use the `*.contoso.com` certificate for `www.eu.contoso.com`. Or, you can't use the `*.eu.contoso.com` certificate for `www.uk.eu.contoso.com`.<br /><br />- Older clients, devices, applications, or services might not support wildcard certificates.<br /><br />- Wildcards aren't available with Extended Validation (EV) certificates.<br /><br />- Careful auditing and control are required. If the wildcard certificate is compromised, it affects every host in the specified domain. |
 
 ## Related content

docs/database-engine/database-mirroring/database-mirroring-operating-modes.md

@@ -217,7 +217,7 @@ helpviewer_keywords:
 
 -   When the witness is connected to a partner, the witness is in the CONNECTED state relative to that partner and has quorum with that partner. In this case, the database can be made available, even if one of the partners is unavailable.  
 
--   When the witness exists but is not connected to a partner, the witness is in the UNKOWN or DISCONNECTED state relative to that partner. In this case, the witness lacks quorum with that partner, and if the partners are not connected to each other, the database becomes unavailable.  
+-   When the witness exists but is not connected to a partner, the witness is in the UNKNOWN or DISCONNECTED state relative to that partner. In this case, the witness lacks quorum with that partner, and if the partners are not connected to each other, the database becomes unavailable.  
 
  For information about quorum, see [Quorum: How a Witness Affects Database Availability (Database Mirroring)](../../database-engine/database-mirroring/quorum-how-a-witness-affects-database-availability-database-mirroring.md).  
 

docs/database-engine/service-broker/conversation-priorities.md

@@ -256,7 +256,7 @@ This script specifies the priority level for the initiator conversation endpoint
     CREATE BROKER PRIORITY InitiatorToTargetPriority
         FOR CONVERSATION
         SET (CONTRACT_NAME = SimpleContract,
-             LOCAL_SERVICE_NAME = InitiatorSerivce,
+             LOCAL_SERVICE_NAME = InitiatorService,
              REMOTE_SERVICE_NAME = N'TargetService',
              PRIORITY_LEVEL = 3);
     GO

docs/integration-services/attunity-connectors.md

@@ -13,7 +13,7 @@ ms.topic: conceptual
 [!INCLUDE[sqlserver-ssis](../includes/applies-to-version/sqlserver-ssis.md)]
 
 > [!NOTE]
-> Atunity Connectors for Oracle and Teradata support SQL Server 2017 and below.
+> Attunity Connectors for Oracle and Teradata support SQL Server 2017 and below.
 >
 > From SQL Server 2019, get latest connectors for Oracle and Teradata here:
 > - [Microsoft connector for Oracle](data-flow/oracle-connector.md)

docs/integration-services/data-flow/cdc-source.md

@@ -161,7 +161,7 @@ use <cdc-enabled-database-name>
 -   **Net with merge**: This mode is similar to the regular Net mode but with Insert and Update operations merged into a single Merge operation (UPSERT).  
 
 > [!NOTE]  
->  For all Net change options, the source table must have a primary key or unique index. For tables without a primary key or unique indes, you must yse the **All** option.  
+>  For all Net change options, the source table must have a primary key or unique index. For tables without a primary key or unique indexes, you must use the **All** option.  
   
  **Variable containing the CDC state**  
  Select the SSIS string package variable that maintains the CDC state for the current CDC context. For more information about the CDC state variable, see [Define a State Variable](../../integration-services/data-flow/define-a-state-variable.md).  

docs/integration-services/data-flow/create-new-infoobject.md

@@ -37,7 +37,7 @@ ms.topic: ui-reference
         > [!NOTE]  
         >  Each row in the table represents a column in the data flow of the package.  
   
-    3.  To create an InfoObject while creating an InfoSouce for transactional data, select **InfoSource**, and then click **Create**. In the **Create InfoSource** dialog box, select **Transaction Data**, and then click **OK**. In the **Create InfoSource for Transaction Data** dialog box, in the **IObject** column for one of the rows in the list, select **Create** to open the **Create New InfoObject** dialog box.  
+    3.  To create an InfoObject while creating an InfoSource for transactional data, select **InfoSource**, and then click **Create**. In the **Create InfoSource** dialog box, select **Transaction Data**, and then click **OK**. In the **Create InfoSource for Transaction Data** dialog box, in the **IObject** column for one of the rows in the list, select **Create** to open the **Create New InfoObject** dialog box.  
 
         > [!NOTE]  
         >  Each row in the table represents a column in the data flow of the package.