fix incorrect slashes <> signs

plamenmitrev · plamenmitrev · commit 4216b8790e95 · 2025-04-09T16:27:00.000+03:00
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/settings-class.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/settings-class.md
@@ -171,7 +171,7 @@ This table lists all of the WebAii framework settings that are available for you
 	<td>"InternetExplorer"<br>
 	"FireFox"<br>
 	"AspNetHost"<br>
-	"Safari"h</td>
+	"Safari"</td>
 	<td>"InternetExplorer"</td>
 </tr>
 <tr>
@@ -267,7 +267,7 @@ This table lists all of the WebAii framework settings that are available for you
 **LogLocation**</td>
 	<td>Location where all logging will be performed, both captured bitmaps and WebAii's log file.</td>
 	<td>Any valid URI.</td>
-	<td>C:\WebAiiLog\</td>
+	<td>C:\WebAiiLog
 </tr>
 <tr>
 <td>
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/locating-elements.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/locating-elements.md
@@ -47,16 +47,16 @@ All of the common methods for finding an element to operate on are:
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByName()&gt;</code>/<code>Find.ByName&lt;T&gt;</code></td><td>Returns the first element having the specified name.</td>
+	<td><code>Find.ByName()</code>/<code>Find.ByName&lt;T&gt;()</code></td><td>Returns the first element having the specified name.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByText&gt;</code></td><td>Returns the first TextBlock that matches the text provided.</td>
+	<td><code>Find.ByText()</code></td><td>Returns the first TextBlock that matches the text provided.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByAutomationId&gt;</code></td><td>Returns an element having the automation ID you specify.</td>
+	<td><code>Find.ByAutomationId()</code></td><td>Returns an element having the automation ID you specify.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByType&gt;</code></td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
+	<td><code>Find.ByType()</code></td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
 </tr>
 </table>
 
@@ -103,16 +103,16 @@ All of the `Find.AllByxxx` functions are:
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByName()&gt;</code>/<code>Find.AllByName&lt;T&gt;</code></td><td>Find all elements that have a specific name. Allows filtering on a specific control type.</td>
+	<td><code>Find.AllByName()</code>/<code>Find.AllByName&lt;T&gt;</code></td><td>Find all elements that have a specific name. Allows filtering on a specific control type.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByText()&gt;</code></td><td>Find all TextBlocks that contain a specific text. Use p:text to search for partial text.</td>
+	<td><code>Find.AllByText()</code></td><td>Find all TextBlocks that contain a specific text. Use p:text to search for partial text.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByType()&gt;</code>/<code>Find.AllByType&lt;T&gt;</code></td><td>Find all elements of certain type. i.e Button, Grid..etc. Filtering on type is inherit here.</td>
+	<td><code>Find.AllByType()</code>/<code>Find.AllByType&lt;T&gt;</code></td><td>Find all elements of certain type. i.e Button, Grid..etc. Filtering on type is inherit here.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByAutomationID(&gt;</code>/<code>Find.AllByAutomationID&lt;T&gt;</code>)</td><td>Find all elements that have a specific automation ID. Allows filtering on a specific control type.</td>
+	<td><code>Find.AllByAutomationID()</code>/<code>Find.AllByAutomationID&lt;T&gt;()</code></td><td>Find all elements that have a specific automation ID. Allows filtering on a specific control type.</td>
 </tr>
 </table>
 
diff --git a/docs/automated-tests/elements/element-repository.md b/docs/automated-tests/elements/element-repository.md
@@ -34,6 +34,6 @@ Since this file is automatically generated, it should not be checked into your s
 
 ### How is the Element Repository used during test execution? 
 
-When you look at the elements being displayed in the Elements Explorer pane, you will see them in a tree structure. At the root is the web page from which they were recorded. Under that may be a Frame node if the element was contained on the source page that an \<iframe> element references, and/or a Silverlight node if it was recorded from a Silverlight application.
+When you look at the elements being displayed in the Elements Explorer pane, you will see them in a tree structure. At the root is the web page from which they were recorded. Under that may be a Frame node if the element was contained on the source page that an `<iframe>` element references, and/or a Silverlight node if it was recorded from a Silverlight application.
 
 During test execution, the root Page node is not actually used to locate the element. The execution engine only uses the Frame, Silverlight nodes, and the element's Find Expression to locate the correct element to interact with during any test step. This allows the test to continue to work when you need to test in a different testing environment (e.g. a Development server, then a Staging server, then a Production server).
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/asp-net-host-server.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/asp-net-host-server.md
@@ -18,7 +18,7 @@ Many of our customers have asked for a way to execute tests without the need for
 
 * If you are using NUnit 2.4 or higher you might experience AppDomainUnloadException similar to the issue described here. To work around this issue, please set the configuration setting legacyUnhandledExceptionPolicy to '0' in nunit.exe.config file.
  
-\<legacyUnhandledExceptionPolicy enabled="0" />
+`<legacyUnhandledExceptionPolicy enabled="0" />`
 
 With all these in mind, let's look at an example that illustrates how we can enable our tests to run against the Asp.Net inproc host. Here is a simply Asp.Net page that utilizes several Asp.Net controls:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class.md
