Merge pull request #173925 from alexbuckgit/windows-brand-20210928-2

GitHubber17 · web-flow · commit b83ea9328dd4 · 2021-09-28T20:13:29.000-07:00
Fix incorrect casing of Windows brand name (part 2)
diff --git a/articles/aks/csi-secrets-store-driver.md b/articles/aks/csi-secrets-store-driver.md
@@ -29,7 +29,7 @@ The minimum recommended Kubernetes version for this feature is 1.18.
 - Supports CSI Inline volumes (Kubernetes version v1.15+)
 - Supports mounting multiple secrets store objects as a single volume
 - Supports pod portability with the SecretProviderClass CRD
-- Supports windows containers
+- Supports Windows containers
 - Sync with Kubernetes Secrets (Secrets Store CSI Driver v0.0.10+)
 - Supports auto rotation of mounted contents and synced Kubernetes secrets (Secrets Store CSI Driver v0.0.15+)
 
diff --git a/articles/aks/planned-maintenance.md b/articles/aks/planned-maintenance.md
@@ -127,7 +127,7 @@ az aks maintenanceconfiguration update -g MyResourceGroup --cluster-name myAKSCl
 
 ## List all maintenance windows in an existing cluster
 
-To see all current maintenance configuration windows in your AKS Cluster, use the `az aks maintenanceconfiguration list` command.
+To see all current maintenance configuration windows in your AKS cluster, use the `az aks maintenanceconfiguration list` command.
 
 ```azurecli-interactive
 az aks maintenanceconfiguration list -g MyResourceGroup --cluster-name myAKSCluster
diff --git a/articles/aks/troubleshooting.md b/articles/aks/troubleshooting.md
@@ -142,7 +142,7 @@ Naming restrictions are implemented by both the Azure platform and AKS. If a res
 * Cluster names must be 1-63 characters. The only allowed characters are letters, numbers, dashes, and underscore. The first and last character must be a letter or a number.
 * The AKS Node/*MC_* resource group name combines resource group name and resource name. The autogenerated syntax of `MC_resourceGroupName_resourceName_AzureRegion` must be no greater than 80 chars. If needed, reduce the length of your resource group name or AKS cluster name. You may also [customize your node resource group name](cluster-configuration.md#custom-resource-group-name)
 * The *dnsPrefix* must start and end with alphanumeric values and must be between 1-54 characters. Valid characters include alphanumeric values and hyphens (-). The *dnsPrefix* can't include special characters such as a period (.).
-* AKS Node Pool names must be all lowercase and be 1-11 characters for linux node pools and 1-6 characters for windows node pools. The name must start with a letter and the only allowed characters are letters and numbers.
+* AKS Node Pool names must be all lowercase and be 1-11 characters for Linux node pools and 1-6 characters for Windows node pools. The name must start with a letter and the only allowed characters are letters and numbers.
 * The *admin-username*, which sets the administrator username for Linux nodes, must start with a letter, may only contain letters, numbers, hyphens, and underscores, and has a maximum length of 64 characters.
 
 ## I'm receiving errors when trying to create, update, scale, delete or upgrade cluster, that operation is not allowed as another operation is in progress.
diff --git a/articles/aks/windows-container-cli.md b/articles/aks/windows-container-cli.md
@@ -338,7 +338,7 @@ To see the sample app in action, open a web browser to the external IP address o
 ![Image of browsing to ASP.NET sample application](media/windows-container/asp-net-sample-app.png)
 
 > [!Note]
-> If you receive a connection timeout when trying to load the page then you should verify the sample app is ready with the following command [kubectl get pods --watch]. Sometimes the windows container will not be started by the time your external IP address is available.
+> If you receive a connection timeout when trying to load the page then you should verify the sample app is ready with the following command [kubectl get pods --watch]. Sometimes the Windows container will not be started by the time your external IP address is available.
 
 ## Delete cluster
 
diff --git a/articles/aks/windows-container-powershell.md b/articles/aks/windows-container-powershell.md
@@ -278,7 +278,7 @@ To see the sample app in action, open a web browser to the external IP address o
 
 > [!Note]
 > If you receive a connection timeout when trying to load the page then you should verify the sample
-> app is ready with the following command `kubectl get pods --watch`. Sometimes the windows
+> app is ready with the following command `kubectl get pods --watch`. Sometimes the Windows
 > container will not be started by the time your external IP address is available.
 
 ## Delete cluster
diff --git a/articles/app-service/environment/creation.md b/articles/app-service/environment/creation.md
@@ -46,7 +46,7 @@ There are three different deployment types;
 - zone redundant
 - host group
 
-The single zone ASE is available in all regions where ASEv3 is available. When you have a single zone ASE, you have a minimum App Service plan instance charge of one instance of windows Isolated v2. As soon as you have one or more instances, then that charge goes away. It is not an additive charge. 
+The single zone ASE is available in all regions where ASEv3 is available. When you have a single zone ASE, you have a minimum App Service plan instance charge of one instance of Windows Isolated v2. As soon as you have one or more instances, then that charge goes away. It is not an additive charge. 
 
 In a zone redundant ASE, your apps spread across three zones in the same region. The zone redundant ASE is available in a subset of ASE capable regions primarily limited by the regions that support availability zones. When you have zone redundant ASE, the smallest size for your App Service plan is three instances. That ensures that there is an instance in each availability zone. App Service plans can be scaled up one or more instances at a time. Scaling does not need to be in units of three, but the app is only balanced across all availability zones when the total instances are multiples of three. A zone redundant ASE has triple the infrastructure and is made with zone redundant components so that if even two of the three zones go down for whatever reason, your workloads remain available. Due to the increased system need, the minimum charge for a zone redundant ASE is nine instances. If you have less than nine total App Service plan instances in your ASEv3, the difference will be charged as Windows I1v2. If you have nine or more instances, there is no added charge to have a zone redundant ASE. To learn more about zone redundancy, read [Regions and Availability zones][AZoverview].
 
diff --git a/articles/azure-app-configuration/quickstart-python.md b/articles/azure-app-configuration/quickstart-python.md
@@ -18,7 +18,7 @@ In this quickstart, you will use Azure App Configuration to centralize storage a
 ## Prerequisites
 
 - Azure subscription - [create one for free](https://azure.microsoft.com/free/)
-- Python 2.7, or 3.6 or later - For information on setting up Python on Windows, see the [Python on Windows documentation]( https://docs.microsoft.com/windows/python/)
+- Python 2.7, or 3.6 or later - For information on setting up Python on Windows, see the [Python on Windows documentation](/windows/python/)
 
 ## Create an App Configuration store
 
diff --git a/articles/azure-australia/gateway-secure-remote-administration.md b/articles/azure-australia/gateway-secure-remote-administration.md
@@ -281,4 +281,4 @@ Conditional access is a component of Azure Active Directory that allows or denie
 
 ## Next steps
 
-Review the article on [Gateway Ingress Traffic Management and Control](gateway-ingress-traffic.md) for details on controlling traffic flows through your Gateway components in Azure.
+Review the article on [Gateway Ingress Traffic Management and Control](gateway-ingress-traffic.md) for details on controlling traffic flows through your Gateway components in Azure.
diff --git a/articles/azure-cache-for-redis/cache-best-practices-performance.md b/articles/azure-cache-for-redis/cache-best-practices-performance.md
@@ -28,7 +28,7 @@ ms.author: shpathak
 
 **Redis-benchmark** documentation can be [found here](https://redis.io/topics/benchmarks).
 
-The `redis-benchmark.exe` doesn't support TLS. You'll have to [enable the Non-TLS port through the Portal](cache-configure.md#access-ports) before you run the test. A windows compatible version of redis-benchmark.exe can be found [here](https://github.com/MSOpenTech/redis/releases).
+The `redis-benchmark.exe` doesn't support TLS. You'll have to [enable the Non-TLS port through the Portal](cache-configure.md#access-ports) before you run the test. A Windows-compatible version of redis-benchmark.exe can be found [here](https://github.com/MSOpenTech/redis/releases).
 
 ## Redis-benchmark examples
 
@@ -57,4 +57,4 @@ redis-benchmark -h yourcache.redis.cache.windows.net -a yourAccesskey -t  GET -n
 
 - [Development](cache-best-practices-development.md)
 - [Azure Cache for Redis development FAQs](cache-development-faq.yml)
-- [Failover and patching for Azure Cache for Redis](cache-failover.md)
+- [Failover and patching for Azure Cache for Redis](cache-failover.md)
diff --git a/articles/azure-functions/functions-reference-java.md b/articles/azure-functions/functions-reference-java.md
@@ -182,7 +182,7 @@ Maven also lets you specify the operating system on which your function app runs
 
 | Element |  Windows | Linux | Docker |
 | ---- | ---- | ---- | --- |
-| **`os`** | windows | linux | docker |
+| **`os`** | `windows` | `linux` | `docker` |
 
 The following example shows the operating system setting in the `runtime` section of the pom.xml file:
 
diff --git a/articles/azure-functions/functions-twitter-email.md b/articles/azure-functions/functions-twitter-email.md
@@ -214,7 +214,7 @@ Create a connection to Twitter so your app can poll for new tweets.
 
 1. Select **Sign in**.
 
-1. Follow the prompts in the popup window to complete signing in to Twitter.
+1. Follow the prompts in the pop-up window to complete signing in to Twitter.
 
 1. Next, enter the following values in the _When a new tweet is posted_ box.
 
@@ -305,7 +305,7 @@ The _Detect Sentiment_ box should look like the following screenshot.
 
 1. Select the **Sign in** button.
 
-1. Follow the prompts in the popup window to complete signing in to Office 365 Outlook.
+1. Follow the prompts in the pop-up window to complete signing in to Office 365 Outlook.
 
 1. Enter your email address in the _To_ box.
 
diff --git a/articles/azure-monitor/agents/diagnostics-extension-schema-windows.md b/articles/azure-monitor/agents/diagnostics-extension-schema-windows.md
@@ -218,7 +218,7 @@ The top-level element of the diagnostics configuration file.
 
 |Child Element|Description|  
 |-------------------|-----------------|  
-|**DataSource**|The Windows Event logs to collect. Required attribute:<br /><br /> **name** - The XPath query describing the windows events to be collected. For example:<br /><br /> `Application!*[System[(Level <=3)]], System!*[System[(Level <=3)]], System!*[System[Provider[@Name='Microsoft Antimalware']]], Security!*[System[(Level <= 3)]`<br /><br /> To collect all events, specify "*" |
+|**DataSource**|The Windows Event logs to collect. Required attribute:<br /><br /> **name** - The XPath query describing the Windows events to be collected. For example:<br /><br /> `Application!*[System[(Level <=3)]], System!*[System[(Level <=3)]], System!*[System[Provider[@Name='Microsoft Antimalware']]], Security!*[System[(Level <= 3)]`<br /><br /> To collect all events, specify "*" |
 |**sinks** | Added in 1.5. Optional. Points to a sink location to also send diagnostic data for all child elements that support sinks. Sink example is Application Insights or Event Hubs.|  
 
 
diff --git a/articles/azure-monitor/app/azure-web-apps-net-core.md b/articles/azure-monitor/app/azure-web-apps-net-core.md
@@ -15,7 +15,7 @@ Enabling monitoring on your ASP.NET Core based web applications running on [Azur
 # [Windows](#tab/Windows)
 
 > [!IMPORTANT]
-> The following versions of ASP.NET Core are supported for auto-instrumentation on windows: ASP.NET Core 3.1, and 5.0. Versions 2.0, 2.1, 2.2, and 3.0 have been retired and are no longer supported. Please upgrade to a [supported version](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core for auto-instrumentation to work.
+> The following versions of ASP.NET Core are supported for auto-instrumentation on Windows: ASP.NET Core 3.1, and 5.0. Versions 2.0, 2.1, 2.2, and 3.0 have been retired and are no longer supported. Please upgrade to a [supported version](https://dotnet.microsoft.com/platform/support/policy/dotnet-core) of .NET Core for auto-instrumentation to work.
 
 Targeting the full framework from ASP.NET Core is **not supported** in Windows. Use [manual instrumentation](./asp-net-core.md) via code instead.
 
diff --git a/articles/azure-monitor/app/configuration-with-applicationinsights-config.md b/articles/azure-monitor/app/configuration-with-applicationinsights-config.md
@@ -74,7 +74,7 @@ Reports the [response time and result code](../../azure-monitor/app/asp-net.md)
 * `Microsoft.ApplicationInsights.Web.ExceptionTrackingTelemetryModule`
 * [Microsoft.ApplicationInsights.Web](https://www.nuget.org/packages/Microsoft.ApplicationInsights.Web) NuGet package
 * `Microsoft.ApplicationInsights.WindowsServer.UnobservedExceptionTelemetryModule` - tracks unobserved task exceptions
-* `Microsoft.ApplicationInsights.WindowsServer.UnhandledExceptionTelemetryModule` - tracks unhandled exceptions for worker roles, windows services, and console applications.
+* `Microsoft.ApplicationInsights.WindowsServer.UnhandledExceptionTelemetryModule` - tracks unhandled exceptions for worker roles, Windows services, and console applications.
 * [Application Insights Windows Server](https://www.nuget.org/packages/Microsoft.ApplicationInsights.WindowsServer/) NuGet package.
 
 ### EventSource Tracking
@@ -301,4 +301,4 @@ TelemetryConfiguration.Active.ApplicationIdProvider = new DictionaryApplicationI
 [netlogs]: ./asp-net-trace-logs.md
 [new]: ./create-new-resource.md
 [redfield]: ./status-monitor-v2-overview.md
-[start]: ./app-insights-overview.md
+[start]: ./app-insights-overview.md
diff --git a/articles/azure-monitor/app/data-model-metric-telemetry.md b/articles/azure-monitor/app/data-model-metric-telemetry.md
@@ -55,7 +55,7 @@ Standard deviation of the aggregated metric. Should not be set for a measurement
 
 ## Custom properties
 
-Metric with the custom property `CustomPerfCounter` set to `true` indicate that the metric represents the windows performance counter. These metrics placed in performanceCounters table. Not in customMetrics. Also the name of this metric is parsed to extract category, counter, and instance names.
+Metric with the custom property `CustomPerfCounter` set to `true` indicate that the metric represents the Windows performance counter. These metrics placed in performanceCounters table. Not in customMetrics. Also the name of this metric is parsed to extract category, counter, and instance names.
 
 [!INCLUDE [application-insights-data-model-properties](../../../includes/application-insights-data-model-properties.md)]
 
@@ -64,4 +64,3 @@ Metric with the custom property `CustomPerfCounter` set to `true` indicate that
 - Learn how to use [Application Insights API for custom events and metrics](./api-custom-events-metrics.md#trackmetric).
 - See [data model](data-model.md) for Application Insights types and data model.
 - Check out [platforms](./platforms.md) supported by Application Insights.
-
diff --git a/articles/azure-monitor/app/data-retention-privacy.md b/articles/azure-monitor/app/data-retention-privacy.md
@@ -311,4 +311,3 @@ This product includes GeoLite2 data created by MaxMind, available from [https://
 [pricing]: https://azure.microsoft.com/pricing/details/application-insights/
 [redfield]: ./status-monitor-v2-overview.md
 [start]: ./app-insights-overview.md
-
diff --git a/articles/azure-monitor/app/javascript.md b/articles/azure-monitor/app/javascript.md
@@ -213,7 +213,7 @@ Most configuration fields are named such that they can be defaulted to false. Al
 | enable&#8203;AjaxErrorStatusText | If true, include response error data text in dependency event on failed AJAX requests. | boolean<br/> false |
 | enable&#8203;AjaxPerfTracking |Flag to enable looking up and including additional browser window.performance timings in the reported `ajax` (XHR and fetch) reported metrics. | boolean<br/> false |
 | maxAjaxPerf&#8203;LookupAttempts | The maximum number of times to look for the window.performance timings (if available), this is required as not all browsers populate the window.performance before reporting the end of the XHR request and for fetch requests this is added after its complete.| numeric<br/> 3 |
-| ajaxPerfLookupDelay | The amount of time to wait before re-attempting to find the windows.performance timings for an `ajax` request, time is in milliseconds and is passed directly to setTimeout(). | numeric<br/> 25 ms |
+| ajaxPerfLookupDelay | The amount of time to wait before re-attempting to find the window.performance timings for an `ajax` request, time is in milliseconds and is passed directly to setTimeout(). | numeric<br/> 25 ms |
 | enableUnhandled&#8203;PromiseRejection&#8203;Tracking | If true, unhandled promise rejections will be autocollected and reported as a JavaScript error. When disableExceptionTracking is true (don't track exceptions), the config value will be ignored and unhandled promise rejections will not be reported. | boolean<br/> false |
 | disable&#8203;InstrumentationKey&#8203;Validation | If true, instrumentation key validation check is bypassed. | boolean<br/>false |
 | enablePerfMgr | When enabled (true) this will create local perfEvents for code that has been instrumented to emit perfEvents (via the doPerf() helper). This can be used to identify performance issues within the SDK based on your usage or optionally within your own instrumented code. [More details are available by the basic documentation](https://github.com/microsoft/ApplicationInsights-JS/blob/master/docs/PerformanceMonitoring.md). Since v2.5.7 | boolean<br/>false |
diff --git a/articles/azure-monitor/essentials/metrics-supported.md b/articles/azure-monitor/essentials/metrics-supported.md
@@ -1920,7 +1920,7 @@ The Azure Monitor Agent replaces the Azure Diagnostics extension and Log Analyti
 |exceptions/server|No|Server exceptions|Count|Count|Count of uncaught exceptions thrown in the server application.|cloud/roleName, cloud/roleInstance|
 |pageViews/count|Yes|Page views|Count|Count|Count of page views.|operation/synthetic, cloud/roleName|
 |pageViews/duration|Yes|Page view load time|MilliSeconds|Average|Page view load time|operation/synthetic, cloud/roleName|
-|performanceCounters/exceptionsPerSecond|Yes|Exception rate|CountPerSecond|Average|Count of handled and unhandled exceptions reported to windows, including .NET exceptions and unmanaged exceptions that are converted into .NET exceptions.|cloud/roleInstance|
+|performanceCounters/exceptionsPerSecond|Yes|Exception rate|CountPerSecond|Average|Count of handled and unhandled exceptions reported to Windows, including .NET exceptions and unmanaged exceptions that are converted into .NET exceptions.|cloud/roleInstance|
 |performanceCounters/memoryAvailableBytes|Yes|Available memory|Bytes|Average|Physical memory immediately available for allocation to a process or for system use.|cloud/roleInstance|
 |performanceCounters/processCpuPercentage|Yes|Process CPU|Percent|Average|The percentage of elapsed time that all process threads used the processor to execute instructions. This can vary between 0 to 100. This metric indicates the performance of w3wp process alone.|cloud/roleInstance|
 |performanceCounters/processIOBytesPerSecond|Yes|Process IO rate|BytesPerSecond|Average|Total bytes per second read and written to files, network and devices.|cloud/roleInstance|
diff --git a/articles/azure-monitor/logs/logs-data-export.md b/articles/azure-monitor/logs/logs-data-export.md
@@ -699,7 +699,7 @@ Supported tables are currently limited to those specified below. All data from t
 | NWConnectionMonitorTestResult |  |
 | OfficeActivity | Partial support in government clouds – some of the data to ingested via webhooks from O365 into LA. This portion is missing in export currently. |
 | Operation | Partial support – some of the data is ingested through internal services that aren't supported for export. This portion is missing in export currently. |
-| Perf | Partial support – only windows perf data is currently supported. The Linux perf data is missing in export currently. |
+| Perf | Partial support – only Windows perf data is currently supported. The Linux perf data is missing in export currently. |
 | PowerBIDatasetsWorkspace |  |
 | PurviewScanStatusLogs |  |
 | SCCMAssessmentRecommendation |  |
diff --git a/articles/azure-monitor/visualize/workbooks-interactive.md b/articles/azure-monitor/visualize/workbooks-interactive.md
@@ -169,7 +169,7 @@ Query and metrics steps can also export one or more parameters when a row (or mu
 3. Check the `allow selection of multiple values` checkbox.
     1. The displayed visualization will allow multi-select and exported parameter's values will be arrays of values, like when using multi-select dropdown parameters.
     2. If unchecked the display visualization will only respect the last selected item. Only exporting a single value at a time.
-4. For each parameter you wish to export, use the *Add Parameter* button. A popup window will appear, containing the settings for the parameter to be exported.
+4. For each parameter you wish to export, use the *Add Parameter* button. A pop-up window will appear, containing the settings for the parameter to be exported.
 
 When single selection is enabled, the author can specify which field of the original data to export. Fields include parameter name, parameter type, and default value to use if nothing is selected (optional).
 
diff --git a/articles/azure-sql-edge/disconnected-deployment.md b/articles/azure-sql-edge/disconnected-deployment.md
diff --git a/articles/azure-sql/database/manage-data-after-migrating-to-database.md b/articles/azure-sql/database/manage-data-after-migrating-to-database.md
diff --git a/articles/azure-sql/database/security-best-practice.md b/articles/azure-sql/database/security-best-practice.md
diff --git a/articles/azure-sql/managed-instance/auditing-configure.md b/articles/azure-sql/managed-instance/auditing-configure.md
diff --git a/articles/azure-sql/virtual-machines/windows/availability-group-clusterless-workgroup-configure.md b/articles/azure-sql/virtual-machines/windows/availability-group-clusterless-workgroup-configure.md
diff --git a/articles/azure-sql/virtual-machines/windows/sql-server-iaas-agent-extension-automate-management.md b/articles/azure-sql/virtual-machines/windows/sql-server-iaas-agent-extension-automate-management.md
diff --git a/articles/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md b/articles/azure-sql/virtual-machines/windows/sql-server-on-azure-vm-iaas-what-is-overview.md
diff --git a/articles/azure-video-analyzer/video-analyzer-for-media-docs/customize-brands-model-overview.md b/articles/azure-video-analyzer/video-analyzer-for-media-docs/customize-brands-model-overview.md

Original file line number	Diff line number	Diff line change
`@@ -281,4 +281,4 @@ Conditional access is a component of Azure Active Directory that allows or denie`
`281`	`281`
`282`	`282`	`## Next steps`
`283`	`283`
`284`		`-Review the article on [Gateway Ingress Traffic Management and Control](gateway-ingress-traffic.md) for details on controlling traffic flows through your Gateway components in Azure.`
	`284`	`+Review the article on [Gateway Ingress Traffic Management and Control](gateway-ingress-traffic.md) for details on controlling traffic flows through your Gateway components in Azure.`