Fix typos

docs/test/code-generation-compilation-and-naming-conventions-in-microsoft-fakes.md

@@ -247,7 +247,7 @@ attribute of the Assembly element in the .fakes:
 > [!NOTE]
 > - **Getters and setters of indexers** are treated similarly to the property. The default name for an indexer is `Item`.
 > - **Parameter type** names are transformed and concatenated.
-> - **Return type** is ignored unless there's an overload ambiguity. If there's an overload amiguity, the return type is appended at the end of the name.
+> - **Return type** is ignored unless there's an overload ambiguity. If there's an overload ambiguity, the return type is appended at the end of the name.
 
 ### Parameter type naming conventions
 

docs/test/creating-a-data-driven-coded-ui-test.md

@@ -99,7 +99,7 @@ This sample creates a coded UI test that runs on the Windows Calculator applicat
 
 1. Add a text file to the dataDrivenSample project named *data.csv*.
 
-     ![Add a comma seperated value file to the project](../test/media/cuit_datadriven_addcsvfile.png)
+     ![Add a comma separated value file to the project](../test/media/cuit_datadriven_addcsvfile.png)
 
 2. Populate the *.csv* file with the following data:
 
@@ -115,7 +115,7 @@ This sample creates a coded UI test that runs on the Windows Calculator applicat
 
 3. It is important to save the *.csv* file using the correct encoding. On the **File** menu, choose **Advanced Save Options** and choose **Unicode (UTF-8 without signature) - Codepage 65001** as the encoding.
 
-4. The *.csv* file, must be copied to the output directory, or the test can't run. Use the **Properties** window to copy it.
+4. The *.csv* file must be copied to the output directory, or the test can't run. Use the **Properties** window to copy it.
 
      ![Deploy the .csv file](../test/media/cuit_datadriven_deploycsvfile.png)