@@ -157,7 +157,7 @@ This table lists all of the WebAii framework settings that are available for you
 	<td>"InternetExplorer"<br>
 	"FireFox"<br>
 	"AspNetHost"<br>
-	"Safari"h</td>
+	"Safari"</td>
 	<td>"InternetExplorer"</td>
 </tr>
 <tr>
@@ -231,7 +231,7 @@ This table lists all of the WebAii framework settings that are available for you
 	<td><strong>LogLocation</strong></td>
 	<td>Location where all logging will be performed, both captured bitmaps and WebAii's log file.</td>
 	<td>Any valid URI.</td>
-	<td>C:\WebAiiLog\</td>
+	<td>C:\WebAiiLog</td>
 </tr>
 <tr>
 	<td><strong>QueryEventLogErrorsOnExit</strong></td>
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions.md
@@ -171,16 +171,16 @@ The FrameworkElement class implements a number of methods just for purpose of te
 	<td><code>CastAs&lt;T&gt;()</code></td><td>Returns a FrameworkElement as a strongly-typed control. Does not enforce a tagname to match the type.</td>
 </tr>
 <tr>
-	<td><code>&lt;GetChildren()&gt;</code></td>Returns the child elements of the FrameworkElement.</td>
+	<td><code>GetChildren()</code></td>Returns the child elements of the FrameworkElement.</td>
 </tr>
 <tr>
-	<td><code>&lt;GetNextSibling()&gt;</code></td><td>Returns the next sibling of  the FrameworkElement.</td>
+	<td><code>GetNextSibling()</code></td><td>Returns the next sibling of  the FrameworkElement.</td>
 </tr>
 <tr>
-	<td><code>&lt;Parent()&gt;</code></td><td>Returns the parent element of the current Framework Element</td>
+	<td><code>Parent()</code></td><td>Returns the parent element of the current Framework Element</td>
 </tr>
 <tr>
-	<td><code>&lt;ScrollToVisible()&gt;</code></td><td>Scrolls the browser so that the Framework Element is visible.</td>
+	<td><code>ScrollToVisible()</code></td><td>Scrolls the browser so that the Framework Element is visible.</td>
 </tr>
 </table>
 
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/locating-elements.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/locating-elements.md
@@ -47,16 +47,16 @@ All of the common methods for finding an element to operate on are:
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByName()&gt;</code>/<code>Find.ByName&lt;T&gt;</code></td><td>Returns the first element having the specified name.</td>
+	<td><code>Find.ByName()</code>/<code>Find.ByName&lt;T&gt;</code></td><td>Returns the first element having the specified name.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByText&gt;</code></td><td>Returns the first TextBlock that matches the text provided.</td>
+	<td><code>Find.ByText</code></td><td>Returns the first TextBlock that matches the text provided.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByAutomationId&gt;</code></td><td>Returns an element having the automation ID you specify.</td>
+	<td><code>Find.ByAutomationId</code></td><td>Returns an element having the automation ID you specify.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.ByType&gt;</code></td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
+	<td><code>Find.ByType</code></td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
 </tr>
 </table>
 
@@ -103,16 +103,16 @@ All of the `Find.AllByxxx` functions are:
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByName()&gt;</code>/<code>Find.AllByName&lt;T&gt;</code></td><td>Find all elements that have a specific name. Allows filtering on a specific control type.</td>
+	<td><code>Find.AllByName()</code>/<code>Find.AllByName&lt;T&gt;()</code></td><td>Find all elements that have a specific name. Allows filtering on a specific control type.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByText()&gt;</code></td><td>Find all TextBlocks that contain a specific text. Use p:text to search for partial text.</td>
+	<td><code>Find.AllByText()</code></td><td>Find all TextBlocks that contain a specific text. Use p:text to search for partial text.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByType()&gt;</code>/<code>Find.AllByType&lt;T&gt;</code></td><td>Find all elements of certain type. i.e Button, Grid..etc. Filtering on type is inherit here.</td>
+	<td><code>Find.AllByType()</code>/<code>Find.AllByType&lt;T&gt;</code></td><td>Find all elements of certain type. i.e Button, Grid..etc. Filtering on type is inherit here.</td>
 </tr>
 <tr>
-	<td><code>&lt;Find.AllByAutomationID(&gt;</code>/<code>Find.AllByAutomationID&lt;T&gt;</code>)</td><td>Find all elements that have a specific automation ID. Allows filtering on a specific control type.</td>
+	<td><code>Find.AllByAutomationID()</code>/<code>Find.AllByAutomationID&lt;T&gt;()</code></td><td>Find all elements that have a specific automation ID. Allows filtering on a specific control type.</td>
 </tr>
 </table>
 
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation.md
@@ -87,7 +87,7 @@ Let's take a closer look at the code above line by line:
  
 	`app.FindName<TextBox>("myName").User.TypeText("Telerik", 50);`
 
-* Line 20 (`app.FindName\<Button>("myBtn").User.Click();`)
+* Line 20 (`app.FindName<Button>("myBtn").User.Click();`)
 
 	Same as above in terms of accessing the button. The difference here is that we are using the '**User**' object to click the button. The **User** object is present on all elements that inherit from **FrameworkElement** and offers real user interactions with Silverlight elements. So a click using the 'User' object will actually move the mouse over that button and click it. That is exactly what this line does.
 
