fix before PR

.script/tests/detectionTemplateSchemaValidation/DetectionTemplateSchemaValidation.Tests.sln

@@ -5,8 +5,6 @@ VisualStudioVersion = 16.0.30621.155
 MinimumVisualStudioVersion = 10.0.40219.1
 Project("{9A19103F-16F7-4668-BE54-9A1E7A4F7556}") = "DetectionTemplateSchemaValidation.Tests", "DetectionTemplateSchemaValidation.Tests.csproj", "{5B7A7358-FA15-45A7-B780-50180855845C}"
 EndProject
-Project("{2150E333-8FDC-42A3-9474-1A3956D46DE8}") = "Solution Items", "Solution Items", "{C485F47B-B0C7-47C0-821A-00F7FDD5896A}"
-EndProject
 Global
 	GlobalSection(SolutionConfigurationPlatforms) = preSolution
 		Debug|Any CPU = Debug|Any CPU

.script/tests/detectionTemplateSchemaValidation/DetectionTemplateSchemaValidationTests.cs

@@ -40,7 +40,7 @@ namespace Kqlvalidations.Tests
                 connectorIds.ForEach(connectorId => {
                     if (!TemplatesSchemaValidationsReader.ValidConnectorIds.Contains(connectorId))
                     {
-                        throw new FormatException($"Not valid connectorId: {connectorId}. If it's a new connector and already configured in the Portal, please add it's Id to the list in 'ValidConnectorIds.json file.'");
+                        throw new FormatException($"Not valid connectorId: {connectorId}. If a new connector is used and already configured in the Portal, please add it's Id to the list in 'ValidConnectorIds.json' file.");
                     }
                 });
             };

README.md

@@ -130,9 +130,7 @@ Total tests: 171
 
 ### Detection schema validation tests
 Similarly to KQL Validation, there is an automatic validation of the schema of a detection.
-It includes two validations:
-* The detection's frequency and period, the detection's trigger type and threshold, existance of required fields, etc.
-* Validity of connectors Ids.
+The schema vlidation includes the detection's frequency and period, the detection's trigger type and threshold, validity of connectors Ids, etc.
 A wrong format or missing attributes will result with an informative check failure, which should guide you through the resolution of the issue, but make sure to look into the format of already approved detection.
 
 ### Run Detection Schema Validation Locally