Merge pull request #10682 from changeworld/patch-1

Fix typo

Author: ttorble

docs/test/customizing-code-coverage-analysis.md

@@ -108,7 +108,7 @@ The following table shows the various ways that assemblies and members can be ma
 ::: moniker range=">=vs-2022"
 ### Code coverage formats
 
-By default code coverage is collected and saved in a `.coverage` file. You can also collect coverage using other formats including Xml and Cobertura. Different formats may be useful across different editors and pipelines. You can enable this in runsettings by adding `<Format>Cobertura</Format>` or `<Format>Xml</Format>` in the [DataCollector configuration section in your runsettings file](../test/configure-unit-tests-by-using-a-dot-runsettings-file.md#codecoverage-data-collector). This format can be viewed in the code coverage results window in Visual Studio Enterprise.
+By default code coverage is collected and saved in a `.coverage` file. You can also collect coverage using other formats including XML and Cobertura. Different formats may be useful across different editors and pipelines. You can enable this in runsettings by adding `<Format>Cobertura</Format>` or `<Format>Xml</Format>` in the [DataCollector configuration section in your runsettings file](../test/configure-unit-tests-by-using-a-dot-runsettings-file.md#codecoverage-data-collector). This format can be viewed in the code coverage results window in Visual Studio Enterprise.
 
 You can also specify different formats from the command-line by either specifying it in the runsettings file or specifying it in a parameter. For example, the dotnet command-line use `dotnet test --collect:"Code Coverage;Format=Cobertura"`. For vstest use `vstest.console.exe /collect:"Code Coverage;Format=Cobertura"`. The collect parameter will override the format specified in runsettings.
 ::: moniker-end

docs/test/how-to-create-a-data-driven-unit-test.md

@@ -197,7 +197,7 @@ The DataSource attribute has three constructors.
 [DataSource(dataSourceSettingName)]
 ```
 
-A constructor with one parameter uses connection information that is stored in the *app.config* file for the solution. The *dataSourceSettingsName* is the name of the Xml element in the config file that specifies the connection information.
+A constructor with one parameter uses connection information that is stored in the *app.config* file for the solution. The *dataSourceSettingsName* is the name of the XML element in the config file that specifies the connection information.
 
 Using an *app.config* file allows you to change the location of the data source without making changes to the unit test itself. For information about how to create and use an *app.config* file, see [Walkthrough: Using a Configuration File to Define a Data Source](../test/walkthrough-using-a-configuration-file-to-define-a-data-source.md)