Fix up product metadata (and spelling) (#5922)

gewarren · web-flow · commit 1cb69e1c890d · 2023-06-27T10:53:57.000-07:00
diff --git a/README.md b/README.md
@@ -15,7 +15,7 @@ The content team tracks issues for .NET documentation in the [dotnet/docs](https
 The code in this repository represents programs that demonstrate application or library scenarios. These samples often use more than one technology, feature, or toolkit. Each sample has a readme.md file that explains the sample and links to resources for more information.
 
 Samples should be buildable projects. Those projects should build and
-run on the widest set of platforms possible for the given sample. In practice, that means building .NET Core-based console applications where possible. Samples that are specific to the web or a UI framework should add those tools as needed. Examples include web applications, mobile apps, WPF or WinForms apps, and so on.
+run on the widest set of platforms possible for the given sample. In practice, that means building .NET Core-based console applications where possible. Samples that are specific to the web or a UI framework should add those tools as needed. Examples include web applications, mobile apps, WPF or Windows Forms apps, and so on.
 
 We are working toward having a CI system in place for all code. When you make any updates to samples, make sure each update is part of a buildable
 project. Ideally, add tests for correctness on samples as well.
diff --git a/azure/app-configuration-dynamic-reload/README.md b/azure/app-configuration-dynamic-reload/README.md
@@ -2,7 +2,7 @@
 languages:
 - csharp
 products:
-- dotnet-core
+- aspnet-core
 - azure
 page_type: sample
 name: "Azure App Configuration dynamic settings sample"
diff --git a/azure/app-insights-aspnet-core-quickstart/README.md b/azure/app-insights-aspnet-core-quickstart/README.md
@@ -2,7 +2,7 @@
 languages:
 - csharp
 products:
-- dotnet-core
+- aspnet-core
 - azure
 page_type: sample
 name: "Azure Monitor Application Insights Quickstart for ASP.NET Core"
diff --git a/azure/sdk-identity-resources-storage/README.md b/azure/sdk-identity-resources-storage/README.md
@@ -3,7 +3,7 @@ languages:
 - csharp
 products:
 - dotnet-core
-- azure
+- azure-sdks
 page_type: sample
 name: "Azure Identity, Resource Management, and Storage sample"
 urlFragment: "azure-identity-resource-management-storage"
diff --git a/core/extensions/COMServerDemo/README.md b/core/extensions/COMServerDemo/README.md
@@ -3,7 +3,6 @@ languages:
 - csharp
 products:
 - dotnet-core
-- windows
 page_type: sample
 name: "COM Server Demo"
 urlFragment: "com-server-demo"
diff --git a/core/extensions/ExcelDemo/ReadMe.md b/core/extensions/ExcelDemo/ReadMe.md
@@ -3,7 +3,6 @@ languages:
 - csharp
 products:
 - dotnet-core
-- windows
 page_type: sample
 name: "Excel Demo"
 urlFragment: "excel-demo"
diff --git a/core/extensions/NetComSxS/README.md b/core/extensions/NetComSxS/README.md
@@ -4,7 +4,6 @@ languages:
 products:
 - dotnet-core
 - dotnet-framework
-- windows
 page_type: sample
 name: ".NET Framework and .NET Core COM interoperability"
 urlFragment: "net-framework-net-core-com-interop"
diff --git a/core/extensions/VisioDemo/README.md b/core/extensions/VisioDemo/README.md
@@ -3,7 +3,6 @@ languages:
 - csharp
 products:
 - dotnet-core
-- windows
 page_type: sample
 name: "Visio Demo"
 urlFragment: "visio-demo"
diff --git a/core/interop/comwrappers/IDispatch/README.md b/core/interop/comwrappers/IDispatch/README.md
@@ -6,7 +6,7 @@ The [`ComWrappers`](https://docs.microsoft.com/dotnet/api/system.runtime.interop
 Key Features
 ------------
 
-Demonstrates how to implement and utilize the `ComWrappers` API by manually implementing a subset of [`IDispatch`](https://docs.microsoft.com/windows/win32/api/oaidl/nn-oaidl-idispatch) for .NET objects. The consumer of the `IDispatch` instance is the [WinForms `WebBrowser`](https://docs.microsoft.com/dotnet/framework/winforms/controls/webbrowser-control-windows-forms) API for [exposing an object to the JavaScript engine](https://docs.microsoft.com/dotnet/api/system.windows.forms.webbrowser.objectforscripting).
+Demonstrates how to implement and utilize the `ComWrappers` API by manually implementing a subset of [`IDispatch`](https://docs.microsoft.com/windows/win32/api/oaidl/nn-oaidl-idispatch) for .NET objects. The consumer of the `IDispatch` instance is the [Windows Forms `WebBrowser`](https://docs.microsoft.com/dotnet/framework/winforms/controls/webbrowser-control-windows-forms) API for [exposing an object to the JavaScript engine](https://docs.microsoft.com/dotnet/api/system.windows.forms.webbrowser.objectforscripting).
 
 This is already fully supported by the built-in COM interop system, but this demonstrates a way for users to provide their own implementation.
 
diff --git a/core/interop/pinvoke/marshaling/README.md b/core/interop/pinvoke/marshaling/README.md
@@ -5,12 +5,12 @@ languages:
 products:
 - dotnet-core
 page_type: sample
-name: "P/Invoke Marshaling Sample"
+name: "P/Invoke Marshalling Sample"
 urlFragment: "pinvoke-marshal-arguments"
 description: "A .NET application that demonstrates different ways to marshal arguments to native functions when using P/Invokes."
 ---
 
-# .NET Core P/Invoke Marshaling Sample
+# .NET Core P/Invoke Marshalling Sample
 
 This project demonstrates different ways to marshal arguments to native functions when using P/Invokes. Documentation can be found here for [P/Invokes](https://docs.microsoft.com/dotnet/standard/native-interop/pinvoke) and here for the [Type marshaling](https://docs.microsoft.com/dotnet/standard/native-interop/type-marshaling).
 
diff --git a/core/linker/README.md b/core/linker/README.md
@@ -6,7 +6,7 @@ These samples demonstrate how to use the new ILLink functionality in the .NET Co
 
 The `HelloWorldTrimmed` sample demonstrates the default behavior of the .NET Core 3.0 SDK with IL Link trimming enabled. For most applications, the HelloWorldTrimmed should work as expected.
 
-The default settings for trimming automatically "root" all application assemblies. "Rooting" an assembly means that none of the IL in that assembly or any IL code that the assembly uses directly will be trimmed. Framework assemblies are not rooted, however, so it is possible to have issues in a trimmed application when using reflection to call types built into the .NET Core framework. Any assembly in the Microsoft.NETCore.App framework is considered a "framework" assembly, but WinForms, WPF, and ASP.NET frameworks are considered application assemblies for the purposes of linking.
+The default settings for trimming automatically "root" all application assemblies. "Rooting" an assembly means that none of the IL in that assembly or any IL code that the assembly uses directly will be trimmed. Framework assemblies are not rooted, however, so it is possible to have issues in a trimmed application when using reflection to call types built into the .NET Core framework. Any assembly in the Microsoft.NETCore.App framework is considered a "framework" assembly, but Windows Forms, WPF, and ASP.NET frameworks are considered application assemblies for the purposes of linking.
 
 ## TrimmedWithAdditionalRoots Sample
 
diff --git a/core/mono-samples/wasm/README.md b/core/mono-samples/wasm/README.md
@@ -11,7 +11,7 @@ urlFragment: "mono-wasm-csharp"
 
 # Wasm Sample: Simple greeting and counter (C#)
 
-In this sample, the mono runtime is used to invoke javascript unmanaged code (index.html) from the C# managed side (WasmSampleApp.cs) and vice versa. With the sample running, you can enter your name and click the corresponding button to modify the greeting message as well as click another button to increment a counter.
+In this sample, the mono runtime is used to invoke JavaScript unmanaged code (index.html) from the C# managed side (WasmSampleApp.cs) and vice versa. With the sample running, you can enter your name and click the corresponding button to modify the greeting message as well as click another button to increment a counter.
 
 > [!NOTE]
 > The purpose of this sample is to demonstrate the concept of building a WebAssembly application on top of the mono runtime. The mono runtime headers should be supplied through the build process.
@@ -24,7 +24,7 @@ This sample will only run on macOS.
 - .NET sdk 6.0.100-alpha.1.20628.2.
 - dotnet-serve (<https://github.com/natemcmain/dotnet-serve>)
 
-To install a specific version of the dotnet sdk, download the latest stable version of the dotnet-install script:
+To install a specific version of the .NET SDK, download the latest stable version of the dotnet-install script:
 
 - Bash: <https://dot.net/v1/dotnet-install.sh>
 
diff --git a/core/tutorials/buggyamb/README.md b/core/tutorials/buggyamb/README.md
@@ -13,7 +13,7 @@ description: "A set of samples to teach production ASP.NET Core debugging for Wi
 
 For a quick tour of the application please click here: [Quick Tour](Docs/quick_tour.md).
 
-BuggyAmb is just a very buggy ASP.NET Core Razor Pages based application. This application was intentionally created as a buggy application so it can be used as a learning resource to practice troubleshooting some sample problem scenarios:
+BuggyAmb is a buggy ASP.NET Core Razor Pages-based application. This application was intentionally created as a buggy application so it can be used as a learning resource to practice troubleshooting some sample problem scenarios:
 
 * High CPU or low CPU performance problems, deadlocks.
 * High memory issues.
@@ -34,7 +34,7 @@ As a support engineer, I can confidently say that if you know how to collect the
 
 ## Best practices
 
-A successfull troubleshooting session has the following characteristics:
+A successful troubleshooting session has the following characteristics:
 
 ### Identifying the issue
 
@@ -50,15 +50,15 @@ For example, "it was running fast and now it is slow." is a bad definition becau
 
 Once you identify the issue you need to collect the data. Most of the data collection may require to be done when the problem happens.
 
-If you can reproduce a problem then you are lucky and you can collect data at any time you want but if you cannot reproduce the problem easily and if you miss the data collection then you may need to wait for the next occurence which may be a problem.
+If you can reproduce a problem then you are lucky and you can collect data at any time you want but if you cannot reproduce the problem easily and if you miss the data collection then you may need to wait for the next occurrence which may be a problem.
 
 So you need to know what kind of tools you have, how to use those tools in which scenario, etc...
 
 ### Data analysis
 
-Just like collecting data, there are great tools that you can use to analyse data and you need to know what kind of tools there are to analyze data.
+Just like collecting data, there are great tools that you can use to analyze data and you need to know what kind of tools there are to analyze data.
 
-Note that some data analysis can be done while capturing the data on the server, for example you may want to look at a network trace while you capture it on the server but some data needs to be analyzed seperately on another machine.
+Note that some data analysis can be done while capturing the data on the server, for example you may want to look at a network trace while you capture it on the server but some data needs to be analyzed separately on another machine.
 
 So you need to prepare your machine so you can use those tools when needed.
 
diff --git a/csharp/api/datetime.parse/README.md b/csharp/api/datetime.parse/README.md
@@ -2,7 +2,6 @@
 languages:
   - csharp
 products:
-  - dotnet
   - dotnet-core
 page_type: sample
 name: DateTime.Parse examples
diff --git a/csharp/api/string.format/README.md b/csharp/api/string.format/README.md
@@ -2,7 +2,6 @@
 languages:
   - csharp
 products:
-  - dotnet
   - dotnet-core
 page_type: sample
 name: String.Format examples
diff --git a/csharp/getting-started/console-webapiclient/README.md b/csharp/getting-started/console-webapiclient/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: "HttpClient sample"
diff --git a/csharp/parallel/ComputePi/README.md b/csharp/parallel/ComputePi/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: ".NET Core parallel computation of PI"
diff --git a/csharp/parallel/EditDistance/README.md b/csharp/parallel/EditDistance/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: ".NET Core parallel wavefront algorithm sample"
diff --git a/csharp/parallel/PLINQ/README.md b/csharp/parallel/PLINQ/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: ".NET Core parallel programming with PLINQ"
diff --git a/csharp/parallel/ParallelGrep/README.md b/csharp/parallel/ParallelGrep/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: ".NET Core parallel grep sample"
diff --git a/csharp/parallel/Raytracer.Wpf/README.md b/csharp/parallel/Raytracer.Wpf/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 - windows-wpf
 page_type: sample
diff --git a/csharp/parallel/Raytracer/README.md b/csharp/parallel/Raytracer/README.md
@@ -2,18 +2,17 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 - windows-forms
 page_type: sample
 name: ".NET Core parallel animated ray-traced bouncing ball"
 urlFragment: "parallel-programming-winforms-raytracer-cs"
-description: "A .NET Core WinForms application that demonstrates an animated, ray-traced bouncing ball with parallel programming."
+description: "A .NET Core Windows Forms application that demonstrates an animated, ray-traced bouncing ball with parallel programming."
 ---
 
 # .NET Core parallel animated ray-traced bouncing ball
 
-The sample source code is a .NET Core WinForms application written in C#, that provides an animated, ray-traced bouncing ball. Sequential and parallel implementations are provided, as is a special parallel implementation that colors the animated image based on which thread was used to calculate which regions. For more information, see [Updates on .NET Core Windows Forms designer](https://devblogs.microsoft.com/dotnet/updates-on-net-core-windows-forms-designer/).
+The sample source code is a .NET Core Windows Forms application written in C#, that provides an animated, ray-traced bouncing ball. Sequential and parallel implementations are provided, as is a special parallel implementation that colors the animated image based on which thread was used to calculate which regions. For more information, see [Updates on .NET Core Windows Forms designer](https://devblogs.microsoft.com/dotnet/updates-on-net-core-windows-forms-designer/).
 
 ## Demo
 
diff --git a/csharp/unit-testing-code-coverage/README.md b/csharp/unit-testing-code-coverage/README.md
@@ -2,12 +2,11 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: ".NET Core unit testing code coverage"
 urlFragment: "unit-testing-code-coverage-cs"
-description: ".NET Core unit testing code coverage and reporting with coverlet, and ReportGenerator."
+description: ".NET Core unit testing code coverage and reporting with coverlet and ReportGenerator."
 ---
 
 # .NET Core unit testing code coverage
diff --git a/csharp/unit-testing/README.md b/csharp/unit-testing/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 page_type: sample
 name: "Order .NET Core unit tests"
diff --git a/iot/cheesecave.net/README.md b/iot/cheesecave.net/README.md
@@ -3,7 +3,7 @@ languages:
 - csharp
 products:
 - dotnet-core
-- azure
+- azure-iot-hub
 page_type: sample
 name: "End-to-end .NET IoT and Azure IoT Hub example"
 urlFragment: "dotnet-iot-end-to-end"
diff --git a/iot/dotnet-iot-and-nanoframework/README.md b/iot/dotnet-iot-and-nanoframework/README.md
@@ -2,9 +2,7 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
-- azure
 - azure-iot-hub
 page_type: sample
 name: "Compare .NET nanoFramework with .NET IoT"
diff --git a/mef/simple-calculator/vb/readme.md b/mef/simple-calculator/vb/readme.md
@@ -3,7 +3,6 @@ languages:
 - vb
 products:
 - dotnet-core
-- windows
 page_type: sample
 name: "MEF Sample: Simple Calculator (Visual Basic)"
 urlFragment: "simple-calculator-vb"
@@ -28,7 +27,7 @@ To download and run the sample, follow these steps:
 
     2. Navigate to the folder that holds the unzipped sample code, and open the solution (*.sln*) file.
 
-    3. Choose the F5 key, or Ctrl+F5 keys, to run the project.
+    3. Press <kbd>F5</kbd> or <kbd>Ctrl</kbd>+<kbd>F5</kbd> to run the project.
 
 3. From the command line:
 
diff --git a/windowsforms/Conway's-Game-of-Life/VB/readme.md b/windowsforms/Conway's-Game-of-Life/VB/readme.md
@@ -3,7 +3,7 @@ languages:
 - vb
 products:
 - dotnet-core
-- windows
+- windows-forms
 page_type: sample
 name: ".NET Core Windows Forms Conway's Game Of Life (Visual Basic)"
 urlFragment: "Conway's-Game-of-Life-vb"
@@ -13,7 +13,7 @@ description: "The Game of Life, also known simply as Life, is a cellular automat
 
 ## Requires
 
-- Visual Studio 2019 Version 16.5.0 Preview 2.0 or later to edit the GUI in the solution designer and you need to enable the designer in the Visual Studio Preview. Go to **Tools** > **Options** > **Environment** > **Preview Features** and select the **Use the preview Windows Forms designer for .NET Core apps** option.
+- Visual Studio 2019 or later to edit the GUI in the solution designer
 - .NET Core 3.1
 
 ## License
@@ -23,7 +23,7 @@ description: "The Game of Life, also known simply as Life, is a cellular automat
 ## Technologies
 
 - Windows Forms
-- dotnet-core
+- .NET Core
 
 ## Topics
 
@@ -36,7 +36,7 @@ description: "The Game of Life, also known simply as Life, is a cellular automat
 
 ## Description
 
-This Windows Forms sample was ported to .NET Core from a [previous .NET Framework 4.5 sample](https://github.com/microsoftarchive/msdn-code-gallery-community-a-c/tree/master/Conway's%20Game%20of%20Life/%5BVB%5D-Conway's%20Game%20of%20Life/VB).  This illustrates how to use Visual Basic in WinForms in .NET Core 3.1. Visual Basic support for WinForms is not fully supported in .NET Core 3.1, but the features used in this sample work fine.
+This Windows Forms sample was ported to .NET Core from a [previous .NET Framework 4.5 sample](https://github.com/microsoftarchive/msdn-code-gallery-community-a-c/tree/master/Conway's%20Game%20of%20Life/%5BVB%5D-Conway's%20Game%20of%20Life/VB).  This illustrates how to use Visual Basic in Windows Forms in .NET Core 3.1. Visual Basic support for Windows Forms is not fully supported in .NET Core 3.1, but the features used in this sample work fine.
 
 The Game of Life, also known simply as Life, is a cellular automaton devised by the British mathematician John Horton Conway in 1970.
 
@@ -49,6 +49,6 @@ The universe of the Game of Life is an infinite two-dimensional orthogonal grid
 3. Any live cell with more than three live neighbors dies, as if by overpopulation.
 4. Any dead cell with exactly three live neighbors becomes a live cell, as if by reproduction.
 
-The initial pattern constitutes the seed of the system. The first generation is created by applying the above rules simultaneously to every cell in the seed�births and deaths occur simultaneously, and the discrete moment at which this happens is sometimes called a tick (in other words, each generation is a pure function of the preceding one). The rules continue to be applied repeatedly to create further generations.
+The initial pattern constitutes the seed of the system. The first generation is created by applying the previous rules simultaneously to every cell in the seed. Births and deaths occur simultaneously, and the discrete moment at which this happens is sometimes called a tick (in other words, each generation is a pure function of the preceding one). The rules continue to be applied repeatedly to create further generations.
 
 ![Conway's Game of Life Image](Conway's-Game-of-Life-VB.jpg)
diff --git a/windowsforms/FlexGridShowcaseDemo/cs/README.md b/windowsforms/FlexGridShowcaseDemo/cs/README.md
@@ -2,7 +2,6 @@
 languages:
 - csharp
 products:
-- dotnet
 - dotnet-core
 - windows-forms
 page_type: sample
@@ -13,7 +12,7 @@ description: ".NET 6.0 Windows Forms application that demonstrates how to use Gr
 
 # FlexGrid Showcase Demo
 
-This sample is a .NET 6.0 Windows Forms application that demonstrates how to use GrapeCity [`FlexGrid`](https://www.grapecity.com/componentone/winforms-ui-controls/flexgrid-winforms-data-grid), a WinForms Datagrid control.
+This sample is a .NET 6.0 Windows Forms application that demonstrates how to use GrapeCity [`FlexGrid`](https://www.grapecity.com/componentone/winforms-ui-controls/flexgrid-winforms-data-grid), a Windows Forms Datagrid control.
 
 The sample shows different operations with `FlexGrid`:
 
diff --git a/windowsforms/MSIX-WindowsForms/README.md b/windowsforms/MSIX-WindowsForms/README.md
@@ -1,6 +1,6 @@
 # MSIX Windows Forms Core Application
 
-This sample shows how to use the Windows Packaging Project to package a WinForms application running on .NET Core 3.1.
+This sample shows how to use the Windows Packaging Project to package a Windows Forms application running on .NET Core 3.1.
 
 ## Pre-requisites
 
diff --git a/windowsforms/README.md b/windowsforms/README.md
diff --git a/windowsforms/Sudoku/VB/readme.md b/windowsforms/Sudoku/VB/readme.md
diff --git a/windowsforms/datagridview/README.md b/windowsforms/datagridview/README.md
diff --git a/windowsforms/formatting-utility/cs/readme.md b/windowsforms/formatting-utility/cs/readme.md
diff --git a/windowsforms/formatting-utility/vb/readme.md b/windowsforms/formatting-utility/vb/readme.md
diff --git a/windowsforms/matching-game/net5-windows/cs/readme.md b/windowsforms/matching-game/net5-windows/cs/readme.md
diff --git a/windowsforms/matching-game/net5-windows/vb/readme.md b/windowsforms/matching-game/net5-windows/vb/readme.md
diff --git a/wpf/README.md b/wpf/README.md
