[AutoPR sql/resource-manager] typo: Winodws -> Windows

lib/services/sqlManagement2/lib/models/index.d.ts

@@ -1575,7 +1575,7 @@ export interface ManagedInstance extends TrackedResource {
   proxyOverride?: string;
   /**
    * Id of the timezone. Allowed values are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry under
+   * Windows keeps details on supported timezones, including the id, in registry under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS timezone_id FROM
    * sys.time_zone_info.
@@ -1651,7 +1651,7 @@ export interface ManagedInstanceUpdate {
   proxyOverride?: string;
   /**
    * Id of the timezone. Allowed values are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry under
+   * Windows keeps details on supported timezones, including the id, in registry under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS timezone_id FROM
    * sys.time_zone_info.

lib/services/sqlManagement2/lib/models/managedInstance.js

@@ -66,7 +66,7 @@ class ManagedInstance extends models['TrackedResource'] {
    * the instance. Possible values include: 'Proxy', 'Redirect', 'Default'
    * @property {string} [timezoneId] Id of the timezone. Allowed values are
    * timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in
+   * Windows keeps details on supported timezones, including the id, in
    * registry under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name

lib/services/sqlManagement2/lib/models/managedInstanceUpdate.js

@@ -54,7 +54,7 @@ class ManagedInstanceUpdate {
    * the instance. Possible values include: 'Proxy', 'Redirect', 'Default'
    * @property {string} [timezoneId] Id of the timezone. Allowed values are
    * timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in
+   * Windows keeps details on supported timezones, including the id, in
    * registry under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name

lib/services/sqlManagement2/lib/operations/index.d.ts

@@ -10844,7 +10844,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -10942,7 +10942,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11113,7 +11113,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11201,7 +11201,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11316,7 +11316,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11414,7 +11414,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11585,7 +11585,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS
@@ -11673,7 +11673,7 @@ export interface ManagedInstances {
      *
      * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
      * are timezones supported by Windows.
-     * Winodws keeps details on supported timezones, including the id, in registry
+     * Windows keeps details on supported timezones, including the id, in registry
      * under
      * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
      * You can get those registry values via SQL Server by querying SELECT name AS

lib/services/sqlManagement2/lib/operations/managedInstances.js

@@ -503,7 +503,7 @@ function _get(resourceGroupName, managedInstanceName, options, callback) {
  *
  * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
  * are timezones supported by Windows.
- * Winodws keeps details on supported timezones, including the id, in registry
+ * Windows keeps details on supported timezones, including the id, in registry
  * under
  * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
  * You can get those registry values via SQL Server by querying SELECT name AS
@@ -716,7 +716,7 @@ function _deleteMethod(resourceGroupName, managedInstanceName, options, callback
  *
  * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
  * are timezones supported by Windows.
- * Winodws keeps details on supported timezones, including the id, in registry
+ * Windows keeps details on supported timezones, including the id, in registry
  * under
  * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
  * You can get those registry values via SQL Server by querying SELECT name AS
@@ -869,7 +869,7 @@ function _update(resourceGroupName, managedInstanceName, parameters, options, ca
  *
  * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
  * are timezones supported by Windows.
- * Winodws keeps details on supported timezones, including the id, in registry
+ * Windows keeps details on supported timezones, including the id, in registry
  * under
  * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
  * You can get those registry values via SQL Server by querying SELECT name AS
@@ -1243,7 +1243,7 @@ function _beginDeleteMethod(resourceGroupName, managedInstanceName, options, cal
  *
  * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
  * are timezones supported by Windows.
- * Winodws keeps details on supported timezones, including the id, in registry
+ * Windows keeps details on supported timezones, including the id, in registry
  * under
  * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
  * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2012,7 +2012,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2122,7 +2122,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2335,7 +2335,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2435,7 +2435,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2565,7 +2565,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2675,7 +2675,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2888,7 +2888,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS
@@ -2988,7 +2988,7 @@ class ManagedInstances {
    *
    * @param {string} [parameters.timezoneId] Id of the timezone. Allowed values
    * are timezones supported by Windows.
-   * Winodws keeps details on supported timezones, including the id, in registry
+   * Windows keeps details on supported timezones, including the id, in registry
    * under
    * KEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Time Zones.
    * You can get those registry values via SQL Server by querying SELECT name AS