diff --git a/.DS_Store b/.DS_Store
new file mode 100644
index 00000000..668cf676
Binary files /dev/null and b/.DS_Store differ
diff --git a/.gitignore b/.gitignore
index 600d2d33..36ed679a 100644
--- a/.gitignore
+++ b/.gitignore
@@ -1 +1,2 @@
-.vscode
\ No newline at end of file
+.vscode.DS_Store
+.DS_Store
diff --git a/docs-apitesting/.gitattributes b/docs-apitesting/.gitattributes
old mode 100644
new mode 100755
diff --git a/docs-apitesting/.gitignore b/docs-apitesting/.gitignore
old mode 100644
new mode 100755
diff --git a/docs-apitesting/40x.html b/docs-apitesting/40x.html
old mode 100644
new mode 100755
diff --git a/docs-apitesting/README.md b/docs-apitesting/README.md
old mode 100644
new mode 100755
diff --git a/docs-apitesting/_config.yml b/docs-apitesting/_config.yml
old mode 100644
new mode 100755
diff --git a/docs-apitesting/_pdf.yml b/docs-apitesting/_pdf.yml
old mode 100644
new mode 100755
diff --git a/docs-apitesting/advanced-topics/ci-server-integration.md b/docs-apitesting/advanced-topics/ci-server-integration.md
old mode 100644
new mode 100755
index 333e126f..6822f9a0
--- a/docs-apitesting/advanced-topics/ci-server-integration.md
+++ b/docs-apitesting/advanced-topics/ci-server-integration.md
@@ -4,7 +4,7 @@ page_title: CI Server Integration
 description: "Progress® Test Studio® for APIs - CI Server Integration"
 previous_url: /api-testing/advanced-topics
 position: 1
-publish: true
+published: true
 ---
 
 # CI Server Integration
@@ -14,15 +14,14 @@ Continuous Integration regularly integrates the individual developer's changes i
 Thanks to its command line interface, Test Studio for APIs can easily be integrated in most famous CI Servers.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Jenkins Integration
  
  * Install Progress® Test Studio® for APIs on your Jenkins slave or master machine (where you will execute your Jenkins project)
    * You can alternatively just copy the Telerik.ApiTesting.Runner.exe with the whole "runnerconsole" directory as described [here](/features/command-line/overview). 
- * Configure the test execution command (see [Command Line Parameters](/features/command-line/command-line-parameters)
- ) - we recommend saving it to a build.cmd file. This is an example:
+ * Configure the test execution command (see [Command Line Parameters](/features/command-line/command-line-parameters) ) - we recommend saving it to a build.cmd file. This is an example:
  
  `Telerik.ApiTesting.Runner.exe test -p "demotests" -f junit -v base-url=http://localhost:5000 -o testresult.xml`
  
diff --git a/docs-apitesting/advanced-topics/configure-custom-proxy.md b/docs-apitesting/advanced-topics/configure-custom-proxy.md
old mode 100644
new mode 100755
index a3860c73..e5b2dbb7
--- a/docs-apitesting/advanced-topics/configure-custom-proxy.md
+++ b/docs-apitesting/advanced-topics/configure-custom-proxy.md
@@ -3,7 +3,7 @@ title: Configure Custom Proxy
 page_title: Configure Custom Proxy
 description: "Progress® Test Studio® for APIs - CI Server Integration"
 position: 2
-publish: true
+published: true
 ---
 
 # Overview
diff --git a/docs-apitesting/advanced-topics/http-request-step-authorization.md b/docs-apitesting/advanced-topics/http-request-step-authorization.md
old mode 100644
new mode 100755
index 2a920107..d9bee21c
--- a/docs-apitesting/advanced-topics/http-request-step-authorization.md
+++ b/docs-apitesting/advanced-topics/http-request-step-authorization.md
@@ -21,17 +21,17 @@ You can enable Basic and OAuth authorization for any Http Request step by follow
 
 Create 3 new variables as shown below.
 
-![Basic][1]
+![Basic](images/variables.png)  
 
 > `credentials-concatenated` is a variable that contains the `username` and `password` variables concatenated by a `:`
 
 Add a <a href="/features/steps/set-variable">Set Variable</a> step that will transform the `credentials-concatenated` variable to a Base64 string and store it in a new variable called `credentials-encoded`
 
-![Basic][2]
+![Basic](images/encode-credentials.png)
 
 Add an <a href="/features/steps/http-request">Http Request</a> step and add an `Authorization` to the list of headers and set its value to `Basic {{credentials-encoded}}`.
 
-![Basic][3]
+![Basic](images/authorization-header.png)
 
 ## OAuth
 
@@ -41,14 +41,8 @@ Enabling OAuth authentication on a REST service api call can be achieved by comb
 
 2.Add a new request header `Content-Type` and set its value to `application/x-www-form-urlencoded` 
 
-![Basic][4]
+![Basic](images/content-type.png)
 
 3.Add all the necessary authentication parameters to the `Body` of the request. 
 
-![Basic][5]
-
-[1]: /img/features/authorization/variables.png
-[2]: /img/features/authorization/encode-credentials.png
-[3]: /img/features/authorization/authorization-header.png
-[4]: /img/features/authorization/content-type.png
-[5]: /img/features/authorization/url-encoded-body.png
\ No newline at end of file
+![Basic](images/url-encoded-body.png)
\ No newline at end of file
diff --git a/docs-apitesting/img/features/authorization/authorization-header.png b/docs-apitesting/advanced-topics/images/authorization-header.png
similarity index 100%
rename from docs-apitesting/img/features/authorization/authorization-header.png
rename to docs-apitesting/advanced-topics/images/authorization-header.png
diff --git a/docs-apitesting/img/features/authorization/content-type.png b/docs-apitesting/advanced-topics/images/content-type.png
similarity index 100%
rename from docs-apitesting/img/features/authorization/content-type.png
rename to docs-apitesting/advanced-topics/images/content-type.png
diff --git a/docs-apitesting/img/features/authorization/encode-credentials.png b/docs-apitesting/advanced-topics/images/encode-credentials.png
similarity index 100%
rename from docs-apitesting/img/features/authorization/encode-credentials.png
rename to docs-apitesting/advanced-topics/images/encode-credentials.png
diff --git a/docs-apitesting/img/features/authorization/url-encoded-body.png b/docs-apitesting/advanced-topics/images/url-encoded-body.png
similarity index 100%
rename from docs-apitesting/img/features/authorization/url-encoded-body.png
rename to docs-apitesting/advanced-topics/images/url-encoded-body.png
diff --git a/docs-apitesting/img/features/authorization/variables.png b/docs-apitesting/advanced-topics/images/variables.png
similarity index 100%
rename from docs-apitesting/img/features/authorization/variables.png
rename to docs-apitesting/advanced-topics/images/variables.png
diff --git a/docs-apitesting/copyright.md b/docs-apitesting/copyright.md
old mode 100644
new mode 100755
diff --git a/docs-apitesting/docs-builder.yml b/docs-apitesting/docs-builder.yml
new file mode 100644
index 00000000..e6129849
--- /dev/null
+++ b/docs-apitesting/docs-builder.yml
@@ -0,0 +1,68 @@
+#top nagivation might be wrong
+top-navigation-product: api-testing
+path-prefix: /teststudio-apis/documentation
+product-id: 1720
+product-name: Telerik Test Studio for APIs
+product-url: https://www.telerik.com/teststudio-apis
+search-engine-id: 001595215763381649090:lxlmtcw2g-u
+cta-overview: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+cta-intro: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+default-title-prefix: Telerik Test Studio for APIs
+avatar-path: ./images/avatar-ninja.svg
+no-results-image-path: ./images/ninja-no-results.svg
+primary-color:
+    light: "#1D8800"
+    dark: "#68BF51"
+
+product-code: TESTSTUDIOAPI
+product-trial-url: https://www.telerik.com/try/test-studio-ultimate
+contribute-url: https://github.com/telerik/teststudio-docs/edit/master/docs-apitesting
+enable-tabbed-code-blocks: true
+pdf-cover-png-path: ./images/pdf-cover.png
+img-max-width: 100%
+table-layout: fixed
+disable-html-redirect: true
+center-images: false
+
+meta:
+# === Test Studio for APIs Documentation Main Nodes ===
+    getting-started:
+        title: "Getting Started"
+        position: 2
+    features:
+        title: "Features"
+        position: 3
+    advanced-topics:
+        title: "Advanced Topics"
+        position: 4
+    troubleshooting-guide:
+        title: "Troubleshooting Guide"
+        position: 5
+        
+#   Features Section        
+    features/steps:
+        title: "Steps"
+        position: 1
+    features/code-features:
+        title: "Code Features"
+        position: 2
+    features/record:
+        title: "Record"
+        position: 3
+    features/command-line:
+        title: "Command Line Interface"
+        position: 4
+
+redirects: 
+-
+    from: "^/?$"
+    to: "/"
+-
+    from: "^/overview$"
+    to: "/"
+-
+    from: "^/features/authorization/basic-authorization$"
+    to: "/features/steps/http-request#authorization"
+-
+    from: "^/features/import/http-traffic$"
+    to: "/features/record/import-http-traffic"
\ No newline at end of file
diff --git a/docs-apitesting/downloads/Jenkins_Plugin_Apitesting.zip b/docs-apitesting/downloads/Jenkins_Plugin_Apitesting.zip
old mode 100644
new mode 100755
diff --git a/docs-apitesting/favicon.ico b/docs-apitesting/favicon.ico
old mode 100644
new mode 100755
diff --git a/docs-apitesting/features/code-features/add-assembly-reference.md b/docs-apitesting/features/code-features/add-assembly-reference.md
old mode 100644
new mode 100755
index 2a1dcb14..c306274c
--- a/docs-apitesting/features/code-features/add-assembly-reference.md
+++ b/docs-apitesting/features/code-features/add-assembly-reference.md
@@ -3,7 +3,7 @@ title: Add Assembly Reference
 page_title: Add Assembly Reference
 description: "Progress® Test Studio® for APIs - Code Features - Add Assembly Reference"
 position: 8
-publish: true
+published: true
 ---
 
 # Add Assembly Reference
diff --git a/docs-apitesting/features/code-features/code-behind-files.md b/docs-apitesting/features/code-features/code-behind-files.md
old mode 100644
new mode 100755
index f7feeead..327bd926
--- a/docs-apitesting/features/code-features/code-behind-files.md
+++ b/docs-apitesting/features/code-features/code-behind-files.md
@@ -3,7 +3,7 @@ title: Code-Behind Files
 page_title: Code-Behind Files
 description: "Progress® Test Studio® for APIs - Code Features - Code-Behind Files"
 position: 2
-publish: true
+published: true
 ---
 
 # Code-Behind Files
@@ -44,7 +44,7 @@ The example below shows hot to log messages to the test output before and after
 
 ![Base Test Methods][4]
 
-```C#
+````C#
 // This method will execute before the start of the test case
 public override void OnBeforeTestStarted()
 {
@@ -56,9 +56,8 @@ public override void OnAfterTestCompleted()
 {
 	this.Log.WriteLine("Ending the test case ...");
 }
-```
-
-```VB
+````
+````VB
 ' This method will execute before the start of the test Case'
 Public Overrides Sub OnBeforeTestStarted()
   Log.WriteLine("The test case is starting ...")
@@ -68,7 +67,7 @@ End Sub
 Public Overrides Sub OnAfterTestCompleted()
   Log.WriteLine("Ending the test case ...")
 End Sub
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -94,7 +93,7 @@ The **Context.SetValue** method sets a value to a runtime variable. You can stor
 
 #### Examples
 
-```C#
+````C#
 // This statement will create a variable named "user-name" with value "user1"
 // in the scope of the current test case
 this.Context.SetValue("user-name", "user1", o);
@@ -102,9 +101,8 @@ this.Context.SetValue("user-name", "user1", o);
 // This statement will create a variable named "user-id" with value 123
 // in the root scope of the project
 this.Context.SetValue("user-id", 123, 1);
-```
-
-```VB
+````
+````VB
 // This statement will create a variable named "user-name" with value "user1"
 // in the scope of the current test case
 this.Context.SetValue("user-name", "user1", 0);
@@ -112,7 +110,7 @@ this.Context.SetValue("user-name", "user1", 0);
 // This statement will create a variable named "user-id" with value 123
 // in the root scope of the project
 this.Context.SetValue("user-id", 123, 1);
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -135,19 +133,18 @@ The **Context.GetValue** method returns the value of a specified runtime variabl
 
 #### Examples
 
-```C#
+````C#
 string userName = this.Context.GetValue("user-name").ToString();
-```
-
-```VB
+````
+````VB
 Dim userName As String = Context.GetValue("user-name").ToString()
-```
+````
 
 > Remember to cast properly your variables when using Context.GetValue. The method returns an object and you need to be aware of where and how the target value was initially created. Any variable, created manually in the Variables pane in the UI, is stored as a string.
 
 ![Casting Variables][5]
 
-```C#
+````C#
 int count = 5;
 this.Context.SetValue("count", count, 0);
 
@@ -164,7 +161,7 @@ this.Log.WriteLine(newUserId.ToString());
 // The "user-name" variable is stored as string, but you still need to convert it with .ToString()
 string userName = this.Context.GetValue("user-name").ToString();
 this.Log.WriteLine(userName);
-```
+````
 
 [Back to top](#Code-Behind-Files)
 
@@ -180,13 +177,12 @@ The **ApiTestBase** base class exposes a **Log** property of type **ILog** which
 
 #### Examples
 
-```C#
+````C#
 this.Log.WriteLine("Logging some message from C# code ...");
-```
-
-```VB
+````
+````VB
 Log.WriteLine("Logging some message from VB code ...")
-```
+````
 
 > See the [Sample Project](../../getting-started/sample-project) for more examples.
 
@@ -198,7 +194,7 @@ The Telerik.ApiTesting.Framework namespace provides a basic assertion framework
 
 The following methods ae available:
 
-```C#
+````C#
 static void AreEqual<T>(T expected, T actual);
 
 static void AreEqual<T>(T expected, T actual, string message);
@@ -226,9 +222,8 @@ static void IsNull(object value, string message);
 static void IsTrue(bool condition);
 
 static void IsTrue(bool condition, string message);
-```
-
-```VB
+````
+````VB
 Shared Sub AreEqual(Of T)(expected As T, actual As T)
 
 Shared Sub AreEqual(Of T)(expected As T, actual As T, message As String)
@@ -256,19 +251,18 @@ Shared Sub IsNull(value As Object, message As String)
 Shared Sub IsTrue(condition As Boolean)
 
 Shared Sub IsTrue(condition As Boolean, message As String)
-```
+````
 
 > When an assertion fails, the execution of the test step will be terminated with status **failed** and the assertion message will be logged to the test output.
 
 ### Examples
 
-```C#
-Assert.AreEqual("administrator", actualValue);
-```
-
-```VB
+````C#
 Assert.AreEqual("administrator", actualValue);
-```
+````
+````VB
+Assert.AreEqual("administrator", actualValue)
+````
 
 ![Assertion Error][6]
 
diff --git a/docs-apitesting/features/code-features/code-items.md b/docs-apitesting/features/code-features/code-items.md
old mode 100644
new mode 100755
index f249bb95..d292677c
--- a/docs-apitesting/features/code-features/code-items.md
+++ b/docs-apitesting/features/code-features/code-items.md
@@ -3,7 +3,7 @@ title: Code Items
 page_title: Code Items
 description: "Progress® Test Studio® for APIs - Code Features - Code Items"
 position: 3
-publish: true
+published: true
 ---
 
 # Code Items
diff --git a/docs-apitesting/features/code-features/coded-steps.md b/docs-apitesting/features/code-features/coded-steps.md
old mode 100644
new mode 100755
index 912ef140..885634b3
--- a/docs-apitesting/features/code-features/coded-steps.md
+++ b/docs-apitesting/features/code-features/coded-steps.md
@@ -3,7 +3,7 @@ title: Coded Steps
 page_title: Coded Steps
 description: "Progress® Test Studio® for APIs - Code Features - Coded Steps"
 position: 1
-publish: true
+published: true
 ---
 
 # Coded Steps
diff --git a/docs-apitesting/features/code-features/compile-project.md b/docs-apitesting/features/code-features/compile-project.md
old mode 100644
new mode 100755
index f20d34e7..6ba70b13
--- a/docs-apitesting/features/code-features/compile-project.md
+++ b/docs-apitesting/features/code-features/compile-project.md
@@ -3,7 +3,7 @@ title: Compile Project
 page_title: Compile Project
 description: "Progress® Test Studio® for APIs - Code Features - Compile Project"
 position: 5
-publish: true
+published: true
 ---
 
 # Compile Project
diff --git a/docs-apitesting/features/code-features/debug-project.md b/docs-apitesting/features/code-features/debug-project.md
old mode 100644
new mode 100755
index 6a47c736..2de5a561
--- a/docs-apitesting/features/code-features/debug-project.md
+++ b/docs-apitesting/features/code-features/debug-project.md
@@ -3,7 +3,7 @@ title: Debug Project
 page_title: Compile Project
 description: "Progress® Test Studio® for APIs - Code Features - Debug Project"
 position: 6
-publish: true
+published: true
 ---
 
 # Debug Project
@@ -12,13 +12,12 @@ When a test project is compiled, Progress® Test Studio® for APIs generates a *
 
 To launch the debugger in Visual studio, you can add a `Debugger.Launch()` statement in the code that you wish to debug. (You wll need a `using System.Diagnostics` statement too.)
 
-```C#
-`Debugger.Launch();
-```
-
-```VB
-`Debugger.Launch()`
-```
+````C#
+Debugger.Launch();
+````
+````VB
+Debugger.Launch()
+````
 
 ![Add Debug Statement][1]
 
diff --git a/docs-apitesting/features/code-features/output-panel.md b/docs-apitesting/features/code-features/output-panel.md
old mode 100644
new mode 100755
index 680e8d88..a0a3181d
--- a/docs-apitesting/features/code-features/output-panel.md
+++ b/docs-apitesting/features/code-features/output-panel.md
@@ -3,7 +3,7 @@ title: Output Panel
 page_title: Output Panel
 description: "Progress® Test Studio® for APIs - Code Features - Output Panel"
 position: 7
-publish: true
+published: true
 ---
 
 # Output Panel
diff --git a/docs-apitesting/features/code-features/overview.md b/docs-apitesting/features/code-features/overview.md
old mode 100644
new mode 100755
index 77e5ea82..68f403b4
--- a/docs-apitesting/features/code-features/overview.md
+++ b/docs-apitesting/features/code-features/overview.md
@@ -3,7 +3,7 @@ title: Overview
 page_title: Overview
 description: "Progress® Test Studio® for APIs - Code Features - Overview"
 position: 0
-publish: true
+published: true
 ---
 
 # Code Features Overview
diff --git a/docs-apitesting/features/code-features/project-coding-language.md b/docs-apitesting/features/code-features/project-coding-language.md
old mode 100644
new mode 100755
index 4aeca5a5..4db00916
--- a/docs-apitesting/features/code-features/project-coding-language.md
+++ b/docs-apitesting/features/code-features/project-coding-language.md
@@ -3,7 +3,7 @@ title: Project Coding Language
 page_title: Project Coding Language
 description: "Progress® Test Studio® for APIs - Code Features - Project Coding Language"
 position: 4
-publish: true
+published: true
 ---
 
 # Project Coding Language
diff --git a/docs-apitesting/features/command-line/command-line-parameters.md b/docs-apitesting/features/command-line/command-line-parameters.md
old mode 100644
new mode 100755
index 1c652c05..682c364f
--- a/docs-apitesting/features/command-line/command-line-parameters.md
+++ b/docs-apitesting/features/command-line/command-line-parameters.md
@@ -3,7 +3,7 @@ title: Command Line Parameters
 page_title: Command Line Parameters
 description: "Progress® Test Studio® for APIs - Command Line Parameters"
 position: 1
-publish: true
+published: true
 ---
 # Command Line Parameters
 
diff --git a/docs-apitesting/features/command-line/overview.md b/docs-apitesting/features/command-line/overview.md
old mode 100644
new mode 100755
index 6c0ae1e2..f0c774f3
--- a/docs-apitesting/features/command-line/overview.md
+++ b/docs-apitesting/features/command-line/overview.md
@@ -3,14 +3,14 @@ title: Overview
 page_title: Overview
 description: "Progress® Test Studio® for APIs - Command Line Interface - Overview"
 position: 0
-publish: true
+published: true
 ---
 # Command Line Interface - Overview
 
 Test Studio for APIs provides a Command Line Interface application (Telerik.ApiTesting.Runner.exe) that you can use to directly execute an existing test project without using the application's user interface.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 <br>
diff --git a/docs-apitesting/features/condition.md b/docs-apitesting/features/condition.md
old mode 100644
new mode 100755
index 93df3cb8..13ca00cd
--- a/docs-apitesting/features/condition.md
+++ b/docs-apitesting/features/condition.md
@@ -3,7 +3,7 @@ title: Condition
 page_title: Condition
 description: "Progress® Test Studio® for APIs - Condition"
 position: 0
-publish: true
+published: true
 ---
 
 # Condition
diff --git a/docs-apitesting/features/project-explorer.md b/docs-apitesting/features/project-explorer.md
old mode 100644
new mode 100755
index fb60ce94..201da63d
--- a/docs-apitesting/features/project-explorer.md
+++ b/docs-apitesting/features/project-explorer.md
@@ -3,7 +3,7 @@ title: Project Explorer
 page_title: Project Explorer
 description: "Progress® Test Studio® for APIs - Project explorer functionality"
 tags: project, explorer, mobile
-publish: true
+published: true
 position: 0
 ---
 
diff --git a/docs-apitesting/features/record/http-traffic.md b/docs-apitesting/features/record/http-traffic.md
old mode 100644
new mode 100755
index 95a8ceac..c9cebf1e
--- a/docs-apitesting/features/record/http-traffic.md
+++ b/docs-apitesting/features/record/http-traffic.md
@@ -3,7 +3,7 @@ title: Record HTTP(S) Traffic
 page_title: Record HTTP(S) Traffic
 description: "Progress® Test Studio® for APIs - Record HTTP(S) Traffic"
 position: 1
-publish: true
+published: true
 ---
 
 # Record HTTP(S) Traffic
diff --git a/docs-apitesting/features/record/import-http-traffic.md b/docs-apitesting/features/record/import-http-traffic.md
old mode 100644
new mode 100755
index ced7f41a..cfec5361
--- a/docs-apitesting/features/record/import-http-traffic.md
+++ b/docs-apitesting/features/record/import-http-traffic.md
@@ -3,7 +3,7 @@ title: Import HTTP(S) Traffic
 page_title: Import HTTP(S) Traffic
 description: "Progress® Test Studio® for APIs - Import HTTP(S) Traffic"
 position: 2
-publish: true
+published: true
 ---
 
 # Import HTTP(S) Traffic
diff --git a/docs-apitesting/features/source-path-expressions.md b/docs-apitesting/features/source-path-expressions.md
old mode 100644
new mode 100755
index 5d1248ea..e0bd0c63
--- a/docs-apitesting/features/source-path-expressions.md
+++ b/docs-apitesting/features/source-path-expressions.md
@@ -3,7 +3,7 @@ title: Source Path Expressions
 page_title: Source Path Expressions
 description: "Progress® Test Studio® for APIs - Source Path Expressions"
 position: 0
-publish: true
+published: true
 ---
 
 # Source Path Expressions
diff --git a/docs-apitesting/features/steps/goto.md b/docs-apitesting/features/steps/goto.md
old mode 100644
new mode 100755
index 39defba7..f53186f2
--- a/docs-apitesting/features/steps/goto.md
+++ b/docs-apitesting/features/steps/goto.md
@@ -3,7 +3,7 @@ title: Goto Step
 page_title: Goto Step
 description: "Progress® Test Studio® for APIs - Steps - Goto Step"
 position: 1
-publish: true
+published: true
 ---
 
 # Goto Step
diff --git a/docs-apitesting/features/steps/http-request.md b/docs-apitesting/features/steps/http-request.md
old mode 100644
new mode 100755
index c46d6c0c..cb68fc54
--- a/docs-apitesting/features/steps/http-request.md
+++ b/docs-apitesting/features/steps/http-request.md
@@ -3,7 +3,7 @@ title: Http Request Step
 page_title: Http Request Step
 description: "Progress® Test Studio® for APIs - Steps - Http Request Step"
 position: 2
-publish: true
+published: true
 ---
 
 # Http Request Step
diff --git a/docs-apitesting/features/steps/overview.md b/docs-apitesting/features/steps/overview.md
old mode 100644
new mode 100755
index 6b6b8926..69470c2c
--- a/docs-apitesting/features/steps/overview.md
+++ b/docs-apitesting/features/steps/overview.md
@@ -3,7 +3,7 @@ title: Overview
 page_title: Overview
 description: "Progress® Test Studio® for APIs - Steps - Overview"
 position: 0
-publish: true
+published: true
 ---
 
 # Steps Overview
diff --git a/docs-apitesting/features/steps/set-variable.md b/docs-apitesting/features/steps/set-variable.md
old mode 100644
new mode 100755
index ec6dfd8f..44fd17b3
--- a/docs-apitesting/features/steps/set-variable.md
+++ b/docs-apitesting/features/steps/set-variable.md
@@ -3,7 +3,7 @@ title: Set Variable Step
 page_title: Set Variable Step
 description: "Progress® Test Studio® for APIs - Steps - Set Variable Step"
 position: 3
-publish: true
+published: true
 ---
 
 # Set Variable Step
diff --git a/docs-apitesting/features/steps/verification.md b/docs-apitesting/features/steps/verification.md
old mode 100644
new mode 100755
index 0f485cee..3557258b
--- a/docs-apitesting/features/steps/verification.md
+++ b/docs-apitesting/features/steps/verification.md
@@ -3,7 +3,7 @@ title: Verification Step
 page_title: Verification Step
 description: "Progress® Test Studio® for APIs - Steps - Verification Step"
 position: 4
-publish: true
+published: true
 ---
 
 # Verification Step
diff --git a/docs-apitesting/features/steps/wait.md b/docs-apitesting/features/steps/wait.md
old mode 100644
new mode 100755
index e7dd5805..71726064
--- a/docs-apitesting/features/steps/wait.md
+++ b/docs-apitesting/features/steps/wait.md
@@ -3,7 +3,7 @@ title: Wait Step
 page_title: Wait Step
 description: "Progress® Test Studio® for APIs - Steps - Wait Step"
 position: 5
-publish: true
+published: true
 ---
 
 # Wait Step
diff --git a/docs-apitesting/features/test-results.md b/docs-apitesting/features/test-results.md
old mode 100644
new mode 100755
index a9374b40..ef873b92
--- a/docs-apitesting/features/test-results.md
+++ b/docs-apitesting/features/test-results.md
@@ -3,7 +3,7 @@ title: Test Results
 page_title: Test Results
 description: "Progress® Test Studio® for APIs - Test Results"
 position: 0
-publish: true
+published: true
 ---
 
 # Test Results
diff --git a/docs-apitesting/features/variables.md b/docs-apitesting/features/variables.md
old mode 100644
new mode 100755
index 02728412..9153b321
--- a/docs-apitesting/features/variables.md
+++ b/docs-apitesting/features/variables.md
@@ -3,7 +3,7 @@ title: Variables
 page_title: Variables
 description: "Progress® Test Studio® for APIs - Variables"
 position: 0
-publish: true
+published: true
 ---
 
 # Variables
diff --git a/docs-apitesting/features/verifications.md b/docs-apitesting/features/verifications.md
old mode 100644
new mode 100755
index d8840895..a576b917
--- a/docs-apitesting/features/verifications.md
+++ b/docs-apitesting/features/verifications.md
@@ -3,7 +3,7 @@ title: Verifications
 page_title: Verifications
 description: "Progress® Test Studio® for APIs - Verifications"
 position: 0
-publish: true
+published: true
 ---
 
 # Verifications
diff --git a/docs-apitesting/fonts/FontAwesome.otf b/docs-apitesting/fonts/FontAwesome.otf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Bold-webfont.eot b/docs-apitesting/fonts/OpenSans-Bold-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Bold-webfont.svg b/docs-apitesting/fonts/OpenSans-Bold-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Bold-webfont.ttf b/docs-apitesting/fonts/OpenSans-Bold-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Bold-webfont.woff b/docs-apitesting/fonts/OpenSans-Bold-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Italic-webfont.eot b/docs-apitesting/fonts/OpenSans-Italic-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Italic-webfont.svg b/docs-apitesting/fonts/OpenSans-Italic-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Italic-webfont.ttf b/docs-apitesting/fonts/OpenSans-Italic-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Italic-webfont.woff b/docs-apitesting/fonts/OpenSans-Italic-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Light-webfont.eot b/docs-apitesting/fonts/OpenSans-Light-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Light-webfont.svg b/docs-apitesting/fonts/OpenSans-Light-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Light-webfont.ttf b/docs-apitesting/fonts/OpenSans-Light-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Light-webfont.woff b/docs-apitesting/fonts/OpenSans-Light-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Regular-webfont.eot b/docs-apitesting/fonts/OpenSans-Regular-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Regular-webfont.svg b/docs-apitesting/fonts/OpenSans-Regular-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Regular-webfont.ttf b/docs-apitesting/fonts/OpenSans-Regular-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Regular-webfont.woff b/docs-apitesting/fonts/OpenSans-Regular-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Semibold-webfont.eot b/docs-apitesting/fonts/OpenSans-Semibold-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Semibold-webfont.svg b/docs-apitesting/fonts/OpenSans-Semibold-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Semibold-webfont.ttf b/docs-apitesting/fonts/OpenSans-Semibold-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-Semibold-webfont.woff b/docs-apitesting/fonts/OpenSans-Semibold-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.eot b/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.svg b/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.ttf b/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.woff b/docs-apitesting/fonts/OpenSans-SemiboldItalic-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/fontawesome-webfont.eot b/docs-apitesting/fonts/fontawesome-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/fontawesome-webfont.svg b/docs-apitesting/fonts/fontawesome-webfont.svg
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/fontawesome-webfont.ttf b/docs-apitesting/fonts/fontawesome-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-apitesting/fonts/fontawesome-webfont.woff b/docs-apitesting/fonts/fontawesome-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-apitesting/getting-started/installation.md b/docs-apitesting/getting-started/installation.md
old mode 100644
new mode 100755
index 380365cd..c613d2bc
--- a/docs-apitesting/getting-started/installation.md
+++ b/docs-apitesting/getting-started/installation.md
@@ -3,10 +3,10 @@ title: Installation
 page_title: Installation
 description: "Progress® Test Studio® for APIs - Getting Started - Installation"
 position: 1
-publish: true
+published: true
 ---
 
-#Installation Procedure
+# Installation Procedure
 
 1. After you have downloaded the install file, locate it using Windows Explorer and double click it to launch the installer.
 2. Click __Read License Agreement__, then __OK__, then I __Agree - Continue__.
diff --git a/docs-apitesting/getting-started/personal-data.md b/docs-apitesting/getting-started/personal-data.md
old mode 100644
new mode 100755
diff --git a/docs-apitesting/getting-started/sample-project.md b/docs-apitesting/getting-started/sample-project.md
old mode 100644
new mode 100755
index a61f9dc8..23882abd
--- a/docs-apitesting/getting-started/sample-project.md
+++ b/docs-apitesting/getting-started/sample-project.md
@@ -3,10 +3,10 @@ title: Sample Project
 page_title: Sample Project
 description: "Progress® Test Studio® for APIs - Getting Started - Sample Project"
 position: 2
-publish: true
+published: true
 ---
 
-#Running Sample Project 
+# Running Sample Project 
 
 To help you explore the functionalities of Test Studio for APIs we have created a demo test project that calls a very simple demo application under test.
 
diff --git a/docs-apitesting/images/2.png b/docs-apitesting/images/2.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/anchor.png b/docs-apitesting/images/anchor.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/api.png b/docs-apitesting/images/api.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/arrow.png b/docs-apitesting/images/arrow.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/avatar-ninja.svg b/docs-apitesting/images/avatar-ninja.svg
new file mode 100755
index 00000000..d98c1b20
--- /dev/null
+++ b/docs-apitesting/images/avatar-ninja.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="109.579" height="100" viewBox="0 0 109.579 100"><defs><style>.a{fill:#a3d8f1;}.b{fill:#fff;}.c{fill:#e3f6ff;}.d{fill:#8174f2;}.e{clip-path:url(#a);}.f,.h,.i,.k{fill:none;}.f{stroke:#0c1b38;stroke-width:30px;}.f,.i,.k{stroke-linecap:round;}.f,.h{stroke-miterlimit:10;}.g{fill:#4f5d6c;}.h{stroke:#000;stroke-width:24.468px;}.i{stroke:#0c1121;stroke-width:20.645px;}.i,.k{stroke-linejoin:round;}.j{fill:#0c1121;}.k{stroke:#14254c;stroke-width:45.877px;}.l{fill:#0c1b38;}.m{fill:#e9ac6a;}.n{fill:#e26841;}</style><clipPath id="a"><ellipse class="a" cx="50" cy="50" rx="50" ry="50" transform="translate(-11251.149 -21710)"/></clipPath></defs><path class="b" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><path class="c" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><g transform="translate(0 12.775)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g class="e" transform="translate(11260.729 21710)"><g transform="translate(-12096.358 -23981.338)"><path class="f" d="M3158.423,2368.839c36.843.145,65.382-23.7,68.744-50.983,3-24.348-15.059-43.243-18.055-46.286" transform="translate(-2234.18 -19.121)"/><g transform="translate(939.33 2257.389)"><path class="g" d="M3203.488,2283.094l7.821,11.323-.855,1.8-20.468,1.627-11.668-16.894.855-1.8,13.4-1.065Z" transform="translate(-3178.317 -2278.085)"/></g><g transform="translate(950.734 2192.443)"><path class="g" d="M3222.208,2230.646l14.987-31.541a2.648,2.648,0,0,0-1.258-3.526l-6.063-2.879a2.647,2.647,0,0,0-3.528,1.252l-32.99,69.127,10.849,5.154,6.518-13.412Z" transform="translate(-3193.356 -2192.443)"/></g><g transform="translate(951.545 2227.636)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.991,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 22.12) rotate(-65.013)"/></g><line class="h" x1="0.724" y2="27.18" transform="translate(844.735 2493.343)"/><path d="M3155.778,2444.706l1.234-32.591a34.077,34.077,0,0,0-38.951-35.012h0a34.077,34.077,0,0,0-27.836,43.189l9.06,31.33a28.825,28.825,0,0,0,30.725,20.658h0A28.824,28.824,0,0,0,3155.778,2444.706Z" transform="translate(-2217.373 -44.536)"/><path class="i" d="M2905.35,2587.494l-49.786,32.326" transform="translate(-2160.994 -95.464)"/><path class="j" d="M3142.522,2628.677a7.968,7.968,0,0,0,8.055,8.435l3.028-.039,27.262-.343a4.921,4.921,0,0,0,.692-9.783l-14.5-2.532-14.975-3.078a7.969,7.969,0,0,0-9.56,7.34Z" transform="translate(-2230.335 -103.603)"/><path class="j" d="M2851.56,2628.677a7.969,7.969,0,0,1-8.055,8.435l-3.028-.039-27.262-.343a4.921,4.921,0,0,1-.693-9.783l14.5-2.532,14.975-3.078a7.968,7.968,0,0,1,9.56,7.34Z" transform="translate(-2149.586 -103.603)"/><path class="i" d="M3210.51,2580.636q-9.805,7.145-20.237,14.306-19.106,13.1-37.478,24.294" transform="translate(-2232.82 -93.807)"/><path class="k" d="M3153.983,2510.447c2.631-.136,5.669-.226,9.057-.2,5.714.044,20.339.235,34.771,4.322,13.86,3.926,28.827,8.165,31.9,17.693,3.67,11.374-9.988,29.089-34.05,42.144" transform="translate(-2233.107 -76.797)"/><path class="k" d="M3064.752,2503.885a530.633,530.633,0,0,0-167.838,72.336" transform="translate(-2170.987 -75.261)"/><g transform="translate(900.392 2433.461)"><path class="j" d="M3126.972,2510.262" transform="translate(-3126.972 -2510.262)"/></g><path d="M3177.856,2483.313l-61.336-19.153h0q-15.026,5.272-30.776,10.39-18.815,6.107-36.943,11.419a72.634,72.634,0,0,0,129.055-2.656Z" transform="translate(-2207.69 -65.661)"/><rect class="d" width="57.81" height="19.325" transform="matrix(-0.988, 0.157, -0.157, -0.988, 942.407, 2422.056)"/><g transform="translate(835.308 2508.631)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.992,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 0.347) rotate(-0.814)"/></g><path class="f" d="M3089.63,2423.256a159.413,159.413,0,0,0-27.3,48.023,161.1,161.1,0,0,0-7.566,76.309" transform="translate(-2208.744 -55.776)"/><g transform="translate(835.63 2284.113)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g transform="translate(873.087 2289.57)"><path class="l" d="M3114.193,2320.557l-2.984.175a21.267,21.267,0,0,0-19.861,23.857l2.83,22.75a21.268,21.268,0,0,0,22.349,18.605h0a21.268,21.268,0,0,0,20.024-21.088l.154-22.924A21.268,21.268,0,0,0,3114.193,2320.557Z" transform="translate(-3091.019 -2320.52)"/><rect class="d" width="45.527" height="11.326" transform="translate(46.111 27.879) rotate(176.647)"/><rect class="m" width="39.681" height="11.634" rx="5.817" transform="translate(43.547 34.093) rotate(176.647)"/><path class="n" d="M3117.6,2364.1l5.041-.3-.568-9.691Z" transform="translate(-3097.402 -2328.638)"/><g transform="translate(7.384 26.937)"><rect class="b" width="6.105" height="3.243" rx="1.622" transform="matrix(-0.998, 0.058, -0.058, -0.998, 6.284, 4.693)"/><rect class="b" width="6.105" height="3.243" rx="1.622" transform="translate(31.121 3.237) rotate(176.647)"/></g><circle cx="1.643" cy="1.643" r="1.643" transform="translate(7.477 28.64)"/><circle cx="1.643" cy="1.643" r="1.643" transform="translate(32.314 27.185)"/></g></g></g></svg>
\ No newline at end of file
diff --git a/docs-apitesting/images/close.png b/docs-apitesting/images/close.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/column.png b/docs-apitesting/images/column.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/getting-started.png b/docs-apitesting/images/getting-started.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/howdoi.png b/docs-apitesting/images/howdoi.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/icon-telerik-badge.png b/docs-apitesting/images/icon-telerik-badge.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/important.png b/docs-apitesting/images/important.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/logo.png b/docs-apitesting/images/logo.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/menu.png b/docs-apitesting/images/menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/nav-arrow.png b/docs-apitesting/images/nav-arrow.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/ninja-icon.png b/docs-apitesting/images/ninja-icon.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/ninja-no-results.svg b/docs-apitesting/images/ninja-no-results.svg
new file mode 100755
index 00000000..5d84ade5
--- /dev/null
+++ b/docs-apitesting/images/ninja-no-results.svg
@@ -0,0 +1,47 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" id="Layer_1" x="0px" y="0px" style="enable-background:new 0 0 2000 2000;" height="150px" width="106px" xml:space="preserve" viewBox="631.99 547.8 788.26 904.27">
+	<style type="text/css">
+		.st0{fill:none;stroke:#0B1122;stroke-width:47.0486;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st1{fill:#0B1122;}
+		.st2{fill:none;stroke:#14254C;stroke-width:104.5525;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st3{fill:none;stroke:#0C1B38;stroke-width:78.4143;stroke-linecap:round;stroke-miterlimit:10;}
+		.st4{fill:#8174F2;}
+		.st5{fill:#0C1B38;}
+		.st6{fill:#E7AA6A;}
+		.st7{fill:#E26841;}
+		.st8{fill:#EEF5FF;}
+		.st9{fill:#4F5D6C;}
+	</style>
+	<g>
+		<path class="st0" d="M723.7,1237.5c11.8,47.5,23.5,95,35.3,142.5"/>
+		<path class="st1" d="M788.6,1383c1,16.7-12.4,30.8-29.2,30.6l-11-0.1l-98.8-1.2c-8.6-0.1-16-6.4-17.4-15.1   c-1.5-9.7,5.2-18.8,14.9-20.4l52.6-9.2l54.3-11.2C771.2,1352.8,787.6,1365.4,788.6,1383L788.6,1383z"/>
+		<path class="st2" d="M1034.1,1192.7c-103-137.5-230.5-179.8-283.3-141.7c-56.8,41-26.1,174.6-24,183.3"/>
+		<path class="st3" d="M1010.1,863.6c-105.4-13.1-192.5,68.8-191.7,156.2c0.7,74,64.5,144.9,152.1,154.2"/>
+		<path class="st3" d="M1108,863.6c105.4-13.1,192.5,68.8,191.7,156.2c-0.7,74-64.5,144.9-152.1,154.2"/>
+		<path d="M1204.6,1064.3l4.5-124.8c3-81.4-68-145.8-147.9-134.2l0,0c-77.6,11.3-127.2,89.2-105.4,165.2l34.5,120   c14.8,51.4,63.9,84.8,116.6,79.2h0C1161,1164,1202.6,1119.1,1204.6,1064.3z"/>
+		<path class="st1" d="M932.5,1322.1c-13.7-9.6-32.7-5.6-41.4,8.8l-5.6,9.4l-50.8,84.8c-4.4,7.3-3,17,3.7,22.7   c7.5,6.4,18.8,5.5,25.1-2L899,1406l38-40.3C949.1,1352.8,947,1332.2,932.5,1322.1L932.5,1322.1z"/>
+		<path class="st0" d="M1163.2,1330c-29.1,3.2-59,6.1-89.4,8.6c-55.8,4.5-109.7,7.4-161.7,8.9"/>
+		<path class="st2" d="M1139.4,1174.4c22.6-0.8,55-0.5,93.6,4.7c53.8,7.3,81.3,10.5,103.1,31.2c20.8,19.8,37.3,54.9,30.2,79.4   c-22.1,75.8-274.5,59.3-297.1,57.7"/>
+		<g>
+			<path class="st4" d="M1150.3,749.8c28.6-11.3,48.6-9.1,61.5-11.9c23.7-5.2,52.3-34.8,72.7-143.2c-16.9-4.8-33.7-9.6-50.6-14.4    c-3.8,85.1-25.7,115-46.6,125.5c-9.5,4.8-22.5,8.2-39.6,20.4c-20,14.3-30.8,33.5-36.8,47.4    C1119.2,766.5,1132.4,756.9,1150.3,749.8z"/>
+			<path class="st4" d="M1208.2,565c-14.7-5.7-29.5-11.5-44.2-17.2c7.3,59.9-6.2,93.7-20.4,113.6c-9.8,13.7-22.1,26.5-31.2,50.4    c-8.4,21.8-5.8,43-2.5,57.1c5.3-14.5,14.9-34.5,33-52.6c16.4-16.5,28.1-23.1,37.4-31.1C1197.7,670,1214.9,638.4,1208.2,565z"/>
+		</g>
+		<g>
+			<path class="st5" d="M1080.4,711.3l-10.8,0.4c-44.5,1.5-78.5,40.3-74.2,84.6l8.2,82.7c4,40.4,38.7,70.8,79.3,69.5h0    c40.6-1.3,73.2-34,74.5-74.6l2.7-83.1C1161.4,746.3,1124.9,709.8,1080.4,711.3z"/>
+			
+				<rect x="995.9" y="795.4" transform="matrix(-0.9994 3.316386e-02 -3.316386e-02 -0.9994 2183.395 1595.6785)" class="st4" width="165" height="41.1"/>
+			<path class="st6" d="M1012.5,860.6l132.4-4.4c3.1-0.1,5.6-2.7,5.5-5.9l-1-30.8c-0.1-3.1-2.7-5.6-5.9-5.5l-132.4,4.4    c-3.1,0.1-5.6,2.7-5.5,5.9l1,30.8C1006.7,858.2,1009.3,860.7,1012.5,860.6z"/>
+			<polygon class="st7" points="1065.8,858.8 1084.1,858.2 1082.9,823   "/>
+			<g>
+				<path class="st8" d="M1021.8,850.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1020.2,849.7,1021,850.4,1021.8,850.4z"/>
+				<path class="st8" d="M1112,847.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1110.4,846.7,1111.1,847.4,1112,847.4z"/>
+			</g>
+			<circle cx="1031.7" cy="849.1" r="6"/>
+			<circle cx="1121.8" cy="846.1" r="6"/>
+		</g>
+		<g>
+			<rect x="906.3" y="1031.2" class="st9" width="371.7" height="269.2"/>
+			<rect x="906.3" y="1293.9" width="371.7" height="24.1"/>
+		</g>
+		<path class="st8" d="M1101.4,1157.7l-14.7-19.5l-2.1,17.8l-19.5,14.7l17.8,2.1l14.7,19.5l2.1-17.8l19.5-14.7L1101.4,1157.7z    M1091.7,1168.6c-1.8-0.2-3.1-1.9-2.9-3.7c0.2-1.8,1.9-3.1,3.7-2.9c1.8,0.2,3.1,1.9,2.9,3.7   C1095.2,1167.5,1093.5,1168.8,1091.7,1168.6z"/>
+	</g>
+</svg>
diff --git a/docs-apitesting/images/open.png b/docs-apitesting/images/open.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/pdf-cover.png b/docs-apitesting/images/pdf-cover.png
new file mode 100644
index 00000000..ce9967ef
Binary files /dev/null and b/docs-apitesting/images/pdf-cover.png differ
diff --git a/docs-apitesting/images/search.png b/docs-apitesting/images/search.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/tap-logo1.png b/docs-apitesting/images/tap-logo1.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/testStudioLogo.png b/docs-apitesting/images/testStudioLogo.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/testStudioforAPIsLogo.png b/docs-apitesting/images/testStudioforAPIsLogo.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/images/tutorials.png b/docs-apitesting/images/tutorials.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/advanced-topics/ci-server-integration/build-api-runner-task.png b/docs-apitesting/img/advanced-topics/ci-server-integration/build-api-runner-task.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/advanced-topics/ci-server-integration/build-task-options.png b/docs-apitesting/img/advanced-topics/ci-server-integration/build-task-options.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/advanced-topics/ci-server-integration/publish-junit.png b/docs-apitesting/img/advanced-topics/ci-server-integration/publish-junit.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/accessing-variables.png b/docs-apitesting/img/features/accessing-variables.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/authorization/basic-authorization/authorization-header.png b/docs-apitesting/img/features/authorization/basic-authorization/authorization-header.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/authorization/basic-authorization/encode-credentials.png b/docs-apitesting/img/features/authorization/basic-authorization/encode-credentials.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/clear-all-runtime-variables.png b/docs-apitesting/img/features/clear-all-runtime-variables.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/add-code-behind.png b/docs-apitesting/img/features/code-features/add-code-behind.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/add-code-item.png b/docs-apitesting/img/features/code-features/add-code-item.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/add-coded-step-context-menu.png b/docs-apitesting/img/features/code-features/add-coded-step-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/add-coded-step-test-explorer.png b/docs-apitesting/img/features/code-features/add-coded-step-test-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/add-reference-button.png b/docs-apitesting/img/features/code-features/add-reference-button.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/added-reference-assembly.png b/docs-apitesting/img/features/code-features/added-reference-assembly.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/assert-error.png b/docs-apitesting/img/features/code-features/assert-error.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/code-item-example.png b/docs-apitesting/img/features/code-features/code-item-example.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/code-item-in-project-explorer.png b/docs-apitesting/img/features/code-features/code-item-in-project-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/coded-step-select-method.png b/docs-apitesting/img/features/code-features/coded-step-select-method.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/coded-step-select-valid-method.png b/docs-apitesting/img/features/code-features/coded-step-select-valid-method.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/compile-output.png b/docs-apitesting/img/features/code-features/compile-output.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/compile-project-button.png b/docs-apitesting/img/features/code-features/compile-project-button.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/compile-project-conetxt-menu.png b/docs-apitesting/img/features/code-features/compile-project-conetxt-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/debug-in-visual-studio.png b/docs-apitesting/img/features/code-features/debug-in-visual-studio.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/debug-launch-debugger.png b/docs-apitesting/img/features/code-features/debug-launch-debugger.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/debug-prompt.png b/docs-apitesting/img/features/code-features/debug-prompt.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/debug-select-vs-instance.png b/docs-apitesting/img/features/code-features/debug-select-vs-instance.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/default-test-method.png b/docs-apitesting/img/features/code-features/default-test-method.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/edit-class-name-mapping.png b/docs-apitesting/img/features/code-features/edit-class-name-mapping.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/edit-project-properties-toolbar.png b/docs-apitesting/img/features/code-features/edit-project-properties-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/executing-base-test-methods.png b/docs-apitesting/img/features/code-features/executing-base-test-methods.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/general-output.png b/docs-apitesting/img/features/code-features/general-output.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/invalid-method-mapping-warning.png b/docs-apitesting/img/features/code-features/invalid-method-mapping-warning.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/open-code-behind.png b/docs-apitesting/img/features/code-features/open-code-behind.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/output-pane.png b/docs-apitesting/img/features/code-features/output-pane.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/project-properties-context-menu.png b/docs-apitesting/img/features/code-features/project-properties-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/project-properties-dialog.png b/docs-apitesting/img/features/code-features/project-properties-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/select-assembly-file.png b/docs-apitesting/img/features/code-features/select-assembly-file.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/select-project-language.png b/docs-apitesting/img/features/code-features/select-project-language.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/set-code-item-name.png b/docs-apitesting/img/features/code-features/set-code-item-name.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/using-a-code-item.png b/docs-apitesting/img/features/code-features/using-a-code-item.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/code-features/variables-casting.png b/docs-apitesting/img/features/code-features/variables-casting.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/command-line/apitesting-runner-help.png b/docs-apitesting/img/features/command-line/apitesting-runner-help.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/command-line/apitesting-runner-location.png b/docs-apitesting/img/features/command-line/apitesting-runner-location.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/condition-prefix-cmd.png b/docs-apitesting/img/features/condition-prefix-cmd.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/condition-prefix.png b/docs-apitesting/img/features/condition-prefix.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/condition.png b/docs-apitesting/img/features/condition.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/disable-step.png b/docs-apitesting/img/features/disable-step.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/folder-item-context-menu.png b/docs-apitesting/img/features/folder-item-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/full-value-path-option.png b/docs-apitesting/img/features/full-value-path-option.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/conditions-and-verifications.png b/docs-apitesting/img/features/import/conditions-and-verifications.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/exchange-details.png b/docs-apitesting/img/features/import/exchange-details.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/import.png b/docs-apitesting/img/features/import/import.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/open-saz.png b/docs-apitesting/img/features/import/open-saz.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/saz-contents.png b/docs-apitesting/img/features/import/saz-contents.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/import/session-exchange.png b/docs-apitesting/img/features/import/session-exchange.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/nesting-variables.png b/docs-apitesting/img/features/nesting-variables.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/project-explorer-create-buttons.png b/docs-apitesting/img/features/project-explorer-create-buttons.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/project-explorer-search.png b/docs-apitesting/img/features/project-explorer-search.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/project-item-context-menu.png b/docs-apitesting/img/features/project-item-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/add-session.png b/docs-apitesting/img/features/record/add-session.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/browser-https-error.png b/docs-apitesting/img/features/record/browser-https-error.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/capturing-traffic.png b/docs-apitesting/img/features/record/capturing-traffic.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/certificate.png b/docs-apitesting/img/features/record/certificate.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/certificate1.png b/docs-apitesting/img/features/record/certificate1.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/clear-all.png b/docs-apitesting/img/features/record/clear-all.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/https-disabled-message.png b/docs-apitesting/img/features/record/https-disabled-message.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/new-tab.png b/docs-apitesting/img/features/record/new-tab.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/record-traffic-menu.png b/docs-apitesting/img/features/record/record-traffic-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/record-traffic-toolbar.png b/docs-apitesting/img/features/record/record-traffic-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/recording-settings.png b/docs-apitesting/img/features/record/recording-settings.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/root-certificate-warning.png b/docs-apitesting/img/features/record/root-certificate-warning.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/stop-button.png b/docs-apitesting/img/features/record/stop-button.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/record/trash.png b/docs-apitesting/img/features/record/trash.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/source-path-options.png b/docs-apitesting/img/features/source-path-options.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/step-item-context-menu.png b/docs-apitesting/img/features/step-item-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/goto.png b/docs-apitesting/img/features/steps/goto.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request-body-format-json.png b/docs-apitesting/img/features/steps/http-request-body-format-json.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request-body-format-raw.png b/docs-apitesting/img/features/steps/http-request-body-format-raw.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request.png b/docs-apitesting/img/features/steps/http-request.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-form-data-response.png b/docs-apitesting/img/features/steps/http-request/body/body-form-data-response.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-form-data-test-file.png b/docs-apitesting/img/features/steps/http-request/body/body-form-data-test-file.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-form-data.png b/docs-apitesting/img/features/steps/http-request/body/body-form-data.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-raw-response.png b/docs-apitesting/img/features/steps/http-request/body/body-raw-response.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-raw.png b/docs-apitesting/img/features/steps/http-request/body/body-raw.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/body/body-x-www-form-urlencoded.png b/docs-apitesting/img/features/steps/http-request/body/body-x-www-form-urlencoded.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/decompress-response-http-setting.png b/docs-apitesting/img/features/steps/http-request/decompress-response-http-setting.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-basic-headers.png b/docs-apitesting/img/features/steps/http-request/http-request-basic-headers.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-basic.png b/docs-apitesting/img/features/steps/http-request/http-request-basic.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-formatting.png b/docs-apitesting/img/features/steps/http-request/http-request-formatting.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-oauth-body.png b/docs-apitesting/img/features/steps/http-request/http-request-oauth-body.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-oauth-headers.png b/docs-apitesting/img/features/steps/http-request/http-request-oauth-headers.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-oauth.png b/docs-apitesting/img/features/steps/http-request/http-request-oauth.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-protocol.png b/docs-apitesting/img/features/steps/http-request/http-request-protocol.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-response-image.png b/docs-apitesting/img/features/steps/http-request/http-request-response-image.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-response-json.png b/docs-apitesting/img/features/steps/http-request/http-request-response-json.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-request/http-request-response.png b/docs-apitesting/img/features/steps/http-request/http-request-response.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/http-response.png b/docs-apitesting/img/features/steps/http-response.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/set-variable-transformations.png b/docs-apitesting/img/features/steps/set-variable-transformations.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/set-variable.png b/docs-apitesting/img/features/steps/set-variable.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/verification.png b/docs-apitesting/img/features/steps/verification.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/steps/wait.png b/docs-apitesting/img/features/steps/wait.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/test-item-context-menu.png b/docs-apitesting/img/features/test-item-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/variables-pane.png b/docs-apitesting/img/features/variables-pane.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/features/verifications/verification-error.png b/docs-apitesting/img/features/verifications/verification-error.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/installation/install-completed.png b/docs-apitesting/img/getting-started/installation/install-completed.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/installation/install.png b/docs-apitesting/img/getting-started/installation/install.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/installation/setup-wizard.png b/docs-apitesting/img/getting-started/installation/setup-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/installation/welcome-screen.png b/docs-apitesting/img/getting-started/installation/welcome-screen.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/sample-project/create-demo-project.png b/docs-apitesting/img/getting-started/sample-project/create-demo-project.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/sample-project/execute-demo-tests.png b/docs-apitesting/img/getting-started/sample-project/execute-demo-tests.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/getting-started/sample-project/run-demo-application.png b/docs-apitesting/img/getting-started/sample-project/run-demo-application.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/troubleshooting-guide/deregister-proxy/no-internet-connection.png b/docs-apitesting/img/troubleshooting-guide/deregister-proxy/no-internet-connection.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/troubleshooting-guide/deregister-proxy/registered-proxy.png b/docs-apitesting/img/troubleshooting-guide/deregister-proxy/registered-proxy.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/troubleshooting-guide/deregister-proxy/windows10.png b/docs-apitesting/img/troubleshooting-guide/deregister-proxy/windows10.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/troubleshooting-guide/no-test-execution-output/no-test-execution-output.png b/docs-apitesting/img/troubleshooting-guide/no-test-execution-output/no-test-execution-output.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/img/troubleshooting-guide/request-headers/request-headers.png b/docs-apitesting/img/troubleshooting-guide/request-headers/request-headers.png
old mode 100644
new mode 100755
diff --git a/docs-apitesting/index.md b/docs-apitesting/index.md
old mode 100644
new mode 100755
index 87847d94..67b93042
--- a/docs-apitesting/index.md
+++ b/docs-apitesting/index.md
@@ -1,16 +1,16 @@
 ---
-title: Index
-page_title: Overview
+title: About Test Studio for APIs
+page_title: About of Test Studio for APIs
 description: "Progress® Test Studio® for APIs - Overview"
 position: 1
 ---
 
-# Overview
+# About Test Studio for APIs
 
 The new Test Studio for APIs helps customers verify the integrity and reliability of their APIs in an easy way and incorporate their API testing effort in their continuous testing and delivery process. Test Studio for APIs is used to determine whether APIs return the correct response for a broad range of commonly accepted requests, react properly to edge cases such as failures and unexpected inputs, as well as deliver the responses in an acceptable amount of time.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Features
diff --git a/docs-apitesting/redirect-tests-teststudio-apis.csv b/docs-apitesting/redirect-tests-teststudio-apis.csv
new file mode 100644
index 00000000..f3ff9961
--- /dev/null
+++ b/docs-apitesting/redirect-tests-teststudio-apis.csv
@@ -0,0 +1,5 @@
+, /
+/SYSTEM-REQUIREMENTS, /system-requirements
+/overview, /
+/features/authorization/basic-authorization, /features/steps/http-request#authorization
+/features/import/http-traffic, /features/record/import-http-traffic
\ No newline at end of file
diff --git a/docs-apitesting/run.cmd b/docs-apitesting/run.cmd
old mode 100644
new mode 100755
diff --git a/docs-apitesting/system-requirements.md b/docs-apitesting/system-requirements.md
old mode 100644
new mode 100755
index f17231db..d04b2f28
--- a/docs-apitesting/system-requirements.md
+++ b/docs-apitesting/system-requirements.md
@@ -6,23 +6,23 @@ into your continuous testing and delivery process. Telerik API Testing by Progre
 enables even non-technical testers to get up-to-speed with testing APIs."
 position: 1
 ---
-# System Requirements#
+# System Requirements
 
 ## Supported Environments
 
 * .NET Framework - 4.7.2
 
-## Supported Operating Systems##
+## Supported Operating Systems
 
 * Windows 11. 10, 8.1
 * Windows Server 2012, 2016, 2019
 
-## Minimum Hardware Requirements##
+## Minimum Hardware Requirements
 
 * Disk Space: 500MB
 * RAM: 2GB
 * CPU: 2.4GHz
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
\ No newline at end of file
diff --git a/docs-apitesting/troubleshooting-guide/corrupted-response.md b/docs-apitesting/troubleshooting-guide/corrupted-response.md
old mode 100644
new mode 100755
index 1b14d5c6..99f6f1b0
--- a/docs-apitesting/troubleshooting-guide/corrupted-response.md
+++ b/docs-apitesting/troubleshooting-guide/corrupted-response.md
@@ -3,7 +3,7 @@ title: Corrupted Response due to HTTP compression
 page_title: Corrupted Response due to HTTP compression
 description: "Progress® Test Studio® for APIs - Troubleshooting guide - Corrupted response due to HTTP compression"
 position: 2
-publish: true
+published: true
 ---
 
 # Corrupted Response due to HTTP compression
diff --git a/docs-apitesting/troubleshooting-guide/no-internet-connection.md b/docs-apitesting/troubleshooting-guide/no-internet-connection.md
old mode 100644
new mode 100755
index 3cd55c1b..9fd3b8a7
--- a/docs-apitesting/troubleshooting-guide/no-internet-connection.md
+++ b/docs-apitesting/troubleshooting-guide/no-internet-connection.md
@@ -4,7 +4,7 @@ page_title: No Internet Connection
 description: "Progress® Test Studio® for APIs - Troubleshooting guide - No Internet Connection"
 previous_url: /troubleshooting-guide/deregister-proxy
 position: 3
-publish: true
+published: true
 ---
 # No Internet Connection
 
diff --git a/docs-apitesting/troubleshooting-guide/no-test-execution-output.md b/docs-apitesting/troubleshooting-guide/no-test-execution-output.md
old mode 100644
new mode 100755
index 2c430084..078b6321
--- a/docs-apitesting/troubleshooting-guide/no-test-execution-output.md
+++ b/docs-apitesting/troubleshooting-guide/no-test-execution-output.md
@@ -3,7 +3,7 @@ title: No Test Execution Output
 page_title: No Test Execution Output
 description: "Progress® Test Studio® for APIs - Troubleshooting guide - No Test Execution Output"
 position: 1
-publish: true
+published: true
 ---
 # No Test Execution Output
 
diff --git a/docs-apitesting/troubleshooting-guide/target-wrong-dll-version.md b/docs-apitesting/troubleshooting-guide/target-wrong-dll-version.md
old mode 100644
new mode 100755
index af51602d..539e9390
--- a/docs-apitesting/troubleshooting-guide/target-wrong-dll-version.md
+++ b/docs-apitesting/troubleshooting-guide/target-wrong-dll-version.md
@@ -3,7 +3,7 @@ title: Targeting Wrong API Framework DLL Version After Upgrade
 page_title: Targeting Wrong API Framework DLL Version After Upgrade
 description: "Progress® Test Studio® for APIs - Troubleshooting guide - Targeting Wrong API Framework DLL Version After Upgrade. Error 'Could not load file or assembly 'Telerik.ApiTesting.Framework, Version=' or one of its dependencies. The system cannot find the file specified. Die Datei oder Assembly 'Telerik.ApiTesting.Framework, Version=' oder eine Abhängigkeit davon wurde nicht gefunden. Das System kann die angegebene Datei nicht finden."
 position: 4
-publish: true
+published: true
 ---
 # Targeting Wrong API Framework DLL Version After Upgrade
 
diff --git a/docs-apitesting/web.config b/docs-apitesting/web.config
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/README.md b/docs-teststudiodev/README.md
index 1456f092..1488c64b 100644
--- a/docs-teststudiodev/README.md
+++ b/docs-teststudiodev/README.md
@@ -1,6 +1,6 @@
 ---
 title: Kendo UI Documentation Repo
-publish: false
+published: false
 ---
 
 # Kendo UI Public Documentation
diff --git a/docs-teststudiodev/advanced-topics/ci/execute-test-with-vstest.md b/docs-teststudiodev/advanced-topics/ci/execute-test-with-vstest.md
index 8f1ca978..5c44b94c 100644
--- a/docs-teststudiodev/advanced-topics/ci/execute-test-with-vstest.md
+++ b/docs-teststudiodev/advanced-topics/ci/execute-test-with-vstest.md
@@ -4,7 +4,7 @@ page_title: Execute Test Studio Test with VSTestConsole.exe - Test Studio Dev Do
 description: Execute Test Studio Test with VSTestConsole.exe 
 position: 10
 ---
-# Execute Test Studio Tests with VSTestConsole.exe #
+# Execute Test Studio Tests with VSTestConsole.exe
 
 To be able to execute Test Studio tests with the Visual Studio default test runner there are few requirements to set in advance. These are described below:
 
@@ -14,11 +14,11 @@ To be able to execute Test Studio tests with the Visual Studio default test runn
 
 3.There are two variables you have to set before executing Test Studio tests - ***TS_PROJECT_PATH*** and ***TS_DLL_PATH***. Project path is the folder which contains the Settings.aiis file. Dll path is the folder which contains the built project dll. 
 
-```
+````
 set TS_PROJECT_PATH=C:\Visual Studio 2015\Projects\TestStudioProject11\TestStudioProject11
 
 set TS_DLL_PATH=C:\Visual Studio 2015\Projects\TestStudioProject11\TestStudioProject11\bin\Debug\TestStudioProject11.dll
-```
+````
 
 > __Note!__ The variables are set for this instance of the Developer Command Prompt. By each next start of the command prompt the variables need to be set again. Therefore these need to be set in the build tasks in __CI environment__ prior the task to execute the test.
 
@@ -28,6 +28,6 @@ The TestAdapter dll will be in any of the sub-folders in the Visual Studio Exten
 
 Below you may find a sample command to execute a Test Studio test with the VSTestConsole.exe after the TS\_PROJECT\_PATH and TS\_DLL\_PATH variables are set for the current instance of the VS Developer Command Prompt:
 
-```
+````
 C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console "C:\Visual Studio 2015\Projects\TestStudioProject11\TestStudioProject11\Parent.tstest" /TestAdapterPath:"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\Extensions\t1fos0ab.vkx"
-```
+````
diff --git a/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig1.png b/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig2.png b/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig3.png b/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig4.png b/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig5.png b/docs-teststudiodev/advanced-topics/ci/images/ciplugin/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig10.png b/docs-teststudiodev/advanced-topics/ci/images/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig11.png b/docs-teststudiodev/advanced-topics/ci/images/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig12.png b/docs-teststudiodev/advanced-topics/ci/images/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig13.png b/docs-teststudiodev/advanced-topics/ci/images/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig14.png b/docs-teststudiodev/advanced-topics/ci/images/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig2.png b/docs-teststudiodev/advanced-topics/ci/images/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig3.png b/docs-teststudiodev/advanced-topics/ci/images/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig4.png b/docs-teststudiodev/advanced-topics/ci/images/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/fig9.png b/docs-teststudiodev/advanced-topics/ci/images/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig1.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig2.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig3.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig4.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig5.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig6.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig7.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig8.png b/docs-teststudiodev/advanced-topics/ci/images/tfs2017/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/EmptyBuildDefinition.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/EmptyBuildDefinition.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig2.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig3.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig4.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig5.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig6.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig7.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig8.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig9.png b/docs-teststudiodev/advanced-topics/ci/images/vstservice/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/ci/jenkins-ci-plugin.md b/docs-teststudiodev/advanced-topics/ci/jenkins-ci-plugin.md
index 4b8a789c..21c52a96 100644
--- a/docs-teststudiodev/advanced-topics/ci/jenkins-ci-plugin.md
+++ b/docs-teststudiodev/advanced-topics/ci/jenkins-ci-plugin.md
@@ -10,34 +10,29 @@ The Test Studio Plugin allows you to build and execute Test Studio tests and tes
 
 >The Test Studio Plugin supports Test Studio projects only.
 
-1.Install the Jenkins CI server to run as a Java application (instead of running it as a Windows service).
+1. Install the Jenkins CI server to run as a Java application (instead of running it as a Windows service).
 
-2.Install the Test Studio Plugin - download it <a href="/downloads/Jenkins_Plugin_TeststudioDev.zip" target="_blank">here</a> and add it to the Plugin folder of the Jenkins server installation or download it from the jenkins plugin marketplace.
+2. Install the Test Studio Plugin - download it <a href="/downloads/Jenkins_Plugin_TeststudioDev.zip" target="_blank">here</a> and add it to the Plugin folder of the Jenkins server installation or download it from the jenkins plugin marketplace.
 
-3.Create a freestyle project. Create an item and select 'Build a freestyle project'.
+3. Create a freestyle project. Create an item and select 'Build a freestyle project'.
 
-![Freestyle project][2]
+![Freestyle project](images/ciplugin/fig2.png)
 
-4.Add a Test Studio runner configuration build step. Under the 'Add build step menu' section select 'Test Studio runner configuration'.
+4. Add a Test Studio runner configuration build step. Under the 'Add build step menu' section select 'Test Studio runner configuration'.
 
-![TS Plugin build step][3]
+![TS Plugin build step](images/ciplugin/fig3.png)
 
-5.Input the full path to ArtOfTest.Runner.exe. The default path to find the Test Runner executable is C:\Program Files (x86)\Progress\Test Studio\Bin.
+5. Input the full path to ArtOfTest.Runner.exe. The default path to find the Test Runner executable is C:\Program Files (x86)\Progress\Test Studio\Bin.
 
-6.Specify the test or test list to execute using the absolute path to the file in the Jenkins CI workspace or its relative to the workspace path.
+6. Specify the test or test list to execute using the absolute path to the file in the Jenkins CI workspace or its relative to the workspace path.
 
 The *project root folder* and *settings file* fields accept relative path to the Jenkins job workspace only.
 
-![Build step arguments][4]
+![Build step arguments](images/ciplugin/fig4.png)
 
-7.TestStudio test as junit test. If enabled, in the test result, test studio tests will be represented as junit tests. Otherwise, test steps from the test studio result will be represented as junit tests.
+7. TestStudio test as junit test. If enabled, in the test result, test studio tests will be represented as junit tests. Otherwise, test steps from the test studio result will be represented as junit tests.
 
-![Convert to JUnit][5]
+![Convert to JUnit](images/ciplugin/fig5.png)
 
 Your test execution step is now ready to save and run.
 
-[1]: images/ciplugin/fig1.png
-[2]: images/ciplugin/fig2.png
-[3]: images/ciplugin/fig3.png
-[4]: images/ciplugin/fig4.png
-[5]: images/ciplugin/fig5.png
\ No newline at end of file
diff --git a/docs-teststudiodev/advanced-topics/ci/jenkins-ci.md b/docs-teststudiodev/advanced-topics/ci/jenkins-ci.md
index 81aa9fad..f33b18c9 100644
--- a/docs-teststudiodev/advanced-topics/ci/jenkins-ci.md
+++ b/docs-teststudiodev/advanced-topics/ci/jenkins-ci.md
@@ -8,47 +8,47 @@ position: 1
 
 Build and execute Test Studio tests in Jenkins CI by following these steps:
 
-1.Install the Java Web Archive (.war) for Jenkins CI. Test Studio requires the Java Web Archive version to run properly. If Jenkins runs as a service, desktop actions for functional UI tests will fail (there is no desktop interaction).
+1. Install the Java Web Archive (.war) for Jenkins CI. Test Studio requires the Java Web Archive version to run properly. If Jenkins runs as a service, desktop actions for functional UI tests will fail (there is no desktop interaction).
 
-2.Create a free-style software project. Create a job and select 'Build a free-style software project'.
+2. Create a free-style software project. Create a job and select 'Build a free-style software project'.
 
-![Free-style software project][1]
+![Free-style software project](images/fig2.png)
 
-3.Add a Windows batch command build step. Under the 'Add build step menu,' select 'Execute Windows batch command'. You can also use any other valid way that will allow you to start a windows process.
+3. Add a Windows batch command build step. Under the 'Add build step menu,' select 'Execute Windows batch command'. You can also use any other valid way that will allow you to start a windows process.
 
-![Command build step][2]
+![Command build step](images/fig3.png)
 
-4.Input ArtOfTest.Runner command line command to execute tests. Under 'Execute Windows batch command', input the ArtOfTest.Runner command to execute your test or test list, including <a href="/features/cli-runner" target="_blank">full path to ArtOfTest.Runner.exe and appropriate arguments</a>.
+4. Input ArtOfTest.Runner command line command to execute tests. Under 'Execute Windows batch command', input the ArtOfTest.Runner command to execute your test or test list, including <a href="/features/cli-runner" target="_blank">full path to ArtOfTest.Runner.exe and appropriate arguments</a>.
 
-![Arguments][3]
+![Arguments](images/fig4.png)
 
 Your test execution step is now ready to save and run.
 
 ## Attach the results files to the Job
 
-1.Add "**out**" parameter in the batch command. It should point to the defaultrkspace **(%WORKSPACE%\%JOB_NAME%%BUILD_NUMBER%**) so the results files are outputted in a folder with an unique name (Job Name + Build Number) and set the result output to be in junit format.
+1. Add "**out**" parameter in the batch command. It should point to the defaultrkspace **(%WORKSPACE%\%JOB_NAME%%BUILD_NUMBER%**) so the results files are outputted in a folder with an unique name (Job Name + Build Number) and set the result output to be in junit format.
 
-![Out parameter][4]
+![Out parameter](images/fig9.png)
 
-2.Add a post-build action of type "**Archive the artifacts**".
+2. Add a post-build action of type "**Archive the artifacts**".
 
-![Archive the artifacts][5]
+![Archive the artifacts](images/fig10.png)
 
-3.Type *${JOB_NAME}${BUILD_NUMBER}\\*** in the "**Files to archive**" field so all the results files can be taken.
+3. Type *${JOB_NAME}${BUILD_NUMBER}\\*** in the "**Files to archive**" field so all the results files can be taken.
 
-![Files to archive][6]
+![Files to archive](images/fig11.png)
 
-4.After the build completion all the results files will be attached to it.
+4. After the build completion all the results files will be attached to it.
 
-![Files to archive][7]
+![Files to archive](images/fig12.png)
 
-5.Click **Build Artifacts** and download the files in a *.zip file (it will keep the folder structure) and open the **.aiiresult* file.
+5. Click **Build Artifacts** and download the files in a *.zip file (it will keep the folder structure) and open the **.aiiresult* file.
 
-![Save in zip file][8]
+![Save in zip file](images/fig13.png)
 
-6.You can also review a result summary directly from the build page (if there are junit formatted results).
+6. You can also review a result summary directly from the build page (if there are junit formatted results).
 
-![Check the junit results][9]
+![Check the junit results](images/fig14.png)
 
 Your Jenkins CI build is now ready to run.
 
@@ -68,12 +68,4 @@ or
 
 **javaws http://$HOST:$PORT/computer/$SLAVEMACHE/slave-agent.jnlp**
 
-[1]: images/fig2.png
-[2]: images/fig3.png
-[3]: images/fig4.png
-[4]: images/fig9.png
-[5]: images/fig10.png
-[6]: images/fig11.png
-[7]: images/fig12.png
-[8]: images/fig13.png
-[9]: images/fig14.png
+
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/data-driven-image-verification.md b/docs-teststudiodev/advanced-topics/data-driven-testing/data-driven-image-verification.md
index 7aea3400..c86917d2 100644
--- a/docs-teststudiodev/advanced-topics/data-driven-testing/data-driven-image-verification.md
+++ b/docs-teststudiodev/advanced-topics/data-driven-testing/data-driven-image-verification.md
@@ -4,14 +4,11 @@ page_title: Data Driven Image Verification - Test Studio Dev Documentation
 description: How to data drive image verification in Test Studio Dev
 position: 3
 ---
-# Data Driven Image Verification #
+# Data Driven Image Verification
 
 To data bind an <a href="/features/recorder/verifications/image-verification" target="_blank">image verification</a> step certain actions have to be performed. An approach to this scenario is to have previously stored histograms of the image element to which verification should be bonded. Then in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> the verification has to be managed as it is given in the sample below:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // get an image of MyImage element
     System.Drawing.Bitmap bitmap = Pages.MyPage.MyImage.Capture();
 
@@ -36,12 +33,8 @@ To data bind an <a href="/features/recorder/verifications/image-verification" ta
 
     // Assert statement 
     ArtOfTest.Common.UnitTesting.Assert.IsTrue(tolerance >= compareValue);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim bitmap As System.Drawing.Bitmap = Pages.MyPage.MyImage.Capture()
 
     Dim histogram As ArtOfTest.Common.Histogram = ArtOfTest.Common.Histogram.FromBitmap(bitmap)
@@ -59,8 +52,7 @@ To data bind an <a href="/features/recorder/verifications/image-verification" ta
     Dim tolerance As Double = 10.0
 
     ArtOfTest.Common.UnitTesting.Assert.IsTrue(tolerance >= compareValue)
-    {{endregion}}
-
+````
 To complete this scenario using the provided sample:
 
 - *System.Drawings* .NET assembly has to be referenced in the project
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig1.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig2.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig3.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig4.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/oracle-db-example/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/sql-database-example/fig1.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/sql-database-example/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/images/sql-database-example/fig2.png b/docs-teststudiodev/advanced-topics/data-driven-testing/images/sql-database-example/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/oracle-db-example.md b/docs-teststudiodev/advanced-topics/data-driven-testing/oracle-db-example.md
index a8f558aa..10646ac6 100644
--- a/docs-teststudiodev/advanced-topics/data-driven-testing/oracle-db-example.md
+++ b/docs-teststudiodev/advanced-topics/data-driven-testing/oracle-db-example.md
@@ -12,39 +12,35 @@ This example is completed using an **Oracle Database Express** (Oracle Database
 
 Next step is to create a database in order to use it for data binding. One way to do it is by using <a href="http://www.oracle.com/technetwork/developer-tools/sql-developer/overview/index.html" target="_blank">Oracle SQL Developer</a>. On the following image there are SQL queries that will create table **Employees** and insert there two rows of data.
 
-![Create Table][1]
+![Create Table](images/oracle-db-example/fig1.png)
 
 Once the table is created it is possible to connect to it and use it for data-driven testing:
 
-1.&nbsp; Click on **Add** from **Data Sources** menu: 
+1. Click on **Add** from **Data Sources** menu: 
 
-![Create Table][4]
+    ![Create Table](images/oracle-db-example/fig4.png)
 
-2.&nbsp; In the **Create new data source** dialog - for **Data Source Types** choose **Database**
+2. In the **Create new data source** dialog - for **Data Source Types** choose **Database**
 
-![Create New Data Source][2]
+    ![Create New Data Source](images/oracle-db-example/fig2.png)
 
-3.&nbsp; For **Provider**, select **Oracle Data Provider for .NET**
+3. For **Provider**, select **Oracle Data Provider for .NET**
 
-4.&nbsp; Here's an example for **Connection String**:
+4. Here's an example for **Connection String**:
 
-```
-Data Source=XE;User Id=SYSTEM;Password=pass;
-```
+    ````
+    Data Source=XE;User Id=SYSTEM;Password=pass;
+    ````
 
 It is possible to create many different connection strings. See <a href="https://www.connectionstrings.com/oracle/" target="_blank">here</a> for more examples.
 
-5.&nbsp; Customize the **Friendly Name** as desired.
+5. Customize the **Friendly Name** as desired.
 
-6.&nbsp; Click **Create** and the new data source should appear in the Data Sources list.
+6. Click **Create** and the new data source should appear in the Data Sources list.
 
 <br/>
 
 When a <a href="/features/data-driven-testing/bind-test-data-source" target="_blank">test is bound</a> to this data base the table to be used will be specified:
 
-![Bind To Table][3]
+![Bind To Table](images/oracle-db-example/fig3.png)
 
-[1]: images/oracle-db-example/fig1.png
-[2]: images/oracle-db-example/fig2.png
-[3]: images/oracle-db-example/fig3.png
-[4]: images/oracle-db-example/fig4.png
\ No newline at end of file
diff --git a/docs-teststudiodev/advanced-topics/data-driven-testing/sql-database-example.md b/docs-teststudiodev/advanced-topics/data-driven-testing/sql-database-example.md
index f2613227..544b04b3 100644
--- a/docs-teststudiodev/advanced-topics/data-driven-testing/sql-database-example.md
+++ b/docs-teststudiodev/advanced-topics/data-driven-testing/sql-database-example.md
@@ -10,32 +10,30 @@ Let's say we have a SQL Server with the name of **SQLEXPRESS**. We have to creat
 
 Let's create a database called **myFirstDB**:
 
-![MS Management Studio][1]
+![MS Management Studio](images/sql-database-example/fig1.png)
 
 Now we can connect to it and use it for data-driven testing.
 
-1.&nbsp; Load the **Create New DataSource** menu.
+1. Load the **Create New DataSource** menu.
 
-![Create New Data Source][2]
+    ![Create New Data Source](images/sql-database-example/fig2.png)
 
-2.&nbsp; Choose **Database**.
+2. Choose **Database**.
 
-3.&nbsp; For **Provider**, select **SqlClient Data Provider**.
+3. For **Provider**, select **SqlClient Data Provider**.
 
-4.&nbsp; Here's an example for **Connection String**:
+4. Here's an example for **Connection String**:
 
-```
-Data Source=MACHINENAME\SQLEXPRESS; Initial Catalog=myFirstDB; Integrated Security=true;
-```
+    ````
+    Data Source=MACHINENAME\SQLEXPRESS; Initial Catalog=myFirstDB; Integrated Security=true;
+    ````
 
-- Data Source is the name of the SQL Server.
-- Initial Catalog is the named of the Database.
+    - Data Source is the name of the SQL Server.
+    - Initial Catalog is the named of the Database.
 
-It is possible to use different connection strings. See <a href="https://www.connectionstrings.com/sql-server/" target="_blank">here</a> for more examples.
+    It is possible to use different connection strings. See <a href="https://www.connectionstrings.com/sql-server/" target="_blank">here</a> for more examples.
 
-5.&nbsp; Customize the **Friendly Name** as desired.
+5. Customize the **Friendly Name** as desired.
 
-6.&nbsp; Click on **Create** button and the new data source should appear in the Data Sources list.
+6. Click on **Create** button and the new data source should appear in the Data Sources list.
 
-[1]: images/sql-database-example/fig1.png
-[2]: images/sql-database-example/fig2.png
\ No newline at end of file
diff --git a/docs-teststudiodev/advanced-topics/elements/change-step-target-element.md b/docs-teststudiodev/advanced-topics/elements/change-step-target-element.md
index 72c0dba9..f112c5df 100644
--- a/docs-teststudiodev/advanced-topics/elements/change-step-target-element.md
+++ b/docs-teststudiodev/advanced-topics/elements/change-step-target-element.md
@@ -10,19 +10,18 @@ If a test step targets an incorrect element, or if you <a href="/features/record
 
 To choose a different target element for a specific test step from the Elements Repository:
 
-1.&nbsp; Select a step from the **Test Steps Panel**.
+1. Select a step from the **Test Steps Panel**.
 
-2.&nbsp; In the Test Step **Properties** pane, click the **Primary Target** property.
+2. In the Test Step **Properties** pane, click the **Primary Target** property.
 
-3.&nbsp; Click the '...' button.
+3. Click the '...' button.
 
-![Click ... button][1]
+    ![Click ... button](images/change-step-target-element/fig1.png)
 
-4.&nbsp; In the **Project Elements Selector,** click the new target element for the test step.
+4. In the **Project Elements Selector,** click the new target element for the test step.
 
-5.&nbsp; Click **Select**.
+5. Click **Select**.
+
+    ![Select](images/change-step-target-element/fig2.png)
 
-![Select][2]
 
-[1]: images/change-step-target-element/fig1.png
-[2]: images/change-step-target-element/fig2.png
diff --git a/docs-teststudiodev/advanced-topics/elements/element-repository.md b/docs-teststudiodev/advanced-topics/elements/element-repository.md
index 36be2762..89bfc1ef 100644
--- a/docs-teststudiodev/advanced-topics/elements/element-repository.md
+++ b/docs-teststudiodev/advanced-topics/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).
\ No newline at end of file
diff --git a/docs-teststudiodev/advanced-topics/elements/images/change-step-target-element/fig1.png b/docs-teststudiodev/advanced-topics/elements/images/change-step-target-element/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/change-step-target-element/fig2.png b/docs-teststudiodev/advanced-topics/elements/images/change-step-target-element/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig1.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig10.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig11.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig2.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig3.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig4.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig5.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig6.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig7.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig8.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig9.png b/docs-teststudiodev/advanced-topics/elements/images/merge-page-nodes/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig1.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig10.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig11.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig2.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig3.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig4.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig5.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig6.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig7.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig8.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig9.png b/docs-teststudiodev/advanced-topics/elements/images/using-chained-find-expressions/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig14.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig15.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig15.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig16.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig16.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig17.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig17.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig18.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig18.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig19.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig19.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig20.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig20.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig21.png b/docs-teststudiodev/advanced-topics/elements/images/using-data-driven-find-expressions/fig21.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/elements/using-chained-find-expressions.md b/docs-teststudiodev/advanced-topics/elements/using-chained-find-expressions.md
index 60afd627..921562ea 100644
--- a/docs-teststudiodev/advanced-topics/elements/using-chained-find-expressions.md
+++ b/docs-teststudiodev/advanced-topics/elements/using-chained-find-expressions.md
@@ -10,68 +10,57 @@ In most cases, Test Studio’s default find logic can dependably find target ele
 
 One type of controls that pose a challenge for Test Studio’s default find logic are hierarchical controls such as tree views.
 
-![TreeView][1]
+![TreeView](images/using-chained-find-expressions/fig1.png)
 
 In these and other situations, the user is less concerned with the sequence of the items in the control, and more with their position relative to one another.
 
 However, Test Studio will usually record find logic based on the element’s sequential position within the control.
 
-![FindExpression][2]
+![FindExpression](images/using-chained-find-expressions/fig2.png)
 
 This is a job for a chained find expression. A chained find expression will locate the first or parent element, then look below it in the DOM for the target element.
 
-1.First, select the target element in the **Elements Explorer** and select Edit in Live from the context menu.
+1. First, select the target element in the **Elements Explorer** and select Edit in Live from the context menu.
 
-![Edit in Live][3]
+    ![Edit in Live](images/using-chained-find-expressions/fig3.png)
 
-This will open the Find Element menu. You can choose <a href="/features/elements-explorer/find-element" target="_blank">how to locate the element</a>. Once you have located the element, you can change the find settings.
+    This will open the Find Element menu. You can choose <a href="/features/elements-explorer/find-element" target="_blank">how to locate the element</a>. Once you have located the element, you can change the find settings.
 
-![Find settings][4]
+    ![Find settings](images/using-chained-find-expressions/fig4.png)
 
-For many tree nodes and other hierarchical controls, Test Studio will initially record a chained find expression. You can identify this by the way the filter(s) for the parent element (1) is connected to the filter(s) for the target element (2) by a blue diagonal arrow. If not, you can chain a new set of filters to an existing set by clicking the blue arrow.
+    For many tree nodes and other hierarchical controls, Test Studio will initially record a chained find expression. You can identify this by the way the filter(s) for the parent element (1) is connected to the filter(s) for the target element (2) by a blue diagonal arrow. If not, you can chain a new set of filters to an existing set by clicking the blue arrow.
 
-2.Change the find logic to reflect the desired find strategy. The goal is to accurately identify the parent element, then give a find logic that is accurate for the target element, given it is beneath the parent element in the DOM.
+2. Change the find logic to reflect the desired find strategy. The goal is to accurately identify the parent element, then give a find logic that is accurate for the target element, given it is beneath the parent element in the DOM.
 
-3.You can manually edit the filter options, or replace one of the rules with a suggested filter from the left side.
+3. You can manually edit the filter options, or replace one of the rules with a suggested filter from the left side.
 
-![Change find settings][5]
+![Change find settings](images/using-chained-find-expressions/fig5.png)
 
 Selecting a suggestion from the left will add it to the existing filter(s) for the selected element in the chained find.
 
-![Add new filter][6]
+![Add new filter](images/using-chained-find-expressions/fig6.png)
 
 Once you have added  a new filter, you can remove the old sequential one.
 
-![Delete filter][7]
+![Delete filter](images/using-chained-find-expressions/fig7.png)
 
 The result is a working chained find expression. Test Studio will look for the parent element (1) first, then find the target element (2).
 
-![New expression][8]
+![New expression](images/using-chained-find-expressions/fig8.png)
 
 You can confirm that your chained find works by using the **Validate** button.
 
-![Validate][9]
+![Validate](images/using-chained-find-expressions/fig9.png)
 
 Once you validate and save the new find logic, you can select the element in the Elements Explorer and locate it in the DOM.
 
-![Locate in DOM][10]
+![Locate in DOM](images/using-chained-find-expressions/fig10.png)
 
 This can help you see how the chained find expression will work against the DOM. The target element highlighted should be beneath the parent element in the DOM hierarchy.
 
-![Locate in DOM][11]
+![Locate in DOM](images/using-chained-find-expressions/fig11.png)
 
 __See Also:__
 
 * <a href="http://www.telerik.com/videos/teststudio/test-studio---flexible-locators-" target="_blank">Watch a video tutorial on chained find expressions</a>
 
-[1]: images/using-chained-find-expressions/fig1.png
-[2]: images/using-chained-find-expressions/fig2.png
-[3]: images/using-chained-find-expressions/fig3.png
-[4]: images/using-chained-find-expressions/fig4.png
-[5]: images/using-chained-find-expressions/fig5.png
-[6]: images/using-chained-find-expressions/fig6.png
-[7]: images/using-chained-find-expressions/fig7.png
-[8]: images/using-chained-find-expressions/fig8.png
-[9]: images/using-chained-find-expressions/fig9.png
-[10]: images/using-chained-find-expressions/fig10.png
-[11]: images/using-chained-find-expressions/fig11.png
\ No newline at end of file
diff --git a/docs-teststudiodev/advanced-topics/installation/images/delete-key.png b/docs-teststudiodev/advanced-topics/installation/images/delete-key.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/installation/images/vs2017installation.png b/docs-teststudiodev/advanced-topics/installation/images/vs2017installation.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/installation/images/vs2022install.png b/docs-teststudiodev/advanced-topics/installation/images/vs2022install.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/installation/re-activating-your-license.md b/docs-teststudiodev/advanced-topics/installation/re-activating-your-license.md
index ac618f3d..a5a457ec 100644
--- a/docs-teststudiodev/advanced-topics/installation/re-activating-your-license.md
+++ b/docs-teststudiodev/advanced-topics/installation/re-activating-your-license.md
@@ -4,16 +4,16 @@ page_title: Re-activating Your License - Test Studio Dev Documentation
 description: How to re-activate your Test Studio Dev license 
 position: 2
 ---
-# Re-activating your License #
+# Re-activating your License
 
 My machine was freshly imaged or replaced and I need to re-activate my license on the new machine. When I try to re-activate my new machine I have 0 seats available. To be able to generate new license key corresponding to the fresh machine follow the below steps:
 
-1.Log on to your <a href="http://www.telerik.com" target="_blank">Telerik.com</a> account.
+1. Log on to your <a href="http://www.telerik.com" target="_blank">Telerik.com</a> account.
 
-2.Navigate to __Test Studio__ product.
+2. Navigate to __Test Studio__ product.
 
-3.<a href="https://www.telerik.com/account/your-products/testing-tools-manage-license-keys" target="_blank">Manage Test Studio Activation Keys</a>.
+3. <a href="https://www.telerik.com/account/your-products/testing-tools-manage-license-keys" target="_blank">Manage Test Studio Activation Keys</a>.
 
-4.Find and delete your old key. This will free up a slot allowing to activate your new machine.
+4. Find and delete your old key. This will free up a slot allowing to activate your new machine.
 
 ![Delete key](images/delete-key.png)
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig1.png b/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig2.png b/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig3.png b/docs-teststudiodev/advanced-topics/project-configuration/images/register-certificate/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/add-existing-item.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/add-existing-item.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig1.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig2.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig3.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig4.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/run-settings-vs22.png b/docs-teststudiodev/advanced-topics/project-configuration/images/test-explorer-settings/run-settings-vs22.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/project-configuration/register-certificate.md b/docs-teststudiodev/advanced-topics/project-configuration/register-certificate.md
index 8c7f67db..3d3e4dcc 100644
--- a/docs-teststudiodev/advanced-topics/project-configuration/register-certificate.md
+++ b/docs-teststudiodev/advanced-topics/project-configuration/register-certificate.md
@@ -12,25 +12,22 @@ If the web application you are automating is accessible via secure HTTP (HTTPS),
 
 I'm working on a web application accessible via secure HTTP (HTTPS) with a URL like this `https://www.something.com`. I encounter certificate related warnings when the Test Studio recorder or runner is attached to the browser. I do not see this warning when the recorder or runner is not attached.
 
-![Certificate][1]
+![Certificate](images/register-certificate/fig1.png)
 
-[1]: images/register-certificate/fig1.png
-[2]: images/register-certificate/fig2.png
-[3]: images/register-certificate/fig3.png
 
 ## Solution
 
 This is expected behavior and it's related to the way Test Studio Dev hooks into the browser. If this warning is a problem for your test automation, use the **Register certificate** for https connection feature:
 
-1.Open the <a href="/features/project-settings/overview" target="_blank">Project Settings</a> and go to the General section.
+1. Open the <a href="/features/project-settings/overview" target="_blank">Project Settings</a> and go to the General section.
 
-2.Click **Register certificate for https connection** under *Connection settings*.
+2. Click **Register certificate for https connection** under *Connection settings*.
 
-![Register certificate][2]
+    ![Register certificate](images/register-certificate/fig2.png)
 
-3.You are prompted to install a certificate. Click Yes. After installing the certificate, you will no longer receive the certificate-related warning when automating your application with Test Studio.
+3. You are prompted to install a certificate. Click Yes. After installing the certificate, you will no longer receive the certificate-related warning when automating your application with Test Studio.
 
-![Security Warning][3]
+![Security Warning](images/register-certificate/fig3.png)
 
 > Ensure that installing the certificate does not violate your company's security policies. </br>
 
@@ -40,6 +37,6 @@ This is expected behavior and it's related to the way Test Studio Dev hooks into
 
 Open a command prompt and navigate to the __Test Studio Dev__ installation directory `C:\Program Files (x86)\Progress\Test Studio\Bin`. Then enter the following command to install the security certificate:
 
-```
+````
 ArtOfTest.WebAii.HttpProxy.exe InstallCertificate
-```
+````
diff --git a/docs-teststudiodev/advanced-topics/recording/images/base-url/fig1.png b/docs-teststudiodev/advanced-topics/recording/images/base-url/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/recording/images/base-url/fig2.png b/docs-teststudiodev/advanced-topics/recording/images/base-url/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/advanced-topics/recording/images/base-url/fig3.png b/docs-teststudiodev/advanced-topics/recording/images/base-url/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/asp-net-host-server.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/asp-net-host-server.md
index 6a4c0c7b..f89c2905 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/asp-net-host-server.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/asp-net-host-server.md
@@ -4,7 +4,7 @@ page_title: Asp.NET Host Server
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Using Asp.Net In-Process Host Server#
+# Using Asp.Net In-Process Host Server
 
 Many of our customers have asked for a way to execute tests without the need for a browser. They wanted a light-weight, fast and agile execution that fits within their Continuous Integration Builds and works easily with 'CruiseControl.Net' or 'Visual Studio Team Foundation Server.' We enabled these scenarios with two areas of support:
 
@@ -18,11 +18,11 @@ 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:
 
-```ASP
+````ASP
 <%@ Page Language="C#" %>
  
 <!DOCTYPE htmlPUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
@@ -90,29 +90,27 @@ With all these in mind, let's look at an example that illustrates how we can ena
     </form>
 </body>
 </html>
-```
+````
 You can run this page using the Asp.Net InProc server by first setting the default browser to 'AspNetHost' and setting the physical location of the web application. For example, you can override these settings in your test initialization or set them in your .config file:
 
-```C#
+````C#
 // Set the default browser to be AspNetHost
 settings.DefaultBrowser = BrowserType.AspNetHost;
  
 // Set the location of the Asp.Net App
 settings.WebAppPhysicalPath = @"C:\MyAspNetApp\";
-```
- 
-
-```VB
+````
+````VB
 ' Set the default browser to be AspNetHost
 mysettings.DefaultBrowser = BrowserType.AspNetHost
  
 ' Set the location of the Asp.Net App
 mysettings.WebAppPhysicalPath = System.IO.Path.Combine(Globals.PATH_TO_PAGES, "AspNetApp")
-```
+````
 
 Next you can perform your automation in the same manner as you would for any other browser. For example:
 
-```C#
+````C#
 // Will initialize a new AspNetApplication object.
 Manager.LaunchNewBrowser();
  
@@ -174,10 +172,8 @@ Assert.IsTrue(label.InnerText.Contains(DateTime.Today.ToShortDateString()));
 Actions.Click(Find.ById("treeView1t1"));
 label.Refresh();
 Assert.IsTrue(label.InnerText.Contains("Node2"));
-```
- 
-
-```VB
+````
+````VB
 
 ' Will initialize a new AspNetApplication object.
 Manager.LaunchNewBrowser()
@@ -235,8 +231,8 @@ Assert.IsTrue(label.InnerText.Contains(DateTime.Today.ToShortDateString))
 Actions.Click(Find.ById("treeView1t1"))
 label.Refresh()
 Assert.IsTrue(label.InnerText.Contains("Node2"))
-```
+````
 
-##Debugging Page Requests##
+## Debugging Page Requests
 
 Given that these page requests are running in-process without any UI showing, it is sometimes difficult to see what exactly is being rendered. To make debugging scenarios easier, Telerik Testing Framework enables the option of rendering the responses from the Asp.Net In-Process server into an IE browser instance. To enable this debug mode, simply set the **Settings.EnableUILessRequestViewing** to True and an IE instance will launch and redirect a copy of all responses from the Asp.Net host to that instance so you can visually inspect the UI of the pages.
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/attribute-extensions.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/attribute-extensions.md
index e37e5b58..c6e57b4c 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/attribute-extensions.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/attribute-extensions.md
@@ -4,9 +4,9 @@ page_title: Attribute Extensions
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Unit Testing Attribute Extensions#
+# Unit Testing Attribute Extensions
 
-##What Are These Extensions?##
+## What Are These Extensions?
 
 Unit testing attribute extensions is one of the coolest features of the framework. They came about as we were reviewing automated unit test code for some of our customers and our own unit testing code for the framework. The things that became apparent after reviewing these automated tests were:
 
@@ -28,14 +28,14 @@ Attribute Extensions are test fixture attributes that can be used to decorate un
 
 * **DialogAttribute**: You use this attribute on test methods to define the Win32 pop-up dialogs you want monitored and define how you want them handled. If you have common dialogs that pop-up across your test methods, you can simply set this attribute on the test class and the dialog will be monitored and handled for all test methods contained in that test class.
 
-##Examples##
+## Examples
 
-###FindParamAttribute###
+### FindParamAttribute
 
 Let's start by taking few examples for FindParamAttribute. Assume we have an input textbox that we commonly access through out all the test methods in our Foo test class. Well, we can share this methods across all the test methods in 'foo' by setting that FindParam using FindParamAttribute on the test class like this:
 
 
-```C#
+````C#
 [TestClass]
 [FindParam("InputTxtbx", FindType.TagIndex, "input:0")]
 class Foo : BaseTest
@@ -60,10 +60,8 @@ class Foo : BaseTest
          Actions.SetText(Find.Elements["InputTxtbx"], "test2");
      }
 }
-```
- 
-
-```VB
+````
+````VB
 <TestClass(), _
 FindParam("InputTxtbx", FindType.TagIndex, "input:0")> _
 Public Class Foo
@@ -94,11 +92,11 @@ Public Class Foo
     End Sub
  
 End Class
-```
+````
 
 You can use 1-N FindParam attributes on your test class or test method. If you have elements that are shared across more than one test method, set these FindParam's on the test class, else simply set them on the test method. For example:
 
-```C#
+````C#
 [TestClass]
 [FindParam("InputTxtbx", FindType.TagIndex, "input:0")]
 class Foo : BaseTest
@@ -134,10 +132,8 @@ class Foo : BaseTest
          // here. Calling Find.Elements["CheckBx"], will throw an exception.
      }
 }
-```
- 
-
-```VB
+````
+````VB
 <TestClass(), _
 FindParam("InputTxtbx", FindType.TagIndex, "input:0")> _
 Public Class Foo
@@ -176,15 +172,15 @@ Public Class Foo
     End Sub
  
 End Class
-```
+````
 
-###FindParamAttributes and TestRegions###
+### FindParamAttributes and TestRegions
 
 FindParamAttributes can also be used with TestRegions when they are defined within an application. In this scenario, the FindParam needs to reflect an element search within a specific TestRegion. To tie a FindParamAttribute with a TestRegion, simply set the TestRegionId property of that FindParam on your test method or test class. Here is an example:
 
 FindParamAttributes can also be used with TestRegions when they are defined within an application. In this scenario, the FindParam needs to reflect an element search within a specific TestRegion. To tie a FindParamAttribute with a TestRegion, simply set the TestRegionId property of that FindParam on your test method or test class. Here is an example:
 
-```C#
+````C#
 
 [TestMethod]
 [Description("Illustrate how to use FindParamAttributes with TestRegion's")]
@@ -211,10 +207,8 @@ public void UsingFindParamAttributeWithTestRegion's()
      // Note: You can also use the FindParamAttribute(fileName) and scope all
      // the elements contained in file to a specific testregion.
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod(), _
 Description("Illustrate how to use FindParamAttributes with TestRegion's"), _
 FindParam("progtbl", FindType.TagIndex, "table:1"), _
@@ -238,13 +232,13 @@ Public Sub UsingFindParamAttributeWithTestRegions()
      ' the elements contained in the file to a specific testregion.
  
 End Sub
-```
+````
 
-###DialogAttribute###
+### DialogAttribute
 
 Dialog attribute is used similar to the FindParamAttribute but instead of defining how an element should be found, it defines how a dialog should be handled in addition to the dialog types to handle. Again these attributes can be shared across test methods by setting them on a test class or can be directly set on the test method that will cause the dialog to pop up. Here are few examples of some of the common dialogs:
 
-```C#
+````C#
 // ALERTS
 [TestMethod]
 [Dialog(DialogButton.OK)] // handle any alert dialogs in this test method
@@ -288,10 +282,8 @@ public void LogonDialogWithAttributes()
      // Navigate to a page that needs a logon
      ActiveBrowser.NavigateTo(http://www.test.com/pageneedinglogon.aspx);
 }
-```
- 
-
-```VB
+````
+````VB
 
 ' Alerts
 <TestMethod(), _
@@ -325,5 +317,5 @@ Dialog("<username>", "<password>", DialogButton.OK)> _
 Public Sub LogonDialogWithAttributes()
      ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>")
 End Sub
-```
+````
 **Note:** All examples shown above should work with NUnit 2.4 and higher and Visual Studio Team Test. In the samples above we simply used Visual Studio Team Test.
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/frames-support.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/frames-support.md
index d9491501..18790db9 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/frames-support.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/frames-support.md
@@ -4,7 +4,7 @@ page_title: Frames Support
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Frames Support#
+# Frames Support
 
 Telerik Testing Framework understands what Frames and IFrames are and includes built-in support to work with them. It automatically scans the webpage and locates all of the frames it contains and then adds them to the FramesCollection property of the Browser object.
  
@@ -15,29 +15,39 @@ Frames are treated just like another browser instance. In order to work with the
 	<th>Method</th><th>Parameter</th><th>Description</th>
 </tr>
 <tr>
-	<td>**Browser.Frames[string frameName]**</td>
-	<td>Takes a string that specifies the name of the frame. e.g. <frame src="t1.html" name="t1_frame"></td>
-	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
+<td>
+	
+**Browser.Frames[string frameName]**</td>
+<td>Takes a string that specifies the name of the frame. e.g. <frame src="t1.html" name="t1_frame"></td>
+<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames[int frameIndex]**</td>
+<td>
+	
+**Browser.Frames[int frameIndex]**</td>
 	<td>Takes an integer specifying which frame to get from the frame collection. Useful if you know ahead of time you want the second frame. e.g. ActiveBrowser.Frames[1]</td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Throws an error if the index value is out of range.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames[FrameInfo frameInfo]**</td>
-	<td>Takes a FrameInfo object that specifies the properties of the frame you want. Perhaps you want to locate a frame by its src property.</td>
-	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
+<td>
+	
+**Browser.Frames[FrameInfo frameInfo]**</td>
+<td>Takes a FrameInfo object that specifies the properties of the frame you want. Perhaps you want to locate a frame by its src property.</td>
+<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames.ById(string frameId)**</td>
-	<td>Takes a string that specifies the ID of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
-	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
+<td>
+	
+**Browser.Frames.ById(string frameId)**</td>
+<td>Takes a string that specifies the ID of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
+<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
 </tr>
 <tr>
-	<td>**Browser.Frames.BySrc(string src)**</td>
-	<td>Takes a string that specifies the source of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
-	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
+<td>
+	
+**Browser.Frames.BySrc(string src)**</td>
+<td>Takes a string that specifies the source of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
+<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
 </tr>
 <table>
 
@@ -45,7 +55,7 @@ Telerik Testing Framework allows users to access frames and perform automation a
  
 Let's take an example that demonstrates this support. Assuming we have the following simple web page:
 
-```HTML
+````HTML
 <HTML>
 <HEAD><TITLE>THE I HATE FRAMES PAGE</TITLE></HEAD>
 <FRAMESET COLS="33%,33%">
@@ -53,11 +63,11 @@ Let's take an example that demonstrates this support. Assuming we have the follo
     <FRAMESRC="..\BrowserActions.htm" id="T2_Frame">
 </FRAMESET>
 </HTML>
-```
+````
 
 To access the 't1.html' frame elements and perform actions against it, first I need to navigate to the page, then I need to access the frame that contains that page from the 'Frames[]' collection as follows:
 
-```C#
+````C#
 // Launch an instance of the browser
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, true);
    
@@ -80,10 +90,8 @@ t1_frame.Actions.Click(toggleOn);
    
 // Click the toggleoff button
 t2_frame.Actions.Click(toggleOff);
-```
- 
-
-```VB
+````
+````VB
 ' Launch an instance of the browser
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, True)
  
@@ -106,10 +114,10 @@ t1_frame.Actions.Click(toggleOn)
  
 ' Click the toggleoff button
 t2_frame.Actions.Click(toggleOff)
-```
+````
 
-At this point, the 't1_frame' object is just like any other Browser object. You can use the Find.Byxxx/Actions objects to find elements/execute actions in the document or execute any of the browser actions like 'NavigateTo' or 'Refresh()', 'GoBack()', etc.
+At this point, the 't1_frame' object is just like any other Browser object. You can use the Find.Byxxx/Actions objects to find elements/execute actions in the document or execute any of the browser actions like `NavigateTo` or `Refresh()`, `GoBack()`, etc.
  
-###Notes about Frames support:###
+### Notes about Frames support:
 
-The Frames collection supports two methods that can be used to easily wait on all frames to be ready or to refresh all the DOM trees within these frames. The methods are : 'ActiveBrowser.Frames.RefreshAllDomTrees()' & 'ActiveBrowser.Frames.WaitAllUntilReady()'. You can use these methods if you are doing actions that affect all frames in the page and you want to wait for these actions across all frames all at once
\ No newline at end of file
+The Frames collection supports two methods that can be used to easily wait on all frames to be ready or to refresh all the DOM trees within these frames. The methods are : `ActiveBrowser.Frames.RefreshAllDomTrees()` & `ActiveBrowser.Frames.WaitAllUntilReady()`. You can use these methods if you are doing actions that affect all frames in the page and you want to wait for these actions across all frames all at once
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
index 79e23cea..87e2b389 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
@@ -4,11 +4,11 @@ page_title: Alert Dialogs
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#Handling Alert Dialogs#
+# Handling Alert Dialogs
 
 With Alerts, you only need to define how the alert should be handled. Your options for alert handling are: DialogButton.OK or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add an alert dialog to monitor
 Manager.DialogMonitor.AddDialog(new AlertDialog(ActiveBrowser, DialogButton.OK));
 
@@ -20,7 +20,7 @@ Manager.DialogMonitor.Start();
 Actions.InvokeScript("InvokeAlert()");
 
 // The dialog will now be automatically handled transparently in the background without any help from the test code.
-```
+````
 
  ```VB
 ' Add an alert dialog to monitor
@@ -34,7 +34,7 @@ Manager.DialogMonitor.Start()
 Actions.InvokeScript("InvokeAlert()")
 
 ' The dialog will now be automatically handled transparently in the background without any help from the test code.
-```
+````
 > **To compile the above code include the following using:**
 >
 > using ArtOfTest.WebAii.Win32.Dialogs;
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers.md
index 83075613..8b641bf7 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers.md
@@ -4,7 +4,7 @@ page_title: Built-In Handlers
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Built-In Handlers#
+# Built-In Handlers
 
 Telerik Testing Framework includes native support for HTML pop-ups for all supported browsers in addition to a dialog handling framework (under the Win32.Dialogs) namespace with built-in support to handle some of the common browser dialogs like JavaScript Alert, Upload dialog and Logon dialog. The framework also enables you to extend this support to handle any custom dialog you need handled in any manner.
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
index 19dc2d7f..9138f28c 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
@@ -4,11 +4,11 @@ page_title: Custom Dialogs
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Custom Dialog Handler#
+# Custom Dialog Handler
 
 If for whatever reason you decide that you don't like the way the dialog is being handled or want to perform extra tasks before handling the dialog, you can simply craft your own dialog handling code and then ask the dialog to call your code instead of its dialog handling code. Here is an example:
 
-```C#
+````C#
 public void DoCustomDialogHandlingForBuiltInDialogs()
  {
     AlertDialog myAlertDialog = new AlertDialog(ActiveBrowser, DialogButton.OK);
@@ -46,10 +46,8 @@ public bool MyCustomAlertHandler(IDialog dialog)
          return false;
     }
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub DoCustomDialogHandlingForBuiltInDialogs()
   
@@ -82,7 +80,7 @@ Public Sub MyCustomAlertHandler(ByVal dialog As ArtOfTest.WebAii.Win32.Dialogs.I
     End Try
   
 End Sub
-```
+````
 > **To compile the above code include the following using:**
 >
 > using ArtOfTest.WebAii.Win32.Dialogs;
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
index 1fc0906a..8706777d 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
@@ -4,33 +4,31 @@ page_title: Custom Handlers
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Creating Custom Dialog Handlers#
+# Creating Custom Dialog Handlers
 
 So far we've addressed the common dialogs that browsers popup and how the built-in support can be used to handle them. So what do we do if we have a different dialog that we need to handle? Telerik Testing Framework provides a **GenericDialog class** (which does all the work for you of implementing a custom dialog handler), a **BaseDialog class** (which does most of the work of implementing a custom dialog handler), and the IDialog interface for when you need to roll your own custom dialog handler from scratch. Once implemented you can add your custom dialog handler to the **DialogMonitor** and have all your other dialogs handled just like the rest of the built-in dialogs.
 
-##Using the GenericDialog Class##
+## Using the GenericDialog Class
 
 Using the GenericDialog class you can create your own custom dialog handler that can handle most any simple standard Win32 dialog. Here's an example of how to implement a handler for Internet Explorers Security Warning dialog:
 
-```C#
+````C#
 GenericDialog SecurityWarningDialog = new GenericDialog(ActiveBrowser, "Security Warning", false, 1);  // Click on the Yes button
 Manager.DialogMonitor.AddDialog(SecurityWarningDialog);
-```
- 
-
-```VB
+````
+````VB
 Dim SecurityWarningDialog As GenericDialog = New GenericDialog(Me.ActiveBrowser, "Security Warning", False, 1)  ' Click on the Yes button
 SecurityWarningDialog GenericDialog = GenericDialog(.ActiveBrowser, , , 1) 
 Manager.DialogMonitor.AddDialog(SecurityWarningDialog)
-```
+````
 
-##Using the BaseDialog Class##
+## Using the BaseDialog Class
 
 By using the BaseDialog class as your base class to derive your custom dialog handler you only need to override the IsDialogActive() and Handle() functions. You may also provide your own constructor to validate the button type that will dismiss the dialog and/or accept a Desktop object (which you will need if you need to call Mouse.Click or Keyboard.SendString). Reference to System.Drawing.dll have to be added to the project as well.
 
 The below example is a complete custom dialog handler that handles the "Security Alert" dialog displayed by Internet Explorer:
 
-```C#
+````C#
 
 using System;
 using ArtOfTest.WebAii.Core;
@@ -144,10 +142,8 @@ namespace WebTesting
         #endregion
     }
 }
-```
- 
-
-```VB
+````
+````VB
 
 Imports ArtOfTest.WebAii.Core
 Imports ArtOfTest.Common.Win32
@@ -245,24 +241,22 @@ Namespace WebTesting
 		#End Region
 	End Class
 End Namespace
-```
+````
 
 Once you have implemented your new custom dialog handler it requires just one line of code to add it to the DialogMonitor:
 
-```C#
+````C#
 Manager.DialogMonitor.AddDialog(new SecurityAlertDialog(ActiveBrowser, DialogButton.YES, Manager.Desktop));
-```
- 
-
-```VB
+````
+````VB
 Manager.DialogMonitor.AddDialog(New SecurityAlertDialog(Me.ActiveBrowser, DialogButton.YES, Me.Manager.Desktop))
-```
+````
 
-##Implementing a Custom Dialog Handler with IDialog##
+## Implementing a Custom Dialog Handler with IDialog
 
 When the GenericDialog and the BaseDialog classes don't provide the functionality you need, you can roll your own complete custom dialog handling by implementing the <a href="http://docs.telerik.com/teststudioapi/html/T_ArtOfTest_WebAii_Win32_Dialogs_IDialog.htm" target="_blank">IDialog</a> interface. An example of when this is necessary is when creating handlers for most FireFox dialogs. See How to handle FireFox dialogs for an example of a FireFox dialog handler implemented using the IDialog interface. A reference to UIAutomationClient.dll has to be added to the project and a using to System.Windows.Automation namespace would be required in the code. The IDialog interface has the following methods and properties that you must implement:
 
-```C#
+````C#
 /// <summary>
 /// Interface to implement for dialogs to be monitored and handled by the DialogMonitor object.
 /// </summary>
@@ -326,10 +320,8 @@ public interface IDialog
      /// </summary>
 	 bool MatchesUIAutomationElement(AutomationElement element);
 }
-```
- 
-
-```VB
+````
+````VB
 ''' <summary>
 ''' The dialogs current state. This property is Managed by the dialog
 ''' monitor. Implementors should simply provide a private field to
@@ -438,7 +430,7 @@ End Sub
 ''' </summary>
 Private Function MatchesUIAutomationElement(element As AutomationElement) As Boolean
 End Function
-```
+````
 
 After implementing this interface and creating an instance of your class in your test code, you can add the instance to the DialogMonitor to begin handling of your special dialog. See Handling FireFox dialogs for an example of implementing the IDialog interface. The interface is pretty straight forward but here is how the DialogMonitor uses it:
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
index 48292226..44e3cb2d 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
@@ -5,11 +5,11 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/advanced-topics/handling-html-popups-and-dialogs/built-in-dialog-handlers/handling-filedownload-dialog.aspx, /user-guide/write-tests-in-code/advanced-topics/handling-html-popups-and-dialogs/built-in-dialog-handlers/handling-filedownload-dialog
 position: 2
 ---
-#Handling FileDownload Dialogs#
+# Handling FileDownload Dialogs
 
 With FileDownload, you need to pass in the full path to the download location and how the dialog should be handled. 
 
-```C#
+````C#
 DownloadDialogsHandler dialog = new DownloadDialogsHandler (Manager.ActiveBrowser, DialogButton.SAVE, @"D:\text.txt", Manager.Desktop); 
  
 Manager.DialogMonitor.Start();
@@ -20,10 +20,8 @@ Element.Click(false);
  
 dialog.WaitUntilHandled(30000);
 
-```
- 
-
-```VB
+````
+````VB
 Dim dialog As New DownloadDialogsHandler(Manager.ActiveBrowser, DialogButton.SAVE, "D:\text.txt", Manager.Desktop)
 
 Manager.DialogMonitor.Start()
@@ -33,7 +31,7 @@ Manager.DialogMonitor.Start()
 Element.Click(False)
 
 dialog.WaitUntilHandled(30000)
-```
+````
 > **To compile the above code include the following using:**
 >
 > using ArtOfTest.WebAii.Win32.Dialogs;
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
index 2aa5f7c0..2addba0f 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
@@ -4,11 +4,11 @@ page_title: FileUpload Dialog
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#FileUpload Dialog#
+# FileUpload Dialog
 
 With FileUpload, you need to pass in the full path to the file to upload and how the dialog should be handled. The options for FileUpload are: DialogButton.OPEN, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add a FileUpload dialog to be monitored.
 Manager.DialogMonitor.AddDialog(new FileUploadDialog(ActiveBrowser, @"C:\EmptyTextFile.txt", DialogButton.OPEN));
   
@@ -23,10 +23,8 @@ Manager.DialogMonitor.Start();
 Pages.YourSite.YourButton.Click();
   
 // Dialog should be automatically handled
-```
- 
-
-```VB
+````
+````VB
 ' Add a FileUpload dialog to be monitored.
 Manager.DialogMonitor.AddDialog(New FileUploadDialog(ActiveBrowser, Path.Combine(Globals.PATH_TO_PAGES, "..\SupportFiles\EmptyTextFile.txt"), DialogButton.OPEN))
   
@@ -36,13 +34,13 @@ Manager.DialogMonitor.Start()
   
 ' Cause the upload Dialog to pop-up
 Pages.YourSite.YourButton.Click()
-```
+````
 
-##Multiple Files Upload##
+## Multiple Files Upload
 
 There are scenarios where multiple files needs to be uploaded. Below you could find a sample code how to obtain that with the Testing Framework. The code will loop through a set of files and will upload each after the previous. The sample is built against a <a href="https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_fileupload_multiple" target="_blank">public accessible webpage</a> and to give a try to that example you have to first navigate to that page. 
 
-```C#
+````C#
 
 // place small pictures with names file1.png and file2.png in c:\temp folder to have the sample working without modification
 string path = @"C:\temp\" ;
@@ -84,12 +82,12 @@ for (int i = 0; i < fileNames.Length; i++ )
     ActiveBrowser.Refresh();
 }
 
-```
+````
 
 > **Note:** To compile the above code include the following using:
 >
 > using ArtOfTest.WebAii.Win32.Dialogs;
 
-##See Also##
+## See Also
 
 * <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files" target="_blank">How to Transfer Files</a>
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md
index 65149522..83ee7746 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md
@@ -4,14 +4,14 @@ page_title: Firefox Dialogs
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#How to Handle Firefox Dialogs#
+# How to Handle Firefox Dialogs
 
 Firefox dialogs require special attention because some of them are not standard Win32 dialogs, for example Firefox's download manager dialog. As a result the usual method for handing dialogs does not work with Firefox dialogs. Here is what the download manager dialog looks like:
 
 <table id="no-table">
 	<tr>
-		<td>![Firefox download manager dialog window][1] <br><br>**Firefox download manager dialog window**</td>
-		<td>![Firefox download manager dialog window after download completes][2] <br><br>**Firefox download manager dialog window after download completes**</td>
+		<td><img src="images/firefox-dialogs/fig1.png" alt="Firefox download manager dialog window" /> <br><br>**Firefox download manager dialog window**</td>
+		<td><img src="images/firefox-dialogs/fig2.png" alt="Firefox download manager dialog window after download completes" /> <br><br>**Firefox download manager dialog window after download completes**</td>
 	</tr>
 <table>
 
@@ -21,7 +21,7 @@ The other thing we discover about this dialog is that the Clear List button and
  
 Let's start implementing our dialog handler. First we'll need some local class variables and property accessors:
 
-```C#
+````C#
 using System;
 using System.Threading;
  
@@ -106,10 +106,8 @@ namespace WebTesting
             set {this._currentState = value; }
         }
         #endregion
-```
- 
-
-```VB
+````
+````VB
 Public Class FFDownloadsDialog
     Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog
  
@@ -140,16 +138,16 @@ Public Class FFDownloadsDialog
     ' Semaphore used by the WaitUntilHandled function.
     ' </summary>
     Private _autoEvent As AutoResetEvent = New AutoResetEvent(False)
-#End Region
+# End Region
  
-#Region "Private Constants"
+# Region "Private Constants"
     ' <summary>
     ' The title of the dialog we want handled.
     ' </summary>
     Private Const DIALOG_TITLE As String = "Downloads"
-#End Region
+# End Region
  
-#Region "Properties"
+# Region "Properties"
     ' <summary>
     ' Gets the Window object of the dialog being handled.
     ' </summary>
@@ -200,37 +198,35 @@ Public Class FFDownloadsDialog
             Me._currentState = value
         End Set
     End Property
-#End Region
-```
+# End Region
+````
 So far everything is very simple and straightforward. Now that the local variables and properties are complete, it's time to implement the constructor. Since all we're going to do to handle the dialog is close it, we don't require the Desktop or DialogButton parameter that standard Win32 dialog handlers require:
 
-```C#
-#region Constructor
+````C#
+# region Constructor
 /// <summary>
 /// Create the dialog.
 /// </summary>
 public FFDownloadsDialog()
 {
 }
-#endregion
-```
- 
-
-```VB
-#Region "Constructor"
+# endregion
+````
+````VB
+# Region "Constructor"
     ' <summary>
     ' Create the dialog handler instance.
     ' </summary>
     Public Sub New()
         MyBase.New()
     End Sub
-#End Region
-```
+# End Region
+````
 
 Since there's nothing to the constructor, we could optionally leave it out and let the default constructor take over. So let's start implementing the IDialog methods starting with IsDialogActive.
 
-```C#
-#region IDialog Members
+````C#
+# region IDialog Members
 /// <summary>
 /// Check whether the dialog is present or not. This function is
 /// called by the DialogMonitor object.
@@ -263,10 +259,8 @@ public bool IsDialogActive(ArtOfTest.WebAii.Win32.WindowCollection dialogs)
     }
     return true;
 }
-```
- 
-
-```VB
+````
+````VB
 ' <summary>
 ' Check whether the dialog is present or not. This function is
 ' called by the DialogMonitor object.
@@ -297,7 +291,7 @@ Public Function IsDialogActive(ByVal dialogs As ArtOfTest.WebAii.Win32.WindowCol
         End If
     Return True
 End Function
-```
+````
 
 Because the DialogMonitor object passes in a **WindowCollection** of windows that have a class name of "#**32770**" and the FireFox dialog has the class name "**MozillaUIWindowClass**" we have to ignore the passed in WindowCollection and perform our own FindWindowRecursively. Once a window with the right caption is found we still need to verify it has the right class name.
  
@@ -305,7 +299,7 @@ Detecting when the download manager has finished downloading files is a little b
  
 Now we need to implement the Handle function:
 
-```C#
+````C#
 /// <summary>
 /// This is called by the DialogMonitor whenever IsDialogActive returns true.
 /// </summary>
@@ -334,10 +328,8 @@ public void Handle()
         }
     }
 }
-```
- 
-
-```VB
+````
+````VB
 ' <summary>
 ' This is called by the DialogMonitor whenever IsDialogActive returns true.
 ' </summary>
@@ -361,7 +353,7 @@ Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.Handle
          End Try
      End If
 End Sub
-```
+````
 
 The normal action we want our custom dialog handler to perform is to simply close the window. This is easily accomplished with this.Window.Close. Once the handler sends to the window the close command we wait up to 500 milliseconds for it to actually go away. We also trigger a semaphore so that the main test thread can be notified that the dialog has been handled.
  
@@ -369,7 +361,7 @@ Optionally our handler code will call a custom handler function if the delegate
  
 Lastly we need to implement the WaitUntilHandled function:
 
-```C#
+````C#
         /// <summary>
 ///
         /// May be called by test code. Waits up to the specific time out
@@ -394,10 +386,8 @@ Lastly we need to implement the WaitUntilHandled function:
          }
      }
 }
-```
- 
-
-```VB
+````
+````VB
     ' <summary>
 ' <summary>
     ' May be called by test code. Waits up to the specific time out
@@ -419,9 +409,7 @@ Lastly we need to implement the WaitUntilHandled function:
 End Sub
  
 End Class
-```
+````
 
 The only thing really happening in this code is to wait on the semaphore to be set. If the semaphore is not set within the timeout period it throws a System.TimeoutException exception. Optionally it will also reset the HandleCount property prior to waiting for the semaphore.
 
-[1]: images/firefox-dialogs/fig1.png
-[2]: images/firefox-dialogs/fig2.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
index d95e7831..71012357 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
@@ -4,7 +4,7 @@ page_title: HTML Popups
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#Handling HTML Pop-ups#
+# Handling HTML Pop-ups
 
 HTML Pop-up are simply browser instances that are invoked by some action on an element of the page. These pop-ups are mostly invoked by calling window.open() from JavaScript. Customers use this method to prompt the user for information without interrupting the current browser instance the user is working in or to simply open new web pages in new browser instances to show side or detailed information.
  
@@ -12,21 +12,19 @@ Given that these pop-ups are just like any other browser instance, the framework
  
 Given that HTML pop-up dialogs are launched through some actions on the page and not through an explicit call to Manager.LaunchNewBrowser(), the framework has no idea which new browser instances you want connected and added to the Manager.Browsers[] collection versus the ones you want ignored. Therefore, you need to notify the framework about the browser instances that you want to be tracked by enabling new browser tracking. You enable manager tracking by calling:
 
-```C#
+````C#
 Manager.SetNewBrowserTracking(true);
-```
- 
-
-```VB
+````
+````VB
 Manager.SetNewBrowserTracking(true)
-```
+````
 
 When new browser tracking is enabled, any new browser instance launched on the machine is automatically added to the Manager.Browsers[] collection. In addition the Manager.ActiveBrowser instance is automatically set to the last launched browser instance. You then have full access to that pop-up instance with its full DOM and the ability to execute automation actions against it just like any other browser instance. When the pop-up is closed using Browser.Close(), the instance is removed from the Manager.Browsers[] collection and the ActiveBrowser instance is again automatically re-assigned to the last active Browser object in the Manager.Browsers[] collection.
  
 The sample below demonstrates this support. Let's start with the following HTML page that invokes a HTML pop-up:
 
 
-```HTML
+````HTML
 <html>
 <head>
     <title>HTMLPopups</title>
@@ -43,11 +41,11 @@ The sample below demonstrates this support. Let's start with the following HTML
     <a onclick="OpenWindow()">Invoke HTML Popup</a>
 </body>
 </html>
-```
+````
 
 The automation code that allows us to connect to that new instance looks like this:
 
-```C#
+````C#
 // Set new browser tracking to enabled.
 // This will make all new browser instances connect to
 // the Manager.
@@ -76,10 +74,8 @@ ActiveBrowser.Close();
 // the last launched active instance.
 Assert.IsTrue(Manager.Browsers.Count == 1);
 Assert.IsTrue(ActiveBrowser.Url.Contains("PAGE_NAME.com"));
-```
- 
-
-```VB
+````
+````VB
 ' Set new browser tracking to enabled.
 ' This will make all new browser instances connect to
 ' the Manager.
@@ -108,16 +104,14 @@ ActiveBrowser.Close()
 ' the last launched active instance.
 Assert.IsTrue(Manager.Browsers.Count = 1)
 Assert.IsTrue(ActiveBrowser.Url.Contains("PAGE_NAME.com"))
-```
+````
 
 Sometimes you need to close the popup by clicking on a button instead of just closing the window. Telerik Testing Framework supports this functionality with an additional paramter to the HtmlControl.Click function. By passing in a 'true' the framework expects the window to close. The ActiveBrowser is also set to the browser window that was open prior to the popup opening.
 
-```C#
+````C#
 Find.ById<HtmlInputButton>("button1").Click(true);  // Here we tell the framework that this click causes the browser window to close
-```
- 
-
-```VB
+````
+````VB
 Find.ById(Of HtmlInputButton)("button1").Click(True)    ' Here we tell the framework that this click causes the browser window to close
-```
+````
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/firefox-dialogs/fig1.png b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/firefox-dialogs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/firefox-dialogs/fig2.png b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/firefox-dialogs/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/modal-dialogs/fig1.png b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/images/modal-dialogs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
index 5a85065c..1738a42e 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
@@ -4,7 +4,7 @@ page_title: Modal Dialogs
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#Handling IE Modal Dialogs#
+# Handling IE Modal Dialogs
 
 ![Modal Dialog][1]
 
@@ -12,7 +12,7 @@ The main difference between IE modal dialogs and the HTML Pop-ups is that the mo
  
 IE modal dialogs require special handling. They don't act like standard HTML pop-up windows, which means the standard approach does not work. Here is an example of how to code for the IE modal dialog special case:
 
-```C#
+````C#
 [TestMethod]
 [Description("How to access and handle IE's modal dialogs")]
 public void IEModalDialogsSupport()
@@ -47,10 +47,8 @@ public void IEModalDialogsSupport()
     // The ActiveBrowser is back to the main browser window.
      ActiveBrowser.NavigateTo("http://www.google.com");
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod(), _
 Description("How to access and handle IE's modal dialogs")> _
 Public Sub IEModalDialogsSupport()
@@ -89,7 +87,7 @@ Public Sub IEModalDialogsSupport()
      ActiveBrowser.NavigateTo("http://www.google.com")
   
 End Sub
-```
+````
 
 [1]: images/modal-dialogs/fig1.png
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
index 31745d6e..0f08816f 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
@@ -4,11 +4,11 @@ page_title: Logon Dialogs
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#Logon Dialogs#
+# Logon Dialogs
 
 With Logon dialogs, you need to pass in the username/password that you want used and how the dialog should be handled. Your options for the Logon dialog are: DialogButton.OK, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add a logon dialog support with username/password
 Manager.DialogMonitor.AddDialog(new LogonDialog(ActiveBrowser, "<username>", "<password>", DialogButton.OK));
 Manager.DialogMonitor.Start();
@@ -17,9 +17,8 @@ Manager.DialogMonitor.Start();
 ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>");
 
 // Dialog should be automatically handled
-```
-
-```VB
+````
+````VB
 ' Add a logon dialog support with username/password
 Manager.DialogMonitor.AddDialog(New LogonDialog(ActiveBrowser, "<username>", "<password>", DialogButton.OK))
 Manager.DialogMonitor.Start()
@@ -28,7 +27,7 @@ Manager.DialogMonitor.Start()
 ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>")
 
 ' Dialog should be automatically handled
-```
+````
 > **To compile the above code include the following using:**
 >
 > using ArtOfTest.WebAii.Win32.Dialogs;
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/check-javascript-errors.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/check-javascript-errors.md
index fbcf7cd4..a4dc82c9 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/check-javascript-errors.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/check-javascript-errors.md
@@ -4,16 +4,13 @@ page_title: Check Javascript Errors - Test Studio Dev Documentation
 description: Check Javascript Errors
 position: 4
 ---
-# Check for JavaScript Errors #
+# Check for JavaScript Errors
 
 Telerik Testing Framework allows you to verify if there are any JavaScript errors on the currently loaded page. The below example demonstrates how to collect the errors in a list and a possible approach how to use these. The sample code will fail the test if there are errors on the page.
 
 > The page in the current example does not actually contain JavaScript errors. Therefore these are invoked on purpose to demonstrate the feature.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // Navigate to a page
     Manager.ActiveBrowser.NavigateTo("https://www.google.com");
             
@@ -45,7 +42,7 @@ Telerik Testing Framework allows you to verify if there are any JavaScript error
             
     // Assert if there are any errors on the current page
     Assert.AreEqual(0, currentErrorsOnPage.Count());
-    {{endregion}}
+````
 
 > __Note:__ The JS error check step detects only JavaScript errors. Any errors related to not loaded resources will not be detected. An example for such console error is listed below:<br>
 <br>
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/invoking-javascript.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
index 3ca21c63..65383915 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/advanced-topics/javascript/invoking-javascript.aspx, /user-guide/write-tests-in-code/advanced-topics/javascript/invoking-javascript
 position: 1
 ---
-#Invoking Javascript#
+# Invoking Javascript
 
 Telerik Testing Framework supports directly invoking JavaScript functions from your .NET test code. One key advantage to this support is that you can use it to do your JavaScript unit testing without having to integrate yet another unit testing framework into your development environment. You can also avoid having to learn/support this additional framework. Abilities include:
 
@@ -19,11 +19,11 @@ Telerik Testing Framework supports directly invoking JavaScript functions from y
 
 * Perform logging/tracing of your JavaScript routines. The logging is done directly into the unified log you are using.
 
-##Invoking JavaScript Functions##
+## Invoking JavaScript Functions
 
 The Actions.InvokeScript() enables you to simply provide a JavaScript function name to invoke. For example:
 
-```C#
+````C#
 // Assume our page has JavaScript method Test1() & Test2() & Test3()
  
 // Call a JavaScript function.
@@ -39,10 +39,10 @@ string jsRetValue = Actions.InvokeScript("Test3();");
  
 // Call a JavaScript function that returns a value
 int val = Actions.InvokeScript<int>(@"Test3(""Bear"", ""Utah"")");
-```
+````
 
 
-```VB
+````VB
 ' Assume our page has JavaScript method Test1() & Test2() & Test3()
  
 ' Call a JavaScript function.
@@ -58,21 +58,21 @@ Dim jsRetValue As String = Actions.InvokeScript("Test3();")
  
 ' Call a JavaScript function that returns a value
 Dim val As Integer = Actions.InvokeScript(Of Integer)("Test3(""Bear"", ""Utah"")")
-```
+````
 
 
 Here is a code which calls an Angular function against input field:
 
-```C#
+````C#
 Actions.InvokeScript("angular.element(" + element.ClientSideLocator + ").val('" + text.Replace("'", "\\'") + "').triggerHandler('input')");
-```
+````
 
-##JavaScript Unit Testing Using NUnit or Visual Studio Team Test##
+## JavaScript Unit Testing Using NUnit or Visual Studio Team Test
 
 Below is an example of how you can define JavaScript unit tests that is consistent with the rest of your tests and manages their execution and reporting using the same unit testing infrastructure, whether it is NUnit or Visual Studio Team Test.
 
 
-```C#
+````C#
 [TestMethod]
 public void JsUnitTest1()
 {
@@ -80,18 +80,16 @@ public void JsUnitTest1()
     string strBool = Actions.InvokeScript("JsUnitTest1()");
     Assert.IsTrue(bool.Parse(strBool));
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub JsUnitTest1()
     ' return 'true' for pass or 'false' for fail.
     Dim strBool As String = Actions.InvokeScript("JsUnitTest1()")
     Assert.IsTrue(Boolean.Parse(strBool))
 End Sub
-```
+````
 
-###See also
+### See also
 
 * <a href="/code-in-test/coded-samples/html/jQuery-events-do-not-fire" target="_blank">jQuery events do not fire</a>
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-events.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-events.md
index 84af85b8..ac2f7fc7 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-events.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-events.md
@@ -4,13 +4,13 @@ page_title: JavaScript Events
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#JavaScript Events#
+# JavaScript Events
 
-##Invoking JavaScript Events##
+## Invoking JavaScript Events
 
 Telerik Testing Framework allows you to invoke JavaScript events directly with or without event arguments. For example:
 
-```C#
+````C#
 // Invoke the OnFocus event
 HtmlButton b = Find.ById<HtmlButton>("b");
 b.InvokeEvent(ScriptEventType.OnFocus);
@@ -25,10 +25,8 @@ MouseEvent me = new MouseEvent();
 me.Type = "mouseover";
 me.SetRelatedTarget(body1);
 area1.InvokeEvent(me);
-```
- 
-
-```VB
+````
+````VB
 ' Invoke the OnFocus event
 Dim b As HtmlButton = Find.ById(Of HtmlButton)("b")
 b.InvokeEvent(ScriptEventType.OnFocus)
@@ -43,13 +41,13 @@ Dim [me] As New MouseEvent()
 [me].Type = "mouseover"
 [me].SetRelatedTarget(body1)
 area1.InvokeEvent([me])
-```
+````
 
-##JavaScript Event Handlers##
+## JavaScript Event Handlers
 
 The framework gives you the ability to attach a .NET event handler to your JavaScript happening in the browser. Start by defining your event handler like this:
 
-```C#
+````C#
 private volatile bool _clickHandled;
 private System.Threading.AutoResetEvent _clickARE;
  
@@ -58,10 +56,8 @@ private void OnClick(object sender, JavascriptEventArgs e)
     _clickHandled = true;
     _clickARE.Set();
 }
-```
- 
-
-```VB
+````
+````VB
 Private _clickHandled As Boolean
 _clickHandled
 Private _clickARE As System.Threading.AutoResetEvent
@@ -70,11 +66,11 @@ Private Sub OnClick(ByVal sender As Object, ByVal e As JavascriptEventArgs)
     _clickHandled = True
     _clickARE.[Set]()
 End Sub
-```
+````
 
 All that's left is to attach the event handler to an element on the DOM like this:
 
-```C#
+````C#
 [TestMethod]
 public void ClickHandler()
 {
@@ -94,10 +90,8 @@ public void ClickHandler()
  
     Assert.IsTrue(_clickHandled);
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub ClickHandler()
     _clickARE = New System.Threading.AutoResetEvent(False)
@@ -116,4 +110,4 @@ Public Sub ClickHandler()
  
     Assert.IsTrue(_clickHandled)
 End Sub
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-logging.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-logging.md
index f6832cbe..8c52dc73 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-logging.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-logging.md
@@ -4,13 +4,13 @@ page_title: Logging from JavaScript
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Logging from JavaScript#
+# Logging from JavaScript
 
 Telerik Testing Framework also supports logging directly from JavaScript into the unified test log that your tests are using. Logging from JavaScript is not enabled by default and needs to be explicitly enabled globally by setting the **Settings.EnableScriptLogging = true** via the <a href="/code-in-test/settings-and-configuration-wtc/settings-class" target="_blank">Settings Class</a> or setting **enableScriptLogging="true"** in the application <a href="/code-in-test/settings-and-configuration-wtc/app-config-file" target="_blank">.config</a> file. In addition each page that wants to perform logging needs to include the WebAii_Logging.js file. You will find this file installed in the %InstallDir%\Bin folder.
  
 Below is a sample to demonstrate how to perform logging from your JavaScript routines:
 
-```C#
+````C#
 // Settings.Current.EnableScriptLogging must be set to true before
 // LaunchNewBrowser. This was done in the Initialize section of
 // this test.
@@ -28,10 +28,8 @@ Settings.Current.EnableScriptLogging = false;
  
 // NOTE: Once script logging is disabled, any logging calls from
 // the script will be ignored and won't cause a script error.
-```
- 
-
-```VB
+````
+````VB
 ' Settings.Current.EnableScriptLogging must be set to true before
 ' LaunchNewBrowser. This was done in the Initialize section of
 ' this test.
@@ -49,13 +47,13 @@ Settings.Current.EnableScriptLogging = False
  
 ' NOTE: Once script logging is disabled, any logging calls from
 ' the script will be ignored and won't cause a script error.
-```
+````
 
 The page script function Test5() can perform logging like this:
 
-```JavaScript
+````JavaScript
 function Test5()
 {
     WebAiiLog("Trace", "Test5: Log this message!");
 }
-```
+````
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/json-objects.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/json-objects.md
index 87380f16..f8e6f068 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/json-objects.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/javascript-wtc/json-objects.md
@@ -4,13 +4,13 @@ page_title: JSON Objects
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 5
 ---
-#Handling JSON Objects#
+# Handling JSON Objects
 
 Your tests can understand JSON (<a href="http://www.json.org/" target="_blank" rel="nofollow">JavaScript Object Notation</a>) and can handle strongly typed objects returned from JavaScript. This might be a bit advanced for regular testers implementing test automation. However, if you are building mini-frameworks on top of Telerik Testing Framework, it is a great tool to help you get rid of having to parse complex strings returned by the InvokeScript function.
  
 This is a basic example of how to use JSON:
 
-```C#
+````C#
 [TestMethod]
 public void KeyValuePairs()
 {
@@ -23,10 +23,8 @@ public void KeyValuePairs()
     Assert.AreEqual<string>("value1", o["root"]["key1"]);
     Assert.AreEqual<string>("value2", o["root"]["key2"]);
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub KeyValuePairs()
     Manager.LaunchNewBrowser()
@@ -37,11 +35,11 @@ Public Sub KeyValuePairs()
     Assert.AreEqual(Of String)("value1", o("root")("key1"))
     Assert.AreEqual(Of String)("value2", o("root")("key2"))
 End Sub
-```
+````
 
 In this example we define our own object in a Data Contract:
 
-```C#
+````C#
 [DataContract]
 public class MyObject
 {
@@ -59,10 +57,8 @@ public void ReturnObject()
     Assert.AreEqual<int>(1, o.One);
     Assert.AreEqual<int>(15, o.Fifteen);
 }
-```
- 
-
-```VB
+````
+````VB
 <DataContract()> _
 Public Class MyObject
     Private _One As Integer
@@ -94,11 +90,11 @@ Public Sub ReturnObject()
     Assert.AreEqual(Of Integer)(1, o.One)
     Assert.AreEqual(Of Integer)(15, o.Fifteen)
 End Sub
-```
+````
 
 In this example we'll access an array returned by InvokeScript, treat it as JSON, and parse it manually for its values.
 
-```C#
+````C#
 var actions = Manager.Current.ActiveBrowser.Actions;
 JsonObject result = actions.InvokeScript <JsonObject>("window.my_list=[1,2,3]");
 JsonArray arr = (JsonArray)result["root"];
@@ -107,10 +103,8 @@ for (int i = 0; i < 3; i++)
 double val = arr[i];
 Log.WriteLine(val.ToString());
 }
-```
- 
-
-```VB
+````
+````VB
 Dim actions = Manager.Current.ActiveBrowser.Actions
 Dim result As JsonObject = actions.InvokeScript(Of JsonObject)("window.my_list=[1,2,3]")
 Dim arr As JsonArray = DirectCast(result("root"), JsonArray)
@@ -118,4 +112,4 @@ For i As Integer = 0 To 2
     Dim val As Double = arr(i)
     Log.WriteLine(val.ToString())
 Next
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/multi-browser-support.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/multi-browser-support.md
index c828e76e..4126b79c 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/multi-browser-support.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/multi-browser-support.md
@@ -5,12 +5,12 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/advanced-topics/multi-browser-instance-support.aspx, /user-guide/write-tests-in-code/advanced-topics/multi-browser-instance-support
 position: 3
 ---
-#Multi-Browser Instance Support#
+# Multi-Browser Instance Support
 
 Throughout the Telerik Testing Framework tutorials, we've been focusing only on the single browser instance 'ActiveBrowser,' given that it is the most common usage in web automation. Multi-browser instance automation within one session of the Manager object is supported, however. Having different types of browsers being automated within the same session is also supported. For example, within one test case session, you can automate two Internet Explorer browser instances and one Firefox instance all running concurrently. Such types of automation might not be very common but might be useful for certain specialized scenarios. (i.e. you could use this feature to do bitmap comparison across different browser types by capturing browser images from one instance and comparing it to the captured image from another instance).
 
 
-##How It Works##
+## How It Works
 
 The 'Manager' object is the main object that keeps tracks of all active browser instances using the Manager.Browsers[] collection. Users can launch as many instances as they want by using the 'Manager.LaunchNewBrowser()' method. Each time a new browser is launched, the 'Manager' creates the new 'Browser' object corresponding to that browser instance and adds it to the Browsers[] collection. The 'ActiveBrowser' property exposed off the 'Manager' is actually the last launched browser and should be the last browser instance in the 'Browsers[]' collection.
 
@@ -18,7 +18,7 @@ The 'Manager' object is the main object that keeps tracks of all active browser
  
 The below sample demonstrates how you can leverage the multi-browser support to automate multiple instances of a browser within one test case. Such testing might be needed when performing concurrency testing in your web app.
 
-```C#
+````C#
 // Launch a new instance of IE
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, true);
   
@@ -56,10 +56,8 @@ ie.Window.SetFocus();
 // You can also choose to set a timeout as shown below to double check that the
 // browser has actually closed and its handle is no longer visible.
 ff.Close(40);
-```
- 
-
-```VB
+````
+````VB
 ' Launch a new instance of IE
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, True)
   
@@ -97,4 +95,4 @@ ie.Window.SetFocus()
 ' You can also choose to set a timeout as shown below to double check that the
 ' browser has actually closed and its handle is no longer visible.
 ff.Close(40)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction.md
index 9955f3db..1e7977a1 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction.md
@@ -4,11 +4,11 @@ page_title: Introduction to TestRegions
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Introduction to TestRegions#
+# Introduction to TestRegions
 
 Building testability and agility into your markup applications.
 
-##What Are TestRegions? (*)##
+## What Are TestRegions? (*)
 
 TestRegions are simple innovations that bring a new perspective to automated software testing by breaking the traditional silos between application authoring and testing. They pave the way to a better and more robust test automation while enhancing the agility of the overall development lifecycle. TestRegions are hopefully a first step that others can use and build upon to usher a new generation of tools and methodologies that bring new advancements in the art of software testing and quality assurance.
  
@@ -28,7 +28,7 @@ Some of the key benefits of TestRegions are:
  
 To help demonstrate these benefits, we will be using the following simple markup page as our sample application through out this tutorial.
 
-```HTML
+````HTML
 <html>
 <head>
    <title>Basic TestRegion's Usage</title>
@@ -65,9 +65,9 @@ To help demonstrate these benefits, we will be using the following simple markup
    </div>
 </body>
 </html>
-```
+````
 
-##Current Automation Practices##
+## Current Automation Practices
 
 Before digging into TestRegions, let's first take a look at some of the current common automation approaches for markup applications and understand their characteristics, challenges and drawbacks.
  
@@ -92,25 +92,25 @@ To clarify this point more, let's take a simple example:
  
 With that being said, it is important to note that TestRegions DO NOT completely eradicate the need for ids/names but instead they augment the current use of ids/names and common automation practices to help address some of the issues mentioned above and add more structure and consistency to test automation.
 
-##Using TestRegions##
+## Using TestRegions
 
 Let's start by using TestRegions in the above sample to provide a structured approach to accessing this application from test automation. To do so, we need to inject TestRegions within our application markup. The TestRegions supported by Telerik Testing Framework Automation Infrastructure are:
 
-```HTML
+````HTML
 <testregion id="regionid">...region content...</testregion>
-```
+````
 
 Given that these are custom tags and are currently not handled as expected in latest browsers (for example, in Firefox, custom tags - even if they are Xhtml defined with extended dtd - are always included with the closing tag right after the open tag regardless of the tag content), the comment version of these tags is supported:
 
-```HTML
+````HTML
 <!--testregion id="regionid"-->...region content...<!--/testregion-->
-```
+````
 
 Using these tags as comments is a very unintrusive approach to the overall application and is completely compliant with markup standards like XHTML and XML.
 
 Let's start by defining two logical regions within our sample application above that we want to target in our automated testing. The page below shows the sample above with the following two logical regions defined: userinput, restaurantdata.
 
-```HTML
+````HTML
 <html>
 <head>
    <title>Basic TestRegion's Usage</title>
@@ -151,23 +151,21 @@ Let's start by defining two logical regions within our sample application above
    </div>
 </body>
 </html>
-```
+````
 
 With test regions defined, our test code can directly access these regions regardless of their nesting or positioning as follows:
 
-```C#
+````C#
 TestRegion userInput = Manager.ActiveBrowser.Regions["userinput"];
 TestRegion restaurantData = Manager.ActiveBrowser.Regions["restaurantdata"];
-```
- 
-
-```VB
+````
+````VB
 Dim userInput As TestRegion = Manager.ActiveBrowser.Regions("userinput")
 Dim restaurantData As TestRegion = Manager.ActiveBrowser.Regions("restaurantdata")
-```
+````
 Each TestRegion above represents the part of the application as defined by the TestRegio's that are part of the application. It is worth noting here that the TestRegions collection accessor is case-insensitive to avoid test failures due to id casing mistakes.
 
-##Identifying Elements Using TestRegions##
+## Identifying Elements Using TestRegions
 
 Now that we know how to define test regions as part of an application under test and how to access them from our automated test code, our next step is to be able to access elements contained in these TestRegions to perform actions on or extract data from.
  
@@ -179,24 +177,22 @@ Each TestRegion object has two properties that provide access to the elements co
  
 For example, to locate the restaurants table in the above sample, you can write:
 
-```C#
+````C#
 TestRegion restaurantData = Manager.ActiveBrowser.Regions["restaurantdata"];
  
 // Given that the table is the first table within the 'restaurantdata' test region, it has an occurrence index of '0'
 Element restaurantTable = restaurantData.Find.ByTagIndex("table", 0);
-```
- 
-
-```VB
+````
+````VB
 Dim restaurantData As TestRegion = Manager.ActiveBrowser.Regions("restaurantdata")
  
 ' Given that the table is the first table within the 'restaurantdata' test region, it has an occurrence index of '0'
 Dim restaurantTable As Element = restaurantData.Find.ByTagIndex("table", 0)
-```
+````
 
 Once you have access to the Element object, you can now use it to extract information from or execute actions on. For example:
 
-```C#
+````C#
 // access the userinput test region.
 TestRegion userInput = Manager.ActiveBrowser.Regions["userinput"];
  
@@ -205,10 +201,8 @@ Element zipCodeTextBox = userInput.Find.ByXPath("//input[2]");
  
 // Perform an action on the element.
 Manager.ActiveBrowser.Actions.SetText(zipCodeTextBox, "90210");
-```
- 
-
-```VB
+````
+````VB
 ' access the userinput test region.
 Dim userInput As TestRegion = Manager.ActiveBrowser.Regions("userinput")
  
@@ -217,11 +211,11 @@ Dim zipCodeTextBox As Element = userInput.Find.ByXPath("/input[2]")
  
 ' Perform an action on the element.
 Manager.ActiveBrowser.Actions.SetText(zipCodeTextBox, "90210")
-```
+````
 
 In the first sample above, the test will not be impacted by any changes to the application regardless of how many 'table' tags get added before or after that testregion. You can even extract that testregion and embed it in a different portion of a different application and all tests that target that region will still work as expected. Same with the second sample.
 
-##Summary##
+## Summary
 
 The samples above introduce you to basic usage of TestRegions as part of the Telerik Testing Framework Automation Infrastructure. They also demonstrate how you can utilize this approach to build robust test automation code that exhibit low maintenance cost and is highly resilient to undesired test breaks. Moreover, they demonstrate how to use a consistent and structured approach to identify application segments to target for automation while making test code more legible and faster to learn and understand. TestRegions can enhance the agility of development teams and fits nicely within an agile development environment.
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
index fb5c96c4..8a6516dd 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
@@ -4,7 +4,7 @@ page_title: Asp.NET TR Control
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 2
 ---
-#Using Asp.Net TestRegion Control#
+# Using Asp.Net TestRegion Control
 
 TestRegions can be a powerful tool to build testability into your web applications and enable your test automation teams to build highly resilient test beds that have low maintenance costs compared to the traditional automation methods like the HTTP record/replay approaches. TestRegions are ideal to be used with dynamic web frameworks like ASP.NET since they can take out some of the complexity that comes with the auto generated html. Given that TestRegions are injected in the source code of web pages, we wanted to provide Visual Studio and ASP.NET developers a richer experience at design time. Telerik Testing Framework includes an ASP.NET TestRegion Custom Control that can be used just like any other asp: control to define TestRegion's into your code. This control allows you to:
 
@@ -20,7 +20,7 @@ Below is a segment of the HTML persisted that is shown in design view above.
 
 **Note:** The samples shown above are included in full in the code samples installed with Telerik Testing Framework.
 
-##Adding ASP.NET TestRegion Control to Your Toolbox##
+## Adding ASP.NET TestRegion Control to Your Toolbox
 
 To be able to use this control as shown above, you simply need to add it first to your ToolBox. Visual Studio should handle all tag registrations once you drag-n-drop the control on your pages. To add the control to your toolbox:
 
diff --git a/docs-teststudiodev/code-in-test/advanced-topics-wtc/using-the-http-proxy.md b/docs-teststudiodev/code-in-test/advanced-topics-wtc/using-the-http-proxy.md
index 1686ece6..1fc4177a 100644
--- a/docs-teststudiodev/code-in-test/advanced-topics-wtc/using-the-http-proxy.md
+++ b/docs-teststudiodev/code-in-test/advanced-topics-wtc/using-the-http-proxy.md
@@ -4,7 +4,7 @@ page_title: Using the HTTP Proxy
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Using the HTTP Proxy#
+# Using the HTTP Proxy
 
 Telerik Testing framework includes the ArtOfTest.WebAii.Messaging.Http namespace. With it you have the ability to intercept raw HTTP traffic under the cover. Using the HTTP proxy you can intercept an HTTP request originating from the browser before it is sent to the web server and/or intercept HTTP responses coming from the web server just before they reach the browser and are rendered by it. This functionality opens up the framework to be used in a wider range of automation scenarios like:
 
@@ -21,31 +21,45 @@ In this namespace you will find the following methods classes:
 	<th>Class</th><th>Description</th>
 </tr>
 <tr>
-	<td>**HttpProxyManager**</td>
+<td>
+	
+**HttpProxyManager**</td>
 	<td>Manages the HTTP proxy agent.</td>
 </tr>
 <tr>
-	<td>**HttpRequest**</td>
+<td>
+	
+**HttpRequest**</td>
 	<td>Used to create and manipulate an HTTP request.</td>
 </tr>
 <tr>
-	<td>**HttpRequestEventArgs**</td>
+<td>
+	
+**HttpRequestEventArgs**</td>
 	<td>EventArgs subclass that wraps an HTTP request, and possibly the related response.</td>
 </tr>
 <tr>
-	<td>**HttpResponse**</td>
+<td>
+	
+**HttpResponse**</td>
 	<td>Class wrapper of an HTTP response.</td>
 </tr>
 <tr>
-	<td>**HttpResponseEventArgs**</td>
+<td>
+	
+**HttpResponseEventArgs**</td>
 	<td>EventArgs subclass that wraps an HTTP response and the related request.</td>
 </tr>
 <tr>
-	<td>**RequestListenerInfo**</td>
+<td>
+	
+**RequestListenerInfo**</td>
 	<td>Wraps a listener for BeforeRequest events from the proxy.</td>
 </tr>
 <tr>
-	<td>**ResponseListenerInfo**</td>
+<td>
+	
+**ResponseListenerInfo**</td>
 	<td>Wraps a listener for BeforeResponse events from the proxy.</td>
 </tr>
 <table>
@@ -53,15 +67,15 @@ In this namespace you will find the following methods classes:
 You must enable the HTTP proxy before you can start using it. This setting is turned off by default. This can be done either by adding the setting to your .config file or modifying the setting in the Settings object. To add the setting to your .config file add this to your .config file:
 
 
-```XML
+````XML
 <WebAii.Settings
     Manager.Settings.Web.UseHttpProxy="true"
 />
-```
+````
 
 To enable this setting in the Settings object, add code to your initialization section like this:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -72,10 +86,8 @@ settings.Web.UseHttpProxy = true;
  
 // Now call Initialize again with your updated settings object
 Initialize(settings, new TestContextWriteLine(this.TestContext.WriteLine));
-```
- 
-
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -86,10 +98,10 @@ settings.UseHttpProxy = True
  
 ' Now call Initialize again with your updated settings object
 Initialize(settings, New TestContextWriteLine(AddressOf Me.TestContext.WriteLine))
-```
+````
 Now that we have the HTTP proxy turned on we can start using it. Here's an example of how we would detect that a response coming back from the web server is an image response.
 
-```C#
+````C#
 [TestMethod]
 public void ImageDetection()
 {
@@ -121,10 +133,8 @@ private void CheckTypeForImage(object sender, HttpResponseEventArgs e)
             e.Response.Headers["Content-Type"]));
     }
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub ImageDetection()
     ' Launch a new browser window
@@ -149,11 +159,11 @@ Private Sub CheckTypeForImage(ByVal sender As Object, ByVal e As HttpResponseEve
         Log.WriteLine([String].Format("Not an image; MIME type: {0}", e.Response.Headers("Content-Type")))
     End If
 End Sub
-```
+````
 
 Let's go one step further. Suppose we want to verify that all of the images on the web page were smaller than 40Kb. We can accomplish this using code like this:
 
-```C#
+````C#
 [TestMethod]
 public void CheckImageSize()
 {
@@ -179,10 +189,8 @@ private void Check(object sender, HttpResponseEventArgs e)
         _imageTooLarge = true;
     }
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub CheckImageSize()
     ' Add our HTTP response event handler
@@ -205,6 +213,6 @@ Private Sub Check(ByVal sender As Object, ByVal e As HttpResponseEventArgs)
         _imageTooLarge = True
     End If
 End Sub
-```
+````
 
 **Note:** If you are using **localhost** in the URL of the **NavigateTo** method it must contain a trailing '.' character like this: ActiveBrowser.NavigateTo("http://localhost./myTestPage") . This is an IE limitation where all URL's must contain a '.' character in them to be recognized properly when a proxy is in place.
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/access-oracle-database.md b/docs-teststudiodev/code-in-test/coded-samples/general/access-oracle-database.md
index d7b48588..8d31f000 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/access-oracle-database.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/access-oracle-database.md
@@ -25,29 +25,22 @@ For default installation the dll file could be found in the Oracle data base ins
 
 Include the following *usings* in the code.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using Oracle.DataAccess.Client;
     using Oracle.DataAccess.Types;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
-    import Oracle.DataAccess.Client
-    import Oracle.DataAccess.Types
-    {{endregion}}
+````
+````VB
+    Imports Oracle.DataAccess.Client
+    Imports Oracle.DataAccess.Types
+````
 
 ## Data Connection String
 
 An Oracle connection string is required to identify the database to connect to. Here is an example:
 
-```
+````
 Data Source=XE;User Id=SYSTEM;Password=pass;
-```
+````
 
 Different connection strings could be used. See <a href="https://www.connectionstrings.com/oracle/" target="_blank">here</a> for more examples.
 
@@ -55,10 +48,7 @@ Different connection strings could be used. See <a href="https://www.connections
 
 This code runs a simple query against a database table similar to <a href="/advanced-topics/data-driven-testing/oracle-db-example" target="_blank">this example</a>:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     string oradb = "Data Source=XE;User Id=SYSTEM;Password=pass;";
 
     OracleConnection conn = new OracleConnection(oradb);
@@ -82,7 +72,7 @@ This code runs a simple query against a database table similar to <a href="/adva
     Log.WriteLine(dr.GetString(0).ToString());
 
     conn.Dispose();
-    {{endregion}}
+````
 
 >**Note**: This code won't run without modification. The database, table, and column in the original code won't exist in your environment unless you create the same database.
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/access-sql-database.md b/docs-teststudiodev/code-in-test/coded-samples/general/access-sql-database.md
index 847cfebc..6b3bc237 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/access-sql-database.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/access-sql-database.md
@@ -19,19 +19,12 @@ If a reference to System.Data 2.0 already exists, remove it and add it from the
 
 Ensure you add the *using* or *Imports* statement to the top of the code-behind file.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Data.SqlClient;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Data.SqlClient;
-    {{endregion}}
+````
 
 ## Sample Code
 
@@ -41,10 +34,7 @@ Here is a SQL database named **myFirstDB** with a table named **Table_1** and co
 
 ### Read from SQL Database
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Define a new SQL connection with a connection string. 
     //The connection string will be different depending on your environment and the name of the database, table, etc.
     //See http://www.connectionstrings.com for connection string examples.
@@ -67,12 +57,8 @@ Here is a SQL database named **myFirstDB** with a table named **Table_1** and co
  
     thisReader.Close();
     thisConnection.Close();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     'Define a new SQL connection with a connection string. 
     'The connection string will be different depending on your environment and the name of the database, table, etc.
     'See http://www.connectionstrings.com for connection string examples.
@@ -94,14 +80,11 @@ Here is a SQL database named **myFirstDB** with a table named **Table_1** and co
     
     thisReader.Close()
     thisConnection.Close()
-    {{endregion}}
+````
 
 ### Write into SQL Database
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Define a new SQL connection with a connection string.
     //The connection string will be different depending on your environment and the name of the database, table, etc.
     //See http://www.connectionstrings.com for connection string examples.
@@ -115,12 +98,8 @@ Here is a SQL database named **myFirstDB** with a table named **Table_1** and co
     SqlCommand thisCommand = thisConnection.CreateCommand();
     thisCommand.CommandText = "INSERT INTO Table_1 (City) VALUES ('Richmond')";
     thisCommand.ExecuteNonQuery();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     'Define a new SQL connection with a connection string.
     'The connection string will be different depending on your environment and the name of the database, table, etc.
     'See http://www.connectionstrings.com for connection string examples.
@@ -134,7 +113,7 @@ Here is a SQL database named **myFirstDB** with a table named **Table_1** and co
     Dim thisCommand As SqlCommand = thisConnection.CreateCommand()
     thisCommand.CommandText = "INSERT INTO Table_1 (City) VALUES ('Richmond')"
     thisCommand.ExecuteNonQuery()
-    {{endregion}}
+````
 
 **Note**: The example requires to be modified as per the databse which will be used as data source. 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/attach-data-columns.md b/docs-teststudiodev/code-in-test/coded-samples/general/attach-data-columns.md
index a944fe0a..2353e306 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/attach-data-columns.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/attach-data-columns.md
@@ -14,48 +14,34 @@ Use the Data object in conjunction with the column name or index.
 
 In this example on Bing.com, I added the *SbFormQText* element to the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a> via the Add To Project Elements feature from the <a href="/features/recorder/highlighting-elements" target="_blank">Elements Menu</a>. Now I can reference that element in code and data drive its input text:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Reference a column by name
     Pages.Bing.SbFormQText.Text = Data["Col1"].ToString();
     
     //Reference a column by index (zero based)
     Pages.Bing.SbFormQText.Text = Data[0].ToString();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     'Reference a column by name
     Pages.Bing.SbFormQText.Text = Data("Col1").ToString()
     
     'Reference a column by index (zero based)
     Pages.Bing.SbFormQText.Text = Data(0).ToString()
-    {{endregion}}
+````
 
 This method can also be applied to a **Verification**:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Reference a column by name
     Assert.IsTrue(ActiveBrowser.ContainsText(Data["Col1"].ToString()));
     
     //Reference a column by index (zero based)
     Assert.IsTrue(ActiveBrowser.ContainsText(Data[0].ToString()));
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     'Reference a column by name
     Assert.IsTrue(ActiveBrowser.ContainsText(Data("Col1").ToString()))
     
     'Reference a column by index (zero based)
     Assert.IsTrue(ActiveBrowser.ContainsText(Data(0).ToString()))
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/browser-specific-actions.md b/docs-teststudiodev/code-in-test/coded-samples/general/browser-specific-actions.md
index 6e8ee705..0a129d7d 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/browser-specific-actions.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/browser-specific-actions.md
@@ -20,10 +20,7 @@ The **RunsAgainst** Test Step Property allows you to choose against which browse
 
 You can  put together a much more complex use-case by using a coded solution. Here's the code from the test sample. It demonstrates how to use a different search word based on browser type:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ActiveBrowser.NavigateTo("http://www.telerik.com/"); 
     //Navigate to the page
     
@@ -49,12 +46,8 @@ You can  put together a much more complex use-case by using a coded solution. He
     
     Find.ById<HtmlInputSubmit>("~btnSearchSubmit").Click(); //Click submit button
     System.Threading.Thread.Sleep(2000); //Wait a bit so we can see the result
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveBrowser.NavigateTo("http://www.telerik.com/")
     'Navigate to the page
     
@@ -82,6 +75,6 @@ You can  put together a much more complex use-case by using a coded solution. He
     'Click submit button
     System.Threading.Thread.Sleep(2000)
     'Wait a bit so we can see the result
-    {{endregion}}
+````
 
 [1]: images/run-against.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/custom-scripts-before-after.md b/docs-teststudiodev/code-in-test/coded-samples/general/custom-scripts-before-after.md
index 9e9a46b0..7c3ea514 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/custom-scripts-before-after.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/custom-scripts-before-after.md
@@ -18,61 +18,47 @@ First, create a coded step in order to generate a code-behind file. Then open th
 
 ### Visual Studio plugin
 
-1.If your test doesn't contain any coded steps, click the <a href="/code-in-test/features-in-code#Code-Behind-File" target="_blank">Add Code-Behind File button</a>.
-2.If you test contains a coded step, right click it and select **View Code** to go to the code-behind file.
+1. If your test doesn't contain any coded steps, click the <a href="/code-in-test/features-in-code#Code-Behind-File" target="_blank">Add Code-Behind File button</a>.
+2. If you test contains a coded step, right click it and select **View Code** to go to the code-behind file.
 
-![View code][3]
+![View code](images/fig3.png)
 
-3.Write the override definition inside the BaseTest (but not inside another method/coded step).
+3. Write the override definition inside the BaseTest (but not inside another method/coded step).
 
 ### The Override Definition
 
 The TestResult object lets you access the test results from the run that just finished (i.e. the one invoking the **OnAfterTestCompleted** method):
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public override void OnAfterTestCompleted(TestResult result)
     {
         string overall = Convert.ToString(result.Result);
         Log.WriteLine(overall);
         result.ExportToResultFile(@"C:\", result.TestName);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Overrides Sub OnAfterTestCompleted(result As TestResult)
         Dim overall As String = Convert.ToString(result.Result)
         Log.WriteLine(overall)
         result.ExportToResultFile("C:\", result.TestName)
     End Sub
-    {{endregion}}
+````
 
 The **OnBeforeTestStarted** method allows you to perform actions required for the initialization of your test (starting scripts, etc.):
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public override void OnBeforeTestStarted()
     {
         this.ExecuteTest("Folder1\\WebTest2.tstest");
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Overrides Sub OnBeforeTestStarted()
         Me.ExecuteTest("Folder1\WebTest2.tstest")
     End Sub
-    {{endregion}}
+````
 
 You can use logic from assemblies in these methods. First add references to the assemblies.
 
-[3]: images/custom-scripts-before-after/fig3.png
+
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/data-driven-find-expressions.md b/docs-teststudiodev/code-in-test/coded-samples/general/data-driven-find-expressions.md
index 6cf09b55..d8a52a2c 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/data-driven-find-expressions.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/data-driven-find-expressions.md
@@ -12,38 +12,29 @@ position: 1
 
 The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/combobox/index" target="_blank">Telerik demo site</a>.
 
-1.Record a *Navigate* to step.
-2.Open the drop-down for the ComboBox.
-3.Locate the parent element in the DOM Explorer (see below). Here the Unordered List holds all the child List Item elements. Right click it and select **Add to Project Elements**.
+1. Record a *Navigate* to step.
+2. Open the drop-down for the ComboBox.
+3. Locate the parent element in the DOM Explorer (see below). Here the Unordered List holds all the child List Item elements. Right click it and select **Add to Project Elements**.
 
-![Add to Project][1]
+	![Add to Project](images/data-driven-find-expressions/fig1.png)
 
-4.Insert a <a href="/code-in-test/features-in-code#Coded-Step" target="_blank">Coded Step</a>.
-5.Use the <a href="/features/data-driven-testing/local-data-driven-test" target="_blank">local data</a> to enter values for the find expression.
-6.We will use the Find.ByContent method in the coded step. More information can be found in our <a href="/code-in-test/element-identification/finding-page-elements" target="_blank">Finding Page Elements</a> article. Here's the code for our Script Step:
-
-#### __[C#]__
-
-	{{region }}
+4. Insert a <a href="/code-in-test/features-in-code#Coded-Step" target="_blank">Coded Step</a>.
+5. Use the <a href="/features/data-driven-testing/local-data-driven-test" target="_blank">local data</a> to enter values for the find expression.
+6. We will use the Find.ByContent method in the coded step. More information can be found in our <a href="/code-in-test/element-identification/finding-page-elements" target="_blank">Finding Page Elements</a> article. Here's the code for our Script Step:
 
+````C#
 	HtmlListItem listItem = Pages.TelerikExtensionsForASP.UnorderedList.Find.ByContent<HtmlListItem>(Data["Col1"].ToString());
 	Assert.IsNotNull(listItem);
 	listItem.Click();
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
-
+````
+````VB
 	Dim listItem As HtmlListItem = Pages.TelerikExtensionsForASP.UnorderedList.Find.ByContent(Of HtmlListItem)(Data("Col1").ToString())
 	Assert.IsNotNull(listItem)
 	listItem.Click()
-	{{endregion}}
+````
+
+7. Test Studio Dev uses the data table to find the element in the list, performs an Assert on it, and then clicks it.
 
-7.Test Studio Dev uses the data table to find the element in the list, performs an Assert on it, and then clicks it.
+![Execute test](images/data-driven-find-expressions/fig3.png)
 
-![Execute test][3]
 
-[1]: images/data-driven-find-expressions/fig1.png
-[2]: images/data-driven-find-expressions/fig2.png
-[3]: images/data-driven-find-expressions/fig3.png
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/execution-extensions.md b/docs-teststudiodev/code-in-test/coded-samples/general/execution-extensions.md
index 2074a9a5..0b39e019 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/execution-extensions.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/execution-extensions.md
@@ -29,52 +29,38 @@ Also add the following **.NET** references:
 3.&nbsp; Add the following using statements to the class file:
 
 	
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.IO;
     using System.Data;
     using System.Data.OleDb;
     using System.Windows.Forms;
     using ArtOfTest.WebAii.Design.Execution;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.IO
     Imports System.Data
     Imports System.Data.OleDb
     Imports System.Windows.Forms
     Imports ArtOfTest.WebAii.Design.Execution
-    {{endregion}}
+````
 
 4.&nbsp; The *ArtOfTest.WebAii.Design.Execution* namespace contains an IExecutionExtension that our class needs to implement:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     namespace ClassLibrary1
     {
         public class Class1 : IExecutionExtension
         {
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Namespace ClassLibrary1
         Public Class Class1
             Implements IExecutionExtension
         End Class
     End Namespace
-    {{endregion}}
+````
 
 5.&nbsp; Right click on **IExecutionExtension** and select **Implement Interface > Implement Interface**. This displays all the methods and notifications exposed by Test Studio. Here are definitions for each **IExecutionExtension** member:
 
@@ -82,10 +68,7 @@ Also add the following **.NET** references:
 
  - The rest of the functions, which you're not using, should be left empty (remove *throw new NotImplementedException*).
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     namespace ClassLibrary1
     {
         public class Class1 : IExecutionExtension
@@ -139,12 +122,8 @@ Also add the following **.NET** references:
             #endregion
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Namespace ClassLibrary1
         Public Class Class1
             Implements IExecutionExtension
@@ -191,7 +170,7 @@ Also add the following **.NET** references:
             #End Region
         End Class
     End Namespace
-    {{endregion}}
+````
 
 A few notes about the code above:
 
@@ -215,10 +194,7 @@ Let's see an example using the **OnInitializeDataSource** method. This assumes t
 
 1.&nbsp; Add the following code to that method:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public System.Data.DataTable OnInitializeDataSource(ExecutionContext executionContext)
     {
         System.Data.DataTable table = null;
@@ -247,12 +223,8 @@ Let's see an example using the **OnInitializeDataSource** method. This assumes t
         thread.Join();
         return table;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Function OnInitializeDataSource(executionContext As ExecutionContext) As System.Data.DataTable
         Dim table As System.Data.DataTable = Nothing
         Dim thread = New System.Threading.Thread(Function(obj) 
@@ -276,14 +248,11 @@ Let's see an example using the **OnInitializeDataSource** method. This assumes t
         thread.Join()
         Return table
     End Function
-    {{endregion}}
+````
 
 2.&nbsp; Now add the following *ImportExcelXLS* method within the same public class:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     private static DataSet ImportExcelXLS(string FileName, bool hasHeaders)
     {
         string HDR = hasHeaders ? "Yes" : "No";
@@ -320,12 +289,8 @@ Let's see an example using the **OnInitializeDataSource** method. This assumes t
         }
         return output;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Private Shared Function ImportExcelXLS(FileName As String, hasHeaders As Boolean) As DataSet
         Dim HDR As String = If(hasHeaders, "Yes", "No")
         Dim strConn As String = Nothing
@@ -355,7 +320,7 @@ Let's see an example using the **OnInitializeDataSource** method. This assumes t
         End Using
         Return output
     End Function
-    {{endregion}}
+````
 
 3.&nbsp; Rebuild the class library, copy the resulting DLL file, and paste it into the Plugins folder (overwriting any other existing class library file).
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/extend-basewebaiitest-class.md b/docs-teststudiodev/code-in-test/coded-samples/general/extend-basewebaiitest-class.md
index 79308837..c72d8fe6 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/extend-basewebaiitest-class.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/extend-basewebaiitest-class.md
@@ -10,85 +10,71 @@ A possible scenario is to use same functionality in most of the tests in the pro
 
 The steps to implement such approach are as follows:
 
-1.Create a new project
+1. Create a new project
 
-2.Add a <a href="/code-in-test/features-in-code#Custom-Code" target="_blank">stand alone class file</a> *ExtendedBaseWebAiiTest* which inherits from the abstract class *BaseWebAiiTest*. A sample implementation of such file containing the method *PrintMessage()* is listed below:
+2. Add a <a href="/code-in-test/features-in-code#Custom-Code" target="_blank">stand alone class file</a> *ExtendedBaseWebAiiTest* which inherits from the abstract class *BaseWebAiiTest*. A sample implementation of such file containing the method *PrintMessage()* is listed below:
 
-#### __[C#]__
+````C#
+using ArtOfTest.WebAii.Design;
 
-	{{region }}
-
-		using ArtOfTest.WebAii.Design;
-		
-		namespace ExtendBaseWebAiiTestProject
+namespace ExtendBaseWebAiiTestProject
+{
+	public class ExtendedBaseWebAiiTest : BaseWebAiiTest
+	{
+		// this method will be available in each test code behind file coded step
+		public void PrintMessage(string message)
 		{
-			public class ExtendedBaseWebAiiTest : BaseWebAiiTest
-			{
-				// this method will be available in each test code behind file coded step
-				public void PrintMessage(string message)
-				{
-					Log.WriteLine(message);
-				}
-			}
+			Log.WriteLine(message);
 		}
-		{{endregion}}
-
-#### __[VB]__
+	}
+}
+````
+````VB	
+Imports ArtOfTest.WebAii.Design
 
-	{{region }}
+Namespace ExtendBaseWebAiiTestProject
 
-		Imports ArtOfTest.WebAii.Design
+	Public Class ExtendedBaseWebAiiTest
+		Inherits BaseWebAiiTest
 		
-		Namespace ExtendBaseWebAiiTestProject
-		
-			Public Class ExtendedBaseWebAiiTest
-				Inherits BaseWebAiiTest
-				
-				Public Sub PrintMessage(ByVal message As String)
-					Log.WriteLine(message)
-				End Sub
-			End Class
-		End Namespace
-		{{endregion}}
-
-3.Open the code behind file of any test and modify its class to inherit the newly created _ExtendedBaseWebAiiTest_ class and the _PrintMessage()_ method defined in it will be available for the test. 
-
-#### __[C#]__
-
-	{{region }}
-
-		using ArtOfTest.WebAii.Core;
-		using ArtOfTest.WebAii.Design.Execution;
-		
-		namespace ExtendBaseWebAiiTestProject
+		Public Sub PrintMessage(ByVal message As String)
+			Log.WriteLine(message)
+		End Sub
+	End Class
+End Namespace
+````
+
+3. Open the code behind file of any test and modify its class to inherit the newly created _ExtendedBaseWebAiiTest_ class and the _PrintMessage()_ method defined in it will be available for the test. 
+
+````C#	
+using ArtOfTest.WebAii.Core;
+using ArtOfTest.WebAii.Design.Execution;
+
+namespace ExtendBaseWebAiiTestProject
+{
+	public class WebTest : ExtendedBaseWebAiiTest
+	{
+		[CodedStep(@"Print From ExtendedBaseAiiTest Method")]
+		public void PrintCodedStep()
 		{
-			public class WebTest : ExtendedBaseWebAiiTest
-			{
-				[CodedStep(@"Print From ExtendedBaseAiiTest Method")]
-				public void PrintCodedStep()
-				{
-					this.PrintMessage("This is printed from extended base class method");
-				}
-			}
+			this.PrintMessage("This is printed from extended base class method");
 		}
-		{{endregion}}
+	}
+}
+````
+````VB	
+Imports ArtOfTest.WebAii.Core
+Imports ArtOfTest.WebAii.Design.Execution
 
-#### __[VB]__
+Namespace ExtendBaseWebAiiTestProject
 
-	{{region }}
-
-		Imports ArtOfTest.WebAii.Core
-		Imports ArtOfTest.WebAii.Design.Execution
-		
-		Namespace ExtendBaseWebAiiTestProject
+	Public Class WebTest
+		Inherits ExtendedBaseWebAiiTest
 		
-			Public Class WebTest
-				Inherits ExtendedBaseWebAiiTest
-				
-				<CodedStep("Print From ExtendedBaseAiiTest Method")>
-				Public Sub PrintCodedStep()
-					Me.PrintMessage("This is printed from extended base class method")
-				End Sub
-			End Class
-		End Namespace
-		{{endregion}}
+		<CodedStep("Print From ExtendedBaseAiiTest Method")>
+		Public Sub PrintCodedStep()
+			Me.PrintMessage("This is printed from extended base class method")
+		End Sub
+	End Class
+End Namespace
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/external-log-file.md b/docs-teststudiodev/code-in-test/coded-samples/general/external-log-file.md
index 0f2589b6..eac682eb 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/external-log-file.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/external-log-file.md
@@ -20,10 +20,7 @@ We have code samples for two file types:
 
 ## Text File
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public IList<AutomationStepResult> stepResults { get; set; }
     public override void OnAfterTestCompleted(TestResult result)
     {
@@ -42,12 +39,8 @@ We have code samples for two file types:
         file.WriteLine("Total Test Result: "+ overall);
         file.Close();
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Property stepResults() As IList(Of AutomationStepResult)
         Get
             Return m_stepResults
@@ -73,7 +66,7 @@ We have code samples for two file types:
         file.WriteLine("Total Test Result: " & overall)
         file.Close()
     End Sub
-    {{endregion}}
+````
 
 Finally you'll need to add an Assembly Reference for *ArtOfTest.Common.Design*. If it is already present, remove it and add it again. Add it from the \**Test Studio\Bin** directory:
 
@@ -85,10 +78,7 @@ Finally you'll need to add an Assembly Reference for *ArtOfTest.Common.Design*.
 
 * You'll need to create the Excel file on disk first.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public override void OnAfterTestCompleted(TestResult result)
     {
         string passed = Convert.ToString(result.TotalPassedSteps);
@@ -123,12 +113,8 @@ Finally you'll need to add an Assembly Reference for *ArtOfTest.Common.Design*.
         GC.Collect();
         System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Overrides Sub OnAfterTestCompleted(result As TestResult)
         Dim passed As String = Convert.ToString(result.TotalPassedSteps)
         Dim notRunSteps As String = Convert.ToString(result.TotalNumberOfNotRunSteps)
@@ -161,4 +147,4 @@ Finally you'll need to add an Assembly Reference for *ArtOfTest.Common.Design*.
         GC.Collect()
         System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp)
     End Sub
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/extracted-variables-in-code.md b/docs-teststudiodev/code-in-test/coded-samples/general/extracted-variables-in-code.md
index fa6c276b..37e21534 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/extracted-variables-in-code.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/extracted-variables-in-code.md
@@ -4,38 +4,24 @@ page_title: Get/Set Extracted Variables in Code - Test Studio Dev Documentation
 description: Get/Set Extracted Variables in Code
 position: 1
 ---
-# Get/Set Extracted Variables in Code #
+# Get/Set Extracted Variables in Code
 
 Use the *SetExtractedValue()* method to set the value of an extraction variable so it can be used later in a standard action or verification step:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     string area = "Atlanta";
     SetExtractedValue("extractedID", area);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim area As String = "Atlanta"
     SetExtractedValue("extractedID", area)
-    {{endregion}}
+````
 
 Use the *GetExtractedValue()* method to use the extracted variable in a coded step:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     object myData = GetExtractedValue("varname");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim myData As Object = GetExtractedValue("varname")
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/fail-the-test.md b/docs-teststudiodev/code-in-test/coded-samples/general/fail-the-test.md
index 3f75f0e0..5907ae90 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/fail-the-test.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/fail-the-test.md
@@ -14,10 +14,7 @@ This is most easily achieved with standard (and non-coded) <a href="/features/re
 
 The following code contains basic examples for demonstration purposes:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-mvc/grid");
     HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
     Assert.IsNotNull(table);
@@ -25,12 +22,8 @@ The following code contains basic examples for demonstration purposes:
     int r = table.Rows.Count;
     Assert.AreEqual(r, 10);
     Assert.IsTrue(table.InnerText.Contains("Mario"));
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-mvc/grid")
     Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
     Assert.IsNotNull(table)
@@ -38,16 +31,13 @@ The following code contains basic examples for demonstration purposes:
     Dim r As Integer = table.Rows.Count
     Assert.AreEqual(r, 10)
     Assert.IsTrue(table.InnerText.Contains("Mario"))
-    {{endregion}}
+````
 
 ## Throw New Exception
 
 When an *Assert* statement is not appropriate, you can throw your own exception. In the example below, the *FileNotFoundException* will result in failure if the specified file does not exist on disk.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     string fileName = "C:\\test.txt";
     
     if (System.IO.File.Exists(fileName) == true)
@@ -58,12 +48,8 @@ When an *Assert* statement is not appropriate, you can throw your own exception.
     {
         throw new System.IO.FileNotFoundException("File does not exist: ", fileName);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim fileName As String = "C:\test.txt"
     
     If System.IO.File.Exists(fileName) = True Then
@@ -71,4 +57,4 @@ When an *Assert* statement is not appropriate, you can throw your own exception.
     Else
         Throw New System.IO.FileNotFoundException("File does not exist: ", fileName)
     End If
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/access-sql-database/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/access-sql-database/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/custom-scripts-before-after/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/data-driven-find-expressions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/fig3.png
new file mode 100644
index 00000000..0285effd
Binary files /dev/null and b/docs-teststudiodev/code-in-test/coded-samples/general/images/fig3.png differ
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/log-error-dialogs/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/log-error-dialogs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/non-iterative-data-driving/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/non-iterative-data-driving/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/run-against.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/run-against.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/general/images/write-into-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/invoke-application.md b/docs-teststudiodev/code-in-test/coded-samples/general/invoke-application.md
index 1681d797..734fe1d7 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/invoke-application.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/invoke-application.md
@@ -4,33 +4,26 @@ page_title: How to Invoke an Application - Test Studio Dev Documentation
 description: How to Invoke an Application
 position: 1
 ---
-#How to Invoke an Application#
+# How to Invoke an Application
 
 I want to invoke a desktop application (i.e. an .exe file) from a test step.
 
-##Solution##
+## Solution
 
 You can write your own code in a <a href="/code-in-test/features-in-code#Coded-Step" target="_blank">coded step</a> that triggers the application you need. Here's a simple example taken from <a href="http://www.csharp-station.com/HowTo/ProcessStart.aspx" target="_blank">this article</a>:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     System.Diagnostics.Process notePad = new System.Diagnostics.Process();
     notePad.StartInfo.FileName   = "notepad.exe";
     notePad.StartInfo.Arguments = @"c:\myText.txt";
     notePad.Start();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim notePad As New System.Diagnostics.Process()
     notePad.StartInfo.FileName = "notepad.exe"
     notePad.StartInfo.Arguments = "c:\myText.txt"
     notePad.Start()
-    {{endregion}}
+````
 
 * In the above sample, **C:\myText.txt** is the argument fed to **notepad.exe**. If you want to test this sample code, you'll need to create this file on your local disk first. Otherwise, the notepad application will throw a *file can't be found* error.
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/log-clipboard-text.md b/docs-teststudiodev/code-in-test/coded-samples/general/log-clipboard-text.md
index 64c89438..d8c0eb24 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/log-clipboard-text.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/log-clipboard-text.md
@@ -4,18 +4,15 @@ page_title: Log Clipboard Text - Test Studio Dev Documentation
 description: Log Clipboard Text
 position: 1
 ---
-#Log Clipboard Text#
+# Log Clipboard Text
 
 *My test copies text into the Clipboard and I would like to log its content.*
 
-##Solution##
+## Solution
  
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the Dynamic Pages Reference region:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Windows.Forms;
     using System.Threading;
     
@@ -47,12 +44,8 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             }
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Windows.Forms
     Imports System.Threading
     
@@ -80,5 +73,5 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             End Sub
         End Class
     End Namespace
-    {{endregion}}
+````
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/log-error-dialogs.md b/docs-teststudiodev/code-in-test/coded-samples/general/log-error-dialogs.md
index 621acdf9..46743747 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/log-error-dialogs.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/log-error-dialogs.md
@@ -4,13 +4,13 @@ page_title: Log Error Dialogs - Test Studio Dev Documentation
 description: Log Error Dialogs
 position: 1
 ---
-#Log Error Dialogs#
+# Log Error Dialogs
 
 *My application can potentially display a dialog containing an error message during test execution. The dialog can appear multiple times and will not always appear at the same point in the test, therefore I cannot use a standard Dialog Handler step.
  
 I want to capture these error messages and automatically handle these dialogs if they appear.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The stipulation is that the dialog is displayed the same way and has the same title in each browser:
 
@@ -24,10 +24,7 @@ This is possible with a coded solution. The stipulation is that the dialog is di
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the Dynamic Pages Reference region:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Threading;
     using System.Windows.Forms;
     using ArtOfTest.WebAii.Win32.Dialogs;
@@ -70,12 +67,8 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             }
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Threading
     Imports System.Windows.Forms
     Imports ArtOfTest.WebAii.Win32.Dialogs
@@ -113,6 +106,6 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             End Sub
         End Class
     End Namespace
-    {{endregion}}
+````
 
 [1]: images/log-error-dialogs/fig1.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/mouse-wheel-scroll.md b/docs-teststudiodev/code-in-test/coded-samples/general/mouse-wheel-scroll.md
index 63f4e99e..8058eb22 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/mouse-wheel-scroll.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/mouse-wheel-scroll.md
@@ -4,25 +4,18 @@ page_title: Mouse Wheel Scroll - Test Studio Dev Documentation
 description: Mouse Wheel Scroll
 position: 1
 ---
-#Mouse Wheel Scroll#
+# Mouse Wheel Scroll
 
 *I need to invoke desktop mouse scroll actions on an HTML or Silverlight element (typically a scroll bar).*
 
-##Solution##
+## Solution
 
 This is doable with a coded solution. The code is desktop-based, which means it is not associated with an element in your Test Project. Because of this you will need to make sure that the intended target element has focus within the browser before the attempted mouse scroll action. Typically you can give an element focus by invoking a mouse click on it (via regular, non-coded step). Here's an example:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Manager.Desktop.Mouse.TurnWheel(100, MouseWheelTurnDirection.Backward);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Manager.Desktop.Mouse.TurnWheel(100, MouseWheelTurnDirection.Backward)
-    {{endregion}}
+````
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/non-iterative-data-driving.md b/docs-teststudiodev/code-in-test/coded-samples/general/non-iterative-data-driving.md
index 6bb72ac0..fb6a0055 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/non-iterative-data-driving.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/non-iterative-data-driving.md
@@ -4,15 +4,15 @@ page_title: Non-iterative Data Driving - Test Studio Dev Documentation
 description: Non-iterative Data Driving
 position: 1
 ---
-#Non-iterative Data Driving#
+# Non-iterative Data Driving
 
 *Is there a way to data drive a step in a test script so that each time the script is run, the test step will select a different sequential row from the data source?*
 
-##Solution##
+## Solution
 
 The solution is to save the number of the row into an XML file. Each time you execute the test, read the number of the row from the XML file and tell Test Studio to use this row from your data source.
 
-1.&nbsp; Create an XML file which will contain the row number.
+1. Create an XML file which will contain the row number.
 
 1.1 Right-click somewhere in the project folder and select **New > Text Document**. Rename it to "IterationIndex.xml".
 
@@ -20,18 +20,18 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 1.3 Write the following code into the file:
 
-```XML
+````XML
 	<?xmlversion="1.0" encoding="UTF-8"?>
 		<IterationValue> 
 		<numVal>0</numVal>
 	</IterationValue>
-```
+````
 
-2.&nbsp; Create your data source, if you don't have one already. In my case this is an Excel file called "foo.xlsx" containing numbers from 1 to 20.
+2. Create your data source, if you don't have one already. In my case this is an Excel file called "foo.xlsx" containing numbers from 1 to 20.
 
-![File][1]
+![File](images/non-iterative-data-driving/fig1.png)
 
-3.&nbsp; Open or create your project in Test Studio.
+3. Open or create your project in Test Studio.
 
 3.1 Start new project or open existing project.
 
@@ -47,10 +47,9 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 3.5 Create a method which will save the row number into the XML file:
 
-#### __[C#]__
-
-	{{region }}
+````C#
 
+	
 	public void SaveValue(int numVal)
 	{
 		string path = @"C:\Box\NextRowOnEachRun\IterationValue.xml";
@@ -58,26 +57,23 @@ The solution is to save the number of the row into an XML file. Each time you ex
 		e.Add(new XElement("numVal", numVal));
 		e.Save(path);
 	}
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
+````
+````VB
 
+	
 	Public Sub SaveValue(numVal As Integer)
 		Dim path As String = "C:\Box\NextRowOnEachRun\IterationValue.xml"
 		Dim e As New XElement("IterationValue")
 		e.Add(New XElement("numVal", numVal))
 		e.Save(path)
 	End Sub
-	{{endregion}}
+````
 
 3.6 Create a method which will load the row number from the XML file:
 
-#### __[C#]__
-
-	{{region }}
+````C#
 
+	
 	public int LoadValue()
 	{
 		string path = @"C:\Box\NextRowOnEachRun\IterationValue.xml";
@@ -87,12 +83,10 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 		return numVal;
 	}
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
+````
+````VB
 
+	
 	Public Function LoadValue() As Integer
 		Dim path As String = "C:\Box\NextRowOnEachRun\IterationValue.xml"
 		Dim e As XElement = XElement.Load(path)
@@ -101,14 +95,13 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 		Return numVal
 	End Function
-	{{endregion}}
+````
 
 3.7 Create a method which will read the row from the Excel file:
 
-#### __[C#]__
-
-	{{region }}
+````C#
 
+	
 	public string ReadingExcel()
 	{
 		int rowValue = LoadValue();
@@ -130,12 +123,10 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 		return value;
 	}
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
+````
+````VB
 
+	
 	Public Function ReadingExcel() As String
 		Dim rowValue As Integer = LoadValue()
 		Dim input As String = "C:\Box\NextRowOnEachRun\foo.xlsx"
@@ -157,6 +148,5 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 		Return value
 	End Function
-	{{endregion}}
+````
 
-[1]: images/non-iterative-data-driving/fig1.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/override-app-config.md b/docs-teststudiodev/code-in-test/coded-samples/general/override-app-config.md
index 070de884..f9fe13ef 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/override-app-config.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/override-app-config.md
@@ -4,11 +4,11 @@ page_title: Override app.config - Test Studio Dev Documentation
 description: Override app.config
 position: 1
 ---
-#Override the app.config File in a Test Studio Project#
+# Override the app.config File in a Test Studio Project
 
 *I would like Visual Studio to load the app.config file to get its run-time configuration settings.*
 
-##Solution##
+## Solution
 
 > The app.config only applies to projects in Visual Studio as explained <a href="http://msdn.microsoft.com/en-us/library/a65txexh.aspx" target="_blank">here</a>.
 
@@ -20,10 +20,7 @@ However, this doesn't work with a default Test Studio Dev project. A Test Studio
 
 * *System.Configuration*
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Assembly me = Assembly.GetExecutingAssembly();
     Configuration config = ConfigurationManager.OpenExeConfiguration(me.ManifestModule.Assembly.Location);
     
@@ -32,12 +29,8 @@ However, this doesn't work with a default Test Studio Dev project. A Test Studio
     string pw = config.AppSettings.Settings["Pass"].Value;
     string UserId = config.AppSettings.Settings["UserId"].Value;
     string conn = config.ConnectionStrings.ConnectionStrings["ConnectionString"].ConnectionString;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim [me] As Assembly = Assembly.GetExecutingAssembly()
     Dim config As Configuration = ConfigurationManager.OpenExeConfiguration([me].ManifestModule.Assembly.Location)
     
@@ -46,4 +39,4 @@ However, this doesn't work with a default Test Studio Dev project. A Test Studio
     Dim pw As String = config.AppSettings.Settings("Pass").Value
     Dim UserId As String = config.AppSettings.Settings("UserId").Value
     Dim conn As String = config.ConnectionStrings.ConnectionStrings("ConnectionString").ConnectionString
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/random-row.md b/docs-teststudiodev/code-in-test/coded-samples/general/random-row.md
index f95f0d4b..985eb7b7 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/random-row.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/random-row.md
@@ -4,11 +4,11 @@ page_title: Random Row - Test Studio Dev Documentation
 description: Random Row
 position: 1
 ---
-#Random Row from Excel Data Source#
+# Random Row from Excel Data Source
 
 *Is there a way to data drive a step in a test script so that each time the script is run, the test step will select a random row from the Excel data source?*
 
-##Solution##
+## Solution
 
 In code, generate a random number based on the number of rows. Then use the corresponding text from that row's cell in the applicable test step.
 
@@ -18,10 +18,7 @@ In code, generate a random number based on the number of rows. Then use the corr
 
 	* **Note:** Ensure you <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">Add an Assembly Reference</a> to *Microsoft.Office.Interop.Excel*. You can download a version of that file on Microsoft's website that matches your version of MS Office.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Random random = new Random();
     int num = random.Next(1, 6);
     
@@ -36,12 +33,8 @@ In code, generate a random number based on the number of rows. Then use the corr
     app = null;
     
     Pages.Bing.SbFormQText.Text = value;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim random As New Random()
     Dim num As Integer = random.[Next](1, 6)
     
@@ -58,5 +51,5 @@ In code, generate a random number based on the number of rows. Then use the corr
     app = Nothing
     
     Pages.Bing.SbFormQText.Text = value
-    {{endregion}}
+````
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/send-keystrokes.md b/docs-teststudiodev/code-in-test/coded-samples/general/send-keystrokes.md
index 62555940..735cf64b 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/send-keystrokes.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/send-keystrokes.md
@@ -4,18 +4,15 @@ page_title: Send Keystorkes - Test Studio Dev Documentation
 description: Send Keystorkes
 position: 1
 ---
-#Send Keystorkes#
+# Send Keystorkes
 
 *I want to send keystrokes like Alt+F4.*
 
-##Solution##
+## Solution
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the *Dynamic Pages Reference* region:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Windows.Forms;
     
     namespace TestProject8
@@ -30,12 +27,8 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             }
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Windows.Forms
     
     Namespace TestProject8
@@ -50,20 +43,17 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             End Sub
         End Class
     End Namespace
-    {{endregion}}
+````
 
 > <a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.sendkeys(v=vs.110).aspx" target="_blank">Here</a> you can find the list with key codes.
 
 *I want to perform multi-select while holding down the Ctrl key.*
 
-##Solution##
+## Solution
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the *Dynamic Pages Reference* region:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Windows.Forms;
     
     namespace TestProject8
@@ -84,12 +74,8 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             }
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Windows.Forms
     
     Namespace TestProject8
@@ -109,5 +95,5 @@ Here is the full code-behind file, excluding the standard *using/Imports* statem
             End Sub
         End Class
     End Namespace
-    {{endregion}}
+````
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/skip-iteration.md b/docs-teststudiodev/code-in-test/coded-samples/general/skip-iteration.md
index 13e4af01..30b366f2 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/skip-iteration.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/skip-iteration.md
@@ -4,11 +4,11 @@ page_title: Skip Iteration - Test Studio Dev Documentation
 description: Skip Iteration
 position: 1
 ---
-#How to Skip a Specific Iteration While Executing a Data-Bound Test#
+# How to Skip a Specific Iteration While Executing a Data-Bound Test
 
 *You're executing a data-driven test. You need to skip one or more iterations based on a specific condition.*
 
-##Solution##
+## Solution
 
 You'll need to create two tests. Let's call them **MainTest** and **Subtest**. Put the actual test steps you want to invoke (i.e. your test) in Subtest.
 
@@ -16,39 +16,25 @@ Now it's time to bind your test to a data source. Make **MainTest** (which is st
 
 After this add **Subtest** via the <a href="/features/custom-steps/test-as-step" target="_blank">Test as Step</a> feature in MainTest. However, we're going to do that in a coded step. Here's what the code looks like: 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     this.ExecuteTest("Subtest.tstest");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Me.ExecuteTest("Subtest.tstest")
-    {{endregion}}
+````
 
 For each iteration of **MainTest**, Test Studio will attempt to implement this code and run **SubTest**. Now we can implement conditional logic which determines whether we execute the above logic. In effect, this will control whether a given iteration executes the **SubTest**. If it doesn't, the iteration is effectively skipped - it will invoke no actions of any consequence. We'll skip the iteration even though it won't seem so from **MainTest**'s point of view (i.e. all the iterations will be listed in **MainTest**'s Log file).
  
 Let's say we want to implement a data-driven test that navigates to <a href="http://www.random.org/" target="_blank">random.org</a>, generates a random number, and executes some steps if the number is even. First we record the required steps in MainTest. A step will Extract the generated number in a variable we're going to name num. Now we check whether this value is even and execute SubTest if it is:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     if (Convert.ToInt16(this.GetExtractedValue("num")) % 2 == 0 )
     {
         this.ExecuteTest("SubTest.tstest");
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     If Convert.ToInt16(Me.GetExtractedValue("num")) Mod 2 = 0 Then
         Me.ExecuteTest("SubTest.tstest")
     End If
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/verify-not-empty.md b/docs-teststudiodev/code-in-test/coded-samples/general/verify-not-empty.md
index eab3a5d7..8a85d1f6 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/verify-not-empty.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/verify-not-empty.md
@@ -4,27 +4,21 @@ page_title: Verify Not Empty - Test Studio Dev Documentation
 description: Verify Not Empty
 position: 1
 ---
-#Verify Not Empty#
+# Verify Not Empty
 
 *I would like to verify the text content of an element is not empty. In other words, that it contains one or more characters.*
 
 This is possible with a coded solution. The example below is against <a href="http://www.w3schools.com/html/html_tables.asp" target="_blank">this W3Schools site</a>.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlTable table = Find.ByTagIndex<HtmlTable>("table", 0);
     HtmlTableRow row = table.Rows[0];
     HtmlTableCell cell = row.Cells[1];
     
     Log.WriteLine(cell.TextContent);
     Assert.IsTrue(cell.TextContent.Length > 0);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }} 
+````
+````VB
 
     Dim table As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
     Dim row As HtmlTableRow = table.Rows(0)
@@ -32,4 +26,4 @@ This is possible with a coded solution. The example below is against <a href="ht
     
     Log.WriteLine(cell.TextContent)
     Assert.IsTrue(cell.TextContent.Length > 0)
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/general/write-into-data-source.md b/docs-teststudiodev/code-in-test/coded-samples/general/write-into-data-source.md
index e6ff2d88..43b68f14 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/general/write-into-data-source.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/general/write-into-data-source.md
@@ -4,11 +4,11 @@ page_title: Write into Data Source - Test Studio Dev Documentation
 description: Write into Data Source
 position: 1
 ---
-#Write into Data Source#
+# Write into Data Source
 
 *I have a data driven test that checks whether a specific condition is met. I'd like to write a message into each corresponding row based on a condition.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. Here's an example:
 
@@ -16,17 +16,14 @@ Let's automate <a href="http://www.checkdomain.com/" target ="_blank">checkdomai
 
 <table id="no-table">
 	<tr>
-		<td>![Before Test Run][1] <br><br>**Before Test Run**</td>
-		<td>![After Test Run][2] <br><br>**After Test Run**</td>
+		<td><img src="images/write-into-data-source/fig1.png" alt="Before Test Run" /> <br><br>**Before Test Run**</td>
+		<td><img src="images/write-into-data-source/fig2.png" alt="After Test Run" /> <br><br>**After Test Run**</td>
 	</tr>
 <table>
 
 The test needs to navigate to checkdomain.com, enter the domain for the respective iteration and click on Submit. Add a coded step and insert the below code:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     string dataSourcePath = this.ExecutionContext.DeploymentDirectory + @"\Data\domainResults.xlsx";
     string myPath = "C:\\domainResults.xlsx";
     
@@ -60,11 +57,8 @@ The test needs to navigate to checkdomain.com, enter the domain for the respecti
     excelApp.Quit();
     GC.Collect();
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }} 
+````
+````VB
 
     Dim dataSourcePath As String = Me.ExecutionContext.DeploymentDirectory + "\Data\domainResults.xlsx"
     Dim myPath As String = "C:\domainResults.xlsx"
@@ -96,9 +90,8 @@ The test needs to navigate to checkdomain.com, enter the domain for the respecti
     excelApp.Quit()
     GC.Collect()
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp)
-    {{endregion}}
+````
 
 **Note:** Add an Assembly Reference to Microsoft.Office.Interop.Excel.
 
-[1]: images/write-into-data-source/fig1.png
-[2]: images/write-into-data-source/fig2.png
+
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/add-tag-to-iFrame.md b/docs-teststudiodev/code-in-test/coded-samples/html/add-tag-to-iFrame.md
index 5160bbbc..a4b00c1a 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/add-tag-to-iFrame.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/add-tag-to-iFrame.md
@@ -4,7 +4,7 @@ page_title: Add Tag to iFrame - Test Studio Dev Documentation
 description: Add Tag to iFrame
 position: 1
 ---
-# Add Tag to iFrame #
+# Add Tag to iFrame
 
 To help Test Studio Dev locate your _iframes_, you can add a custom tag to the iframe. You can then add this tag to the <a href="/features/recorder/specific-recording-scenario/frames" target="_blank">frame properties</a> in your test. There are two ways to add a tag to an iframe:
 
@@ -12,50 +12,41 @@ To help Test Studio Dev locate your _iframes_, you can add a custom tag to the i
 
 * Add the tag dynamically in a <a href="/code-in-test/features-in-code#Coded-Step" target="_blank">coded step</a>.
 
-## Add a Tag to a iframe in HTML ##
+## Add a Tag to a iframe in HTML
 
 To add a tag to a iframe in your application's HTML, add the 'testStudioTag' attribute to the frame element. For example:
 
-```HTML
+````HTML
 <iframe src="http://www.example.com" testStudioTag="ExampleTag"></iframe>
-```
+````
 
-## Add a Tag Dynamically in Code ##
+## Add a Tag Dynamically in Code
 
 If it is not possible to add custom tags to your iframes, you can add them at runtime using a coded step.
 
 1. Add the following using directive to your ode-behind file:
 
-#### __[C#]__
-
-		{{region }}
-
-		using ArtOfTest.WebAii.Design.Extensions;
-		{{endregion}}
+````C#
+	using ArtOfTest.WebAii.Design.Extensions;
+````
 
 2. Call the **myFrame()** method on the frame object in a coded step. For example:
 
-#### __[C#]__
-
-	{{region }}
-
-		[CodedStep(@"Tag Frame with 'MyCustomTag'")]
-		public void WebTest1_CodedStep()
+````C#	
+	[CodedStep(@"Tag Frame with 'MyCustomTag'")]
+	public void WebTest1_CodedStep()
+	{
+		Browser myFrame = this.ActiveBrowser.Frames[0] as Browser;
+		if (myFrame != null )
 		{
-			Browser myFrame = this.ActiveBrowser.Frames[0] as Browser;
-			if (myFrame != null )
-			{
-				myFrame.TagFrame("MyCustomTag");
-			}          
-		}
-		{{endregion}}
+			myFrame.TagFrame("MyCustomTag");
+		}          
+	}
+````
 
 To tag a nested iframe, ensure the entire DOM is built, so that Test Studio Dev can access the iframes. For example:
 
-#### __[C#]__
-
-	{{region }}	
-
+````C#
 	[CodedStep(@"Tag nested frame with 'MyCustomTag'")]
 	public void WebTest1_CodedStep()
 	{
@@ -67,7 +58,7 @@ To tag a nested iframe, ensure the entire DOM is built, so that Test Studio Dev
 			myFrame.TagFrame("MyCustomTag");
 		}
 	}
-	{{endregion}}
+````
 
 __See also:__
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/ajax-calendar-random-date.md b/docs-teststudiodev/code-in-test/coded-samples/html/ajax-calendar-random-date.md
index fd3b018f..2e36b50f 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/ajax-calendar-random-date.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/ajax-calendar-random-date.md
@@ -4,18 +4,15 @@ page_title: AJAX Calendar Random Date - Test Studio Dev Documentation
 description: AJAX Calendar Random Date
 position: 1
 ---
-#AJAX Calendar - Random Date Selection#
+# AJAX Calendar - Random Date Selection
 
 *I would like to select a random date from an Ajax Calendar.*
 
-##Solution##
+## Solution
 
 The code below will show you how to select a random date from the Calendar on <a href="http://www.weekendesk.fr/week-end/4398/week-end-a-Courseulles-sur-Mer-Normandie-Week-ends_gourmands" target="_blank">this site</a>.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //We scroll to the date picker so that we can see the click occurring. //Pages.WeekEndCourseullesSurMer.WeekendFormFormTag is a definition which Test Studio Dev automatically generated.
     Pages.WeekEndCourseullesSurMer.WeekendFormFormTag.ScrollToVisible(ScrollToVisibleType.ElementBottomAtWindowBottom);
                 
@@ -52,12 +49,8 @@ The code below will show you how to select a random date from the Calendar on <a
     
     //Click on the node after we reach it in the list.
     l.Value.MouseClick();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     'We scroll to the date picker so that we can see the click occurring. //Pages.WeekEndCourseullesSurMer.WeekendFormFormTag is a definition which Test Studio Dev automatically generated.
     Pages.WeekEndCourseullesSurMer.WeekendFormFormTag.ScrollToVisible(ScrollToVisibleType.ElementBottomAtWindowBottom)
     
@@ -91,4 +84,4 @@ The code below will show you how to select a random date from the Calendar on <a
     
     'Click on the node after we reach it in the list.
     l.Value.MouseClick()
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/async-upload-dialog.md b/docs-teststudiodev/code-in-test/coded-samples/html/async-upload-dialog.md
index 0a77b7b1..5a306e57 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/async-upload-dialog.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/async-upload-dialog.md
@@ -4,14 +4,11 @@ page_title: AsyncUpload Dialog - Test Studio Dev Documentation
 description: AsyncUpload Dialog
 position: 1
 ---
-#How to Handle the AsyncUpload Dialog#
+# How to Handle the AsyncUpload Dialog
 
 There are differences in how RadAsyncUpload is interpreted across different browsers. AsyncUpload is built over Silverlight in Internet Explorer, but rendered in HTML5 in the other browsers (Firefox, Safari, and Chrome). This greatly affects cross-browser UI Automation. You can work around the problem by using a coded step to handle the dialog:
 
-#### __[C#]__
-
-    {{region }} 
-
+````C#
     public void Upload(int index, string filePath)
     {
     FileUploadDialog uploadDialog = new FileUploadDialog(OwnerBrowser, filePath, DialogButton.OPEN, this.UploadDialogTitle);
@@ -23,12 +20,8 @@ There are differences in how RadAsyncUpload is interpreted across different brow
     Manager.Current.DialogMonitor.Stop();
     Manager.Current.DialogMonitor.RemoveDialog(uploadDialog);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Sub Upload(index As Integer, filePath As String)
         Dim uploadDialog As New FileUploadDialog(OwnerBrowser, filePath, DialogButton.OPEN, Me.UploadDialogTitle)
         Manager.Current.DialogMonitor.AddDialog(uploadDialog)
@@ -39,6 +32,6 @@ There are differences in how RadAsyncUpload is interpreted across different brow
         Manager.Current.DialogMonitor.[Stop]()
         Manager.Current.DialogMonitor.RemoveDialog(uploadDialog)
     End Sub
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/common-find-expressions.md b/docs-teststudiodev/code-in-test/coded-samples/html/common-find-expressions.md
index 24782ef4..79cea2ab 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/common-find-expressions.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/common-find-expressions.md
@@ -12,7 +12,7 @@ position: 1
 
 Let's use <a href="http://www.wikipedia.org/" target="_blank">wikipedia.org</a> as an example. First we'll find and click the top bold English link.
 
-![wikipedia][1]
+![wikipedia](images/common-find-expressions/fig1.png)
 
 Here's the HTML code for that link:
 
@@ -28,27 +28,21 @@ Here's the HTML code for that link:
 
 The anchor element has no direct TextContent, so we'll need to locate by a partial match on InnerText:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlAnchor a = Find.ByExpression<HtmlAnchor>("InnerText=~English", "tagname=a");
     Assert.IsNotNull(a);
     a.Click();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }} 
+````
+````VB
 
     Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("InnerText=~English", "tagname=a")
     Assert.IsNotNull(a)
     a.Click()
-    {{endregion}}
+````
 
 If we locate by an exact match on TextContent, the bottom *English* link will found.
 
-![english link][2]
+![english link](images/common-find-expressions/fig2.png)
 
 Here's the HTML code for that link:
 
@@ -58,71 +52,40 @@ Here's the HTML code for that link:
 
 Here's how to locate and click that link:
 
-#### __[C#]__
-
-    {{region }} 
-
+````C#
     HtmlAnchor a = Find.ByExpression<HtmlAnchor>("TextContent=English", "tagname=a");
     Assert.IsNotNull(a);
     a.Click();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("TextContent=English", "tagname=a")
     Assert.IsNotNull(a)
     a.Click()
-    {{endregion}}
+````
 
 The following attributes apply to both links, however Test Studio returns the first HtmlAnchor that matches. In this case, that's the top bold *English* link.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlAnchor a = Find.ByExpression<HtmlAnchor>("tagname=a", "href=//en.wikipedia.org/");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("tagname=a", "href=//en.wikipedia.org/")
-    {{endregion}}
+````
 
 You can find it by xpath:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlAnchor a = Find.ByXPath<HtmlAnchor>("//*[@id=\"www-wikipedia-org\"]/div[5]/div/a[2]");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim a As HtmlAnchor = Find.ByXPath(Of HtmlAnchor)("//*[@id=""www-wikipedia-org""]/div[5]/div/a[2]")
-    {{endregion}}
+````
 
 You can also data drive the find expression:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlAnchor a = Find.ByExpression<HtmlAnchor>("tagname=a", "textcontent=" + Data["Col1"].ToString());
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("tagname=a", "textcontent=" + Data("Col1").ToString())
-    {{endregion}}
-
-[1]: images/common-find-expressions/fig1.png
-[2]: images/common-find-expressions/fig2.png
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/conditional-dialog-handling.md b/docs-teststudiodev/code-in-test/coded-samples/html/conditional-dialog-handling.md
index 1c76fde7..9b6558a9 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/conditional-dialog-handling.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/conditional-dialog-handling.md
@@ -4,18 +4,15 @@ page_title: Conditional Dialog Handling - Test Studio Dev Documentation
 description: Conditional Dialog Handling
 position: 1
 ---
-#Conditionally Handling Dialog#
+# Conditionally Handling Dialog
 
 *I would like to conditionally handle a dialog. If it appears, I'd like to handle it normally. If it doesn't, I'd like to continue with test execution.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The action that potentially triggers the dialog must be included in the code.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ActiveBrowser.NavigateTo("http://www.w3schools.com/js/tryit.asp?filename=tryjs_alert");
     
     //Create the dialog and add it to the monitor
@@ -40,12 +37,8 @@ This is possible with a coded solution. The action that potentially triggers the
     Manager.DialogMonitor.RemoveDialog(ad);
     
     ActiveBrowser.NavigateTo("http://www.bing.com");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveBrowser.NavigateTo("http://www.w3schools.com/js/tryit.asp?filename=tryjs_alert")
     
 
@@ -65,5 +58,5 @@ This is possible with a coded solution. The action that potentially triggers the
     Manager.DialogMonitor.RemoveDialog(ad)
     
     ActiveBrowser.NavigateTo("http://www.bing.com")
-    {{endregion}}
+````
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/dynamic-grid.md b/docs-teststudiodev/code-in-test/coded-samples/html/dynamic-grid.md
index 435b430e..25659f08 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/dynamic-grid.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/dynamic-grid.md
@@ -34,10 +34,7 @@ Going back to Test Studio Dev project, you will notice a new element has appeare
 
 Create a new coded step and add the following lines that go through each (visible) cell in the Grid:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     foreach (HtmlTableRow r in Pages.ClientSideRowSelection.ContentPlaceholder1RadGrid1Table.AllRows)
     {
         foreach(HtmlTableCell c in r.Cells)
@@ -45,7 +42,7 @@ Create a new coded step and add the following lines that go through each (visibl
             Log.WriteLine("Cell found. TextContent:"+c.TextContent);  
         }
     }
-    {{endregion}}
+````
 
 This is C# code, the VB code will follow the same logic only transcribed in the corresponding syntax. Make sure the coded step executes at a point in your test when the page contains the grid fully loaded in the currently active browser.
 
@@ -57,10 +54,7 @@ Let's look at the grid in the below image. Let's imagine we want to get the row
 
 In this example we want to check a checkbox but this could be any kind of control. The code we will use doesn't take into account what the content of the actual cell is: we just click it. Once again we'll be using the definition of the grid that we've stored in the the elements repository. Here's the code:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlTableRow containerRow=null; //The variable that will store the row that contains the name cell and the checkbox cell
 
     foreach (HtmlTableRow r in Pages.ClientSideRowSelection.ContentPlaceholder1RadGrid1Table.AllRows)
@@ -83,12 +77,9 @@ In this example we want to check a checkbox but this could be any kind of contro
     checkbox.ScrollToVisible();
 
     checkbox.MouseClick();
-    {{endregion}}
+````
 
 [1]: images/dynamic-grid/fig1.png
 [2]: images/dynamic-grid/fig2.png
 [3]: images/dynamic-grid/fig3.png
 [4]: images/dynamic-grid/fig4.png
-[5]: images/dynamic-grid/fig5.png
-
-
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/extract-an-attribute.md b/docs-teststudiodev/code-in-test/coded-samples/html/extract-an-attribute.md
index a81f5cfb..d4455aff 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/extract-an-attribute.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/extract-an-attribute.md
@@ -4,46 +4,39 @@ page_title: Extract an Attribute - Test Studio Dev Documentation
 description: Extract an Attribute
 position: 1
 ---
-# Extract an Individual HTML Attribute #
+# Extract an Individual HTML Attribute
 
 *I would like to extract an individual HTML attribute and use it later in the test.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. Note that if you're simply verifying the value for a specific attribute you could use an <a href="/features/recorder/verifications/advanced-verification" target="_blank">Advanced Verification</a>.
 
 HTML elements are formatted the following way:
 
-```HTML
+````HTML
 <tagname attribute="value">content</tagname>
-```
+````
 
-```HTML
+````HTML
 <a href="http://www.google.com" lang="en" id="googleLink">Go to Google</a>
-```
+````
 
 Here's how to set the value of the *lang* attribute (*which is en*) to a string. That string is then set as an <a href="/code-in-test/coded-samples/general/extracted-variables-in-code" target="_blank">extracted value</a> to use later in the test through data binding (either attached to an <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">input value</a> or a <a href="/features/data-driven-testing/attach-columns-verifications" target="_blank">verification</a>).
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlAnchor a = Find.ById<HtmlAnchor>("googleLink");
     Assert.IsNotNull(a);
     
     string atr = a.Attributes.Single(x => x.Name == "lang").Value;
     Log.WriteLine(atr);
     SetExtractedValue("extraction", atr);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim a As HtmlAnchor = Find.ById(Of HtmlAnchor)("googleLink")
     Assert.IsNotNull(a)
     
     Dim atr As String = a.Attributes.[Single](Function(x) x.Name = "lang").Value
     Log.WriteLine(atr)
     SetExtractedValue("extraction", atr)
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/html/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/html/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/html/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/fig4.png b/docs-teststudiodev/code-in-test/coded-samples/html/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/image-comparison.md b/docs-teststudiodev/code-in-test/coded-samples/html/image-comparison.md
index 0ba25394..29fc9be9 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/image-comparison.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/image-comparison.md
@@ -4,18 +4,15 @@ page_title: Image Comparison - Test Studio Dev Documentation
 description: Image Comparison
 position: 1
 ---
-# Perform an Image Comparison in Code #
+# Perform an Image Comparison in Code
 
 *I would like to compare a specific image from the browser to one stored on disk.*
 
-## Solution ##
+## Solution
 
 Here is sample code showing how to perform the image comparison:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlImage img = Find.ById<HtmlImage>("myImageId");
     System.Drawing.Bitmap actualbmp = img.Capture();
     
@@ -23,12 +20,8 @@ Here is sample code showing how to perform the image comparison:
     ArtOfTest.Common.PixelMap actual = ArtOfTest.Common.PixelMap.FromBitmap(actualbmp);
     
     Assert.IsTrue(expected.Compare(actual, 5.0));
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim img As HtmlImage = Find.ById(Of HtmlImage)("myImageId")
     Dim actualbmp As System.Drawing.Bitmap = img.Capture()
 
@@ -36,6 +29,6 @@ Here is sample code showing how to perform the image comparison:
     Dim actual As ArtOfTest.Common.PixelMap = ArtOfTest.Common.PixelMap.FromBitmap(actualbmp)
 
     Assert.IsTrue(expected.Compare(actual, 5.0))
-    {{endregion}}
+````
 
 In the above code I am getting the image of the "myImageId" element from the browser and comparing it to the expected image stored on disk named "myExpected.png". The comparison is allowing a 5% tolerance, meaning there may be up to a 5% difference in the image or else the Assert fails and the test aborts.
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/common-find-expressions/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/common-find-expressions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/common-find-expressions/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/common-find-expressions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig4.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/dynamic-grid/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig2.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig3.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig4.png b/docs-teststudiodev/code-in-test/coded-samples/html/images/jQuery-events-do-not-fire/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/jQuery-events-do-not-fire.md b/docs-teststudiodev/code-in-test/coded-samples/html/jQuery-events-do-not-fire.md
index 8d7c003f..c34098fe 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/jQuery-events-do-not-fire.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/jQuery-events-do-not-fire.md
@@ -12,25 +12,24 @@ Inputting text into <a href="http://www.w3schools.com/jquery/tryit.asp?filename=
 
 <table id="no-table">
 	<tr>
-		<td>![Before Selection][1] </br></br>**Before Selection**</td>
-		<td>![Available Selections][2] </br></br>**Available Selections**</td>
-		<td>![After Selection][3] </br></br>**After Selection**</td>
+		<td><img src="images/jQuery-events-do-not-fire/fig1.png" alt="Before Selection" /> </br></br>**Before Selection**</td>
+		<td><img src="images/jQuery-events-do-not-fire/fig2.png" alt="Available Selections" /> </br></br>**Available Selections**</td>
+		<td><img src="images/jQuery-events-do-not-fire/fig3.png" alt="After Selection" /> </br></br>**After Selection**</td>
 	</tr>
 <table>
 
 This is the HTML for the text input element:
 
-```HTML
+````HTML
 Enter your name: <input class="field" type="text">
-```
+````
 Invoke the script that changes the background color with the following coded step:
 
-#### __[C#]__
-
-	{{region }}
+````C#
 
+	
 	Pages.TryitEditorV220.FrameIframeResult.Text.AsjQueryControl().InvokejQueryEvent(ArtOfTest.WebAii.jQuery.jQueryControl.jQueryControlEvents.change);
-	{{endregion}}
+````
 
 * The guideline is to always pair the two steps together. Immediately after performing the change step (input, radio button, etc.), run the coded step that calls the .change function for that element.
 
@@ -38,6 +37,4 @@ Invoke the script that changes the background color with the following coded ste
 
 * If you have a choice between using id and name of an element, we recommend using id. It is usually a unique value which will make your tests run more reliably. Name is sometimes duplicated, which can cause your test to find and act against the wrong element, since the selector will act on the first element it finds matching the selector criteria.
 
-[1]: images/jQuery-events-do-not-fire/fig1.png
-[2]: images/jQuery-events-do-not-fire/fig2.png
-[3]: images/jQuery-events-do-not-fire/fig3.png
+
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/partial-attributes-search-fails.md b/docs-teststudiodev/code-in-test/coded-samples/html/partial-attributes-search-fails.md
index cf20b66e..752afa0b 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/partial-attributes-search-fails.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/partial-attributes-search-fails.md
@@ -4,42 +4,33 @@ page_title: Partial Attributes Search Fails - Test Studio Dev Documentation
 description:  Partial Attributes Search Fails
 position: 1
 ---
-# Partial Attributes Search by Control Type Fails #
+# Partial Attributes Search by Control Type Fails
 
 _A partial search of control by attribute may return null even with correct partial search syntax._
 
 For example a HtmlInputButton search on the page having a complex ID containing some specific string should be located successfully using the following syntax:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlInputButton button = Find.ById<HtmlInputButton>("~MyButtonIDPart");
-    {{endregion}}
+````
 
 Although the next example works as well:
 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlInputButton button = Find.ById<HtmlInputButton>("SomeButtonIDPart_MyButtonIDPart");
-    {{endregion}}
+````
 
-## Notes ##
+## Notes
 
 The framework locates the first element matching the given attribute search criteria. Next, it compares the control type of the element and returns that element if the control type matches. If it does not, it simply returns null.
 
 In the first example, the framework returns null if there is another element that matches the given attribute search criteria and it is found before the target element. The control type does not match.
 
-## Solution ##
-
-A simple solution is available. Use Find.AllByAttributes<Control Type> overload and return the first (and actually the only completely matching control):
-
-#### __[C#]__
+## Solution
 
-    {{region }}
+A simple solution is available. Use `Find.AllByAttributes<Control Type>` overload and return the first (and actually the only completely matching control):
 
+````C#
     HtmlInputButton button = Find.AllByAttributes<HtmlInputButton>("id=~MyButtonIDPart")[0];
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/radwindow-width-height.md b/docs-teststudiodev/code-in-test/coded-samples/html/radwindow-width-height.md
index 79af0fd0..43e25220 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/radwindow-width-height.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/radwindow-width-height.md
@@ -4,20 +4,17 @@ page_title: RadWindow Width & Height - Test Studio Dev Documentation
 description: RadWindow Width & Height
 position: 1
 ---
-# Getting RadWindow Width and Height #
+# Getting RadWindow Width and Height
 
 *I need to get the RadWindow width or height property.*
 
-## Solution ##
+## Solution
 
 First you need to get a reference to the RadWindow control by ID. Once you get it there are two options for getting the width/height. The first option is to use the relevant width/height properties of the RadWindow. The second is by invoking a straight JavaScript on the page.
 
 Here is the standard approach:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Manager.LaunchNewBrowser();
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx");
     Find.ById<HtmlInputSubmit>("Button3").MouseClick();
@@ -27,12 +24,8 @@ Here is the standard approach:
     
     //First Option
     Assert.AreEqual(300, window.Width);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Manager.LaunchNewBrowser()
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx")
     Find.ById(Of HtmlInputSubmit)("Button3").MouseClick()
@@ -41,14 +34,11 @@ Here is the standard approach:
     Dim window As RadWindow = Find.ById(Of RadWindow)("RadWindowWrapper_RadWindow_ContentTemplate")
 
     Assert.AreEqual(300, window.Width)
-    {{endregion}}
+````
 
 Invoking JavaScript on the page:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Manager.LaunchNewBrowser();
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx");
     Find.ById<HtmlInputSubmit>("Button3").MouseClick();
@@ -59,11 +49,8 @@ Invoking JavaScript on the page:
     //Second Option
     string windowWidth = this.ActiveBrowser.Actions.InvokeScript(String.Format("$telerik.getBounds($find('RadWindow_ContentTemplate').get_popupElement()).width"));
     Assert.AreEqual("300", windowWidth);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }} 
+````
+````VB
 
     Manager.LaunchNewBrowser()
     ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx")
@@ -74,6 +61,6 @@ Invoking JavaScript on the page:
 
     Dim windowWidth As String = Me.ActiveBrowser.Actions.InvokeScript([String].Format("$telerik.getBounds($find('RadWindow_ContentTemplate').get_popupElement()).width"))
     Assert.AreEqual("300", windowWidth)
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/table-searching-paging.md b/docs-teststudiodev/code-in-test/coded-samples/html/table-searching-paging.md
index 32c1000e..1501f50d 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/table-searching-paging.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/table-searching-paging.md
@@ -4,18 +4,15 @@ page_title: Table Searching & Paging - Test Studio Dev Documentation
 description: Table Searching & Paging
 position: 1
 ---
-#HTML Table Searching and Paging#
+# HTML Table Searching and Paging
 
 *I would like to search an HTML table for specific content and continue through the pages until it is found.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/grid/index" target="_blank">Telerik demo site</a>.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
     HtmlSpan next = Find.ByExpression<HtmlSpan>("class=k-icon k-i-arrow-e");
     HtmlAnchor a = Find.ByExpression<HtmlAnchor>("title=Go to the next page");
@@ -54,12 +51,8 @@ This is possible with a coded solution. The example below is against this <a hre
         System.Threading.Thread.Sleep(1000);
         table.Refresh();
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
     Dim [next] As HtmlSpan = Find.ByExpression(Of HtmlSpan)("class=k-icon k-i-arrow-e")
     Dim a As HtmlAnchor =
@@ -93,4 +86,4 @@ This is possible with a coded solution. The example below is against this <a hre
         System.Threading.Thread.Sleep(1000)
         table.Refresh()
     End While
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/table-sum-average.md b/docs-teststudiodev/code-in-test/coded-samples/html/table-sum-average.md
index 3df78817..5364c8e2 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/table-sum-average.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/table-sum-average.md
@@ -4,18 +4,15 @@ page_title: Table Sum & Average - Test Studio Dev Documentation
 description: Table Sum & Average
 position: 1
 ---
-# HTML Table Sum and Average #
+# HTML Table Sum and Average
 
 *I would like to get the sum and the average of the values in a certain column of an HTML table.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. The example below is against <a href="http://www.w3schools.com/html/html_tables.asp" target="_blank">this W3Schools site</a>.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     HtmlTable table = Find.ByTagIndex<HtmlTable>("table", 0);
     
     double r = table.Rows.Count;
@@ -38,12 +35,8 @@ This is possible with a coded solution. The example below is against <a href="ht
     double average = sum / r;
     Log.WriteLine("Average: " + average.ToString());
     Assert.IsTrue(sum == 90);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim table As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
     
     Dim r As Double = table.Rows.Count
@@ -65,6 +58,6 @@ This is possible with a coded solution. The example below is against <a href="ht
     Dim average As Double = sum / r
     Log.WriteLine("Average: " + average.ToString())
     Assert.IsTrue(sum = 90)
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text-chrome.md b/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text-chrome.md
index a3e8d2ea..dff52eb8 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text-chrome.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text-chrome.md
@@ -4,11 +4,11 @@ page_title: Verify Dialog Text In Chrome - Test Studio Dev Documentation
 description: Verify Dialog Text In Chrome
 position: 1
 ---
-#How to Verify Dialog Text (Chrome)#
+# How to Verify Dialog Text (Chrome)
 
 *I would like to verify the text of a <a href="/features/recorder/specific-recording-scenario/dialogs" target="_blank">Dialog</a> that is fired from the browser during test execution.*
 
-##Solution##
+## Solution
 
 This could be achieved in a coded solution. The code will both handle the dialog and verify the text within it. What is used to handle this in Chrome is **<a href="https://msdn.microsoft.com/en-us/library/system.windows.automation.automationelement(v=vs.110).aspx" target="_blank">AutomationElement Class</a>**.  A new AutomationElement object is retrieved for the dialog window referenced by the specified window handle and its node is located. The location of the text may vary depending on the machine used for execution though this is handled in the if..else statement.
 
@@ -21,10 +21,7 @@ This could be achieved in a coded solution. The code will both handle the dialog
 
 The last three could be usually found in *'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\'*.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     [CodedStep(@"New Coded Step")]
             public void WebTest_CodedStep()
             {
@@ -54,12 +51,8 @@ The last three could be usually found in *'C:\Program Files (x86)\Reference Asse
                 // handle the dialog
                 Manager.Desktop.KeyBoard.KeyPress(Keys.Enter);
             }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-    
+````
+````VB    
     <CodedStep("New Coded Step")> _
     Public Sub WebTest_CodedStep()
         System.Threading.Thread.Sleep(1000)
@@ -85,24 +78,17 @@ The last three could be usually found in *'C:\Program Files (x86)\Reference Asse
         ' handle the dialog
         Manager.Desktop.KeyBoard.KeyPress(Keys.Enter)
     End Sub
-    {{endregion}}
+````
 
 Ensure you add the following *using or Imports* statements to the top of the code-behind file:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using System.Windows.Automation;
     using ArtOfTest.Common.Extensions;
     using System.Windows.Forms;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports System.Windows.Automation
     Imports ArtOfTest.Common.Extensions
     Imports System.Windows.Forms
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text.md b/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text.md
index a4473de9..180baa00 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/verify-dialog-text.md
@@ -4,18 +4,15 @@ page_title: Verify Dialog Text - Test Studio Dev Documentation
 description: Verify Dialog Text
 position: 1
 ---
-# How to Verify Dialog Text (Internet Explorer only) #
+# How to Verify Dialog Text (Internet Explorer only)
 
 *I would like to verify the text of a <a href="/features/recorder/specific-recording-scenario/dialogs" target="_blank">Dialog</a> that is fired from the browser during test execution.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution.  The code will both handle the dialog and verify the text within it. The second part uses a <a href="http://msdn.microsoft.com/en-us/library/ms173171(v=vs.80).aspx" target="_blank">delegate</a> to implement a custom handler for the dialog.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     string dialogText;
     
     [CodedStep(@"Navigate then verify text in popup dialog")]
@@ -53,12 +50,8 @@ This is possible with a coded solution.  The code will both handle the dialog an
         Manager.Desktop.KeyBoard.KeyPress(Keys.Enter);
         dialog.HandleCount++;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Private dialogText As String
     
     <CodedStep("Navigate then verify text in popup dialog")> _
@@ -90,22 +83,15 @@ This is possible with a coded solution.  The code will both handle the dialog an
         Manager.Desktop.KeyBoard.KeyPress(Keys.Enter)
         dialog.HandleCount += 1
     End Sub
-    {{endregion}}
+````
 
 Ensure you add the following *using* or *Imports* statements to the top of the code-behind file.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     using ArtOfTest.WebAii.Win32.Dialogs;
     using System.Windows.Forms;
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Imports ArtOfTest.WebAii.Win32.Dialogs
     Imports System.Windows.Forms
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/verify-sort-order-html.md b/docs-teststudiodev/code-in-test/coded-samples/html/verify-sort-order-html.md
index 7dd7020c..c1ce9065 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/verify-sort-order-html.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/verify-sort-order-html.md
@@ -4,20 +4,17 @@ page_title: Verify Sort Order - Test Studio Dev Documentation
 description:  Verify Sort Order
 position: 1
 ---
-# Verify Sort Order in an HTML Table #
+# Verify Sort Order in an HTML Table
 
 *I would like to sort a column in an HTML Table and verify the content is in the correct order.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/grid/index" target="_blank">Telerik demo site</a>.
 
 Let's verify the first column, Order ID, is in sequential order:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Get the table.
     HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
     
@@ -45,12 +42,8 @@ Let's verify the first column, Order ID, is in sequential order:
             Assert.IsTrue(list[j+1].CompareTo(list[j]) >= 0);
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
     
     Dim r As Integer = table.Rows.Count
@@ -72,4 +65,4 @@ Let's verify the first column, Order ID, is in sequential order:
             Assert.IsTrue(list(j + 1).CompareTo(list(j)) >= 0)
         End If
     Next
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/html/verify-style.md b/docs-teststudiodev/code-in-test/coded-samples/html/verify-style.md
index 11702230..fc8a1478 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/html/verify-style.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/html/verify-style.md
@@ -4,20 +4,17 @@ page_title: Verify Style - Test Studio Dev Documentation
 description: Verify Style
 position: 1
 ---
-# Verify HTML Style #
+# Verify HTML Style
 
 *I would like to verify an HTML element's style and extract it for use later in the test.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. Note that if you're simply verifying the style of an element you could use an <a href="/features/recorder/verifications/advanced-verification" target="_blank">Advanced Verification</a>.
 
 The example below is against <a href="http://www.w3schools.com/html/tryit.asp?filename=tryhtml_styles_font-family" target="_blank">this W3Schools site</a>. Two styles are verified, retrieved as strings, and set as <a href="/code-in-test/coded-samples/general/extracted-variables-in-code" target="_blank">extracted values</a> to use later in the test through data binding (either attached to an <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">input value</a> or a <a href="/features/data-driven-testing/attach-columns-verifications" target="_blank">verification</a>).
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Browser frame = ActiveBrowser.Frames["view"];
     HtmlControl paragraph = frame.Find.ByTagIndex<HtmlControl>("p", 0);
     Assert.IsNotNull(paragraph);
@@ -32,12 +29,8 @@ The example below is against <a href="http://www.w3schools.com/html/tryit.asp?fi
     
     paragraph.AssertStyle().Font(HtmlStyleFont.Family, "verdana", HtmlStyleType.Computed, StringCompareType.Exact);
     paragraph.AssertStyle().ColorAndBackground(HtmlStyleColorAndBackground.Color, "#FF0000", HtmlStyleType.Computed, StringCompareType.Exact);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim frame As Browser = ActiveBrowser.Frames("view")
     Dim paragraph As HtmlControl = frame.Find.ByTagIndex(Of HtmlControl)("p", 0)
     Assert.IsNotNull(paragraph)
@@ -52,7 +45,7 @@ The example below is against <a href="http://www.w3schools.com/html/tryit.asp?fi
     
     paragraph.AssertStyle().Font(HtmlStyleFont.Family, "verdana", HtmlStyleType.Computed, StringCompareType.Exact)
     paragraph.AssertStyle().ColorAndBackground(HtmlStyleColorAndBackground.Color, "#FF0000", HtmlStyleType.Computed, StringCompareType.Exact)
-    {{endregion}}
+````
 
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/samples/use-external-dll/MultiprojectSample.zip b/docs-teststudiodev/code-in-test/coded-samples/samples/use-external-dll/MultiprojectSample.zip
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/change-find-strategy.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/change-find-strategy.md
index c62e7910..0a176034 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/change-find-strategy.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/change-find-strategy.md
@@ -2,24 +2,21 @@
 title: Change Find Strategy
 page_title:  Change Find Strategy - Test Studio Dev Documentation
 description: Change Find Strategy
-position: 1
+position: 2
 ---
-# Change Silverlight Find Strategy #
+# Change Silverlight Find Strategy
 
 The default behavior of Test Studio Dev is to time out after a certain interval if the element is not found.
 
 *I would like to avoid the Timeout Exception and perform a different set of steps depending on whether the element is found.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. Change the SilverlightApp or any FrameworkElement VisualFind.Strategy value to WhenNotVisibleReturnNull.
 
 The example below is against this <a href="http://www.silverlight.net/content/samples/sl4/toolkitcontrolsamples/run/default.html" target="_blank">Silverlight demo site</a>. After navigating there, click DataGrid in the left-hand menu. Then add a coded step:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
     FindStrategy originalStrategy = app.Find.Strategy;
     
@@ -44,12 +41,8 @@ The example below is against this <a href="http://www.silverlight.net/content/sa
     {
         app.Find.Strategy = originalStrategy;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
     Dim originalStrategy As FindStrategy = app.Find.Strategy
     
@@ -68,6 +61,6 @@ The example below is against this <a href="http://www.silverlight.net/content/sa
     Finally
         app.Find.Strategy = originalStrategy
     End Try
-    {{endregion}}
+````
 
 **Note:** As is, the IF portion is executed. You can disable step two (treeview item 'DataGrid' select action) to see the ELSE portion execute.
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-all-text.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-all-text.md
index 84d97462..652334c8 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-all-text.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-all-text.md
@@ -8,10 +8,7 @@ position: 1
 
 Here is the sample code to accomplish that.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ComboBox cb = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox;
     
     string full = cb.TextBlockContent.ToString();
@@ -19,12 +16,8 @@ Here is the sample code to accomplish that.
     
     Log.WriteLine(full);
     Assert.AreEqual(full, "All Add Delete Edit Navigation None");
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim cb As ComboBox = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox
     
     Dim full As String = cb.TextBlockContent.ToString()
@@ -32,4 +25,4 @@ Here is the sample code to accomplish that.
     
     Log.WriteLine(full)
     Assert.AreEqual(full, "All Add Delete Edit Navigation None")
-    {{endregion}}
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-specific-text.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-specific-text.md
index 2f4db6c3..a3fe6e15 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-specific-text.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/combobox-automation/verify-specific-text.md
@@ -4,32 +4,25 @@ page_title: Verify Specific Text - Test Studio Dev Documentation
 description: Verify Specific Text
 position: 1
 ---
-# Verify Silverlight ComboBox Contains Specific Text #
+# Verify Silverlight ComboBox Contains Specific Text
 
 *I would like to iterate through a Silverlight ComboBox and verify that it contains specific text strings.*
 
-## Solution ##
+## Solution
 
 Here is the sample code to achieve that. 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ComboBox cb = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox;
     bool found = cb.TextBlockContent.Contains(Data["Col1"].ToString());
     
     Log.WriteLine("Match found: " + found.ToString());
     Assert.IsTrue(found);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim cb As ComboBox = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox
     Dim found As Boolean = cb.TextBlockContent.Contains(Data("Col1").ToString())
     
     Log.WriteLine("Match found: " + found.ToString())
     Assert.IsTrue(found)
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/images/verify-text-in-rich-textbox/fig1.png b/docs-teststudiodev/code-in-test/coded-samples/silverlight/images/verify-text-in-rich-textbox/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling-paging.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling-paging.md
index ec1285c6..1c9aca3a 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling-paging.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling-paging.md
@@ -4,13 +4,13 @@ page_title: Scrolling & Paging - Test Studio Dev Documentation
 description: Scrolling & Paging
 position: 1
 ---
-# RadGridView Scrolling & Paging #
+# RadGridView Scrolling & Paging
 
 *I have a lot of data contained in a RadGridView with scrolling and paging. I need to find a specific element in the grid. To find it, I need to scroll down through the entire GridView and go through every page verifying the data.*
 
 ![Paging][1]
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. To accomplish the main goal, we need to combine the solutions of the two sub-problems. We need to take the following steps to implement the solution:
 
@@ -22,10 +22,7 @@ This is possible with a coded solution. To accomplish the main goal, we need to
 
 The following code demonstrates how to accomplish this on a <a href="http://demos.telerik.com/silverlight/#GridView/PagingLargeData" target="_blank">Telerik demo site</a>.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public FrameworkElement FindElementByTextContent(string content)
     {
         int extentHeight; // The total height of the grid, visible plus non-visible     
@@ -79,12 +76,8 @@ The following code demonstrates how to accomplish this on a <a href="http://demo
         grid.Find.Strategy = originalStrategy;
         return null;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Function FindElementByTextContent(content As String) As FrameworkElement
         
         Dim extentHeight As Integer
@@ -137,7 +130,7 @@ The following code demonstrates how to accomplish this on a <a href="http://demo
         grid.Find.Strategy = originalStrategy
         Return Nothing
     End Function
-    {{endregion}}
+````
     
 Place this in the code-behind and then call this method from a coded step.
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling.md
index 1a0a4438..42382878 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/scrolling.md
@@ -4,11 +4,11 @@ page_title: Scrolling - Test Studio Dev Documentation
 description: Scrolling
 position: 1
 ---
-# RadGridView Scrolling #
+# RadGridView Scrolling
 
 *I need to scroll down through the entire GridView verifying the data, because currently only the rows presented in the Visual Tree can be tested.*
 
-## Solution ##
+## Solution
 
 This is a limitation of the Visual Tree contained in the Silverlight engine. Silverlight puts into the Visual Tree only the UI components necessary to render the page on the screen.
 
@@ -16,10 +16,9 @@ Here is an example. Let's say you have a grid that holds 100 rows of data but ca
 
 The following code demonstrates how to accomplish this against a <a href="http://demos.telerik.com/silverlight/#GridView/UIVirtualization" target="_blank">Telerik demo page</a>.
 
-#### __[C#]__
-
-	{{region }}
+````C#
 
+	
 	int verticalOffset = 0; // Holds the current vertical offset in the viewport
 	int viewPortHeight; // The height of the visible part of the grid
 	int extentHeight; // The total height of the grid, visible plus non-visible
@@ -54,12 +53,10 @@ The following code demonstrates how to accomplish this against a <a href="http:/
 	verticalOffset += viewPortHeight;
 	VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset);
 	}
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
+````
+````VB
 
+	
 	Dim verticalOffset As Integer = 0
 	' Holds the current vertical offset in the viewport
 	Dim viewPortHeight As Integer
@@ -93,6 +90,6 @@ The following code demonstrates how to accomplish this against a <a href="http:/
 	verticalOffset += viewPortHeight
 	VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset)
 	End While
-	{{endregion}}
+````
 
 > Due to the volume of data contained in the sample RadGridView, this test will take hours to run through it all. But it shows all the necessary steps.
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/total-rows-count.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/total-rows-count.md
index ea1b1acc..ade0b9e3 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/total-rows-count.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/total-rows-count.md
@@ -4,20 +4,17 @@ page_title: Total Rows Count - Test Studio Dev Documentation
 description: Total Rows Count
 position: 1
 ---
-# RadGridView Total Rows Count #
+# RadGridView Total Rows Count
 
 *I need to get the total number of rows contained in a RadGridView. The Rows.Count property of the RadGridView only returns the number of rows on the current page.*
 
-## Solution #
+## Solution
 
 The only way to get the total rows count is by calculating the number of rows per page and adding them to the running total.
 
 The following code demonstrates how to get the rows count of the RadGridView shown on this <a href="http://demos.telerik.com/silverlight/#GridView/PagingLargeData" target="_blank">Telerik demo site</a>. We use a Do/While loop in code which exits once the "Next Page" button is no longer Enabled. Then the row count is performed once more to account for the last page.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     int extentHeight; // The total height of the grid, visible plus non-visible
     int rowHeight; // The height of the row
     
@@ -48,12 +45,8 @@ The following code demonstrates how to get the rows count of the RadGridView sho
     
     // Show the result
     Log.WriteLine("Total Number of Rows: "+ totalOverallRows.ToString());
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim extentHeight As Integer
 
     Dim rowHeight As Integer
@@ -83,4 +76,4 @@ The following code demonstrates how to get the rows count of the RadGridView sho
     
 
     Log.WriteLine("Total Number of Rows: " + totalOverallRows.ToString())
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/verify-specific-column.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/verify-specific-column.md
index 91847036..bd19b874 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/verify-specific-column.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/radgridview-automation/verify-specific-column.md
@@ -4,18 +4,15 @@ page_title: Verify Specific Column - Test Studio Dev Documentation
 description: Verify Specific Column
 position: 1
 ---
-# RadGridView Verify Data in a Specific Column #
+# RadGridView Verify Data in a Specific Column
 
 *I need to find the correct column of a GridView based on something other than index, such as text content or a data driven variable.*
 
-## Solution ##
+## Solution
 
 Here is how to accomplish this against a <a href="http://demos.telerik.com/silverlight/#GridView/Totals" target="_blank">Telerik demo site</a>. First you need to retrieve all the Header Row Cells from the Grid and iterate through each one looking for a specific string. Each time it isn't found, the integer idx is increased by one. Once a match is made, idx will equal the index of the target column. Then you can use that integer to identify the column later:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     int verticalOffset = 0; // Holds the current vertical offset in the viewport
     int viewPortHeight; // The height of the visible part of the grid
     int extentHeight; // The total height of the grid, visible plus non-visible
@@ -59,12 +56,8 @@ Here is how to accomplish this against a <a href="http://demos.telerik.com/silve
         verticalOffset += viewPortHeight;
         VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim verticalOffset As Integer = 0
 
     Dim viewPortHeight As Integer
@@ -106,7 +99,7 @@ Here is how to accomplish this against a <a href="http://demos.telerik.com/silve
         verticalOffset += viewPortHeight
         VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset)
     End While
-    {{endregion}}
+````
 
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/select-listbox-item-by-text.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/select-listbox-item-by-text.md
index 2becf1c8..09903914 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/select-listbox-item-by-text.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/select-listbox-item-by-text.md
@@ -2,13 +2,13 @@
 title: Select Listbox Item by Text
 page_title: Select Listbox Item by Text - Test Studio Dev Documentation
 description: Select Listbox Item by Text
-position: 1
+position: 2
 ---
-# Select Listbox Item by Text in Silverlight #
+# Select Listbox Item by Text in Silverlight
 
 *I have a listbox contained in my Silverlight application. I want to be able to find and select an item contained in the listbox by its text, not by its index. I can't use select by index because the position of the item that needs to be selected may change at any time.*
 
-## Solution ##
+## Solution
 
 This is a tricky one to solve. There are two subtle problems that need to be dealt with before accomplishing the end goal:
 
@@ -26,7 +26,7 @@ The solution is to use this approach in a **loop**:
 
 My sample Silverlight application to test contains this XAML code to render my listbox:
 
-```XAML
+````XML
 <ListBox AutomationProperties.AutomationId="lb001" Height="117" HorizontalAlignment="Left" Margin="23,102,0,0" Name="listBox1" VerticalAlignment="Top" Width="281">
     <ListBoxItem Content="Item 1" />
     <ListBoxItem Content="Item 2" />
@@ -88,14 +88,11 @@ My sample Silverlight application to test contains this XAML code to render my l
     <ListBoxItem Content="Item 58" />
     <ListBoxItem Content="Item 59" />
 </ListBox>
-```
+````
 
 To help make the code necessary to accomplish our search task more modular, let's define a function that takes a listbox, a string to search for and finds and returns the listbox item want. Here is that function:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     private static ListBoxItem FindListboxItemByText
         (string itemToFind, ListBox myLB)
     {
@@ -130,15 +127,12 @@ To help make the code necessary to accomplish our search task more modular, let'
         // We scanned the entire list and didn't find the right item to select.
         return null;
     }
-    {{endregion}}
+````
 
 We call this resusable function from a coded step like this:
 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     [CodedStep("Select a listbox item by text")]
     public void SelectListItemByTextCodedStep()
     {
@@ -151,4 +145,4 @@ We call this resusable function from a coded step like this:
         Assert.IsNotNull(item, "\"" + itemToFind + "\" not found in the listbox.");
         item.User.Click();
     }
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-colors-in-silverlight.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-colors-in-silverlight.md
index 17db3151..c5640eb8 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-colors-in-silverlight.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-colors-in-silverlight.md
@@ -2,20 +2,17 @@
 title: Verify Colors in Silverlight
 page_title: Verify Colors in Silverlight - Test Studio Dev Documentation
 description: Verify Colors in Silverlight
-position: 1
+position: 2
 ---
-# Verify Colors in Silverlight #
+# Verify Colors in Silverlight
 
 _I would like to add a color verification for an element in a Silverlight application._
 
-## Solution ##
+## Solution
 
 The code below demonstrates this approach against this <a href="http://demos.telerik.com/silverlight/#TreeView/Performance" target="_blank">Telerik demo site</a>. It gets the first item in the menu and verifies that its foreground color matches pre-defined values:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Manager.Settings.Web.EnableSilverlight = true; 
     Manager.LaunchNewBrowser(); 
     ActiveBrowser.NavigateTo("http://demos.telerik.com/silverlight/#TreeView/Performance"); 
@@ -47,11 +44,8 @@ The code below demonstrates this approach against this <a href="http://demos.tel
         // If it's not a SolidColorBrush what is it? How do we handle it?
         throw new ApplicationException("Expecting a SolidColorBrush, but got a " + textblockBrush.GetType().ToString());
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }} 
+````
+````VB
 
     Manager.Settings.Web.EnableSilverlight = True
     Manager.LaunchNewBrowser()
@@ -84,7 +78,7 @@ The code below demonstrates this approach against this <a href="http://demos.tel
     Else
         Throw New ApplicationException("Expecting a SolidColorBrush, but got a " + textblockBrush.[GetType]().ToString())
     End If
-    {{endregion}}
+````
 
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-sort-order.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-sort-order.md
index 38a92e06..7cb92d43 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-sort-order.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-sort-order.md
@@ -2,22 +2,19 @@
 title: Verify Sort Order
 page_title: Verify Sort Order - Test Studio Dev Documentation
 description: Verify Sort Order
-position: 1
+position: 2
 ---
-# Verify Sort Order in a Silverlight DataGrid #
+# Verify Sort Order in a Silverlight DataGrid
 
 _I would like to sort a column in a Silverlight DataGrid and verify the content is in the correct order._
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. The example below is against <a href="http://silverlight.codeplex.com/downloads/get/119862" target="_blank">a Silverlight toolkit sample</a>.
 
 After navigating there, click DataGrid in the left-hand menu. Then click the **FirstName** column header to sort that column. Finally, add a coded step:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Get the data grid.
     SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
     DataGrid grid = app.Find.ByAutomationId<DataGrid>("dataGrid");
@@ -46,12 +43,8 @@ After navigating there, click DataGrid in the left-hand menu. Then click the **F
             Assert.IsTrue(list[j+1].CompareTo(list[j]) >= 0);
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
     Dim grid As DataGrid = app.Find.ByAutomationId(Of DataGrid)("dataGrid")
     
@@ -74,6 +67,6 @@ After navigating there, click DataGrid in the left-hand menu. Then click the **F
             Assert.IsTrue(list(j + 1).CompareTo(list(j)) >= 0)
         End If
     Next
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-text-in-rich-textbox.md b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-text-in-rich-textbox.md
index 7a5d0182..0e7aea11 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-text-in-rich-textbox.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/silverlight/verify-text-in-rich-textbox.md
@@ -2,25 +2,25 @@
 title: Verify Text in Rich TextBox
 page_title: Verify Text in Rich TextBox - Test Studio Dev Documentation
 description: Verify Text in Rich TextBox
-position: 1
+position: 2
 ---
-# Verify Text in a Silverlight RichTextBox #
+# Verify Text in a Silverlight RichTextBox
 
 _I cannot verify all the text or its properties in my Silverlight RichTextBox. The contents are either not visible or each word is contained in an individual TextBlock in the Visual Tree._
 
-## Solution ##
+## Solution
 
 The <a href="http://msdn.microsoft.com/en-us/library/system.windows.controls.richtextbox%28v=vs.95%29.aspx" target="_blank">Silverlight RichTextBox</a> is tricky to work with. It is a "container" type of control, meaning it contains other <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.block%28v=vs.95%29.aspx" target="_blank">"block" elements</a>, usually the <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.paragraph%28v=vs.95%29.aspx" target="_blank">Paragraph</a> or <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.section%28v=vs.95%29.aspx" target="_blank">Section</a>. It is these block elements that hold the actual text displayed in the RichTextBox. Thus, to fetch the displayed text, you must enumerate through the individual blocks and fetch the text from each block element.
 
 To make matters worse, the contents of the RichTextBox may not be contained in the Silverlight Visual Tree. You have to get the Xaml property and parse the contents yourself. Here is an example. Let's assume that you have this in the XAML file for your Silverlight application:
 
-```XAML
+````XML
 <RichTextBox AutomationProperties.AutomationId="richTextBox1" Name="richTextBox1" Margin="310,6,6,235">
     <Paragraph FontSize="11" FontFamily="Portable User Interface" Foreground="#FF000000" FontWeight="Normal" FontStyle="Normal" FontStretch="Normal" TextAlignment="Left">
         <Run FontWeight="Bold" Text="Now is the time for all good men to come to the aid of their country." />
     </Paragraph>
 </RichTextBox>
-```
+````
 
 The application will show text as shown below.
 
@@ -28,7 +28,7 @@ The application will show text as shown below.
 
 However in DOM Explorer all you see is this:
 
-```XAML
+````XML
 <?xml version="1.0"?>
 <richtextbox Name="richTextBox1" AutomationId="richTextBox1" Uid="16157963">
   <grid Name="RootElement" Uid="37840511">
@@ -52,14 +52,13 @@ However in DOM Explorer all you see is this:
     <border Name="FocusVisualElement" Uid="13045638" />
   </grid>
 </richtextbox>
-```
+````
 
 Notice that there's no text in the DOM view, even though it is specified in the XAML and displayed in the application. We have to use code to fetch the XAML that the RichTextBox holds as data, then parse out the text buried in it. Here's an example:
 
-#### __[C#]__
-
-  {{region }}
+````C#
 
+  
   // Fetch the XAML property of the RichTextBox
   string rtbContents = (string)Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(new AutomationProperty("Xaml", typeof(string)));
   
@@ -75,12 +74,10 @@ Notice that there's no text in the DOM view, even though it is specified in the
   {
       Log.WriteLine(runNode.Attributes["Text"].Value);
   }
-  {{endregion}}
-
-#### __[VB]__
-
-  {{region }}
+````
+````VB
 
+  
   Dim rtbContents As String = DirectCast(Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(New AutomationProperty("Xaml", GetType(String))), String)
     
   Dim doc As XmlDocument = New System.Xml.XmlDocument()
@@ -91,14 +88,13 @@ Notice that there's no text in the DOM view, even though it is specified in the
   For Each runNode As XmlNode In runNodes
       Log.WriteLine(runNode.Attributes("Text").Value)
   Next
-  {{endregion}}
+````
 
 Here's how to verify the text is bold:
 
-#### __[C#]__
-
-  {{region }}
+````C#
 
+  
   string rtbContents = (string)Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(new AutomationProperty("Xaml", typeof(string)));
   Log.WriteLine(rtbContents);
     
@@ -114,12 +110,10 @@ Here's how to verify the text is bold:
   
   // Verify it is Bold
   Assert.AreEqual<string>("Bold", attr.Value);
-  {{endregion}}
-
-#### __[VB]__
-
-  {{region }}
+````
+````VB
 
+  
   Dim rtbContents As String = DirectCast(Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(New AutomationProperty("Xaml", GetType(String))), String)
   Log.WriteLine(rtbContents)
     
@@ -135,6 +129,6 @@ Here's how to verify the text is bold:
     
 
   Assert.AreEqual(Of String)("Bold", attr.Value)
-  {{endregion}}
+````
 
 [1]: images/verify-text-in-rich-textbox/fig1.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/wpf/automate-clickonce-app.md b/docs-teststudiodev/code-in-test/coded-samples/wpf/automate-clickonce-app.md
index eb0a5235..6cc475dd 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/wpf/automate-clickonce-app.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/wpf/automate-clickonce-app.md
@@ -14,33 +14,23 @@ To automate a WPF application it is necessary to <a href="/features/recorder/rec
 
 It is necessary to create a stand alone class file (*Utility*) which static property (*pathFile*) will be used to store the path to the latest app version:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     public class Utility
     {
         public static string pathFile = string.Empty;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Public Class Utility
 
         Public Shared pathFile As String = String.Empty
 
     End Class
-    {{endregion}}
+````
 
 The following scenario assumes that the app is downloaded form a web destination, installed and ran from a browser. In such case the first test in the list will be a Web test that will complete the app installation part. At the end of the installation the latest app version will be up and running. This test have to end with acoded step which will save in a variable the path to the new application as given bellow:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // check if there is running process with same name
     var runningApp = System.Diagnostics.Process.GetProcesses().Where(p => p.ProcessName == "YourClickOnceWpfApp");
 
@@ -52,12 +42,8 @@ The following scenario assumes that the app is downloaded form a web destination
 
     // save the full path to a common variable
     Utility.pathFile = proc.MainModule.FileName.ToString();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim runningApp = System.Diagnostics.Process.GetProcesses().Where(Function(p) p.ProcessName = "YourClickOnceWpfApp")
 
     Dim proc = runningApp.FirstOrDefault()
@@ -66,14 +52,11 @@ The following scenario assumes that the app is downloaded form a web destination
 
     Utility.pathFile = proc.MainModule.FileName.ToString()
 
-    {{endregion}}
+````
 
 Next step is to create a WPF test that begins with a coded step and is configured to run a dummy WPF app. In the coded step the initially started mock app will be closed. Then depending on the latest version state (running/stoped) Test Studio will connect to or open it for next test steps execution:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // Shut down "mock" app
     ActiveApplication.Quit();
 
@@ -90,12 +73,8 @@ Next step is to create a WPF test that begins with a coded step and is configure
         // or - launch new application
         Manager.LaunchNewApplication(Utility.pathFile);
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveApplication.Quit()
 
     Dim runningApp = System.Diagnostics.Process.GetProcesses().Where(Function(p) p.ProcessName = "YourClickOnceWpfApp")
@@ -110,4 +89,4 @@ Next step is to create a WPF test that begins with a coded step and is configure
 
     End If
 
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/wpf/connect-to-running-app.md b/docs-teststudiodev/code-in-test/coded-samples/wpf/connect-to-running-app.md
index 2d943edb..ca6475f2 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/wpf/connect-to-running-app.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/wpf/connect-to-running-app.md
@@ -4,20 +4,17 @@ page_title: Connect to Running App - Test Studio Dev Documentation
 description: Connect to Running App
 position: 1
 ---
-# Connect to a Running WPF Application #
+# Connect to a Running WPF Application
 
 *I would like to connect to an already running WPF application and execute the test there, instead of launching a new instance of the app.*
 
-##Solution##
+## Solution
 
 When you Quick Execute or execute a Test List, a new instance of the app launches from its pre-configured location.
 
 To work around this limitation, create a mock application to feed to Test Studio. Then insert a coded step as the first step of the test. Use the following code which closes the mock application and connects to the desired application if it's running. If not, a new instance is launched.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     ActiveApplication.Quit();
     var runningApp = System.Diagnostics.Process.GetProcesses().Where(p => p.ProcessName == "WPFHelloWorld");
     
@@ -31,12 +28,8 @@ To work around this limitation, create a mock application to feed to Test Studio
     }
     
     Manager.ActiveApplication.MainWindow.RefreshVisualTrees();
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveApplication.Quit()
     Dim runningApp = System.Diagnostics.Process.GetProcesses().Where(Function(p) p.ProcessName = "WPFHelloWorld")
     
@@ -47,4 +40,4 @@ To work around this limitation, create a mock application to feed to Test Studio
     End If
     
     Manager.ActiveApplication.MainWindow.RefreshVisualTrees()
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-grid-cells.md b/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-grid-cells.md
index 1fb84917..82b1701b 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-grid-cells.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-grid-cells.md
@@ -4,18 +4,15 @@ page_title: Go Through Grid Cells - Test Studio Dev Documentation
 description: Connect to Running App
 position: 4
 ---
-# Go Through Each Cell in a WPF RadGridView #
+# Go Through Each Cell in a WPF RadGridView
 
 *I would like to go through each cell in a WPF RadGridView and perform some action or verification.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. Here's an example that goes through all the visible cells in a WPF demo grid (as opposed to all the cells contained in the grid). It writes the text content of each cell into the test log.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     WpfApplication app = Manager.ActiveApplication;
     Assert.IsNotNull(app);
     
@@ -36,12 +33,8 @@ This is possible with a coded solution. Here's an example that goes through all
         }
         rowCounter++;
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim app As WpfApplication = Manager.ActiveApplication
     Assert.IsNotNull(app)
     
@@ -60,7 +53,7 @@ This is possible with a coded solution. Here's an example that goes through all
         Next
         rowCounter += 1
     Next
-    {{endregion}}
+````
 
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-radtreeview.md b/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-radtreeview.md
index 34806d22..99e79797 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-radtreeview.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/wpf/go-through-radtreeview.md
@@ -4,18 +4,15 @@ page_title: Go Through RadTreeView - Test Studio Dev Documentation
 description: Go Through RadTreeView
 position: 3
 ---
-# Go Through Each Node in a WPF RadTreeView #
+# Go Through Each Node in a WPF RadTreeView
 
 *I would like to go through each node in a WPF RadTreeView until a match is made.*
 
-## Solution ##
+## Solution
 
 This is possible with a coded solution. You'll expand each node and refresh the tree until you find your match.
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     WpfApplication app = Manager.ActiveApplication;
     Assert.IsNotNull(app);
     Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView tree = app.MainWindow.Find.ByName<Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView>("treeView");
@@ -55,12 +52,8 @@ This is possible with a coded solution. You'll expand each node and refresh the
             break;
         }
     }
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     Dim app As WpfApplication = Manager.ActiveApplication
     Assert.IsNotNull(app)
     Dim tree As Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView = app.MainWindow.Find.ByName(Of Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView)("treeView")
@@ -92,6 +85,6 @@ This is possible with a coded solution. You'll expand each node and refresh the
             Exit While
         End If
     End While
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/coded-samples/wpf/parameterize-wpf-app.md b/docs-teststudiodev/code-in-test/coded-samples/wpf/parameterize-wpf-app.md
index aca91549..d7c214f0 100644
--- a/docs-teststudiodev/code-in-test/coded-samples/wpf/parameterize-wpf-app.md
+++ b/docs-teststudiodev/code-in-test/coded-samples/wpf/parameterize-wpf-app.md
@@ -4,13 +4,13 @@ page_title: Parameterize WPF App - Test Studio Dev Documentation
 description: Parameterize WPF App
 position: 2
 ---
-# Parameterize the Location of a WPF Application #
+# Parameterize the Location of a WPF Application
 
 Currently Test Studio Dev is rigged that you cannot run a WPF Test unless you provide a definite (non-parameterized) location for the application under testing.
 
 ![Configure WPF path][1]
 
-## Solution ##
+## Solution
 
 To work around this limitation, create a mock application to feed to Test Studio Dev. Then change the application under testing in a coded step. This allows you to use a parameterization method of your choosing for the app's location. 
 
@@ -24,10 +24,7 @@ To work around this limitation, create a mock application to feed to Test Studio
 
 Let's assume that the "real" application is in the following location: **C:\myapps\Go.exe**. Here's the code:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     //Shut down "mock" app
     ActiveApplication.Quit();
     
@@ -45,12 +42,8 @@ Let's assume that the "real" application is in the following location: **C:\myap
     
     //Check whether we connected successfully
     Assert.IsNotNull(app);
-    {{endregion}}
-
-#### __[VB]__
-
-    {{region }}
-
+````
+````VB
     ActiveApplication.Quit()
     
 
@@ -64,15 +57,12 @@ Let's assume that the "real" application is in the following location: **C:\myap
     
 
     Assert.IsNotNull(app)
-    {{endregion}}
+````
 
 You can extend this code to include parameterization for the app's location. You can use data binding, for instance. Let's say your test is bound to a data sheet with a column named "paths":
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     var pinfo = new System.Diagnostics.ProcessStartInfo(Data["paths"]);
-    {{endregion}}
+````
 
 [1]: images/parameterize-wpf-app/fig1.png
diff --git a/docs-teststudiodev/code-in-test/element-identification/dom-navigation.md b/docs-teststudiodev/code-in-test/element-identification/dom-navigation.md
index 3dc8807a..92eb1f9d 100644
--- a/docs-teststudiodev/code-in-test/element-identification/dom-navigation.md
+++ b/docs-teststudiodev/code-in-test/element-identification/dom-navigation.md
@@ -4,7 +4,7 @@ page_title: DOM Navigation - Test Studio Dev Documentation
 description: DOM Navigation
 position: 1
 ---
-#DOM Navigation#
+# DOM Navigation
 
 Once you have an element, you can navigate to other elements relative to this element. Navigation methods include:
 
@@ -20,7 +20,7 @@ Once you have an element, you can navigate to other elements relative to this el
 Suppose we have some HTML that looks like this:
 
 
-```HTML
+````HTML
 <div id="div1">
   DIV1 TEXT
        <div id="div2">
@@ -30,13 +30,10 @@ Suppose we have some HTML that looks like this:
                <span id="span3" class="style-span-3">SPAN3 TEXT</span>
        </div>
 </div>
-```
+````
 Here is how we can navigate around the DOM once we have a starting element:
 
-#### __[C#]__
-
-        {{region }}
-
+````C#    
     // Let's start with the span1 element.
     Element span1 = Find.ById("span1");
     Element span2 = span1.GetNextSibling();
@@ -67,12 +64,8 @@ Here is how we can navigate around the DOM once we have a starting element:
     Assert.IsTrue(span1.IdAttributeValue.Equals("span1"), string.Format("Actual ID: {0}", span1.IdAttributeValue));
     Assert.IsTrue(span2.IdAttributeValue.Equals("span2"), string.Format("Actual ID: {0}", span2.IdAttributeValue));
     Assert.IsTrue(span3.IdAttributeValue.Equals("span3"), string.Format("Actual ID: {0}", span3.IdAttributeValue));
-    {{endregion}}
-
-#### __[VB]__
-
-      {{region }}
-
+````
+````VB  
     ' Let's start with the span1 element.
     Dim span1 As Element = Find.ById("span1")
     Dim span2 As Element = span1.GetNextSibling()
@@ -103,4 +96,4 @@ Here is how we can navigate around the DOM once we have a starting element:
     Assert.IsTrue(span1.IdAttributeValue.Equals("span1"), String.Format("Actual ID: {0}", span1.IdAttributeValue))
     Assert.IsTrue(span2.IdAttributeValue.Equals("span2"), String.Format("Actual ID: {0}", span2.IdAttributeValue))
     Assert.IsTrue(span3.IdAttributeValue.Equals("span3"), String.Format("Actual ID: {0}", span3.IdAttributeValue))
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/element-identification/find-expressions.md b/docs-teststudiodev/code-in-test/element-identification/find-expressions.md
index e6216b72..6e156282 100644
--- a/docs-teststudiodev/code-in-test/element-identification/find-expressions.md
+++ b/docs-teststudiodev/code-in-test/element-identification/find-expressions.md
@@ -4,7 +4,7 @@ page_title: Find Expressions - Test Studio Dev Documentation
 description: Find Expressions
 position: 1
 ---
-#HTML and XAML Find Expressions#
+# HTML and XAML Find Expressions
 
 FindExpression's are the replacement/evolution of FindParam's. We will be using FindExpression's as the base for all element searches in the DOM, HWnd, or control trees (including Translator Locators). The key design goal for FindExpressions is to enable a flexible, rich and extensible search definition pattern that can be used across all of our Telerik technologies. This will enable our customers to carry over their product experience as they move across our product stacks making the learning curve for customers moving from one technology to another minimal.ma
  
@@ -32,28 +32,28 @@ FindExpression's are the following:
 
 6.Can't easily be leveraged for searches within other technologies.
 
-##Basic Concept##
+## Basic Concept
 
 The key to understanding FindExpression's is to understand its basic component: the FindClause. A FindClause is a name/value pair with an optional comparison operator. A FindExpression consists of 1-n FindClauses. For example:
 
-###FindClauses Without Operators###
+### FindClauses Without Operators
 
-```
+````
 TagName=div
 id=bar
 innermarkup=hellothere
-```
+````
 
-###FindClauses With Operators###
+### FindClauses With Operators
 
-```
+````
 name=~bar [name attribute partially contains bar]
 automationid=^hat [the automation id of an element starts with hat]
-```
+````
 **Note:** The optional operator is ALWAYS the first character after the = in the expression. This special character can be escaped with a preceding ' character if it is meant to be interpreted as a literal character.
 
 
-###Supported Operators###
+### Supported Operators
 
 <table class="docs">
 <tr>
@@ -108,17 +108,17 @@ automationid=^hat [the automation id of an element starts with hat]
 
 The name portion of the clause can be a well known enumeration that a certain technology (i.e. HTML, XAML) recognizes as a certain search pattern. For example, in HTML:
 
-```
+````
 xpath=HTML[0]/div[1]
-```
+````
 
 is interpreted by the HTML search tree as a specific search that requires XPATH interpretation.
 
-```
+````
 automationid=?sam
-```
+````
 
-##Constructing FindExpressions##
+## Constructing FindExpressions
 
 Each technology (HTML, Silverlight, etc.) will define its own FindExpression that inherits from the base FindExpression object. All FindExpression's need only one constructor to define any type of search.
  
@@ -126,16 +126,13 @@ For example:
  
 Find the HTML element with an id that ends with 'sam' and also has a class attribute that contains bar and also has a text content that does not contain foo.
 
-#### __[C#]__
-
-      {{region }}
-
+````C#  
 	HtmlFindExpression expr = new HtmlFindExpression("id=bar","|","tagindex=td:0","|","tagname=img","src=~png");
-	{{endregion}}
+````
 
-##Hierarchy Constraint##
+## Hierarchy Constraint
 
-You can also describe a certain hierarchal constraint to be applied against that FindExpression so that the decision on whether a specific element matches a specific translator or not is not solely based on the tag but also takes into consideration its hierarchical position. For example a tag that looks like <div class='foo' /> might be part of a grid while at the same time other elements on the page could contain that tag. The only way to distinguish whether that tag is part of the grid is to inspect its parent or child hierarchy.
+You can also describe a certain hierarchal constraint to be applied against that FindExpression so that the decision on whether a specific element matches a specific translator or not is not solely based on the tag but also takes into consideration its hierarchical position. For example a tag that looks like `<div class='foo' />` might be part of a grid while at the same time other elements on the page could contain that tag. The only way to distinguish whether that tag is part of the grid is to inspect its parent or child hierarchy.
  
 FindExpression's natively support hierarchy constraints. A FindExpression can have 0-n HierarchyConstraint objects associated with it.
  
@@ -147,19 +144,18 @@ A hierarchy constraint contains two pieces of data:
  
 For example, suppose we have the following HTML code snippet to deal with:
 
-```HTML
+````HTML
 <div class="bar">
   <div id="foo1">
      <section id="foo2">
          <div class="bar">
-```
+````
 
 Now we want to match the div tag that has class='bar' and its parent's parent has an id='foo1':
 
-#### __[C#]__
-
-		{{region }}
+````C#
 
+		
 	// This expression will locate both p tags at [0] & [3]
 	HtmlFindExpression expression = new HtmlFindExpression("class=bar", "tagname=div");
 	
@@ -170,12 +166,10 @@ Now we want to match the div tag that has class='bar' and its parent's parent ha
 	// -2 signifies two parents up.
 	// Note that HierarchyConstraints are [1] based. Zero signifies the target element or reference point.
 	expression.AddHierarchyConstraint(new HierarchyConstraint(parentExpr, -2));
-	{{endregion}}
-
-#### __[VB]__
-
-		{{region }}
+````
+````VB
 
+		
 	' This expression will locate both p tags at [0] & [3]
 	Dim expression As New HtmlFindExpression("class=bar", "tagname=div")
 	
@@ -186,13 +180,13 @@ Now we want to match the div tag that has class='bar' and its parent's parent ha
 	' -2 signifies two parents up.
 	' Note that HierarchyConstraints are [1] based. Zero signifies the target element or reference point.
 	expression.AddHierarchyConstraint(New HierarchyConstraint(parentExpr, -2))
-	{{endregion}}
+````
 
 The resulting expression now will match [3] ONLY.
  
 Here is a more involved scenario:
 
-```HTML
+````HTML
 <div class="bar">
   <p id="foo1">
     <span id="foo2" />
@@ -204,13 +198,13 @@ Here is a more involved scenario:
     </span>
   </p>
 </div>
-```
+````
 
 If we wish the constraint to match the first child of the parent's parent (i.e. [2]) and to be an 'span' instead, that is also doable.
  
 The path in that case is -2, 1 => Two parents up, one down at index 1. (Or -1, -1, 1, both are the same) and the second FindExpression will be "TagName=span" instead of "id=foo1".
 
-##HtmlFindExpression Types##
+## HtmlFindExpression Types
 
 The following is a list of the types that can appear on the left side of the expression in HtmlFindExpressions:
 
@@ -234,7 +228,7 @@ The following is a list of the types that can appear on the left side of the exp
 
 * XPath - search for an element at the specified XPath expression.
 
-##XamlFindExpression Types##
+## XamlFindExpression Types
 
 The following is a list of the types that can appear on the left side of the expression in XamlFindExpressions:
 
diff --git a/docs-teststudiodev/code-in-test/element-identification/find-param-as-xml-data.md b/docs-teststudiodev/code-in-test/element-identification/find-param-as-xml-data.md
index 9fffa750..9c3ad0f3 100644
--- a/docs-teststudiodev/code-in-test/element-identification/find-param-as-xml-data.md
+++ b/docs-teststudiodev/code-in-test/element-identification/find-param-as-xml-data.md
@@ -4,7 +4,7 @@ page_title: FindParam as XML Data - Test Studio Dev Documentation
 description: FindParam as XML Data
 position: 1
 ---
-#FindParams as External XML Data Sources#
+# FindParams as External XML Data Sources
 
 **Note:** This topics assumes a basic understanding of FindParam objects. It is recommended to read the <a href="/code-in-test/element-identification/finding-page-elements" target="_blank">Finding Page Elements</a> topic first before reading this topic.
  
@@ -18,14 +18,12 @@ By doing so we can:
 
 * Enable the same test logic/code to run against different versions of the same application that differ in UI layout or DOM structure. By versioning the external data sources per each different application version, we can configure our tests to consume different data source versions for each application being tested without having to duplicate test code and worry about maintaining multiple code bases. This approach can dramatically cut down maintenance and support costs especially for product teams that maintain and service multiple versions of the same application. It is also a great approach to take on if you are starting a new project and you think you will end up having to support multiple versions of that product in the future.
  
-##Building FindParam Data Sources##
+## Building FindParam Data Sources
 
 We currently don't offer any UI design tools that can help build these data sources directly from your application. Therefore, to build these data source we need to craft our FindParams manually and then using FindParam and FindParamCollection XML serialization methods, store the generated sources to our storage medium of choice (i.e. database, file system ...etc).
 The sample below shows an example of how to build an XML file that can be later consumed by your test code to identify elements to use in the automation logic.
 
-#### __[C#]__
-
-        {{region }}
+````C#        
     // First we build the list of FindParam objects we want serialized
     // and add them to a FindParamCollection object.
     
@@ -48,16 +46,13 @@ The sample below shows an example of how to build an XML file that can be later
     // in your choice of storage medium.
     //
     // string serializedParams = paramCol.ToXml();
-    {{endregion}}
+````
 
-##Consuming the Data Sources##
+## Consuming the Data Sources
 
 The are three different methods you can use to consume the data source generated above. We can deserialize the data back into a FindParamCollection object and then select one of these FindParams to locate a specific element on the page.
 
-#### __[C#]__
-
-        {{region }}
-
+````C#    
     // Given we already have a datasource of FindParam's stored on a different medium,
     // we can deserialize the data back into a FindParamCollection object and then
     // select one of these FindParam's to locate a specific element on the page
@@ -69,14 +64,11 @@ The are three different methods you can use to consume the data source generated
     
     // Perform your automation actions on the element.
     ActiveBrowser.Actions.SetText(inputText, "sometext");
-    {{endregion}}
+````
 
 Alternatively we can can create a Dictionary lookup object from the external datasource.
 
-#### __[C#]__
-
-      {{region }}
-
+````C#  
     // FindParams can be completely extracted out of test code and stored in an external xml file. 
     // 
     // This allows you to:
@@ -101,14 +93,11 @@ Alternatively we can can create a Dictionary lookup object from the external dat
     // Note:
     // 1. If you have the XML string stored in a DataBase, you can use the Find.FromXml() 
     //    to find these elements directly from the string.
-    {{endregion}}
+````
 
 Finally we can load the external datasource using a FindParamAttribute.
 
-#### __[C#]__
-
-        {{region }}
-
+````C#    
     // The SupportFiles\FindElementsFromFile.xml shows a sample xml file with two FindParams defined; one for
     // the MainTable and the other for ProgramsTable.
     
@@ -120,9 +109,9 @@ Finally we can load the external datasource using a FindParamAttribute.
     Assert.IsTrue(Find.Elements.Count == 2);
     Assert.IsTrue(Find.Elements["MainTable"].ElementType == ElementType.Table);
     Assert.IsTrue(Find.Elements["ProgramsTable"].ElementType == ElementType.Table);
-    {{endregion}}
+````
 
-##Managing and Organizing Data Sources for an Entire Application##
+## Managing and Organizing Data Sources for an Entire Application
 
 There are probably many ways you can think of to organize your external data sources for your an entire application. We though want to discuss three approaches you might want to consider. You can organize your external sources:
 
diff --git a/docs-teststudiodev/code-in-test/element-identification/find-param-objects.md b/docs-teststudiodev/code-in-test/element-identification/find-param-objects.md
index ec5a6454..fe3f01c2 100644
--- a/docs-teststudiodev/code-in-test/element-identification/find-param-objects.md
+++ b/docs-teststudiodev/code-in-test/element-identification/find-param-objects.md
@@ -4,27 +4,21 @@ page_title: FindParam Objects - Test Studio Dev Documentation
 description: FindParam Objects
 position: 1
 ---
-#FindParam Objects#
+# FindParam Objects
 
 All the identification methods exposed by the 'Find' object described above use FindParam objects under the covers to describe the desired element within the DOM tree to Telerik's identification engine. The engine itself can only understand searches using FindParam's. You can directly invoke element searches against the identification engine using the Find.ByParam() or Find.AllByParam() methods. When FindParam's are used directly to define a search, they enable a richer, consistent and more flexible way to describe a certain element than just the Find.Byxx() which were designed to cater for the most common scenarios. For example, if you want to describe the second 'div' on a page with class=myclass. You can't directly do that using the Find.Byxx() methods unless you first find the second 'div' element then inspect its attributes to figure out if the class attribute is set 'myclass'. With FindParam objects, you can simply describe that search by:
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // The find object will only return an element if all conditions
     // exist. Else NULL.
     Element e = Find.ByParam(new FindParam("div", 1,"class=myclass"));
     Assert.IsNotNull(e);
-    {{endregion}}
+````
 
 Here are some other examples:
 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     Element e;
       
     // Find.ById() is implemented as
@@ -42,9 +36,9 @@ Here are some other examples:
     p.ContentType = FindContentType.InnerMarkup;
     e = Find.ByParam(p);
     Assert.IsNotNull(e);
-    {{endregion}}
+````
 
-##Chained Identification##
+## Chained Identification
 
 Chained identification is simply using multiple FindParam objects (as in a chain) to identify an element. Chained identification is used to help simplify locating nested and complex markup elements and promote a more robust approach for element identification in these scenarios.
  
@@ -54,7 +48,7 @@ To help understand chained identification better, let's take a concrete example.
  
 Many times developers find themselves struggling with a markup nesting similar to the one below; particularly on rich content websites when heavy styling is applied or when using dynamic web development technologies like ASP.NET. In the sample below, the outer table contains an id attribute but the rest of the nested tables don't. Let's assume a test needs to access the inner most table to verify its content. Instead of looking up the overall 'table' occurrence index over an entire document which can easily become difficult on large complex pages, we would like to first identify the "table1" element by its id and then simply count two table occurrences from it (occurrence index 1) to locate the inner table.
 
-```HTML
+````HTML
 <table id="table1">
    <tr>
      <td>
@@ -80,15 +74,12 @@ Many times developers find themselves struggling with a markup nesting similar t
      </td>
    </tr>
 </table>
-```
+````
 
 Below is the chained identification code to accomplish that.
 
 
-#### __[C#]__
-
-    {{region }}
-
+````C#
     // Generic chained identification
     FindParam idtable1 = new FindParam("id=table1");
       
@@ -99,8 +90,8 @@ Below is the chained identification code to accomplish that.
     Element innerTable = Find.ByParam(new FindParam[] { idtable1, innertable });
     Assert.IsNotNull(innertable);
     Assert.AreEqual(3, innerTable.Children[0].Children.Count);
-    {{endregion}}
+````
 
-##Defining FindParam Objects Outside Test Code (i.e. FindParam Serialization)##
+## Defining FindParam Objects Outside Test Code (i.e. FindParam Serialization)
 
 FindParam objects support serialization including the FindParamCollection. This support allows you to define your FindParam's outside your test code and consume them as data sources. This enables you to be more agile when changes are made to your application by simply updating the xml that defines your FindParam objects. This topic is covered in more detail under <a href="/code-in-test/element-identification-wtc/find-param-as-xml-data" target="_blank">FindParams as External Xml DataSources</a>.
diff --git a/docs-teststudiodev/code-in-test/element-identification/finding-page-elements.md b/docs-teststudiodev/code-in-test/element-identification/finding-page-elements.md
index 1d838545..aaeaa7fc 100644
--- a/docs-teststudiodev/code-in-test/element-identification/finding-page-elements.md
+++ b/docs-teststudiodev/code-in-test/element-identification/finding-page-elements.md
@@ -5,33 +5,7 @@ description: "Test Studio Find methods. Progress Testing Framework Find.By metho
 position: 1
 ---
 
-<style>
-table.docs {
-font-family: verdana,arial,sans-serif;
-font-size:11px;
-color:#333333;
-border: 1px solid #dbdbdb;
-border-collapse: collapse;
-table-layout: fixed;
-width: 900px;
-
-}
-table.docs th {
-color:#fff;
-background-color:#ed8200;
-border: 1px solid #dbdbdb;
-padding: 8px;
-}
-table.docs tr {
-background-color:#ffffff;
-}
-table.docs td {
-border: 1px solid #dbdbdb;
-padding: 8px;
-}
-</style>
-
-# Finding Page Elements #
+# Finding Page Elements
 
 Telerik Testing Framework provides one of the richest markup identification infrastructures currently available on the market. It builds on top of commonly known element identification methods like 'getElementById', 'getElementByName' or 'XPath' and extends them to provide identification routines that cater more to application automation scenarios. In addition to maintaining a simple and easy to use set of APIs, Telerik Testing Framework introduces a consistent and extensible way to build identification and persist it using 'FindParam' objects.
 
@@ -39,7 +13,7 @@ All the Find.Byxxx methods now support LINQ queries.
 
 It is important to understand how Telerik's identification method works because that understanding will allow you to exploit the power of these identification methods to build robust automation quicker.
 
-##Element Identification Overview##
+## Element Identification Overview
 
 The following identification methods are supported:
 
@@ -48,56 +22,61 @@ The following identification methods are supported:
 	<th style="width:165px;">Methods</th><th style="width:200px;">Description</th><th>Example</th>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ById_System_String_" target="_blank">**Find.ById()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ById_System_String_" target="_blank">Find.ById()</a></td>
 	<td>Searches for an element contained in a markup document using its set 'id' attribute. When the desired 'id' matches an element's id, the element is returned - identical to getElementById</td>
 <td>
-```	
+
+````	
 // Find element with id=input1
 Element e = Find.ById("input1");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByName_System_String_" target="_blank">**Find.ByName()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByName_System_String_" target="_blank">Find.ByName()</a></td>
 	<td>Searches for an element contained in a markup document using its set 'name' attribute. When the desired 'name' matches an element's name, the element is returned</td>
 <td>
-```	
+
+````	
 // Find element with name=goButton
 Element e = Find.ByName("goButton")
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByImage_System_Drawing_Image_System_Double_System_Int32_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">**Find.ByImage()**</a><br>
-    <a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByImage_System_Drawing_Image_System_Double_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">**Find.AllByImage()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByImage_System_Drawing_Image_System_Double_System_Int32_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">Find.ByImage()</a><br>
+    <a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByImage_System_Drawing_Image_System_Double_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">Find.AllByImage()</a></td>
 	<td>Searches for an element or 'All' elements that look like a predefined image</td>
 <td>
-```
+
+````
 // Specify the predefined image on which the search will be based
 System.Drawing.Image img1 = System.Drawing.Image.FromFile(@"C:\sampleImg.png");
 // Find an element that looks like the predefind image
 var elementImg1 = Manager.ActiveBrowser.Find.ByImage(img1, 70); // the second argument is the threshold % to use, while searching for the image
 // Cast the found element to be able to use it. The type of located element needs to be specified.
 HtmlButton btn1 = elementImg1.As<HtmlButton>();
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByTagIndex_System_String_System_Int32_" target="_blank">**Find.ByTagIndex()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByTagIndex_System_String_System_Int32_" target="_blank">Find.ByTagIndex()</a></td>
 	<td>Searches for an element using its tag name occurrence index. Finds the element at the specified occurrence index and returns it. This method uses zero based indexing.</td>
 <td>
-```	
+
+````	
 // Find the 3rd occurrence of table tag
 Element table = Find.ByTagIndex("table", 2);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByAttributes_System_String___" target="_blank">**Find.ByAttributes()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByAttributes_System_String___" target="_blank">**Find.AllByAttributes()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByAttributes_System_String___" target="_blank">Find.ByAttributes()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByAttributes_System_String___" target="_blank">Find.AllByAttributes()</a></td>
 	<td>Searches for an element or 'All' elements using an 'exact' or 'partial' list of attribute values (You can specify 1-N attribute/value pairs). When all attribute values match, the element or collection of elements is returned.</td>
 <td>
-```	
+
+````	
 // Find the first element with attribute class=myclass
 Element e = Find.ByAttributes("class=myclass");
 // Find the first element with attribute class=myclass
@@ -105,15 +84,16 @@ Element e = Find.ByAttributes("class=myclass");
 Element e = Find.ByAttributes("class=myclass", "src=~foo.gif");
 // Find all elements with class=myclass and src has a partial foo.gif
 IList<Element> allbtns = Find.AllByAttributes("class=myclass", "src=~foo.gif");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByContent_System_String_" target="_blank">**Find.ByContent()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByContent_System_String_" target="_blank">**Find.AllByContent()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByContent_System_String_" target="_blank">Find.ByContent()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByContent_System_String_" target="_blank">Find.AllByContent()</a></td>
 	<td>Searches for an element or 'All' elements using 'exact', 'partial' or 'regex' of the element content. The element content can be: InnerText, InnerMarkup, OuterMarkup, TextContent (default), StartTagContent.</td>
 <td>
-```	
+
+````	
 // Find element with TextContent has literal value: Education
 // l: signifies literal
 Element e = Find.ByContent("l:Education");
@@ -138,64 +118,68 @@ IList<Element> alle = Find.AllByContent("p:car")
 // TextContent of div1 : Text1 {non-recursive}
 //
 // Default for ByContent is TextContent which is the most common usage.
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">**Find.ByExpression()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">**Find.AllByExpression()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">Find.ByExpression()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">Find.AllByExpression()</a></td>
 	<td>Searches for an element or 'All' elements matching an HtmlFindExpression. The HtmlFindExpression cannot use any type of hierarchical expressions including tag index path expressions, HTML path expressions, and XPath expressions.</td>
 <td>
-```	
+
+````	
 // Create an HtmlFindExpression element
 HtmlFindExpression expr = new HtmlFindExpression("id=?sam","class=~bar","textcontent=!foo");
 // Return all elements matching HtmlFindExpression
 IList<Element> allSams = Find.AllByExpression(expr);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByXPath_System_String_" target="_blank">**Find.ByXPath()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByXPath_System_String_" target="_blank">**Find.AllByXPath()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByXPath_System_String_" target="_blank">Find.ByXPath()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByXPath_System_String_" target="_blank">Find.AllByXPath()</a></td>
 	<td>Searches for an element or 'All' elements using an XPath expression. WebAii supports the .NET Framework XPath implementation.</td>
 <td>
-```	
+
+````	
 // Find the banner img element
 Element img = Find.ByXPath("//body[1]/table[1]/tbody[1]/tr[1]/td[1]/img[1]");
 // Find all times with id=div
 IList<Element> allDivs = Find.AllByXPath("/descendant::node()[starts-with(@id,'div')]");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByCssSelector_System_String_" target="_blank">**Find.ByCssSelector()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCssSelector_System_String_" target="_blank">**Find.AllByCssSelector()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_ByCssSelector_System_String_" target="_blank">Find.ByCssSelector()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCssSelector_System_String_" target="_blank">Find.AllByCssSelector()</a></td>
 	<td>Searches for an element or 'All' elements using a css selector query.</td>
 <td>
-```	
+
+````	
 // Find the active link
 HtmlAnchor activeLink = Find.ByCssSelector<HtmlAnchor>("a:active");
 // Find all links
 IList<HtmlAnchor> allLinks = Find.AllByCssSelector<HtmlAnchor>("a"); 
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByTagName_System_String_" target="_blank">**Find.AllByTagName()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByTagName_System_String_" target="_blank">Find.AllByTagName()</a></td>
 	<td>Searches for 'All' elements with the specified tag name and returns it as a list of elements.</td>
 <td>
-```	
+
+````	
 // Return all img elements
 IList<Element> allimg = Find.AllByTagName("img");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByNodeIndexPath_System_String_" target="_blank">**Find.ByNodeIndexPath()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByNodeIndexPath_System_String_" target="_blank">Find.ByNodeIndexPath()</a></td>
 	<td>Searches for an element using dom tree node index paths. This identification is done using an xpath like approach that simply describes the hierarchy path to a specific element using the node index within the hierarchy without having to specify the tag name at each level. This identification method can be chosen in cases where a segment of the DomTree hierarchy at a specific location is consistent but element type changes. For example, if an element you are trying to target is the direct child of another element that fluctuates between a span and div, you can choose this identification method to provide a consistent way to identify that element.</td>
 <td>
 
-```	
+````
 Given this DOM:
 
  <referenceElement>
@@ -217,25 +201,27 @@ Given this DOM:
 
 // We can find the <target></target> element by:
 Element target = Find.ByNodeIndexPath("0/2/0/1");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_FromCollection_ArtOfTest_WebAii_ObjectModel_FindExpressionCollection_ArtOfTest_WebAii_Core_HtmlFindExpression__" target="_blank">**Find.FromCollection()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_FromCollection_ArtOfTest_WebAii_ObjectModel_FindExpressionCollection_ArtOfTest_WebAii_Core_HtmlFindExpression__" target="_blank">Find.FromCollection()</a></td>
 	<td>Finds all elements with the FindParams in the passed in collection.</td>
 <td>
-```	
+
+````	
 FindParamCollection col = FindParamCollection.LoadFromXml(xml);
 return this.FromCollection(col);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">**Find.ByCustom()**</a><br>
-	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">**Find.AllByCustom()**</a></td>
+	<td><a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">Find.ByCustom()</a><br>
+	<a href="https://docs.telerik.com/teststudio/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">Find.AllByCustom()</a></td>
 	<td>Searches for an element or 'All' elements using a custom predicate.</td>
 <td>
-```	
+
+````	
 // Find the first input button having an ID of 'input1'
 HtmlInputButton btn = Find.ByCustom<HtmlInputButton>(
     delegate(HtmlInputButton e)
@@ -247,12 +233,12 @@ HtmlInputButton btn = Find.ByCustom<HtmlInputButton>(
     }
 );
 Assert.IsNotNull(btn);
-```
+````
 </td>
 </tr>
 <table>
 
-##Identification Methods Usage##
+## Identification Methods Usage
 
 Telerik Testing Framework identification methods are accessible using the **Find** object that is exposed as a property off of the 'Browser' object : *Manager.ActiveBrowser.Find.Byxx(...)* and also as a property off of each TestRegion object : *TestRegion.Find.Byxx(...)*.
 
@@ -260,7 +246,7 @@ The difference between the Find object off of the Browser class (Root Base Ident
 
 With TestRegions, depending on the areas of the application that each automated test is targeting, you can use different Find objects to give each test a greater level of independence and shield it from product changes outside its target area. This topic is discussed in greater details in <a href="/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction" target="_blank">Introduction to TestRegions</a>.
 
-##Matching Syntax Used in Parameters##
+## Matching Syntax Used in Parameters
 
 The Byxxx functions that take a nameValuePairs parameter recognizes the following matching syntax:
 
@@ -280,11 +266,11 @@ The Byxxx functions that take a content string parameter recognizes the followin
 
 * Prefix the string parameter with 'x:' for regular expression matching. e.g. 'x:[*foo*]' will match any content containing the string 'foo' in the middle of it. For more information about  regular expressions see: http://msdn.microsoft.com/en-us/library/2k3te2cs.aspx.
 
-##Identification Sample##
+## Identification Sample
 
 To help illustrate the above identification methods, let's use the following sample application. Note that this application uses TestRegions excessively to allow it to demonstrate the different identification methods that can be performed using both **RBI** and **RGBI**:
 
-```HTML
+````HTML
 <!DOCTYPE html>
 <html>
 <head>
@@ -328,11 +314,11 @@ To help illustrate the above identification methods, let's use the following sam
 <!--/testregion-->
 </body>
 </html>
-```
+````
 
 The code below shows the different methods you can use in your test code to identify elements. Note in the sample below, we are using Visual Studio's Assert class to demonstrate how different objects can be identified differently and to illustrate how to scope the identification with TestRegions using RGBI and across the entire document DomTree using RBI.
 
-```C#
+````C#
 // Set the short-cuts to the main automation objects.
 Browser brwser = mgr.ActiveBrowser;
 Find rootFind = brwser.Find;
@@ -386,8 +372,8 @@ Assert.IsTrue(rootFind.ByNodeIndexPath("1/0/0").TagName.Equals("div", StringComp
   
 //*** Using name
 Assert.IsNull(r1.Find.ByName("bla"));
-```
-```VB
+````
+````VB
 ' Set the short-cuts to the main automation objects.
 Dim brwser As ArtOfTest.WebAii.Core.Browser = Manager.ActiveBrowser
 Dim rootFind As Find = brwser.Find
@@ -441,4 +427,4 @@ Assert.IsTrue(rootFind.ByNodeIndexPath("1/0/0").TagName.Equals("div", StringComp
   
 '*** Using name
 Assert.IsNull(r1.Find.ByName("bla"))
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/element-identification/linq-queries.md b/docs-teststudiodev/code-in-test/element-identification/linq-queries.md
index 3ca34780..0bde9878 100644
--- a/docs-teststudiodev/code-in-test/element-identification/linq-queries.md
+++ b/docs-teststudiodev/code-in-test/element-identification/linq-queries.md
@@ -4,7 +4,7 @@ page_title: LINQ Queries - Test Studio Dev Documentation
 description: LINQ Queries
 position: 1
 ---
-#LINQ Queries#
+# LINQ Queries
 
 The Find.Byxxx methods now support Language-Integrated Query (LINQ) queries. Some of the Find functions are intended to be used by LINQ queries only. These include:
 
@@ -13,24 +13,27 @@ The Find.Byxxx methods now support Language-Integrated Query (LINQ) queries. Som
 	<th>Methods</th><th>Description</th><th>Example</th>
 </tr>
 <tr>
-	<td>**AllElements**</td>
+<td>
+	
+**AllElements**</td>
 	<td>Gets a IEnumerable for all elements to be used for LINQ queries.</td>
 	<td>var inlineStyledElements = Find.AllElements().Where(element =><br>
 	element.ContainsAttribute("style"));</td>
 </tr>
 <tr>
-	<td>**AllControls**</td>
-	<td>Gets an IEnmerable for TControl to be used for LINQ queries. This will return only elements that are convertable to TControl.</td>
-	<td>var images = Find.AllControls<HtmlImage>();</td>
+<td>
+	
+**AllControls**</td>
+<td>Gets an IEnmerable for TControl to be used for LINQ queries. This will return only elements that are convertable to TControl.</td>
+<td>
+
+`var images = Find.AllControls<HtmlImage>();`</td>
 </tr>
 <table>
 
 Using LINQ we can create strongly typed advanced queries with intellisense support that we couldn't before. The most basic LINQ example is something like this:
 
-### __[VB]__
-
-				{{region }}
-
+````C#				
 	// Find all images on a page.
 	var images = Find.AllControls<HtmlImage>();
 	
@@ -38,14 +41,11 @@ Using LINQ we can create strongly typed advanced queries with intellisense suppo
 	{
 		// Do what you want with each img.
 	}
-	{{endregion}}
+````
 
 We can also use lambda expressions like this:
 
-### __[VB]__
-
-            {{region }}
-
+````C#            
 	// Find the first element that contains "Go Google"
 	Element el = Find.ByCustom(e => e.TextContent.Contains("Go Google"));
 	
@@ -69,4 +69,4 @@ We can also use lambda expressions like this:
 	// Fetch a list of HTML anchor's that contain 'a' in the ID
 	IList<Element> li = (from b in Find.AllElements() where b.IdAttributeValue.Contains("a") select b).ToArray();
 	Assert.IsTrue(li.Count > 0);
-	{{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/features-in-code.md b/docs-teststudiodev/code-in-test/features-in-code.md
index 7b16cc59..70286caf 100644
--- a/docs-teststudiodev/code-in-test/features-in-code.md
+++ b/docs-teststudiodev/code-in-test/features-in-code.md
@@ -12,9 +12,9 @@ __Test Studio Dev__ allows you to implement coded solutions for a scenario that
 
 __Test Studio Dev__ supports coded steps. This allows you to write code and have it executed as a test step. Use a coded step for a scenario where you need to extend the recorded steps functionality.
 
-1.&nbsp; Add a coded step from the <a href="/features/recorder/step-builder" target="_blank">Step Builder</a> under the _Common_ section.
+1. Add a coded step from the <a href="/features/recorder/step-builder" target="_blank">Step Builder</a> under the _Common_ section.
 
-![Add a coded step][1]
+![Add a coded step](images/fig1.png)
 
 Inserting the first __Coded step__ in a test automatically generates a <a href="/code-in-test/features-in-code#Code-Behind-File" target=blank>code behind file</a> for the current test and opens it ready for editing.
 
@@ -31,7 +31,7 @@ Each next coded step allows you to choose whether to reuse any of the existing m
 
 Almost each recorded step could be edited in code from the <a href="/features/test-maintenance/test-step-context-menu" target="_blank">Step Context menu</a>. The steps which could not be converted because of their specifics are dialog handling steps, all condition steps (if...else, loop, while) and the Manual step and Inspection Point step in the Common section of the Step Builder.
 
-![Convert step into code][5]
+![Convert step into code](images/fig5.png)
 
 This will generate a code-behind file (if this is the first coded step for the test) or will add a new method to the already existing code-behind file. The method for a recorded step will contain the required actions in code to execute all actions for the step.
 
@@ -39,11 +39,11 @@ This will generate a code-behind file (if this is the first coded step for the t
 
 The code-behind file is automatically generated when a coded step is inserted in a test. A plain code behind file (without inserted methods) can be generated by clicking the _Add Code Behind File_ button. 
 
-![Add Code Behind File][3]
+![Add Code Behind File](images/fig3.png)
 
 The code-behind file is nested under the parent test in Solution Explorer:
 
-![Code Behind File][4]
+![Code Behind File](images/fig4.png)
 
 A code behind file can be generated for each test where you need to implement coded steps and custom test classes. That coded file and its methods are related to the particular test.
 
@@ -56,8 +56,3 @@ A code behind file can be generated for each test where you need to implement co
 
 You can implement any custom logic organized in standalone code files located in your project. This includes but is not limited to classes and functions which perform common or often re-used functionality and can be called by your coded steps or code behind methods. The only requirement is to define classes in the project namespace else they will not be accessible.
 
-[1]: images/fig1.png
-[2]: images/fig2.png
-[3]: images/fig3.png
-[4]: images/fig4.png
-[5]: images/fig5.png
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/generate-unit-test.md b/docs-teststudiodev/code-in-test/generate-unit-test.md
index 054427c5..d26e83c0 100644
--- a/docs-teststudiodev/code-in-test/generate-unit-test.md
+++ b/docs-teststudiodev/code-in-test/generate-unit-test.md
@@ -22,15 +22,14 @@ A unit test file and XML file containing your data are created in your Test Proj
 
 **Note:** When you convert an entire test to code, it doesn't take into account the **Enable Silverlight** setting. You need to enable it in code prior to the LaunchNewBrowser call:
 
-```C#
+````C#
 Manager.Settings.Web.EnableSilverlight = true;
 Manager.LaunchNewBrowser();
-```
-
-```VB
+````
+````VB
 Manager.Settings.Web.EnableSilverlight = True
 Manager.LaunchNewBrowser()
-```
+````
 
 ## Preview Code
 
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/custom-html-control.md b/docs-teststudiodev/code-in-test/html-control-suite/custom-html-control.md
index 6620429b..098c3de5 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/custom-html-control.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/custom-html-control.md
@@ -4,13 +4,13 @@ page_title: Custom HtmlControl - Test Studio Dev Documentation
 description: Custom HtmlControl
 position: 2
 ---
-#Creating Your Own Custom HtmlControls#
+# Creating Your Own Custom HtmlControls
 
 Let's suppose you're testing a web site that uses a third party or custom control. You can easily create your own custom HtmlControl class and then design tests that interact with the custom control via your custom HtmlControl class.
  
 As an example, let's create a custom HtmlControl that wraps the ASP.NET calendar control. We'll give it some methods for reading and controlling the date selection along with a custom ClientSideLocator just for an example. First here's our ASPX web page containing a calendar control that we want to test
 
-```
+````
 <% @ Page Language="C#" MasterPageFile="~/AppMaster.master" Title="Untitled Page" %>
 <% @ Import Namespace="System.Data" %>
 <% @ Register Assembly="ArtOfTest.WebAii.AspNet" Namespace="ArtOfTest.WebAii.AspNet.WebControls" TagPrefix="test" %>
@@ -146,14 +146,11 @@ As an example, let's create a custom HtmlControl that wraps the ASP.NET calendar
      </test:TestRegion>
      <!-- This Data Page Content -->
 </asp:Content>
-```
+````
 
 Let's put together our custom HtmlControl that we can use interact with an ASP.NET calendar control:
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     public class AspNetCalendar : HtmlTable
         {
             /// <summary>
@@ -284,12 +281,8 @@ Let's put together our custom HtmlControl that we can use interact with an ASP.N
                 return GetMonth();
             }
         }
-    {{endregion}}
-
-#### __[VB]__
-
-                {{region }}
-
+````
+````VB            
     Public Class AspNetCalendar
             Inherits HtmlTable
             ''' <summary>
@@ -408,7 +401,7 @@ Let's put together our custom HtmlControl that we can use interact with an ASP.N
                 Return GetMonth()
             End Function
         End Class
-    {{endregion}}
+````
 
 Notice how we derive from an HtmlTable. That way we can take advantage of all the functionality already built into a standard table. We'll just add all the functions useful for our calendar control which include:
 
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/drag-and-drop.md b/docs-teststudiodev/code-in-test/html-control-suite/drag-and-drop.md
index 65f36f0c..5c22ce3c 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/drag-and-drop.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/drag-and-drop.md
@@ -4,7 +4,7 @@ page_title: Drag & Drop - Test Studio Dev Documentation
 description: Drag & Drop
 position: 2
 ---
-#How to Drag and Drop#
+# How to Drag and Drop
 
 The HTML element wrapper classes make mouse drag & drop operations significantly easier. There are 7 different drag methods defined:
 
@@ -33,10 +33,7 @@ The HTML element wrapper classes make mouse drag & drop operations significantly
 Suppose we have an sales by area table that supports drag & drop between cells. We can easily drag & drop the contents of one cell to another cell like this:
 
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 // Find the sales table
 HtmlTable salesTable = Find.ById<HtmlTable>("area_1_table");
   
@@ -46,13 +43,8 @@ salesTable.BodyRows[3].Cells[1].DragTo(salesTable.BodyRows[2].Cells[1]);
 // Verify the new row subtotals are correct
 Assert.AreEqual(salesTable.Rows[2].Cells[5].TextContent, "$3342.78");
 Assert.AreEqual(salesTable.Rows[3].Cells[5].TextContent, "$2175.17");
-{{endregion}}
- 
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
 ' Find the sales table
 Dim salesTable As HtmlTable = Find.ById(Of HtmlTable)("area_1_table")
   
@@ -62,4 +54,4 @@ salesTable.BodyRows(3).Cells(1).DragTo(salesTable.BodyRows(2).Cells(1))
 ' Verify the new row subtotals are correct
 Assert.AreEqual(salesTable.Rows(2).Cells(5).TextContent, "$3342.78")
 Assert.AreEqual(salesTable.Rows(3).Cells(5).TextContent, "$2175.17")
-{{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/element-styles.md b/docs-teststudiodev/code-in-test/html-control-suite/element-styles.md
index 1db155db..c46071bf 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/element-styles.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/element-styles.md
@@ -4,7 +4,7 @@ page_title: Element Styles - Test Studio Dev Documentation
 description: Element Styles
 position: 2
 ---
-#Element Styles and HtmlStyle, GetStyle, GetComputedStyle#
+# Element Styles and HtmlStyle, GetStyle, GetComputedStyle
 
 Telerik Testing Framework includes a good set of classes and methods for reading and validating the styles often attached to HTML controls. With this feature you can do things like:
 
@@ -25,10 +25,7 @@ Telerik Testing Framework includes a good set of classes and methods for reading
 Let's look at some code samples to see how this works:
 
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 // Verify the color of the warning text is Red
 HtmlSpan warningSpan = Find.ById<HtmlSpan>("Warning");
 HtmlStyle warningColorStyle = warningSpan.GetStyle("color");
@@ -64,14 +61,11 @@ HtmlStyle warningMarginStyle = warningSpan.GetStyle("margin");
 Assert.IsTrue(warningMarginStyle.IsInt());
 int warningMargin = warningMarginStyle.ToInt();
 Assert.AreEqual(30, warningMargin);
-{{endregion}}
+````
  
 
 
-#### __[VB]__
-
-            {{region }}
-
+````VB        
     ' Verify the color of the warning text is Red
     Dim warningSpan As HtmlSpan = Find.ById(Of HtmlSpan)("Warning")
     Dim warningColorStyle As HtmlStyle = warningSpan.GetStyle("color")
@@ -105,17 +99,14 @@ Assert.AreEqual(30, warningMargin);
     Assert.IsTrue(warningMarginStyle.IsInt())
     Dim warningMargin As Integer = warningMarginStyle.ToInt()
     Assert.AreEqual(30, warningMargin)
-    {{endregion}}
+````
 
 The GetComputedStyle is especially powerful. It will follow the CSS chain up through all the parent elements until it finds the first matching style and returns the value picked up from that style. This is quite different from GetStyle which only returns an explicitly set style value on the specific element (i.e. it does not follow the CSS chain). If no explicit value has been set then GetStyle returns an empty string for the value. 
 
 Here's an example:
 
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     // GetStyle returns the value of an explicit style applied to the element.
     // If the element does not have an explicit style applied, GetStyle returns an empty value.
     // Since our warning span does not have the padding style explicitly applied to it,
@@ -128,13 +119,10 @@ Here's an example:
     // Therefore GetComputedStyle on the warning span will return the value set in the parent form tag.
     paddingStyle = warningSpan.GetComputedStyle("padding");
     Assert.IsFalse(string.IsNullOrEmpty(paddingStyle.Value));
-    {{endregion}}
-
-
-#### __[VB]__
+````
 
-            {{region }}
 
+````VB        
     ' GetStyle returns the value of an explicit style applied to the element.
     ' If the element does not have an explicit style applied, GetStyle returns an empty value.
     ' Since our warning span does not have the padding style explicitly applied to it,
@@ -147,4 +135,4 @@ Here's an example:
     ' Therefore GetComputedStyle on the warning span will return the value set in the parent form tag.
     paddingStyle = warningSpan.GetComputedStyle("padding")
     Assert.IsFalse(String.IsNullOrEmpty(paddingStyle.Value))
-    {{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/find-and-navigate-elements.md b/docs-teststudiodev/code-in-test/html-control-suite/find-and-navigate-elements.md
index 9131b557..b54e7f2c 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/find-and-navigate-elements.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/find-and-navigate-elements.md
@@ -4,15 +4,12 @@ page_title: Find and Navigate Elements - Test Studio Dev Documentation
 description: Find and Navigate Elements 
 position: 2
 ---
-#Finding and Navigating HTML Elements#
+# Finding and Navigating HTML Elements
 
 The example above used just two of the available find methods, the Find.ById<**TControl**> and the Find.AllByTagName<**TControl**> and did not take advantage of the powerful navigation features. Let's look at some other find examples:
 
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 // Find the first table on the page.
 HtmlTable outertable = Find.ByTagIndex<HtmlTable>("table", 0);
   
@@ -42,13 +39,10 @@ Assert.AreEqual(1, imgCtrls.Count);
 // Find the <div> section containing the Eastern US Division sales report
 HtmlDiv EasternUSDivision = Find.ByContent<HtmlDiv>("Eastern US Division", FindContentType.TextContent);
 Assert.IsNotNull(EasternUSDivision);
-{{endregion}}
-
-
-#### __[VB]__
+````
 
-          {{region }}
 
+````VB      
     ' Find the first table on the page.
     Dim outertable As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
     Assert.AreEqual(3, outertable.Rows.Count)
@@ -79,15 +73,12 @@ Assert.IsNotNull(EasternUSDivision);
     ' Find the <div> section containing the Eastern US Division sales report
     Dim EasternUSDivision As HtmlDiv = Find.ByContent(Of HtmlDiv)("Eastern US Division", FindContentType.TextContent)
     Assert.IsNotNull(EasternUSDivision)
-    {{endregion}} 
+```` 
 
 The above example demonstrates how to use many of the more useful find methods. There are many more. It would take up too much space to try and document them all here. Refer to the API reference to learn about the others. Let's look at some HTML navigation functions:
 
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     // Traverse the control tree upwards too. You can easily
     // Find the container control of a certain type from its children.
     
@@ -113,14 +104,11 @@ The above example demonstrates how to use many of the more useful find methods.
     // Find the form this table is contained in.
     HtmlForm form1 = table2.Parent<HtmlForm>();
     Assert.IsTrue(form1.ID.Equals("form1"));
-    {{endregion}}
+````
  
 
 
-#### __[VB]__
-
-          {{region }}
-
+````VB      
 ' Traverse the control tree upwards too. You can easily
 ' Find the container control of a certain type from its children.
 
@@ -147,4 +135,4 @@ Assert.IsTrue(table2.ID.Equals(outertable.ID))
 ' Find the form this table is contained in.
 Dim form1 As HtmlForm = table2.Parent(Of HtmlForm)()
 Assert.IsTrue(form1.ID.Equals("form1"))
-{{endregion}}
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/get-set-properties.md b/docs-teststudiodev/code-in-test/html-control-suite/get-set-properties.md
index 23ab10b4..12ca8dae 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/get-set-properties.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/get-set-properties.md
@@ -4,15 +4,12 @@ page_title: Get & Set Properties - Test Studio Dev Documentation
 description: Get & Set Properties
 position: 2
 ---
-#Getting and Setting Properties#
+# Getting and Setting Properties
 
 We can also get and set the current value of any property of the wrapped element:
 
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 // Get whether a checkbox is enabled or disabled.
 HtmlInputCheckBox cks = Find.ById<HtmlInputCheckBox>("checkbox1");
 bool disabled = cks.GetValue<bool>("disabled");
@@ -36,14 +33,11 @@ string strColor = mySpan.GetStyleValue("color");
 // style.
 HtmlStyle styleMargin = mySpan.GetComputedStyle("margin");
 string strMargin = mySpan.GetComputedStyleValue("margin");
-{{endregion}}
+````
  
 
 
-#### __[VB]__
-
-          {{region }}
-
+````VB      
 ' Get whether a checkbox is enabled or disabled.
 Dim cks As HtmlInputCheckBox = Find.ById(Of HtmlInputCheckBox)("checkbox1")
 Dim disabled As Boolean = cks.GetValue(Of Boolean)("disabled")
@@ -61,6 +55,6 @@ Dim strColor As String = mySpan.GetStyleValue("color")
 ' style.
 Dim styleMargin As HtmlStyle = mySpan.GetComputedStyle("margin")
 Dim strMargin As String = mySpan.GetComputedStyleValue("margin")
-{{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/html-actions.md b/docs-teststudiodev/code-in-test/html-control-suite/html-actions.md
index f4514b8a..e87765b7 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/html-actions.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/html-actions.md
@@ -4,7 +4,7 @@ page_title: HTML Actions - Test Studio Dev Documentation
 description: HTML Actions 
 position: 2
 ---
-#Common HTML Control Actions#
+# Common HTML Control Actions
 
 What are some of the things we can do after finding the element we want to act upon? We can:
 
@@ -22,10 +22,7 @@ What are some of the things we can do after finding the element we want to act u
  
 Here are some examples:
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
     // All controls have a Click/MouseClick. The .Click invokes a click from the DOM,
     // the MouseClick(), moves the mouse to the control and clicks it.
     
@@ -116,13 +113,8 @@ Here are some examples:
     
     // Invoke any events on the control
     link.InvokeEvent(ScriptEventType.OnFocus);
-    {{endregion}}
- 
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
     ' All controls have a Click/MouseClick. The .Click invokes a click from the DOM,
     ' the MouseClick(), moves the mouse to the control and clicks it.   
     
@@ -213,4 +205,4 @@ Here are some examples:
         
     ' Invoke any events on the control
     link.InvokeEvent(ScriptEventType.OnFocus)
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/html-asserts.md b/docs-teststudiodev/code-in-test/html-control-suite/html-asserts.md
index e8848095..7e07366a 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/html-asserts.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/html-asserts.md
@@ -4,7 +4,7 @@ page_title: HTML Asserts - Test Studio Dev Documentation
 description: 
 position: 2
 ---
-#HTML Asserts#
+# HTML Asserts
 
 Telerik Testing Framework has a set of Assert classes to make validation of your HTML controls easier. An 'Assert' basically says "Verify the specified property of the control has the specified value or setting. If it doesn't have that setting/value, then throw an error and stop the test." 
 
@@ -142,10 +142,7 @@ For example: AssertCheck.IsTrue() will verify the associated checkbox control is
 
 Now let's see how this works in action:
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 // Attribute checks
 HtmlSpan span = Find.ById<HtmlSpan>("Warning");
 span.AssertAttribute().Exists("style");
@@ -201,12 +198,9 @@ table.AssertTable().RowCount(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.
 table.AssertTable().RowRange(ArtOfTest.Common.NumberRangeCompareType.OutsideRange, 1, 2);
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.Contains, "TD5");
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.NotContain, "TD37");
-{{endregion}}
+````
  
-#### __[VB]__
-
-          {{region }}
-
+````VB      
 ' Attribute checks
 Dim span As HtmlSpan = Find.ById(Of HtmlSpan)("Warning")
 span.AssertAttribute().Exists("style")
@@ -260,7 +254,7 @@ table.AssertTable().RowCount(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.
 table.AssertTable().RowRange(ArtOfTest.Common.NumberRangeCompareType.OutsideRange, 1, 2)
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.Contains, "TD5")
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.NotContain, "TD37")
-{{endregion}}
+````
 
 There are many other possible assert verification combinations built into the framework that you can take advantage of. The above examples are just a small subset of what is possible to help you get started implementing them in your code and crafting the kinds of verification you need for your particular website. Consult the API reference manual to learn about the other combinations.
 
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/html-wait-class.md b/docs-teststudiodev/code-in-test/html-control-suite/html-wait-class.md
index ee2f739e..843d250a 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/html-wait-class.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/html-wait-class.md
@@ -4,7 +4,7 @@ page_title: HtmlWait Class - Test Studio Dev Documentation
 description: HtmlWait Class
 position: 2
 ---
-#How to Use the HtmlWait Class#
+# How to Use the HtmlWait Class
 
 The HtmlWait class extends and enhances the Element.Wait class with some powerful methods that are very useful with the HTML control suite. It adds:
 
@@ -17,10 +17,7 @@ The HtmlWait class extends and enhances the Element.Wait class with some powerfu
 The HtmlWait.ForVisible and HtmlWait.ForVisibleNot use the HtmlControl.IsVisible function to test whether or not the element is currently visible in the browser. Since IsVisible follows the CSS chain, we get a true reading of whether or not the element actually is visible. For example:
 
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     HtmlDiv div = Find.ByTagIndex<HtmlDiv>("div", 0);
     HtmlWait waitObj = div.Wait;
     
@@ -35,12 +32,8 @@ The HtmlWait.ForVisible and HtmlWait.ForVisibleNot use the HtmlControl.IsVisible
     waitObj.ForVisible();
     // Wait 120 seconds for the div to become invisible
     waitObj.ForVisibleNot();
-    {{endregion}}
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
     HtmlDiv div = Find.ByTagIndex<HtmlDiv>("div", 0);
     HtmlWait waitObj = div.Wait;
     
@@ -55,14 +48,11 @@ The HtmlWait.ForVisible and HtmlWait.ForVisibleNot use the HtmlControl.IsVisible
     waitObj.ForVisible();
     // Wait 120 seconds for the div to become invisible
     waitObj.ForVisibleNot();
-    {{endregion}}
+````
 
 Using the HtmlWait.ForStyles and HtmlWait.ForStylesNot methods you can wait for a particular style to be set or removed from the element. For example:
 
-#### __[C#]__
-
-          {{region }}
-            
+````C#                  
     HtmlSpan span = Find.ByTagIndex<HtmlSpan>("span", 0);
     HtmlWait spanWaitObj = div.Wait;
     
@@ -94,13 +84,8 @@ Using the HtmlWait.ForStyles and HtmlWait.ForStylesNot methods you can wait for
     // Will continue to wait if either style is still set to the specified value.
     // Uses the default timeout value from Settings.Current.ExecuteCommandTimeout
     span.Wait.ForStylesNot("backgroundColor=red", "margin=30px");
-    {{endregion}}
- 
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
     Dim span As HtmlSpan = Find.ByTagIndex(Of HtmlSpan)("span", 0)
     Dim spanWaitObj As HtmlWait = div.Wait
     
@@ -132,38 +117,28 @@ Using the HtmlWait.ForStyles and HtmlWait.ForStylesNot methods you can wait for
     ' Will continue to wait if either style is still set to the specified value.
     ' Uses the default timeout value from Settings.Current.ExecuteCommandTimeout
     span.Wait.ForStylesNot("backgroundColor=red", "margin=30px")
-    {{endregion}}
+````
 
 The HtmlWait.ForCondition is an advanced method that calls a user defined function to determine whether or not the wait condition has been satisfied. You, the test automation programmer, may code up any sort of wait condition you can imagine. The only requirement is that your function must return true to indicate that the condition has been satisfied or return false to indicate the condition has not been satisfied.
  
 The overloads of the HtmlWait.ForCondition are split into two virtually identical sets of three overloads. The first set operates on basic Element objects. The second set operates on Control objects, which all of the classes contained in the HTML control suite derive from. Except for this difference, they operate identically. The sample below shows only the Control version:
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
     HtmlTextArea textArea = Find.ByTagIndex<HtmlTextArea>("textarea", 0);
     HtmlWait textAreaWaitObj = textArea.Wait;
     // Wait 30 seconds for the HtmlTextArea element to contain the text "Now is the time"
     textArea.Wait.ForCondition(textAreaContainsStr, false, "Now is the time", 30000);
-    {{endregion}}
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
     Dim textArea As HtmlTextArea = Find.ByTagIndex(Of HtmlTextArea)("textarea", 0)
     Dim textAreaWaitObj As HtmlWait = textArea.Wait
     ' Wait 30 seconds for the HtmlTextArea element to contain the text "Now is the time"
     textArea.Wait.ForCondition(AddressOf textAreaContainsStr, False, "Now is the time", 30000)
-    {{endregion}}
+````
     
 Now we need the definition of the condition function 'textAreaContainsStr':
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
     /// <summary>
     /// Tests whether or not the HtmlTextArea element contains the specified string.
     /// </summary>
@@ -185,13 +160,8 @@ Now we need the definition of the condition function 'textAreaContainsStr':
         HtmlTextArea textArea = (HtmlTextArea)ctl;
         return textArea.Text.Contains((string)obj);
     }
-    {{endregion}}
- 
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
     ''' <summary>
     ''' Tests whether or not the HtmlTextArea element contains the specified string.
     ''' </summary>
@@ -212,4 +182,4 @@ Now we need the definition of the condition function 'textAreaContainsStr':
         Return textArea.Text.Contains(CType(obj, String))
     
     End Function
-    {{endregion}}
+````
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/introduction.md b/docs-teststudiodev/code-in-test/html-control-suite/introduction.md
index 5c9b159b..7d64b5d8 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/introduction.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/introduction.md
@@ -4,7 +4,7 @@ page_title: Introduction - Test Studio Dev Documentation
 description: Introduction
 position: 1
 ---
-#Intro to Test Studio Devs HTML Control Element Wrappers Suite#
+# Intro to Test Studio Devs HTML Control Element Wrappers Suite
 
 Telerik Framework includes an extensive suite of strongly typed HTML element wrappers that abstracts out actions and verifications of the controls contained on the webpage. With the classes contained in the control suite you can do things like:
 
@@ -22,7 +22,9 @@ In addition there are many other features that make the abstraction even more po
 	<th>HTML Control</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlAnchor**</td>
+<td>
+	
+**HtmlAnchor**</td>
 	<td>Wraps access to a HTML \<a> anchor element.</td>
 	<td>HRef<br>
 	Name<br>
@@ -32,7 +34,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlButton**</td>
+<td>
+	
+**HtmlButton**</td>
 	<td>Wraps access to a HTML \<button> element.</td>
 	<td>Disabled
 	Name<br>
@@ -42,14 +46,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionDescription**</td>
+<td>
+	
+**HtmlDefinitionDescription**</td>
 	<td>Wraps access to a HTML \<dd /> element . This control is used by the HtmlDefinitionList control.</td>
 	<td>Description</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionList**</td>
+<td>
+	
+**HtmlDefinitionList**</td>
 	<td>Wraps access to a HTML \<dl> element.</td>
 	<td>Descriptions<br>
 	Terms</td>
@@ -57,21 +65,27 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionTerm**</td>
+<td>
+	
+**HtmlDefinitionTerm**</td>
 	<td>Wraps access to a HTML \<dt> element. This control is used by the HtmlDefinitionList control.</td>
 	<td>Terms</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDiv**</td>
+<td>
+	
+**HtmlDiv**</td>
 	<td>Wraps access to a HTML \<div> container element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlForm**</td>
+<td>
+	
+**HtmlForm**</td>
 	<td>Wraps access to a HTML \<form> element.</td>
 	<td>EncType<br>
 	Length<br>
@@ -81,7 +95,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlImage**</td>
+<td>
+	
+**HtmlImage**</td>
 	<td>Wraps access to a HTML \<image> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -93,7 +109,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputButton**</td>
+<td>
+	
+**HtmlInputButton**</td>
 	<td>Wraps access to a HTML \<input type=button> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -105,28 +123,36 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputCheckBox**</td>
+<td>
+	
+**HtmlInputCheckBox**</td>
 	<td>Wraps access to a HTML \<input type=checkbox> element.</td>
 	<td>Checked</td>
 	<td>Check</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputFile**</td>
+<td>
+	
+**HtmlInputFile**</td>
 	<td>Wraps access to a HTML \<input type=file> element.</td>
 	<td>FilePath</td>
 	<td>Upload</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputHidden**</td>
+<td>
+	
+**HtmlInputHidden**</td>
 	<td>Wraps access to a HTML \<input type=hidden> element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputImage**</td>
+<td>
+	
+**HtmlInputImage**</td>
 	<td>Wraps access to a HTML \<input type=image> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -138,7 +164,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputPassword**</td>
+<td>
+	
+**HtmlInputPassword**</td>
 	<td>Wraps access to a HTML \<input type=password> element.</td>
 	<td>Disabled
 	Size<br>
@@ -148,14 +176,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputRadioButton**</td>
+<td>
+	
+**HtmlInputRadioButton**</td>
 	<td>Wraps access to a HTML \<input type=radio> element.</td>
 	<td>Cheched</td>
 	<td>Check</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputReset**</td>
+<td>
+	
+**HtmlInputReset**</td>
 	<td>Wraps access to a HTML \<input type=reset> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -167,7 +199,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputSubmit**</td>
+<td>
+	
+**HtmlInputSubmit**</td>
 	<td>Wraps access to a HTML \<input type=submit> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -179,7 +213,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputText**</td>
+<td>
+	
+**HtmlInputText**</td>
 	<td>Wraps access to a HTML \<input type=text> element.</td>
 	<td>Disabled<br>
 	Size<br>
@@ -189,14 +225,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlListItem**</td>
+<td>
+	
+**HtmlListItem**</td>
 	<td>Wraps access to a HTML \<li> element. This control is used by the HtmlOrdererList control and the HtmlUnorderedList control.</td>
 	<td>GetItemOrder</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlOption**</td>
+<td>
+	
+**HtmlOption**</td>
 	<td>Wraps access to a HTML \<option> element which is a member of a select element.</td>
 	<td>Selected<br>
 	Text<br>
@@ -205,7 +245,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlOrderedList**</td>
+<td>
+	
+**HtmlOrderedList**</td>
 	<td>Wraps access to a HTML \<ol>.</td>
 	<td>AllItems<br>
 	Itemst</td>
@@ -213,7 +255,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlSelect**</td>
+<td>
+	
+**HtmlSelect**</td>
 	<td>Wraps access to a HTML \<select> list box or drop-down list element.</td>
 	<td>Options<br>
 	SelectedIndex<br>
@@ -230,14 +274,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlSpan**</td>
+<td>
+	
+**HtmlSpan**</td>
 	<td>Wraps access to a HTML \<span> inline text container element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTable**</td>
+<td>
+	
+**HtmlTable**</td>
 	<td>Wraps access to a HTML \<table> table element containing rows and columns.</td>
 	<td>AllRows<br>
 	BodyRows<br>
@@ -255,7 +303,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTableCell**</td>
+<td>
+	
+**HtmlTableCell**</td>
 	<td>Wraps access to a HTML \<td> table cell element.</td>
 	<td>Align<br>
 	BgColor<br>
@@ -271,7 +321,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTableRow**</td>
+<td>
+	
+**HtmlTableRow**</td>
 	<td>Wraps access to a HTML \<tr> element.</td>
 	<td>Align<br>
 	BgColor<br>
@@ -284,7 +336,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTextArea**</td>
+<td>
+	
+**HtmlTextArea**</td>
 	<td>Wraps access to a HTML \<textArea> text input element.</td>
 	<td>Cols<br>
 	Rows<br>
@@ -293,7 +347,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlUnorderedList**</td>
+<td>
+	
+**HtmlUnorderedList**</td>
 	<td>Wraps access to a HTML \<ul> element.</td>
 	<td>AllItems<br>
 	Items</td>
@@ -310,7 +366,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<th>Base Class</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlContainerControl**</td>
+<td>
+	
+**HtmlContainerControl**</td>
 	<td>Base class for all wrapper controls that can contain other controls.</td>
 	<td>Find<br>
 	InnerText<br>	
@@ -319,7 +377,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>HtmlControl</td>
 </tr>
 <tr>
-	<td>**HtmlInputControl**</td>
+<td>
+	
+**HtmlInputControl**</td>
 	<td>Base class for all input wrapper controls.</td>
 	<td>Name<br>
 	Type<br>
@@ -328,7 +388,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>HtmlControl</td>
 </tr>
 <tr>
-	<td>**HtmlControl**</td>
+<td>
+	
+**HtmlControl**</td>
 	<td>Base class for the entire HTML wrapper control suite.</td>
 	<td>Attributes<br>
 	ChildNodes<br>
@@ -365,7 +427,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>Control</td>
 </tr>
 <tr>
-	<td>**Control**</td>
+<td>
+	
+**Control**</td>
 	<td>Root base class for all WebAii controls.</td>
 	<td>BaseElement<br>
 	IsRefresh<br>
@@ -389,7 +453,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<th>Base Class</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlFind**</td>
+<td>
+	
+**HtmlFind**</td>
 	<td>An extended Find class that includes HTML specific find methods.</td>
 	<td>Table<br>
 	TableCell<br>
@@ -398,7 +464,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<td>Find</td>
 </tr>
 <tr>
-	<td>**HtmlStyle**</td>
+<td>
+	
+**HtmlStyle**</td>
 	<td>Represents a single HtmlStyle. This object can be used to help probe and do validation against Html styles. Has functionality to convert unit styles to int values and color styles to System.Drawing.Color.</td>
 	<td>Name<br>
 	Value</td>
@@ -411,7 +479,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<td>Name<br>Value</td>
 </tr>
 <tr>
-	<td>**HtmlWait**</td>
+<td>
+	
+**HtmlWait**</td>
 	<td>An extended Wait class that includes HTML specific wait methods.</td>
 	<td></td>
 	<td>ForCondition<br>
@@ -425,14 +495,11 @@ Here is a list of the support classes that make it easier to use the rest of the
 <table>
 *Table 3. List of HtmlControl support classes contained in Telerik Testing Framework's HTML control suite.*
 
-##Example of How to Fill Out a Web Form Using the HTML Element Wrapper Control Suite##
+## Example of How to Fill Out a Web Form Using the HTML Element Wrapper Control Suite
 
 Suppose we're automating a form to submit an auto classified ad. Here's how to write the code and take advantage of the HTML element wrapper suite:
 
-#### __[C#]__
-
-          {{region }}
-
+````C#      
 	[TestClass]
 	public class SubmitAdTestClass : BaseTest
 	{
@@ -502,13 +569,8 @@ Suppose we're automating a form to submit an auto classified ad. Here's how to w
 			submit.Click();
 		}
 	}
-	{{endregion}}
- 
-
-#### __[VB]__
-
-          {{region }}
-
+````
+````VB      
 	<TestClass()> _
 	Public Class SubmitAdTestClass
 		Inherits BaseTest
@@ -581,11 +643,11 @@ Suppose we're automating a form to submit an auto classified ad. Here's how to w
 		End Sub
 	
 	End Class
-	{{endregion}}
+````
 	
 By taking advantage of the object oriented nature of the HTML element wrapper classes, our test code that fills in the fields and clicks the submit button is much simpler, more descriptive and more intuitive in nature. Note how simple it was to enter text into all the input fields, as well as make all the drop down selections using intuitive methods included with Telerik's HTML element wrapper classes!
-Also notice how we're doing a nested find. The line **form.Find.AllByTagName<HtmlSelect>("select");** is returning all of the **\<select>** elements that are contained within the form "Form2" contained on the page, not the entire page itself which may contain other \<select> elements on the page, perhaps even on other forms contained on the same page.
+Also notice how we're doing a nested find. The line `form.Find.AllByTagName<HtmlSelect>("select");` is returning all of the `<select>` elements that are contained within the form "Form2" contained on the page, not the entire page itself which may contain other `<select>` elements on the page, perhaps even on other forms contained on the same page.
  
-One special feature to note about the **Find.AllByXXX<TControl>()** functions is that they filter on the type of the **TControl** such that the returned list only includes elements of type **TControl**. In the example above we're calling **Find.AllByTagName<HtmlInputText>("input")**. Due to the filtering being performed by the framework we only get back \<input type="text"> elements and not other input elements such as the \<input type="password"> element that is also on the form.
+One special feature to note about the `Find.AllByXXX<TControl>()` functions is that they filter on the type of the `TControl` such that the returned list only includes elements of type `TControl`. In the example above we're calling `Find.AllByTagName<HtmlInputText>("input")`. Due to the filtering being performed by the framework we only get back `<input type="text">` elements and not other input elements such as the `<input type="password">` element that is also on the form.
  
-By the same token all of the Fi**nd.ByXXX<TControl>()** functions also verify that the found element is of type **TControl**. If, for example, you call **Find.ByTagIndex<HtmlInputPassword>("input", 4)** and the 5th \<input> element is not type="password" then the framework will throw a System.ArgumentException.
+By the same token all of the `Find.ByXXX<TControl>()` functions also verify that the found element is of type `TControl`. If, for example, you call `Find.ByTagIndex<HtmlInputPassword>("input", 4)` and the 5th `<input>` element is not type="password" then the framework will throw a System.ArgumentException.
diff --git a/docs-teststudiodev/code-in-test/html-control-suite/transfer-files.md b/docs-teststudiodev/code-in-test/html-control-suite/transfer-files.md
index f38956bc..261820c3 100644
--- a/docs-teststudiodev/code-in-test/html-control-suite/transfer-files.md
+++ b/docs-teststudiodev/code-in-test/html-control-suite/transfer-files.md
@@ -4,33 +4,27 @@ page_title: Transfer Files - Test Studio Dev Documentation
 description: Transfer Files
 position: 2
 ---
-#How to Transfer Files#
+# How to Transfer Files
 
 We can even perform complete file uploads and downloads with Telerik Testing Framework automatically handling all of the popup dialogs that appear as part of the file upload/download:
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     // Initiate a file upload
     Find.ByTagIndex<HtmlInputFile>("input", 0).Upload(
         Path.Combine(Globals.PATH_TO_PAGES, @"..\SupportFiles\EmptyTextFile.txt"), 5000);
     
     // Initiate a file download. Download will not return until the download is complete.
     Find.ByTagIndex<HtmlAnchor>("a", 0).Download(false, DownloadOption.Save, saveLocation, 20000);
-{{endregion}}
+````
  
 
-#### __[C#]__
-
-            {{region }}
-
+````C#        
     ' Initiate a file upload
     Find.ByTagIndex(Of HtmlInputFile)("input", 0).Upload( _
         Path.Combine(Globals.PATH_TO_PAGES, "..\SupportFiles\EmptyTextFile.txt"), 5000)
     
     ' Initiate a file download. Download will not return until the download is complete.
     Find.ByTagIndex(Of HtmlAnchor)("a", 0).Download(False, DownloadOption.Save, saveLocation, 20000)
-    {{endregion}}
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/images/fig1.png b/docs-teststudiodev/code-in-test/images/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig2.png b/docs-teststudiodev/code-in-test/images/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig3.png b/docs-teststudiodev/code-in-test/images/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig4.png b/docs-teststudiodev/code-in-test/images/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig5.png b/docs-teststudiodev/code-in-test/images/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig6.png b/docs-teststudiodev/code-in-test/images/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig7.png b/docs-teststudiodev/code-in-test/images/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig8.png b/docs-teststudiodev/code-in-test/images/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/fig9.png b/docs-teststudiodev/code-in-test/images/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/images/script-file.png b/docs-teststudiodev/code-in-test/images/script-file.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/Annotator.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/Annotator.md
index 98d9d9be..714af63e 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/Annotator.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/Annotator.md
@@ -4,63 +4,59 @@ page_title: Annotator
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Annotator#
+# Annotator
 
 The annotator displays in the browser window the actions that Telerik Testing Framework is performing along with highlighting the UI element that it is acting upon. If the action does not involve a UI element (such as navigating to a URL or creating a cookie) the action is displayed at the top of the browsers window. Here is what the annotator looks like in action:
 
 ![Annotation][1]
 
-##Activating the Annotator via the Application .config File##
+## Activating the Annotator via the Application .config File
 
 There are 2 methods to activating Telerik Testing Framework's automatic annotator. The simplest method is to activate it via the application .config file. By setting "annotateExecution" to true, the framework turns on the annotator and begins annotating all actions in the browser
 
-```XML
+````XML
 <WebAii.Settings
   annotateExecution="true"
 />
-```
+````
 
-##Activating the Annotator Programmatically##
+## Activating the Annotator Programmatically
 
 The next method is to turn on the annotator programmatically in your application. This is accomplished by placing this simple line of code in your unit test:
 
-```C#
+````C#
 // Enable Annotated Execution.
 Manager.Settings.AnnotateExecution = true;
 // Disable Annotated Execution.
 Manager.Settings.AnnotateExecution = false;
-```
- 
-
-```VB
+````
+````VB
 ' Enable Annotated Execution.
 Manager.Settings.AnnotateExecution = True
 ' Disable Annotated Execution.
 Manager.Settings.AnnotateExecution = False
-```
+````
 
-##Performing Your Own Annotation##
+## Performing Your Own Annotation
 
 You can also perform your own annotation programmatically using the Annotator class. First you must create an Annotator object passing into it which browser window to display annotation in. Once you have an Annotator object you can call one of the annotate functions. For example:
 
-```C#
+````C#
 Annotator myAnnotator = new Annotator(ActiveBrowser);
 myAnnotator.Annotate("This annotation message appears at the top of the browser document window");
 myAnnotator.Annotate("This annotation message appears at the top left corner of the browser document window",
      350, OffsetReference.TopLeftCorner);
 myAnnotator.Annotate(new Point(100, 300), "This annotation message appears under the point at 100,300 in the browser document window");
 myAnnotator.Annotate(Find.ById("btn1").GetRectangle(), "This annotation highlights the Color On button");
-```
- 
-
-```VB
+````
+````VB
 Dim myAnnotator As Annotator = New Annotator(ActiveBrowser)
 myAnnotator.Annotate("This annotation message appears at the top of the browser document window")
 myAnnotator.Annotate("This annotation message appears at the top left corner of the browser document window", _
                       350, OffsetReference.TopLeftCorner)
 myAnnotator.Annotate(New Point(100, 300), "This annotation message appears under the point at 100,300 in the browser document window")
 myAnnotator.Annotate(Find.ById("btn1").GetRectangle(), "This annotation highlights the Color On button")
-```
+````
 
 [1]: images/annotator/fig1.png
 
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/ajax-support.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/ajax-support.md
index abf6a709..a19ad90d 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/ajax-support.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/ajax-support.md
@@ -4,7 +4,7 @@ page_title: Ajax Support
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Ajax Support#
+# Ajax Support
 
 Ajax is one of the latest and fastest growing web development technologies that is fueling today's Web 2.0 era. The technology enables developers to build great and rich web content. However at the same time it adds great complexity to the testing methods required to validate the web applications that use it. To a certain extent, websites that rely heavily on Ajax can no longer rely on using the legacy HTTP record/replay methods to test the entire functionality given that major portions of the website logic are executed within the browser JavaScript engine and in some cases no HTTP requests are being made to the server at all!
 
@@ -26,23 +26,23 @@ Telerik Testing Framework has been built from the ground up with features like A
 
 * **Attach event handlers** directly to JavaScript events. This topic is covered in detail under <a href="/code-in-test/advanced-topics-wtc/javascript-wtc/javascript-events" target="_blank">JavaScript Events</a>.
 
-##Waiting on DOM Changes: WaitForElement(s)##
+## Waiting on DOM Changes: WaitForElement(s)
 
 **WaitForElement**(s) is a great method to use when trying to suspend test execution until a certain element is present or has changed or a specific value of a certain attribute for an element has been set (or even a combination of values). This is a common scenario when automating Ajax applications. WaitForElement(s) requires a basic understanding of <a href="/code-in-test/element-identification/find-param-objects" target="_blank">FindParams and how to define them</a>. Once you know how to craft FindParam's, you will be able to write custom and rich wait routines using a consistent pattern.
  
 Let's examine a couple of examples to illustrate how WaitForElement(s) is used. Assume that you are waiting for a table to be inserted in your DOM tree at a certain location and you want to wait until the whole table is built including the sixth row. The following is the DOM segment before the Ajax call is made:
 
-```HTML
+````HTML
 <!--testregion id="ajaxupdate"-->
 <div>
 </div>
 <!--/testregion-->
-```
+````
 
 Here is the DOM after the call has been made:
 
 
-```HTML
+````HTML
 <!--testregion id="ajaxupdate"-->
 <div>
   <table>
@@ -55,11 +55,11 @@ Here is the DOM after the call has been made:
    </table>
 </div>
 <!--/testregion-->
-```
+````
 
 The following code will perform this wait:
 
-```C#
+````C#
 // Get the ajaxupdate region.
 // Notice how using a testregion simplifies our identification and makes it
 // more isolated to the current DOM region being targeted and less prone
@@ -75,10 +75,8 @@ FindParam sixth_row = new FindParam("tr", 6);
 // perform the wait for both elements. WaitForElements() takes 1-N FindParam objects to
 // to wait for.
 ActiveBrowser.Actions.WaitForElements(500, ajaxupdate, false, table, sixth_row);
-```
- 
-
-```VB
+````
+````VB
 ' Get the ajaxupdate region.
 ' Notice how using a testregion simplifies our identification and makes it
 ' more isolated to the current DOM region being targeted and less prone
@@ -94,13 +92,13 @@ Dim sixth_row As FindParam = New FindParam("tr", 6)
 ' perform the wait for both elements. WaitForElements() takes 1-N FindParam objects to
 ' to wait for.
 ActiveBrowser.Actions.WaitForElements(500, ajaxupdate, False, table, sixth_row)
-```
+````
 
 In the above code sample, we used <a href="/code-in-test/advanced-topics-wtc/test-regions-wtc/Introduction" target="_blank">TestRegions</a> to make our automation simpler and targeted at the DOM region we are interested in. If you choose to not use TestRegions, you can simply use the WaitForElement(s) overload that takes in only the FindParam and the Timeout. In that case, all identification will be performed with reference to the root element of the DomTree.
  
 You can also use "Chained Identification" to wait for an element. For example if we have a DOM segment that looks like the sample below: 
 
-```HTML
+````HTML
 <spanid="myspan">
    <div>
      <table>
@@ -113,10 +111,10 @@ You can also use "Chained Identification" to wait for an element. For example if
      </table>
    </div>
  </span>
-```
+````
 ... and we want to wait until we have six rows available, then we can use chained identification as follows:
 
-```C#
+````C#
 // First find the span by id
 FindParam myspan = new FindParam("id=myspan");
   
@@ -125,10 +123,8 @@ FindParam sixth_row = new FindParam("tr", 5);
   
 // perform the wait for the row element.
 ActiveBrowser.Actions.WaitForElement(new FindParam[] { myspan, sixth_row }, 500);
-```
- 
-
-```VB
+````
+````VB
 ' First find the span by id
 Dim myspan As FindParam = New FindParam("id=myspan")
   
@@ -137,21 +133,21 @@ Dim sixth_row As FindParam = New FindParam("tr", 5)
   
 ' perform the wait for the row element.
 ActiveBrowser.Actions.WaitForElement(New FindParam() {myspan, sixth_row}, 500)
-```
+````
 
 The above scenario is one of the most common when testing Ajax apps. Therefore, the WaitForElement provides an easy to use overload for these common scenarios where you need to first identify an element by id/name then validate a certain attribute list. This helps reduce the lines of code each time you need to identify an element. If you need a more complex identification, you can use chained identification as described above.
 
-##Retrieving Dynamic Property Values Directly From the DOM##
+## Retrieving Dynamic Property Values Directly From the DOM
 
 When using Ajax the application, in most scenarios, updates the document's DOM using JavaScript. The DOM tree provided to your test code by Telerik Testing Framework is automatically updated after each command gets executed against the browser if Browser.AutoDomRefresh property is set to "true," which is the default value. In most scenarios the DOM tree is the latest up-to-date DOM tree from the browser. In cases where the DOM tree is updated without using Telerik browser commands (for example, the page auto-refreshes based on an internal timer, or you are using Pure UI automation), you can always refresh the DOM by calling Browser.RefreshDomTree().
  
 In some scenarios that might not even be enough. For example, you want to retrieve a property value that doesn't usually get emitted into the DOM when serialized like the default or inherited values of an unset property or in Firefox the 'value' property of input tags.
  
-To help address this issue and potentially other issues, the Telerik infrastructure supports a generic and simple method of retrieving any property of any element directly from the live DOM hosted in the browser. Each Element object in the Telerik Testing Framework has a GetValue<T>() method that you can use to evaluate any custom or standard attribute of your Dom element at any point in your test code or application.
+To help address this issue and potentially other issues, the Telerik infrastructure supports a generic and simple method of retrieving any property of any element directly from the live DOM hosted in the browser. Each Element object in the Telerik Testing Framework has a `GetValue<T>()` method that you can use to evaluate any custom or standard attribute of your Dom element at any point in your test code or application.
  
 For example, if you want to retrieve the text set by a user in an input textbox in Firefox, you can simply do the following:
 
-```C#
+````C#
 // Get the element.
 Element input = ActiveBrowser.Find.ById("myinput");
   
@@ -163,10 +159,8 @@ string display = input.GetValue<string>("display");
   
 // Get its 'visibility' property from the DOM
 string visibility = input.GetValue<string>("visibility");
-```
- 
-
-```VB
+````
+````VB
 ' Get the element.
 Dim input As Element = ActiveBrowser.Find.ById("myinput")
   
@@ -178,19 +172,17 @@ Dim display As String = input.GetValue(Of String)("display")
   
 ' Get its 'visibility' property from the DOM
 Dim visibility As String = input.GetValue(Of String)("visibility")
-```
+````
 
 **Note:** If you are retrieving property values of set attributes available in the serialized DOM string, you should use the GetAttribute() method to retrieve these attributes and their values.
 
-##Browser.WaitForAjax()##
+## Browser.WaitForAjax()
 
 This method will wait for any active AJAX requests to complete.
 
-```C#
+````C#
 Manager.ActiveBrowser.WaitForAjax(30000);
-```
- 
-
-```VB
+````
+````VB
 Manager.ActiveBrowser.WaitForAjax(30000)
-```
+````
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/app-config-file.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/app-config-file.md
index b899ddf7..b69884a9 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/app-config-file.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/app-config-file.md
@@ -5,28 +5,27 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/using-application-config-file.aspx, /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/using-application-config-file
 position: 1
 ---
-#Using the Application's .config File#
+# Using the Application's .config File
 
 Instead of programmatically setting the configuration, the application or test program can use an application .config file to fetch the appropriate settings. The Telerik infrastructure has a built in .NET Config SectionHandler (under the 'ArtOfTest.Core' namespace) that can read the configuration settings from the .config file associated with the application or test. You place the settings in your .config file as follows:
 
 1.&nbsp; First add the following line to the 'configSections' section:
 
-```XML
+````XML
 <configSections>                                     
 <section name="WebAii.Settings" type="ArtOfTest.WebAii.Core.SettingsConfigSectionHandler,ArtOfTest.WebAii"/>
 <section name="WebAii.Settings.Web" type="ArtOfTest.WebAii.Core.WebSettingsConfigSectionHandler,ArtOfTest.WebAii"/>
 <section type="ArtOfTest.WebAii.Core.WpfSettingsConfigSectionHandler,ArtOfTest.WebAii" name="WebAii.Settings.Wpf"/>  
 </configSections>
-```
+````
 
 2.&nbsp; Then add the settings you need under the 'WebAii.Settings' section or WebAii.Settings.Web' section.
 
-	**Note:** It is not necessary to include all of Telerik's settings in your .config file. You only need to add settings for those you wish to override. The Telerik Testing Framework uses default values for any setting not explicitly set in the .config file. 
-
-	**Note:** The configuration setting names are case sensitive e.g.  **AnnotateExecution** will not be recognized and will cause an exception to be thrown while **annotateExecution** will be recognized and used.
+**Note:** It is not necessary to include all of Telerik's settings in your .config file. You only need to add settings for those you wish to override. The Telerik Testing Framework uses default values for any setting not explicitly set in the .config file. 
 
+**Note:** The configuration setting names are case sensitive e.g.  **AnnotateExecution** will not be recognized and will cause an exception to be thrown while **annotateExecution** will be recognized and used.
 		
-```XML
+````XML
 	<WebAii.Settings                                           
                    logLocation="F:\Log\"
                    executionTimeout="30000"
@@ -41,11 +40,11 @@ Instead of programmatically setting the configuration, the application or test p
 	</WebAii.Settings>
 	<WebAii.Settings.Web baseUrl="http://www.lava.com">           
 	</WebAii.Settings.Web>
-```
+````
 
 Here is an example of a complete app.config file that contains all of Telerik's configuration settings:
 
-```XML
+````XML
 <?xml version="1.0" encoding="UTF-8"?>
 <configuration>
  <configSections>
@@ -57,17 +56,15 @@ Here is an example of a complete app.config file that contains all of Telerik's
  <WebAii.Settings.Web verboseHttpProxy="false" enableSilverlight="true" useHttpProxy="false" enableUILessRequestViewing="false" aspNetDevServerPort="-1" webAppPhysicalPath="" localWebServer="None" silverlightApplicationPath="" silverlightConnectTimeout="30000" enableScriptLogging="false" defaultBrowser="InternetExplorer" killBrowserProcessOnClose="false" baseUrl="http://www.telerik.com"> </WebAii.Settings.Web>
 <WebAii.Settings.Wpf defaultApplicationPath="E:\Users\Dad\Documents\visual studio 2010\Projects\TelerikWpfApp1\TelerikWpfApp1\bin\Debug\TelerikWpfApp1.exe" />
 </configuration>
-```	
+````
 In your test code initialization, you read these settings by simply setting the UseConfig flag to true when calling the Manager() constructor. If you use the BaseTest template (which is what the VsUnit, MbUnit, NUnit and xUnit templates do) this call is done for you by BaseTest during the Initialize call:
 
-```C#
+````C#
 Manager mgr = new Manager(true);
-```
- 
-
-```VB
+````
+````VB
 Dim myManager As Manager = New Manager(True)
-```
+````
 
 **Note:** If you are using Telerik's BaseTest (which the Telerik VS item templates use), there is no need to for your test code to read from the app.config file as shown above. The base class already does that for you. Read the item template's comments for the initialization routine for more details.
 
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/configure-browser-In-code.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/configure-browser-In-code.md
index 91630a51..f089574f 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/configure-browser-In-code.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/configure-browser-In-code.md
@@ -4,11 +4,11 @@ page_title: Configure Browser In Code
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Configure Browser In Code#
+# Configure Browser In Code
 
 Apart from manually configuring each of the browsers for test execution this could be also accomplished in code. 
 
-```C#
+````C#
 //declare string variable to write possible errors in 
 string error;
 // to configure FireFox
@@ -21,13 +21,12 @@ Manager.ConfigureBrowser(BrowserType.InternetExplorer, out error);
 Manager.ConfigureBrowser(BrowserType.Safari, out error);
 // to configure Edge
 Manager.ConfigureBrowser(BrowserType.MicrosoftEdge, out error);
-```
-
-```VB
+````
+````VB
 Dim error As String
 Manager.ConfigureBrowser(BrowserType.FireFox, error)
 Manager.ConfigureBrowser(BrowserType.Chrome, error)
 Manager.ConfigureBrowser(BrowserType.InternetExplorer, error)
 Manager.ConfigureBrowser(BrowserType.Safari, error)
 Manager.ConfigureBrowser(BrowserType.MicrosoftEdge, error)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/cookie-support.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/cookie-support.md
index 071a65d8..322b174c 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/cookie-support.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/cookie-support.md
@@ -4,7 +4,7 @@ page_title: Cookie Support
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Cookie Support#
+# Cookie Support
 
 Using the CookieManager class you can:
 
@@ -16,81 +16,71 @@ Using the CookieManager class you can:
 
 * Delete a cookie in the browser
 
-##Retrieving Cookies##
+## Retrieving Cookies
 
 There are two functions that can be used to retrieve cookies from the browser:
 
 
-```C#
+````C#
 public CookieCollection GetCookies (string url)
 public CookieCollection GetCookies (Uri uri)
-```
- 
-
-```VB
+````
+````VB
 Public Function GetCookies(ByVal url As String) As System.Net.CookieCollection
 Public Function GetCookies(ByVal uri As System.Uri) As System.Net.CookieCollection
-```
+````
 
 These functions retrieve all the cookies from the browser for the specified website. For example:
 
-```C#
+````C#
 // Query the cookie
 System.Net.CookieCollection siteCookies = ActiveBrowser.Cookies.GetCookies("http://www.telerik.com");
-```
- 
-
-```VB
+````
+````VB
 ' Query the cookie
 Dim siteCookies As System.Net.CookieCollection = ActiveBrowser.Cookies.GetCookies("http://www.telerik.com")
-```
+````
 
-##Creating and Setting Cookies##
+## Creating and Setting Cookies
 
 Below is an example of how to create or set a cookie. If the cookie already exists, it will be overwritten. If it does not exist, a new cookie will be created in the browser:
 
-```C#
+````C#
 // Let's create a new cookie for a url.
 ActiveBrowser.Cookies.SetCookie(new System.Net.Cookie("WebAii", "Rocks", "/", "http://www.telerik.com"));
-```
- 
-
-```VB
+````
+````VB
 ' Let's create a new cookie for a url.
 ActiveBrowser.Cookies.SetCookie(New System.Net.Cookie("WebAii", "Rocks", "/", "http://www.telerik.com"))
-```
+````
 
-##Deleting Cookies##
+## Deleting Cookies
 
 Here is an example of how to delete a cookie:
 
-```C#
+````C#
 // Now delete the cookie.
 ActiveBrowser.Cookies.DeleteCookie(siteCookies[0]);
-```
- 
-
-```VB
+````
+````VB
 ' Now delete the cookie.
 ActiveBrowser.Cookies.DeleteCookie(siteCookies(0))
-```
+````
 
 A simple foreach loop can be used to delete all the cookies for a particular website:
 
-```C#
+````C#
 // Purge any cookies associated with this server
 System.Net.CookieCollection cookies = ActiveBrowser.Cookies.GetCookies(Settings.Current.BaseUrl);
 foreach (System.Net.Cookie cookie in cookies)
 {
     ActiveBrowser.Cookies.DeleteCookie(cookie);
 }
-```
- 
-
-```VB
+````
+````VB
 ' Purge any cookies associated with this server
 Dim cookies As System.Net.CookieCollection = ActiveBrowser.Cookies.GetCookies(Settings.Current.BaseUrl)
 For Each cookie As System.Net.Cookie In cookies
      ActiveBrowser.Cookies.DeleteCookie(cookie)
 Next cookie
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/desktop-manager.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/desktop-manager.md
index 1656222e..f2ce3c09 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/desktop-manager.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/desktop-manager.md
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 position: 1
 ---
 
-#The Desktop Manager Class#
+# The Desktop Manager Class
 
 The Desktop manager class is used to control interaction between the Windows desktop and the browser. It also contains instances of the Keyboard and Mouse managers. It has the following properties:
 
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/annotator/fig1.png b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/annotator/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/visual-capturing/fig1.png b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/visual-capturing/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/visual-capturing/fig2.png b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/images/visual-capturing/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/keyboard-manager.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/keyboard-manager.md
index dde8cc1e..f57979f7 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/keyboard-manager.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/keyboard-manager.md
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 position: 1
 ---
 
-#The KeyBoard Manager Class#
+# The KeyBoard Manager Class
 
 The KeyBoard manager class is used to simulate typing keys on the keyboard. It has the following methods:
 
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/mouse-manager.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/mouse-manager.md
index c6630c01..3ded53f0 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/mouse-manager.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/mouse-manager.md
@@ -4,7 +4,7 @@ page_title: Mouse Manager
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Mouse Manager Class#
+# Mouse Manager Class
 
 The Mouse manager class is used to simulate moving the physical mouse and performing various types of mouse clicks. It has the following properties:
 
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
index fb3795ca..c20c3103 100644
--- 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
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/settings-class.aspx, /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/settings-class
 position: 1
 ---
-#Settings Class#
+# Settings Class
 
 How the Telerik Testing Framework behaves during a test run is controlled by the settings contained in the Settings object. There are many settings you can take advantage of to modify its behavior to better meet your testing requirements or testing environment. The complete list of settings is detailed in the table below. A few of the more commonly used settings include:
 
@@ -17,11 +17,11 @@ How the Telerik Testing Framework behaves during a test run is controlled by the
  
 There are a few methods of controlling the settings in the Settings object. Which method you use depends on when and how you want them set in your unit test.
 
-##Initializing the Settings Object Without Using a Telerik Test Template##
+## Initializing the Settings Object Without Using a Telerik Test Template
 
 If you're not using one of Telerik's test templates (VsUnit, NUnit, MbUnit, xUnit) to create your unit test, you'll need to create your own Settings object and then pass that object as a parameter to the constructor of your Manager object. For example:
 
-```C#
+````C#
 // Create my own Settings object and then modify the defaults
 Settings mySettings = new Settings();
 mySettings.DefaultBrowser = BrowserType.FireFox;
@@ -29,10 +29,8 @@ mySettings.ClientReadyTimeout = 60000;
   
 // Use my Settings object to construct my Manager object
 Manager myManager = new Manager(mySettings);
-```
- 
-
-```VB
+````
+````VB
 ' Create my own Settings object and then modify the defaults
 Dim mySettings As New Settings()
 mySettings.DefaultBrowser = BrowserType.FireFox
@@ -40,13 +38,13 @@ mySettings.ClientReadyTimeout = 60000
   
 ' Use my Settings object to construct my Manager object
 Dim myManager As New Manager(mySettings)
-```
+````
 
-##Initializing the Settings Object When Using a Test Template##
+## Initializing the Settings Object When Using a Test Template
 
 If you're using one of Telerik's test templates (VsUnit, NUnit, MbUnit, xUnit) to create your unit test, you'll need to create your own Settings object in the TestInitialize section (or Setup section if you're using NUnit) and then pass that object as a parameter to the Initialize method of the base class. For example:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -57,10 +55,8 @@ settings.UseHttpProxy = true;
   
 // Now call Initialize again with your updated settings object
 Initialize(settings, new TestContextWriteLine(this.TestContext.WriteLine));
-```
- 
-
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -71,28 +67,26 @@ settings.UseHttpProxy = True
   
 ' Now call Initialize again with your updated settings object
 Initialize(settings, New TestContextWriteLine(AddressOf Me.TestContext.WriteLine))
-```
+````
 
 **Note:** Be sure to call Initialize only once. Calling Initialize a second time will simply be ignored and you'll be left wondering why your settings did not take effect.
 
-##Changing Settings On-The-Fly##
+## Changing Settings On-The-Fly
 
 Lastly you can modify most of the settings after your test is already initialized and under-way. Here's how you to do that:
 
-```C#
+````C#
 Manager.Settings.AnnotateExecution = true;
 Manager.Settings.DefaultBrowser = BrowserType.FireFox;
-```
- 
-
-```VB
+````
+````VB
 Manager.Settings.AnnotateExecution = True
 Manager.Settings.DefaultBrowser = BrowserType.FireFox
-```
+````
 
 **Note:** The following settings can only be set during initialization: AspNetDevServerPort, CreateLogFile, EnableUILessRequestViewing, LocalWebServer, LogLocation, VerboseHttpProxy and WebAppPhysicalPath.
 
-##Using the RecycleBrowser Feature##
+## Using the RecycleBrowser Feature
 
 The RecycleBrowser feature was added in version 2.0. Using it can significantly speed up running an entire test suite, no more starting and shutting down of the browser for each individual unit test. It works by launching one browser window in the test fixture initialization of your test suite and then constantly reusing that same browser window for all unit tests contained in your test suite.
 
@@ -102,18 +96,16 @@ There are a just a couple of things you need to be aware of to properly use the
 
 2. You must call the base classes ShutDown() method in the test fixture teardown section to properly the browser window at the end of the test suite. If you miss this then browser windows will be left behind after your test suite has finished and exited.
 
-##Restoring Default Settings##
+## Restoring Default Settings
 
 If it ever becomes necessary you can restore all the settings (except for those that can only be set during initialization) back to their default values. Just use the Reset() method of the Settings object. For example:
 
-```C#
+````C#
 Manager.Settings.Reset();
-```
- 
-
-```VB
+````
+````VB
 Manager.Settings.Reset()
-```
+````
 
 This table lists all of the WebAii framework settings that are available for you to use:
 
@@ -122,167 +114,217 @@ This table lists all of the WebAii framework settings that are available for you
 	<th>Name</th><th>Description</th><th>Possible Values</th><th>Default Value</th>
 </tr>
 <tr>
-	<td>**AnnotateExecution**</td>
+<td>
+	
+**AnnotateExecution**</td>
 	<td>Controls whether or not to highlight/annotate the target elements that the requested action is being executed against. e.g. **Actions.Click(goButton)**;</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**AnnotationMode**</td>
+<td>
+	
+**AnnotationMode**</td>
 	<td>This read-only setting contains the full physical path to your local ASP.NET development web server (WebDev.WebServer.EXE). It is set by the framework when LocalWebServer is set to "AspNetDevelopmentServer". Otherwise it is an empty string.</td>
 	<td></td>
 	<td></td>
 </tr>
 <tr>
-	<td>**AspNetDevServerPort**</td>
+<td>
+	
+**AspNetDevServerPort**</td>
 	<td>Controls the AspNetDevServer (if used) port. If this is not set (-1) a random port will be generated each time the manager is created.</td>
 	<td>0 to int.MaxValue</td>
 	<td>Random value</td>
 </tr>
 <tr>
-	<td>**BaseUrl**</td>
+<td>
+	
+**BaseUrl**</td>
 	<td>Sets the base URL to use for all NavigateTo() commands. When set NavigateTo() should use a relative URL (e.g. "~/default.aspx").</td>
 	<td>Any valid URL</td>
 	<td>string.Empty</td>
 </tr>
 <tr>
-	<td>**ClientReadyTimeout**</td>
+<td>
+	
+**ClientReadyTimeout**</td>
 	<td>Timeout used to wait for a client (a browser) to be ready after it is first launched or after executing a command (in milliseconds). For example after launching the browser if the browser is not ready within this timeout the framework will throw a <a href="http://msdn2.microsoft.com/en-us/library/system.timeoutexception%28vs.80%29.aspx" target="_blank">TimeoutException</a>.</td>
 	<td>0 to int.MaxValue</td>
 	<td>30000</td>
 </tr>
 <tr>
-	<td>**CreateLogFile**</td>
+<td>
+	
+**CreateLogFile**</td>
 	<td>Gets or sets whether to create a log file on disk. This value is read once at initialization time. Changing this value during test execution has no effect.</td>
 	<td>true<br>
 	false</td>
 	<td>true</td>
 </tr>
 <tr>
-	<td>**DefaultBrowser**</td>
+<td>
+	
+**DefaultBrowser**</td>
 	<td>The default browser (i.e. Internet Explorer or Firefox or AspNetHost) to launch when calling Manager.LaunchNewBrowser().</td>
 	<td>"InternetExplorer"<br>
 	"FireFox"<br>
 	"AspNetHost"<br>
-	"Safari"h</td>
+	"Safari"</td>
 	<td>"InternetExplorer"</td>
 </tr>
 <tr>
-	<td>**EnableScriptLogging**</td>
+<td>
+	
+**EnableScriptLogging**</td>
 	<td>Globally enables or disables logging of JavaScript execution.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**EnableSilverlight**</td>
+<td>
+	
+**EnableSilverlight**</td>
 	<td>Controls whether or not Silverlight test automation is enabled.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**EnableUILessRequestViewing**</td>
+<td>
+	
+**EnableUILessRequestViewing**</td>
 	<td>Controls whether or not to allow debugging of UILess page requests using a UI browser like Internet Explorer.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**ExecuteCommandTimeout**</td>
+<td>
+	
+**ExecuteCommandTimeout**</td>
 	<td>The amount of time to wait for a response to be received from the browser (in milliseconds) after sending it a command request. For example: if there is no response from the browser within this amount of time after sending it a click request, the framework will throw a <a href="http://msdn2.microsoft.com/en-us/library/system.timeoutexception%28vs.80%29.aspx" target="_blank">TimeoutException</a>.</td>
 	<td>0 to int.MaxValue</td>
 	<td>20000</td>
 </tr>
 <tr>
-	<td>**ExecutionDelay**</td>
+<td>
+	
+**ExecutionDelay**</td>
 	<td>Sets the amount of execution delay (in milliseconds) between commands. This can help in observing test execution.</td>
 	<td>0 to int.MaxValue</td>
 	<td>0</td>
 </tr>
 <tr>
-	<td>**IsStressRecordingMode**</td>
+<td>
+	
+**IsStressRecordingMode**</td>
 	<td>Used internally by Automation Design Canvas only.</td>
 	<td></td>
 	<td></td>
 </tr>
 <tr>
-	<td>**IsUserInteractiveMode**</td>
+<td>
+	
+**IsUserInteractiveMode**</td>
 	<td>This read-only setting indicates whether or not the currently logged on user is an interactive user. Normally this will always be true unless you are logged in under a non-interactive account. For example, if you create another account on your machine and from your current account launch a process using that other account without interactively logging into that account. That is when this property will be set to false. This is a common scenario when performing continuous integration within a build system and running tests. Usually there is a machine that has an account that VisualStudio simply uses to logon the machine non-interactively, build a product and launch tests.</td>
 	<td>true<br>
 	false</td>
 	<td>Depends on run time environment.</td>
 </tr>
 <tr>
-	<td>**KillBrowserProcessOnClose**</td>
+<td>
+	
+**KillBrowserProcessOnClose**</td>
 	<td>Gets or sets whether to make sure the browser process is killed when closing the browser. **Note:** Firefox is a single process browser. If you are using multiple browser instances and this setting is on, it will kill all open instances of Firefox.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**LocalWebServer**</td>
+<td>
+	
+**LocalWebServer**</td>
 	<td>Controls whether or not to use the local ASP.NET development server. When set to true, be sure to set WebAppPhysicalPath to the full physical path of the root of your ASP.NET development server.</td>
 	<td>None<br>
 	AspNetDevelopmentServer</td>
 	<td>None</td>
 </tr>
 <tr>
-	<td>**LogAnnotations**</td>
+<td>
+	
+**LogAnnotations**</td>
 	<td>Controls whether to log annotations to the log file.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**LogLocation**</td>
+<td>
+	
+**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 </td>
 </tr>
 <tr>
-	<td>**QueryEventLogErrorsOnExit**</td>
+<td>
+	
+**QueryEventLogErrorsOnExit**</td>
 	<td>Controls whether or not the Manager object will query Windows Application Event log on exit for any error logged from automation clients. Any errors will be logged to the test log.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**RecycleBrowser**</td>
+<td>
+	
+**RecycleBrowser**</td>
 	<td>When set to true, one instance of the browser will be launched and recycled through out the entire test class and tests until Manager.Dispose is called.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**SimulatedMouseMoveSpeed**</td>
+<td>
+	
+**SimulatedMouseMoveSpeed**</td>
 	<td>Sets the simulated mouse move speed for Desktop.Mouse.Move()/DragDrop() operations in pixels/millisecond. Typically values are between 0.1f - 0.5f.</td>
 	<td>0 to Single.MaxValue</td>
 	<td>0.3</td>
 </tr>
 <tr>
-	<td>**UseHttpProxy**</td>
+<td>
+	
+**UseHttpProxy**</td>
 	<td>Gets/Sets whether to use the built-in http proxy during automation. **NOTE:** will be forced to true when EnableSilverlight is set to true.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**VerboseHttpProxy**</td>
+<td>
+	
+**VerboseHttpProxy**</td>
 	<td>Gets/Sets whether the HTTP proxy produces lots of tracing output.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**WaitCheckInterval**</td>
+<td>
+	
+**WaitCheckInterval**</td>
 	<td>Controls the rate that the condition is tested by the HtmlWait class. This value specifies the number of milliseconds to wait between tests of the condition.</td>
 	<td>1 to int.MaxValue</td>
 	<td>500</td>
 </tr>
 <tr>
-	<td>**WebAppPhysicalPath**</td>
+<td>
+	
+**WebAppPhysicalPath**</td>
 	<td>This setting is used when LocalWebServer is set to 'AspNetDevelopmentServer'. It must be the full physical path to the web application root that you are testing or a path relative to the location of the .config file.</td>
 	<td>The full physical path to the web application root.</td>
 	<td>string.Empty</td>
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/visual-capturing.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/visual-capturing.md
index 20c1ed2c..8f41171e 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/visual-capturing.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/visual-capturing.md
@@ -4,48 +4,44 @@ page_title: Visual Capturing
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Visual Capturing#
+# Visual Capturing
 
 
-##Visual Capturing of Browser States and Win32 Windows##
+## Visual Capturing of Browser States and Win32 Windows
 
 Each Telerik Testing Framework Window object provides functionality to capture the visual bitmaps of the actual window it represents. You can capture the entire window or a targeted portion of that window using the Window.GetBitmap() method. You can use this method for any Win32 window represented by the Window object. Lets take a quick example:
 
 
-```C#
+````C#
 // Get the current browser window bitmap.
 System.Drawing.Bitmap browserImage = ActiveBrowser.Window.GetBitmap();
-```
- 
-
-```VB
+````
+````VB
 Dim browserImage As System.Drawing.Bitmap = ActiveBrowser.Window.GetBitmap()
-```
+````
 
 The Log uses the above method to capture the browser window when calling the Log.CaptureBrowser() method. The log also saves the captured bitmap to the 'LogLocation' as provided by your settings and a line is added to the log file that points to that bitmap file. The bitmaps are also added to the Log.CapturedBitmaps[] array. For example:
 
 
-```C#
+````C#
 // Capture the bitmap of my current ActiveBrowser and save it to the LogLocation
 // [LogLocation is set using the Settings object that is passed in to the Manager's constructor]
 Manager.Log.CaptureBrowser(Manager.ActiveBrowser);
   
 // Note: If you are automating multiple browser instances, you can simply
 // call the CaptureBrowser() passing in any instance from the Manager.Browser[] collection.
-```
- 
-
-```VB
+````
+````VB
 Manager.Log.CaptureBrowser(Manager.ActiveBrowser)
-```
+````
 
-##Visual Capturing of Elements##
+## Visual Capturing of Elements
 
 In addition to capturing the entire window, you can also capture targeted portions of that window. Such functionality can be extremely useful when combined with the functionality provided by each DOM element in Telerik Testing Framework. For example, you can use the Element.GetRectangle() to get the coordinates of a specific element and pass that to the Window.GetBitmap(targetRectangle) to visually capture that element. You can then do bitmap comparisons of that element to a base line or even compare it across browsers.
  
 Let's take a simple example to demonstrate this functionality. Assume we have the following simple page:
 
-```HTML
+````HTML
 <html>
    <head>
     <title>Visual Capturing sample</title>
@@ -65,7 +61,7 @@ Let's take a simple example to demonstrate this functionality. Assume we have th
      </div>
    </body>
 </html>
-```
+````
 
 The above page renders as follows:
 
@@ -73,22 +69,20 @@ The above page renders as follows:
 
 The below code shows how we can get the visual capture of the second 'div' element:
 
-```C#
+````C#
 // Get the element
 Element myDiv = ActiveBrowser.Find.ById("mydiv");
   
 // Capture it visually as a bitmap
 System.Drawing.Bitmap divimage = ActiveBrowser.Window.GetBitmap(myDiv.GetRectangle());
-```
- 
-
-```VB
+````
+````VB
 ' Get the element
 Dim myDiv As Element = ActiveBrowser.Find.ById("mydiv")
   
 ' Capture it visually as a bitmap
 Dim divimage As System.Drawing.Bitmap = ActiveBrowser.Window.GetBitmap(myDiv.GetRectangle())
-```
+````
 The divimage bitmap captured object is:
 
 ![Captured div][2]
diff --git a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/win32-windows.md b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/win32-windows.md
index 495f9ddd..f4d6d7ea 100644
--- a/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/win32-windows.md
+++ b/docs-teststudiodev/code-in-test/settings-and-configuration-wtc/win32-windows.md
@@ -4,7 +4,7 @@ page_title: Win32 Windows
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
 ---
-#Native Win32 Windows Handling#
+# Native Win32 Windows Handling
 
 Telerik Testing Framework provides generic support for Win32 Windows handling. Under the 'ArtOfTest.Common.Win32' namespace, Telerik Framework provides two key objects that you can use in your test code to generically manage Win32 Windows and Dialogs.
 
@@ -17,7 +17,7 @@ In addition to the functionality described above, the WindowManager exposes a st
 Let's take an example to illustrate how these two classes can help provide automation functionality for native Win32 windows:
 
 
-```C#
+````C#
 Window vsWindow = null;
   
 // Get all desktop Windows
@@ -39,10 +39,8 @@ foreach (Window win in winManager.Items)
 // Find the vsWindow recursively. Passing IntPtr.Zero will start from the desktop.
 Window vsWindowRecur = WindowManager.FindWindowRecursively(
      IntPtr.Zero, "Microsoft Visual Studio", true, 0);
-```
- 
-
-```VB
+````
+````VB
 Dim vsWindow As Window = Nothing
   
 ' Get all desktop Windows
@@ -63,5 +61,5 @@ Next
 ' Find the vsWindow recursively. Passing IntPtr.Zero will start from the desktop.
 Dim vsWindowRecur As Window = WindowManager.FindWindowRecursively( _
      IntPtr.Zero, "Microsoft Visual Studio", True, 0)
-```
+````
 
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/element-validation.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/element-validation.md
index 463bd977..bfaba9ea 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/element-validation.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/element-validation.md
@@ -4,23 +4,21 @@ page_title: Element Validation
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Validating Properties of Silverlight Elements#
+# Validating Properties of Silverlight Elements
 
-```C#
+````C#
 Assert.IsTrue(guidanceOverlays.Count == 15);
 Assert.IsTrue(CompareUtils.NumberCompareRange(foundPatients.Count, 93, 105, NumberRangeCompareType.InRange);
 Assert.IsTrue(patientSearchItem.Find.ByName("Address").Visibility == Visibility.Collapsed);
 Assert.IsTrue(searchScroll.VerticalOffset == 2000);
 Assert.AreEqual<System.Drawing.Rectangle>(new System.Drawing.Rectangle(1700, 259, 813, 465), admin1.GetScreenRectangle());
-```
- 
-
-```VB
+````
+````VB
 app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy
 Assert.IsTrue(CompareUtils.NumberCompareRange(foundPatients.Count, 93, 105, NumberRangeCompareType.InRange))
 Assert.IsTrue(patientSearchItem.Find.ByName("Address").Visibility = Visibility.Collapsed)
 Assert.AreEqual(2000, searchScroll.VerticalOffset)
 Assert.AreEqual(Of System.Drawing.Rectangle)(New System.Drawing.Rectangle(1700, 259, 813, 465), admin1.GetScreenRectangle())
-```
+````
 
 
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/framework-element-object.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/framework-element-object.md
index 8d4010a2..9533eacc 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/framework-element-object.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/framework-element-object.md
@@ -4,7 +4,7 @@ page_title: FrameworkElement Object
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#FrameworkElement Object#
+# FrameworkElement Object
 
 The **FrameworkElement** object is analogous to the <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement(VS.95).aspx" target="_blank">FrameworkElement</a> in Silverlight and is the base object that all visual elements and controls inherit from in the **ArtOfTest.WebAii.Silverlight.UI** namespace. For customers interested in our extensibility model, the Silverlight Extension does not expose a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.95).aspx" target="_blank">UIElement</a> and therefore, our **FrameworkElement** can be viewed as the combination of Silverlight's **UIElement + FrameworkElement**.
  
@@ -15,135 +15,135 @@ The **FrameworkElement** and all objects that inherit from it get the following
 	<th>Property</th><th>Description</th>
 </tr>
 <tr>
-	<td>**AbsoluteSiblingTagIndex**</td><td>Get the sibling tag index of this FrameworkElement.</td>
+	<td>AbsoluteSiblingTagIndex</td><td>Get the sibling tag index of this FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**AbsoluteTagIndex**</td><td>Get the absolute index of this XAML tag in the Visual Tree.</td>
+	<td>AbsoluteTagIndex</td><td>Get the absolute index of this XAML tag in the Visual Tree.</td>
 </tr>
 <tr>
-	<td>**ActualHeight**</td><td>Gets the rendered height of a FrameworkElement.</td>
+	<td>ActualHeight</td><td>Gets the rendered height of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**ActualWidth**</td><td>Gets the rendered width of a FrameworkElement.</td>
+	<td>ActualWidth</td><td>Gets the rendered width of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**Application**</td><td>Get the Application object that owns this element.</td>
+	<td>Application</td><td>Get the Application object that owns this element.</td>
 </tr>
 <tr>
-	<td>**AutomationId**</td><td>Gets the AutomationId set on this element if any.</td>
+	<td>AutomationId</td><td>Gets the AutomationId set on this element if any.</td>
 </tr>
 <tr>
-	<td>**Children**</td><td>Gets the visual children of this element.</td>
+	<td>Children</td><td>Gets the visual children of this element.</td>
 </tr>
 <tr>
-	<td>**Clip**</td><td>Gets or sets the <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.geometry(VS.96).aspx" target="_blank">Geometry</a> used to define the outline of the contents of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+	<td>Clip</td><td>Gets or sets the <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.geometry(VS.96).aspx" target="_blank">Geometry</a> used to define the outline of the contents of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
 </tr>
 <tr>
-	<td>**Depth**</td><td>Get the depth of this element in the Visual Tree.</td>
+	<td>Depth</td><td>Get the depth of this element in the Visual Tree.</td>
 </tr>
 <tr>
-	<td>**EnableValidateMouseLocation**</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
+	<td>EnableValidateMouseLocation</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
 </tr>
 <tr>
-	<td>**Find**</td><td>Get the Find object used to search the visual children of this element.</td>
+	<td>Find</td><td>Get the Find object used to search the visual children of this element.</td>
 </tr>
 <tr>
-	<td>**Height**</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
+	<td>Height</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**HorizontalAlignment**</td><td>Gets or sets the horizontal alignment characteristics applied to a FrameworkElement when it is composed within a layout parent, such as a panel or items control.</td>
+	<td>HorizontalAlignment</td><td>Gets or sets the horizontal alignment characteristics applied to a FrameworkElement when it is composed within a layout parent, such as a panel or items control.</td>
 </tr>
 <tr>
-	<td>**Host**</td><td>Returns the SilverlightApp object owning this FrameworkElement.</td>
+	<td>Host</td><td>Returns the SilverlightApp object owning this FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**IsHitTestVisible**</td><td>Gets or sets whether the contained area of this UIElement can return true values for hit testing.</td>
+	<td>IsHitTestVisible</td><td>Gets or sets whether the contained area of this UIElement can return true values for hit testing.</td>
 </tr>
 <tr>
-	<td>**IsTestRegion**</td><td>Returns whether or not this FrameworkElement is contained inside a TestRegion (not supported in WebAii 2.0 Beta 2).</td>
+	<td>IsTestRegion</td><td>Returns whether or not this FrameworkElement is contained inside a TestRegion (not supported in WebAii 2.0 Beta 2).</td>
 </tr>
 <tr>
-	<td>**Language**</td><td>Gets or sets localization/globalization language information that applies to a FrameworkElement.</td>
+	<td>Language</td><td>Gets or sets localization/globalization language information that applies to a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**Margin**</td><td>Gets or sets the outer margin of a FrameworkElement.</td>
+	<td>Margin</td><td>Gets or sets the outer margin of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**MaxHeight**</td><td>Gets or sets the maximum height constraint of a FrameworkElement.</td>
+	<td>MaxHeight</td><td>Gets or sets the maximum height constraint of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**MaxWidth**</td><td>Gets or sets the maximum width constraint of a FrameworkElement.</td>
+	<td>MaxWidth</td><td>Gets or sets the maximum width constraint of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**MinHeight**</td><td>Gets or sets the minimum height constraint of a FrameworkElement.</td>
+	<td>MinHeight</td><td>Gets or sets the minimum height constraint of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**MinWidth**</td><td>Gets or sets the minimum width constraint of a FrameworkElement.</td>
+	<td>MinWidth</td><td>Gets or sets the minimum width constraint of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**Name**</td><td>Gets (or sets, but see Remarks) the identifying name of the object. The name provides a reference that is initially markup-compiled. After a XAML processor creates the object tree from markup, run-time code can refer to a markup element by this name.</td>
+	<td>Name</td><td>Gets (or sets, but see Remarks) the identifying name of the object. The name provides a reference that is initially markup-compiled. After a XAML processor creates the object tree from markup, run-time code can refer to a markup element by this name.</td>
 </tr>
 <tr>
-	<td>**Opacity**</td><td>Gets or sets the degree of the object's opacity.</td>
+	<td>Opacity</td><td>Gets or sets the degree of the object's opacity.</td>
 </tr>
 <tr>
-	<td>**OpacityMask**</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
+	<td>OpacityMask</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
 </tr>
 <tr>
-	<td>**Projection**</td><td>Gets or sets the perspective projection (3-D effect) to apply when rendering this <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+	<td>Projection</td><td>Gets or sets the perspective projection (3-D effect) to apply when rendering this <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
 </tr>
 <tr>
-	<td>**RenderSize**</td><td>Gets the final render size of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+	<td>RenderSize</td><td>Gets the final render size of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
 </tr>
 <tr>
-	<td>**RenderTransform**</td><td>Gets or sets transform information that affects the rendering position of a UIElement.</td>
+	<td>RenderTransform</td><td>Gets or sets transform information that affects the rendering position of a UIElement.</td>
 </tr>
 <tr>
-	<td>**RenderTransformOrigin**</td><td>Gets or sets the origin point of any possible render transform declared by <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement.rendertransform(VS.96).aspx" target="_blank">RenderTransform</a>, relative to the bounds of the <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+	<td>RenderTransformOrigin</td><td>Gets or sets the origin point of any possible render transform declared by <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement.rendertransform(VS.96).aspx" target="_blank">RenderTransform</a>, relative to the bounds of the <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
 </tr>
 <tr>
-	<td>**Resources**</td><td>Gets the locally defined resource dictionary. In XAML, you can establish resource items as child object elements of the <object.Resources> property element, through XAML implicit collection syntax.</td>
+	<td>Resources</td><td>Gets the locally defined resource dictionary. In XAML, you can establish resource items as child object elements of the <code>&lt;object.Resources&gt;</code> property element, through XAML implicit collection syntax.</td>
 </tr>
 <tr>
-	<td>**Style**</td><td>Gets or sets an instance <a href="http://msdn.microsoft.com/en-us/library/system.windows.style(VS.96).aspx" target="_blank">Style</a> that is applied for this object during rendering.</td>
+	<td>Style</td><td>Gets or sets an instance <a href="http://msdn.microsoft.com/en-us/library/system.windows.style(VS.96).aspx" target="_blank">Style</a> that is applied for this object during rendering.</td>
 </tr>
 <tr>
-	<td>**TagNameIndex**</td><td>Gets the tag name index of the xaml tag name in the visual tree.</td>
+	<td>TagNameIndex</td><td>Gets the tag name index of the xaml tag name in the visual tree.</td>
 </tr>
 <tr>
-	<td>**TechnologyType**</td><td>Get the technology type of this element. Always returns TechnologyType.Silverlight for FrameworkElement objects.</td>
+	<td>TechnologyType</td><td>Get the technology type of this element. Always returns TechnologyType.Silverlight for FrameworkElement objects.</td>
 </tr>
 <tr>
-	<td>**TextContent**</td><td>Gets the text content of this framework element if any.</td>
+	<td>TextContent</td><td>Gets the text content of this framework element if any.</td>
 </tr>
 <tr>
-	<td>**UseLayoutRounding**</td><td>Gets or sets a value that determines whether rendering for the object and its subtree should use rounding behavior that aligns rendering to whole pixels.</td>
+	<td>UseLayoutRounding</td><td>Gets or sets a value that determines whether rendering for the object and its subtree should use rounding behavior that aligns rendering to whole pixels.</td>
 </tr>
 <tr>
-	<td>**User**</td><td>Gets the UI interaction object that allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
+	<td>User</td><td>Gets the UI interaction object that allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
 </tr>
 <tr>
-	<td>**VerticalAlignment**</td><td>Gets or sets the vertical alignment characteristics applied to a FrameworkElement when it is composed within a parent object such as a panel or items control.</td>
+	<td>VerticalAlignment</td><td>Gets or sets the vertical alignment characteristics applied to a FrameworkElement when it is composed within a parent object such as a panel or items control.</td>
 </tr>
 <tr>
-	<td>**Visibility**</td><td>Gets or sets the visibility of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>. A <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> that is not visible does not render and does not communicate its desired size to layout.</td>
+	<td>Visibility</td><td>Gets or sets the visibility of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>. A <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> that is not visible does not render and does not communicate its desired size to layout.</td>
 </tr>
 <tr>
-	<td>**Wait**</td><td>Gets a VisualWait object to be used on waiting for Visual elements in the VisualTree.</td>
+	<td>Wait</td><td>Gets a VisualWait object to be used on waiting for Visual elements in the VisualTree.</td>
 </tr>
 <tr>
-	<td>**Width**</td><td>Gets or sets the width of a FrameworkElement.</td>
+	<td>Width</td><td>Gets or sets the width of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**XamlTag**</td><td>Get the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
+	<td>XamlTag</td><td>Get the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
 </tr>
 <table>
 
-##The FrameworkElement Methods##
+## The FrameworkElement Methods
 
 Before describing all of the methods of the FrameworkElement object I'd like to point out the following special features:
 
-1. VisualTree navigation: All FrameworkElements enable you to navigate the visual tree up or down. The object exposes methods and properties like **Parent**, **Children**, **NextSibling**, **PreviousSibling**, **AnySibling<T>**. The navigation also supports control sensitive navigation. For example, if you would like to find the parent 'Grid' that a certain text is contained in you do the following:
+1. VisualTree navigation: All FrameworkElements enable you to navigate the visual tree up or down. The object exposes methods and properties like `Parent`, `Children`, `NextSibling`, `PreviousSibling`, `AnySibling<T>`. The navigation also supports control sensitive navigation. For example, if you would like to find the parent 'Grid' that a certain text is contained in you do the following:
 
 	
 	```C#
@@ -169,7 +169,7 @@ Before describing all of the methods of the FrameworkElement object I'd like to
 3. **Element coordinates:** 
 
 
-	All FrameworkElements offer the ability to get both the relative coordinates of the element within the Silverlight application and the actual coordinates in screen coordinates. The two methods are **GetRectangle()**and **GetScreenRectangle()**.
+	All FrameworkElements offer the ability to get both the relative coordinates of the element within the Silverlight application and the actual coordinates in screen coordinates. The two methods are **GetRectangle()** and **GetScreenRectangle()**.
 
 	**Note:** Given that WPF/Silverlight applications allow for rich transforms for visual elements (i.e. rotate, zoom….etc) and some elements like ellipses don't really conform to a rectangle per-say, our coordinate calculations will always return the largest rectangle that contains the actual element with its center right at the center of the element. For example, a GetRectangle on an ellipse will return this:
 
@@ -189,55 +189,55 @@ These are all of the FrameworkElement methods available for use by your automati
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td>**AnySibling(T)**</td><td>Return any sibling of this control of type T. The framework first searches for a previous sibling having the specified type. If it finds one that sibling is returned. If it doesn't find one then it searches for the next sibling. If it find one that sibling is returned, otherwise null (Nothing in VB.NET) is returned.</td>
+	<td>AnySibling(T)</td><td>Return any sibling of this control of type T. The framework first searches for a previous sibling having the specified type. If it finds one that sibling is returned. If it doesn't find one then it searches for the next sibling. If it find one that sibling is returned, otherwise null (Nothing in VB.NET) is returned.</td>
 </tr>
 <tr>
-	<td>**As(T)**</td><td>Return this framework element as a strongly-typed control of type T.</td>
+	<td>As(T)</td><td>Return this framework element as a strongly-typed control of type T.</td>
 </tr>
 <tr>
-	<td>**CastAs(T)**</td><td>Returns this framework element as a strongly-typed control of type T without enforcing tag name to match the type it is being cast to. This functions gives you free casting abilities between types.</td>
+	<td>CastAs(T)</td><td>Returns this framework element as a strongly-typed control of type T without enforcing tag name to match the type it is being cast to. This functions gives you free casting abilities between types.</td>
 </tr>
 <tr>
-	<td>**Equals**</td><td>Determines whether this FrameworkElement is equal to another, by comparing their AutomationReferences.</td>
+	<td>Equals</td><td>Determines whether this FrameworkElement is equal to another, by comparing their AutomationReferences.</td>
 </tr>
 <tr>
-	<td>**GetChildren**</td><td>Get the children of this framework element.</td>
+	<td>GetChildren</td><td>Get the children of this framework element.</td>
 </tr>
 <tr>
-	<td>**GetNextSibling**</td><td>Get the next sibling of this FrameworkElement.</td>
+	<td>GetNextSibling</td><td>Get the next sibling of this FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**GetParent**</td><td>Get the Parent of this element.</td>
+	<td>GetParent</td><td>Get the Parent of this element.</td>
 </tr>
 <tr>
-	<td>**GetPrevSibling**</td><td>Get the previous sibling.</td>
+	<td>GetPrevSibling</td><td>Get the previous sibling.</td>
 </tr>
 <tr>
-	<td>**GetRectangle**</td><td>Get the bounding rectangle of this FrameworkElement within the owning Silverlight application.</td>
+	<td>GetRectangle</td><td>Get the bounding rectangle of this FrameworkElement within the owning Silverlight application.</td>
 </tr>
 <tr>
-	<td>**GetScreenRectangle**</td><td>Return the actual coordinates of this element in absolute screen coordinates taking into account the location of the overall plug-in on the page.</td>
+	<td>GetScreenRectangle</td><td>Return the actual coordinates of this element in absolute screen coordinates taking into account the location of the overall plug-in on the page.</td>
 </tr>
 <tr>
-	<td>**Highlight**</td><td>Highlight this element in the Silverlight application.</td>
+	<td>Highlight</td><td>Highlight this element in the Silverlight application.</td>
 </tr>
 <tr>
-	<td>**NextSibling**</td><td>Get the next sibling control of a specific type.</td>
+	<td>NextSibling</td><td>Get the next sibling control of a specific type.</td>
 </tr>
 <tr>
-	<td>**Parent**</td><td>Get the parent FrameworkElement of this element.</td>
+	<td>Parent</td><td>Get the parent FrameworkElement of this element.</td>
 </tr>
 <tr>
-	<td>**PreviousSibling**</td><td>Get the previous sibling control of a specific type.</td>
+	<td>PreviousSibling</td><td>Get the previous sibling control of a specific type.</td>
 </tr>
 <tr>
-	<td>**Refresh**</td><td>Refresh this FrameworkElement within the VisualTree.</td>
+	<td>Refresh</td><td>Refresh this FrameworkElement within the VisualTree.</td>
 </tr>
 <tr>
-	<td>**ScrollToVisible**</td><td>Scrolls the web page so that this element is visible in the browser window.</td>
+	<td>ScrollToVisible</td><td>Scrolls the web page so that this element is visible in the browser window.</td>
 </tr>
 <tr>
-	<td>**ToXml**</td><td>Gets an XML formatted string that represents this element and all its children This XML represents the VisualTree.</td>
+	<td>ToXml</td><td>Gets an XML formatted string that represents this element and all its children This XML represents the VisualTree.</td>
 </tr>
 <table>
 
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/framework-element-object/fig1.png b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/framework-element-object/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/silverlight-ui-automation/fig1.png b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/silverlight-ui-automation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/wpf-ui-automation/fig1.png b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/images/wpf-ui-automation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/invoking-actions.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/invoking-actions.md
index 51da741c..d80b5814 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/invoking-actions.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/invoking-actions.md
@@ -4,7 +4,7 @@ page_title: Invoking Actions
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Invoking Actions on Elements#
+# Invoking Actions on Elements
 
 Once you have found an element you can then interact with it. Many different types of interactions are supported like clicking, mouse hover over, mouse wheel-related actions, keyboard clicks etc.
 
@@ -21,11 +21,11 @@ Once you have found an element you can then interact with it. Many different typ
 	* [Getting and Setting Properties on Elements](#Getting-and-Setting-Properties-on-Elements) - working with non-built in Properties.
 5. [Invoking Element Methods](#Invoking-Element-Methods) - invoke any method attached to an element.
 
-##Clicking On an Element##
+## Clicking On an Element
 
 To invoke a UI action, use the User object that is attached to every UI element. For example, to click on an element such as a button, enter code like this:
 
-```C#
+````C#
 //In this example app can be a Silverlight application or the MainWindow element of a WPF application 
 // Click the ShowGuide button.
 app.Find.ByName("guideButton").User.Click();
@@ -33,10 +33,8 @@ app.Find.ByName("guideButton").User.Click();
 // Right click the ShowGuide button 5 pixels away from the center of the control
 app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick,
      new System.Drawing.Point(5, 5), OffsetReference.AbsoluteCenter);
-```
- 
-
-```VB
+````
+````VB
 'In this example app can be a Silverlight application or the MainWindow of a WPF application 
 ' Click the ShowGuide button.
 app.Find.ByName("guideButton").User.Click()
@@ -45,53 +43,49 @@ app.Find.ByName("guideButton").User.Click()
 app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick, _
                                        New System.Drawing.Point(5, 5), _
                                         OffsetReference.AbsoluteCenter)
-```
+````
 
-##Sending Text to a Control##
+## Sending Text to a Control
 
 To send text to the control use one of the following lines of code:
 
-```C#
+````C#
 searchText.User.TypeText("Abe Lincoln", 100);
  
 searchText.User.KeyPress(System.Windows.Forms.Keys.L, 100);
  
 searchText.User.KeyDown(System.Windows.Forms.Keys.L);
 searchText.User.KeyUp(System.Windows.Forms.Keys.L);
-```
- 
-
-```VB
+````
+````VB
 searchText.User.TypeText("Abe Lincoln", 100)
  
 searchText.User.KeyPress(Windows.Forms.Keys.L, 100)
  
 searchText.User.KeyDown(Windows.Forms.Keys.L)
 searchText.User.KeyUp(Windows.Forms.Keys.L)
-```
+````
 
-##Mouse Actions##
+## Mouse Actions
 
 To perform one of the various possible mouse actions use one of the following lines of code:
 
-```C#
+````C#
 admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"));
 admin1.User.HoverOver();
 admin1.User.MouseEnter(OffsetReference.LeftCenter);
 admin1.User.MouseLeave(OffsetReference.RightCenter);
 admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, false);
-```
- 
-
-```VB
+````
+````VB
 admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"))
 admin1.User.HoverOver()
 admin1.User.MouseEnter(OffsetReference.LeftCenter)
 admin1.User.MouseLeave(OffsetReference.RightCenter)
 admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, False)
-```
+````
 
-##Framework Element Properties and Actions##
+## Framework Element Properties and Actions
 
 All of the Telerik Testing Framework UI controls derive from the FrameworkElement object. Our FrameworkElement object mirrors as closely as possible XAML's FrameworkElement as defined in MSDN <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement%28VS.96%29.aspx" target="_blank">here</a>. For customers interested in our extensibility model, the Silverlight Extension does not expose a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> and therefore, our FrameworkElement can be viewed as the combination of Silverlight/WPF's UIElement + FrameworkElement. These are just few examples of the many available properties of our FrameworkElement object:
 
@@ -100,33 +94,33 @@ All of the Telerik Testing Framework UI controls derive from the FrameworkElemen
 	<th>Property</th><th>Description</th>
 </tr>
 <tr>
-	<td>**AutomationId**</td><td>Retrieves the Automation ID assigned to this element.</td>
+	<td>AutomationId</td><td>Retrieves the Automation ID assigned to this element.</td>
 </tr>
 <tr>
-	<td>**Children**</td>Retrieves a list of elements that are children of this element in the visual tree.</td>
+	<td>Children</td>Retrieves a list of elements that are children of this element in the visual tree.</td>
 </tr>
 <tr>
-	<td>**Clip**</td><td>Gets or sets the Geometry used to define the outline of the contents of a UI Element.</td>
+	<td>Clip</td><td>Gets or sets the Geometry used to define the outline of the contents of a UI Element.</td>
 </tr>
 <tr>
-	<td>**Height**</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
+	<td>Height</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
 </tr>
 <tr>
-	<td>**Opacity**</td><td>Gets or sets the degree of the object's opacity.</td>
+	<td>Opacity</td><td>Gets or sets the degree of the object's opacity.</td>
 </tr>
 <tr>
-	<td>**OpacityMask**</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
+	<td>OpacityMask</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
 </tr>
 <tr>
-	<td>**Width**</td><td>Gets or sets the suggested width of a FrameworkElement.</td>
+	<td>Width</td><td>Gets or sets the suggested width of a FrameworkElement.</td>
 </tr>
 <table>
 
-##UI Element Actions##
+## UI Element Actions
 
 Each UI element wrapper class contained in Telerik Testing Framework has a set of properties used to access the properties appropriate for that UI element. For example: The Calendar control has a SelectedDate property that you can use to read and/or set the currently selected date of the control. It also has a SelectionMode property you can use to read and/or change the selection mode from a single date to a multi-range date selection. The CheckBox control has an IsChecked property you can use to read/set the checked state of the control and so on.
 
-##Telerik Testing Framework Specific Properties##
+## Telerik Testing Framework Specific Properties
 
 We have implemented a few special properties in our FrameworkElement object to aid in automation. These include:
 
@@ -135,35 +129,35 @@ We have implemented a few special properties in our FrameworkElement object to a
 	<th>Property</th><th>Description</th>
 </tr>
 <tr>
-	<td>**AbsoluteSiblingTagIndex**</td><td>Returns the sibling tag index of this FrameworkElement relative to its other siblings within the Visual Tree.</td>
+	<td>AbsoluteSiblingTagIndex</td><td>Returns the sibling tag index of this FrameworkElement relative to its other siblings within the Visual Tree.</td>
 </tr>
 <tr>
-	<td>**AbsoluteTagIndex**</td><td>Returns the absolute index of this XAML tag within the entire Visual Tree.</td>
+	<td>AbsoluteTagIndex</td><td>Returns the absolute index of this XAML tag within the entire Visual Tree.</td>
 </tr>
 <tr>
-	<td>**Application**</td><td>Gets the Application object that owns this element.</td>
+	<td>Application</td><td>Gets the Application object that owns this element.</td>
 </tr>
 <tr>
-	<td>**EnableValidateMouseLocation**</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
+	<td>EnableValidateMouseLocation</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
 </tr>
 <tr>
-	<td>**Find**</td><td>Gets the Find object that can be used to search the visual children of this element.</td>
+	<td>Find</td><td>Gets the Find object that can be used to search the visual children of this element.</td>
 </tr>
 <tr>
-	<td>**TagNameIndex**</td><td>Gets the tag name index of the XAML tag name in the visual tree.</td>
+	<td>TagNameIndex</td><td>Gets the tag name index of the XAML tag name in the visual tree.</td>
 </tr>
 <tr>
-	<td>**User**</td><td>Gets the UI interaction object which allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
+	<td>User</td><td>Gets the UI interaction object which allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
 </tr>
 <tr>
-	<td>**Wait**</td><td>Gets a VisualWait object you can use to wait for Visual elements in the Visual Tree.</td>
+	<td>Wait</td><td>Gets a VisualWait object you can use to wait for Visual elements in the Visual Tree.</td>
 </tr>
 <tr>
-	<td>**XamlTag**</td><td>Gets the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
+	<td>XamlTag</td><td>Gets the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
 </tr>
 <table>
 
-##Telerik Testing Framework Specific Methods##
+## Telerik Testing Framework Specific Methods
 
 The FrameworkElement class implements a number of methods just for purpose of test automation. Some of the most commonly used include:
 
@@ -172,27 +166,27 @@ The FrameworkElement class implements a number of methods just for purpose of te
 	<th>Property</th><th>Description</th>
 </tr>
 <tr>
-	<td>**CastAs\<T>()**</td><td>Returns a FrameworkElement as a strongly-typed control. Does not enforce a tagname to match the type.</td>
+	<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>**GetChildren()**</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>**GetNextSibling()**</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>**Parent()**</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>**ScrollToVisible()**</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>
 
-##Getting and Setting Properties on Elements##
+## Getting and Setting Properties on Elements
 
 If the property of an element you want to get or set isn't available as a property in the UI element wrapper object, you can use the GetProperty and SetProperty from the FrameworkElement object to get/set it. This is especially useful if you start designing your own custom Silverlight UI controls or use a third party custom control. Let's suppose I have a UI element that represents an airline ticket. One of the many obvious properties such a control would need to have is flight number. To fetch this property from the control I can use code like this:
 
-```C#
+````C#
 // Fetch the flight number from the ticket
 FrameworkElement ticket = app.FindName("airlineTicket");
 AutomationProperty flightNoProperty = new AutomationProperty("flightNo", typeof(string));
@@ -200,10 +194,8 @@ string flightNo = (string)ticket.GetProperty(flightNoProperty);
  
 // Update the flight number on the ticket
 ticket.SetProperty(flightNoProperty, "HX-1572");
-```
- 
-
-```VB
+````
+````VB
 ' Fetch the flight number from the ticket
 Dim ticket As FrameworkElement = app.FindName("airlineTicket")
 Dim flightNoProperty As New AutomationProperty("flightNo", GetType(String))
@@ -211,24 +203,22 @@ Dim flightNo As String = DirectCast(ticket.GetProperty(flightNoProperty), String
  
 ' Update the flight number on the ticket
 ticket.SetProperty(flightNoProperty, "HX-1572")
-```
+````
 
-##Invoking Element Methods##
+## Invoking Element Methods
 
 Another advanced feature of the framework is the ability to invoke any method attached to an element. Here's how to invoke the ScrollToVerticalOffset method of a ScrollViewer element.
 
-```C#
+````C#
 ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
 searchScroll = app.FindName().Find.ByType<>();
  
 AutomationMethod scrollVert = new AutomationMethod("ScrollToVerticalOffset", null);
 searchScroll.InvokeMethod(scrollVert, 2000);
-```
- 
-
-```VB
+````
+````VB
 Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
  
 Dim scrollVert As New AutomationMethod("ScrollToVerticalOffset", Nothing)
 searchScroll.InvokeMethod(scrollVert, 2000)
-```
\ No newline at end of file
+````
\ No newline at end of file
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
index a0681483..314c805a 100644
--- 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
@@ -5,9 +5,9 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/locating-elements.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/locating-elements
 position: 3
 ---
-#Locating Elements in Silverlight and WPF applications 
+# Locating Elements in Silverlight and WPF applications 
 
-Before you can automate interaction with elements contained in a Silverlight/WPF application, you need to first locate the elements contained within the application. For complex applications, locating elements is probably going to be one of the more time consuming tasks. Testers will need to spend time understanding how to reliably find an element. Silverlight/WPF applications that we studied that rely heavily on control templates and data binding produce quite complex visual trees. Their elements are not easily searchable by **Find.ByName()** given the different <a href=http://msdn.microsoft.com/en-us/library/cc189026%28VS.95%29.aspx" target="_blank">Silverlight</a> and <a href="http://msdn.microsoft.com/en-us/library/ms746659.aspx" target="_blank">WPF</a> name scopes created, and the duplication of names within those templates.
+Before you can automate interaction with elements contained in a Silverlight/WPF application, you need to first locate the elements contained within the application. For complex applications, locating elements is probably going to be one of the more time consuming tasks. Testers will need to spend time understanding how to reliably find an element. Silverlight/WPF applications that we studied that rely heavily on control templates and data binding produce quite complex visual trees. Their elements are not easily searchable by `Find.ByName()` given the different <a href=http://msdn.microsoft.com/en-us/library/cc189026%28VS.95%29.aspx" target="_blank">Silverlight</a> and <a href="http://msdn.microsoft.com/en-us/library/ms746659.aspx" target="_blank">WPF</a> name scopes created, and the duplication of names within those templates.
 
 1. <a href="#the-find-strategy">The Find Strategy</a> - change the 'Strategy' property that controls how the method behaves when searching for an element.
 
@@ -17,18 +17,16 @@ Before you can automate interaction with elements contained in a Silverlight/WPF
 
 4. <a href="#finding-elements-by-xamlfindexpression">Finding Elements by XamlFindExpression</a> - search for an element using a FindExpression.
 
-The simplest method of searching is to use the **Find.ByName(String name)** method or the **Find.ByName\<TControl>(String name)** method. Both methods take a string parameter that specifies the name of the element to locate in the application. The first method returns a FrameworkElement object while the second method returns an object of type T having the specified name. If an element having the specified name does not exist or is not currently visible, or if the found element cannot be cast into type T, the functions will return null ('Nothing' in VB.NET). For example:
+The simplest method of searching is to use the `Find.ByName(String name)` method or the `Find.ByName<TControl>(String name)` method. Both methods take a string parameter that specifies the name of the element to locate in the application. The first method returns a FrameworkElement object while the second method returns an object of type T having the specified name. If an element having the specified name does not exist or is not currently visible, or if the found element cannot be cast into type T, the functions will return null ('Nothing' in VB.NET). For example:
 
-```C#
+````C#
 FrameworkElement zoomBox = app.FindName("zoomBox");
 TextBox searchText = app.FindName<TextBox>("searchText");
-```
- 
-
-```VB
+````
+````VB
 Dim zoomBox As FrameworkElement = app.FindName("zoomBox")
 Dim searchText As TextBox = app.FindName(Of TextBox)("searchText")
-```
+````
 
 You might be asking "How do I know what name to use to find the element I want?" There really are only a few ways to find out:
 
@@ -49,20 +47,20 @@ All of the common methods for finding an element to operate on are:
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td>**Find.ByName()/Find.ByName\<T>**</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>**Find.ByText**</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>**Find.ByAutomationId**</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>**Find.ByType**</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>
+</table>
 
-##The Find Strategy##
+## The Find Strategy
 
 The Find object has a 'Strategy' property that controls how the method behaves when searching for an element. To change the strategy simply change the Strategy property on the Find object. The following strategies can be set:
 
@@ -71,82 +69,76 @@ The Find object has a 'Strategy' property that controls how the method behaves w
 	<th>Strategy</th><th>Description</th>
 </tr>
 <tr>
-	<td>**AlwaysWaitForElementsVisible**</td><td>In this mode the Find object always waits for the element to exist and for its Visibility property to equal "Visible". The default amount of time it will wait is 5 seconds. This timeout can be changed by modifying the Find.Timeout property before using the Find object. This strategy is the default setting.</td>
+	<td>AlwaysWaitForElementsVisible</td><td>In this mode the Find object always waits for the element to exist and for its Visibility property to equal "Visible". The default amount of time it will wait is 5 seconds. This timeout can be changed by modifying the Find.Timeout property before using the Find object. This strategy is the default setting.</td>
 </tr>
 <tr>
-	<td>**WhenNotVisibleReturnElementProxy**</td><td>In this mode an 'Element Proxy' is returned if the element cannot be found right away. An 'Element Proxy' is a lightweight FrameworkElement object that only contains information on how to locate the desired element in the Visual Tree. This is useful when you want to use the SilverlightApp.Wait.ForExists method.</td>
+	<td>WhenNotVisibleReturnElementProxy</td><td>In this mode an 'Element Proxy' is returned if the element cannot be found right away. An 'Element Proxy' is a lightweight FrameworkElement object that only contains information on how to locate the desired element in the Visual Tree. This is useful when you want to use the SilverlightApp.Wait.ForExists method.</td>
 </tr>
 <tr>
-	<td>**WhenNotVisibleReturnNull**</td><td>In this mode null (Nothing in VB.NET) is returned if the element cannot be found right away.</td>
+	<td>WhenNotVisibleReturnNull</td><td>In this mode null (Nothing in VB.NET) is returned if the element cannot be found right away.</td>
 </tr>
 <tr>
-	<td>**WhenNotVisibleThrowException**</td><td>In this mode a generic exception is thrown if the element cannot be found right away.</td>
+	<td>WhenNotVisibleThrowException</td><td>In this mode a generic exception is thrown if the element cannot be found right away.</td>
 </tr>
 <table>
 
-##Finding All Elements##
+## Finding All Elements
 
 Sometimes you may need to fetch a list of the elements contained in the application. Suppose we want a list of all the DataGrids contained in the application. Either of the following lines of code will return this list:
 
 
-```C#
+````C#
 IList<FrameworkElement> dataGrids1 = app.Find.AllByType("DataGrid");
 IList<DataGrid> dataGrids2 = app.Find.AllByType<DataGrid>();
-```
- 
-
-```VB
+````
+````VB
 Dim dataGrids1 As IList(Of FrameworkElement) = app.Find.AllByType("DataGrid")
 Dim dataGrids2 As IList(Of DataGrid) = app.Find.AllByType(Of DataGrid)()
-```
+````
 
-All of the Find.AllByxxx functions are:
+All of the `Find.AllByxxx` functions are:
 
 <table class="docs">
 <tr>
 	<th>Method</th><th>Description</th>
 </tr>
 <tr>
-	<td>**Find.AllByName()/Find.AllByName\<T>**</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>**Find.AllByText()**</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>**Find.AllByType()/Find.AllByType\<T>**</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>**Find.AllByAutomationID()/Find.AllByAutomationID\<T>**</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>
+</table>
 
-##Scoped Searches##
+## Scoped Searches
 
 A more advanced feature is scoped searches. Suppose you need to find the ScrollBar attached to some other element. You would use code like this:
 
 
-```C#
+````C#
 ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
 searchScroll = app.FindName().Find.ByType<>();
-```
- 
-
-```VB
+````
+````VB
 Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
 searchScroll ScrollViewer = app.FindName().Find.ByType( ScrollViewer)()
-```
+````
 
 The above code first locates the element named "patientSearchScroller" and then within that control finds the element of type "ScrollViewer". The search for "ScrollViewer" is considered a scoped search (aka chained search) because the search is limited to only those elements found underneath the "patientSearchScroller" element of the Visual Tree. The FrameworkElement base class has a Find property which allows scoped searches for all elements of an application.
 
-##Finding Elements by XamlFindExpression##
+## Finding Elements by XamlFindExpression
 
-Another advanced feature is to find the element using a XamlFindExpression. FindExpressions are the replacement/evolution of FindParams. Telerik Testing Framework uses FindExpressions as the basis for all element searches in the DOM, HWnd, or control trees (including Translator Locators). For example, the above scoped search to retrieve a ScrollViewer can be written using Find.ByExpression as follows:
+Another advanced feature is to find the element using a XamlFindExpression. FindExpressions are the replacement/evolution of FindParams. Telerik Testing Framework uses FindExpressions as the basis for all element searches in the DOM, HWnd, or control trees (including Translator Locators). For example, the above scoped search to retrieve a ScrollViewer can be written using `Find.ByExpression` as follows:
 
-```C#
+````C#
 ScrollViewer searchScroll = app.Find.ByExpression(new XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).As<ScrollViewer>();
-```
- 
-
-```VB
+````
+````VB
 Dim searchScroll2 As ScrollViewer = app.Find.ByExpression(New XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).[As](Of ScrollViewer)()
-```
+````
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-automation.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-automation.md
index 90f28c33..f2fdab1f 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-automation.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-automation.md
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/introduction.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/introduction
 position: 1
 ---
-#Getting Started with Silverlight UI Automation#
+# Getting Started with Silverlight UI Automation
 
 When thinking about Silverlight applications and automated testing, there are a couple of different approaches that come to mind:
  
@@ -15,7 +15,7 @@ To get started, let's use a simple application and demo some basic automation sc
 
 To automate the application above to set the text, click the button and then verify the hello text in Telerik Testing Framework, we can simply write the following code using the Silverlight Extension (which resides under ArtOfTest.WebAii.Silverlight).
 
-```C#
+````C#
 [TestMethod]
 public void SLDemo()
 {  
@@ -40,10 +40,8 @@ public void SLDemo()
 	// Verify the text
 	Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"));
 }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod> _
 Public Sub SampleWebAiiTest()
     'Enable Silverlight
@@ -67,35 +65,35 @@ Public Sub SampleWebAiiTest()
     ' Verify the text
     Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"))
 End Sub
-```
+````
 Let's take a closer look at the code above line by line:
 
 * Line 8-12
 
 	This is basic code that launches the browser and navigates to a specific page.
 
-* Line 14 (*SilverlightApp app = ActiveBrowser.SilverlightApps()[0];*)
+* Line 14 (`SilverlightApp app = ActiveBrowser.SilverlightApps()[0];`)
 
-	As soon as you include the Silverlight extension namespace in your test, (**ArtOfTest.WebAii.Silverlight**), the '**SilverlightApps()**' extension method is added to the ActiveBrowser. The extension method offers you a list of all Silverlight applications found on that page. The extension method returns a list that has two accessors. An **index** accessor that takes an int (as shown above) and a string accessor that takes a hostid [The ID of the HTML element that contains the <object> tag for the plug-in]. You can pick and choose what works for you. In this sample, given that we only have one Silverlight plug-in on the page, we simply accessed the first and only one.
+	As soon as you include the Silverlight extension namespace in your test, (**ArtOfTest.WebAii.Silverlight**), the `SilverlightApps()` extension method is added to the ActiveBrowser. The extension method offers you a list of all Silverlight applications found on that page. The extension method returns a list that has two accessors. An **index** accessor that takes an int (as shown above) and a string accessor that takes a hostid [The ID of the HTML element that contains the `<object>` tag for the plug-in]. You can pick and choose what works for you. In this sample, given that we only have one Silverlight plug-in on the page, we simply accessed the first and only one.
 
-* Line 17 (*app.FindName<TextBox>("myName").Text = "Telerik";*)
+* Line 17 (`app.FindName<TextBox>("myName").Text = "Telerik";`)
 
 	As soon as you have an instance of a **SilverlightApp**, you now have full access to the application including the entire **VisualTree**. The app offers a short-cut method '**FindName**', that can be used to search the application using an element name. In the above sample, given that the **TextBox** has a name associated with it, we can use FindName to locate it. The SilverlightApp object offers two versions of 'FindName': The first is a generic method that can return a strongly-typed object of the element (As shown above , i.e. a Button, a TextBox, a Grid, etc). The second is simpler and returns the base **FrameworkElement** object. We will discuss the strongly-typed object model offered in Silverlight Extension later.
  
 	To go back to the line above, we are simply accessing the **TextBox** that has a name '**myName**' and then setting its Text property to "Telerik". Note that given we are accessing a property on the element, this is analogous to **SetText** on a DOM element in Telerik Testing Framework automation. You are not really typing the text in the textbox but rather setting the Text property inside the application to that text. Our extension enables you to access and set properties directly against any **FrameworkElement**. If we wanted to simulate real typing of the text we would have written code like this:
  
  
-	*app.FindName<TextBox>("myName").User.TypeText("Telerik", 50);*
+	`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.
+	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.
 
-* Line 23 (*Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"));*) 
+* Line 23 (`Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"));`) 
 
-	Now that the button is clicked, we need to verify that the message is correct. The difference here is that we can't really use **FindName** to locate the **TextBlock** because the TextBlock doesn't really have a name. The **SilverlightApp** object offers extensive search support within the **VisualTree** beyond FindName() by utilizing similar approach to the Find object off the ActiveBrowser (that is used for HTML DOM searches) but adapted to specific **XAML** search scenarios.
+	Now that the button is clicked, we need to verify that the message is correct. The difference here is that we can't really use **FindName** to locate the **TextBlock** because the TextBlock doesn't really have a name. The **SilverlightApp** object offers extensive search support within the **VisualTree** beyond `FindName()` by utilizing similar approach to the Find object off the ActiveBrowser (that is used for HTML DOM searches) but adapted to specific **XAML** search scenarios.
  
-	In our code above, we are searching for a TextBlock (All Find.xxText() routines return TextBlocks) that partially contains '**Hello**', hence '**p:Hello**' (Similar to Find.ByContent in HTML search). Once we find the TextBlock, we then verify that the Text of that label is actually 'Hello Telerik' using the **Assert.IsTrue**.
+	In our code above, we are searching for a TextBlock (All `Find.xxText()` routines return TextBlocks) that partially contains '**Hello**', hence '**p:Hello**' (Similar to Find.ByContent in HTML search). Once we find the TextBlock, we then verify that the Text of that label is actually 'Hello Telerik' using the **Assert.IsTrue**.
 
 Now that we understand this sample, let's dig into some of the key objects available in the Silverlight Extension.
 
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md
index 3017b17b..08eb817e 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md
@@ -4,7 +4,7 @@ page_title: Silverlight UI Namespace
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#The ArtOfTest.WebAii.Silverlight.UI Namespace#
+# The ArtOfTest.WebAii.Silverlight.UI Namespace
 
 The UI namespace includes all the strongly-typed controls like **Button**, **DataGrid**, **TextBox**, etc. and their properties/methods and enum's, mirroring as much as possible the set of controls available in Silverlight as documented <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement(VS.96).aspx" target="_blank">here</a>. The namespace also includes the types used by these properties like **Brush**, **SolidBrush**, etc.
  
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/synchronization.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/synchronization.md
index 402b1ae9..57d4119e 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/synchronization.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/synchronization.md
@@ -4,7 +4,7 @@ page_title: Synchronization
 description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Synchronization#
+# Synchronization
 
 In the world of testing mostly static HTML pages synchronization was easy. Telerik Testing Framework was even able to automatically take care of synchronization for you (most of the time). All you had to do was click on a button and wait for the browser to be ready, which the framework does behind the scenes for most HTML UI actions.
  
@@ -17,81 +17,87 @@ The framework has many features implemented to aid you in synchronizing with you
 	<th>Wait Type</th><th>Description</th>
 </tr>
 <tr>
-	<td>**ForExists**</td><td>This method waits for the element to exist in the Visual Tree. It accepts an optional timeout parameter.</td>
+<td>
+	
+**ForExists**</td><td>This method waits for the element to exist in the Visual Tree. It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForExistsNot**</td><td>This method waits for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter</td>
+<td>
+	
+**ForExistsNot**</td><td>This method waits for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter</td>
 </tr>
 <tr>
-	<td>**ForVisible**</td><td>This method waits for the element to both exist in the Visual Tree and its Visibility attribute to equal "Visible". It accepts an optional timeout parameter.</td>
+<td>
+	
+**ForVisible**</td><td>This method waits for the element to both exist in the Visual Tree and its Visibility attribute to equal "Visible". It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForVisibleNot**</td><td>This method waits for the Visibility property of the element to not equal 'Visible' or for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter.</td>
+<td>
+	
+**ForVisibleNot**</td><td>This method waits for the Visibility property of the element to not equal 'Visible' or for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForNoMotion**</td><td>This method waits for the element to stop moving on the drawing surface. It takes a check interval and an optional timeout parameter.</td>
+<td>
+	
+**ForNoMotion**</td><td>This method waits for the element to stop moving on the drawing surface. It takes a check interval and an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**For(Predicate)**</td><td>This method takes a custom predicate and waits for that predicate to return true. It accepts an optional error message and an optional timeout parameter.</td>
+<td>
+	
+**For(Predicate)**</td><td>This method takes a custom predicate and waits for that predicate to return true. It accepts an optional error message and an optional timeout parameter.</td>
 </tr>
 <table>
 
-##Waiting for an Element to Exist##
+## Waiting for an Element to Exist
 
 Before you can use the VisualWait.ForExists method to wait for an element to exist you need to create what is called an "Element Proxy". An element proxy is a lightweight FrameworkElement that doesn't actually represent a real element but contains information on how to find the desired element in the Visual Tree. To create an element proxy implement code like this:
 
-```C#
+````C#
 app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy;
 FrameworkElement myElementProxy = app.Find.ByName("MyElement");
-```
- 
-
-```VB
+````
+````VB
 app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy
 Dim myElementProxy As FrameworkElement = app.Find.ByName("MyElement")
-```
+````
 
 Now that you have an element proxy you use it to wait for the element to exist using this line of code:
 
-```C#
+````C#
 // Wait 15 seconds for the element to exist
 proxy.Wait.ForExists(15000);
-```
- 
-
-```VB
+````
+````VB
 ' Wait 15 seconds for the element to exist
 proxy.Wait.ForExists(15000)
-```
+````
 
-##Using ForExistsNot, ForVisible, ForVisibleNot,  ForNoMotion##
+## Using ForExistsNot, ForVisible, ForVisibleNot,  ForNoMotion
 
 Using any of these functions is pretty straightforward. Just call the method with appropriate parameters, for example:
 
-```C#
+````C#
 FrameworkElement ticket = app.FindName("airlineTicket");
 ticket.Wait.ForExistsNot();         // Wait for the element to no longer exist
 ticket.Wait.ForVisible(3000);       // Wait up to 3 seconds for the element to become visible
 ticket.Wait.ForVisibleNot(2500);    // Wait up to 2.5 seconds for the element to no longer be visible
 ticket.Wait.ForNoMotion(250, 4500); // Wait up to 4.5 seconds for the element to stop moving. Check every 1/4 second.
-```
- 
-
-```VB
+````
+````VB
 Dim ticket As FrameworkElement = app.FindName("airlineTicket")
 ticket.Wait.ForExistsNot()          ' Wait for the element to no longer exist
 ticket.Wait.ForVisible(3000)        ' Wait up to 3 seconds for the element to become visible
 ticket.Wait.ForVisibleNot(2500)     ' Wait up to 2.5 seconds for the element to no longer be visible
 ticket.Wait.ForNoMotion(250, 4500)  ' Wait up to 4.5 seconds for the element to stop moving. Check every 1/4 second.
-```
+````
 
-##Creating Your Own Wait Condition##
+## Creating Your Own Wait Condition
 
 If none of the built-in framework wait for methods meet your needs, the framework has the ability to use your own coded conditional predicate instead. This feature relieves you of the burden of having to fully implement your own custom wait loop.
  
 You can implement your conditional predicate in a function or a lambda expression. Here is a sample of how to implement and use your own conditional predicate in a function:
 
-```C#
+````C#
 FrameworkElement guideButton = app.FindName("guideButton");
 guideButton.Wait.For(myComparator);
  
@@ -99,27 +105,23 @@ public bool myComparator(FrameworkElement elem)
 {
     return elem.Visibility == ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible;
 }
-```
- 
-
-```VB
+````
+````VB
 Dim guideButton As FrameworkElement = app.FindName("guideButton")
     guideButton.Wait.[For](AddressOf myComparator)
  
 Public Function myComparator(ByVal elem As FrameworkElement) As Boolean
     Return elem.Visibility = ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible
 End Function
-```
+````
 To do the same thing in a lambda expression would look like this:
 
 
-```C#
+````C#
 FrameworkElement guideButton = app.FindName("guideButton");
 guideButton.Wait.For(new System.Predicate<FrameworkElement>((fe) => fe.Visibility == ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible));
-```
- 
-
-```VB
+````
+````VB
 Dim guideButton As FrameworkElement = app.FindName("guideButton")
 guideButton.Wait.[For](New System.Predicate(Of FrameworkElement)(Function(fe) fe.Visibility = ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible))
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/wpf-ui-automation.md b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/wpf-ui-automation.md
index b2364c16..dc2bb481 100644
--- a/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/wpf-ui-automation.md
+++ b/docs-teststudiodev/code-in-test/silverlight-wpf-automation-wtc/wpf-ui-automation.md
@@ -5,7 +5,7 @@ description: "Test Studio is an innovative and easy-to-use automated web, WPF an
 previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation
 position: 2
 ---
-#Getting started with WPF UI Automation#
+# Getting started with WPF UI Automation
 
 To get started, let's use a simple application and demo some basic automation scenarios like button click and set text. Then we will expand into more advanced topics and scenarios. Let's take the following simple application that contains a button and a text box. When you click the button, it simply changes "Push the button" to "Hello world!" in the text box. The application looks like this:
 
@@ -13,7 +13,7 @@ To get started, let's use a simple application and demo some basic automation sc
 
 To automate the application above to set the text, click the button and then verify the hello text in **Telerik Testing Framework**, we can simply write the following code using the **WPF Extension** (which resides under **ArtOfTest.WebAii.Wpf**). The template for this method is based on a VsUnit test. However, the code itself can be reused in other type of Unit tests - it's just the template that will be different.
 
-```C#
+````C#
 [TestMethod]
 public void wpfDemo()
    {
@@ -36,10 +36,8 @@ public void wpfDemo()
     Assert.IsTrue(tb.Text.Equals("Hello World!"));
    
     }
-```
- 
-
-```VB
+````
+````VB
 <TestMethod> _
   Public Sub wpfDemo()
    ' Launch the application instance from its location in file system
@@ -61,18 +59,18 @@ public void wpfDemo()
       Assert.IsTrue(tb.Text.Equals("Hello World!"))
    
   End Sub
-```
+````
 Let's take a closer look at the code above line by line:
 
-* Line 5 (*WpfApplication wpfApp = Manager.LaunchNewApplication(@"C:\Projects\WpfApplication2\bin\Debug\WpfApplication2.exe");*)
+* Line 5 (`WpfApplication wpfApp = Manager.LaunchNewApplication(@"C:\Projects\WpfApplication2\bin\Debug\WpfApplication2.exe");`)
 
 	This is basic code that launches the application from a location on the local machine and initializes it into a variable for us. As soon as you have an instance of a Wpf App,you now have full access to the application including the entire Logical Tree. 
 
-* Line 8 ( *Assert.IsTrue(wpfApp.MainWindow.Window.Caption.Equals("MainWindow"));*)
+* Line 8 ( `Assert.IsTrue(wpfApp.MainWindow.Window.Caption.Equals("MainWindow"));`)
 
 	We use the standard Assert class to check the name of the **MainWindow**. The MainWindow is a member of the generic WpfApplication class since every application has one and it holds its entire content.
 
-* Line 11 (*Button b = wpfApp.MainWindow.Find.ByName\<Button>("button1");*)
+* Line 11 (`Button b = wpfApp.MainWindow.Find.ByName<Button>("button1");`)
 
 	The **MainWindow** offers a short-cut member '**Find**' which contains search-related methods. In the above sample, given that the **Button** has a name associated with it, we can use **Find.ByName** to locate it. The MainWindow class offers two versions of **Find.ByName**:
 
@@ -82,15 +80,15 @@ Let's take a closer look at the code above line by line:
  
 	We'll be using the specific version.
 
-* Line 14 (*b.User.Click();*)
+* Line 14 (`b.User.Click();`)
 
 	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 WPF 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.
 
-* Line 17 (*TextBox tb = wpfApp.MainWindow.Find.ByName\<TextBox>("textBlock1");*)
+* Line 17 (`TextBox tb = wpfApp.MainWindow.Find.ByName<TextBox>("textBlock1");`)
 
 	Similarly to line 11 we initialize the Texbox from the app into a variable after locating it by name.
 
-* Line 20 (*Assert.IsTrue(tb.Text.Equals("Hello World!"));*)
+* Line 20 (`Assert.IsTrue(tb.Text.Equals("Hello World!"));`)
 
 	Now that the button is clicked, we need to verify that the message is correct.
  
diff --git a/docs-teststudiodev/docs-builder.yml b/docs-teststudiodev/docs-builder.yml
new file mode 100644
index 00000000..7b38f8b7
--- /dev/null
+++ b/docs-teststudiodev/docs-builder.yml
@@ -0,0 +1,175 @@
+#top nagivation might be wrong
+top-navigation-product: test-studio-dev-edition
+path-prefix: /teststudio-dev/documentation
+product-id: 1846
+product-name: Telerik Test Studio Dev Edition
+product-url: https://www.telerik.com/teststudio-dev
+search-engine-id: 001595215763381649090:8yrsvynfbrc
+cta-overview: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+cta-intro: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+default-title-prefix: Telerik Test Studio Dev Edition
+avatar-path: ./images/avatar-ninja.svg
+no-results-image-path: ./images/ninja-no-results.svg
+pdf-cover-png-path: ./images/pdf-cover.png
+primary-color:
+    light: "#1D8800"
+    dark: "#68BF51"
+
+product-code: TSDEVED
+product-trial-url: https://www.telerik.com/try/test-studio-ultimate
+contribute-url: https://github.com/telerik/teststudio-docs/edit/master/docs-teststudiodev
+enable-tabbed-code-blocks: true
+img-max-width: 100%
+table-layout: fixed
+disable-html-redirect: true
+center-images: false
+
+
+meta:
+## Test Studio Dev Edition Documentation Main Nodes:
+    prerequisites:
+        title: Prerequisites
+        position: 1
+    code-in-test:
+        title: Implement Code in Test
+        position: 4
+    features:
+        title: Features
+        position: 6
+    advanced-topics:
+        title: Advanced Topics
+        position: 7
+
+#   Implement Code in Test Section
+    code-in-test/element-identification:
+        title: Element Identification
+        position: 2
+    code-in-test/html-control-suite:
+        title: HTML Control Suite
+        position: 3
+    code-in-test/silverlight-wpf-automation-wtc:
+        title: WPF/Silverlight Automation
+        position: 4
+    code-in-test/settings-and-configuration-wtc:
+        title: Settings and Configuration
+        position: 5
+    code-in-test/advanced-topics-wtc:
+        title: Advanced Topics
+        position: 6
+    code-in-test/coded-samples:
+        title: Coded Samples
+        position: 7
+
+#   Implement Code in Tests/Advanced Topics Section
+    code-in-test/advanced-topics-wtc/html-popups-and-dialogs-wtc:
+        title: Popups and Dialogs
+        position: 0
+    code-in-test/advanced-topics-wtc/javascript-wtc:
+        title: JavaScript
+        position: 1
+    code-in-test/advanced-topics-wtc/test-regions-wtc:
+        title: Test Regions
+        position: 2
+
+#   Implement Code in Tests/Coded Samples Section
+    code-in-test/coded-samples/general:
+        title: General
+        position: 0
+    code-in-test/coded-samples/html:
+        title: HTML
+        position: 1
+    code-in-test/coded-samples/silverlight:
+        title: Silverlight
+        position: 2
+    code-in-test/coded-samples/wpf:
+        title: WPF
+        position: 3
+
+#   Implement Code in Tests/Coded Samples/Silverlight Section
+    code-in-test/coded-samples/silverlight/combobox-automation:
+        title: ComboBox Automatiion
+        position: 0
+    code-in-test/coded-samples/silverlight/radgridview-automation:
+        title: RadGridView Automation
+        position: 1
+
+#   Features Section
+    features/recorder:
+        title: Recorder
+        position: 1
+    features/elements-explorer:
+        title: Elements Explorer
+        position: 2
+    features/test-execution:
+        title: Test Execution
+        position: 3
+    features/failed-tests-debugging:
+        title: Debug Failed Tests
+        position: 4
+    features/test-maintenance:
+        title: Test Maintenance
+        position: 5
+    features/data-driven-testing:
+        title: Data Driven Testing
+        position: 6    
+    features/logical-steps:
+        title: Logical Steps
+        position: 7
+    features/custom-steps:
+        title: Custom Steps
+        position: 8
+    features/project-settings:
+        title: Project Settings
+        position: 9
+
+#   Features/Recorder Section
+    features/recorder/verifications:
+        title: Verifications
+        position: 5
+    features/recorder/mouse-actions:
+        title: Mouse Actions
+        position: 6
+    features/recorder/specific-recording-scenario:
+        title: Recording Specifics
+        position: 7
+
+#   Advanced Topics Section
+    advanced-topics/installation:
+        title: Installation
+        position: 0
+    advanced-topics/recording:
+        title: Recording
+        position: 1
+    advanced-topics/elements:
+        title: Elements
+        position: 2
+    advanced-topics/data-driven-testing:
+        title: Data Driven Testing 
+        position: 3
+    advanced-topics/project-configuration:
+        title: Project Configuration
+        position: 4
+    advanced-topics/ci:
+        title: Continuous Integration
+        position: 5
+    api:
+        title: API Reference
+        position: 1000
+        pdfHidden: true
+
+redirects: 
+-
+    from: "^/?$"
+    to: "/introduction"
+-
+    from: "^/getting-started(\\.html)?$"
+    to: "/quickstart"
+-
+    from: "^/basic-usage/rapid-testing-with-justcode(\\.html)?$"
+    to: "/introduction"
+-
+    from: "^/advanced-usage/openaccess-mocking(\\.html)?$"
+    to: "/introduction"
+-
+    from: "^/scenarios(\\.html)?$"
+    to: "/introduction"
\ No newline at end of file
diff --git a/docs-teststudiodev/downloads/Jenkins_Plugin_TeststudioDev.zip b/docs-teststudiodev/downloads/Jenkins_Plugin_TeststudioDev.zip
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/downloads/TestSettings1.zip b/docs-teststudiodev/downloads/TestSettings1.zip
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/favicon.ico b/docs-teststudiodev/favicon.ico
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/cli-runner.md b/docs-teststudiodev/features/cli-runner.md
index 4dd39178..9a3638e2 100644
--- a/docs-teststudiodev/features/cli-runner.md
+++ b/docs-teststudiodev/features/cli-runner.md
@@ -12,13 +12,13 @@ The ArtOfTest.Runner.exe is the command line runner for __Test Studio Dev__ test
 
 When working with the execution engine in the command prompt always make sure you have started it as Administrator and have the root directory in context as shown below so that you can call the runner directly.
 
-![cmd][1]
+![cmd](images/artoftest-runner/fig1.png)
 
 ## Help Screen
 
 Here is the Help Screen for ArtOfTest.Runner.exe:
 
-![Options][2]
+![Options](images/artoftest-runner/fig2.png)
 
 ## Execution Options
 
@@ -29,7 +29,7 @@ Several execution options use file paths as values. When using file paths in the
 - Enclose the file path in double quotes.
 - To prevent typing mistakes, use the clipboard paste option within the command prompt window. To find the paste option after copying the path to the clipboard, right mouse click on the top left corner of the command prompt and choose **Edit > Paste**.
 
-![Edit>Paste][3]
+![Edit>Paste](images/artoftest-runner/fig3.png)
 
 ### File to Execute Options
 
@@ -37,10 +37,10 @@ Several execution options use file paths as values. When using file paths in the
 
 <table id="no-table">
 <tr>
-<td>![Test Execution Syntax][4]<br>ArtOfTest.Runner Test Execution syntax</td>
+<td><img src="images/artoftest-runner/fig4.png" alt="Test Execution Syntax" /><br>ArtOfTest.Runner Test Execution syntax</td>
 </tr>
 <tr>
-<td>![Test Execution Result][5]<br>ArtOfTest.Runner Test Execution result</td>
+<td><img src="images/artoftest-runner/fig5.png" alt="Test Execution Result" /><br>ArtOfTest.Runner Test Execution result</td>
 </tr>
 <table>
 
@@ -66,7 +66,7 @@ Several execution options use file paths as values. When using file paths in the
 
 Below is an example of a complete JSON setting file that contains all of Telerik's test/test list run configuration settings. These are corresponding to the available <a href="/features/test-execution/test-list-settings" target="_blank">test list settings</a>.
 
-```JSON
+````JSON
 {
   "Settings": {
     "__type": "ArtOfTest.WebAii.Core.Settings",
@@ -131,7 +131,7 @@ Below is an example of a complete JSON setting file that contains all of Telerik
   "PropertyBag": null
 }
 
-```
+````
 
 ## Exit Codes
 
@@ -165,36 +165,45 @@ padding: 8px;
 	<th>Code</th><th>Title</th><th>Summary</th>
 </tr>
 <tr>
-	<td>**0**</td><td>RUN_TESTS_SUCCESS </td><td>Run is processed and all tests passed.</td>
+<td>
+	
+**0**</td><td>RUN_TESTS_SUCCESS </td><td>Run is processed and all tests passed.</td>
 </tr>
 <tr>
-	<td>**1**</td><td>RUN_TESTS_ERROR</td><td>Run is processed and some tests failed.</td>
+<td>
+	
+**1**</td><td>RUN_TESTS_ERROR</td><td>Run is processed and some tests failed.</td>
 </tr>
 <tr>
-	<td>**2**</td><td>NOT_RUN_UNEXPECTED_ERROR</td><td>Run is not processed due to unexpected error.</td>
+<td>
+	
+**2**</td><td>NOT_RUN_UNEXPECTED_ERROR</td><td>Run is not processed due to unexpected error.</td>
 </tr>
 <tr>
-	<td>**3**</td><td>NOT_RUN_COMPILATION_ERROR</td><td>Run is not processed due to compilation errors.</td>
+<td>
+	
+**3**</td><td>NOT_RUN_COMPILATION_ERROR</td><td>Run is not processed due to compilation errors.</td>
 </tr>
 <tr>
-	<td>**10**</td><td>NOT_RUN_USAGE_INFO</td><td>No run to process, requested usage info.</td>
+<td>
+	
+**10**</td><td>NOT_RUN_USAGE_INFO</td><td>No run to process, requested usage info.</td>
 </tr>
 <tr>
-	<td>**11**</td><td>NOT_RUN_INVALID_COMMAND_ARGS</td><td>No run to process due to general invalid arguments error.</td>
+<td>
+	
+**11**</td><td>NOT_RUN_INVALID_COMMAND_ARGS</td><td>No run to process due to general invalid arguments error.</td>
 </tr>
 <tr>
-	<td>**12**</td><td>NOT_RUN_TEST_NOT_FOUND</td><td>Run is not processed due to invalid test path argument.</td>
+<td>
+	
+**12**</td><td>NOT_RUN_TEST_NOT_FOUND</td><td>Run is not processed due to invalid test path argument.</td>
 </tr>
 <tr>
-	<td>**13**</td><td>NOT_RUN_TESTLIST_NOT_FOUND</td><td>Run is not processed due to invalid test list path argument.</td>
+<td>
+	
+**13**</td><td>NOT_RUN_TESTLIST_NOT_FOUND</td><td>Run is not processed due to invalid test list path argument.</td>
 </tr>
 <table>
 
-[1]: images/artoftest-runner/fig1.png
-[2]: images/artoftest-runner/fig2.png
-[3]: images/artoftest-runner/fig3.png
-[4]: images/artoftest-runner/fig4.png
-[5]: images/artoftest-runner/fig5.png
-[6]: images/artoftest-runner/fig6.png
-[7]: images/artoftest-runner/fig7.png
-[8]: images/artoftest-runner/fig8.png
\ No newline at end of file
+
diff --git a/docs-teststudiodev/features/custom-steps/images/change-window-state.png b/docs-teststudiodev/features/custom-steps/images/change-window-state.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig2.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig3.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig4.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig5.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig6.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig7.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig8.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig9.png b/docs-teststudiodev/features/custom-steps/images/check-js-errors/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/clear-browser-cache.png b/docs-teststudiodev/features/custom-steps/images/clear-browser-cache.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/comment-step.png b/docs-teststudiodev/features/custom-steps/images/comment-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/custom-annotation-step.png b/docs-teststudiodev/features/custom-steps/images/custom-annotation-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/custom-annotation-view.png b/docs-teststudiodev/features/custom-steps/images/custom-annotation-view.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/enable-annotations.png b/docs-teststudiodev/features/custom-steps/images/enable-annotations.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/execution-delay-step.png b/docs-teststudiodev/features/custom-steps/images/execution-delay-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/inspect-dom-step.png b/docs-teststudiodev/features/custom-steps/images/inspect-dom-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/inspect-dom-test-paused.png b/docs-teststudiodev/features/custom-steps/images/inspect-dom-test-paused.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/manual-step-execution.png b/docs-teststudiodev/features/custom-steps/images/manual-step-execution.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/manual-step.png b/docs-teststudiodev/features/custom-steps/images/manual-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/maximize-browser.png b/docs-teststudiodev/features/custom-steps/images/maximize-browser.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/navigate-to-step.png b/docs-teststudiodev/features/custom-steps/images/navigate-to-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/refresh-browser.png b/docs-teststudiodev/features/custom-steps/images/refresh-browser.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/script-file.png b/docs-teststudiodev/features/custom-steps/images/script-file.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/script-step.png b/docs-teststudiodev/features/custom-steps/images/script-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/select-test-as-step.png b/docs-teststudiodev/features/custom-steps/images/select-test-as-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/step-builder-common.png b/docs-teststudiodev/features/custom-steps/images/step-builder-common.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/test-as-step.png b/docs-teststudiodev/features/custom-steps/images/test-as-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/custom-steps/images/wait-for-url.png b/docs-teststudiodev/features/custom-steps/images/wait-for-url.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/add-data-source.md b/docs-teststudiodev/features/data-driven-testing/add-data-source.md
index 4d05b79a..e0c67710 100644
--- a/docs-teststudiodev/features/data-driven-testing/add-data-source.md
+++ b/docs-teststudiodev/features/data-driven-testing/add-data-source.md
@@ -12,33 +12,33 @@ position: 2
 
 The first row entries in the Excel spreadsheet are used as column names when attaching columns to the inputs. In this example, *Input A* is the name of the first column, *Input B* is the name of the second column, and *Results* is the name of the third column and these will be used to identify the columns to attach to the input values of the test steps.
 
-![Excel][1]
+![Excel](images/add-data-source/fig1.png)
 
 > _Note!__ For numeric-only fields, you may need to add an apostrophe, also known as a single quote character ( ' ), to the beginning of the number for the data to render correctly in Test Studio. This is an Excel command to store the number as text.
 
 Open the data source dropdown by clicking its button down arrow, then select **Add New > Excel**.
 
-![Excel VS][3]
+![Excel VS](images/add-data-source/fig3.png)
 
 The **Create new data source** dialog opens:
 
-![Create new datasource][4]
+![Create new datasource](images/add-data-source/fig4.png)
 
 Enter the path to your Excel file or click the "..." button to browse and select it. Click _Create_ to save this data source definition. A new entry is added to the Data folder of your test project.
 
-![Solution expl][7]
+![Solution expl](images/add-data-source/fig7.png)
 
 Click Ok to confirm binding the current test to the Excel data file.
 
-![Confirm][6]
+![Confirm](images/add-data-source/fig6.png)
 
 Then select data source and data table in the _Bind test to data source_ dialog to see the Excel sheet data bound to the test. 
 
 <table id="no-table">
 <tr>
-<td>![Select Data source][11]</td>
-<td>![Select Data table][12]</td>
-<td>![Preview bound data][13]</td>
+<td><img src="images/add-data-source/fig11.png" alt="Select Data source" /></td>
+<td><img src="images/add-data-source/fig12.png" alt="Select Data table" /></td>
+<td><img src="images/add-data-source/fig13.png" alt="Preview bound data" /></td>
 </tr>
 <table>
 
@@ -46,17 +46,17 @@ Then select data source and data table in the _Bind test to data source_ dialog
 
 Here is an example of a basic XML file with two columns:
 
-```xml
+````XML
 <Searches>
    <Search UserName="john.smith" Password="t3ler1k" />
    <Search UserName="bob.brown" Password="5ilverl1ght" />
    <Search UserName="sam.jones" Password="t3st5tudi0" />
 </Searches>
-```
+````
 
 *Search* is the equivalent of an Excel Sheet. *UserName* and *Password* translate as the column names. Use **$(UserName)** and **$(Password)** to data bind the applicable properties.
 
-![Bind XML file][8]
+![Bind XML file](images/add-data-source/fig8.png)
 
 ## Add a CSV File
 
@@ -64,7 +64,7 @@ CSV files can be created in any spreadsheet application or directly in Notepad i
 
 Here is an example of a basic CSV file with two columns:
 
-![CSV file][9]
+![CSV file](images/add-data-source/fig9.png)
 
 Just like an Excel spreadsheet, the first row of data will be used as the column names. Use **$(UserName)** and **$(Password)** to data bind the applicable properties.
 
@@ -77,7 +77,7 @@ Adding a database source is different than adding an Excel spreadsheet, CSV, or
 - **Test** - click this button to test the connection to your database. A dialog indicating success will display if <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> makes a connection.
 - **Friendly Name** - enter a name to represent this database connection definition. The name entered here is displayed in the Data Sources pane in the Standalone version and in the Data folder in the VS plugin.
 
-![Database source][10]
+![Database source](images/add-data-source/fig10.png)
 
 Once you have added the data source you could proceed to <a href="/features/data-driven-testing/bind-test-data-source" target="_blank">__bind a test to that data source__</a>. 
 
@@ -86,15 +86,3 @@ __See Also:__
 * <a href="/advanced-topics/data-driven-testing/sql-database-example" target="_blank">How to connect a SQL Database to be used for data source</a>
 *  <a href="/advanced-topics/data-driven-testing/oracle-db-example" target="_blank">How to connect an Oracle Database to be used for data source</a>
 
-[1]: images/add-data-source/fig1.png
-[3]: images/add-data-source/fig3.png
-[4]: images/add-data-source/fig4.png
-[5]: images/add-data-source/fig5.png
-[6]: images/add-data-source/fig6.png
-[7]: images/add-data-source/fig7.png
-[8]: images/add-data-source/fig8.png
-[9]: images/add-data-source/fig9.png
-[10]: images/add-data-source/fig10.png
-[11]: images/add-data-source/fig11.png
-[12]: images/add-data-source/fig12.png
-[13]: images/add-data-source/fig13.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/data-driven-testing/attach-columns-input-values.md b/docs-teststudiodev/features/data-driven-testing/attach-columns-input-values.md
index e34e5444..435c64e7 100644
--- a/docs-teststudiodev/features/data-driven-testing/attach-columns-input-values.md
+++ b/docs-teststudiodev/features/data-driven-testing/attach-columns-input-values.md
@@ -8,29 +8,25 @@ position: 4
 
 Most action steps have at least one property that can be bound to a column from your data source. To bind a test step property to a project data source column follow the steps below:
 
-1.&nbsp; Click the step in the Test Steps pane to activate its properties in the Property pane.
+1. Click the step in the Test Steps pane to activate its properties in the Property pane.
 
-2.&nbsp; Click the _(Collection)_ dropdown next to the _(Bindings)_ property to see the available properties for the selected step which could be data driven. 
+2. Click the _(Collection)_ dropdown next to the _(Bindings)_ property to see the available properties for the selected step which could be data driven. 
 
-![Properties to data drive][1]
+    ![Properties to data drive](images/attach-columns-input-values/fig1.png)
 
-3.&nbsp; Click the dropdown menu next to the step property which will be data driven to see the available columns from the data source.
+3. Click the dropdown menu next to the step property which will be data driven to see the available columns from the data source.
 
-![Display column from data source][2]
+    ![Display column from data source](images/attach-columns-input-values/fig2.png)
 
-4.&nbsp; Select the column name which contains the respective values for that property and click the **Set** button. 
+4. Select the column name which contains the respective values for that property and click the **Set** button. 
 
-![Select column][3]
+![Select column](images/attach-columns-input-values/fig3.png)
 
 >__Note!__ If the current test is used as a <a href="/features/custom-steps/test-as-step" target=blank>test as step and inherits the parent data source or there is a variable value extracted in code the list described above will __not__ contain these.
 
 If you wish to access the data source of a parent test or the extracted variable, type the column or variable name in the text box (without the $ notation), click the brackets and **Set** button. 
 
-![Variable extracted in code][4]
+![Variable extracted in code](images/attach-columns-input-values/fig4.png)
 
 Review how to attach a column to <a href="/features/data-driven-test/attach-columns-verifications" target=blank>Verification step</a>. 
 
-[1]: images/attach-columns-input-values/fig1.png
-[2]: images/attach-columns-input-values/fig2.png
-[3]: images/attach-columns-input-values/fig3.png
-[4]: images/attach-columns-input-values/fig4.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/data-driven-testing/attach-columns-verifications.md b/docs-teststudiodev/features/data-driven-testing/attach-columns-verifications.md
index c40ea94f..5d7154c3 100644
--- a/docs-teststudiodev/features/data-driven-testing/attach-columns-verifications.md
+++ b/docs-teststudiodev/features/data-driven-testing/attach-columns-verifications.md
@@ -8,29 +8,25 @@ position: 5
 
 The verification steps also have at least one property that can be bound to a column from your data source. To bind a test step property to a project data source follow the steps below:
 
-1.&nbsp; Click the step in the Test Steps pane to activate its properties in the Property pane.
+1. Click the step in the Test Steps pane to activate its properties in the Property pane.
 
-2.&nbsp; Click the _(Collection)_ dropdown next to the _(Bindings)_ property to see the available properties for the selected step which could be data driven.
+2. Click the _(Collection)_ dropdown next to the _(Bindings)_ property to see the available properties for the selected step which could be data driven.
 
-![Properties to data drive][1]
+    ![Properties to data drive](images/attach-columns-verifications/fig1.png)
 
-3.&nbsp; Click the dropdown menu next to the step property which will be data driven to see the available columns from the data source.
+3. Click the dropdown menu next to the step property which will be data driven to see the available columns from the data source.
 
-![Display column from data source][2]
+    ![Display column from data source](images/attach-columns-verifications/fig2.png)
 
-4.&nbsp; Select the column name which contains the respective values for that property and click the **Set** button. 
+4. Select the column name which contains the respective values for that property and click the **Set** button. 
 
-![Select column][3]
+![Select column](images/attach-columns-verifications/fig3.png)
 
 >__Note!__ If the current test is used as a <a href="/features/custom-steps/test-as-step" target=blank>test as step and inherits the parent data source or there is a variable value extracted in code the list described above will __not__ contain these.
 
 If you wish to access the data source of a parent test or the extracted variable, type the column or variable name in the text box (without the $ notation), click the brackets and **Set** button.
 
-![Variable extracted in code][4]
+![Variable extracted in code](images/attach-columns-verifications/fig4.png)
 
 Review how to attach a column to <a href="/features/data-driven-test/attach-columns-input-values" target=blank>Input value step</a>. 
 
-[1]: images/attach-columns-verifications/fig1.png
-[2]: images/attach-columns-verifications/fig2.png
-[3]: images/attach-columns-verifications/fig3.png
-[4]: images/attach-columns-verifications/fig4.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/data-driven-testing/bind-test-data-source.md b/docs-teststudiodev/features/data-driven-testing/bind-test-data-source.md
index 5944ac9f..de36602a 100644
--- a/docs-teststudiodev/features/data-driven-testing/bind-test-data-source.md
+++ b/docs-teststudiodev/features/data-driven-testing/bind-test-data-source.md
@@ -8,15 +8,15 @@ position: 3
 
 Now that you have added a data source definition to your test project, you are ready to bind your test to that data source. Click the _Bind test to data source_ button. 
 
-![Bind test to data source][2]
+![Bind test to data source](images/bind-test-data-source/fig2.png)
 
 The **Bind test to data source** dialog opens:
 
-![Bind test to data source][3]
+![Bind test to data source](images/bind-test-data-source/fig3.png)
 
 Click the **Select DataSource** dropdown and choose the data source you just defined in the previous section. If your source is an Excel spreadsheet, choose which sheet from the spreadsheet to use. Once you select a sheet, the data from that sheet will be read and displayed in the dialog. Note that the first row of the excel spreadsheet is used to define the column names.
 
-![Select Data Source][4]
+![Select Data Source](images/bind-test-data-source/fig4.png)
 
 Check the **Filter data between rows** box under the **Configure** section to adjust which rows from the data source to use:
 
@@ -25,8 +25,8 @@ Check the **Filter data between rows** box under the **Configure** section to ad
 
 <table id="no-table">
 <tr>
-<td>![filter data][5]</td>
-<td>![filter data][6]</td>
+<td><img src="images/bind-test-data-source/fig5.png" alt="filter data" /></td>
+<td><img src="images/bind-test-data-source/fig6.png" alt="filter data" /></td>
 </tr>
 <table>
 
@@ -34,7 +34,7 @@ Check the **Filter data between rows** box under the **Configure** section to ad
 
 If your source is a __SQL database__, you have the option of using T-SQL to select the data you want. Using T-SQL, you can get as complex as you need in your SQL select statement. For example:
 
-![SQL database][7]
+![SQL database](images/bind-test-data-source/fig7.png)
 
 After entering your select statement, click **Update** to test and display the selected data in the **Preview** table.
 
@@ -44,14 +44,7 @@ Click OK to bind this data source to your test.
 
 To remove the external data source associated with a test, open the test and click the down arrow of the _Bind test to data source_ button and click on __Unbind__.
 
-![Remove Data Binding][8]
+![Remove Data Binding](images/bind-test-data-source/fig8.png)
 
 After you have configured the test to use a data source you can attach the data columns to <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">__an input value__</a> or <a href="/features/data-driven-testing/attach-columns-verifications" target="_blank">__a verification__</a>. 
 
-[2]: images/bind-test-data-source/fig2.png
-[3]: images/bind-test-data-source/fig3.png
-[4]: images/bind-test-data-source/fig4.png
-[5]: images/bind-test-data-source/fig5.png
-[6]: images/bind-test-data-source/fig6.png
-[7]: images/bind-test-data-source/fig7.png
-[8]: images/bind-test-data-source/fig8.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig1.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig10.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig11.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig12.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig13.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig4.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig5.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig6.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig7.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig8.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig9.png b/docs-teststudiodev/features/data-driven-testing/images/add-data-source/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig1.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig2.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig4.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-input-values/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig1.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig2.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig4.png b/docs-teststudiodev/features/data-driven-testing/images/attach-columns-verifications/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig2.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig4.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig5.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig6.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig7.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig8.png b/docs-teststudiodev/features/data-driven-testing/images/bind-test-data-source/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig1.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig12.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig20.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig20.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig21.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig21.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig22.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig22.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig23.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig23.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig4.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig5.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig6.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig9.png b/docs-teststudiodev/features/data-driven-testing/images/local-data-driven-test/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig1.png b/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig2.png b/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig3.png b/docs-teststudiodev/features/data-driven-testing/images/quick-execute-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/data-driven-testing/local-data-driven-test.md b/docs-teststudiodev/features/data-driven-testing/local-data-driven-test.md
index d8ff4bde..7e466c70 100644
--- a/docs-teststudiodev/features/data-driven-testing/local-data-driven-test.md
+++ b/docs-teststudiodev/features/data-driven-testing/local-data-driven-test.md
@@ -8,67 +8,57 @@ position: 1
 
 Let's create a new, Local Data Driven test. We'll go through five iterations of the test, each with a different search text.
 
-1.Create a new Web Test and click Record.
+1. Create a new Web Test and click Record.
 
-2.Navigate to www.google.com, enter *Telerik* in the Google search box, and hit the Search button.
+2. Navigate to www.google.com, enter *Telerik* in the Google search box, and hit the Search button.
 
-3.Click the **Pause recording** button in the <a href="/features/recorder/recording-toolbar" target="_blank">Recording toolbar</a>.
+3. Click the **Pause recording** button in the <a href="/features/recorder/recording-toolbar" target="_blank">Recording toolbar</a>.
 
-![Pause recording][1]
+    ![Pause recording](images/local-data-driven-test/fig1.png)
 
-4.Click the **Data** tab in the current test.
+4. Click the **Data** tab in the current test.
 
-![Local Data][3]
+    ![Local Data](images/local-data-driven-test/fig3.png)
 
-5.There are few buttons at the top of this pane and at this point only **Create a new data table** is enabled. Click it to add a new data grid.
+5. There are few buttons at the top of this pane and at this point only **Create a new data table** is enabled. Click it to add a new data grid.
 
-![Create a new data table][4]
+    ![Create a new data table](images/local-data-driven-test/fig4.png)
 
-6.The default grid will have five columns and a single row. Also the rest of the buttons get active and allows you to modify the grid.
+6. The default grid will have five columns and a single row. Also the rest of the buttons get active and allows you to modify the grid.
 
 - Set number of rows and columns (columns are limited to 50) and update the grid
 
-![Set number of rows and columns][20]
+    ![Set number of rows and columns](images/local-data-driven-test/fig20.png)
 
 - Create new data table or remove current data table - both options inform that the current data is deleted if you go ahead
 
-![Create new or remove data table][21]
+    ![Create new or remove data table](images/local-data-driven-test/fig21.png)
 
 - Add a row/Delete the last row or Add a column/Delete the last column
 
 <table id="no-table">
 <tr>
-<td>![Add/Delete Row][22]<br>Add/Delete Row</td>
-<td>![Add/Delete Column][23]<br>Add/Delete Column</td>
+<td><img src="images/local-data-driven-test/fig22.png" alt="Add/Delete Row" /><br>Add/Delete Row</td>
+<td><img src="images/local-data-driven-test/fig23.png" alt="Add/Delete Column" /><br>Add/Delete Column</td>
 </tr>
 <table>
 
-7.For this example we want to execute five iterations of the test entering different search text for each iteration. Therefore modify the table to have a single column and 5 rows and click on _Update_. 
+7. For this example we want to execute five iterations of the test entering different search text for each iteration. Therefore modify the table to have a single column and 5 rows and click on _Update_. 
 
-![Update the local data grid][5]
+    ![Update the local data grid](images/local-data-driven-test/fig5.png)
 
-8.Enter random values in each of the cells in that column. Right click *Col1* and choose **Rename Column** to enter a meaningful to you name for the column. Then save the modified test.
+8. Enter random values in each of the cells in that column. Right click *Col1* and choose **Rename Column** to enter a meaningful to you name for the column. Then save the modified test.
 
-![Enter values and rename the column][6]
+    ![Enter values and rename the column](images/local-data-driven-test/fig6.png)
 
-9.Get back to the **Steps** tab and select step 2. This is the recorded step that sets the value of the Google search text box and open its properties in the Properties pane. 
+9. Get back to the **Steps** tab and select step 2. This is the recorded step that sets the value of the Google search text box and open its properties in the Properties pane. 
 
-![Enter Text Step][9]
+    ![Enter Text Step](images/local-data-driven-test/fig9.png)
 
-10.Click the '...' button for the **(Bindings)** property and select the column name created in the local data to set it for the Text property of the selected step. Click the **Set** button.
+10. Click the '...' button for the **(Bindings)** property and select the column name created in the local data to set it for the Text property of the selected step. Click the **Set** button.
 
-![Bind step][12]
+    ![Bind step](images/local-data-driven-test/fig12.png)
 
 The data for the column in the local grid is now bound to the _Text_ property for the 'Enter text' step. Instead of entering _Telerik_ into the search box, the data stored in the data table will be entered. Save and execute the test. Note that the test will be executed for each row in the data table, for a total of five iterations.
 
-[1]: images/local-data-driven-test/fig1.png
-[3]: images/local-data-driven-test/fig3.png
-[4]: images/local-data-driven-test/fig4.png
-[5]: images/local-data-driven-test/fig5.png
-[6]: images/local-data-driven-test/fig6.png
-[9]: images/local-data-driven-test/fig9.png
-[12]: images/local-data-driven-test/fig12.png
-[20]: images/local-data-driven-test/fig20.png
-[21]: images/local-data-driven-test/fig21.png
-[22]: images/local-data-driven-test/fig22.png
-[23]: images/local-data-driven-test/fig23.png
+
diff --git a/docs-teststudiodev/features/elements-explorer/element-mapping.md b/docs-teststudiodev/features/elements-explorer/element-mapping.md
index 9d59c7f9..d80dd49c 100644
--- a/docs-teststudiodev/features/elements-explorer/element-mapping.md
+++ b/docs-teststudiodev/features/elements-explorer/element-mapping.md
@@ -10,8 +10,8 @@ Once your application is ready for testing you can map your <a href="/features/e
 
 <table id="no-table">
 	<tr>
-		<td>!![Element Mapping TS][6] <br><br>**Standalone version**</td>
-		<td>![Element Mapping TS][15] <br><br>**VS plugin**</td>
+		<td><img src="images/element-mapping/fig6.png" alt="Element Mapping TS" /> <br><br>**Standalone version**</td>
+		<td><img src="images/element-mapping/fig15.png" alt="Element Mapping TS" /> <br><br>**VS plugin**</td>
 	</tr>
 <table>
 
@@ -23,8 +23,8 @@ The mapping dialog window appears allowing you to select between a Web or WPF te
 
 <table id="no-table">
 <tr>
-<td>![Web][7] <br><br>**Web**</td>
-<td>![WPF][8] <br><br>**WPF**</td>
+<td><img src="images/element-mapping/fig7.png" alt="Web" /> <br><br>**Web**</td>
+<td><img src="images/element-mapping/fig8.png" alt="WPF" /> <br><br>**WPF**</td>
 <tr>
 <table>
 
@@ -32,43 +32,34 @@ The mapping dialog window appears allowing you to select between a Web or WPF te
 
 Select Recording browser and click **Record**. 
 
-![Choose Recording Browser][9]
+![Choose Recording Browser](images/element-mapping/fig9.png)
 
 Test Studio will navigate to the URL, attach the recorder and enable Highlighting so you can directly highlight the desired element and click on **Select Element** as shown below:
 
 
-![Select Element][10]
+![Select Element](images/element-mapping/fig10.png)
 
 You select the predefined element you would like to map (1) from the Elements section, confirm the find logic (2) and click on Map Element button (3).
 
-![Map Element][11]
+![Map Element](images/element-mapping/fig11.png)
 
 > Please note in the example above we are working with only one predefined element in the Elements section. However you can have many predefined elements listed there. You need to be careful when mapping with an actual element which predefined element is selected. In order to avoid confusion it will be best to use descriptive friendly names to your predefined elements.
 
 In case you would like to build more robust find logic before mapping the predefined element you can add an **Expression Item**.
 
-![Add Expression Item][12]
+![Add Expression Item](images/element-mapping/fig12.png)
 
 Another filter is added so you can tweak the element's find logic.
 
-![find logic][13]
+![find logic](images/element-mapping/fig13.png)
 
 You can undo all the changes and revert to the default find expression using the **Restore Default Expression** button.
 
-![Restore Default Expression][14]
+![Restore Default Expression](images/element-mapping/fig14.png)
 
 <br>
 <br>
 
 * See Also: <a href="/features/elements-explorer/predefined-elements" target="_blank">Predefined elements</a>
 
-[6]: images/element-mapping/fig6.png
-[7]: images/element-mapping/fig7.png
-[8]: images/element-mapping/fig8.png
-[9]: images/element-mapping/fig9.png
-[10]: images/element-mapping/fig10.png
-[11]: images/element-mapping/fig11.png
-[12]: images/element-mapping/fig12.png
-[13]: images/element-mapping/fig13.png
-[14]: images/element-mapping/fig14.png
-[15]: images/element-mapping/fig15.png
+
diff --git a/docs-teststudiodev/features/elements-explorer/find-element.md b/docs-teststudiodev/features/elements-explorer/find-element.md
index bec5342f..0e020eb1 100644
--- a/docs-teststudiodev/features/elements-explorer/find-element.md
+++ b/docs-teststudiodev/features/elements-explorer/find-element.md
@@ -62,7 +62,7 @@ The **Find Settings** view is on the right side. You can edit these settings by
 
 <table id="no-table">
 <tr>
-<td>![Element Found](images/find-element/fig12.png)</td>
-<td>![Element Not Found](images/find-element/fig13.png)</td>
+<td><img src="images/find-element/fig12.png" alt="Element Found" /></td>
+<td><img src="images/find-element/fig13.png" alt="Element Not Found" /></td>
 </tr>
 <table>
\ No newline at end of file
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig1.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig10.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig11.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig12.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig13.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig14.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig15.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig15.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig16.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig16.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig17.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig17.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig18.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig18.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig19.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig19.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig2.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig20.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig20.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig3.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig4.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig5.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig6.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig7.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig8.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig9.png b/docs-teststudiodev/features/elements-explorer/images/element-mapping/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig1.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig10.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig11.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig12.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig13.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig3.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig4.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig5.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig6.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig7.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig8.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/find-element/fig9.png b/docs-teststudiodev/features/elements-explorer/images/find-element/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/element-context.png b/docs-teststudiodev/features/elements-explorer/images/overview/element-context.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/elements-explorer.png b/docs-teststudiodev/features/elements-explorer/images/overview/elements-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/html-tree-view.png b/docs-teststudiodev/features/elements-explorer/images/overview/html-tree-view.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/menu-bar.png b/docs-teststudiodev/features/elements-explorer/images/overview/menu-bar.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/page-node-context.png b/docs-teststudiodev/features/elements-explorer/images/overview/page-node-context.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/silverlight-tree-view.png b/docs-teststudiodev/features/elements-explorer/images/overview/silverlight-tree-view.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/images/overview/wpf-tree-view.png b/docs-teststudiodev/features/elements-explorer/images/overview/wpf-tree-view.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/elements-explorer/overview.md b/docs-teststudiodev/features/elements-explorer/overview.md
index 21fbf812..fd2f4e70 100644
--- a/docs-teststudiodev/features/elements-explorer/overview.md
+++ b/docs-teststudiodev/features/elements-explorer/overview.md
@@ -40,9 +40,9 @@ The hierarchy is maintained according to where the element is located on the pag
 
 <table id="no-table">
 <tr>
-<td>![HTML Tree View](images/overview/html-tree-view.png)<br>**HTML Tree View**</td>
-<td>![Silverlight Tree View](images/overview/silverlight-tree-view.png)<br>**Silverlight Tree View**</td>
-<td>![WPF Tree View](images/overview/wpf-tree-view.png)<br> **WPF Tree View**</td>
+<td><img src="images/overview/html-tree-view.png" alt="HTML Tree View" /><br>**HTML Tree View**</td>
+<td><img src="images/overview/silverlight-tree-view.png" alt="Silverlight Tree View" /><br>**Silverlight Tree View**</td>
+<td><img src="images/overview/wpf-tree-view.png" alt="WPF Tree View" /><br> **WPF Tree View**</td>
 </tr>
 <table>
 
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig1.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig2.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig3.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig4.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig5.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig6.png b/docs-teststudiodev/features/failed-tests-debugging/images/step-failure-details/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-dom-on-failure/fig1.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-dom-on-failure/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig1.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig2.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig3.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig4.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/quick-execution-log-copy.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-execution-log/quick-execution-log-copy.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig1.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig2.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig3.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig4.png b/docs-teststudiodev/features/failed-tests-debugging/images/using-the-visual-debugger/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig1.png b/docs-teststudiodev/features/images/artoftest-runner/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig2.png b/docs-teststudiodev/features/images/artoftest-runner/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig3.png b/docs-teststudiodev/features/images/artoftest-runner/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig4.png b/docs-teststudiodev/features/images/artoftest-runner/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig5.png b/docs-teststudiodev/features/images/artoftest-runner/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig6.png b/docs-teststudiodev/features/images/artoftest-runner/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig7.png b/docs-teststudiodev/features/images/artoftest-runner/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/images/artoftest-runner/fig8.png b/docs-teststudiodev/features/images/artoftest-runner/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/if-else.md b/docs-teststudiodev/features/logical-steps/if-else.md
index df0a94ce..a7fb7db5 100644
--- a/docs-teststudiodev/features/logical-steps/if-else.md
+++ b/docs-teststudiodev/features/logical-steps/if-else.md
@@ -11,87 +11,72 @@ Walk-through the IF...Else conditional statement process - <a href="/features/lo
 
 ## Build a new If...Else Statement
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to <a href="https://www.random.org/" target="_blank">www.random.org</a>.
+2. Navigate to <a href="https://www.random.org/" target="_blank">www.random.org</a>.
 
-3.&nbsp; Set the Min field to 1 and the Max field to 2.
+3. Set the Min field to 1 and the Max field to 2.
 
-4.&nbsp; Click **Generate**.
+4. Click **Generate**.
 
-![Random][1]
+    ![Random](images/if-else/fig1.png)
 
-5.&nbsp; Enable hover over highlighting by clicking Highlight Element in the Test Studio Recorder and hover over the *Result box*.
+5. Enable hover over highlighting by clicking Highlight Element in the Test Studio Recorder and hover over the *Result box*.
 
-![Enable Highlighting][2]
+    ![Enable Highlighting](images/if-else/fig2.png)
 
-6.&nbsp; Click **Quick Tasks** and double click **Verify - text contains '1'**.
+6. Click **Quick Tasks** and double click **Verify - text contains '1'**.
 
-![Verification][3]
+    ![Verification](images/if-else/fig3.png)
 
-7.&nbsp; Disable hover over highlighting and minimize the browser.
+7. Disable hover over highlighting and minimize the browser.
 
-8.&nbsp; Choose **Conditions** in the <a href="/features/recorder/step-builder">**Step Builder**</a> and add **if...else** step.
+8. Choose **Conditions** in the <a href="/features/recorder/step-builder">**Step Builder**</a> and add **if...else** step.
 
-![VS Plugin][13]
+    ![VS Plugin](images/if-else/fig13.png)
 
 
-9.&nbsp; From the drop down in the IF step select the previously recorded verification.
+9. From the drop down in the IF step select the previously recorded verification.
 
-![Choose Verification][6]
+    ![Choose Verification](images/if-else/fig6.png)
 
-10.&nbsp; Uncheck/Delete the verification outside the IF step, so it will not be executed (We have this verification already added in the IF step)
+10. Uncheck/Delete the verification outside the IF step, so it will not be executed (We have this verification already added in the IF step)
 
-![Uncheck Verification][7]
+    ![Uncheck Verification](images/if-else/fig7.png)
 
-11.&nbsp; Bring up the IE recording window and navigate to <a href="http://www.google.com" target="_blank">www.google.com</a>. Minimize the browser again.
+11. Bring up the IE recording window and navigate to <a href="http://www.google.com" target="_blank">www.google.com</a>. Minimize the browser again.
 
-12.&nbsp; Drag the *Navigate to Google* step into the IF step.
+12. Drag the *Navigate to Google* step into the IF step.
 
-![Drag in IF Step][8]
+    ![Drag in IF Step](images/if-else/fig8.png)
 
-13.&nbsp; Bring up the IE recording window and navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>. Minimize the browser again.
+13. Bring up the IE recording window and navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>. Minimize the browser again.
 
-14.&nbsp; Drag the *Navigate to Bing* step into the ELSE step.
+14. Drag the *Navigate to Bing* step into the ELSE step.
 
-![Drag in ELSE Step][9]
+    ![Drag in ELSE Step](images/if-else/fig9.png)
 
 ## Execution status and Results
 
-15.&nbsp; Save and Execute the test.
+15. Save and Execute the test.
 
 - If 1 is generated the **if condition** is evaluated as true and the steps in the **if branch** are executed. The steps in the **else branch** are skipped and shown as 'Not Run'.
 
-![Navigate to Google][10]
+    ![Navigate to Google](images/if-else/fig10.png)
 
 - If 2 is generated the **if condition** is evaluated as false (for example, the target TextBox element contains the wrong content) and the steps in the **else branch** are executed. The skipped steps are in the **if branch** and are shown as 'Not Run'. 
 - **Note**:  if the condition of an **if branch** cannot be evaluated (for example, the target element for a TextContent verification cannot be located), the steps in the **if branch** will be skipped again, and will display a 'not-run' icon as if the condition is false. 
 
-![Navigate to Bing][11]
+    ![Navigate to Bing](images/if-else/fig11.png)
 
 ## Check if an element exists in the DOM
 
 To check if an element is present in the application DOM - a "<a href="/features/recorder/verifications/Wait" target="_blank">wait on element</a>" verification has to be used. It returns *true/false* output and **if condition** could be completed not braking the test execution. On the following image - if step 4 does not execute - the *SecondLink* element would not be added to the DOM and steps would continue in the **else branch**.
 
-![If Element Exists][14]
+![If Element Exists](images/if-else/fig14.png)
 
 If step 4 is executed the *SecondLink* element would be added to the DOM and **if condition** passes normally as shown bellow.
 
-![Else Element Exists][15]
-
-[1]: images/if-else/fig1.png
-[2]: images/if-else/fig2.png
-[3]: images/if-else/fig3.png
-[4]: images/if-else/fig4.png
-[5]: images/if-else/fig5.png
-[6]: images/if-else/fig6.png
-[7]: images/if-else/fig7.png
-[8]: images/if-else/fig8.png
-[9]: images/if-else/fig9.png
-[10]: images/if-else/fig10.png
-[11]: images/if-else/fig11.png
-[12]: images/if-else/fig12.png
-[13]: images/if-else/fig13.png
-[14]: images/if-else/fig14.png
-[15]: images/if-else/fig15.png
+![Else Element Exists](images/if-else/fig15.png)
+
 
diff --git a/docs-teststudiodev/features/logical-steps/images/loop/fig1.png b/docs-teststudiodev/features/logical-steps/images/fig1.png
similarity index 100%
rename from docs-teststudiodev/features/logical-steps/images/loop/fig1.png
rename to docs-teststudiodev/features/logical-steps/images/fig1.png
diff --git a/docs-teststudiodev/features/logical-steps/images/loop/fig4.png b/docs-teststudiodev/features/logical-steps/images/fig4.png
similarity index 100%
rename from docs-teststudiodev/features/logical-steps/images/loop/fig4.png
rename to docs-teststudiodev/features/logical-steps/images/fig4.png
diff --git a/docs-teststudiodev/features/logical-steps/images/loop/fig5.png b/docs-teststudiodev/features/logical-steps/images/fig5.png
similarity index 100%
rename from docs-teststudiodev/features/logical-steps/images/loop/fig5.png
rename to docs-teststudiodev/features/logical-steps/images/fig5.png
diff --git a/docs-teststudiodev/features/logical-steps/images/loop/fig7.png b/docs-teststudiodev/features/logical-steps/images/fig7.png
similarity index 100%
rename from docs-teststudiodev/features/logical-steps/images/loop/fig7.png
rename to docs-teststudiodev/features/logical-steps/images/fig7.png
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig1.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig10.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig11.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig12.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig13.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig14.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig15.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig15.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig2.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig3.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig6.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig7.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig8.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/if-else/fig9.png b/docs-teststudiodev/features/logical-steps/images/if-else/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/loop/fig6.png b/docs-teststudiodev/features/logical-steps/images/loop/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig1.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig10.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig11.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig12.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig13.jpg b/docs-teststudiodev/features/logical-steps/images/while-loop/fig13.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig14.jpg b/docs-teststudiodev/features/logical-steps/images/while-loop/fig14.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig2.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig3.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig4.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig7.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig8.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/images/while-loop/fig9.png b/docs-teststudiodev/features/logical-steps/images/while-loop/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/logical-steps/loop.md b/docs-teststudiodev/features/logical-steps/loop.md
index 9ea18d79..7fae2d61 100644
--- a/docs-teststudiodev/features/logical-steps/loop.md
+++ b/docs-teststudiodev/features/logical-steps/loop.md
@@ -10,34 +10,29 @@ position: 1
 
 Walk--through of creating a loop process.
 
-1.&nbsp; Create a Web Test and click **Record**.
+1. Create a Web Test and click **Record**.
 
-2.&nbsp; Navigate to <a href="http://www.random.org/integers/" target="_blank">www.random.org/integers</a>.
+2. Navigate to <a href="http://www.random.org/integers/" target="_blank">www.random.org/integers</a>.
 
-3.&nbsp; Click Get Numbers. 
+3. Click Get Numbers. 
 
-4.&nbsp; Click Again.
+4. Click Again.
 
-![Random][1]
+    ![Random](images/fig1.png)
 
-5.&nbsp; Pause recording and minimize the browser.
+5. Pause recording and minimize the browser.
 
-6.&nbsp; Choose **Conditions** in the <a href="/features/recorder/step-builder">**Step Builder**</a> and add **loop** step.
+6. Choose **Conditions** in the <a href="/features/recorder/step-builder">**Step Builder**</a> and add **loop** step.
 
-![VS Plugin][7]
+    ![VS Plugin](images/fig7.png)
 
-7.&nbsp; Set the *Count* of the Loop step to 5.
+7. Set the *Count* of the Loop step to 5.
 
-![Loop step count][4]
+    ![Loop step count](images/fig4.png)
 
-8.&nbsp; Drag the second Click Submit step into the *LOOP* step.
+8. Drag the second Click Submit step into the *LOOP* step.
 
-![Drag Submit][5]
+    ![Drag Submit](images/fig5.png)
 
-9.&nbsp; Save and Execute. After the initial set of integers is generated, the process is repeated 5 times.
+9. Save and Execute. After the initial set of integers is generated, the process is repeated 5 times.
 
-[1]: images/loop/fig1.png
-[4]: images/loop/fig4.png
-[5]: images/loop/fig5.png
-[6]: images/loop/fig6.png
-[7]: images/loop/fig7.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/logical-steps/while-loop.md b/docs-teststudiodev/features/logical-steps/while-loop.md
index 5cc5381b..756bf689 100644
--- a/docs-teststudiodev/features/logical-steps/while-loop.md
+++ b/docs-teststudiodev/features/logical-steps/while-loop.md
@@ -10,79 +10,68 @@ position: 1
 
 Walk--through of <a href="/features/logical-steps/while-loop#Build-a-While-loop">Do...While Statement process</a> and <a href="/features/logical-steps/while-loop#Execution-Status">execution status overview</a>.
 
-##Build a While loop
+## Build a While loop
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to www.random.org.
+2. Navigate to www.random.org.
 
-3.&nbsp; Set the Min field to 1 and the Max field to 10.
+3. Set the Min field to 1 and the Max field to 10.
 
-4.&nbsp; Click Generate.
+4. Click Generate.
 
-![Random][1]
+![Random](images/while-loop/fig1.png)
 
-5.&nbsp; Enable hover over highlighting and hover over the *Result* box.
+5. Enable hover over highlighting and hover over the *Result* box.
 
-6.&nbsp; Click **Build Step**.
+6. Click **Build Step**.
 
-![Build Verification][2]
+![Build Verification](images/while-loop/fig2.png)
 
-7.&nbsp; Choose **Content** under **Verifications** in the <a href="/features/recorder/step-builder">**Step Builder**</a>.
+7. Choose **Content** under **Verifications** in the <a href="/features/recorder/step-builder">**Step Builder**</a>.
 
 - Set the first drop-down to **InnerText**.
 - Set the second drop-down to **NotContain**.
 - Click **Add Step**.
 
-![Content][3]
+![Content](images/while-loop/fig3.png)
 
-8.&nbsp; Disable hover over highlighting and minimize the browser.
+8. Disable hover over highlighting and minimize the browser.
 
-9.&nbsp; Choose **Conditions** in the **Step Builder** and add **while...loop** step. 
+9. Choose **Conditions** in the **Step Builder** and add **while...loop** step. 
 
-![VS Plugin][12]
+![VS Plugin](images/while-loop/fig12.png)
 
-10.&nbsp; Choose the verification we've already added from the dropdown of the While step.
+10. Choose the verification we've already added from the dropdown of the While step.
 
-![Choose Verification][7]
+![Choose Verification](images/while-loop/fig7.png)
 
-11.&nbsp; Uncheck/Delete the verification step so it will not be executed (We have this verification already added in the while step)
+11. Uncheck/Delete the verification step so it will not be executed (We have this verification already added in the while step)
 
-![Uncheck Verification][8]
+![Uncheck Verification](images/while-loop/fig8.png)
 
-12.&nbsp; Drag the Click Generate Button step into the WHILE step.
+12. Drag the Click Generate Button step into the WHILE step.
 
-![Drag into While Step][9]
+![Drag into While Step](images/while-loop/fig9.png)
 
-13.&nbsp; Add an <a href="/features/custom-steps/execution-delay" target="_blank">Execution Delay</a> step from the More drop-down in the Add ribbon. Set it to 20 milliseconds.
+13. Add an <a href="/features/custom-steps/execution-delay" target="_blank">Execution Delay</a> step from the More drop-down in the Add ribbon. Set it to 20 milliseconds.
 
-14.&nbsp; Drag the *Execution Delay* step into the *WHILE* step.
+14. Drag the *Execution Delay* step into the *WHILE* step.
 
-![Drag Execution Step][10]
+![Drag Execution Step](images/while-loop/fig10.png)
 
 ## Execution Status
 
-15.&nbsp; Click Save and Execute. The test will continue to generate a random number between 1 and 10 until it generates the number referenced in the Verify step (4 in this example). 
+15. Click Save and Execute. The test will continue to generate a random number between 1 and 10 until it generates the number referenced in the Verify step (4 in this example). 
 
 The **While step** will be always marked as 'Passed' since it is always executed - the condition is to be evaluated. Depending on whether the condition evaluation is true or false the test will either execute the **while branch ** steps or skip and show them as 'Not Run'. 
 
 An execution status example when the while loop is executed few times and the steps in the while loop are executed at least once. 
 
-![While condition is evaluated at least once as true][13]
+![While condition is evaluated at least once as true](images/while-loop/fig13.jpg)
 
 An execution status example when the while condition is false and the steps in the while loop are not run at all. 
 
-![While condition is evaluated at least once as false][14]
-
-[1]: images/while-loop/fig1.png
-[2]: images/while-loop/fig2.png
-[3]: images/while-loop/fig3.png
-[4]: images/while-loop/fig4.png
-[7]: images/while-loop/fig7.png
-[8]: images/while-loop/fig8.png
-[9]: images/while-loop/fig9.png
-[10]: images/while-loop/fig10.png
-[11]: images/while-loop/fig11.png
-[12]: images/while-loop/fig12.png
-[13]: images/while-loop/fig13.jpg
-[14]: images/while-loop/fig14.jpg
+![While condition is evaluated at least once as false](images/while-loop/fig14.jpg)
+
+
diff --git a/docs-teststudiodev/features/project-settings/images/analytics/fig1.png b/docs-teststudiodev/features/project-settings/images/analytics/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/browsers/fig1.png b/docs-teststudiodev/features/project-settings/images/browsers/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/browsers/fig2.png b/docs-teststudiodev/features/project-settings/images/browsers/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/browsers/fig3.png b/docs-teststudiodev/features/project-settings/images/browsers/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/browsers/fig4.png b/docs-teststudiodev/features/project-settings/images/browsers/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/browsers/fig5.png b/docs-teststudiodev/features/project-settings/images/browsers/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/element-images/fig1.png b/docs-teststudiodev/features/project-settings/images/element-images/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/emulated-device/fig1.png b/docs-teststudiodev/features/project-settings/images/emulated-device/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/find-logic/fig1.png b/docs-teststudiodev/features/project-settings/images/find-logic/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/find-logic/fig2.png b/docs-teststudiodev/features/project-settings/images/find-logic/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/find-logic/fig3.png b/docs-teststudiodev/features/project-settings/images/find-logic/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/general/fig1.png b/docs-teststudiodev/features/project-settings/images/general/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/general/fig2.png b/docs-teststudiodev/features/project-settings/images/general/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/installation/fig1.png b/docs-teststudiodev/features/project-settings/images/installation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/logging/fig1.png b/docs-teststudiodev/features/project-settings/images/logging/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/overview/fig1.png b/docs-teststudiodev/features/project-settings/images/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/overview/fig2.png b/docs-teststudiodev/features/project-settings/images/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/recording-options/fig1.png b/docs-teststudiodev/features/project-settings/images/recording-options/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/recording-options/fig2.png b/docs-teststudiodev/features/project-settings/images/recording-options/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/recording-options/fig3.png b/docs-teststudiodev/features/project-settings/images/recording-options/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/script-options/fig1.png b/docs-teststudiodev/features/project-settings/images/script-options/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/theme/fig1.png b/docs-teststudiodev/features/project-settings/images/theme/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/translators/fig1.png b/docs-teststudiodev/features/project-settings/images/translators/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/translators/fig2.png b/docs-teststudiodev/features/project-settings/images/translators/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/translators/fig3.png b/docs-teststudiodev/features/project-settings/images/translators/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/images/updates/fig1.png b/docs-teststudiodev/features/project-settings/images/updates/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/project-settings/translators.md b/docs-teststudiodev/features/project-settings/translators.md
index be7f93a1..54c9561c 100644
--- a/docs-teststudiodev/features/project-settings/translators.md
+++ b/docs-teststudiodev/features/project-settings/translators.md
@@ -26,656 +26,159 @@ As Quality Assurance Engineer you often don't know what type and version of UI c
 
 In the below grid you can find the versions of the supported UI components matching the translators versions from the list.
 
-<p id="Blazor">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Telerik UI for Blazor<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2.27.0</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">3.0.0</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">3.1.0</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">3.3.0</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">3.4.0</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">3.6.0</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-
-<p id="asp.net ajax">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Telerik UI for ASP.NET AJAX<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2021.3.914</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">2022.1.119</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.1.302</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">2022.2.511</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.2.622</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">2022.3.913</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-
-<p id="jQuery">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Kendo UI for jQuery<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2021.3.914</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">2022.1.119</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.1.301</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">2022.2.510</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.2.621</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">2022.3.913</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-
-
-<script type="text/javascript">
-        function showHideRow(row) {
-            $("#" + row).toggle();
-            $('#expand'+row[row.length-1]).text(function (i, oldText) {
-        return $.trim(oldText) == 'Click to expand the list of translators' ? 'Collapse' : 'Click to expand the list of translators';
-		});
-        }
-</script>
-
-<style>
-    #Angular .hidden_row {
-            display: none;
-        }
-</style>
-
-<table class="Tbl k-table" id="Angular">
-    <colgroup>
-        <col width="30%" />
-        <col width="70%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="2" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Kendo UI for Angular</td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr onclick="showHideRow('hidden_row1');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R32021</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand1">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row1" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                            <col width="34%" />
-                            <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">5.1.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>                        
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">7.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">1.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">7.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">5.1.1</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRow('hidden_row2');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R12022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand2">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row2" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">3.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRow('hidden_row3');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R12022SP1</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand3">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row3" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">7.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">6.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.7</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">3.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.5.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.7</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.5.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.2</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRow('hidden_row4');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R22022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand4">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row4" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRow('hidden_row5');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R22022SP1</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand5">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row5" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.2</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRow('hidden_row6');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R32022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand6">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row6" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.3.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">10.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.5</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">10.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-    </tbody>
-</table>
+## Telerik UI for Blazor
+
+| Release    | Version  |
+|------------|----------|
+| R32021     | 2.27.0   |
+| R12022     | 3.0.0    |
+| R12022SP1  | 3.1.0    |
+| R22022     | 3.3.0    |
+| R22022SP1  | 3.4.0    |
+| R32022     | 3.6.0    |
+| R12023     | 4.0.0    |
+| R12023SP1  | 4.1.0    |
+| R22023     | 4.3.0    |
+| R32023     | 4.6.0    |
+| R22024     | 6.0.0    |
+
+## Telerik UI for ASP.NET AJAX
+
+| Release    | Version      |
+|------------|--------------|
+| R32021     | 2021.3.914   |
+| R12022     | 2022.1.119   |
+| R12022SP1  | 2022.1.302   |
+| R22022     | 2022.2.511   |
+| R22022SP1  | 2022.2.622   |
+| R32022     | 2022.3.913   |
+| R12023     | 2023.1.117   |
+| R12023SP1  | 2023.1.314   |
+| R22023     | 2023.2.606   |
+| R32023     | 2023.3.1010  |
+| R22024     | 2024.2.513   |
+
+## Kendo UI for jQuery
+
+| Release    | Version      |
+|------------|--------------|
+| R32021     | 2021.3.914   |
+| R12022     | 2022.1.119   |
+| R12022SP1  | 2022.1.301   |
+| R22022     | 2022.2.510   |
+| R22022SP1  | 2022.2.621   |
+| R32022     | 2022.3.913   |
+| R12023     | 2023.1.117   |
+| R12023SP1  | 2023.1.314   |
+| R22023     | 2023.2.606   |
+| R32023     | 2023.3.1010  |
+| R22024     | 2024.2.514   |
+
+## Kendo UI for Angular
+
+| Release R32021           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 6.3.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 5.1.1             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 5.4.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 7.4.0             |
+| KendoAngularPager        | kendo-angular-pager        | 1.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.3.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 7.4.0             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.3.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 5.1.1             |
+
+| Release R12022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 7.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 6.0.0             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 6.0.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 8.0.0             |
+| KendoAngularPager        | kendo-angular-pager        | 3.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.4.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 8.0.0             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.4.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 6.0.0             |
+
+| Release R12022SP1        |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularButton       | kendo-angular-buttons      | 7.0.3             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularDialog       | kendo-angular-dialog       | 6.0.2             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularGrid         | kendo-angular-grid         | 6.1.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 8.0.7             |
+| KendoAngularPager        | kendo-angular-pager        | 3.0.2             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.5.1             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 8.0.7             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.5.1             |
+| KendoAngularWindow       | kendo-angular-dialog       | 6.0.2             |
+
+| Release R22022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.0.0             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.0.1             |
+| KendoAngularInputs       | kendo-angular-inputs       | 9.0.1             |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.0.1             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 9.0.1             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.0.1             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.0.0             |
+
+| Release R22022SP1        |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.1.2             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.2.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 9.0.3             |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.1.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 9.0.3             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.1.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.1.2             |
+
+| Release R32022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.1.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.1.3             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.3.1             |
+| KendoAngularInputs       | kendo-angular-inputs       | 10.0.0            |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.5             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.1.3             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 10.0.0            |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.1.3             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.1.3             |
+
+| Release    | Version  |
+|------------|----------|
+| R12023     | 11.0.0   |
+| R12023SP1  | 11.4.0   |
+| R22023     | 13.0.0   |
+| R32023     | 14.0.0   |
+| R22024     | 16.0.0   |
 
 ## Available Translators
 
diff --git a/docs-teststudiodev/features/recorder/images/dom-add-element.png b/docs-teststudiodev/features/recorder/images/dom-add-element.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/dom-context-menu.png b/docs-teststudiodev/features/recorder/images/dom-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/dom-explorer.png b/docs-teststudiodev/features/recorder/images/dom-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/dom-search-elements-regex.png b/docs-teststudiodev/features/recorder/images/dom-search-elements-regex.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/dom-search-elements.png b/docs-teststudiodev/features/recorder/images/dom-search-elements.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/dom-toolbar.png b/docs-teststudiodev/features/recorder/images/dom-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/elements-menu.png b/docs-teststudiodev/features/recorder/images/elements-menu.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig10.png b/docs-teststudiodev/features/recorder/images/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig11-lock.png b/docs-teststudiodev/features/recorder/images/fig11-lock.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig11-unlock.png b/docs-teststudiodev/features/recorder/images/fig11-unlock.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig12-refresh.png b/docs-teststudiodev/features/recorder/images/fig12-refresh.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig2.png b/docs-teststudiodev/features/recorder/images/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig3.png b/docs-teststudiodev/features/recorder/images/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig4.png b/docs-teststudiodev/features/recorder/images/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig5.png b/docs-teststudiodev/features/recorder/images/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig6.png b/docs-teststudiodev/features/recorder/images/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig7.png b/docs-teststudiodev/features/recorder/images/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig8.png b/docs-teststudiodev/features/recorder/images/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/fig9.png b/docs-teststudiodev/features/recorder/images/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/js-events.png b/docs-teststudiodev/features/recorder/images/js-events.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/mouse-actions.png b/docs-teststudiodev/features/recorder/images/mouse-actions.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quick-steps.png b/docs-teststudiodev/features/recorder/images/quick-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/add-new-test-wizard.png b/docs-teststudiodev/features/recorder/images/quickstart/add-new-test-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/add-new-test.png b/docs-teststudiodev/features/recorder/images/quickstart/add-new-test.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/attach-to-existing.png b/docs-teststudiodev/features/recorder/images/quickstart/attach-to-existing.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/configure-desktop-wizard.png b/docs-teststudiodev/features/recorder/images/quickstart/configure-desktop-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/configure-desktop.png b/docs-teststudiodev/features/recorder/images/quickstart/configure-desktop.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/configure-wpf-wizard.png b/docs-teststudiodev/features/recorder/images/quickstart/configure-wpf-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/configure-wpf.png b/docs-teststudiodev/features/recorder/images/quickstart/configure-wpf.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/create-project.png b/docs-teststudiodev/features/recorder/images/quickstart/create-project.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/elements-explorer.png b/docs-teststudiodev/features/recorder/images/quickstart/elements-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/enter-url.png b/docs-teststudiodev/features/recorder/images/quickstart/enter-url.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/execute-test-button.png b/docs-teststudiodev/features/recorder/images/quickstart/execute-test-button.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/failed-step-details.png b/docs-teststudiodev/features/recorder/images/quickstart/failed-step-details.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/failed-step.png b/docs-teststudiodev/features/recorder/images/quickstart/failed-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/name-of-project.png b/docs-teststudiodev/features/recorder/images/quickstart/name-of-project.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-log-copy.png b/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-log-copy.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-log.png b/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-log.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-overall-results.png b/docs-teststudiodev/features/recorder/images/quickstart/quick-execution-overall-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/record-button.png b/docs-teststudiodev/features/recorder/images/quickstart/record-button.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/recorded-steps.png b/docs-teststudiodev/features/recorder/images/quickstart/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-failed-results.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-failed-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-group-tests.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-group-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-results.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-run-selected-tests.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-run-selected-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-run-tests.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl-run-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl.png b/docs-teststudiodev/features/recorder/images/quickstart/vs-test-expl.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/quickstart/web-test-by-default.png b/docs-teststudiodev/features/recorder/images/quickstart/web-test-by-default.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/recording-toolbar.png b/docs-teststudiodev/features/recorder/images/recording-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/scroll-actions.png b/docs-teststudiodev/features/recorder/images/scroll-actions.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/show-step-builder-from-menu.png b/docs-teststudiodev/features/recorder/images/show-step-builder-from-menu.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/show-step-builder.png b/docs-teststudiodev/features/recorder/images/show-step-builder.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/step-builder-recorder.png b/docs-teststudiodev/features/recorder/images/step-builder-recorder.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/step-builder-test-level.png b/docs-teststudiodev/features/recorder/images/step-builder-test-level.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/translators-hover-over.png b/docs-teststudiodev/features/recorder/images/translators-hover-over.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/images/translators-quick-steps.png b/docs-teststudiodev/features/recorder/images/translators-quick-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/drag-and-drop.md b/docs-teststudiodev/features/recorder/mouse-actions/drag-and-drop.md
index af17b0dc..2afe84b2 100644
--- a/docs-teststudiodev/features/recorder/mouse-actions/drag-and-drop.md
+++ b/docs-teststudiodev/features/recorder/mouse-actions/drag-and-drop.md
@@ -7,25 +7,25 @@ position: 0
 ---
 # Drag and Drop
 
-1.&nbsp; Start <a href="/features/recorder/record-test" target="_blank">recording a test</a>.
+1. Start <a href="/features/recorder/record-test" target="_blank">recording a test</a>.
 
-2.&nbsp; Enable Hover Over Highlighting from the Recording Toolbar. When the mouse pauses over a highlighted element in the recording surface the context menu with multiple options.
+2. Enable Hover Over Highlighting from the Recording Toolbar. When the mouse pauses over a highlighted element in the recording surface the context menu with multiple options.
 
-3.&nbsp; Highlight an element you want to drag and drop and click **Build Step**.
+3. Highlight an element you want to drag and drop and click **Build Step**.
 
-![Build Step](images/build-step.png)
+    ![Build Step](images/build-step.png)
 
-4.&nbsp; From Mouse Actions select **DragDrop** and click **Pick** button.
+4. From Mouse Actions select **DragDrop** and click **Pick** button.
 
-![Pick Target Element](images/pick-target.png)
+    ![Pick Target Element](images/pick-target.png)
 
-5.&nbsp; Highlight and select the target element where you want to drop the element.
+5. Highlight and select the target element where you want to drop the element.
 
-![Select Target](images/select-target.png)
+    ![Select Target](images/select-target.png)
 
-6.&nbsp; Choose **Element Center** from the **Location** drop down to drop the element in the center of the target element and click **Add Step**. The Drag&Drop step is created in Test Studio.
+6. Choose **Element Center** from the **Location** drop down to drop the element in the center of the target element and click **Add Step**. The Drag&Drop step is created in Test Studio.
 
-![Add Step](images/add-step.png)
+    ![Add Step](images/add-step.png)
 
 ## Drag and Drop to a specific location
 
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/add-step.png b/docs-teststudiodev/features/recorder/mouse-actions/images/add-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/build-step.png b/docs-teststudiodev/features/recorder/mouse-actions/images/build-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/choose-mouse-click.png b/docs-teststudiodev/features/recorder/mouse-actions/images/choose-mouse-click.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/create-step.png b/docs-teststudiodev/features/recorder/mouse-actions/images/create-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/pick-target.png b/docs-teststudiodev/features/recorder/mouse-actions/images/pick-target.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/select-actual-spec-point.png b/docs-teststudiodev/features/recorder/mouse-actions/images/select-actual-spec-point.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/select-point.png b/docs-teststudiodev/features/recorder/mouse-actions/images/select-point.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/select-specific-point.png b/docs-teststudiodev/features/recorder/mouse-actions/images/select-specific-point.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/select-target.png b/docs-teststudiodev/features/recorder/mouse-actions/images/select-target.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/specific-coordinates.png b/docs-teststudiodev/features/recorder/mouse-actions/images/specific-coordinates.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/specific-point.png b/docs-teststudiodev/features/recorder/mouse-actions/images/specific-point.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/images/specify-coordinates.png b/docs-teststudiodev/features/recorder/mouse-actions/images/specify-coordinates.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/mouse-actions/relative-mouse-actions.md b/docs-teststudiodev/features/recorder/mouse-actions/relative-mouse-actions.md
index c471ba61..7d6d8a5e 100644
--- a/docs-teststudiodev/features/recorder/mouse-actions/relative-mouse-actions.md
+++ b/docs-teststudiodev/features/recorder/mouse-actions/relative-mouse-actions.md
@@ -7,28 +7,28 @@ position: 1
 ---
 # Specific location
 
-1.&nbsp; Start <a href="/features/recorder/record-test" target="_blank">recording a test</a>.
+1. Start <a href="/features/recorder/record-test" target="_blank">recording a test</a>.
 
-2.&nbsp; Enable Hover Over Highlighting from the Recording Toolbar. When the mouse pauses over a highlighted element in the recording surface the context menu with multiple options.
+2. Enable Hover Over Highlighting from the Recording Toolbar. When the mouse pauses over a highlighted element in the recording surface the context menu with multiple options.
 
-3.&nbsp; Highlight an element and click **Build Step**.
+3. Highlight an element and click **Build Step**.
 
-![Build Step](images/create-step.png)
+    ![Build Step](images/create-step.png)
 
-4.&nbsp; Select the mouse click you want to perform.
+4. Select the mouse click you want to perform.
 
-![Mouse click](images/choose-mouse-click.png)
+    ![Mouse click](images/choose-mouse-click.png)
 
-> __Note:__ If you leave Element Center option the click will be performed in the center of the element.
+    > __Note:__ If you leave Element Center option the click will be performed in the center of the element.
 
-5.&nbsp; Choose **Specific Point** from the Location drop down.
+5. Choose **Specific Point** from the Location drop down.
 
-![Specific point](images/select-specific-point.png)
+    ![Specific point](images/select-specific-point.png)
 
-6.&nbsp; Select against which part of the element will be the specific point calculated from the grid (1).
+6. Select against which part of the element will be the specific point calculated from the grid (1).
 
-![Tetris](images/select-actual-spec-point.png)
+    ![Tetris](images/select-actual-spec-point.png)
 
-7.&nbsp; Drag the circle to the point where you want to click (the coordinates will be calculated automatically) or type the coordinates manually and click Add Step.
+7. Drag the circle to the point where you want to click (the coordinates will be calculated automatically) or type the coordinates manually and click Add Step.
 
-![Coordinates](images/specify-coordinates.png)
\ No newline at end of file
+    ![Coordinates](images/specify-coordinates.png)
\ No newline at end of file
diff --git a/docs-teststudiodev/features/recorder/recording-toolbar.md b/docs-teststudiodev/features/recorder/recording-toolbar.md
index fa017f91..5c1e1ced 100644
--- a/docs-teststudiodev/features/recorder/recording-toolbar.md
+++ b/docs-teststudiodev/features/recorder/recording-toolbar.md
@@ -21,44 +21,48 @@ Below are listed its features related to the <a href="/features/recorder/dom-exp
 
 <table id="no-table" >
 	<tr cellspacing="10">
-		<td cellspacing="1">![Enable/Disable Hover Over Highlighting](images/fig2.png)<br></td>
-		<td><a href="/features/recorder/highlighting-elements" target="_blank">**Enable/Disable Hover Over Highlighting**</a> (Use "**Pause/Break**" on your keyboard to toggle the highlighting on/off)</td>
+		<td cellspacing="1">
+			<img src="images/fig2.png" alt="Enable/Disable Hover Over Highlighting" /><br>
+		</td>
+		<td><a href="/features/recorder/highlighting-elements" target="_blank">Enable/Disable Hover Over Highlighting</a> (Use "Pause/Break" on your keyboard to toggle the highlighting on/off)
+		</td>
 	</tr>
 	<tr cellspacing="10">
-		<td>![Pause Recording](images/fig3.png)</td>
-		<td>**Pause Recording** (Use "**Print Screen**" on your keyboard to pause recording)</td>
+		<td><img src="images/fig3.png" alt="Pause Recording" /></td>
+		<td>"Pause Recording" (Use "Print Screen" on your keyboard to pause recording)</td>
 	</tr>
 	<tr>
-		<td>![Start Recording](images/fig4.png)</td>
-		<td>**Start Recording** (Use "**Print Screen**" on your keyboard to resume recording)</td>
+		<td><img src="images/fig4.png" alt="Start Recording" /></td>
+		
+<td>"Start Recording" (Use "Print Screen" on your keyboard to resume recording)</td>
 	</tr>
 	<tr>
-		<td>![Reconnect Recorder](images/fig5.png)</td>
-		<td>**Reconnect Recorder** - restores communication between Test Studio and the recording browser window or WPF app, if necessary</td>
+		<td><img src="images/fig5.png" alt="Reconnect Recorder" /></td>
+	<td>"Reconnect Recorder" - restores communication between Test Studio and the recording browser window or WPF app, if necessary</td>
 	</tr>
 	<tr>
-		<td>![Navigation panel](images/fig6.png)</td>
-		<td>**Navigation panel** - during the recording session type URL to navigate to or refresh the browser</td>
+		<td><img src="images/fig6.png" alt="Navigation panel" /></td>
+		<td>"Navigation panel" - during the recording session type URL to navigate to or refresh the browser</td>
 	</tr>
 	<tr>
-		<td>![Dock/Undock](images/fig7.png) / ![Dock/Undock](images/fig8.png)</td>
-		<td>**Undock/Dock** - undock or dock back the recorder</td>
+		<td><img src="images/fig7.png" alt="Dock/Undock" /> / <img src="images/fig8.png" alt="Dock/Undock" /></td>
+		<td>"Undock/Dock" - undock or dock back the recorder</td>
 	</tr>
 	<tr>
-		<td>![Add to elements repository](images/fig9.png)</td>
-		<td>**Add To Elements Repository** - add a single or multiple elements to the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a>)</td>
+		<td><img src="images/fig9.png" alt="Add to elements repository" /></td>
+		<td>"Add To Elements Repository" - add a single or multiple elements to the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a>)</td>
 	</tr>
 		<tr>
-		<td>![Manual Refresh of the DOM][12]</td>
-		<td>**Manual Refresh of the DOM** - Used when auto-refresh is paused and the DOM tree is changed</td>
+		<td><img src="images/fig12-refresh.png" alt="Manual Refresh of the DOM" /></td>
+		<td>"Manual Refresh of the DOM" - Used when auto-refresh is paused and the DOM tree is changed</td>
 	</tr>
 	<tr>
-		<td>![Freeze DOM tree][11] / ![Unfreeze DOM tree][11a]</td>
-		<td>**Freeze/Unfreeze DOM tree** - Pause/Resume the DOM tree auto-refresh option</td>
+		<td><img src="images/fig11-lock.png" alt="Freeze DOM tree" /> / <img src="images/fig11-unlock.png" alt="Unfreeze DOM tree" /></td>
+		<td>"Freeze/Unfreeze DOM tree" - Pause/Resume the DOM tree auto-refresh option</td>
 	</tr>
 	<tr>
-		<td>![Elements tree/tag view](images/fig10.png)</td>
-		<td>**Elements Tree/Tag View** - whether to display the elements as tree view or tag view</td>
+		<td><img src="images/fig10.png" alt="Elements tree/tag view" /></td>
+		<td>"Elements Tree/Tag View" - whether to display the elements as tree view or tag view</td>
 	</tr>
 <table>
 
@@ -76,6 +80,3 @@ __See Also:__
 
 * <a href="/features/recorder/verifications/introduction" target="_blank">Verifications</a>
 
-[11]: images/fig11-lock.png
-[11a]: images/fig11-unlock.png
-[12]: images/fig12-refresh.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/dialog-handler-updater.md b/docs-teststudiodev/features/recorder/specific-recording-scenario/dialog-handler-updater.md
index fabaf453..fb02113d 100644
--- a/docs-teststudiodev/features/recorder/specific-recording-scenario/dialog-handler-updater.md
+++ b/docs-teststudiodev/features/recorder/specific-recording-scenario/dialog-handler-updater.md
@@ -2,7 +2,7 @@
 title: Dialog Handler Updater
 page_title: Dialog Handler Updater - Test Studio Dev Documentation
 description: How to update the Dialog Handlers.
-slug: features/dialogs
+slug: features/dialog-handler-updater
 position: 0
 ---
 # Dialog Handler Updater
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/alert-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/alert-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-alert-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-alert-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-confirm-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-confirm-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-prompt-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/browser-prompt-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/close-popup.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/close-popup.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/confirm-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/confirm-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/connect-to-popup.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/connect-to-popup.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig1.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig2.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig3.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dialog-handler-updater/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/download-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/download-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dynamic-frame.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/dynamic-frame.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/frame-node.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/frame-node.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/frame-properties.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/frame-properties.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/modal-popup-connect-step.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/modal-popup-connect-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/modal-popup.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/modal-popup.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/prompt-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/prompt-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/upload-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/upload-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/win-32-download-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/win-32-download-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/specific-recording-scenario/images/win-32-upload-dialog.png b/docs-teststudiodev/features/recorder/specific-recording-scenario/images/win-32-upload-dialog.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/advanced-verification.md b/docs-teststudiodev/features/recorder/verifications/advanced-verification.md
index 826c40f4..c2870ab8 100644
--- a/docs-teststudiodev/features/recorder/verifications/advanced-verification.md
+++ b/docs-teststudiodev/features/recorder/verifications/advanced-verification.md
@@ -9,23 +9,23 @@ position: 2
 
 An advanced verification allows you to interactively build verification rules and validate them against a live web document or WPF application. In order to create custom verification you need to locate the target element in the DOM tree and use the <a href="/features/recorder/step-builder" target="_blank">Step Builder</a> and its _Verification_ section.
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
+2. Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
 
-3.&nbsp; Enter _Telerik_ in the search box and click the __Search__ button.
+3. Enter _Telerik_ in the search box and click the __Search__ button.
 
-4.&nbsp; Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
+4. Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
 
-5.&nbsp; Choose _Build Step..._ from the context menu which will locate the element in the DOM tree and display the available options in the Step Builder to add a custom step. 
+5. Choose _Build Step..._ from the context menu which will locate the element in the DOM tree and display the available options in the Step Builder to add a custom step. 
 
-![Locate Element](images/highlight-element.png)
+    ![Locate Element](images/highlight-element.png)
 
-6.&nbsp; Select the **Verifications** tab in the Step Builder.
+6. Select the **Verifications** tab in the Step Builder.
 
-![Verifications](images/verification-section.png)
+    ![Verifications](images/verification-section.png)
 
-7.&nbsp; Start by selecting a type of available Verifications for the selected element:
+7. Start by selecting a type of available Verifications for the selected element:
 
 - IsVisible
 - Content
@@ -34,28 +34,28 @@ An advanced verification allows you to interactively build verification rules an
 - IsEnabled
 - <a href="/features/recorder/verifications/image-verification" target="_blank">Image</a>
 
-![Available verifications](images/available-verifications.png)
+    ![Available verifications](images/available-verifications.png)
 
-When crafting verifications, content is dynamically built against the currently selected element. As selections are made, default values are populated according to values the element contains.
-For example, choose Content as the verification type and three menu options appear. 
+    When crafting verifications, content is dynamically built against the currently selected element. As selections are made, default values are populated according to values the element contains.
+    For example, choose Content as the verification type and three menu options appear. 
 
-![Content](images/verify-content-options.png)
+    ![Content](images/verify-content-options.png)
 
-Click on the drop downs for each option to see a list of possible values.
+    Click on the drop downs for each option to see a list of possible values.
 
-<table id="no-table">
-<tr>
-<td>![Content Type](images/content-type.png)</td>
-<td>![Match Type](images/match-type.png)</td>
-</tr>
-<table>
+    <table id="no-table">
+    <tr>
+    <td><img src="images/content-type.png" alt="Content Type" /></td>
+    <td><img src="images/match-type.png" alt="Match Type" /></td>
+    </tr>
+    <table>
 
-8.&nbsp; Once finished building the verification(s), click **Add Step** to add it as a step to the current test.
+8. Once finished building the verification(s), click **Add Step** to add it as a step to the current test.
 
-![Add Step](images/add-step.png)
+    ![Add Step](images/add-step.png)
 
-The newly created verification appears in the test:
+    The newly created verification appears in the test:
 
-![Test Steps](images/verify-advanced-step.png)
+    ![Test Steps](images/verify-advanced-step.png)
 
 > We recommend against using the Content Markup validation types. They are fragile in the face of minor page changes, and different browsers may reorder the element attributes making them unreliable. For more information please see our Automated Testing blog entry on <a href="http://blogs.telerik.com/jimholmes/posts/11-08-23/understanding-validation-content-element-types.aspx" target="_blank">**Understanding Validation Content Element Types**</a>.
diff --git a/docs-teststudiodev/features/recorder/verifications/extraction.md b/docs-teststudiodev/features/recorder/verifications/extraction.md
index ae7a92bc..c0930162 100644
--- a/docs-teststudiodev/features/recorder/verifications/extraction.md
+++ b/docs-teststudiodev/features/recorder/verifications/extraction.md
@@ -11,57 +11,57 @@ An _Extraction_ step can be created in the same manner as <a href="/features/rec
 
 This example is against a <a href="http://www.wordgenerator.net/random-word-generator.php" target="_blank">random word generator site</a>.
 
-1.&nbsp; Enable highlighting and hover over the target element, choose **Quick Steps > Extract - text contains** entry. 
+1. Enable highlighting and hover over the target element, choose **Quick Steps > Extract - text contains** entry. 
 
-![Word Generator](images/highlight-element-to-extract.png)
+    ![Word Generator](images/highlight-element-to-extract.png)
 
-2.&nbsp; An Extraction step is added to the test.
+2. An Extraction step is added to the test.
 
-3.&nbsp; Pause recording, double click that step, and change the DataBindVariableName. In this example I renamed it to *randomWord*.
+3. Pause recording, double click that step, and change the DataBindVariableName. In this example I renamed it to *randomWord*.
 
-![Extracted Step Added](images/extraction-step.png)
+    ![Extracted Step Added](images/extraction-step.png)
 
-4.&nbsp; Resume recording and navigate to www.bing.com from the Navigation pane in the <a href="/features/recorder/recording-toolbar" target="_blank">Recording toolbar</a>.
+4. Resume recording and navigate to www.bing.com from the Navigation pane in the <a href="/features/recorder/recording-toolbar" target="_blank">Recording toolbar</a>.
 
-5.&nbsp; Enter any word into the search box and click **Submit**.
+5. Enter any word into the search box and click **Submit**.
 
-6.&nbsp; Close the browser to stop recording.
+6. Close the browser to stop recording.
 
-![Recorded Test Steps](images/recorded-steps.png)
+    ![Recorded Test Steps](images/recorded-steps.png)
 
-7.&nbsp; Select the step that enters a word for the search engine (step 4 in this example).
+7. Select the step that enters a word for the search engine (step 4 in this example).
 
-8.&nbsp; Click the **Bindings** drop-down in the <a href="/features/test-maintenance/test-step-properties" target="_blank">**Step Properties** pane</a>.
+8. Click the **Bindings** drop-down in the <a href="/features/test-maintenance/test-step-properties" target="_blank">**Step Properties** pane</a>.
 
-9.&nbsp; Select the extracted variable from the value drop-down and click **Set**.
+9. Select the extracted variable from the value drop-down and click **Set**.
 
-![Set Extracted Value](images/set-extracted-value.png)
+    ![Set Extracted Value](images/set-extracted-value.png)
 
-10.&nbsp; Save and execute the test.
+10. Save and execute the test.
 
-11.&nbsp; A random word is extracted from the first site and used as the query in a Bing search.
+11. A random word is extracted from the first site and used as the query in a Bing search.
 
-> If you have <a href="/code-in-test/coded-samples/general/extracted-variables-in-code" target="_blank">Set an Extracted Variable in Code</a>, type the variable name in the text box (without the $ notation), click on the brackets and then Set:
+    > If you have <a href="/code-in-test/coded-samples/general/extracted-variables-in-code" target="_blank">Set an Extracted Variable in Code</a>, type the variable name in the text box (without the $ notation), click on the brackets and then Set:
 
-![Extracted variable in code](images/extracted-in-code.png)
+    ![Extracted variable in code](images/extracted-in-code.png)
 
-## Extract an attribute of an element##
+## Extract an attribute of an element
 
-1.&nbsp; Create an <a href="/features/recorder/verifications/advanced-verification" target="_blank">advanced verification</a> for an attribute of an element (e.g. Title).
+1. Create an <a href="/features/recorder/verifications/advanced-verification" target="_blank">advanced verification</a> for an attribute of an element (e.g. Title).
 
-![Advanced verification](images/create-adv-ver.png)
+    ![Advanced verification](images/create-adv-ver.png)
 
 If the element is **hidden** you should select it from the DOM Explorer
 
 ![DOM Selection](images/dom-selection.png)
 
-2.&nbsp; Change the role of the verification step to Extraction.
+2. Change the role of the verification step to Extraction.
 
-![Change the Step Role](images/change-role.png)
+    ![Change the Step Role](images/change-role.png)
 
-3.&nbsp; The step is changed to an extraction one.
+3. The step is changed to an extraction one.
 
-![Extraction](images/changed-to-extraction.png)
+    ![Extraction](images/changed-to-extraction.png)
 
 > __Note!__ Each Verfication/Wait/Extract step could have it role changed between Verification, Wait, and Extraction (if based on text). Right click the step and select from the context menu __Change Role > Set As...__
 
diff --git a/docs-teststudiodev/features/recorder/verifications/image-verification.md b/docs-teststudiodev/features/recorder/verifications/image-verification.md
index 0b6dfefd..2b03c695 100644
--- a/docs-teststudiodev/features/recorder/verifications/image-verification.md
+++ b/docs-teststudiodev/features/recorder/verifications/image-verification.md
@@ -13,60 +13,52 @@ You can build an image verification against specific elements for pixel-by-pixel
 
 There are few things that could ensure more stable and reliable test execution:
 
-&nbsp; &nbsp; ![Green][1] Use Image Verification when you need to verify an exact and static image, such as a logo, button, or icon.
+  ![Green](images/image-verification/fig1.png) Use Image Verification when you need to verify an exact and static image, such as a logo, button, or icon.
 
-&nbsp; &nbsp; ![Red][2] Do not use Image Verification to verify a specific color, an image with text content, or a dynamic slide show.
+  ![Red](images/image-verification/fig2.png) Do not use Image Verification to verify a specific color, an image with text content, or a dynamic slide show.
 
 ## How to record an image verification step
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to the application under test, for example www.Telerik.com.
+2. Navigate to the application under test, for example www.Telerik.com.
 
-3.&nbsp; Enable highlighting from the Recorder.
+3. Enable highlighting from the Recorder.
 
-![Enable Highlighting][3]
+    ![Enable Highlighting](images/image-verification/fig3.png)
 
-4.&nbsp; Hover over the image, for example the Progress Telerik logo in the header, and select **Build Step...** from the context menu.
+4. Hover over the image, for example the Progress Telerik logo in the header, and select **Build Step...** from the context menu.
 
-![Build Step][4]
+    ![Build Step](images/image-verification/fig4.png)
 
-5.&nbsp; In the Recorder click **Verifications > Image**.
+5. In the Recorder click **Verifications > Image**.
 
-![Image][5]
+    ![Image](images/image-verification/fig5.png)
 
-* __Web test__
+    * __Web test__
 
-By default, **Verify Entire Image** is checked and the **Threshold** is set to 90%.
+    By default, **Verify Entire Image** is checked and the **Threshold** is set to 90%.
 
-> We recommend keeping the __Threshold__ around 90%. A setting of 100% equals an exact match and the verification will fail, if it is off by a single pixel.
+    > We recommend keeping the __Threshold__ around 90%. A setting of 100% equals an exact match and the verification will fail, if it is off by a single pixel.
 
-* __WPF test__
+    * __WPF test__
 
-By default, **Verify Entire Image** is checked and the **Tolerance** is set to 1%.
+    By default, **Verify Entire Image** is checked and the **Tolerance** is set to 1%.
 
-> We recommend keeping the __Tolerance__ around 1% to 9%. A setting of 0% equals an exact match and increasing the tolerance means the verification is more forgiving.
+    > We recommend keeping the __Tolerance__ around 1% to 9%. A setting of 0% equals an exact match and increasing the tolerance means the verification is more forgiving.
 
-6.&nbsp; Uncheck **Verify Entire Image** to refine the comparison area. Either enter coordinates or drag the desired selection area within the image.
+6. Uncheck **Verify Entire Image** to refine the comparison area. Either enter coordinates or drag the desired selection area within the image.
 
-![Refine][6]
+    ![Refine](images/image-verification/fig6.png)
 
-7.&nbsp; Click **Add Step** and notice the Verify image step is added to the test.
+7. Click **Add Step** and notice the Verify image step is added to the test.
 
-![Step Added][7]
+    ![Step Added](images/image-verification/fig7.png)
 
 ## Configure the recorded image verification step
 
 You can configure the threshold and scrolling options that will be used during test execution.
 
-![Configure Test Step Options][8]
-
-[1]: /features/recorder/verifications/images/image-verification/fig1.png
-[2]: /features/recorder/verifications/images/image-verification/fig2.png
-[3]: /features/recorder/verifications/images/image-verification/fig3.png
-[4]: /features/recorder/verifications/images/image-verification/fig4.png
-[5]: /features/recorder/verifications/images/image-verification/fig5.png
-[6]: /features/recorder/verifications/images/image-verification/fig6.png
-[7]: /features/recorder/verifications/images/image-verification/fig7.png
-[8]: /features/recorder/verifications/images/image-verification/fig8.png
-[9]: /features/recorder/verifications/images/image-verification/gif9.gif
+![Configure Test Step Options](images/image-verification/fig8.png)
+
+
diff --git a/docs-teststudiodev/features/recorder/verifications/images/TBD-changed-to-extraction.png b/docs-teststudiodev/features/recorder/verifications/images/TBD-changed-to-extraction.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/actual-vs-expected.png b/docs-teststudiodev/features/recorder/verifications/images/actual-vs-expected.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/add-step.png b/docs-teststudiodev/features/recorder/verifications/images/add-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/available-verifications.png b/docs-teststudiodev/features/recorder/verifications/images/available-verifications.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/change-role.png b/docs-teststudiodev/features/recorder/verifications/images/change-role.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/changed-to-extraction.png b/docs-teststudiodev/features/recorder/verifications/images/changed-to-extraction.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/content-type.png b/docs-teststudiodev/features/recorder/verifications/images/content-type.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/create-adv-ver.png b/docs-teststudiodev/features/recorder/verifications/images/create-adv-ver.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/dom-selection.png b/docs-teststudiodev/features/recorder/verifications/images/dom-selection.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/enable-highlighting.png b/docs-teststudiodev/features/recorder/verifications/images/enable-highlighting.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/extracted-in-code.png b/docs-teststudiodev/features/recorder/verifications/images/extracted-in-code.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/extraction-step.png b/docs-teststudiodev/features/recorder/verifications/images/extraction-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/green-circle.png b/docs-teststudiodev/features/recorder/verifications/images/green-circle.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/highlight-element-to-extract.png b/docs-teststudiodev/features/recorder/verifications/images/highlight-element-to-extract.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/highlight-element.png b/docs-teststudiodev/features/recorder/verifications/images/highlight-element.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-build-step.png b/docs-teststudiodev/features/recorder/verifications/images/image-build-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-enable-highlighting.png b/docs-teststudiodev/features/recorder/verifications/images/image-enable-highlighting.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification-step.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig1.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig2.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig3.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig4.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig5.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig6.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig7.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig8.png b/docs-teststudiodev/features/recorder/verifications/images/image-verification/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/image-verification/gif9.gif b/docs-teststudiodev/features/recorder/verifications/images/image-verification/gif9.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/insert-from-quick-steps.png b/docs-teststudiodev/features/recorder/verifications/images/insert-from-quick-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/match-type.png b/docs-teststudiodev/features/recorder/verifications/images/match-type.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/recorded-steps.png b/docs-teststudiodev/features/recorder/verifications/images/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/red-circle.png b/docs-teststudiodev/features/recorder/verifications/images/red-circle.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/refine-image-area.png b/docs-teststudiodev/features/recorder/verifications/images/refine-image-area.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/set-extracted-value.png b/docs-teststudiodev/features/recorder/verifications/images/set-extracted-value.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/step-failure-details.png b/docs-teststudiodev/features/recorder/verifications/images/step-failure-details.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig1.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig10.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig2.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig3.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig4.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig5.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig6.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig7.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig8.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig9.png b/docs-teststudiodev/features/recorder/verifications/images/text-from-image/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/verification-section.png b/docs-teststudiodev/features/recorder/verifications/images/verification-section.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/verify-advanced-step.png b/docs-teststudiodev/features/recorder/verifications/images/verify-advanced-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/verify-content-options.png b/docs-teststudiodev/features/recorder/verifications/images/verify-content-options.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/verify-step.png b/docs-teststudiodev/features/recorder/verifications/images/verify-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/wait-quick-steps.png b/docs-teststudiodev/features/recorder/verifications/images/wait-quick-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/images/wait-test-step.png b/docs-teststudiodev/features/recorder/verifications/images/wait-test-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/recorder/verifications/quick-verification.md b/docs-teststudiodev/features/recorder/verifications/quick-verification.md
index 644e23c6..fc0a64d9 100644
--- a/docs-teststudiodev/features/recorder/verifications/quick-verification.md
+++ b/docs-teststudiodev/features/recorder/verifications/quick-verification.md
@@ -5,28 +5,28 @@ description: How to create a quick verification in Test Studio Dev
 slug: recorder/quick-execution
 position: 1
 ---
-# Add a Quick Verification#
+# Add a Quick Verification
 
 The easiest and fastest way to add a _verification_ to your test is through the Quick Steps section in the element's context menu.
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
+2. Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
 
-3.&nbsp; Enter _Telerik_ in the search box and click the __Search__ button.
+3. Enter _Telerik_ in the search box and click the __Search__ button.
 
-4.&nbsp; Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
+4. Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
 
-![Enable hover over](images/enable-highlighting.png)
+    ![Enable hover over](images/enable-highlighting.png)
 
-5.&nbsp; In the recording browser window, hover over the element against which to verify. Choose **Quick Steps > Verify - text contains** entry.
+5. In the recording browser window, hover over the element against which to verify. Choose **Quick Steps > Verify - text contains** entry.
 
-![highlight telerik](images/insert-from-quick-steps.png)
+    ![highlight telerik](images/insert-from-quick-steps.png)
 
 
-6.&nbsp; The Verify step is added to the test.
+6. The Verify step is added to the test.
 
-![test steps](images/verify-step.png)
+    ![test steps](images/verify-step.png)
 
 > __Note!__ Each Verification/Wait/Extract step could have it role changed between Verification, Wait, and Extraction (if based on text). Right click the step and select from the context menu __Change Role > Set As...__
 
diff --git a/docs-teststudiodev/features/recorder/verifications/text-from-image.md b/docs-teststudiodev/features/recorder/verifications/text-from-image.md
index b213d4b8..fd02b40d 100644
--- a/docs-teststudiodev/features/recorder/verifications/text-from-image.md
+++ b/docs-teststudiodev/features/recorder/verifications/text-from-image.md
@@ -12,54 +12,46 @@ You can verify specific text from an image in your application. Test Studio will
 
 There are few things that could ensure more stable and reliable test execution:
 
-&nbsp; &nbsp; ![Green][1] Use Text from Image Verification when you need to verify the text in an exact and static image.
+  ![Green](/features/recorder/verifications/images/text-from-image/fig1.png) Use Text from Image Verification when you need to verify the text in an exact and static image.
 
-&nbsp; &nbsp; ![Green][1] Specify only the part of the image which has the text, because logos and other symbols might be misinterpreted as characters.
+  ![Green](/features/recorder/verifications/images/text-from-image/fig1.png) Specify only the part of the image which has the text, because logos and other symbols might be misinterpreted as characters.
 
-&nbsp; &nbsp; ![Red][2] Do not use Text from Image Verification to verify a dynamic slide show or GIFs.
+  ![Red](/features/recorder/verifications/images/text-from-image/fig2.png) Do not use Text from Image Verification to verify a dynamic slide show or GIFs.
 
 ## How to record a text from image step
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to the application under test, for example "www.telerik.com".
+2. Navigate to the application under test, for example "www.telerik.com".
 
-3.&nbsp; Enable highlighting from the Recorder.
+3. Enable highlighting from the Recorder.
 
-![Enable Highlighting][3]
+    ![Enable Highlighting](images/text-from-image/fig3.png)
 
-4.&nbsp; Hover over the image, for example the Forbes logo, and add a verification, wait or extract step from the context menu.
+4. Hover over the image, for example the Forbes logo, and add a verification, wait or extract step from the context menu.
 
-![Build Quick Step][4]
+    ![Build Quick Step](images/text-from-image/fig4.png)
 
-5.&nbsp; Another way to add a Text from Image step is to select **Build Step...** from the context menu.
+5. Another way to add a Text from Image step is to select **Build Step...** from the context menu.
 
-![Build Step][5]
+    ![Build Step](images/text-from-image/fig5.png)
 
-6.&nbsp; In the Recorder click **Verifications > TextFromImage**.
+6. In the Recorder click **Verifications > TextFromImage**.
 
-![Image][6]
+    ![Image](images/text-from-image/fig6.png)
 
-7.&nbsp; By default, **OCR Entire Image** is checked. Uncheck this option to refine the comparison area and the image text.
+7. By default, **OCR Entire Image** is checked. Uncheck this option to refine the comparison area and the image text.
 
-![Refine][7]
+    ![Refine](images/text-from-image/fig7.png)
 
-8.&nbsp; Click **Add Step** and notice the Verify text steps are added to the test.
+8. Click **Add Step** and notice the Verify text steps are added to the test.
 
-![Step Added][8]
+    ![Step Added](images/text-from-image/fig8.png)
 
 ## Configure the recorded text from image step
 
 You can configure the TextToMatch and CompareType that will be used during test execution. That said, if you need to change the image, you need to record the verification step again.
 
-![Configure Test Step][9]
-
-[1]: /features/recorder/verifications/images/text-from-image/fig1.png
-[2]: /features/recorder/verifications/images/text-from-image/fig2.png
-[3]: /features/recorder/verifications/images/text-from-image/fig3.png
-[4]: /features/recorder/verifications/images/text-from-image/fig4.png
-[5]: /features/recorder/verifications/images/text-from-image/fig5.png
-[6]: /features/recorder/verifications/images/text-from-image/fig6.png
-[7]: /features/recorder/verifications/images/text-from-image/fig7.png
-[8]: /features/recorder/verifications/images/text-from-image/fig8.png
-[9]: /features/recorder/verifications/images/text-from-image/fig9.png
+![Configure Test Step](images/text-from-image/fig9.png)
+
+
diff --git a/docs-teststudiodev/features/recorder/verifications/wait.md b/docs-teststudiodev/features/recorder/verifications/wait.md
index 2634951f..3db67449 100644
--- a/docs-teststudiodev/features/recorder/verifications/wait.md
+++ b/docs-teststudiodev/features/recorder/verifications/wait.md
@@ -5,27 +5,27 @@ description: How to create a wait step to pause the Test Studio Dev test executi
 slug: recorder/wait-step
 position: 3
 ---
-# Create a Wait Step#
+# Create a Wait Step
 
 You can create a _Wait step_ in the same manner as a <a href="/features/recorder/verifications/quick-verification" target="_blank">quick verification</a> step. Instead of passing or failing based on a comparison, this step will wait for the comparison to be true before proceeding. The verification is performed after the server has responded.
 
-1.&nbsp; Create a Web Test and click Record.
+1. Create a Web Test and click Record.
 
-2.&nbsp; Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
+2. Navigate to <a href="http://www.bing.com" target="_blank">www.bing.com</a>
 
-3.&nbsp; Enter _Telerik_ in the search box and click the __Search__ button.
+3. Enter _Telerik_ in the search box and click the __Search__ button.
 
-4.&nbsp; Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
+4. Enable hover over highlighting by clicking _Highlight Element_ in the __Test Studio Dev Recorder__.
 
-5.&nbsp; Highlight the desired element. From the menu that appears choose **Quick Steps > Wait - element exists**.
+5. Highlight the desired element. From the menu that appears choose **Quick Steps > Wait - element exists**.
 
-![Wait element exists](images/wait-quick-steps.png)
+    ![Wait element exists](images/wait-quick-steps.png)
 
-6.&nbsp; The Wait step is added to the test.
+6. The Wait step is added to the test.
 
-![Wait step added](images/wait-test-step.png)
+    ![Wait step added](images/wait-test-step.png)
 
-7.&nbsp; With the Wait step highlighted, you can see the test <a href="/features/test-maintenance/test-step-properties" target="_blank">**Step Properties** pane</a> where you can change the Check interval and the timeout.
+7. With the Wait step highlighted, you can see the test <a href="/features/test-maintenance/test-step-properties" target="_blank">**Step Properties** pane</a> where you can change the Check interval and the timeout.
 
 > __Note!__ Each Verification/Wait/Extract step could have it role changed between Verification, Wait, and Extraction (if based on text). Right click the step and select from the context menu __Change Role > Set As...__
 
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig3.png b/docs-teststudiodev/features/test-execution/images/fig3.png
similarity index 100%
rename from docs-teststudiodev/features/test-execution/images/quick-execution/fig3.png
rename to docs-teststudiodev/features/test-execution/images/fig3.png
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig10.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig2.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig4.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig5.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig6.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig7.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/quick-execution/fig9.png b/docs-teststudiodev/features/test-execution/images/quick-execution/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-list-settings/fig11.png b/docs-teststudiodev/features/test-execution/images/test-list-settings/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig1.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig10.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig11.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig2.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig3.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig4.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig5.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig6.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig7.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig8.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig9.png b/docs-teststudiodev/features/test-execution/images/test-lists-in-vs-2017-2019/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-console/fig1.png b/docs-teststudiodev/features/test-execution/images/vs-test-console/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig1.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig2.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig3.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig4.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-group-tests.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-group-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-run-selected-tests.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-run-selected-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-run-tests.png b/docs-teststudiodev/features/test-execution/images/vs-test-explorer/vs-test-expl-run-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-execution/quick-execution.md b/docs-teststudiodev/features/test-execution/quick-execution.md
index af849ee0..c4b74ce7 100644
--- a/docs-teststudiodev/features/test-execution/quick-execution.md
+++ b/docs-teststudiodev/features/test-execution/quick-execution.md
@@ -12,53 +12,45 @@ Quick execution allows you to easily find out if a test is configured and design
 
 ## Execute a Test
 
-1.&nbsp; Once a test scenario is already recorded, click the **Execute** button in the test step pane.
+1. Once a test scenario is already recorded, click the **Execute** button in the test step pane.
 
-![Execute button][2]
+![Execute button](images/quick-execution/fig2.png)
 
-1.1 &nbsp; Select the execution browser. This step will be skipped if you have already set a preferred browser from the <a href="/features/project-settings/browsers" target="_blank">Project Settings Browsers tab</a>.
+1.1. Select the execution browser. This step will be skipped if you have already set a preferred browser from the <a href="/features/project-settings/browsers" target="_blank">Project Settings Browsers tab</a>.
 
-![Select browser][3]
+![Select browser](images/fig3.png)
 
-2.&nbsp; The Test Studio Dev Test Runner launches first in a command prompt window. This calls the set browser or application.
+2. The Test Studio Dev Test Runner launches first in a command prompt window. This calls the set browser or application.
 
-![Test Runner][4]
+![Test Runner](images/quick-execution/fig4.png)
 
 ## Visual Debugger
 
 By default in the lower right of your screen there is a ribbon which indicates the current step, includes play and pause ability, and shows additional Debug Options if you set a <a href="/features/test-maintenance/steps-pane" target="_blank">Breakpoint to any step</a>. This is the <a href="/features/failed-tests-debugging/using-the-visual-debugger" target="_blank">visual debugger</a> and is a feature you could turn on or off. 
 
-![Debugger][5]
+![Debugger](images/quick-execution/fig5.png)
 
 ## Execute with Annotation
 
 Click **Toggle Annotation** button to have the browser annotate each step with a brief message and by highlighting the target element for each step. Note that this will slow the test run down by inserting a delay between steps (in milliseconds) you set either from the dropdown menu or by entering a custom value.
 
-![Toggle Annotation][7]
+![Toggle Annotation](images/quick-execution/fig7.png)
 
 ## Debugger Options
 
 Click **Debugger Options** icon to to turn the debugger on/off and customize the Auto-Pause Options, if errors occur during the execution.
 
-![Debugger options][9]
+![Debugger options](images/quick-execution/fig9.png)
 
 ## Execution Timeouts
 
 Quick access to change the default timeouts for **Wait on elements** and **Client ready** is also available through the test step pane.
 
-![Timeouts][10]
+![Timeouts](images/quick-execution/fig10.png)
 
 ## Execution Results 
 
 Afterwards, when the test execution is complete, test results are automatically generated and can be reviewed. Click **View Log** for test results details.
 
-![View log][6]
+![View log](images/quick-execution/fig6.png)
 
-[2]: images/quick-execution/fig2.png
-[3]: images/quick-execution/fig3.png
-[4]: images/quick-execution/fig4.png
-[5]: images/quick-execution/fig5.png
-[6]: images/quick-execution/fig6.png
-[7]: images/quick-execution/fig7.png
-[9]: images/quick-execution/fig9.png
-[10]: images/quick-execution/fig10.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/test-execution/test-list-settings.md b/docs-teststudiodev/features/test-execution/test-list-settings.md
index 82821171..1536b7eb 100644
--- a/docs-teststudiodev/features/test-execution/test-list-settings.md
+++ b/docs-teststudiodev/features/test-execution/test-list-settings.md
@@ -4,13 +4,13 @@ page_title: Test List Settings  - Test Studio Dev Documentation
 description: "Test Studio Test List Settings. Change the browser for a test list run. RunnerResponseTimeout. UnexpectedDialogAction. KillBrowserProcessOnClose KillBrowsersBeforeStart Test list baseURL"
 position: 4
 ---
-# Test List Settings #
+# Test List Settings
 
 The Test lists in Test Studio Dev have various settings to modify and customize the test runs. These are specific for the test lists in Test Studio Dev project.
 
 ![Test List Settings][1]
 
-## General Tab ##
+## General Tab
 
 * ***Annotation***
 	* **AnnotateExecution** - whether to highlight and annotate the target element that the current action is being executed against.
@@ -49,7 +49,7 @@ The Test lists in Test Studio Dev have various settings to modify and customize
 	* **RecordingScale** - sets downscaling of the recorded video in percents. From 10 to 100.
 	* **RecordingSizeLimit** - sets file size limit in megabytes, 0 is unlimited size. If the limit is reached, video recording will be stopped before the test execution ends.
 
-## Web Tab ##
+## Web Tab
 
 * ***ASP.NET***
 	* **AspNetDevServerPort** - the ASP.NET development server port to use, if enabled. If set to -1, a random port is generated each time the manager is created.
@@ -77,7 +77,7 @@ The Test lists in Test Studio Dev have various settings to modify and customize
 	* **SilverlightApplicationPath** - the web address or local directory from which to load a Silverlight application.
 	* **SilverlightConnectTimeout** - the amount of time to wait for a Silverlight application to load before timing out.
 
-## WPF Tab ##
+## WPF Tab
 
 * ***Misc***
 	* **DefaultApplicationPath** - represents the default application path for WPF tests.
diff --git a/docs-teststudiodev/features/test-execution/test-lists-in-vs-2017-2019.md b/docs-teststudiodev/features/test-execution/test-lists-in-vs-2017-2019.md
index feba54fb..756523d0 100644
--- a/docs-teststudiodev/features/test-execution/test-lists-in-vs-2017-2019.md
+++ b/docs-teststudiodev/features/test-execution/test-lists-in-vs-2017-2019.md
@@ -4,7 +4,7 @@ page_title: Test Lists in Visual Studio 2017 and Later - Test Studio Dev Documen
 description: "Test Lists in Visual Studio. How to create a Test Studio Dev test list (suite) in Visual Studio. Static test list dynamic test list"
 position: 3
 ---
-# Test Lists in Visual Studio 2017 and 2019 #
+# Test Lists in Visual Studio 2017 and 2019
 
 As of **Test Studio 2019 R3 (v.2019.3) release** test lists can be also created and executed in a Visual Studio project. There are two types of Test Lists - **Static** and **Dynamic**.
 
@@ -13,7 +13,7 @@ As of **Test Studio 2019 R3 (v.2019.3) release** test lists can be also created
 
 > __Note!__ Test lists in Visual Studio can only execute web or WPF functional tests.
 
-## Create a Test List File in Visual Studio ##
+## Create a Test List File in Visual Studio
 
 A test list file has the extension ___*.aiilist___ and can be added in a Visual Studio project under a predefined folder named ___TestLists___ - this folder exists in each new project.
 
@@ -35,11 +35,11 @@ Build the solution (press F6) and all test list files will appear in the Test Ex
 
 ![Test list files listed in Test Explorer][5]
 
-### Add a Test List in Newly Created Project ###
+### Add a Test List in Newly Created Project
 
 Ensure you are using Test Studio with minimum version 2019.3 and create a new Test Studio project in Visual Studio 2017 or 2019. In the Solution Explorer you can add test list files under the folder named ___TestLists___.
 
-### Add a Test List in an Existing Project ###
+### Add a Test List in an Existing Project
 
 Once you upgrade Test Studio to minimum version 2019.3 and open an existing project, you will be prompted with a message, that the project needs to be upgraded as well. Once the upgrade is done and the project is loaded, you will need to include the ___TestLists___ folder in the solution.
 
@@ -55,7 +55,7 @@ Now all files from the project root folder will be listed in the __Solution Expl
 
 Again click the ___Show All Files___ button to hide the other files. Save and reopen the solution to apply the changes. Now the ___TestLists___ folder can be used to add test list files in it.
 
-## Add Test Files to Static Test List ##
+## Add Test Files to Static Test List
 
 Once a test list file is added into the ___TestLists___ folder, double click it to choose the test files to add in it.
 
@@ -63,7 +63,7 @@ Once a test list file is added into the ___TestLists___ folder, double click it
 
 Save the test list file to apply the changes and execute the test list from the ___Test Explorer___ in Visual Studio.
 
-## Add Test Files to Dynamic Test List ##
+## Add Test Files to Dynamic Test List
 
 Once a test list file is added into the ___TestLists___ folder, double click it to craft the rules to filter, upon specific criteria, the test files to add.
 
@@ -77,13 +77,13 @@ The rules can be built upon the specific <a href="/features/test-maintenance/tes
 
 __See also:__ You can find further interesting details in the following <a href="http://blogs.telerik.com/automated-testing-tools/posts/13-09-23/power-of-dynamic-test-lists" target="_blank">in-depth look at Dynamic Test Lists</a>.
 
-## Test List Settings in Visual Studio ##
+## Test List Settings in Visual Studio
 
 To change any of the <a href="/features/test-execution/test-list-settings" target="_blank">Test List settings</a> in Visual Studio, use the gear icon in the upper right corner in each test list.
 
 ![Test List Settings][11]
 
-## Execute Test List Files in Visual Studio ##
+## Execute Test List Files in Visual Studio
 
 To execute the designed test lists in Visual Studio, you can use the different <a href="/features/test-execution/vs-test-explorer#run-tests-and-test-lists-in-test-explorer" target="_blank">Run options in Visual Studio Test Explorer</a>.
 
diff --git a/docs-teststudiodev/features/test-execution/vs-test-console.md b/docs-teststudiodev/features/test-execution/vs-test-console.md
index 82ea908a..c27875cf 100644
--- a/docs-teststudiodev/features/test-execution/vs-test-console.md
+++ b/docs-teststudiodev/features/test-execution/vs-test-console.md
@@ -12,7 +12,7 @@ This article describes all necessary settings, as well as example commands.
 
 - [Add Test Studio Dev dlls to the GAC](#install-test-studio-dev-specific-dlls-in-gac)
 - [Set Test Studio Dev specific variables for the VS Command Prompt](#configure-the-vs-developer-command-prompt)
-- [Tailor up the command for the VSTest.Console.exe](#list-the-vstestconsoleexe-command)
+- [Tailor up the command for the VSTest.Console.exe](#list-the-vstest-console-exe-command)
 - [Examples](#example-commands)
 
 ## Install Test Studio Dev Specific DLLs in GAC
@@ -37,11 +37,11 @@ __2.__&nbsp; Change the __working folder__ to the one, which __contains the vste
 
 __3.__&nbsp; __Set the following two variables__ - ***TS_PROJECT_PATH*** (the folder, which contains the Test Studio project _Settings.aiis_) and ***TS_DLL_PATH*** (the folder, which contains the built project dll - by default it is in the project root under _\bin\Debug_).
 
-```
+````
 set TS_PROJECT_PATH=C:\Projects\TestStudioProject11\TestStudioProject11
 
 set TS_DLL_PATH=C:\Projects\TestStudioProject11\TestStudioProject11\bin\Debug\TestStudioProject11.dll
-```
+````
 
 > __Important!__
 ><br>
@@ -67,7 +67,7 @@ __2.__&nbsp; It is recommended to use the argument __/Settings:[fullPathToFile]_
 
 Below are listed sample commands to execute a Test Studio test and test list with the **VSTestConsole.exe in Visual Studio 2019**, after the **TS\_PROJECT\_PATH** and **TS\_DLL\_PATH** variables are set for the current instance of the VS Developer Command Prompt:
 
-```
+````
 trigger Parent.tstest run
 
 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console.exe "C:\Projects\TestStudioProject11\TestStudioProject11\Parent.tstest" /TestAdapterPath:"C:\Program Files (x86)\Progress\Test Studio\VS2019" /Settings:"C:\Projects\TestStudioProject11\TestStudioProject11\TestSettings1.testsettings
@@ -75,4 +75,4 @@ C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Com
 trigger sampleList.aiilist run
 
 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console.exe  "C:\Projects\TestStudioProject11\TestStudioProject11\TestLists\sampleList.aiilist" /TestAdapterPath:"C:\Program Files (x86)\Progress\Test Studio\VS2019" /Settings:"C:\Projects\TestStudioProject11\TestStudioProject11\TestSettings1.testsettings
-```
+````
diff --git a/docs-teststudiodev/features/test-execution/vs-test-explorer.md b/docs-teststudiodev/features/test-execution/vs-test-explorer.md
index 8bc52711..afad38df 100644
--- a/docs-teststudiodev/features/test-execution/vs-test-explorer.md
+++ b/docs-teststudiodev/features/test-execution/vs-test-explorer.md
@@ -4,11 +4,11 @@ page_title: Visual Studio Test Explorer - Test Studio Dev Documentation
 description: Test Studio Dev tests are recognized by VS Test Explorer and can be executed from its context. Run Test Studio Dev tests via the Test Explorer in Visual Studio
 position: 1
 ---
-# Visual Studio Test Explorer #
+# Visual Studio Test Explorer
 
 The <a href="http://msdn.microsoft.com/en-us/library/hh270865.aspx" target="_blank">Test Explorer</a> in Visual Studio discovers and runs tests, including Test Studio Dev tests and <a href="/features/test-execution/test-lists-in-vs-2017-2019" target="_blank">test lists</a>.
 
-## View Tests and Test Lists in Test Explorer ##
+## View Tests and Test Lists in Test Explorer
 
 If the __Test Explorer__ pane is not opened in your Visual Studio, you can access this as follows:
 
@@ -22,13 +22,13 @@ The Test Studio Dev tests and test lists are listed in the __Test Explorer__ aut
 
 ![Test Explorer][2]
 
-## Group Tests and Test Lists in Test Explorer ##
+## Group Tests and Test Lists in Test Explorer
 
 You can use Test Explorer to group tests into categories, filter the list of tests, and create, save, and run playlists of tests. There are few different options to group the test files and what makes sense in the context of Test Studio test project is to use __custom grouping starting with either _Namespace_ or _Project_, and use _Class_ and _State_ as sub-filters__ in the desired order.
 
 ![Group Tests and Test lists][3]
 
-## Run Tests and Test Lists in Test Explorer ##
+## Run Tests and Test Lists in Test Explorer
 
 To execute the test files from __Test Explorer__, use the **Run...** buttons and their available options.
 
diff --git a/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig1.png b/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig2.png b/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig3.png b/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig4.png b/docs-teststudiodev/features/test-maintenance/images/reorder-test-steps/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig1.png b/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig2.png b/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig3.png b/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig4.png b/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig5.png b/docs-teststudiodev/features/test-maintenance/images/search-test-steps/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig1.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig10.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig11.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig12.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig13.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig14.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig15.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig15.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig16.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig16.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig18.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig18.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig19.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig19.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig2.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig20.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig20.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig21.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig21.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig22.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig22.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig23.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig23.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig24.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig24.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig25.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig25.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig26.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig26.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig27.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig27.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig28.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig28.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig29.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig29.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig3.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig30.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig30.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig31.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig31.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig32.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig32.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig4.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig5.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig6.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig7.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig8.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig9.png b/docs-teststudiodev/features/test-maintenance/images/steps-pane/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/storyboard/fig2.png b/docs-teststudiodev/features/test-maintenance/images/storyboard/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/storyboard/fig3.png b/docs-teststudiodev/features/test-maintenance/images/storyboard/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/storyboard/fig4.png b/docs-teststudiodev/features/test-maintenance/images/storyboard/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/storyboard/fig5.png b/docs-teststudiodev/features/test-maintenance/images/storyboard/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/fig1.png b/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/file-properties.png b/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/file-properties.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/vs-properties.png b/docs-teststudiodev/features/test-maintenance/images/test-properties-vs/vs-properties.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-step-context-menu/fig1.png b/docs-teststudiodev/features/test-maintenance/images/test-step-context-menu/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-step-context-menu/fig2.png b/docs-teststudiodev/features/test-maintenance/images/test-step-context-menu/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-step-properties/fig1.png b/docs-teststudiodev/features/test-maintenance/images/test-step-properties/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/images/test-step-properties/fig2.png b/docs-teststudiodev/features/test-maintenance/images/test-step-properties/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/features/test-maintenance/reorder-test-steps.md b/docs-teststudiodev/features/test-maintenance/reorder-test-steps.md
index af00a757..e6cdb768 100644
--- a/docs-teststudiodev/features/test-maintenance/reorder-test-steps.md
+++ b/docs-teststudiodev/features/test-maintenance/reorder-test-steps.md
@@ -8,23 +8,19 @@ position: 3
 
 You can easily change the order of existing test steps.
 
-1.&nbsp; Use the **Move Step Down** and **Move Step Up** icons in the Steps pane. You can Ctrl + Click multiple steps and then move them together.
+1. Use the **Move Step Down** and **Move Step Up** icons in the Steps pane. You can Ctrl + Click multiple steps and then move them together.
 
-![Down/UP][1]
+    ![Down/UP](images/reorder-test-steps/fig1.png)
 
-2.&nbsp; The next method is to drag and drop. You can Ctrl + Click multiple steps and then drag them together.
+2. The next method is to drag and drop. You can Ctrl + Click multiple steps and then drag them together.
 
-![Drag&drop][2]
+    ![Drag&drop](images/reorder-test-steps/fig2.png)
 
-3.&nbsp; Use the standard keyboard shortcuts to Cut (Ctrl+X), Copy(Ctrl+C) and Paste (Ctrl+V) steps into the step pane. Multiple steps could be selected with Ctrl + Click and perform all of the above actions.
+3. Use the standard keyboard shortcuts to Cut (Ctrl+X), Copy(Ctrl+C) and Paste (Ctrl+V) steps into the step pane. Multiple steps could be selected with Ctrl + Click and perform all of the above actions.
 
-All steps could be deleted at once with the Clear All button - ![Clear All][3]
+All steps could be deleted at once with the Clear All button - ![Clear All](images/reorder-test-steps/fig3.png)
 
-4.&nbsp; To choose where to insert new steps from the step builder or paste any copied steps click the gray box to the left of the step number. An arrow will appear next to that step and any new steps will be inserted after that one selected.
+4. To choose where to insert new steps from the step builder or paste any copied steps click the gray box to the left of the step number. An arrow will appear next to that step and any new steps will be inserted after that one selected.
 
-![>][4]
+![>](images/reorder-test-steps/fig4.png)
 
-[1]: images/reorder-test-steps/fig1.png
-[2]: images/reorder-test-steps/fig2.png
-[3]: images/reorder-test-steps/fig3.png
-[4]: images/reorder-test-steps/fig4.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/test-maintenance/steps-pane.md b/docs-teststudiodev/features/test-maintenance/steps-pane.md
index 7e815657..2418497e 100644
--- a/docs-teststudiodev/features/test-maintenance/steps-pane.md
+++ b/docs-teststudiodev/features/test-maintenance/steps-pane.md
@@ -52,12 +52,12 @@ The available options related to test execution in the Step pane are listed belo
 | ![Test Properties](images/steps-pane/fig32.png) | __Test Properties__ - Displays the test properties |
 
 [1]: images/steps-pane/fig1.png
-[2]: images/steps-pane/fig2.png
+
 [3]: images/steps-pane/fig3.png
 [4]: images/steps-pane/fig4.png
 [5]: images/steps-pane/fig5.png
 [6]: images/steps-pane/fig6.png
-[7]: images/steps-pane/fig7.png
+
 [8]: images/steps-pane/fig8.png
 [9]: images/steps-pane/fig9.png
 [10]: images/steps-pane/fig10.png
@@ -67,6 +67,6 @@ The available options related to test execution in the Step pane are listed belo
 [14]: images/steps-pane/fig14.png
 [15]: images/steps-pane/fig15.png
 [16]: images/steps-pane/fig16.png
-[17]: images/steps-pane/fig17.png
+
 [18]: images/steps-pane/fig18.png
 [19]: images/steps-pane/fig19.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/test-maintenance/test-step-context-menu.md b/docs-teststudiodev/features/test-maintenance/test-step-context-menu.md
index 9f9c3952..04f14263 100644
--- a/docs-teststudiodev/features/test-maintenance/test-step-context-menu.md
+++ b/docs-teststudiodev/features/test-maintenance/test-step-context-menu.md
@@ -11,8 +11,8 @@ Each test step has a context menu with further actions that can be taken. Note t
 
 <table id="no-table">
 <tr>
-<td>![Step Context Menu - Navigate][1]</td>
-<td>![Step Context Menu][2]</td>
+<td><img src="images/test-step-context-menu/fig1.png" alt="Step Context Menu - Navigate" /></td>
+<td><img src="images/test-step-context-menu/fig2.png" alt="Step Context Menu" /></td>
 </tr>
 <table>
 
@@ -85,5 +85,3 @@ The options in this section are only available for Verification steps!
 - **Edit in Code** - converts the recorded step to a new method in the coded file related to the test. Notice that the description and icon change to indicate the step is now a coded one. Once converted, it cannot be switched back to the initially recorded step.
 - **View Code** - switches to the code-behind file and shows the test method for the selected coded step.
 
-[1]: images/test-step-context-menu/fig1.png
-[2]: images/test-step-context-menu/fig2.png
\ No newline at end of file
diff --git a/docs-teststudiodev/features/test-maintenance/test-step-properties.md b/docs-teststudiodev/features/test-maintenance/test-step-properties.md
index d743a770..fd9e08ae 100644
--- a/docs-teststudiodev/features/test-maintenance/test-step-properties.md
+++ b/docs-teststudiodev/features/test-maintenance/test-step-properties.md
@@ -43,115 +43,190 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AltKey**</td><td>Whether to hold the Alt key while clicking.</td><td>To execute an Alt + Click.</td>
+<td>
+	
+**AltKey**</td><td>Whether to hold the Alt key while clicking.</td><td>To execute an Alt + Click.</td>
 </tr>
 <tr>
-	<td>**AnnotationText**</td><td>The text to use for annotation.</td><td>With a Custom Annotation step.</td>
+<td>
+	
+**AnnotationText**</td><td>The text to use for annotation.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**BaseUrl**</td><td>The BaseURL to use when a global base is missing.</td><td> </td>
+<td>
+	
+**BaseUrl**</td><td>The BaseURL to use when a global base is missing.</td><td> </td>
 </tr>
 <tr>
-	<td>**CaptureType**</td><td>The type of window to capture.</td><td>With a Browser/Desktop Capture step.</td>
+<td>
+	
+**CaptureType**</td><td>The type of window to capture.</td><td>With a Browser/Desktop Capture step.</td>
 </tr>
 <tr>
-	<td>**ClickPoint / Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To click the target element based on specific offset coordinates instead of at absolute center.</td>
+<td>
+	
+**ClickPoint / Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To click the target element based on specific offset coordinates instead of at absolute center.</td>
 </tr>
 <tr>
-	<td>**ClosesBrowser**</td><td>ndicates to the automation that this action will force the browser to close. Typical for HTML pop-ups.</td><td>With a Click step that closes an HTML pop-up.</td>
+<td>
+	
+**ClosesBrowser**</td><td>ndicates to the automation that this action will force the browser to close. Typical for HTML pop-ups.</td><td>With a Click step that closes an HTML pop-up.</td>
 </tr>
 <tr>
-	<td>**ControlKey**</td><td>Whether to hold the <em>Ctrl</em> key while clicking.</td><td>To execute a Ctrl + Click. </td>
+<td>
+	
+**ControlKey**</td><td>Whether to hold the <em>Ctrl</em> key while clicking.</td><td>To execute a Ctrl + Click. </td>
 </tr>
 <tr>
-	<td>**Desktop Command Type**</td><td> The mouse action type.</td><td></td>
+<td>
+	
+**Desktop Command Type**</td><td> The mouse action type.</td><td></td>
 </tr>
 <tr>
-	<td>**DisplayLocation**</td><td>The location to display the annotation relative to the browser window.</td><td>With a Custom Annotation step.</td>
+<td>
+	
+**DisplayLocation**</td><td>The location to display the annotation relative to the browser window.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**DisplayTime**</td><td> The length of time in milliseconds to display the annotation.</td><td>With a Custom Annotation step.</td>
+<td>
+	
+**DisplayTime**</td><td> The length of time in milliseconds to display the annotation.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**Encrypt**</td><td>When set, will encrypt text typed into input control.<br>Once set to true, cannot be changed back to false.<br>'Text' property cannot be modified and current step cannot be converted to code. </td><td>With a <em>Set text</em> step on a password field. </td>
+<td>
+	
+**Encrypt**</td><td>When set, will encrypt text typed into input control.<br>Once set to true, cannot be changed back to false.<br>'Text' property cannot be modified and current step cannot be converted to code. </td><td>With a <em>Set text</em> step on a password field. </td>
 </tr>
 <tr>
-	<td>**EventType**</td><td>The Javascript event type to invoke.</td><td></td>
+<td>
+	
+**EventType**</td><td>The Javascript event type to invoke.</td><td></td>
 </tr>
 <tr>
-	<td>**FileNamePrefix**</td><td>The file name prefix to use to save the capture on disk.</td><td>To edit the file name for a browser or desktop Capture image.</td>
+<td>
+	
+**FileNamePrefix**</td><td>The file name prefix to use to save the capture on disk.</td><td>To edit the file name for a browser or desktop Capture image.</td>
 </tr>
 <tr>
-	<td>**FireKeyEvents**</td><td>Whether to fire <em>KeyDown</em> and <em>KeyUp</em> events during simulated typing.</td><td>If target input element requires these events to be fired.</td>
+<td>
+	
+**FireKeyEvents**</td><td>Whether to fire <em>KeyDown</em> and <em>KeyUp</em> events during simulated typing.</td><td>If target input element requires these events to be fired.</td>
 </tr>
 <tr>
-	<td>**Focus**</td><td>Scroll element into view before performing an action on it.</td><td>For action steps that require the element be scrolled into view before being acted upon.</td>
+<td>
+	
+**Focus**</td><td>Scroll element into view before performing an action on it.</td><td>For action steps that require the element be scrolled into view before being acted upon.</td>
 </tr>
 <tr>
-	<td>**HandleButton**</td><td>The button to click to handle this dialog.</td><td>To change the button clicked in the dialog.</td>
+<td>
+	
+**HandleButton**</td><td>The button to click to handle this dialog.</td><td>To change the button clicked in the dialog.</td>
 </tr>
 <tr>
-	<td>**HandleTimeout**</td><td>The timeout in milliseconds for the dialog to be handled once it is detected.</td><td>Increase if dialog is not fully handled within time set.</td>
+<td>
+	
+**HandleTimeout**</td><td>The timeout in milliseconds for the dialog to be handled once it is detected.</td><td>Increase if dialog is not fully handled within time set.</td>
 </tr>
 <tr>
-	<td>**InitializationTime**</td><td>The fixed time to wait in milliseconds before the handling of the dialog starts.</td><td>Increase if dialog needs longer to initialize.</td>
+<td>
+	
+**InitializationTime**</td><td>The fixed time to wait in milliseconds before the handling of the dialog starts.</td><td>Increase if dialog needs longer to initialize.</td>
 </tr>
 <tr>
-	<td>**IsPassword**</td><td>Whether the text field is a password.</td><td>To mask the password in the step description. </td>
+<td>
+	
+**IsPassword**</td><td>Whether the text field is a password.</td><td>To mask the password in the step description. </td>
 </tr>
 <tr>
-	<td>**KeyHoldTime**</td><td>The length of time in milliseconds to hold each key down when <em>SimulateRealTyping</em> is true.</td><td>To slow down or speed up typing.</td>
+<td>
+	
+**KeyHoldTime**</td><td>The length of time in milliseconds to hold each key down when <em>SimulateRealTyping</em> is true.</td><td>To slow down or speed up typing.</td>
 </tr>
 <tr>
-	<td>**Modifier Keys**</td><td>Any modifier keys held while clicking.</td><td>If the click step requires a modifier key to be held.</td>
+<td>
+	
+**Modifier Keys**</td><td>Any modifier keys held while clicking.</td><td>If the click step requires a modifier key to be held.</td>
 </tr>
 <tr>
-	<td>**MouseButton**</td><td>The clicked mouse button.</td><td>With a Mouse Action Desktop Command step.</td>
+<td>
+	
+**MouseButton**</td><td>The clicked mouse button.</td><td>With a Mouse Action Desktop Command step.</td>
 </tr>
 <tr>
-	<td>**NavigateUrl**</td><td>The URL for the Navigate step.</td><td>To edit the target URL.</td>
+<td>
+	
+**NavigateUrl**</td><td>The URL for the Navigate step.</td><td>To edit the target URL.</td>
 </tr>
 <tr>
-	<td>**OverrideFile**</td><td>Whether to override the image file if it exists.</td><td>To create new or override existing browser or desktop Capture images.</td>
+<td>
+	
+**OverrideFile**</td><td>Whether to override the image file if it exists.</td><td>To create new or override existing browser or desktop Capture images.</td>
 </tr>
 <tr>
-	<td>**Recorded Text Content**</td><td> Text to use when <em>SimulateRealTyping</em> is false.</td><td>To edit input text.</td>
+<td>
+	
+**Recorded Text Content**</td><td> Text to use when <em>SimulateRealTyping</em> is false.</td><td>To edit input text.</td>
 </tr>
 <tr>
-	<td>**ScrollToVisibleType**</td><td>Scroll element to visible type.</td><td>To set a Scroll step to window top, center or bottom.</td>
+<td>
+	
+**ScrollToVisibleType**</td><td>Scroll element to visible type.</td><td>To set a Scroll step to window top, center or bottom.</td>
 </tr>
 <tr>
-	<td>**SearchByImageFirst**</td><td>Search by image before searching by element's find expression.</td><td>**ParentSetting** will inherit Project or Test List settings. **True** and **False** overrides Project and Test List settings.</td>
+<td>
+	
+**SearchByImageFirst**</td><td>Search by image before searching by element's find expression.</td>
+**ParentSetting** will inherit Project or Test List settings. **True** and **False** overrides Project and Test List settings.</td>
 </tr>
 <tr>
-	<td>**ShiftKey**</td><td>Whether to hold the Shift key while clicking.</td><td>To execute a Shift + Click.</td>
+<td>
+	
+**ShiftKey**</td><td>Whether to hold the Shift key while clicking.</td><td>To execute a Shift + Click.</td>
 </tr>
 <tr>
-	<td>**SimulateRealClick**</td><td>Whether to perform the click using the mouse rather than directly invoking a click on the DOM element.</td><td>If the click target requires a real click to trigger an event or validation.</td>
+<td>
+	
+**SimulateRealClick**</td><td>Whether to perform the click using the mouse rather than directly invoking a click on the DOM element.</td><td>If the click target requires a real click to trigger an event or validation.</td>
 </tr>
 <tr>
-	<td>**SimulateRealTyping**</td><td>Whether to simulate real text typing one character at a time.</td><td>If input field requires real typing to trigger an event or validation.</td>
+<td>
+	
+**SimulateRealTyping**</td><td>Whether to simulate real text typing one character at a time.</td><td>If input field requires real typing to trigger an event or validation.</td>
 </tr>
 <tr>
-	<td>**SimulateRealUser**</td><td>Whether to simulate real user actions.</td><td>For Silverlight/WPF action steps.</td>
+<td>
+	
+**SimulateRealUser**</td><td>Whether to simulate real user actions.</td><td>For Silverlight/WPF action steps.</td>
 </tr>
 <tr>
-	<td>**Text**</td><td>Text entered into input control.</td><td>To edit the input text.</td>
+<td>
+	
+**Text**</td><td>Text entered into input control.</td><td>To edit the input text.</td>
 </tr>
 <tr>
-	<td>**TimeBetweenKeyPresses**</td><td>The pause in milliseconds between key presses to use when SimulateRealUser is set.</td><td>To increase or decrease the typing speed.</td>
+<td>
+	
+**TimeBetweenKeyPresses**</td><td>The pause in milliseconds between key presses to use when SimulateRealUser is set.</td><td>To increase or decrease the typing speed.</td>
 </tr>
 <tr>
-	<td>**Typed Text**</td><td>Text that will be played back when <em>SimulateRealUser</em> is true.</td><td>To edit the typed text.</td>
+<td>
+	
+**Typed Text**</td><td>Text that will be played back when <em>SimulateRealUser</em> is true.</td><td>To edit the typed text.</td>
 </tr>
 <tr>
-	<td>**Typing Delay**</td><td>The pause between key presses when <em>SimulateRealUser</em> is set.</td><td>To increase or decrease the typing speed. </td>
+<td>
+	
+**Typing Delay**</td><td>The pause between key presses when <em>SimulateRealUser</em> is set.</td><td>To increase or decrease the typing speed. </td>
 </tr>
 <tr>
-	<td>**Use Offset**</td><td>Whether to click at a specific point within the target element or the center of it.</td><td>With a Click step. </td>
+<td>
+	
+**Use Offset**</td><td>Whether to click at a specific point within the target element or the center of it.</td><td>With a Click step. </td>
 </tr>
 <tr>
-	<td>**WaitTime**</td><td>Time to wait in milliseconds.</td><td>With an Execution Delay step. </td>
+<td>
+	
+**WaitTime**</td><td>Time to wait in milliseconds.</td><td>With an Execution Delay step. </td>
 </tr>
 <table>
 
@@ -162,7 +237,9 @@ padding: 8px;
 	<th>Property</th><th>Property</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Comment**</td><td>The text comment to display as a single test step in the test log.</td><td>To insert a comment into the test log next to the step. </td>
+<td>
+	
+**Comment**</td><td>The text comment to display as a single test step in the test log.</td><td>To insert a comment into the test log next to the step. </td>
 </tr>
 <table>
 
@@ -173,7 +250,9 @@ padding: 8px;
 	<th>Property</th><th>Property</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**(Bindings)**</td><td>Bind data driven properties against a data source. Click the drop-down to see properties that support data binding.</td><td>To data bind the step to a specific column from the data source.</td>
+<td>
+	
+**(Bindings)**</td><td>Bind data driven properties against a data source. Click the drop-down to see properties that support data binding.</td><td>To data bind the step to a specific column from the data source.</td>
 </tr>
 <table>
 
@@ -184,13 +263,19 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ChildWindowTextContent**</td><td>A partial text that might be found on the dialog.</td><td>If two dialogs have similar titles, further distinguish them by adding this property. </td>
+<td>
+	
+**ChildWindowTextContent**</td><td>A partial text that might be found on the dialog.</td><td>If two dialogs have similar titles, further distinguish them by adding this property. </td>
 </tr>
 <tr>
-	<td>**DialogTitle**</td><td>The dialog title to look for to identify the dialog.</td><td>To edit the identifying dialog title. </td>
+<td>
+	
+**DialogTitle**</td><td>The dialog title to look for to identify the dialog.</td><td>To edit the identifying dialog title. </td>
 </tr>
 <tr>
-	<td>**MatchPartialTitle**</td><td>Whether to use partial text matching to match the dialog title.</td><td>To match an exact or partial dialog title. </td>
+<td>
+	
+**MatchPartialTitle**</td><td>Whether to use partial text matching to match the dialog title.</td><td>To match an exact or partial dialog title. </td>
 </tr>
 <table>
 
@@ -201,7 +286,9 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DownloadPath**</td><td>The download location to set for the download dialog.</td><td>To change where a file is saved by the Download dialog handler step. </td>
+<td>
+	
+**DownloadPath**</td><td>The download location to set for the download dialog.</td><td>To change where a file is saved by the Download dialog handler step. </td>
 </tr>
 <table>
 
@@ -212,7 +299,9 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To start the drag from an offset of the source element, as opposed to absolute center. </td>
+<td>
+	
+**Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To start the drag from an offset of the source element, as opposed to absolute center. </td>
 </tr>
 <table>
 
@@ -223,13 +312,19 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DragDropWindowData**</td><td>Used when entire window is considered the drop target.</td><td>To edit the window coordinates where the source element is dropped when using window target.</td>
+<td>
+	
+**DragDropWindowData**</td><td>Used when entire window is considered the drop target.</td><td>To edit the window coordinates where the source element is dropped when using window target.</td>
 </tr>
 <tr>
-	<td>**DropOffset**</td><td>The offset to use for the drop target.</td><td>To drop the source element to offset coordinates of the target element. </td>
+<td>
+	
+**DropOffset**</td><td>The offset to use for the drop target.</td><td>To drop the source element to offset coordinates of the target element. </td>
 </tr>
 <tr>
-	<td>**DropTargetType**</td><td>The type of drop target to use for the drag drop.</td><td>To drop the source element to a window or element target. Element targets tend to be more reliable. </td>
+<td>
+	
+**DropTargetType**</td><td>The type of drop target to use for the drag drop.</td><td>To drop the source element to a window or element target. Element targets tend to be more reliable. </td>
 </tr>
 <table>
 
@@ -240,22 +335,34 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Drag Element**</td><td>Key of the element to use for the drag.</td><td>To change the source element to drag. </td>
+<td>
+	
+**Drag Element**</td><td>Key of the element to use for the drag.</td><td>To change the source element to drag. </td>
 </tr>
 <tr>
-	<td>**Drop Element**</td><td>Key of the element to use for the drop.</td><td>To change the target element to drop onto. </td>
+<td>
+	
+**Drop Element**</td><td>Key of the element to use for the drop.</td><td>To change the target element to drop onto. </td>
 </tr>
 <tr>
-	<td>**PrimaryTarget**</td><td>The primary automation element that this step is targeting.</td><td>To change the element the step is based on. </td>
+<td>
+	
+**PrimaryTarget**</td><td>The primary automation element that this step is targeting.</td><td>To change the element the step is based on. </td>
 </tr>
 <tr>
-	<td>**SecondaryTarget**</td><td>The primary automation element that this step is targeting. Used only for steps that require two targets, like a drag and drop.</td><td>Only in drag and drop scenarios. </td>
+<td>
+	
+**SecondaryTarget**</td><td>The primary automation element that this step is targeting. Used only for steps that require two targets, like a drag and drop.</td><td>Only in drag and drop scenarios. </td>
 </tr>
 <tr>
-	<td>**Virtualizing Container**</td><td>The object containing this element, if any.</td><td>(Silverlight only) </td>
+<td>
+	
+**Virtualizing Container**</td><td>The object containing this element, if any.</td><td>(Silverlight only) </td>
 </tr>
 <tr>
-	<td>**Virtualizing Container Offset**</td><td>The offset to scroll the virtualizing container to before searching for the target element of this step.</td><td>(Silverlight only) </td>
+<td>
+	
+**Virtualizing Container Offset**</td><td>The offset to scroll the virtualizing container to before searching for the target element of this step.</td><td>(Silverlight only) </td>
 </tr>
 <table>
 
@@ -266,28 +373,44 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AjaxTimeout** </td><td>The timeout to wait for pending AJAX requests. </td><td>If the test step relies on an AJAX postback to complete before proceeding. </td>
+<td>
+	
+**AjaxTimeout** </td><td>The timeout to wait for pending AJAX requests. </td><td>If the test step relies on an AJAX postback to complete before proceeding. </td>
 </tr>
 <tr>
-	<td>**EnsureElementsClickable**</td><td>Whether to ensure the target element of this action is visible and clickable before performing the action.</td><td></td>
+<td>
+	
+**EnsureElementsClickable**</td><td>Whether to ensure the target element of this action is visible and clickable before performing the action.</td><td></td>
 </tr>
 <tr>
-	<td>**ScrollToVisibleType**</td><td>When 'SimulateRealClick' or 'SimulateRealTyping' is set to 'True', you can specify the scroll direction in order to get the target element into view.</td><td>Choose whether to scroll the element to top, center or  bottom of the page.</td>
+<td>
+	
+**ScrollToVisibleType**</td><td>When 'SimulateRealClick' or 'SimulateRealTyping' is set to 'True', you can specify the scroll direction in order to get the target element into view.</td><td>Choose whether to scroll the element to top, center or  bottom of the page.</td>
 </tr>
 <tr>
-	<td>**Pause**</td><td>Whether to pause the step during execution. Only respected when running tests from the Test Explorer.</td><td>To pause test execution at a certain point to manually debug. </td>
+<td>
+	
+**Pause**</td><td>Whether to pause the step during execution. Only respected when running tests from the Test Explorer.</td><td>To pause test execution at a certain point to manually debug. </td>
 </tr>
 <tr>
-	<td>**UseStepWaitOnElementsTimeout**</td><td>Whether to use step's WaitOnElementsTimeout instead of the global setting.</td><td>To specifically increase one step's element locating timeout. </td>
+<td>
+	
+**UseStepWaitOnElementsTimeout**</td><td>Whether to use step's WaitOnElementsTimeout instead of the global setting.</td><td>To specifically increase one step's element locating timeout. </td>
 </tr>
 <tr>
-	<td>**WaitForNoMotion**</td><td>Wait for the element to stop moving before executing the action.</td><td></td>
+<td>
+	
+**WaitForNoMotion**</td><td>Wait for the element to stop moving before executing the action.</td><td></td>
 </tr>
 <tr>
-	<td>**WaitOnElements**</td><td>Whether to wait on step's elements to exist before executing it.</td><td>The default is True (recommended). False will ignore the Global and per step settings and will execute the step without waiting for the element (not recommended). </td>
+<td>
+	
+**WaitOnElements**</td><td>Whether to wait on step's elements to exist before executing it.</td><td>The default is True (recommended). False will ignore the Global and per step settings and will execute the step without waiting for the element (not recommended). </td>
 </tr>
 <tr>
-	<td>**WaitOnElementsTimeout**</td><td>Number of milliseconds to wait for element to exist if <em>WaitOnElements</em> is true.</td><td>To specifically increase one step's element locating timeout. </td>
+<td>
+	
+**WaitOnElementsTimeout**</td><td>Number of milliseconds to wait for element to exist if <em>WaitOnElements</em> is true.</td><td>To specifically increase one step's element locating timeout. </td>
 </tr>
 <table>
 
@@ -298,7 +421,9 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DataBindVariableName**</td><td>The name with which this extraction is published.</td><td>To change the Extraction variable used for later data binding. </td>
+<td>
+	
+**DataBindVariableName**</td><td>The name with which this extraction is published.</td><td>To change the Extraction variable used for later data binding. </td>
 </tr>
 <table>
 
@@ -309,7 +434,9 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**TriggerjQueryEvent**</td><td>During step execution, attempt to trigger proper jQuery event.</td><td>Step is expected to trigger a jQuery event on the page.</td>
+<td>
+	
+**TriggerjQueryEvent**</td><td>During step execution, attempt to trigger proper jQuery event.</td><td>Step is expected to trigger a jQuery event on the page.</td>
 </tr>
 <table>
 
@@ -320,13 +447,19 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ButtonId**</td><td>The button ID to use when <em>HandleButtonMethod = ButtonId</em>.</td><td>To edit the button ID used to handle a Generic dialog. </td>
+<td>
+	
+**ButtonId**</td><td>The button ID to use when <em>HandleButtonMethod = ButtonId</em>.</td><td>To edit the button ID used to handle a Generic dialog. </td>
 </tr>
 <tr>
-	<td>**ButtonPartialText**</td><td>The partial button text to use when <em>HandleButtonMethod = ButtonPartialText</em>.</td><td>To edit the partial button text used to handle a Generic dialog. </td>
+<td>
+	
+**ButtonPartialText**</td><td>The partial button text to use when <em>HandleButtonMethod = ButtonPartialText</em>.</td><td>To edit the partial button text used to handle a Generic dialog. </td>
 </tr>
 <tr>
-	<td>**HandleButtonMethod**</td><td>Identification method of the handle method. <em>NoneCloseDialog</em> simply attempts to knock down the dialog using the Close button.</td><td>To change the handle method for a Generic dialog.</td>
+<td>
+	
+**HandleButtonMethod**</td><td>Identification method of the handle method. <em>NoneCloseDialog</em> simply attempts to knock down the dialog using the Close button.</td><td>To change the handle method for a Generic dialog.</td>
 </tr>
 <table>
 
@@ -337,10 +470,14 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Password**</td><td>The password to use to log on.</td><td>To edit the password in a Logon dialog handler step. </td>
+<td>
+	
+**Password**</td><td>The password to use to log on.</td><td>To edit the password in a Logon dialog handler step. </td>
 </tr>
 <tr>
-	<td>**UserName**</td><td>The user name to use to log on.</td><td>To edit the user name in a Logon dialog handler step. </td>
+<td>
+	
+**UserName**</td><td>The user name to use to log on.</td><td>To edit the user name in a Logon dialog handler step. </td>
 </tr>
 <table>
 
@@ -351,10 +488,14 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ExecutionTimeout**</td><td>Timeout in milliseconds to wait for the manual execution, else step will timeout and log a failure.</td><td>To change the time in minutes a Manual step will wait for input. </td>
+<td>
+	
+**ExecutionTimeout**</td><td>Timeout in milliseconds to wait for the manual execution, else step will timeout and log a failure.</td><td>To change the time in minutes a Manual step will wait for input. </td>
 </tr>
 <tr>
-	<td>**ManualDescription**</td><td>Description displayed in <em>Execute Manual Step</em> dialog.</td><td>To edit the message displayed in the Manual step dialog. </td>
+<td>
+	
+**ManualDescription**</td><td>Description displayed in <em>Execute Manual Step</em> dialog.</td><td>To edit the message displayed in the Manual step dialog. </td>
 </tr>
 <table>
 
@@ -365,49 +506,79 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DialogType**</td><td>The type of dialog handled by the step.</td><td>(Read only) </td>
+<td>
+	
+**DialogType**</td><td>The type of dialog handled by the step.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**InvokeSelectionChanged** </td><td>Whether to invoke the OnChange javascript event. </td><td>If the step requires the OnChange event. </td>
+<td>
+	
+**InvokeSelectionChanged** </td><td>Whether to invoke the OnChange javascript event. </td><td>If the step requires the OnChange event. </td>
 </tr>
 <tr>
-	<td>**IsDoubleClick**</td><td>Whether a click step is a single or double click.</td><td>To toggle between single or double click. </td>
+<td>
+	
+**IsDoubleClick**</td><td>Whether a click step is a single or double click.</td><td>To toggle between single or double click. </td>
 </tr>
 <tr>
-	<td>**IsPartial**</td><td>Whether to perform a partial or exact match on the URL.</td><td>With a Wait For Url step. </td>
+<td>
+	
+**IsPartial**</td><td>Whether to perform a partial or exact match on the URL.</td><td>With a Wait For Url step. </td>
 </tr>
 <tr>
-	<td>**LogMessageOnFailure**</td><td>Message to log as part of log content if step fails.</td><td>To insert a custom message in the test log if the step fails. </td>
+<td>
+	
+**LogMessageOnFailure**</td><td>Message to log as part of log content if step fails.</td><td>To insert a custom message in the test log if the step fails. </td>
 </tr>
 <tr>
-	<td>**RequiresSilverlight**</td><td>Whether this step requires Silverlight to be enabled.</td><td></td>
+<td>
+	
+**RequiresSilverlight**</td><td>Whether this step requires Silverlight to be enabled.</td><td></td>
 </tr>
 <tr>
-	<td>**RunsAgainst**</td><td>The browsers this step can run against.</td><td>If a step should only be run for a specific browser type. </td>
+<td>
+	
+**RunsAgainst**</td><td>The browsers this step can run against.</td><td>If a step should only be run for a specific browser type. </td>
 </tr>
 <tr>
-	<td>**RunsAgainstVersion**</td><td>The browser version that this step can run against.</td><td>If a step should only be run for a specific browser version. </td>
+<td>
+	
+**RunsAgainstVersion**</td><td>The browser version that this step can run against.</td><td>If a step should only be run for a specific browser version. </td>
 </tr>
 <tr>
-	<td>**RunsAgainstVersionCompare**</td><td>The compare type of the browser version that this step can run against.</td><td>To change the browser version comparison from Equals to LessThan, for example.</td>
+<td>
+	
+**RunsAgainstVersionCompare**</td><td>The compare type of the browser version that this step can run against.</td><td>To change the browser version comparison from Equals to LessThan, for example.</td>
 </tr>
 <tr>
-	<td>**StepType**</td><td>Step descriptor type.</td><td>(Read only) </td>
+<td>
+	
+**StepType**</td><td>Step descriptor type.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**TestName**</td><td>Name of the test to execute for Test as Step.</td><td>(Read only) </td>
+<td>
+	
+**TestName**</td><td>Name of the test to execute for Test as Step.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**TestPath**</td><td>Test path to use for Test as Step.</td><td></td>
+<td>
+	
+**TestPath**</td><td>Test path to use for Test as Step.</td><td></td>
 </tr>
 <tr>
-	<td>**TestUniqueId**</td><td>Unique ID for Test as Step.</td><td></td>
+<td>
+	
+**TestUniqueId**</td><td>Unique ID for Test as Step.</td><td></td>
 </tr>
 <tr>
-	<td>**Url**</td><td>The URL to wait for.</td><td>With a Wait For Url step. </td>
+<td>
+	
+**Url**</td><td>The URL to wait for.</td><td>With a Wait For Url step. </td>
 </tr>
 <tr>
-	<td>**WaitTimeout**</td><td>The timeout to use for waiting.</td><td>With a Wait For Url step.</td>
+<td>
+	
+**WaitTimeout**</td><td>The timeout to use for waiting.</td><td>With a Wait For Url step.</td>
 </tr>
 <table>
 
@@ -418,7 +589,9 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**FileUploadPath**</td><td>The file upload path on disk.</td><td>To change the upload path. </td>
+<td>
+	
+**FileUploadPath**</td><td>The file upload path on disk.</td><td>To change the upload path. </td>
 </tr>
 <table>
 
@@ -429,28 +602,44 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AttributeName** </td><td>The attribute name to verify. </td><td>To change the target attribute to verify. </td>
+<td>
+	
+**AttributeName** </td><td>The attribute name to verify. </td><td>To change the target attribute to verify. </td>
 </tr>
 <tr>
-	<td>**AttributeValue** </td><td>The attribute value to verify. </td><td>To change the attribute's value to verify. </td>
+<td>
+	
+**AttributeValue** </td><td>The attribute value to verify. </td><td>To change the attribute's value to verify. </td>
 </tr>
 <tr>
-	<td>**CompareType**</td><td>The compare type of the text verification.</td><td>To change from an exact to a partial match, for example. </td>
+<td>
+	
+**CompareType**</td><td>The compare type of the text verification.</td><td>To change from an exact to a partial match, for example. </td>
 </tr>
 <tr>
-	<td>**EnsureStateIsCurrent**</td><td>Whether to explicitly refresh the target element on which the verification is performed.</td><td>To eliminate the need to explicitly refresh the DOM tree in a coded step before the verification. </td>
+<td>
+	
+**EnsureStateIsCurrent**</td><td>Whether to explicitly refresh the target element on which the verification is performed.</td><td>To eliminate the need to explicitly refresh the DOM tree in a coded step before the verification. </td>
 </tr>
 <tr>
-	<td>**ExpectedString**</td><td>The expected string to compare against.</td><td>To change the string to verify. </td>
+<td>
+	
+**ExpectedString**</td><td>The expected string to compare against.</td><td>To change the string to verify. </td>
 </tr>
 <tr>
-	<td>**PropertyName**</td><td>The name of the property being verified.</td><td>To change the property to verify. </td>
+<td>
+	
+**PropertyName**</td><td>The name of the property being verified.</td><td>To change the property to verify. </td>
 </tr>
 <tr>
-	<td>**TagSegmentType**</td><td>The segment of the target element to compare.</td><td>To change which attribute the Verification is based on. </td>
+<td>
+	
+**TagSegmentType**</td><td>The segment of the target element to compare.</td><td>To change which attribute the Verification is based on. </td>
 </tr>
 <tr>
-	<td>**Value**</td><td>Represents the expected value of the property.</td><td>To change the value to verify. </td>
+<td>
+	
+**Value**</td><td>Represents the expected value of the property.</td><td>To change the value to verify. </td>
 </tr>
 <table>
 
@@ -461,18 +650,26 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**CheckInterval**</td><td>The check interval in milliseconds when acting as a Wait.</td><td>To cause the Wait to check its condition more or less frequently.</td>
+<td>
+	
+**CheckInterval**</td><td>The check interval in milliseconds when acting as a Wait.</td><td>To cause the Wait to check its condition more or less frequently.</td>
 </tr>
 <tr>
-	<td>**IsWaitOnly**</td><td>Whether this descriptor can only be a wait.</td><td>(Read only)</td>
+<td>
+	
+**IsWaitOnly**</td><td>Whether this descriptor can only be a wait.</td><td>(Read only)</td>
 </tr>
 <tr>
-	<td>**SupportsWait**</td><td>Whether this verification supports wait.</td><td>(Read only)</td>
+<td>
+	
+**SupportsWait**</td><td>Whether this verification supports wait.</td><td>(Read only)</td>
 </tr>
 <tr>
-	<td>**Timeout**</td><td>The wait time when acting as a wait.</td><td>To increase or decrease the wait time. </td>
+<td>
+	
+**Timeout**</td><td>The wait time when acting as a wait.</td><td>To increase or decrease the wait time. </td>
 </tr>
 <table>
 
-[1]: images/test-step-properties/fig1.png
+
 [2]: images/test-step-properties/fig2.png
diff --git a/docs-teststudiodev/fonts/FontAwesome.otf b/docs-teststudiodev/fonts/FontAwesome.otf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/KendoUIGlyphs.eot b/docs-teststudiodev/fonts/KendoUIGlyphs.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/KendoUIGlyphs.ttf b/docs-teststudiodev/fonts/KendoUIGlyphs.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/KendoUIGlyphs.woff b/docs-teststudiodev/fonts/KendoUIGlyphs.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Bold-webfont.eot b/docs-teststudiodev/fonts/OpenSans-Bold-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Bold-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-Bold-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Bold-webfont.woff b/docs-teststudiodev/fonts/OpenSans-Bold-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Italic-webfont.eot b/docs-teststudiodev/fonts/OpenSans-Italic-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Italic-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-Italic-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Italic-webfont.woff b/docs-teststudiodev/fonts/OpenSans-Italic-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Light-webfont.eot b/docs-teststudiodev/fonts/OpenSans-Light-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Light-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-Light-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Light-webfont.woff b/docs-teststudiodev/fonts/OpenSans-Light-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Regular-webfont.eot b/docs-teststudiodev/fonts/OpenSans-Regular-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Regular-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-Regular-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Regular-webfont.woff b/docs-teststudiodev/fonts/OpenSans-Regular-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.eot b/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.woff b/docs-teststudiodev/fonts/OpenSans-Semibold-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.eot b/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.ttf b/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.woff b/docs-teststudiodev/fonts/OpenSans-SemiboldItalic-webfont.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/WebComponentsIcons.eot b/docs-teststudiodev/fonts/WebComponentsIcons.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/WebComponentsIcons.ttf b/docs-teststudiodev/fonts/WebComponentsIcons.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/WebComponentsIcons.woff b/docs-teststudiodev/fonts/WebComponentsIcons.woff
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/fontawesome-webfont.eot b/docs-teststudiodev/fonts/fontawesome-webfont.eot
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/fonts/fontawesome-webfont.ttf b/docs-teststudiodev/fonts/fontawesome-webfont.ttf
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/CFW.gif b/docs-teststudiodev/icons/CFW.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/Caution.gif b/docs-teststudiodev/icons/Caution.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/CopyCode.gif b/docs-teststudiodev/icons/CopyCode.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/CopyCode_h.gif b/docs-teststudiodev/icons/CopyCode_h.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/LastChild.gif b/docs-teststudiodev/icons/LastChild.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/adm.gif b/docs-teststudiodev/icons/adm.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/adm_arch.gif b/docs-teststudiodev/icons/adm_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/adm_dev.gif b/docs-teststudiodev/icons/adm_dev.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/adm_dev_arch.gif b/docs-teststudiodev/icons/adm_dev_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/alert_caution.gif b/docs-teststudiodev/icons/alert_caution.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/alert_note.gif b/docs-teststudiodev/icons/alert_note.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/alert_security.gif b/docs-teststudiodev/icons/alert_security.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/arch.gif b/docs-teststudiodev/icons/arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/big_adm.gif b/docs-teststudiodev/icons/big_adm.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/big_arch.gif b/docs-teststudiodev/icons/big_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/big_dev.gif b/docs-teststudiodev/icons/big_dev.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/big_kw.gif b/docs-teststudiodev/icons/big_kw.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/box.gif b/docs-teststudiodev/icons/box.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/collall.gif b/docs-teststudiodev/icons/collall.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/collapse.gif b/docs-teststudiodev/icons/collapse.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/collapse_all.gif b/docs-teststudiodev/icons/collapse_all.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/copycodeHighlight.gif b/docs-teststudiodev/icons/copycodeHighlight.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/dev.gif b/docs-teststudiodev/icons/dev.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/dev_arch.gif b/docs-teststudiodev/icons/dev_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/dropdown.gif b/docs-teststudiodev/icons/dropdown.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/dropdownHover.gif b/docs-teststudiodev/icons/dropdownHover.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/drpdown.gif b/docs-teststudiodev/icons/drpdown.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/drpdown_orange.gif b/docs-teststudiodev/icons/drpdown_orange.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/drpdown_orange_up.gif b/docs-teststudiodev/icons/drpdown_orange_up.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/drpup.gif b/docs-teststudiodev/icons/drpup.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/exp.gif b/docs-teststudiodev/icons/exp.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/expall.gif b/docs-teststudiodev/icons/expall.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/expand_all.gif b/docs-teststudiodev/icons/expand_all.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/filter1a.gif b/docs-teststudiodev/icons/filter1a.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/filter1c.gif b/docs-teststudiodev/icons/filter1c.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/footer.gif b/docs-teststudiodev/icons/footer.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/gradient.gif b/docs-teststudiodev/icons/gradient.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/greencheck.gif b/docs-teststudiodev/icons/greencheck.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/greychck.gif b/docs-teststudiodev/icons/greychck.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/header_prev_next.jpg b/docs-teststudiodev/icons/header_prev_next.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/header_sql_tutorial_blank.jpg b/docs-teststudiodev/icons/header_sql_tutorial_blank.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/header_sql_tutorial_logo.GIF b/docs-teststudiodev/icons/header_sql_tutorial_logo.GIF
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw.gif b/docs-teststudiodev/icons/kw.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_adm.gif b/docs-teststudiodev/icons/kw_adm.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_adm_arch.gif b/docs-teststudiodev/icons/kw_adm_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_adm_dev.gif b/docs-teststudiodev/icons/kw_adm_dev.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_adm_dev_arch.gif b/docs-teststudiodev/icons/kw_adm_dev_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_arch.gif b/docs-teststudiodev/icons/kw_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_dev.gif b/docs-teststudiodev/icons/kw_dev.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/kw_dev_arch.gif b/docs-teststudiodev/icons/kw_dev_arch.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/load.gif b/docs-teststudiodev/icons/load.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/load_hover.gif b/docs-teststudiodev/icons/load_hover.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/note.gif b/docs-teststudiodev/icons/note.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pencil.GIF b/docs-teststudiodev/icons/pencil.GIF
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privclass.gif b/docs-teststudiodev/icons/privclass.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privdelegate.gif b/docs-teststudiodev/icons/privdelegate.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privenum.gif b/docs-teststudiodev/icons/privenum.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privenumeration.gif b/docs-teststudiodev/icons/privenumeration.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privevent.gif b/docs-teststudiodev/icons/privevent.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privextension.gif b/docs-teststudiodev/icons/privextension.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privfield.gif b/docs-teststudiodev/icons/privfield.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privinterface.gif b/docs-teststudiodev/icons/privinterface.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privmethod.gif b/docs-teststudiodev/icons/privmethod.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privproperty.gif b/docs-teststudiodev/icons/privproperty.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/privstructure.gif b/docs-teststudiodev/icons/privstructure.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protclass.gif b/docs-teststudiodev/icons/protclass.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protdelegate.gif b/docs-teststudiodev/icons/protdelegate.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protenum.gif b/docs-teststudiodev/icons/protenum.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protenumeration.gif b/docs-teststudiodev/icons/protenumeration.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protevent.gif b/docs-teststudiodev/icons/protevent.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protextension.gif b/docs-teststudiodev/icons/protextension.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protfield.gif b/docs-teststudiodev/icons/protfield.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protinterface.gif b/docs-teststudiodev/icons/protinterface.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protmethod.gif b/docs-teststudiodev/icons/protmethod.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protoperator.gif b/docs-teststudiodev/icons/protoperator.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protproperty.gif b/docs-teststudiodev/icons/protproperty.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/protstructure.gif b/docs-teststudiodev/icons/protstructure.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubclass.gif b/docs-teststudiodev/icons/pubclass.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubdelegate.gif b/docs-teststudiodev/icons/pubdelegate.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubenum.gif b/docs-teststudiodev/icons/pubenum.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubenumeration.gif b/docs-teststudiodev/icons/pubenumeration.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubevent.gif b/docs-teststudiodev/icons/pubevent.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubextension.gif b/docs-teststudiodev/icons/pubextension.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubfield.gif b/docs-teststudiodev/icons/pubfield.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubinterface.gif b/docs-teststudiodev/icons/pubinterface.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubmethod.gif b/docs-teststudiodev/icons/pubmethod.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/puboperator.gif b/docs-teststudiodev/icons/puboperator.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubproperty.gif b/docs-teststudiodev/icons/pubproperty.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/pubstructure.gif b/docs-teststudiodev/icons/pubstructure.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/requirements1a.gif b/docs-teststudiodev/icons/requirements1a.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/requirements1c.gif b/docs-teststudiodev/icons/requirements1c.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/save.gif b/docs-teststudiodev/icons/save.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/save_hover.gif b/docs-teststudiodev/icons/save_hover.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/security.gif b/docs-teststudiodev/icons/security.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/seealso1a.gif b/docs-teststudiodev/icons/seealso1a.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/seealso1c.gif b/docs-teststudiodev/icons/seealso1c.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/slMobile.gif b/docs-teststudiodev/icons/slMobile.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/static.gif b/docs-teststudiodev/icons/static.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/icons/xna.gif b/docs-teststudiodev/icons/xna.gif
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/EnableDisableJustMock.png b/docs-teststudiodev/images/EnableDisableJustMock.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/anchor.png b/docs-teststudiodev/images/anchor.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/avatar-ninja.svg b/docs-teststudiodev/images/avatar-ninja.svg
new file mode 100755
index 00000000..d98c1b20
--- /dev/null
+++ b/docs-teststudiodev/images/avatar-ninja.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="109.579" height="100" viewBox="0 0 109.579 100"><defs><style>.a{fill:#a3d8f1;}.b{fill:#fff;}.c{fill:#e3f6ff;}.d{fill:#8174f2;}.e{clip-path:url(#a);}.f,.h,.i,.k{fill:none;}.f{stroke:#0c1b38;stroke-width:30px;}.f,.i,.k{stroke-linecap:round;}.f,.h{stroke-miterlimit:10;}.g{fill:#4f5d6c;}.h{stroke:#000;stroke-width:24.468px;}.i{stroke:#0c1121;stroke-width:20.645px;}.i,.k{stroke-linejoin:round;}.j{fill:#0c1121;}.k{stroke:#14254c;stroke-width:45.877px;}.l{fill:#0c1b38;}.m{fill:#e9ac6a;}.n{fill:#e26841;}</style><clipPath id="a"><ellipse class="a" cx="50" cy="50" rx="50" ry="50" transform="translate(-11251.149 -21710)"/></clipPath></defs><path class="b" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><path class="c" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><g transform="translate(0 12.775)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g class="e" transform="translate(11260.729 21710)"><g transform="translate(-12096.358 -23981.338)"><path class="f" d="M3158.423,2368.839c36.843.145,65.382-23.7,68.744-50.983,3-24.348-15.059-43.243-18.055-46.286" transform="translate(-2234.18 -19.121)"/><g transform="translate(939.33 2257.389)"><path class="g" d="M3203.488,2283.094l7.821,11.323-.855,1.8-20.468,1.627-11.668-16.894.855-1.8,13.4-1.065Z" transform="translate(-3178.317 -2278.085)"/></g><g transform="translate(950.734 2192.443)"><path class="g" d="M3222.208,2230.646l14.987-31.541a2.648,2.648,0,0,0-1.258-3.526l-6.063-2.879a2.647,2.647,0,0,0-3.528,1.252l-32.99,69.127,10.849,5.154,6.518-13.412Z" transform="translate(-3193.356 -2192.443)"/></g><g transform="translate(951.545 2227.636)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.991,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 22.12) rotate(-65.013)"/></g><line class="h" x1="0.724" y2="27.18" transform="translate(844.735 2493.343)"/><path d="M3155.778,2444.706l1.234-32.591a34.077,34.077,0,0,0-38.951-35.012h0a34.077,34.077,0,0,0-27.836,43.189l9.06,31.33a28.825,28.825,0,0,0,30.725,20.658h0A28.824,28.824,0,0,0,3155.778,2444.706Z" transform="translate(-2217.373 -44.536)"/><path class="i" d="M2905.35,2587.494l-49.786,32.326" transform="translate(-2160.994 -95.464)"/><path class="j" d="M3142.522,2628.677a7.968,7.968,0,0,0,8.055,8.435l3.028-.039,27.262-.343a4.921,4.921,0,0,0,.692-9.783l-14.5-2.532-14.975-3.078a7.969,7.969,0,0,0-9.56,7.34Z" transform="translate(-2230.335 -103.603)"/><path class="j" d="M2851.56,2628.677a7.969,7.969,0,0,1-8.055,8.435l-3.028-.039-27.262-.343a4.921,4.921,0,0,1-.693-9.783l14.5-2.532,14.975-3.078a7.968,7.968,0,0,1,9.56,7.34Z" transform="translate(-2149.586 -103.603)"/><path class="i" d="M3210.51,2580.636q-9.805,7.145-20.237,14.306-19.106,13.1-37.478,24.294" transform="translate(-2232.82 -93.807)"/><path class="k" d="M3153.983,2510.447c2.631-.136,5.669-.226,9.057-.2,5.714.044,20.339.235,34.771,4.322,13.86,3.926,28.827,8.165,31.9,17.693,3.67,11.374-9.988,29.089-34.05,42.144" transform="translate(-2233.107 -76.797)"/><path class="k" d="M3064.752,2503.885a530.633,530.633,0,0,0-167.838,72.336" transform="translate(-2170.987 -75.261)"/><g transform="translate(900.392 2433.461)"><path class="j" d="M3126.972,2510.262" transform="translate(-3126.972 -2510.262)"/></g><path d="M3177.856,2483.313l-61.336-19.153h0q-15.026,5.272-30.776,10.39-18.815,6.107-36.943,11.419a72.634,72.634,0,0,0,129.055-2.656Z" transform="translate(-2207.69 -65.661)"/><rect class="d" width="57.81" height="19.325" transform="matrix(-0.988, 0.157, -0.157, -0.988, 942.407, 2422.056)"/><g transform="translate(835.308 2508.631)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.992,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 0.347) rotate(-0.814)"/></g><path class="f" d="M3089.63,2423.256a159.413,159.413,0,0,0-27.3,48.023,161.1,161.1,0,0,0-7.566,76.309" transform="translate(-2208.744 -55.776)"/><g transform="translate(835.63 2284.113)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g transform="translate(873.087 2289.57)"><path class="l" d="M3114.193,2320.557l-2.984.175a21.267,21.267,0,0,0-19.861,23.857l2.83,22.75a21.268,21.268,0,0,0,22.349,18.605h0a21.268,21.268,0,0,0,20.024-21.088l.154-22.924A21.268,21.268,0,0,0,3114.193,2320.557Z" transform="translate(-3091.019 -2320.52)"/><rect class="d" width="45.527" height="11.326" transform="translate(46.111 27.879) rotate(176.647)"/><rect class="m" width="39.681" height="11.634" rx="5.817" transform="translate(43.547 34.093) rotate(176.647)"/><path class="n" d="M3117.6,2364.1l5.041-.3-.568-9.691Z" transform="translate(-3097.402 -2328.638)"/><g transform="translate(7.384 26.937)"><rect class="b" width="6.105" height="3.243" rx="1.622" transform="matrix(-0.998, 0.058, -0.058, -0.998, 6.284, 4.693)"/><rect class="b" width="6.105" height="3.243" rx="1.622" transform="translate(31.121 3.237) rotate(176.647)"/></g><circle cx="1.643" cy="1.643" r="1.643" transform="translate(7.477 28.64)"/><circle cx="1.643" cy="1.643" r="1.643" transform="translate(32.314 27.185)"/></g></g></g></svg>
\ No newline at end of file
diff --git a/docs-teststudiodev/images/close.png b/docs-teststudiodev/images/close.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/column.png b/docs-teststudiodev/images/column.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/external.png b/docs-teststudiodev/images/external.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/file-white.png b/docs-teststudiodev/images/file-white.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/file.png b/docs-teststudiodev/images/file.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/folder-close.png b/docs-teststudiodev/images/folder-close.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/folder-open.png b/docs-teststudiodev/images/folder-open.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/important.png b/docs-teststudiodev/images/important.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/menu.png b/docs-teststudiodev/images/menu.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/minus.png b/docs-teststudiodev/images/minus.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/ninja-icon.png b/docs-teststudiodev/images/ninja-icon.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/ninja-no-results.svg b/docs-teststudiodev/images/ninja-no-results.svg
new file mode 100644
index 00000000..5d84ade5
--- /dev/null
+++ b/docs-teststudiodev/images/ninja-no-results.svg
@@ -0,0 +1,47 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" id="Layer_1" x="0px" y="0px" style="enable-background:new 0 0 2000 2000;" height="150px" width="106px" xml:space="preserve" viewBox="631.99 547.8 788.26 904.27">
+	<style type="text/css">
+		.st0{fill:none;stroke:#0B1122;stroke-width:47.0486;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st1{fill:#0B1122;}
+		.st2{fill:none;stroke:#14254C;stroke-width:104.5525;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st3{fill:none;stroke:#0C1B38;stroke-width:78.4143;stroke-linecap:round;stroke-miterlimit:10;}
+		.st4{fill:#8174F2;}
+		.st5{fill:#0C1B38;}
+		.st6{fill:#E7AA6A;}
+		.st7{fill:#E26841;}
+		.st8{fill:#EEF5FF;}
+		.st9{fill:#4F5D6C;}
+	</style>
+	<g>
+		<path class="st0" d="M723.7,1237.5c11.8,47.5,23.5,95,35.3,142.5"/>
+		<path class="st1" d="M788.6,1383c1,16.7-12.4,30.8-29.2,30.6l-11-0.1l-98.8-1.2c-8.6-0.1-16-6.4-17.4-15.1   c-1.5-9.7,5.2-18.8,14.9-20.4l52.6-9.2l54.3-11.2C771.2,1352.8,787.6,1365.4,788.6,1383L788.6,1383z"/>
+		<path class="st2" d="M1034.1,1192.7c-103-137.5-230.5-179.8-283.3-141.7c-56.8,41-26.1,174.6-24,183.3"/>
+		<path class="st3" d="M1010.1,863.6c-105.4-13.1-192.5,68.8-191.7,156.2c0.7,74,64.5,144.9,152.1,154.2"/>
+		<path class="st3" d="M1108,863.6c105.4-13.1,192.5,68.8,191.7,156.2c-0.7,74-64.5,144.9-152.1,154.2"/>
+		<path d="M1204.6,1064.3l4.5-124.8c3-81.4-68-145.8-147.9-134.2l0,0c-77.6,11.3-127.2,89.2-105.4,165.2l34.5,120   c14.8,51.4,63.9,84.8,116.6,79.2h0C1161,1164,1202.6,1119.1,1204.6,1064.3z"/>
+		<path class="st1" d="M932.5,1322.1c-13.7-9.6-32.7-5.6-41.4,8.8l-5.6,9.4l-50.8,84.8c-4.4,7.3-3,17,3.7,22.7   c7.5,6.4,18.8,5.5,25.1-2L899,1406l38-40.3C949.1,1352.8,947,1332.2,932.5,1322.1L932.5,1322.1z"/>
+		<path class="st0" d="M1163.2,1330c-29.1,3.2-59,6.1-89.4,8.6c-55.8,4.5-109.7,7.4-161.7,8.9"/>
+		<path class="st2" d="M1139.4,1174.4c22.6-0.8,55-0.5,93.6,4.7c53.8,7.3,81.3,10.5,103.1,31.2c20.8,19.8,37.3,54.9,30.2,79.4   c-22.1,75.8-274.5,59.3-297.1,57.7"/>
+		<g>
+			<path class="st4" d="M1150.3,749.8c28.6-11.3,48.6-9.1,61.5-11.9c23.7-5.2,52.3-34.8,72.7-143.2c-16.9-4.8-33.7-9.6-50.6-14.4    c-3.8,85.1-25.7,115-46.6,125.5c-9.5,4.8-22.5,8.2-39.6,20.4c-20,14.3-30.8,33.5-36.8,47.4    C1119.2,766.5,1132.4,756.9,1150.3,749.8z"/>
+			<path class="st4" d="M1208.2,565c-14.7-5.7-29.5-11.5-44.2-17.2c7.3,59.9-6.2,93.7-20.4,113.6c-9.8,13.7-22.1,26.5-31.2,50.4    c-8.4,21.8-5.8,43-2.5,57.1c5.3-14.5,14.9-34.5,33-52.6c16.4-16.5,28.1-23.1,37.4-31.1C1197.7,670,1214.9,638.4,1208.2,565z"/>
+		</g>
+		<g>
+			<path class="st5" d="M1080.4,711.3l-10.8,0.4c-44.5,1.5-78.5,40.3-74.2,84.6l8.2,82.7c4,40.4,38.7,70.8,79.3,69.5h0    c40.6-1.3,73.2-34,74.5-74.6l2.7-83.1C1161.4,746.3,1124.9,709.8,1080.4,711.3z"/>
+			
+				<rect x="995.9" y="795.4" transform="matrix(-0.9994 3.316386e-02 -3.316386e-02 -0.9994 2183.395 1595.6785)" class="st4" width="165" height="41.1"/>
+			<path class="st6" d="M1012.5,860.6l132.4-4.4c3.1-0.1,5.6-2.7,5.5-5.9l-1-30.8c-0.1-3.1-2.7-5.6-5.9-5.5l-132.4,4.4    c-3.1,0.1-5.6,2.7-5.5,5.9l1,30.8C1006.7,858.2,1009.3,860.7,1012.5,860.6z"/>
+			<polygon class="st7" points="1065.8,858.8 1084.1,858.2 1082.9,823   "/>
+			<g>
+				<path class="st8" d="M1021.8,850.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1020.2,849.7,1021,850.4,1021.8,850.4z"/>
+				<path class="st8" d="M1112,847.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1110.4,846.7,1111.1,847.4,1112,847.4z"/>
+			</g>
+			<circle cx="1031.7" cy="849.1" r="6"/>
+			<circle cx="1121.8" cy="846.1" r="6"/>
+		</g>
+		<g>
+			<rect x="906.3" y="1031.2" class="st9" width="371.7" height="269.2"/>
+			<rect x="906.3" y="1293.9" width="371.7" height="24.1"/>
+		</g>
+		<path class="st8" d="M1101.4,1157.7l-14.7-19.5l-2.1,17.8l-19.5,14.7l17.8,2.1l14.7,19.5l2.1-17.8l19.5-14.7L1101.4,1157.7z    M1091.7,1168.6c-1.8-0.2-3.1-1.9-2.9-3.7c0.2-1.8,1.9-3.1,3.7-2.9c1.8,0.2,3.1,1.9,2.9,3.7   C1095.2,1167.5,1093.5,1168.8,1091.7,1168.6z"/>
+	</g>
+</svg>
diff --git a/docs-teststudiodev/images/pdf-cover.png b/docs-teststudiodev/images/pdf-cover.png
new file mode 100644
index 00000000..ce9967ef
Binary files /dev/null and b/docs-teststudiodev/images/pdf-cover.png differ
diff --git a/docs-teststudiodev/images/plus.png b/docs-teststudiodev/images/plus.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/add-new-test-wizard.png b/docs-teststudiodev/images/quickstart/add-new-test-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/add-new-test.png b/docs-teststudiodev/images/quickstart/add-new-test.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/attach-to-existing.png b/docs-teststudiodev/images/quickstart/attach-to-existing.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/configure-desktop-wizard.png b/docs-teststudiodev/images/quickstart/configure-desktop-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/configure-desktop.png b/docs-teststudiodev/images/quickstart/configure-desktop.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/configure-wpf-wizard.png b/docs-teststudiodev/images/quickstart/configure-wpf-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/configure-wpf.png b/docs-teststudiodev/images/quickstart/configure-wpf.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/create-project-vs-2019.png b/docs-teststudiodev/images/quickstart/create-project-vs-2019.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/create-project.png b/docs-teststudiodev/images/quickstart/create-project.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/elements-explorer-from-menu.png b/docs-teststudiodev/images/quickstart/elements-explorer-from-menu.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/elements-explorer.png b/docs-teststudiodev/images/quickstart/elements-explorer.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/enter-url.png b/docs-teststudiodev/images/quickstart/enter-url.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/execute-test-button.png b/docs-teststudiodev/images/quickstart/execute-test-button.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/failed-step-details.png b/docs-teststudiodev/images/quickstart/failed-step-details.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/failed-step.png b/docs-teststudiodev/images/quickstart/failed-step.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/name-of-project-vs-2019.png b/docs-teststudiodev/images/quickstart/name-of-project-vs-2019.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/name-of-project.png b/docs-teststudiodev/images/quickstart/name-of-project.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/open-new-test.png b/docs-teststudiodev/images/quickstart/open-new-test.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/quick-execution-log-copy.png b/docs-teststudiodev/images/quickstart/quick-execution-log-copy.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/quick-execution-log.png b/docs-teststudiodev/images/quickstart/quick-execution-log.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/quick-execution-overall-results.png b/docs-teststudiodev/images/quickstart/quick-execution-overall-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/record-button.png b/docs-teststudiodev/images/quickstart/record-button.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/recorded-steps.png b/docs-teststudiodev/images/quickstart/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl-failed-results.png b/docs-teststudiodev/images/quickstart/vs-test-expl-failed-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl-group-tests.png b/docs-teststudiodev/images/quickstart/vs-test-expl-group-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl-results.png b/docs-teststudiodev/images/quickstart/vs-test-expl-results.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl-run-selected-tests.png b/docs-teststudiodev/images/quickstart/vs-test-expl-run-selected-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl-run-tests.png b/docs-teststudiodev/images/quickstart/vs-test-expl-run-tests.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/vs-test-expl.png b/docs-teststudiodev/images/quickstart/vs-test-expl.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/quickstart/web-test-by-default.png b/docs-teststudiodev/images/quickstart/web-test-by-default.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/search-24.png b/docs-teststudiodev/images/search-24.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/images/search.png b/docs-teststudiodev/images/search.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/introduction.md b/docs-teststudiodev/introduction.md
index 84a0194b..285fc088 100644
--- a/docs-teststudiodev/introduction.md
+++ b/docs-teststudiodev/introduction.md
@@ -18,7 +18,7 @@ Releases can be stressful especially with the market’s high demand for continu
 Test Automation can replace error-prone, repetitive and tedious manual testing tasks, with minimal efforts to maintain sustainable levels of software quality on schedule.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## How Test Studio Dev Edition Helps You in Automation Testing
diff --git a/docs-teststudiodev/prerequisites/activate-license.md b/docs-teststudiodev/prerequisites/activate-license.md
index d51c9253..49278644 100644
--- a/docs-teststudiodev/prerequisites/activate-license.md
+++ b/docs-teststudiodev/prerequisites/activate-license.md
@@ -14,7 +14,7 @@ After installing Test Studio Dev, you will be asked to activate your license. Du
 > All users, both trial and purchased, will need to activate their product after installation before they can begin using the tool.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Activate Test Studio Dev License 
@@ -53,29 +53,29 @@ The following steps demonstrate how to manually activate Test Studio on a machin
 > 
 > While the machine that runs Test Studio may not be connected to the Internet, you need access on another device to the Internet and our website to complete the activation process.
 
-1.Select __Activate Manually__.
+1. Select __Activate Manually__.
 
 ![Activate Manually](images/installation/manual-activation.png)
 
-2.Copy your machine key from the __Machine Info Key__ field for later use.
+2. Copy your machine key from the __Machine Info Key__ field for later use.
 
 ![Machine Key](images/installation/fig3.png)
 
-3.Navigate to the <a href="https://www.telerik.com/account/your-products/testing-tools-manage-license-keys" target="_blank">License Keys Management Form</a> and click the _Add a key_ button.
+3. Navigate to the <a href="https://www.telerik.com/account/your-products/testing-tools-manage-license-keys" target="_blank">License Keys Management Form</a> and click the _Add a key_ button.
 
 ![License Keys Management Form](images/installation/fig4.png)
 
-4.Select Product from the drop down menu. Input your machine info key within the provided field, the machine name and friendly name, then click the Generate Key button. 
+4. Select Product from the drop down menu. Input your machine info key within the provided field, the machine name and friendly name, then click the Generate Key button. 
 
 ![Select Product](images/installation/fig5.png)
 
 > There are reserved words that cannot be used for Machine key, Machine name and Friendly name. The words are **telerik**, **admin**, **administrator**, **sitefinity**, **icenium**, **kendo**, **kendoui** and **moderator**. 
 
-5.A confirmation appears that the Key was successfully created. Locate the key and click __View key__.
+5. A confirmation appears that the Key was successfully created. Locate the key and click __View key__.
 
 ![Copy key](images/installation/view-key.png)
 
-6.Select and copy the registration key. Then paste it within the respective field in Test Studio Dev Activation wizard, then click __Activate__.
+6. Select and copy the registration key. Then paste it within the respective field in Test Studio Dev Activation wizard, then click __Activate__.
 
 ![Activate](images/installation/fig7.png)
 
diff --git a/docs-teststudiodev/prerequisites/calibrate-browsers.md b/docs-teststudiodev/prerequisites/calibrate-browsers.md
index 2b4772a9..d030383d 100644
--- a/docs-teststudiodev/prerequisites/calibrate-browsers.md
+++ b/docs-teststudiodev/prerequisites/calibrate-browsers.md
@@ -7,36 +7,13 @@ tags: configure. browsers, calibrate
 published: True
 position: 3
 ---
-<style>
-p.trigger{
-	margin-bottom:7px;
-	margin-top:-5px;
-	font-size:1.8rem;
-
-}
-
-	.toggle_container{
-	margin-bottom:10px;
-}
-
-	.toggle_container p{
-	margin:0px;
-}
-
-	.toggle_container{
-    
-	clear: both;
-	font-size:100%;
-}
-
-</style>
 
 # Calibrate Browsers
 
 A specific set of settings is required to enable each of the supported browsers for test recording and execution with Test Studio Dev and this is called __Browser Calibration__. Some of the browsers also require the installation of an extension.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Built-in Calibration
@@ -54,424 +31,331 @@ If a browser is not yet configured the button allows you to calibrate it.
 ![Calibrate](images/calibrate.png)
 
 > __Note!__
-> <br>
-> <br>
+> 
+> 
 > During browser calibration __Test Studio Dev automatically closes__ all currently running browser instances. Ensure there is no important information you might lose if browser gets closed before proceeding with calibration</br></br>
 
 > __Tip__
-> <br>
-> <br>
+> 
+> 
 > You can check all settings applied from the calibration in the <a href="#manual-settings-to-configure-a-browser">Manual Configuration</a> section below (click the + sign to expand it).
 
 ## Enable Chrome and Edge Chromium for Automation 
 
 Once Chrome and Edge Chromium browsers are __calibrated you can continue with recording and executing__ the automated tests. 
 
-### Enable Chrome and Edge Chromium for Automation with Extension (Optional)
-
-By default Test Studio Dev projects are __set to use Chrome and Edge Chromium without extension__. Along with that, there is the option to run these two browsers automation with the help of an extension. The <a href="https://chrome.google.com/webstore/detail/progress-test-studio-exte/gegcllkonmciadpdldechnepmjildoan" target="_blank">__Progress Telerik Test Studio Extension__</a> is officially distributed in the Chrome web store and is available for download and installation (Edge Chromium supports adding extensions from the Chrome store).
-
-If you choose to use Chrome for recording and execution with the extension, you need to __change a setting in the Test Studio Dev project__. The <a href="/features/project-settings/overview" target="_blank">project setting is listed under the __Browsers__ tab</a> and is named __Use browser extension(Chrome/Edge Chromium)__. This option is disabled by default, but you can __check the checkbox__ to set Test Studio Dev to __start the Chrome/Edge Chromium browser for this project with the extensions__.
-
-![Enable UseBrowserExtension](images/browser-config/disable-extension.png)
-
 ## Enable Firefox for Automation
 
 Firefox browser requires an extension for the purposes of automation testing with __Test Studio Dev__.
 
-The __Firefox__ extension can be found in the Firefox Add-ons Page - <a href="https://addons.mozilla.org/en-US/firefox/addon/progress-test-studio-extension/", target=blank>__Progress Test Studio Extension__</a>.
+The __Firefox__ extension can be found in the Firefox Add-ons Page - [Progress Test Studio Extension](https://addons.mozilla.org/en-US/firefox/addon/progress-test-studio-extension/).
 
 ## Settings Applied from the Calibration
 
-
 ### Chrome
 
 > <p>If your Chrome browser has an active <strong>Google Apps session</strong> (for example, you are logged into GMail), automatic calibration will not work as expected. To use automatic configuration, log out of your Google account first.</p><p></p>
 <p></p>
 
-You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).<br><br>
+You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).
 
-<p><hr></p>
-<p></p>
-<p></p>
-
-<p></p>
-<p class="trigger"><a name="Manual_Configuration" style="color:black; text-decoration: none;";> Manual Configuration <span id="d" style="color:#28a1e2";> + </span></a></p>
-
-<div class="toggle_container">
-<div class="block">
-
-<hr/>
-<br>
+### Manual Configuration
 
-<h3>Enable Extensions</h3>
+#### Enable Extensions
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> located in the upper right corner of the browser <strong>More tools > Extensions</strong>.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> located in the upper right corner of the browser <strong>More tools > Extensions</strong>.
 
-2.&nbsp; Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.<br><br>
+2. Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.
 
-<img src="images/chrome/fig2.png" alt="Extensions"><br><br>
+<img src="images/chrome/fig2.png" alt="Extensions">
 
-<h3>Zoom Level Set to 100%</h3>
+#### Zoom Level Set to 100%
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.
 
-2.&nbsp; Use the plus (+) and minus (-) buttons next to <strong>Zoom</strong> to set it to 100% (or use the keyboard shortcut: Ctrl + 0).<br><br> 
+2. Use the plus (+) and minus (-) buttons next to <strong>Zoom</strong> to set it to 100% (or use the keyboard shortcut: Ctrl + 0). 
 
-<img src="images/chrome/fig3.png" alt="Zoom"><br><br>
+<img src="images/chrome/fig3.png" alt="Zoom">
 
-<h3>Enable File Downloads</h3>
+#### Enable File Downloads
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-3.&nbsp; Scroll to the bottom and click <strong>Advanced</strong>.<br><br>
+3. Scroll to the bottom and click <strong>Advanced</strong>.
 
-4.&nbsp; Locate the <strong>Downloads</strong> section.<br><br>
+4. Locate the <strong>Downloads</strong> section.
 
-5.&nbsp; Enable <strong>Ask where to save each file before downloading</strong>.<br><br>
+5. Enable <strong>Ask where to save each file before downloading</strong>.
 
-<img src="images/chrome/fig4.png" alt="Downloads"><br><br>
+<img src="images/chrome/fig4.png" alt="Downloads">
 
-<h3>Disable Pop-up Blocker</h3>
+#### Disable Pop-up Blocker
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-3.&nbsp; Scroll to the bottom and click <strong>Advanced</strong>.<br><br>
+3. Scroll to the bottom and click <strong>Advanced</strong>.
 
-4.&nbsp; Locate the <strong>Privacy and security</strong> section.<br><br>
+4. Locate the <strong>Privacy and security</strong> section.
 
-5.&nbsp; Click <strong>Content Settings</strong>.<br><br>
+5. Click <strong>Content Settings</strong>.
 
-<img src="images/chrome/fig5.png" alt="Pop up blocker"><br><br>
+<img src="images/chrome/fig5.png" alt="Pop up blocker">
 
-6.&nbsp; Under <strong>Popups</strong> section enable <strong>Allowed</strong>.<br><br>
+6. Under <strong>Popups</strong> section enable <strong>Allowed</strong>.
 
-<img src="images/chrome/fig6.png" alt="Pop up blocker"><br><br>
+<img src="images/chrome/fig6.png" alt="Pop up blocker">
 
-<h3>Allow All Sites to Run JavaScript</h3>
+#### Allow All Sites to Run JavaScript
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner.
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br> <br>
+2. Select <strong>Settings</strong> from the drop-down menu. 
 
-3.&nbsp; Scroll to the bottom and click <strong>Advanced</strong>.<br> <br>
+3. Scroll to the bottom and click <strong>Advanced</strong>. 
 
-4.&nbsp; Locate the <strong>Privacy and security</strong> section. <br> <br>
+4. Locate the <strong>Privacy and security</strong> section.  
 
-5.&nbsp; Click <strong>Content Settings</strong>.<br><br>
+5. Click <strong>Content Settings</strong>.
 
-6.&nbsp; Under <strong>JavaScript</strong> enable <strong>Allowed</strong>.<br><br>
+6. Under <strong>JavaScript</strong> enable <strong>Allowed</strong>.
 
-<img src="images/chrome/fig7.png" alt="Allow JavaScript"><br><br>
+<img src="images/chrome/fig7.png" alt="Allow JavaScript">
 
-<h3>Unblock Third-Party Cookies and Site Data</h3>
+#### Unblock Third-Party Cookies and Site Data
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner <strong>Settings > Advanced > Privacy and security > Content Settings > Cookies </strong>.<br><br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner <strong>Settings > Advanced > Privacy and security > Content Settings > Cookies </strong>.
 
-2.&nbsp; Enable <strong>Allow sites to save and read cookie data (recommended)</strong>.<br><br>
+2. Enable <strong>Allow sites to save and read cookie data (recommended)</strong>.
 
-3.&nbsp; Disable <strong>Block third-party cookies</strong>.<br><br>
+3. Disable <strong>Block third-party cookies</strong>.
 
-<img src="images/chrome/fig8.png" alt="Allow Cookies"><br><br>
+<img src="images/chrome/fig8.png" alt="Allow Cookies">
 
-<h3>Allow all Sites to Download Multiple Files Automatically</h3>
+#### Allow all Sites to Download Multiple Files Automatically
 
-1.&nbsp; Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner <strong>> Settings > Advanced > Privacy and security > Content Settings</strong>.<br> <br>
+1. Click on <img src="images/chrome/fig1.png" alt="chrome settings button"> in the upper right corner <strong>> Settings > Advanced > Privacy and security > Content Settings</strong>. 
 
-2.&nbsp; Under <strong>Automatic Downloads</strong> section enable <strong>Allow all sites to download multiple files automatically</strong> .<br><br>
+2. Under <strong>Automatic Downloads</strong> section enable <strong>Allow all sites to download multiple files automatically</strong> .
 
-<img src="images/chrome/fig9.png" alt="Automatic Download"><br><br>
+<img src="images/chrome/fig9.png" alt="Automatic Download">
 
-<h3>Disable Web Security</h3>
+#### Disable Web Security
 
-<p>1. Open the Default Chrome User data folder under the your Windows account - "C:\Users\[WindowsUser]\AppData\Local\Google\Chrome\User Data\Default" and locate the <strong>Preferences</strong> file.</p><br>
+1. Open the Default Chrome User data folder under the your Windows account - "C:\Users\[WindowsUser]\AppData\Local\Google\Chrome\User Data\Default" and locate the <strong>Preferences</strong> file.
 
-<p>2. Open it with a text editor and search for "webkit". If there is no such preference in the file, add the following at the bottom of the file:</p><br>
+2. Open it with a text editor and search for "webkit". If there is no such preference in the file, add the following at the bottom of the file:
 
-<style>
-.code {
-  background-color: #FFFFFF;    
-  text-align: left;
-  text-indent: 50px;
-  color: #000000;
-}
-</style>
+````
+~"webkit":{"webprefs":{"web_security_enabled":false}}
+````
 
-<div class="code">
-    <p>"webkit":{"webprefs":{"web_security_enabled":false}}</p>
-</div>
-<br>
-<p>If the "webkit" preference already exists in the <strong>Preferences</strong> file and has any value in the "webprefs", you can add the web security as follows:</p>
-<br>
-<div class="code">
-    <p>Existing values listed in the file:</p>
-    <p>"webkit":{"webprefs":{"minimum_font_size":6}}</p><br>
-    <p>The file after adding the web security:</p>
-    <p>"webkit":{"webprefs":{"minimum_font_size":6, "web_security_enabled":false}}</p>
-</div>
+If the "webkit" preference already exists in the <strong>Preferences</strong> file and has any value in the "webprefs", you can add the web security as follows:
 
-<hr/>
-
-</div>
-</div>
-<p><hr></p>
-<p></p>
-<p></p>
+````
+Existing values listed in the file:
+"webkit":{"webprefs":{"minimum_font_size":6}}
+The file after adding the web security:
+"webkit":{"webprefs":{"minimum_font_size":6, "web_security_enabled":false}}
+````
 
 ### Edge Chromium
 
-You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).<br><br>
-
-<p></p>
-<p></p>
-<p><hr></p>
-<p></p>
-<p></p>
-
-<p class="trigger"><a name="Manual_Configuration" style="color:black; text-decoration: none;";> Manual Configuration <span id="d" style="color:#28a1e2";> + </span></a></p>
-
-<div class="toggle_container">
-<div class="block">
-<hr/>
-<br>
-
-<h3>Enable Extensions</h3>
+You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser <strong>Settings -> Extensions</strong>.<br><br>
+### Manual Configuration
 
-2.&nbsp; Ensure that the <strong>Progress Telerik Test Studio Extension</strong> is enabled.<br><br>
+#### Enable Extensions
 
-<img src="images/edge-chromium/fig2.png" alt="Extensions"><br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser <strong>Settings -> Extensions</strong>.
 
-<h3>Zoom Level Set to 100%</h3>
+2. Ensure that the <strong>Progress Telerik Test Studio Extension</strong> is enabled.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig2.png" alt="Extensions">
 
-2.&nbsp; Use the plus (+) and minus (-) buttons next to <strong>Zoom</strong> to set it to 100%.<br><br> 
+#### Zoom Level Set to 100%
 
-<img src="images/edge-chromium/fig3.png" alt="Zoom"><br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-<h3>Enable File Downloads</h3>
+2. Use the plus (+) and minus (-) buttons next to <strong>Zoom</strong> to set it to 100%. 
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig3.png" alt="Zoom">
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+#### Enable File Downloads
 
-3.&nbsp; Locate the <strong>Downloads</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Enable <strong>Ask where to save each file before downloading</strong>.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-<img src="images/edge-chromium/fig4.png" alt="Downloads"><br><br>
+3. Locate the <strong>Downloads</strong> section.
 
-<h3>Disable Pop-up Blocker</h3>
+4. Enable <strong>Ask where to save each file before downloading</strong>.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig4.png" alt="Downloads">
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+#### Disable Pop-up Blocker
 
-3.&nbsp; Locate the <strong>Site Permissions</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Open the <strong>Pop-ups and redirects</strong> section.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-5.&nbsp; Disable the <strong>Block</strong> option.<br><br>
+3. Locate the <strong>Site Permissions</strong> section.
 
-<img src="images/edge-chromium/fig6.png" alt="Pop up blocker"><br><br>
+4. Open the <strong>Pop-ups and redirects</strong> section.
 
-<h3>Allow All Sites to Run JavaScript</h3>
+5. Disable the <strong>Block</strong> option.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig6.png" alt="Pop up blocker">
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+#### Allow All Sites to Run JavaScript
 
-3.&nbsp; Locate the <strong>Site Permissions</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Open the <strong>JavaScript</strong> section.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-5.&nbsp; Enable the <strong>Allowed</strong> option.<br><br>
+3. Locate the <strong>Site Permissions</strong> section.
 
-<img src="images/edge-chromium/fig7.png" alt="Allow JavaScript"><br><br>
+4. Open the <strong>JavaScript</strong> section.
 
-<h3>Unblock Third-Party Cookies and Site Data</h3>
+5. Enable the <strong>Allowed</strong> option.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig7.png" alt="Allow JavaScript">
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+#### Unblock Third-Party Cookies and Site Data
 
-3.&nbsp; Locate the <strong>Site Permissions</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Open the <strong>Cookies and site data</strong> section.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-5.&nbsp; Enable the <strong>Allow sites to save cookies</strong> option.<br><br>
+3. Locate the <strong>Site Permissions</strong> section.
 
-6.&nbsp; Disable the <strong>Block third-party cookies</strong> option.<br><br>
+4. Open the <strong>Cookies and site data</strong> section.
 
-<img src="images/edge-chromium/fig8.png" alt="Allow Cookies"><br><br>
+5. Enable the <strong>Allow sites to save cookies</strong> option.
 
-<h3>Allow all Sites to Download Multiple Files Automatically</h3>
+6. Disable the <strong>Block third-party cookies</strong> option.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig8.png" alt="Allow Cookies">
 
-2.&nbsp; Select <strong>Settings</strong> from the drop-down menu.<br><br>
+#### Allow all Sites to Download Multiple Files Automatically
 
-3.&nbsp; Locate the <strong>Site Permissions</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Open the <strong>Automatic downloads</strong> section.<br><br>
+2. Select <strong>Settings</strong> from the drop-down menu.
 
-5.&nbsp; Enable the <strong>Ask when site tries to download multiple files</strong> option.<br><br>
+3. Locate the <strong>Site Permissions</strong> section.
 
-<img src="images/edge-chromium/fig9.png" alt="Automatic Download"><br><br>
+4. Open the <strong>Automatic downloads</strong> section.
 
-<h3>Allow Extension from Other Stores</h3>
+5. Enable the <strong>Ask when site tries to download multiple files</strong> option.
 
-1.&nbsp; Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.<br><br>
+<img src="images/edge-chromium/fig9.png" alt="Automatic Download">
 
-2.&nbsp; Select <strong>Extensions</strong> from the drop-down menu.<br><br>
+#### Allow Extension from Other Stores
 
-3.&nbsp; Locate the <strong>Site Permissions</strong> section.<br><br>
+1. Click on Edge browser *Settings* button - the three dots located in the upper right corner of the browser.
 
-4.&nbsp; Enable the <strong>Allow extensions from other stores</strong> option.<br><br>
+2. Select <strong>Extensions</strong> from the drop-down menu.
 
-<img src="images/edge-chromium/fig10.png" alt="Allow Extension from Other Stores"><br><br>
+3. Locate the <strong>Site Permissions</strong> section.
 
-<hr/>
+4. Enable the <strong>Allow extensions from other stores</strong> option.
 
-</div>
-</div>
-
-<p><hr></p>
-<p></p>
-<p></p>
+<img src="images/edge-chromium/fig10.png" alt="Allow Extension from Other Stores">
 
 ### FireFox
 
-You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).<br><br>
+You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).
 
-<p></p>
-<p></p>
-<p><hr></p>
-<p></p>
-<p></p>
-
-<p class="trigger"><a name="Manual_Configuration" style="color:black; text-decoration: none;";> Manual Configuration <span id="d" style="color:#28a1e2";> + </span></a></p>
+#### Manual Configuration 
 
-<div class="toggle_container">
-<div class="block">
+#### Enable Progress Test Studio Extension
 
-<h3>Enable Progress Test Studio Extension</h3>
+1. Click on browser settings in the right upper corner and press on <strong>Add-ons</strong>.
 
-1. Click on browser settings in the right upper corner and press on <strong>Add-ons</strong>.<br><br>
+<img src="images/firefox/fig1.png" alt="Extension">
 
-<img src="images/firefox/fig1.png" alt="Extension"><br><br>
+2. Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.
 
-2. Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.<br><br>
+<img src="images/firefox/fig2.png" alt="Extension">
 
-<img src="images/firefox/fig2.png" alt="Extension"><br><br>
+#### Zoom Level Set to 100%
 
-<h3>Zoom Level Set to 100%</h3>
+1. Click on browser settings.
 
-1. Click on browser settings.<br>
+2. Use the plus (+) and minus (-) buttons to set it to 100%.
 
-2. Use the plus (+) and minus (-) buttons to set it to 100%.<br><br>
+<img src="images/firefox/fig3.png" alt="Zoom">
 
-<img src="images/firefox/fig3.png" alt="Zoom"><br><br>
+#### Turn Off Pop-up Blocker & Enable JavaScript
 
-<h3>Turn Off Pop-up Blocker & Enable JavaScript</h3>
+1. Click on browser settings and press on <strong>Options</strong>.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br><br>
+<img src="images/firefox/fig4.png" alt="Zoom">
 
-<img src="images/firefox/fig4.png" alt="Zoom"><br><br>
+2. Click on the <strong>Privacy and Security</strong> tab (on the left side) and scroll down to <strong>Permissions</strong> section.
 
-2. Click on the <strong>Privacy and Security</strong> tab (on the left side) and scroll down to <strong>Permissions</strong> section.<br><br>
+3. Uncheck the <strong>Block pop-up windows</strong> checkbox.
 
-3. Uncheck the <strong>Block pop-up windows</strong> checkbox.<br><br>
+<img src="images/firefox/fig5.png" alt="Pop up blocker">
 
-<img src="images/firefox/fig5.png" alt="Pop up blocker"><br><br>
+#### Pop-ups Open in a New Tab
 
-<h3>Pop-ups Open in a New Tab</h3>
+1. Click on browser settings and press on <strong>Options</strong>.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br>
+2. Scroll down to <strong>Tabs</strong> section and check <strong>Open new windows in a new tab instead</strong>. 
 
-2. Scroll down to <strong>Tabs</strong> section and check <strong>Open new windows in a new tab instead</strong>. <br><br>
+<img src="images/firefox/fig6.png" alt="Pop up open in new window">
 
-<img src="images/firefox/fig6.png" alt="Pop up open in new window"><br><br>
+#### Enable File Downloads
 
-<h3>Enable File Downloads</h3>
+1. Click on browser settings and press on <strong>Options</strong>.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br>
+2. Scroll down to <strong>Downloads</strong> section and check and select <strong>Always ask you where to save files</strong>.
 
-2. Scroll down to <strong>Downloads</strong> section and check and select <strong>Always ask you where to save files</strong>.<br><br>
+<img src="images/firefox/fig7.png" alt="Downloads">
 
-<img src="images/firefox/fig7.png" alt="Downloads"><br><br>
+#### Enable Cookies
 
-<h3>Enable Cookies</h3>
+1. Click on browser settings and press on <strong>Options</strong>.
+2. Click on the <strong>Privacy and Security</strong>.
+3. Scroll down to <strong>History</strong> section to set the option to <strong>Remember history</strong>.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br>
-2. Click on the <strong>Privacy and Security</strong>.<br>
-3. Scroll down to <strong>History</strong> section to set the option to <strong>Remember history</strong>.<br><br>
+<img src="images/firefox/fig8.png" alt="Cookies">
 
-<img src="images/firefox/fig8.png" alt="Cookies"><br><br>
+#### Disable 'Remember passwords for sites'
 
-<h3>Disable 'Remember passwords for sites'</h3>
+1. Click on browser settings and press on <strong>Options</strong>.
+2. Click on the <strong>Privacy and Security</strong>.
+3. Make sure the <strong>Remember logins and passwords for websites</strong> option is disabled.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br>
-2. Click on the <strong>Privacy and Security</strong>.<br>
-3. Make sure the <strong>Remember logins and passwords for websites</strong> option is disabled.<br><br>
+<img src="images/firefox/fig9.png" alt="Passwords">
 
-<img src="images/firefox/fig9.png" alt="Passwords"><br><br>
+#### Use System Proxy Settings
 
-<h3>Use System Proxy Settings</h3>
+As of the 2012 R1 version released in April 2012, set the Connection Settings to Use system proxy settings.
 
-As of the 2012 R1 version released in April 2012, set the Connection Settings to Use system proxy settings.<br><br>
+1. Click on browser settings and press on <strong>Options</strong>.
+2. Click on the <strong>General</strong>.
+3. Scroll down to <strong>Network Proxy</strong> section and press on <strong>Settings... </strong> button.
+4. In the <strong>Connection Settings</strong> window select <strong>Use system proxy settings</strong>.
 
-1. Click on browser settings and press on <strong>Options</strong>.<br>
-2. Click on the <strong>General</strong>.<br>
-3. Scroll down to <strong>Network Proxy</strong> section and press on <strong>Settings... </strong> button.<br>
-4. In the <strong>Connection Settings</strong> window select <strong>Use system proxy settings</strong>.<br><br>
+<img src="images/firefox/fig15.png" alt="Proxy">
 
-<img src="images/firefox/fig15.png" alt="Proxy"><br><br>
-
-<h3>Setting Configuration Flags</h3>
+#### Setting Configuration Flags
 
 There are three more settings to be modified in the configuration editor -  type <strong>about:config</strong> in the url bar and press Enter to access it. Double click the following settings to set these to <strong>false</strong>:
 
-<ul>
-	<li> <strong>browser.sessionstore.resume_from_crash</strong> <br> <br> <img src="images/firefox/fig16.png" alt="browser_sessionstore_resume_from_crash"> <br> </li>
-	<li> <strong>browser.tabs.warnOnClose</strong> <br> <br><img src="images/firefox/fig17.png" alt="browser_tabs_warnOnClose"> <br></li>
-	<li> <strong>browser.tabs.warnOnCloseOtherTabs</strong> <br> <br> <img src="images/firefox/fig18.png" alt="browser_tabs_warnOnCloseOtherTabs"> <br></li>
-
-</ul>
+- <strong>browser.sessionstore.resume_from_crash</strong>   <img src="images/firefox/fig16.png" alt="browser_sessionstore_resume_from_crash">
+- <strong>browser.tabs.warnOnClose</strong>  <img src="images/firefox/fig17.png" alt="browser_tabs_warnOnClose">
+- <strong>browser.tabs.warnOnCloseOtherTabs</strong>   <img src="images/firefox/fig18.png" alt="browser_tabs_warnOnCloseOtherTabs">
 
-<br>
+#### Disable Conflicting Extensions
 
-<h3>Disable Conflicting Extensions</h3>
-
-The following Add-ons are known to conflict with the Progress Test Studio Extension: <br>
-
-<ul>
-	<li>AOL Messaging Toolbar</li>
-	<li>FoxyProxyStandard</li>
-</ul>
-
-</div>
-</div>
-<p><hr></p>
-<p></p>
-<p></p>
+The following Add-ons are known to conflict with the Progress Test Studio Extension: 
 
-<script>
-window.addEventListener('DOMContentLoaded', function () {	
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(){
-    $(this).toggleClass("active").next().slideToggle("normal");
-	$(this).find('#d').text(function (i, oldText) {
-    return $.trim(oldText) == '+' ? '-' : '+';
-	});
-		
-    });
-	});
-</script>
+- AOL Messaging Toolbar
+- FoxyProxyStandard
\ No newline at end of file
diff --git a/docs-teststudiodev/prerequisites/images/Black-10x10.png b/docs-teststudiodev/prerequisites/images/Black-10x10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/White-10x10.png b/docs-teststudiodev/prerequisites/images/White-10x10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/browser-config/accept-permissions.jpg b/docs-teststudiodev/prerequisites/images/browser-config/accept-permissions.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/browser-config/accept-popup.jpg b/docs-teststudiodev/prerequisites/images/browser-config/accept-popup.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/browser-config/disable-extension.png b/docs-teststudiodev/prerequisites/images/browser-config/disable-extension.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/browser-config/edge-notification.jpg b/docs-teststudiodev/prerequisites/images/browser-config/edge-notification.jpg
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/calibrate.png b/docs-teststudiodev/prerequisites/images/calibrate.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig1.png b/docs-teststudiodev/prerequisites/images/chrome/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig10.png b/docs-teststudiodev/prerequisites/images/chrome/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig11.png b/docs-teststudiodev/prerequisites/images/chrome/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig12.png b/docs-teststudiodev/prerequisites/images/chrome/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig13.png b/docs-teststudiodev/prerequisites/images/chrome/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig14.png b/docs-teststudiodev/prerequisites/images/chrome/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig2.png b/docs-teststudiodev/prerequisites/images/chrome/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig3.png b/docs-teststudiodev/prerequisites/images/chrome/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig4.png b/docs-teststudiodev/prerequisites/images/chrome/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig5.png b/docs-teststudiodev/prerequisites/images/chrome/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig6.png b/docs-teststudiodev/prerequisites/images/chrome/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig7.png b/docs-teststudiodev/prerequisites/images/chrome/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig8.png b/docs-teststudiodev/prerequisites/images/chrome/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/chrome/fig9.png b/docs-teststudiodev/prerequisites/images/chrome/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig10.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig2.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig3.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig4.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig6.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig7.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig8.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge-chromium/fig9.png b/docs-teststudiodev/prerequisites/images/edge-chromium/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig1.png b/docs-teststudiodev/prerequisites/images/edge/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig10.png b/docs-teststudiodev/prerequisites/images/edge/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig2.png b/docs-teststudiodev/prerequisites/images/edge/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig3.png b/docs-teststudiodev/prerequisites/images/edge/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig4.png b/docs-teststudiodev/prerequisites/images/edge/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig5.png b/docs-teststudiodev/prerequisites/images/edge/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig6.png b/docs-teststudiodev/prerequisites/images/edge/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig7.png b/docs-teststudiodev/prerequisites/images/edge/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig8.png b/docs-teststudiodev/prerequisites/images/edge/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/edge/fig9.png b/docs-teststudiodev/prerequisites/images/edge/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig1.png b/docs-teststudiodev/prerequisites/images/firefox/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig10.png b/docs-teststudiodev/prerequisites/images/firefox/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig11.png b/docs-teststudiodev/prerequisites/images/firefox/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig12.png b/docs-teststudiodev/prerequisites/images/firefox/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig13.png b/docs-teststudiodev/prerequisites/images/firefox/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig14.png b/docs-teststudiodev/prerequisites/images/firefox/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig15.png b/docs-teststudiodev/prerequisites/images/firefox/fig15.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig16.png b/docs-teststudiodev/prerequisites/images/firefox/fig16.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig17.png b/docs-teststudiodev/prerequisites/images/firefox/fig17.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig18.png b/docs-teststudiodev/prerequisites/images/firefox/fig18.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig2.png b/docs-teststudiodev/prerequisites/images/firefox/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig3.png b/docs-teststudiodev/prerequisites/images/firefox/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig4.png b/docs-teststudiodev/prerequisites/images/firefox/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig5.png b/docs-teststudiodev/prerequisites/images/firefox/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig6.png b/docs-teststudiodev/prerequisites/images/firefox/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig7.png b/docs-teststudiodev/prerequisites/images/firefox/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig8.png b/docs-teststudiodev/prerequisites/images/firefox/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/firefox/fig9.png b/docs-teststudiodev/prerequisites/images/firefox/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/activate-ts-dev.png b/docs-teststudiodev/prerequisites/images/installation/activate-ts-dev.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/activation-wizard.png b/docs-teststudiodev/prerequisites/images/installation/activation-wizard.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/browser-login.png b/docs-teststudiodev/prerequisites/images/installation/browser-login.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/choose-license.png b/docs-teststudiodev/prerequisites/images/installation/choose-license.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/devcraft.png b/docs-teststudiodev/prerequisites/images/installation/devcraft.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/fig3.png b/docs-teststudiodev/prerequisites/images/installation/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/fig4.png b/docs-teststudiodev/prerequisites/images/installation/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/fig5.png b/docs-teststudiodev/prerequisites/images/installation/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/fig6.png b/docs-teststudiodev/prerequisites/images/installation/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/fig7.png b/docs-teststudiodev/prerequisites/images/installation/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/finish.png b/docs-teststudiodev/prerequisites/images/installation/finish.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/install.png b/docs-teststudiodev/prerequisites/images/installation/install.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/licence-agreement.png b/docs-teststudiodev/prerequisites/images/installation/licence-agreement.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/manual-activation.png b/docs-teststudiodev/prerequisites/images/installation/manual-activation.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/sso-button.png b/docs-teststudiodev/prerequisites/images/installation/sso-button.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/installation/view-key.png b/docs-teststudiodev/prerequisites/images/installation/view-key.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig1.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig10.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig10.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig11.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig11.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig12.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig12.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig13.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig13.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig14.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig14.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig2.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig3.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig4.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig5.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig6.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig7.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig7.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig8.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig8.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/internet-explorer/fig9.png b/docs-teststudiodev/prerequisites/images/internet-explorer/fig9.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/open-settings-browser.png b/docs-teststudiodev/prerequisites/images/open-settings-browser.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/restore.png b/docs-teststudiodev/prerequisites/images/restore.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig1.png b/docs-teststudiodev/prerequisites/images/safari/fig1.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig2.png b/docs-teststudiodev/prerequisites/images/safari/fig2.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig3.png b/docs-teststudiodev/prerequisites/images/safari/fig3.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig4.png b/docs-teststudiodev/prerequisites/images/safari/fig4.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig5.png b/docs-teststudiodev/prerequisites/images/safari/fig5.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/safari/fig6.png b/docs-teststudiodev/prerequisites/images/safari/fig6.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/images/sys-req/vs2017installation.png b/docs-teststudiodev/prerequisites/images/sys-req/vs2017installation.png
old mode 100644
new mode 100755
diff --git a/docs-teststudiodev/prerequisites/installation.md b/docs-teststudiodev/prerequisites/installation.md
index b8e1f23a..36596992 100644
--- a/docs-teststudiodev/prerequisites/installation.md
+++ b/docs-teststudiodev/prerequisites/installation.md
@@ -13,17 +13,17 @@ position: 1
 
 - If this is your first time here and you want to try __Test Studio Dev__, download the trial installer of DevCraft Ultimate bundle  from <a href="https://www.telerik.com/teststudio-dev" target="_blank">here</a>. By default all products in the bundle are ready to be installed. If you would like to try out Test Studio Dev only you have to uncheck the rest of the products. 
 
-![DevCraft Ultimate Installation](images/installation/devcraft.png)
+<img src="images/installation/devcraft.png" alt="DevCraft Ultimate Installation" />
 
 - If you are a licensed Test Studio Dev user, log in your Telerik account and navigate to the <a href="https://www.telerik.com/account/product-download?product=TSDEVED" target="_blank">Test Studio Dev download page</a>.
 
 2.Run the installer and follow the steps. Configure the default installation folder.
 
-![Installation Wizard](images/installation/licence-agreement.png)
+<img src="images/installation/licence-agreement.png" alt="Installation Wizard" />
 
 3.When the installation is complete, the Installation Successful screen is displayed.
 
-![Successful Installation](images/installation/finish.png)
+<img src="images/installation/finish.png" alt="Successful Installation" />
 
 __See Also:__
 
diff --git a/docs-teststudiodev/prerequisites/system-requirements.md b/docs-teststudiodev/prerequisites/system-requirements.md
index e8baaa3f..d0dd7d11 100644
--- a/docs-teststudiodev/prerequisites/system-requirements.md
+++ b/docs-teststudiodev/prerequisites/system-requirements.md
@@ -13,9 +13,12 @@ __Test Studio Dev__ is an extension for Visual Studio tool and as such it inheri
 - <a href="https://docs.microsoft.com/en-us/visualstudio/releases/2022/system-requirements" target="_blank">Visual Studio 2022</a>
 - <a href="https://docs.microsoft.com/en-us/visualstudio/releases/2019/system-requirements" target="_blank">Visual Studio 2019</a>
 
+> **Important** 
+><br>
+> Test Studio Dev Edition ends support for Visual Studio 2019 at the beginning of 2026.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 
@@ -37,6 +40,10 @@ __Test Studio Dev__ is an extension for Visual Studio tool and as such it inheri
     * Visual Studio projects target a version between .NET Framework 4.7.2 to .NET Framework 4.8.
     * Visual Studio 2022 requires minimum <a href="/advanced-topics/installation/vs-2022-compatibility" target="_blank">workload components selection</a>.
 
+> **Important** 
+><br>
+> Test Studio Dev Edition ends support for Visual Studio 2019 at the beginning of 2026. 
+
 ## .NET Framework
 
 * <a href="https://www.microsoft.com/en-us/download/details.aspx?id=42642" target="_blank">.Net 4.7.2 - .Net 4.8</a> 
diff --git a/docs-teststudiodev/quickstart.md b/docs-teststudiodev/quickstart.md
index d363e44e..c6037897 100644
--- a/docs-teststudiodev/quickstart.md
+++ b/docs-teststudiodev/quickstart.md
@@ -14,7 +14,7 @@ __Test Studio Dev Edition__ is the Test Studio plugin for Visual Studio.With thi
 Follow the steps lised below to get familiar with the Test Studio Dev Edition capabilities. 
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 - [Create a project](#create-a-test-studio-dev-project)
@@ -30,8 +30,8 @@ Create a new project using the Test Studio Dev template - select _Create New Tes
 
 <table id=no-table>
 	<tr>
-		<td>![Create TS Dev project](images/quickstart/create-project.png)<br><br>**Visual Studio 2017**</td>
-		<td>![Create TS Dev project VS 2019](images/quickstart/create-project-vs-2019.png)<br><br>**Visual Studio 2019**</td>
+		<td><img src="images/quickstart/create-project.png" alt="Create TS Dev project" /><br><br>**Visual Studio 2017**</td>
+		<td><img src="images/quickstart/create-project-vs-2019.png" alt="Create TS Dev project VS 2019" /><br><br>**Visual Studio 2019**</td>
 	</tr>
 <table>
 
@@ -39,8 +39,8 @@ Next choose the type of programming language between _C# or VB.NET_ and set a me
 
 <table id=no-table>
 	<tr>
-		<td>![Choose type of TS Dev project](images/quickstart/name-of-project.png)<br><br>**Visual Studio 2017**</td>
-		<td>![Choose type of TS Dev project VS 2019](images/quickstart/name-of-project-vs-2019.png)<br><br>**Visual Studio 2019**</td>
+		<td><img src="images/quickstart/name-of-project.png" alt="Choose type of TS Dev project" /><br><br>**Visual Studio 2017**</td>
+		<td><img src="images/quickstart/name-of-project-vs-2019.png" alt="Choose type of TS Dev project VS 2019" /><br><br>**Visual Studio 2019**</td>
 	</tr>
 <table>
 
diff --git a/docs-teststudiodev/redirect-tests-teststudio-dev.csv b/docs-teststudiodev/redirect-tests-teststudio-dev.csv
new file mode 100644
index 00000000..b2cd89a7
--- /dev/null
+++ b/docs-teststudiodev/redirect-tests-teststudio-dev.csv
@@ -0,0 +1,10 @@
+, /introduction
+/INTRODUCTION, /introduction
+/getting-started, /quickstart
+/getting-started.html, /quickstart
+/basic-usage/rapid-testing-with-justcode, /introduction
+/basic-usage/rapid-testing-with-justcode.html, /introduction
+/advanced-usage/openaccess-mocking, /introduction
+/advanced-usage/openaccess-mocking.html, /introduction
+/scenarios, /introduction
+/scenarios.html, /introduction
\ No newline at end of file
diff --git a/docs-teststudiodev/redirects.conf b/docs-teststudiodev/redirects.conf
old mode 100644
new mode 100755
diff --git a/docs/_config.yml b/docs/_config.yml
index dd4aaf90..e8e102c9 100644
--- a/docs/_config.yml
+++ b/docs/_config.yml
@@ -9,7 +9,7 @@ productName: "Test Studio Documentation"
 
 # Exclude files which should not be in the output
 exclude: [README.md,Gemfile,Gemfile.lock,build.cmd,run.cmd,deploy.cmd,apireference/*, docs-watcher/*]
-exclude_navigation: ["archived-docs/*", "license-server/*", "test-studio-mobile/*", "copyright.html"]
+exclude_navigation: ["archived-docs/*", "license-server/*", "copyright.html"]
 
 
 
@@ -52,9 +52,6 @@ navigation:
     "security":
         title: "Security"
         position: 11
-    "test-studio-mobile":
-        title: "Test Studio Mobile"
-        position: 12
     "license-server":
         title: "License Server"
         position: 13
@@ -249,6 +246,7 @@ navigation:
     features/integration:
         title: "Integration"
         position: 12
+
 # ....Integration section
     features/integration/bug-tracking:
         title: "Bug Tracking"
@@ -257,6 +255,7 @@ navigation:
         title: "Quality Center"
         position: 2
  # ....End Integration section    
+
     features/test-runners:
         title: "Test Runners"
         position: 13
@@ -304,9 +303,7 @@ navigation:
     "*manual-testing":
         title: "Manual Testing"
         position: 1
-    "*exploratory-testing":
-        title: "Exploratory Testing"
-        position: 2
+
 
 # === Step Builder ===
     features/custom-steps/all-tests-common:
@@ -331,26 +328,28 @@ navigation:
         position: 11
         
 # === Advanced Topics ===
-    "*coded-steps":
-        title: "Coded Steps"
+#......Build server.......
+    "*build-server":
+        title: "Continuous Integration"
+        position: 0
+#......Azure DevOps.......
+    "*azdo":
+        title: "Azure DevOps Pipelines"
+        position: 2
+
+#.....Coded Samples......
     "*coded-samples":
         title: "Coded Samples"
-#.....Coded Samples
+        position: 1
+#.....Coded Samples-subsections......
     "*general":
         title: "General"
     "*html":
         title: "HTML"
-    "*silverlight":
-        title: "Silverlight"
-    "*combobox-automation":
-        title: "ComboBox Automation"
-    "*radgridview-automation":
-        title: "RadGridView Automation"
     "*wpf":
         title: "WPF"
-#........................
-    "*build-server":
-        title: "Build Server"
+
+
 # === Knowledge Base ===
     "*activation-kb":
         title: "Activation"
@@ -368,8 +367,6 @@ navigation:
         title: "Project Configuration"
     "*scheduling-kb":
         title: "Scheduling"
-    "*silverlight-kb":
-        title: "Silverlight"
     "*source-control-kb":
         title: "Source Control"
     "*test-automation-kb":
@@ -386,6 +383,7 @@ navigation:
         title: "Browsers"
     "*product-notices-kb":
         title: "Product Notices"
+        position: 50
 # === Troubleshooting Guide ===
     "*browser-inconsistencies-tg":
         title: "Browser Inconsistencies"
@@ -395,6 +393,8 @@ navigation:
         title: "Installation Problems"
     "*load-testing-problems-tg":
         title: "Load Testing Problems"
+    "*network-related-problems-tg":
+        title: "Network Related Problems"
     "*recording-problems-tg":
         title: "Recording Problems"
     "*scheduling-issues-tg":
@@ -403,24 +403,9 @@ navigation:
         title: "Source Control Problems"
     "*test-execution-problems-tg":
         title: "Test Execution Problems"
-    "*chrome-tg":
-        title: "Chrome"
-    "*firefox-tg":
-        title: "Firefox"
-    "*safari-tg":
-        title: "Safari"
-    "*silverlight-wpf-tg":
-        title: "Silverlight WPF"
-    "*test-maintenance-problems-tg":
-        title: "Test Maintenance Problems"
-    "*troubleshooting-tools-tg":
-        title: "Troubleshooting Tools"
-    "*verification-problems-tg":
-        title: "Verification Problems"
     "*visual-studio-tg":
         title: "Visual Studio"
-    "*network-related-problems-tg":
-        title: "Network Related Problems"
+    
 # === Testing Framework ===
     "*write-tests-in-code":
         title: "Write Tests in Code"
@@ -442,59 +427,11 @@ navigation:
         title: "Javascript"
     "*test-regions-wtc":
         title: "Test Regions"
-    "*silverlight-wpf-automation-wtc":
-        title: "Silverlight/WPF Automation"
+    "*wpf-automation-wtc":
+        title: "WPF Automation"
     testing-framework/api-reference:
         title: "Api Reference"
-# === Mobile Testing ===
-    test-studio-mobile/getting-started:
-       title: "Getting Started"
-       position: 3
-    test-studio-mobile/native-applications:
-       title: "Native Applications"
-       position: 4
-    test-studio-mobile/native-applications/installation:
-       title: "Installation"
-       position: 1
-    test-studio-mobile/native-applications/configure-your-app:
-       title: "Configure Your App"
-       position: 2
-    test-studio-mobile/native-applications/connect-agent-app:
-       title: "Connect Agent App"
-       position: 3
-    test-studio-mobile/web-applications:
-       title: "Web Applications"
-       position: 5
-    test-studio-mobile/web-applications/configuration:
-       title: "Configuration"
-       position: 1
-    test-studio-mobile/test-recording:
-       title: "Test Recording"
-       position: 6
-    test-studio-mobile/test-recording/record-a-test:
-       title: "Record a Test"
-       position: 1
-    test-studio-mobile/test-execution:
-       title: "Test Execution"
-       position: 7
-    test-studio-mobile/features:
-       title: "Features"
-       position: 8
-    test-studio-mobile/features/code-features:
-       title: "Code Features"
-       position: 1
-    test-studio-mobile/knowledge-base:
-       title: "Knowledge Base"
-       position: 9
-    test-studio-mobile/knowledge-base/continuous-integration:
-       title: "Continuous Integration"
-       position: 1
-    test-studio-mobile/troubleshooting:
-       title: "Troubleshooting Guide"
-       position: 10
-    test-studio-mobile/api-reference:
-        title: "API Reference"
-        position: 11
+
 
 # === Archived Documentation ===
     archived-docs/recorder:
diff --git a/docs/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests.md b/docs/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests.md
new file mode 100644
index 00000000..da5e21d9
--- /dev/null
+++ b/docs/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests.md
@@ -0,0 +1,167 @@
+---
+title: Azure DevOps Pipelines and Test Studio Tests
+page_title: Test Studio Tests in Azure DevOps Build Pipelines
+description: "Learn how to integrate and execute Test Studio automated tests in Azure DevOps pipelines using self-hosted or Microsoft-hosted agents. This guide covers prerequisites, agent setup, artifact management, and limitations for web and desktop test execution."
+position: 0
+---
+# Test Studio Tests and Azure DevOps Build Pipeline
+
+You can integrate <a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests for automated execution within Azure DevOps pipelines. This article outlines the key prerequisites and configuration steps you should consider before setting up your pipeline.
+
+## Environmental Prerequisites
+
+The build machine may be either a physical or virtual system that hosts both the Azure DevOps agent and the Test Studio Runner. For minimum hardware and software requirements, see the <a href="/system-requirements" target="_blank">Test Studio system requirements documentation</a>.
+
+Additional prerequisites: 
+
+* __Azure DevOps account__ enabled to configure Agent pools, Microsoft-hosted agent VMs and pipelines: __mandatory__
+* __Azure DevOps Agent__ : __mandatory__
+* __Test Studio Run-time Edition__ (ArtOfTest.Runner.exe must be available - preferably latest version): __mandatory__
+* __Internet Browser__ (Chrome, Edge, Firefox - preferably latest versions) or WPF/desktop application: __mandatory__
+
+## Upload the Testing Project into a Source Control Repository
+
+Executing the Test Studio automated tests as part of any CI pipeline requires the project to be deployed on the execution machine. The most convenient approach is to manage the project into a source control repository and use it to checkout the current latest version at the time of execution. The type of source control repository to use depends on your company policies and specifics. 
+
+## Choose the Configuration to Setup
+
+Azure DevOps provides two options to run pipelines - on a on-premise local machine (physical or virtual) and on a container hosted by Microsoft. Depending on the configuration you choose there are different initial adjustments of the setup. 
+
+Running __pipeline with Test Studio automated tests on a local machine__ requires you to: 
+
+* [create a new self-hosted agent in the AzDO project](#create-a-self-hosted-agent)
+* [configure the self-hosted agent to always run n interactive mode](#configure-the-self-hosted-agent)
+
+Running __pipeline with Test Studio automated tests on a Microsoft hosted machine__ requires you to:
+
+* [upload Test Studio installer as artifact](#add-test-studio-run-time-installer-as-artifact-in-azdo-project)
+* [check known limitations for using the MS-hosted agent machines](#limitations-in-using-ms-hosted-agent-with-test-studio-tests)
+
+    > __Important!__
+    > <br>
+    > <br>
+    > Microsoft-hosted agent VMs use no GUI session or UI, thus it can be __used only for executing web tests__!
+
+## Create a Self-Hosted Agent 
+
+Test Studio application is a Windows OS based and as such you can execute the automated tests only on a Windows machine. Thus, you need to use the <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops" target="_blank">AzDO self-hosted Windows agent</a> to execute tests as part of a pipeline.
+
+To create such agent, follow the steps listed below: 
+
+1. Open the **Project settings** of the current AzDO project.
+
+    ![Open the current AzDO project settings][2]
+
+2. Click on **Pipelines -> Agent Pools**.
+
+    ![Agent Pools][3]
+
+3. Add a new pool or open the default one.
+
+    ![New Agent Pools][4]
+
+4. Click **New Agent**,
+
+    ![New Agent][5]
+
+5. Download the Agent to the corresponding physical or virtual machine as per the installation requirements above.
+
+6. Extract the Agent and run as Administrator.
+
+    ![Start Agent][6]
+
+> **Note** 
+> <br>
+> To avoid any permissions issues make sure that the user configuring the Agent is part of the following Permission Groups in AzDO project: Build Administrators, Release Administrators, Project Administrators, ProjectName Team.
+
+<br>
+<div><a style="float:right" href="#choose-the-configuration-to-setup">Back to top of section</a></div>
+<br>
+
+## Configure the Self-Hosted Agent
+
+1. Enter server URL: i.e. https://dev.azure.com/OrganizationName.
+
+2. <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops#permissions" target="_blank">Create Personal Access Token (PAT)</a> and save it.
+
+3. Choose PAT for authentication type and paste yours.
+
+4. Choose the Agent pool you created earlier.
+
+5. Choose Agent name, the default name is the machine name on which it is hosted.
+
+6. Choose a work folder or press enter for the default `_work` sub-folder.
+
+7. Choose to run the Agent in Interactive mode - select `N` when asked to run agent as a service.
+
+8. Choose whether to configure autologon and run agent on startup - from Test Studio perspective this is optional and depends on the project demands.
+
+    ![Configure Agent][7]
+
+9. Upon successful configuration the config console gets closed. Run the `run.cmd` file in console to trigger the Agent.
+
+    ![Trigger Agent][8]
+
+
+<br>
+<div><a style="float:right" href="#choose-the-configuration-to-setup">Back to top of section</a></div>
+<br>
+
+
+
+
+
+
+
+## Add Test Studio Run-time Installer as Artifact in AzDO Project
+
+Follow the below steps to upload the Test Studio Run-time installer as artifact in the AzDO project:
+
+
+1. Open the __Artifacts__ view in the Azure platform and choose the feed in which you want to add the Test Studio Run-time installer. 
+
+    > __Tip!__
+    ><br>
+    > You can __download the Test Studio Run-time Edition *.msi installer file__ from your <a href="https://www.telerik.com/account/product-download?product=TESTSTUDIORUNTIME" target="_blank">Telerik account here</a>. 
+   
+2. Then select the __Connect to feed__ option to add an artifact in the feed. If you need further information about _Feeds in Azure DevOps_, you can visit the <a href="https://docs.microsoft.com/en-us/azure/devops/artifacts/concepts/feeds?view=azure-devops" target="_blank">Microsoft docs page on the topic</a>.
+
+    ![Artifacts and Feed in Azure](/img/advanced-topics/build-server/mha-testing/fig1.png)
+
+3. Choose the __Universal Packages__ option from the list of artifacts. The instructions how to publish a package are listed on the right side of the list. It is necessary to use the Azure CLI to login and publish the installer file - you can find example commands, which need to be adjusted for your project specifics. If you need further information about __Publishing Universal Packages__, you can refer to the <a href="https://docs.microsoft.com/en-us/azure/devops/artifacts/quickstarts/universal-packages?view=azure-devops" target="_blank">Microsoft docs page on the topic</a>.
+
+    ![Publish Universal package in Azure feed](/img/advanced-topics/build-server/mha-testing/fig2.png)
+
+4. After the package is successfully uploaded, it is __listed as an artifact__ and can be used in the Azure pipelines for that project.
+
+    ![Artifacts in Azure feed](/img/advanced-topics/build-server/mha-testing/fig3.png)
+
+<br>
+<div><a style="float:right" href="#choose-the-configuration-to-setup">Back to top of section</a></div>
+<br>
+
+## Limitations in Using MS-Hosted Agent with Test Studio Tests
+
+* __Only web tests using Edge and Chrome browsers__ can be executed in a Microsoft-hosted agent.
+* __The <a href="/automated-tests/test-results/step-failure-details#images-tab" target="_blank">images on failure</a>__ are not available in the results generated from the test runs in Microsoft-hosted agent.
+
+<br>
+<div><a style="float:right" href="#choose-the-configuration-to-setup">Back to top of section</a></div>
+<br>
+
+## Continue to Setting Up a Pipeline
+
+You can integrate the Test Studio automated tests execution in both classic and YAML type of pipelines in AzDO. Find reference for the different options and choose the one which suits your project needs: 
+
+- <a href="/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline" target="_blank">Configure classic pipeline to execute tests on self hosted machine</a>
+- <a href="/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline" target="_blank">Configure classic pipeline to execute tests on Microsoft hosted machine</a>
+- <a href="/advanced-topics/build-server/azdo/self-hosted-agent-yml-pipeline" target="_blank">Configure YAML pipeline to execute tests on self hosted machine</a>
+- <a href="/advanced-topics/build-server/azdo/ms-hosted-agent-yml-pipeline" target="_blank">Configure YAML pipeline to execute tests on Microsoft hosted machine</a>
+
+[2]: /img/advanced-topics/build-server/azure-devops/fig2.png
+[3]: /img/advanced-topics/build-server/azure-devops/fig3.png
+[4]: /img/advanced-topics/build-server/azure-devops/fig4.png
+[5]: /img/advanced-topics/build-server/azure-devops/fig5.png
+[6]: /img/advanced-topics/build-server/azure-devops/fig6.png
+[7]: /img/advanced-topics/build-server/azure-devops/fig7.png
+[8]: /img/advanced-topics/build-server/azure-devops/fig8.png
\ No newline at end of file
diff --git a/docs/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline.md b/docs/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline.md
new file mode 100644
index 00000000..2dc4d1d1
--- /dev/null
+++ b/docs/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline.md
@@ -0,0 +1,173 @@
+---
+title: AzDO Classic Pipeline Using Microsoft-Hosted Agent
+page_title: Test Studio Tests in Azure DevOps Classic Pipeline Using Microsoft-Hosted Agent
+description: "Integrate Test Studio tests in Azure DevOps continuous integration. Execute Test Studio tests with Azure DevOps Classic Pipeline configured with Microsoft-hosted agent."
+position: 2
+---
+
+# Test Studio Tests in Azure DevOps Classic Piepline Using Microsoft-Hosted Agent
+
+<a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests can be successfully integrated for execution with the Azure DevOps pipelines. This article guides you through an example setup of classic pipeline using Microsoft-hosted agent.
+
+> __Tip!__
+><br>
+> Double check if you have covered all <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests#choose-the-configuration-to-setup" target="_blank">prerequisites for this setup</a>.
+
+## Create a Free Form Pipeline
+
+1. In the Azure DevOps project go to **Pipelines >> New Pipeline**.
+
+    ![Create new Pipeline][9]
+
+2. For this setup choose the option to **Use the classic editor**.
+
+    ![Choose classic editor][10]
+
+3. Choose the repository type where the project is and fill in the necessary details to connect to the repo. Click **Continue**.
+
+    ![Choose repo type][11]
+
+4. Choose **Empty job** as a template for the build
+
+    ![Choose empty job][12]
+
+5. Click the __Pipeline__ tile and set a meaningful name for the pipeline. Then select the __Agent pool__ for Microsoft-hosted agents and choose a default image to be installed on the VM when running the pipeline - you can use _windows-latest_.
+
+    ![Set name and select agent pool for the pipeline, choose agent image](/img/advanced-topics/build-server/mha-testing/fig7.png)
+
+6. Continue with adding the Agent tasks as described below. 
+
+    > __Tip__
+    ><br>
+    > Set __all tasks__ to **Continue on error** in the task **Control Options** section. This ensures that result upload tasks run even if a previous task fails. 
+    ><br>
+    ><br>
+    > All tasks except the first Command Line task (which executes the test run command) are optional. 
+
+## Add Universal Download Package Task to Deploy Test Studio Installer on Agent Machine
+
+1. Click the __Agent__ tile and create a new __Packages >> Universal Packages__ task.
+
+    ![Universal Package task](/img/advanced-topics/build-server/mha-testing/fig8.png)
+
+2. Set a meaningful name for the __Universal Packages__ task. Then set the task command to download action and specify the destination folder. 
+
+    ![Download Universal Package task](/img/advanced-topics/build-server/mha-testing/fig9a.png)
+
+3. Verify the __Feed & packages details__ section in the __Universal Packages__ task and ensure the feed, name and version details of the artifact correspond to details specified when <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests#add-test-studio-run-time-installer-as-artifact-in-azdo-project" target="_blank">publishing the installer as an artifact</a>.
+
+    ![Feed & Packages details section](/img/advanced-topics/build-server/mha-testing/fig9.png)
+
+## Add Command Line Agent Task to Install Test Studio Runtime
+
+1. Click the __Agent__ tile and create a new __Utility >> Command line__ task.
+
+    ![Command line new task][14]
+
+2. Set a meaningful name for the __Command Line__ task. Then place a command which calls the <a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/msiexec" target="_blank">Windows msiexec command</a> in passive mode. The passive mode is required due to the lack of UI session. Below is an example command to use as baseline in the task.
+
+    ```
+    msiexec.exe /i c:\TestStudio_Runtime_2021_3_1103_1.msi /passive /le c:\errorlog.txt
+    ```
+
+    ![Install Runtime task](/img/advanced-topics/build-server/mha-testing/fig10.png)
+
+## Add Command Line Agent Task to Execute Test or Test List
+
+1. Click the __Agent__ tile and create a new __Utility >> Command line__ task.
+
+    ![Command line new task][14]
+
+2. Set a meaningful name for the __Command Line__ task. Then place a command which calls the <a href="/features/test-runners/artoftest-runner" target="_blank">Test Studio CLI Runner</a> to trigger the test execution. 
+
+    > __Tip__
+    > <br>
+    > Test Studio CLI runner is called __ArtOfTest.Runner.exe__ and provides various execution options. If you are not yet familiar with these check the <a href="/features/test-runners/artoftest-runner#options-to-specify-which-file-to-execute" target="_blank">CLI runner syntax options here</a> to build your command. 
+   
+3. The sample image executes a test list, sets specific name for the output Test Studio result file and also generates a _junit_ type of result. 
+
+    ![Execute test list task][15]
+
+## Add Publish Test Results Task to Upload JUnit Results
+
+1. Click the __Agent__ tile and create a new __Tests >> Publish Test Results__ task.
+
+    ![Add Publish Test results task][17]
+
+2. Test Studio CLI runner lets you output the execution result in _junit_ format and this is the type of result which can be used in this pipeline task. 
+   
+3. Set a meaningful name for the **Publish Test Results**. Then set the folder where the test results are deployed and choose to upload all .xml files. 
+
+    ![Configure Publish Test results][18]
+
+4. Once the pipeline run is complete the details from _junit_ result are visible in the **Test** tab.
+
+    ![See test results][19]
+
+## Add Publish Pipeline Artifacts Task to Upload the Test Studio Result File 
+
+Test Studio test run produces its proprietary test result file which contains additional useful information for the test run. That result file can be very helpful in the case when a test run fails. The __result file always ends with file extension *.aiiresult__ and we recommend to <a href="/features/test-runners/artoftest-runner#result-option" target="_blank">specify its name as part of the command which triggers the CLI runner</a>. That way you can control the upload of the file to the pipeline artifacts. 
+
+1. Click the __Agent__ tile and create a new __All >> Publish Pipeline Artifacts__ task.
+
+    ![Add Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig20.png)
+
+2. Set a meaningful name for the **Publish Pipeline Artifacts** task. Then specify the file to upload using the predefined name set in the execution command and define a meaningful name for the artifact.
+
+    ![Configure Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig21.png)
+
+3. Once the pipeline run is complete the artifacts are accessible under the __Summary__ tab in the __Related__ listings. 
+
+    ![See published Artifacts](/img/advanced-topics/build-server/azure-devops/fig22.png)
+
+## Add Publish Pipeline Artifacts Task to Upload the Test Studio Failure Details When Available 
+
+Test Studio test run produces its proprietary <a href="/automated-tests/test-results/step-failure-details" target="_blank">failure details</a> in case a test run fails. These provide additional context for the specific failure and are very useful for debugging a failing test. The failure details are output in a folder which has the name of the test result and ends with __*\_files__. Since __these are available only if a test fails__ you need to setup a task to check if such folder exists and upload the artifacts only if it does. 
+
+1. Click the __Agent__ tile and create a new __Utility >> Command line__ task.
+
+    ![Command line new task][14]
+
+2. Set a meaningful name for the __Command Line__ task. Then place a command which checks for the folder using the predefined name of the result file set in the execution command and returns true or false depending on the outcome. 
+
+    ![Script to check if a folder exists and set](/img/advanced-topics/build-server/azure-devops/fig23.png)
+
+3. Click the __Agent__ tile and create a new __All >> Publish Pipeline Artifacts__ task.
+
+    ![Add Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig20.png)
+
+4. Set a meaningful name for the **Publish Pipeline Artifacts** task. Then specify the folder to upload using the predefined name set in the execution command adding the ending __*\_files__ and define a meaningful name for the artifact.
+
+    ![Configure Publish Pipeline Artifacts task for the failure details](/img/advanced-topics/build-server/azure-devops/fig24.png)
+
+5. This task is supposed to be executed only if the failure folder exists. Therefore you need to __specify a custom condition for executing the task__. Expand the __Control Options__ section of the task and set the __Custom Condiition__ to check the result of the previous __Command Line__ task. 
+
+    ![Configure control options for Publish Pipeline Artifacts task for the failure details](/img/advanced-topics/build-server/azure-devops/fig25.png)
+
+6. Once the pipeline run is complete the artifacts are accessible under the __Summary__ tab in the __Related__ listings. 
+
+    ![See published Artifacts](/img/advanced-topics/build-server/azure-devops/fig22.png)
+
+
+## See Also
+
+* <a href="https://www.telerik.com/blogs/using-microsoft-hosted-agents-azure-pipelines-automated-test-execution" target="_blank">Using Microsoft Hosted Agents in Azure Pipelines for Automated Test Execution</a>.
+
+
+[9]: /img/advanced-topics/build-server/azure-devops/fig9.png
+[10]: /img/advanced-topics/build-server/azure-devops/fig10.png
+[11]: /img/advanced-topics/build-server/azure-devops/fig11.png
+[12]: /img/advanced-topics/build-server/azure-devops/fig12.png
+[14]: /img/advanced-topics/build-server/azure-devops/fig14.png
+[15]: /img/advanced-topics/build-server/azure-devops/fig15.png
+[16]: /img/advanced-topics/build-server/azure-devops/fig16.png
+[17]: /img/advanced-topics/build-server/azure-devops/fig17.png
+[18]: /img/advanced-topics/build-server/azure-devops/fig18.png
+[19]: /img/advanced-topics/build-server/azure-devops/fig19.png
+
+
+> __Tip__
+> <br>
+> <br>
+> Check out our blog post about <a href="https://www.telerik.com/blogs/using-microsoft-hosted-agents-azure-pipelines-automated-test-execution" target="_blank">Tesitng in Microsoft-hosted agents</a>.
+
diff --git a/docs/advanced-topics/build-server/azdo/ms-hosted-agent-yml-pipeline.md b/docs/advanced-topics/build-server/azdo/ms-hosted-agent-yml-pipeline.md
new file mode 100644
index 00000000..0f8af24c
--- /dev/null
+++ b/docs/advanced-topics/build-server/azdo/ms-hosted-agent-yml-pipeline.md
@@ -0,0 +1,100 @@
+---
+title: AzDO YAML Pipeline Using MS-Hosted Agent 
+page_title: Test Studio Tests in Azure DevOps YAML Pipeline Using Microsoft-Hosted Agent
+description: "Integrate Test Studio tests in Azure DevOps continuous integration. Execute Test Studio tests with Azure DevOps YAML Pipeline configured with MS-Hosted agent."
+position: 4
+---
+# Test Studio Tests in Azure DevOps YAML Pipeline Using Microsoft-Hosted Agent
+
+<a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests can be successfully integrated for execution with the Azure DevOps pipelines. 
+
+Below is a sample YAML pipeline using Microsoft-hosted agent machine which follows the instructions for <a href="/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline#add-universal-download-package-task-to-deploy-test-studio-installer-on-agent-machine" target="_blank">building the classic pipeline using MS-hosted agent</a>. 
+
+> __Tip!__
+><br>
+> Double check if you have covered all <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests#choose-the-configuration-to-setup" target="_blank">prerequisites for this setup</a>.
+
+```YAML
+trigger:
+- none
+
+pool:
+  vmImage: 'windows-latest'
+
+steps:
+
+# Download latest runtime from feed
+- task: DownloadPackage@1
+  inputs:
+    packageType: 'upack'
+    feed: '/b1db09af-8756-4092-9ea2-df51da8b1e16'
+    view: 'eaa25bb8-bcde-44dd-8bd5-0fbedb0a137e'
+    definition: '791755a9-0985-4fe9-8905-eea8f0a03569'
+    version: '0.0.3'
+    downloadPath: '$(Pipeline.Workspace)\downloads'
+
+# Install latest runtime
+- task: PowerShell@2
+  displayName: Install runtime
+  inputs:
+      targetType: 'inline'
+      script: |
+        $temp_dir = "$(Pipeline.Workspace)\downloads"
+        # Select the installer from the temp folder.
+        $installer = (Get-ChildItem $temp_dir -recurse -include TestStudio_Runtime_*.msi | Sort-Object LastWriteTime | Select-Object -last 1)
+        
+        # Output the installer file name that is installed
+        Write-Output("Msi to install: " + $installer.name)
+        
+        # Install Test Studio silently in temp folder.
+        $arg = @()
+        $arg += "/i"
+        $arg += ("$(Pipeline.Workspace)\downloads\" + $installer.name)
+        $arg += "/passive"
+        Write-Host "Calling msiexec.exe" $arg
+        Start-Process "msiexec.exe" -ArgumentList $arg -Wait
+        Write-Output("Install completed!")
+
+# Specify test list to execute
+- script: | 
+    "C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" ^
+      list="$(System.DefaultWorkingDirectory)\navToTSPage\TestLists\openTSPage.aiilist" ^
+      result="openTSPage" ^
+      settings="$(System.DefaultWorkingDirectory)\navToTSPage\mshosted-run-settings-using-edge-headless.json" ^
+      junit
+  displayName: 'CMD Execute Test List'
+  continueOnError: true
+
+# Publish JUnit result
+- task: PublishTestResults@2 
+  displayName: 'Publish Test Results **.xml' 
+  inputs: 
+    testResultsFiles: '**.xml' 
+    searchFolder: '$(System.DefaultWorkingDirectory)\navToTSPage\Results' 
+    failTaskOnFailedTests: true
+    testRunTitle: 'Test Run - openTSPage'
+
+# Publish aiiresult file
+- task: PublishPipelineArtifact@1
+  displayName: 'Publish aiiresult file'
+  inputs:
+    targetPath: '$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage.aiiresult'
+    artifact: 'aiiresult file - openTSPage'
+
+# Check if failure details exists 
+- script: |
+    if exist "$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage_files" (
+      echo "##vso[task.setvariable variable=folderExists]true"
+    ) else (
+      echo "##vso[task.setvariable variable=folderExists]false"
+    )
+  displayName: 'Check if failure details folder exists'
+
+# Publish failure details if applicable
+- task: PublishPipelineArtifact@1
+  displayName: 'Publish failure details if applicable'
+  condition: and(succeededOrFailed(), eq(variables['folderExists'], 'true'))
+  inputs:
+    targetPath: '$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage_files'
+    artifact: 'failure-details - openTSPage'
+```
\ No newline at end of file
diff --git a/docs/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline.md b/docs/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline.md
new file mode 100644
index 00000000..4e7ab28f
--- /dev/null
+++ b/docs/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline.md
@@ -0,0 +1,139 @@
+---
+title: AzDO Classic Pipeline Using Self-Hosted Agent
+page_title: Test Studio Tests in Azure DevOps Classic Pipeline Using Self-Hosted Agent
+description: "Integrate Test Studio tests in Azure DevOps continuous integration. Execute Test Studio tests with Azure DevOps Classic Pipeline configured with self-hosted agent."
+position: 1
+---
+
+# Test Studio Tests in Azure DevOps Classic Pipeline Using Self-Hosted Agent
+
+<a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests can be successfully integrated for execution with the Azure DevOps pipelines. This article guides you through an example setup of classic pipeline using self-hosted agent machine. 
+
+> __Tip!__
+><br>
+> Double check if you have covered all <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests#choose-the-configuration-to-setup" target="_blank">prerequisites for this setup</a>. 
+
+## Create Classic Pipeline
+
+1. In the Azure DevOps project go to **Pipelines >> New Pipeline**.
+
+    ![Create new Pipeline][9]
+
+2. For this setup choose the option to **Use the classic editor**.
+
+    ![Choose classic editor][10]
+
+3. Choose the repository type where the project is and fill in the necessary details to connect to the repo. Click **Continue**.
+
+    ![Choose repo type][11]
+
+4. Choose **Empty job** as a template for the build
+
+    ![Choose empty job][12]
+
+5. Click the __Pipeline__ tile and set a meaningful name for the pipeline. Then select the __Agent pool__ for self-hosted agents configured earlier.
+
+    ![Set name and select agent pool for the pipeline][13]
+
+6. Continue with adding the Agent tasks as described below. 
+
+    > __Tip__
+    ><br>
+    > Set __all tasks__ to **Continue on error** in the task **Control Options** section. This ensures that result upload tasks run even if a previous task fails. 
+    ><br>
+    ><br>
+    > All tasks except the first Command Line task (which executes the test run command) are optional. 
+
+## Add Command Line Agent Task to Execute Test or Test List
+
+1. Click the __Agent__ tile and create a new __Utility >> Command line__ task.
+
+    ![Command line new task][14]
+
+2. Set a meaningful name for the __Command Line__ task. Then place a command which calls the <a href="/features/test-runners/artoftest-runner" target="_blank">Test Studio CLI Runner</a> to trigger the test execution. 
+
+    > __Tip__
+    > <br>
+    > Test Studio CLI runner is called __ArtOfTest.Runner.exe__ and provides various execution options. If you are not yet familiar with these check the <a href="/features/test-runners/artoftest-runner#options-to-specify-which-file-to-execute" target="_blank">CLI runner syntax options here</a> to build your command. 
+   
+3. The sample image executes a test list, sets specific name for the output Test Studio result file and also generates a _junit_ type of result. 
+
+    ![Execute test list task][15]
+
+## Add Publish Test Results Task to Upload JUnit Results
+
+1. Click the __Agent__ tile and create a new __Tests >> Publish Test Results__ task.
+
+    ![Add Publish Test results task][17]
+
+2. Test Studio CLI runner lets you output the execution result in _junit_ format and this is the type of result which can be used in this pipeline task. 
+   
+3. Set a meaningful name for the **Publish Test Results**. Then set the folder where the test results are deployed and choose to upload all .xml files. 
+
+    ![Configure Publish Test results][18]
+
+4. Once the pipeline run is complete the details from _junit_ result are visible in the **Test** tab.
+
+    ![See test results][19]
+
+## Add Publish Pipeline Artifacts Task to Upload the Test Studio Result File 
+
+Test Studio test run produces its proprietary test result file which contains additional useful information for the test run. That result file can be very helpful in the case when a test run fails. The __result file always ends with file extension *.aiiresult__ and we recommend to <a href="/features/test-runners/artoftest-runner#result-option" target="_blank">specify its name as part of the command which triggers the CLI runner</a>. That way you can control the upload of the file to the pipeline artifacts. 
+
+1. Click the __Agent__ tile and create a new __All >> Publish Pipeline Artifacts__ task.
+
+    ![Add Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig20.png)
+
+2. Set a meaningful name for the **Publish Pipeline Artifacts** task. Then specify the file to upload using the predefined name set in the execution command and define a meaningful name for the artifact.
+
+    ![Configure Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig21.png)
+
+3. Once the pipeline run is complete the artifacts are accessible under the __Summary__ tab in the __Related__ listings. 
+
+    ![See published Artifacts](/img/advanced-topics/build-server/azure-devops/fig22.png)
+
+## Add Publish Pipeline Artifacts Task to Upload the Test Studio Failure Details When Available 
+
+Test Studio test run produces its proprietary <a href="/automated-tests/test-results/step-failure-details" target="_blank">failure details</a> in case a test run fails. These provide additional context for the specific failure and are very useful for debugging a failing test. The failure details are output in a folder which has the name of the test result and ends with __*\_files__. Since __these are available only if a test fails__ you need to setup a task to check if such folder exists and upload the artifacts only if it does. 
+
+1. Click the __Agent__ tile and create a new __Utility >> Command line__ task.
+
+    ![Command line new task][14]
+
+2. Set a meaningful name for the __Command Line__ task. Then place a command which checks for the folder using the predefined name of the result file set in the execution command and returns true or false depending on the outcome. 
+
+    ![Script to check if a folder exists and set](/img/advanced-topics/build-server/azure-devops/fig23.png)
+
+3. Click the __Agent__ tile and create a new __All >> Publish Pipeline Artifacts__ task.
+
+    ![Add Publish Pipeline Artifacts task](/img/advanced-topics/build-server/azure-devops/fig20.png)
+
+4. Set a meaningful name for the **Publish Pipeline Artifacts** task. Then specify the folder to upload using the predefined name set in the execution command adding the ending __*\_files__ and define a meaningful name for the artifact.
+
+    ![Configure Publish Pipeline Artifacts task for the failure details](/img/advanced-topics/build-server/azure-devops/fig24.png)
+
+5. This task is supposed to be executed only if the failure folder exists. Therefore you need to __specify a custom condition for executing the task__. Expand the __Control Options__ section of the task and set the __Custom Condiition__ to check the result of the previous __Command Line__ task. 
+
+    ![Configure control options for Publish Pipeline Artifacts task for the failure details](/img/advanced-topics/build-server/azure-devops/fig25.png)
+
+6. Once the pipeline run is complete the artifacts are accessible under the __Summary__ tab in the __Related__ listings. 
+
+    ![See published Artifacts](/img/advanced-topics/build-server/azure-devops/fig22.png)
+
+
+[9]: /img/advanced-topics/build-server/azure-devops/fig9.png
+[10]: /img/advanced-topics/build-server/azure-devops/fig10.png
+[11]: /img/advanced-topics/build-server/azure-devops/fig11.png
+[12]: /img/advanced-topics/build-server/azure-devops/fig12.png
+[13]: /img/advanced-topics/build-server/azure-devops/fig13.png
+[14]: /img/advanced-topics/build-server/azure-devops/fig14.png
+[15]: /img/advanced-topics/build-server/azure-devops/fig15.png
+[16]: /img/advanced-topics/build-server/azure-devops/fig16.png
+[17]: /img/advanced-topics/build-server/azure-devops/fig17.png
+[18]: /img/advanced-topics/build-server/azure-devops/fig18.png
+[19]: /img/advanced-topics/build-server/azure-devops/fig19.png
+
+
+
+    
+
diff --git a/docs/advanced-topics/build-server/azdo/self-hosted-agent-yml-pipeline.md b/docs/advanced-topics/build-server/azdo/self-hosted-agent-yml-pipeline.md
new file mode 100644
index 00000000..689933ed
--- /dev/null
+++ b/docs/advanced-topics/build-server/azdo/self-hosted-agent-yml-pipeline.md
@@ -0,0 +1,70 @@
+---
+title: AzDO YAML Pipeline Using Self Hosted Agent 
+page_title: Test Studio Tests in Azure DevOps YAML Pipeline Using Self-Hosted Agent
+description: "Integrate Test Studio tests in Azure DevOps continuous integration. Execute Test Studio tests with Azure DevOps YAML Pipeline configured with Self Hosted agent."
+position: 3
+---
+# Test Studio Tests in Azure DevOps YAML Pipeline Using Self-Hosted Agent
+
+<a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests can be successfully integrated for execution with the Azure DevOps pipelines. 
+
+Below is a sample YAML pipeline using self-hosted agent machine which follows the instructions for <a href="/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline#add-command-line-agent-task-to-execute-test-or-test-list" target="_blank">building the classic pipeline using self-hosted agent</a>.
+
+> __Tip!__
+><br>
+> Double check if you have covered all <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests#choose-the-configuration-to-setup" target="_blank">prerequisites for this setup</a>.
+
+```YAML
+trigger:
+- main
+
+pool: 
+ name: selfHostedAgentPool
+
+steps: 
+
+# Specify test list to execute
+- script: |
+    "C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" ^
+      list="$(System.DefaultWorkingDirectory)\navToTSPage\TestLists\openTSPage.aiilist" ^
+      result="openTSPage" ^
+      settings="$(System.DefaultWorkingDirectory)\navToTSPage\local-run-settings-using-ff.json" ^
+      junit
+  displayName: 'CMD Execute Test List'
+  continueOnError: true
+
+# Publish JUnit result
+- task: PublishTestResults@2 
+  displayName: 'Publish Test Results **.xml' 
+  condition: succeededOrFailed()
+  inputs: 
+    testResultsFiles: '**/*.xml' 
+    searchFolder: '$(System.DefaultWorkingDirectory)\navToTSPage\Results' 
+    failTaskOnFailedTests: true
+    testRunTitle: 'Test Run - openTSPage'
+
+# Publish aiiresult file
+- task: PublishPipelineArtifact@1
+  displayName: 'Publish aiiresult file'
+  condition: succeededOrFailed()
+  inputs:
+    targetPath: '$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage.aiiresult'
+    artifact: 'aiiresult - openTSPage'
+
+# Check if failure details exists 
+- script: |
+    if exist "$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage_files" (
+      echo "##vso[task.setvariable variable=folderExists]true"
+    ) else (
+      echo "##vso[task.setvariable variable=folderExists]false"
+    )
+  displayName: 'Check if failure details folder exists'
+
+# Publish failure details if applicable
+- task: PublishPipelineArtifact@1
+  displayName: 'Publish failure details if applicable'
+  condition: and(succeededOrFailed(), eq(variables['folderExists'], 'true'))
+  inputs:
+    targetPath: '$(System.DefaultWorkingDirectory)\navToTSPage\Results\openTSPage_files'
+    artifact: 'failure-details - openTSPage'
+```
\ No newline at end of file
diff --git a/docs/advanced-topics/build-server/azure-devops.md b/docs/advanced-topics/build-server/azure-devops.md
index 929e2648..19471bb5 100644
--- a/docs/advanced-topics/build-server/azure-devops.md
+++ b/docs/advanced-topics/build-server/azure-devops.md
@@ -36,25 +36,25 @@ The tests should be run using <a href="https://docs.microsoft.com/en-us/azure/de
 
 To create such agent, follow the steps listed below
 
-1.&nbsp; Open the current **Project settings**.
+1. Open the current **Project settings**.
 
 ![Open the current project settings][2]
 
-2.&nbsp; Click on **Pipelines -> Agent Pools**.
+2. Click on **Pipelines -> Agent Pools**.
 
 ![Agent Pools][3]
 
-3.&nbsp; Add a new pool or open the default one.
+3. Add a new pool or open the default one.
 
 ![New Agent Pools][4]
 
-4.&nbsp; Click **New Agent**,
+4. Click **New Agent**,
 
 ![New Agent][5]
 
-5.&nbsp; Download the Agent to the corresponding physical or virtual machine as per the installation requirements above.
+5. Download the Agent to the corresponding physical or virtual machine as per the installation requirements above.
 
-6.&nbsp; Extract the Agent and run as Administrator.
+6. Extract the Agent and run as Administrator.
 
 ![Start Agent][6]
 
@@ -62,55 +62,55 @@ To create such agent, follow the steps listed below
 
 ### Configure a Self-hosted Agent
 
-1.&nbsp; Enter server URL: i.e. https://dev.azure.com/OrganizationName.
+1. Enter server URL: i.e. https://dev.azure.com/OrganizationName.
 
-2.&nbsp; Create Personal Access Token (PAT) as described <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops#permissions" target="_blank">here</a> and save it.
+2. Create Personal Access Token (PAT) as described <a href="https://docs.microsoft.com/en-us/azure/devops/pipelines/agents/v2-windows?view=azure-devops#permissions" target="_blank">here</a> and save it.
 
-3.&nbsp; Choose PAT for authentication type and paste yours.
+3. Choose PAT for authentication type and paste yours.
 
-4.&nbsp; Choose the Agent pool you created earlier.
+4. Choose the Agent pool you created earlier.
 
-5.&nbsp; Choose Agent name, the default name is the machine name on which it is hosted.
+5. Choose Agent name, the default name is the machine name on which it is hosted.
 
-6.&nbsp; Choose a work folder or press enter for the default one _work sub-folder.
+6. Choose a work folder or press enter for the default one _work sub-folder.
 
-7.&nbsp; Select N when asked to enter agent as a service.
+7. Select N when asked to enter agent as a service.
 
-8.&nbsp; Enter configure autologon and run agent on startup Y/N is optional.
+8. Enter configure autologon and run agent on startup Y/N is optional.
 
 ![Configure Agent][7]
 
-9.&nbsp; Upon successful configuration the config console will close, so execute run.cmd in console to trigger the Agent.
+9. Upon successful configuration the config console will close, so execute run.cmd in console to trigger the Agent.
 
 ![Trigger Agent][8]
 
 ### Run Tests on Agent
 
-1.&nbsp; Go to **Pipelines >> Builds >> Create new**.
+1. Go to **Pipelines >> Builds >> Create new**.
 
 ![Create Pipeline][9]
 
-2.&nbsp; For this setup choose the option to **Use the classic editor**.
+2. For this setup choose the option to **Use the classic editor**.
 
 ![Create Pipeline][10]
 
-3.&nbsp; Choose the repository where your code is and click **Continue**.
+3. Choose the repository where your code is and click **Continue**.
 
 ![Choose repo][11]
 
-4.&nbsp; Choose **Empty job** as a template for the build
+4. Choose **Empty job** as a template for the build
 
 ![Choose empty job][12]
 
-5.&nbsp; Select a pipeline and choose the Agent pool configured earlier.
+5. Select a pipeline and choose the Agent pool configured earlier.
 
 ![Select pipeline and agent pool][13]
 
-6.&nbsp; Create a new task on the **Agent -> Utility -> Command line**.
+6. Create a new task on the **Agent -> Utility -> Command line**.
 
 ![Command line new task][14]
 
-7.&nbsp; Insert a command which triggers the test execution via the Test Studio CLI Runner called ArtOfTest.Runner.exe - see the <a href="/features/test-runners/artoftest-runner" target="_blank">CLI runner syntax options here</a>. 
+7. Insert a command which triggers the test execution via the Test Studio CLI Runner called ArtOfTest.Runner.exe - see the <a href="/features/test-runners/artoftest-runner" target="_blank">CLI runner syntax options here</a>. 
 
 > __Note!__ The __Publish results__ task in the Azure pipeline supports reading results in _junit_ format. Test Studio CLI runner provides the option to automatically output the results in that format, so if you intend to use that task __make sure you add the _junit_ option in the command__.
 
@@ -118,11 +118,11 @@ The below example executes a test list.
 
 ![Command line script][15]
 
-8.&nbsp; Select **Continue on error** from the Command line script **Control Options**, if you’d like to complete a results' upload task (see next point) even if the test execution task fails.
+8. Select **Continue on error** from the Command line script **Control Options**, if you’d like to complete a results' upload task (see next point) even if the test execution task fails.
 
 ![Control Options][16]
 
-9.&nbsp; To add a **Publish Test Result** task, select the folder to which the test results are deployed and choose to upload all .xml files **.xml for file search for example. 
+9. To add a **Publish Test Result** task, select the folder to which the test results are deployed and choose to upload all .xml files **.xml for file search for example. 
 
 ![Publish Test results task][17]
 
diff --git a/docs/advanced-topics/build-server/bamboo.md b/docs/advanced-topics/build-server/bamboo.md
index 66f9c19a..e61ecba7 100644
--- a/docs/advanced-topics/build-server/bamboo.md
+++ b/docs/advanced-topics/build-server/bamboo.md
@@ -1,6 +1,5 @@
 ---
 title: Bamboo CI
-
 page_title: Bamboo Test Studio Tests Integration
 description: "Integrate Test Studio tests in bamboo continuous integration. Execute Test Studio tests with Bamboo"
 position: 8
@@ -33,15 +32,15 @@ First step is to add new executable, it's path should be path to the Test Studio
 
 To configure the task add following arguments:
 
-```
+````
 list="PATH_TO_PROJECT\TEST_LIST_NAME.aiilist" out=${bamboo.build.working.directory} junitstep
-```
+````
 
-**OR**
+<strong>OR</strong>
 
-```
+````
 test="PATH_TO_PROJECT\TEST_NAME.tstest" out=$bamboo.build.working.directory} junitstep
-```
+````
 
 ![Command task][5]
 
@@ -57,7 +56,7 @@ test="PATH_TO_PROJECT\TEST_NAME.tstest" out=$bamboo.build.working.directory} jun
 
 Source of the script:
 
-```
+````
 Write-Output $env:WORKDIR;
 
 Get-ChildItem $env:WORKDIR -Filter *.xml | 
@@ -67,14 +66,14 @@ Foreach-Object {
     $Utf8NoBomEncoding = New-Object System.Text.UTF8Encoding($False)
     [System.IO.File]::WriteAllLines($_.FullName, $MyFile, $Utf8NoBomEncoding)
 }
-```
+````
 
 Save the script in desired location.
 Add following Environment variable to the task:
 
-```
+````
 WORKDIR=${bamboo.build.working.directory}
-```
+````
 
 ![Script config][7]
 
diff --git a/docs/advanced-topics/build-server/cruise-control.net-builds.md b/docs/advanced-topics/build-server/cruise-control.net-builds.md
index 92384dc8..ad9dd167 100644
--- a/docs/advanced-topics/build-server/cruise-control.net-builds.md
+++ b/docs/advanced-topics/build-server/cruise-control.net-builds.md
@@ -2,7 +2,7 @@
 title: CruiseControl.NET Builds
 page_title: CruiseControl.NET Builds
 description: "Integrate Test Studio tests in CruiseControl.NET continuous integration builds. Execute Test Studio tests with CruiseControl.NET"
-position: 2
+position: 7
 ---
 # Telerik Testing Framework and CruiseControl.NET
 
@@ -35,7 +35,7 @@ With CruiseControl.NET you have two different build configurations you can use.
 
 To build using the <a href="http://www.cruisecontrolnet.org/projects/ccnet/wiki/Visual_Studio_Task" target="_blank">Visual Studio task</a>, you simply add the task configuration to your project file. The following example assumes you're using Visual Studio 2010. Refer to the CruiseControl.NET documentation for other settings to make it work with other versions of Visual Studio. It should look something like this:
 
-```XML
+````XML
 <cruisecontrol xmlns:cb="urn:ccnet.config.builder">
   <project name="Test Studio Unit Tests For Project Sydney">
     <sourcecontrol type="enter your type here">
@@ -57,13 +57,13 @@ To build using the <a href="http://www.cruisecontrolnet.org/projects/ccnet/wiki/
     </publishers>
   </project>
 </cruisecontrol>
-```
+````
 
 ### 4.1.2 Building Using the MSBuild Task
 
 This method is pretty much the same but instead of a Visual Studio task we replace it with a <a href="http://www.cruisecontrolnet.org/projects/ccnet/wiki/MsBuild_Task" target="_blank">MSBuild task</a>. It should look something like this:
 
-```XML
+````XML
 <cruisecontrol xmlns:cb="urn:ccnet.config.builder">
   <project name="WebAii Unit Tests For Project Sydney">
     <sourcecontrol type="enter your type here">
@@ -86,7 +86,7 @@ This method is pretty much the same but instead of a Visual Studio task we repla
     </publishers>
   </project>
 </cruisecontrol>
-```
+````
 
 ### 4.2 Adding a Run Tests Task
 
@@ -94,7 +94,7 @@ The program that runs Visual Studio unit tests is <a href="http://msdn.microsoft
 If you're using NUnit or something similar you can skip this section but be sure to add an appropriate NUnit (or whatever testing framework you use) test task to your project.
 An MSTest task is an "Exec" task to CruiseControl.NET. It should look something like this:
 
-```XML
+````XML
 <cruisecontrol xmlns:cb="urn:ccnet.config.builder">
   <project name="QuickStarts_VSTS_CS_1.1">
     <sourcecontrol type="...">
@@ -121,11 +121,11 @@ An MSTest task is an "Exec" task to CruiseControl.NET. It should look something
     </publishers>
   </project>
 </cruisecontrol>
-```
+````
 
 If you want to run a suite of tests, add them to a Visual Studio test list and use a buildArgs like this:
 
-```XML
+````XML
 <cruisecontrol xmlns:cb="urn:ccnet.config.builder">
   <project name="QuickStarts_VSTS_CS_1.1">
     <sourcecontrol type="...">
@@ -152,13 +152,13 @@ If you want to run a suite of tests, add them to a Visual Studio test list and u
     </publishers>
   </project>
 </cruisecontrol>
-```
+````
 
 ### 4.3 Publishing Test Results
 
 You need to merge the generated .trx file from MSTest into the build results. Add something like this to the 'publishers' section of your project configuration:
 
-```XML
+````XML
   <publishers>
       <!--to get the test results in the dashboard we have to merge the results XML file -->
       <merge>
@@ -168,14 +168,14 @@ You need to merge the generated .trx file from MSTest into the build results. Ad
       </merge>
       <xmllogger />
     </publishers>
-```
+````
 
 ### 4.4 Publishing Test Results
 
 One caveat to using MSTest is that you must delete the .trx file it creates before doing another test run. Otherwise MSTest will fail indicating it was unable to create the output file.
 This is done via another "Exec" task in ccnet.config. Place this section just in before your Exec task that runs MSTest. It probably would be best to place it at the beginning of the build because if a build fails (which causes CruiseControl.NET to skip any remaining tasks) to compile, CruiseControl.NET will still pick up and merge any left over .trx file into the build log:
 
-```XML
+````XML
 <exec>
         <!--Delete the testResults.trx first. This is required as MsTest will not create the file if
             it exists this could be merged with the mstest action in a single batch file-->
@@ -184,7 +184,7 @@ This is done via another "Exec" task in ccnet.config. Place this section just in
         <buildArgs>/c if exist testResults.trx del testResults.trx /f</buildArgs>
         <buildTimeoutSeconds>30</buildTimeoutSeconds>
       </exec>
-```
+````
 
 ### 4.5 Publishing Test Results
 
@@ -208,7 +208,7 @@ This section is a list of .xsl files that will be used after every build to gene
 
 If you are running Test Studio tests you will want to install and use the TestStudioMSTest2010Report.xsl file. Download the file from the previous link and place it in the folder C:\Program Files (x86)\CruiseControl.NET\webdashboard\xsl. Next we need to add TestStudioMSTest2010Report.xsl so that it looks something like this:
 
-```XML
+````XML
 <dashboard>
   <remoteServices>
 
@@ -228,11 +228,11 @@ If you are running Test Studio tests you will want to install and use the TestSt
     </buildPlugins>
   </plugins>
 </dashboard>
-```
+````
 
 If instead you are running Telerik Testing Framework coded unit tests we need to add MsTestSummary2010.xsl and MsTestReport2010 so that it looks something like this:
 
-```XML
+````XML
 <dashboard>
   <remoteServices>
 
@@ -253,9 +253,9 @@ If instead you are running Telerik Testing Framework coded unit tests we need to
     </buildPlugins>
   </plugins>
 </dashboard>
-```
+````
 
-### 5.2 Modifying the xslReportBuildPlugin Section###
+### 5.2 Modifying the xslReportBuildPlugin Section
 
 This section is used to generate a menu of the different detail reports you can display. After you make these changes you'll get something that looks like this:
 
@@ -263,7 +263,7 @@ This section is used to generate a menu of the different detail reports you can
 
 Note the last entry in the list. To obtain this entry we need to modify this section in the dashboard.config file to look something like this:
 
-```XML
+````XML
 <?xml version="1.0" encoding="utf-8" ?>
 <dashboard>
 
@@ -278,7 +278,7 @@ Note the last entry in the list. To obtain this entry we need to modify this sec
     </buildPlugins>
   </plugins>
 </dashboard>
-```
+````
 
 After making the above changes, the next build will successfully display test results.
 
diff --git a/docs/advanced-topics/build-server/docker-container-testing.md b/docs/advanced-topics/build-server/docker-container-testing.md
index 3ef88133..8f63f9bf 100644
--- a/docs/advanced-topics/build-server/docker-container-testing.md
+++ b/docs/advanced-topics/build-server/docker-container-testing.md
@@ -2,7 +2,7 @@
 title: Docker Container Testing
 page_title: Use Docker Container for Test Studio Test Execution
 description: "Docker container testing is compatible with Test Studio. Execute Test Studio tests in a Docker container. Headless test execution of Test Studio tests in Docker container."
-position: 9
+position: 3
 ---
 # Docker Container Testing with Test Studio
 
@@ -41,10 +41,10 @@ Below are listed the steps to setup a Docker container for testing.
 
 2.&nbsp; Pull the <a href="https://hub.docker.com/_/microsoft-windows" target="_blank">official Microsoft Windows Docker image</a> from the Docker Hub. Use the command that is provided in the Docker Hub and make sure to specify the exact build to be pulled.
 
-```
+````
 //For Windows build 1909, use the following command
 docker pull mcr.microsoft.com/windows:1909
-```
+````
 
 > __Note__
 > <br>
@@ -68,9 +68,9 @@ Then, expand the _Optional Settings_ and specify **Host Path** and **Container P
 
 __Install both Test Studio Run-Time and Chrome browser enterprise edition in passive mode__, because there is no UI in the container and active installation can not complete. You can use the following command, but make sure that each installer is finished without errors before you proceed with the next one.
 
-```
+````
 msiexec.exe /i msiInstallerFileName.msi /passive /le c:\tools\errorLogForThisInstaller.txt
-```
+````
 
 > __Note__
 > <br>
@@ -88,10 +88,10 @@ After completing the above steps in this article, you need to copy the project,
 
 Open the container's Command Line Interface (CLI) and use the <a href="/features/test-runners/artoftest-runner" target="_blank">ArtOfTest.Runner.exe</a> to start the execution. This test runner provide multiple options for execution and output, which are all explained in the linked documentation. The below example command triggers a test list execution.
 
-```
+````
 //navigate to the Test Studio installation bin sub-folder
 ArtOfTest.Runner.exe /list="full path to the test list file with extension .aiilist"
-```
+````
 
 You can apply specific settings for Docker container test list execution, like the browser type. Since the test list execution runs only in Headless mode, you can choose different <a href="/features/test-runners/artoftest-runner#settings-option" target="_blank">settings file</a> to be used from the ArtOfTest.Runner.exe. Using such file allows you to not change the <a href="/features/test-lists/test-list-settings" target="_blank">Test List Settings</a> on your original test list and still execute it in Headless mode in the container.
 
diff --git a/docs/advanced-topics/build-server/execute-test-with-vstest.md b/docs/advanced-topics/build-server/execute-test-with-vstest.md
index c77568da..7836eaf5 100644
--- a/docs/advanced-topics/build-server/execute-test-with-vstest.md
+++ b/docs/advanced-topics/build-server/execute-test-with-vstest.md
@@ -4,7 +4,7 @@ page_title: Execute Test Studio Test and Test lists with VSTestConsole.exe
 description: "Integrate Test Studio tests in TFS continuous integration builds. Execute Test Studio tests and test lists with VSTestConsole.exe"
 position: 10
 ---
-# Execute Test Studio Tests with VSTest.Console.exe #
+# Execute Test Studio Tests with VSTest.Console.exe
 
 The <a href="https://msdn.microsoft.com/en-us/library/jj155796.aspx" target="_blank">VSTest.Console.exe</a> in Visual Studio discovers and runs tests, including Test Studio tests and <a href="/automated-tests/vs-plugin/test-lists-in-vs-2017-2019" target="_blank">test lists</a>.
 
@@ -25,11 +25,11 @@ __3.__&nbsp; Change the __working folder__ to this, which __contains the vstest.
 
 __4.__&nbsp; __Set these two variables__ - ***TS_PROJECT_PATH*** (the folder, which contains the Test Studio project _Settings.aiis_) and ***TS_DLL_PATH*** (the folder, which contains the built project dll - by default it is in the project root under _\bin\Debug_).
 
-```
+````
 set TS_PROJECT_PATH=C:\Projects\TestStudioProject11\TestStudioProject11
 
 set TS_DLL_PATH=C:\Projects\TestStudioProject11\TestStudioProject11\bin\Debug\TestStudioProject11.dll
-```
+````
 
 > __Important__
 ><br>
@@ -49,7 +49,7 @@ __6.__&nbsp; __Visual Studio 2019 requires the argument /Settings:[_file name_]_
 
 Below are listed sample commands to execute a Test Studio test and test list with the **VSTestConsole.exe in Visual Studio 2019**, after the **TS\_PROJECT\_PATH** and **TS\_DLL\_PATH** variables are set for the current instance of the VS Developer Command Prompt:
 
-```
+````
 trigger Parent.tstest run
 
 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console.exe "C:\Projects\TestStudioProject11\TestStudioProject11\Parent.tstest" /TestAdapterPath:"C:\Program Files (x86)\Progress\Test Studio\VS2019" /Settings:"C:\Projects\TestStudioProject11\TestStudioProject11\TestSettings1.testsettings
@@ -57,4 +57,4 @@ C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\Com
 trigger sampleList.aiilist run
 
 C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE\CommonExtensions\Microsoft\TestWindow>vstest.console.exe  "C:\Projects\TestStudioProject11\TestStudioProject11\TestLists\sampleList.aiilist" /TestAdapterPath:"C:\Program Files (x86)\Progress\Test Studio\VS2019" /Settings:"C:\Projects\TestStudioProject11\TestStudioProject11\TestSettings1.testsettings
-```
+````
diff --git a/docs/advanced-topics/build-server/jenkins-ci-plugin.md b/docs/advanced-topics/build-server/jenkins-ci-plugin.md
index 4ab67f43..e569d39c 100644
--- a/docs/advanced-topics/build-server/jenkins-ci-plugin.md
+++ b/docs/advanced-topics/build-server/jenkins-ci-plugin.md
@@ -2,9 +2,9 @@
 title: Jenkins CI Plugin
 page_title: Jenkins CI Plugin
 description: "Test Studio plugin for Jenkins Continuous integration setup. Configure the Test Studio plugin for Jenkins CI."
-position: 2
+position: 5
 ---
-# Test Studio Plugin for Jenkins CI #
+# Test Studio Plugin for Jenkins CI
 
 The Test Studio Plugin for Jenkins allows you to build and execute <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests and test lists in Jenkins CI environment and easily explore the generated JUnit xml results in the built-in Jenkins functionality.
 
@@ -36,7 +36,7 @@ The *project root folder* and *settings file* fields accept relative path to the
 
 Your test execution step is now ready to save and run.
 
-[1]: /img/advanced-topics/build-server/jenkins-ci-plugin/fig1.png
+
 [2]: /img/advanced-topics/build-server/jenkins-ci-plugin/fig2.png
 [3]: /img/advanced-topics/build-server/jenkins-ci-plugin/fig3.png
 [4]: /img/advanced-topics/build-server/jenkins-ci-plugin/fig4.png
diff --git a/docs/advanced-topics/build-server/jenkins-ci.md b/docs/advanced-topics/build-server/jenkins-ci.md
index 948b6e41..3954bbca 100644
--- a/docs/advanced-topics/build-server/jenkins-ci.md
+++ b/docs/advanced-topics/build-server/jenkins-ci.md
@@ -3,62 +3,51 @@ title: Jenkins CI
 page_title: Jenkins CI
 description: "Integrate Test Studio tests in Jenkins continuous integration. Execute Test Studio tests with Jenkins."
 previous_url: /user-guide/command-line-test-execution/continuous-integration/jenkins_ci.aspx, /user-guide/command-line-test-execution/continuous-integration/jenkins_ci
-position: 2
+position: 4
 ---
 # Jenkins CI
 
 Build and execute <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> tests in Jenkins CI by following these steps:
 
-1.&nbsp; **Install the Java Web Archive (.war) for Jenkins CI**. Test Studio tests should not be run from a Windows Service account. Because the Windows native package for Jenkins CI runs as a Windows Service, Test Studio requires the Java Web Archive version to run properly.
+## Install the Java Web Archive (.war) for Jenkins CI
 
-![Download Jenkins][1]
-
-2.&nbsp; **Run the Jenkins Listener on a custom port**. By default, the Jenkins Listener runs on port 8009 -- the same port as the Test Studio Scheduling Service. When installing the .war, use a command line argument to configure a different, non-conflicting port number for the listener (that is, avoid port numbers 8009, 8010, 8011, 8012, and 8013). For example:
-
-*java -jar jenkins.war --ajp13Port=8019*
-
-> As of release **R1 2018 (v2018.1.301)** you could install and use the <a href="/advanced-topics/build-server/jenkins-ci-plugin" target="_blank">Jenkins Test Studio Plugin</a>.
-
-3.&nbsp; **Create a free-style software project**. Create a job and select 'Build a free-style software project'.
-
-![Free-style software project][2]
-
-4.&nbsp; **Add a Windows batch command build step**. Under the 'Add build step menu,' select 'Execute Windows batch command'.
-
-![Command build step][3]
+Test Studio tests should not be run from a Windows Service account. Because the Windows native package for Jenkins CI runs as a Windows Service, Test Studio requires the Java Web Archive version to run properly.
 
-5.&nbsp; **Input ArtOfTest.Runner command line command to execute tests**. Under 'Execute Windows batch command', input the ArtOfTest.Runner command to execute your test or test list, including <a href="/features/test-runners/artoftest-runner" target="_blank">full path to ArtOfTest.Runner.exe and appropriate arguments</a>.
+![Download Jenkins][1]
 
-![Arguments][4]
+## Run the Jenkins Listener on a Custom Port
 
-Your test execution step is now ready to save and run.
+By default, the Jenkins Listener runs on port 8009 -- the same port as the Test Studio Scheduling Service. When installing the .war, use a command line argument to configure a different, non-conflicting port number for the listener (that is, avoid port numbers 8009, 8010, 8011, 8012, and 8013). For example:
 
-##Build a Visual Studio project or a Solution
+```
+java -jar jenkins.war --ajp13Port=8019
+```
 
-1. **Configure MSBuild Plugin to build coded tests**.
+> Optionally you can use the <a href="/advanced-topics/build-server/jenkins-ci-plugin" target="_blank">Jenkins Test Studio Plugin</a> to setup Jenkins
 
-	1.1 Under the **Jenkins** menu, open **Manage Jenkins > Manage Plugins**.
+## Create a Free-style Software Project 
 
-	![Manage plugins][5]
+Create a job and select 'Build a free-style software project'.
 
-	1.2 Select and install the **MSBuild Plugin**.
+![Free-style software project][2]
 
-	![MSBuild Plugin][6]
+## Add a Windows Batch Command Build Step 
 
-	1.3 Configure MSBuild Plugin according to <a href="https://wiki.jenkins-ci.org/display/JENKINS/MSBuild+Plugin" target="_blank">Jenkins CI instructions</a>.
+Under the 'Add build step menu,' select 'Execute Windows batch command'.
 
-2. **Add MSBuild Step**. Under **Build**, open the **Add build step** and select **Build a Visual Studio project or solution using MSBuild**.
+![Command build step][3]
 
-	![MSBuild Step][7]
+## Input ArtOfTest.Runner Command to Execute Test
 
-3. **Specify a Visual Studio project or solution for your test**. Save the build configuration.
+Under 'Execute Windows batch command', input the ArtOfTest.Runner command to execute your test or test list, including <a href="/features/test-runners/artoftest-runner" target="_blank">full path to ArtOfTest.Runner.exe and appropriate arguments</a>.
 
-	![Specify a Visual Studio project][8]
+![Arguments][4]
 
-##Attach the results files to the Job##
+Your test execution step is now ready to save and run.
 
-1.	Add "**out**" parameter in the batch command. It should point to the default jenkins workspace **(C:\Users\[userName]\.jenkins\jobs\test\workspace\%JOB_NAME%%BUILD_NUMBER%**) so the results files are outputted in a folder with an unique name (Job Name + Build Number).
+## Attach the Results Files to the Job 
 
+1.	Add "**out**" parameter in the batch command. It should point to the default jenkins workspace `C:\Users\[userName]\.jenkins\jobs\test\workspace\%JOB_NAME%%BUILD_NUMBER%` so the results files are outputted in a folder with an unique name (Job Name + Build Number).
 	
 	![Out parameter][9]
 
@@ -66,7 +55,7 @@ Your test execution step is now ready to save and run.
 
 	![Archive the artifacts][10]
 
-3. Type *${JOB_NAME}${BUILD_NUMBER}\\*** in the "**Files to archive**" field so all the results files can be taken.
+3. Type `${JOB_NAME}${BUILD_NUMBER}` in the "**Files to archive**" field so all the results files can be taken.
 
 	![Files to archive][11]
 
@@ -80,36 +69,42 @@ Your test execution step is now ready to save and run.
 
 Your Jenkins CI build is now ready to run.
 
-**Disclaimer**:
+## Disclaimer
 
 In case you are running Test Studio tests using <a href="http://www.donaldsimpson.co.uk/2011/10/06/jenkins-slave-nodes/" target="_blank">Jenkins slaves</a> you may experience the following exception:
 
 The process is not running in 'Interactive Mode'! The 'DialogMonitor' has been disabled for this Browser.
 
-*TestExecuteProxy.ExecuteTest() : EXCEPTION! (see below)* <br>
-*Outer Exception Type: System.TimeoutException*<br>
-*Message: Wait for condition has timed out*<br>
-*HRESULT: 0x80131505 (Official ID (if app.) = COR_E_TIMEOUT, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5381)*<br>
-*Call Stack:*<br>
-*at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)*<br>
-*at ArtOfTest.Common.WaitSync.For&#91;T&#93;(Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)*<br>
-*at ArtOfTest.Common.WaitSync.For&#91;T&#93;(Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)*<br>
-*at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)*<br>
-*at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect,*<br>
-*ProcessWindowStyle windowStyle, String arguments)*<br>
-*at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)*<br>
-*at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)*<br>
-*at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)*<br>
-
-The problem is that Jenkins slaves cannot be ran as service. This will cause the automation to fail with the above exception. In this case you should start Jenkins service headless.
-
-Example:
-
-**java -jar slave.jar -jnlpurl http://$HOST:$PORT/computer/$SLAVEMACHINE/slave-agent.jnlp**
+```
+TestExecuteProxy.ExecuteTest() : EXCEPTION! (see below)
+Outer Exception Type: System.TimeoutException
+Message: Wait for condition has timed out
+HRESULT: 0x80131505 (Official ID (if app.) = COR_E_TIMEOUT, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5381)
+Call Stack:
+at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
+at ArtOfTest.Common.WaitSync.For&#91;T&#93;(Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
+at ArtOfTest.Common.WaitSync.For&#91;T&#93;(Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
+at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
+at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect,*<br>
+*ProcessWindowStyle windowStyle, String arguments)
+at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)
+at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)
+at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
+```
+
+The error is related to the fact that Jenkins slaves cannot be ran as service. This will cause the automation to fail with the above exception. In this case you should start Jenkins service headless.
+
+__Example__:
+
+```
+java -jar slave.jar -jnlpurl http://$HOST:$PORT/computer/$SLAVEMACHINE/slave-agent.jnlp
+```
 
 or
 
-**javaws http://$HOST:$PORT/computer/$SLAVEMACHE/slave-agent.jnlp**
+```
+javaws http://$HOST:$PORT/computer/$SLAVEMACHE/slave-agent.jnlp
+```
 
 [1]: /img/advanced-topics/build-server/jenkins-ci/fig1.png
 [2]: /img/advanced-topics/build-server/jenkins-ci/fig2.png
diff --git a/docs/advanced-topics/build-server/microsoft-hosted-agent-testing.md b/docs/advanced-topics/build-server/microsoft-hosted-agent-testing.md
index 9ad3db2d..463a692d 100644
--- a/docs/advanced-topics/build-server/microsoft-hosted-agent-testing.md
+++ b/docs/advanced-topics/build-server/microsoft-hosted-agent-testing.md
@@ -93,9 +93,9 @@ To trigger the installation of the downloaded package, add the next task and cho
 
 The installation can be triggered with a <a href="https://docs.microsoft.com/en-us/windows-server/administration/windows-commands/msiexec" target="_blank">msiexec command</a> in passive mode due to the lack of UI session. Find below an example command to use in the task.
 
-```
+````
 msiexec.exe /i c:\TestStudio_Runtime_2021_3_1103_1.msi /passive /le c:\errorlog.txt
-```
+````
 
 ### Execute the Tests on Microsoft-hosted Agent
 
diff --git a/docs/advanced-topics/build-server/team-city-builds.md b/docs/advanced-topics/build-server/team-city-builds.md
index f2085c53..8b280b90 100644
--- a/docs/advanced-topics/build-server/team-city-builds.md
+++ b/docs/advanced-topics/build-server/team-city-builds.md
@@ -2,7 +2,7 @@
 title: TeamCity Builds
 page_title: TeamCity Test Execution
 description: "Integrate Test Studio tests in TeamCity continuous integration. Execute Test Studio tests with TeamCity."
-position: 2
+position: 6
 ---
 # TeamCity Test Execution
 
@@ -15,7 +15,7 @@ The below steps will guide you through the necessary TeamCity project adjustment
 There are no specifics in installation of the TeamCity server. To be able to execute automated tests that include Windows and Browser interactions it is necessary to run build agent from command line.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Run the Build Agent
@@ -49,15 +49,15 @@ For "Build script content" enter:
 
 Path to Test Studio runner
 
-```
+````
 list="PATH_TO_PROJECT\TEST_LIST_NAME.aiilist" out="PATH_TO_RESULT_DIR"  junitstep
-```
+````
 
-**OR**
+<strong>OR</strong>
 
-```
+````
 test="PATH_TO_PROJECT\TEST_NAME.tstest" out="PATH_TO_RESULT_DIR" junitstep
-```
+````
 
 4.&nbsp; Add new Build Feature
 
@@ -70,9 +70,9 @@ For report type select "Ant JUnit" and save build feature.
 For "Monitoring rules" specify output directory from previous step and ad all xml files.
 
 Example:
-```
+````
 C:\Users\deyan\Desktop\TestStudioResults\*.xml
-```
+````
 
 [1]: /img/advanced-topics/build-server/team-city-builds/New_project.png
 [2]: /img/advanced-topics/build-server/team-city-builds/New_Build_config.png
diff --git a/docs/advanced-topics/build-server/ts-test-runner-app.md b/docs/advanced-topics/build-server/ts-test-runner-app.md
index 55a061b7..dd8bd957 100644
--- a/docs/advanced-topics/build-server/ts-test-runner-app.md
+++ b/docs/advanced-topics/build-server/ts-test-runner-app.md
@@ -2,7 +2,7 @@
 title: Test Studio Execution Client in CI Builds
 page_title: Test Studio Execution Client in CI
 description: "Use Test Studio Test Runner app to control the machine user session when running UI tests as part of CI pipeline. "
-position: 0
+position: 1
 ---
 # Test Studio Test Runner in CI Builds
 
@@ -157,11 +157,6 @@ This section appears only if there is an <a href="/features/dialogs-and-popups/d
 [0]: /img/features/scheduling-test-runs/create-execution-server/fig0.png
 [1]: /img/features/scheduling-test-runs/create-execution-server/fig1.png
 [1a]: /img/features/scheduling-test-runs/create-execution-server/fig1a.png
-[2]: /img/features/scheduling-test-runs/create-execution-server/fig2.png
-[3]: /img/features/scheduling-test-runs/create-execution-server/fig3.png
-[4]: /img/features/scheduling-test-runs/create-execution-server/fig4.png
-[5]: /img/features/scheduling-test-runs/create-execution-server/fig5.png
-[6]: /img/features/scheduling-test-runs/create-execution-server/fig6.png
 [6a]: /img/features/scheduling-test-runs/create-execution-server/fig6a.png
 [6b]: /img/features/scheduling-test-runs/create-execution-server/fig6b.png
 [6c]: /img/features/scheduling-test-runs/create-execution-server/fig6c.png
diff --git a/docs/advanced-topics/coded-samples/general/aborted-test-list-results.md b/docs/advanced-topics/coded-samples/general/aborted-test-list-results.md
index 568d3985..faa0ac38 100644
--- a/docs/advanced-topics/coded-samples/general/aborted-test-list-results.md
+++ b/docs/advanced-topics/coded-samples/general/aborted-test-list-results.md
@@ -1,26 +1,26 @@
 ---
 title: Record Results for Aborted Test List
 page_title: Record Results for Aborted Test List
-description: "Record Results for Aborted Test List in Test Studio."
+description: "Learn how to configure Test Studio to record and save results for executed tests even if a test list execution is aborted. This article explains how to enable step-by-step result persistence via configuration file or command line arguments."
 position: 1
 ---
-# Record results even if test list execution is aborted #
+# Record results even if test list execution is aborted 
 
 *I would like to have results file for the already executed tests if the test list execution is aborted at an earlier stage.*
 
-## Solution ##
+## Solution 
 
 Test Studio has the ability to store run results on each executed step and this could be turned on within the ***Telerik.TestStudio.Desktop.exe.config*** file. For the default installation, the file could be found in the following folder: *C:\Program Files (x86)\Progress\Test Studio\Bin*. Open the file in a text editor and set the **'PersistOnEachStep'** key value to True.
 
  
 
-```XML
+````XML
   <appSettings>
       <add key="CommandLineRun" value="True" />
       <add key="PersistOnEachStep" value="False" />
   </appSettings>
-```
+````
 
-## Command line runner arguments ##
+## Command line runner arguments 
 
 If you execute tests from <a href="/features/test-runners/artoftest-runner" target="_blank">the command line runner</a> you could set that value to "true" by passing an argument to the command to be executed. The 'PersistOnEachStep' is one of the general options available for modifying the command line test execution behavior. 
diff --git a/docs/advanced-topics/coded-samples/general/access-oracle-database.md b/docs/advanced-topics/coded-samples/general/access-oracle-database.md
index e5510c74..25d531d2 100644
--- a/docs/advanced-topics/coded-samples/general/access-oracle-database.md
+++ b/docs/advanced-topics/coded-samples/general/access-oracle-database.md
@@ -1,18 +1,18 @@
 ---
 title: Access Oracle Database
 page_title: Access Oracle Database
-description: "how to access an Oracle database through code in Test Studio coded step."
+description: "Learn how to connect to and query an Oracle database in Test Studio coded steps. This article covers installing Oracle Data Access Components, adding assembly references, building connection strings, and running SQL queries in C# and VB.NET"
 position: 1
 ---
-#How to Access an Oracle Database in Code#
+# How to Access an Oracle Database in Code
 
 Oracle database could be used as data source in a data driven test as described <a href="/features/data-driven-testing/add-data-source#add-a-database-source" target="_blank">here</a>. This is a built-in functionality for Test Studio but if using the Telerik Testing Framework the connection and interaction with the database need to be established step by step. This article demonstrates how to access an Oracle database through code.
 
-##Install Oracle Client##
+## Install Oracle Client
 
 To access the Oracle database in C# it is necessary to install <a href="http://www.oracle.com/technetwork/topics/dotnet/utilsoft-086879.html" target="_blank">**Oracle Data Access Components**</a>. That driver package contains the necessary libraries to refer in the project.
 
-##Add an Assembly Reference##
+## Add an Assembly Reference
 
 Once the ODAC is installed the following dll have to be <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">referred</a> in the project:
 
@@ -24,30 +24,30 @@ For default installation the dll file could be found in the Oracle data base ins
 
 Include the following *usings* in the code.
 
-```C#
+````C#
 using Oracle.DataAccess.Client;
 using Oracle.DataAccess.Types;
-```
-```VB
+````
+````VB
 import Oracle.DataAccess.Client
 import Oracle.DataAccess.Types
-```
+````
 
-##Data Connection String##
+## Data Connection String
 
 An Oracle connection string is required to identify the database to connect to. Here is an example:
 
-```
+````
 Data Source=XE;User Id=SYSTEM;Password=pass;
-```
+````
 
 Different connection strings could be used. See <a href="https://www.connectionstrings.com/oracle/" target="_blank">here</a> for more examples.
 
-##Sample Code##
+## Sample Code
 
 This code runs a simple query against a database table similar to <a href="/features/data-driven-testing/oracle-db-example" target="_blank">this example</a>:
 
-```C#
+````C#
 string oradb = "Data Source=XE;User Id=SYSTEM;Password=pass;";
 
 OracleConnection conn = new OracleConnection(oradb);
@@ -71,7 +71,7 @@ dr.Read();
 Log.WriteLine(dr.GetString(0).ToString());
 
 conn.Dispose();
-```
+````
 
 
 >This code won't run without modification. The database, table, and column in the original code won't exist in your environment unless you create the same database.
diff --git a/docs/advanced-topics/coded-samples/general/access-performance-data.md b/docs/advanced-topics/coded-samples/general/access-performance-data.md
deleted file mode 100644
index 22b34e65..00000000
--- a/docs/advanced-topics/coded-samples/general/access-performance-data.md
+++ /dev/null
@@ -1,141 +0,0 @@
----
-title: Access Performance Data
-page_title: Access Performance Data
-description: "access the results of a performance test in code in Test Studio coded step."
-position: 1
----
-#Access Performance Data#
-
-In order to access the results of a performance test in code, it will be necessary to create an <a href="execution-extensions" target="_blank">execution extension</a> library. The approach to this problem is to use a <a href="/getting-started/test-execution/test-lists-type-standalone#Performance" target="_blank">performance test list</a> to execute one or many performance tests. Then at the end of the execution to collect the data from each one of the performance test results files.
-
-### Preconditions
-
-1. Add a reference to the VS project for the following library located in product installation **\bin** folder:
-	- Telerik.TestStudio.Interfaces.dll
-1. Include in the project listed below namespaces:
-	- ArtOfTest.WebAii.Design.Execution.Profiler
-	- ArtOfTest.WebAii.Design.Execution.Profiler.Storage
-1. If not present - create *C:\temp* directory, where the new result file will be placed
-
-### Sample Code
-
-The following extension class will store the full path to each performance test result and its ID in a Dictionary data structure. This structure will be updated after each test completion in the *OnAfterTestCompleted()* method. Then at the end of the test list execution in *OnAfterTestListCompleted()* method - all files will be opened one by one to collect necessary data and save it in *C:\temp\lastPerformanceResults.txt* file.
-
-```C#
-namespace ExecutionExtensionSample
-{
-    using System.Collections.Generic;
-    using System.Data;
-    using ArtOfTest.WebAii.Design.Execution;
-    using ArtOfTest.WebAii.Design;
-    using ArtOfTest.WebAii.Design.ProjectModel;
-    // namespaces to include:
-    using ArtOfTest.WebAii.Design.Execution.Profiler;
-    using ArtOfTest.WebAii.Design.Execution.Profiler.Storage;
-
-    public class MyExecutionExtension : IExecutionExtension
-    {
-        // initialize the variable to save test ID and full path to the result file
-        private Dictionary<System.Guid, string> testIdAndPath = new Dictionary<System.Guid, string>();
-
-        public void OnAfterTestCompleted(ExecutionContext executionContext, TestResult result)
-        {
-            // add each test ID and result file path to the dictionary 
-            testIdAndPath.Add(System.Guid.Parse(result.TestId.ToString()), result.ProfilerResultsPath);
-        }
-
-        public void OnAfterTestListCompleted(RunResult result)
-        {
-            // 5 sec timeout to let the last result file to be created - extend it if necessary
-            System.Threading.Thread.Sleep(5000);
-
-            // open a file stream writer to collect the data from results in a new file
-            using (System.IO.StreamWriter file = new System.IO.StreamWriter(@"C:\temp\lastPerformanceResults.txt", true))
-            {
-                // loop over each result file 
-                foreach (var resultFile in this.testIdAndPath)
-                {
-                    file.WriteLine("Result ID: " + resultFile.Key);
-                    file.WriteLine("File Path: " + resultFile.Value);
-
-                    // load the ProfileResultFile
-                    ProfilerResultsFile resultsFile = ProfilerResultsFile.Load(resultFile.Key, resultFile.Value);
-
-                    // print each step values in the new result file
-                    foreach (ProfilerTestStep step in resultsFile.Steps)
-                    {
-                        // set here the necessary step property in [] to save in the new result file
-                        file.WriteLine("Some Property Value: " + step.[..].ToString());
-                    }
-                }
-            }
-        }
-
-        public void OnBeforeTestListStarted(TestList list)
-        {
-        }
-
-        public void OnBeforeTestStarted(ExecutionContext executionContext, Test test)
-        {
-        }
-
-        public DataTable OnInitializeDataSource(ExecutionContext executionContext)
-        {
-            return null;
-        }
-
-        public void OnStepFailure(ExecutionContext executionContext, AutomationStepResult stepResult)
-        {
-        }
-    }
-}
-```
-```VB
-Imports System.Collections.Generic
-Imports System.Data
-Imports ArtOfTest.WebAii.Design.Execution
-Imports ArtOfTest.WebAii.Design
-Imports ArtOfTest.WebAii.Design.ProjectModel
-Imports ArtOfTest.WebAii.Design.Execution.Profiler
-Imports ArtOfTest.WebAii.Design.Execution.Profiler.Storage
-
-Namespace ExecutionExtensionSample
-
-    Public Class MyExecutionExtension
-        Inherits IExecutionExtension
-
-        Private testIdAndPath As Dictionary(Of System.Guid, String) = New Dictionary(Of System.Guid, String)()
-
-        Public Sub OnAfterTestCompleted(ByVal executionContext As ExecutionContext, ByVal result As TestResult)
-            testIdAndPath.Add(System.Guid.Parse(result.TestId.ToString()), result.ProfilerResultsPath)
-        End Sub
-
-        Public Sub OnAfterTestListCompleted(ByVal result As RunResult)
-            System.Threading.Thread.Sleep(5000)
-            Using file As System.IO.StreamWriter = New System.IO.StreamWriter("C:\temp\lastPerformanceResults.txt", True)
-                For Each resultFile In Me.testIdAndPath
-                    file.WriteLine("Result ID: " & resultFile.Key)
-                    file.WriteLine("File Path: " & resultFile.Value)
-                    Dim resultsFile As ProfilerResultsFile = ProfilerResultsFile.Load(resultFile.Key, resultFile.Value)
-                    For Each [step] As ProfilerTestStep In resultsFile.Steps
-                        file.WriteLine("Some Property Value: " & [step].....ToString())
-                    Next
-                Next
-            End Using
-        End Sub
-
-        Public Sub OnBeforeTestListStarted(ByVal list As TestList)
-        End Sub
-
-        Public Sub OnBeforeTestStarted(ByVal executionContext As ExecutionContext, ByVal test As Test)
-        End Sub
-
-        Public Function OnInitializeDataSource(ByVal executionContext As ExecutionContext) As DataTable
-            Return Nothing
-        End Function
-
-        Public Sub OnStepFailure(ByVal executionContext As ExecutionContext, ByVal stepResult As AutomationStepResult)
-        End Sub
-    End Class
-End Namespace
-```
diff --git a/docs/advanced-topics/coded-samples/general/access-sql-database.md b/docs/advanced-topics/coded-samples/general/access-sql-database.md
index 415e31b0..c7973ddc 100644
--- a/docs/advanced-topics/coded-samples/general/access-sql-database.md
+++ b/docs/advanced-topics/coded-samples/general/access-sql-database.md
@@ -1,15 +1,14 @@
 ---
 title: Access SQL Database
 page_title: Access SQL Database
-description: "how to access an SQL database through code in Test Studio coded step."
-previous_url: /user-guide/code-samples/general/access-sql-database.aspx, /user-guide/code-samples/general/access-sql-database
+description: "Learn how to connect to and interact with a SQL database in Test Studio coded steps. This article covers adding assembly references, building connection strings, and using C# or VB.NET code to read from and write to SQL databases."
 position: 1
 ---
-#How to Access a SQL Database in Code#
+# How to Access a SQL Database in Code
 
 > You can access an SQL database in a data driven test, as seen <a href="/features/data-driven-testing/add-data-source#add-a-database-source" target="_blank">here</a>. This is built-in functionality for Test Studio, but not for Telerik Testing Framework. This article demonstrates how to access a SQL database through code, which allows for greater flexibility. Also, writing into a database is only possible with a coded solution.
 
-##Add Assembly Reference##
+## Add Assembly Reference
 
 Use the *System.Data.SqlClient* API. You'll need to add an assembly reference to it, as seen <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">here</a>. This API is part of the *System.Data* assembly. This assembly is located, by default, in the following location (on a 64-bit Windows 7 machine with .NET 4.0):
 
@@ -19,22 +18,22 @@ If a reference to System.Data 2.0 already exists, remove it add it again from th
 
 Ensure you add the *using* or *Imports* statement to the top of the code-behind file. Click the View Class button, scroll to the top of the code, and add this line:
 
-```C#
+````C#
 using System.Data.SqlClient;
-```
-```VB
+````
+````VB
 Imports System.Data.SqlClient;
-```
+````
 
-##Sample Code##
+## Sample Code
 
 Here we've create a SQL database named **myFirstDB**. This database contains a table named **Table_1**. This table contains a column named **City**.
 
 ![Database][1]
 
-###Read from SQL Database###
+### Read from SQL Database
 
-```C#
+````C#
 //Define a new SQL connection with a connection string. 
 //The connection string will be different depending on your environment and the name of the database, table, etc.
 //See http://www.connectionstrings.com for connection string examples.
@@ -57,8 +56,8 @@ while (thisReader.Read())
  
 thisReader.Close();
 thisConnection.Close();
-```
-```VB
+````
+````VB
 'Define a new SQL connection with a connection string. 
 'The connection string will be different depending on your environment and the name of the database, table, etc.
 'See http://www.connectionstrings.com for connection string examples.
@@ -80,11 +79,11 @@ End While
  
 thisReader.Close()
 thisConnection.Close()
-```
+````
 
-###Write into SQL Database###
+### Write into SQL Database
 
-```C#
+````C#
 //Define a new SQL connection with a connection string.
 //The connection string will be different depending on your environment and the name of the database, table, etc.
 //See http://www.connectionstrings.com for connection string examples.
@@ -98,8 +97,8 @@ Log.WriteLine(thisConnection.Database);
 SqlCommand thisCommand = thisConnection.CreateCommand();
 thisCommand.CommandText = "INSERT INTO Table_1 (City) VALUES ('Richmond')";
 thisCommand.ExecuteNonQuery();
-```
-```VB
+````
+````VB
 'Define a new SQL connection with a connection string.
 'The connection string will be different depending on your environment and the name of the database, table, etc.
 'See http://www.connectionstrings.com for connection string examples.
@@ -113,7 +112,7 @@ Log.WriteLine(thisConnection.Database)
 Dim thisCommand As SqlCommand = thisConnection.CreateCommand()
 thisCommand.CommandText = "INSERT INTO Table_1 (City) VALUES ('Richmond')"
 thisCommand.ExecuteNonQuery()
-```
+````
 
 **Note**: This code won't run without modification. The database, table, and column in the original code won't exist in your environment.
 
diff --git a/docs/advanced-topics/coded-samples/general/add-message-box.md b/docs/advanced-topics/coded-samples/general/add-message-box.md
index 3dcace39..7df0b009 100644
--- a/docs/advanced-topics/coded-samples/general/add-message-box.md
+++ b/docs/advanced-topics/coded-samples/general/add-message-box.md
@@ -1,10 +1,10 @@
 ---
 title: Add MessageBox
 page_title: Add MessageBox
-description: "Add MessageBox in a Test Studio test."
+description: "Learn how to display a MessageBox in Test Studio tests using C# or VB.NET. This article explains how to add the necessary assembly reference, shows code examples for web and WPF tests, and demonstrates how to use MessageBox for debugging or displaying data-driven values."
 position: 1
 ---
-#Add a MessageBox to a Test#
+# Add a MessageBox to a Test
 
 This alert box is a pop-up that is fired at some point and displays text content.
 
@@ -14,30 +14,30 @@ The .NET Framework includes the MessageBox class which offers the intended funct
 
 This implementation is very similar to a pop-up this is fired when Test Studio executes a <a href="/features/custom-steps/manual-step" target="_blank">Manual Step</a>. The only important difference is that the MessageBox can be made to display custom text content. This might come in handy in certain situations - you can use it to perform improvised debugging.
 
-```C#
+````C#
 NativeWindow window = new NativeWindow();
 window.AssignHandle(ActiveBrowser.Window.Handle);
 MessageBox.Show(window, "This is a message!");
-```
-```VB
+````
+````VB
 Dim window As New NativeWindow()
 window.AssignHandle(ActiveBrowser.Window.Handle)
 MessageBox.Show(window, "This is a message!")
-```
+````
 
 Here's how to do it in a **WPF Test**:
 
 
-```C#
+````C#
 NativeWindow window = new NativeWindow();
 window.AssignHandle(ActiveApplication.MainWindow.Window.Handle);
 MessageBox.Show(window, "This is a message!");
-```
-```VB
+````
+````VB
 Dim window As New NativeWindow()
 window.AssignHandle(ActiveApplication.MainWindow.Window.Handle)
 MessageBox.Show(window, "This is a message!")
-```
+````
 
 
 This will pause the test and the alert box will be displayed:
@@ -45,27 +45,27 @@ This will pause the test and the alert box will be displayed:
 ![Messagebox][1]
 
 Test Execution will not continue until you click the button.
- 
+
 Ensure you add the *using* or *Imports* statement to the top of the code-behind file. Click the **View Class** button, scroll to the top of the code, and add this line:
 
-```C#
+````C#
 using System.Windows.Forms;
-```
-```VB
+````
+````VB
 Imports Windows.Forms;
-```
+````
 
 You can use the alert box to display a variety of information. Here's how to display the value of the data source for the current iteration (when using <a href="/features/data-driven-testing/Overview" target="_blank">Data Driven Testing</a>):
 
-```C#
+````C#
 NativeWindow window = new NativeWindow();
 window.AssignHandle(ActiveBrowser.Window.Handle);
 MessageBox.Show(window, Data["excelColumnName"].ToString());
-```
-```VB
+````
+````VB
 Dim window As New NativeWindow()
 window.AssignHandle(ActiveBrowser.Window.Handle)
 MessageBox.Show(window, Data("excelColumnName").ToString())
-```
+````
 
 [1]: /img/advanced-topics/coded-samples/general/add-message-box/fig1.png
diff --git a/docs/advanced-topics/coded-samples/general/attach-data-columns.md b/docs/advanced-topics/coded-samples/general/attach-data-columns.md
index b3b12817..3c06ca87 100644
--- a/docs/advanced-topics/coded-samples/general/attach-data-columns.md
+++ b/docs/advanced-topics/coded-samples/general/attach-data-columns.md
@@ -1,48 +1,47 @@
 ---
 title: Attach Data Columns
 page_title: Attach Data Columns in Code
-description: "Attach Data Columns in Code in Test Studio coded test. Data bind a value in coded test in Test Studio."
-previous_URL: /user-guide/code-samples/general/attach-columns-to-input-values-in-code.aspx
+description: "Learn how to bind data columns to input values in Test Studio coded tests. This article explains how to use the Data object to reference columns by name or index in C# and VB.NET, enabling data-driven input and verification."
 position: 1
 ---
-# Attach Columns to Input Values in Code #
+# Attach Columns to Input Values in Code 
 
 *I would like to attach a column from my data table to an input value in code. (This is more easily accomplished through the <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">Test Studio UI</a>.)*
 
-## Solution ##
+## Solution 
 
 Use the Data object in conjunction with the column name or index.
 
 In this example on Bing.com, I added the *SbFormQText* element to the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a> via the Add To Project Elements feature from the <a href="/features/elements-menu/overview" target="_blank">Elements Menu</a>. Now I can reference that element in code and data drive its input text:
 
-```C#
+````C#
 //Reference a column by name
 Pages.Bing.SbFormQText.Text = Data["Col1"].ToString();
   
 //Reference a column by index (zero based)
 Pages.Bing.SbFormQText.Text = Data[0].ToString();
-```
-```VB
+````
+````VB
 'Reference a column by name
 Pages.Bing.SbFormQText.Text = Data("Col1").ToString()
  
 'Reference a column by index (zero based)
 Pages.Bing.SbFormQText.Text = Data(0).ToString()
-```
+````
 
 This method can also be applied to a **Verification**:
 
-```C#
+````C#
 //Reference a column by name
 Assert.IsTrue(ActiveBrowser.ContainsText(Data["Col1"].ToString()));
   
 //Reference a column by index (zero based)
 Assert.IsTrue(ActiveBrowser.ContainsText(Data[0].ToString()));
-```
-```VB
+````
+````VB
 'Reference a column by name
 Assert.IsTrue(ActiveBrowser.ContainsText(Data("Col1").ToString()))
  
 'Reference a column by index (zero based)
 Assert.IsTrue(ActiveBrowser.ContainsText(Data(0).ToString()))
-```
+````
diff --git a/docs/advanced-topics/coded-samples/general/browser-specific-actions.md b/docs/advanced-topics/coded-samples/general/browser-specific-actions.md
index 30af390c..bf0b44ac 100644
--- a/docs/advanced-topics/coded-samples/general/browser-specific-actions.md
+++ b/docs/advanced-topics/coded-samples/general/browser-specific-actions.md
@@ -1,14 +1,14 @@
 ---
 title: Browser Specific Actions
 page_title: Browser Specific Actions
-description: "Invoke browser specific actions in a standard or coded step in Test Studio only if the specified browser type is the execution browser. "
+description: "Learn how to execute browser-specific actions in Test Studio tests using standard or coded steps. This article explains how to use the RunsAgainst property and provides C# and VB.NET examples for handling different browsers during automated test execution."
 position: 1
 ---
-# Invoke Browser-Specific Actions #
+# Invoke Browser-Specific Actions 
 
 *I would like to invoke browser-specific actions in a standard or coded step. This means the step is only executed if the test is running in the specified browser type.*
 
-## Solution ##
+## Solution 
 
 Use a standard (non-coded) step or use a coded solution.
 
@@ -20,7 +20,7 @@ Keep in mind that if you use this feature, the step will run against the specifi
 
 You can  put together a much more complex use-case by using a coded solution. Here's the code from the test sample. It demonstrates how to use a different search word based on browser type:
 
-```C#
+````C#
 ActiveBrowser.NavigateTo("http://www.telerik.com/"); 
 //Navigate to the page
   
@@ -46,8 +46,8 @@ Log.WriteLine("Test is executing in the following browser:" + ActiveBrowser.Brow
   
 Find.ById<HtmlInputSubmit>("~btnSearchSubmit").Click(); //Click submit button
 System.Threading.Thread.Sleep(2000); //Wait a bit so we can see the result
-```
-```VB
+````
+````VB
 ActiveBrowser.NavigateTo("http://www.telerik.com/")
 'Navigate to the page
   
@@ -75,7 +75,7 @@ Find.ById(Of HtmlInputSubmit)("~btnSearchSubmit").Click()
 'Click submit button
 System.Threading.Thread.Sleep(2000)
 'Wait a bit so we can see the result
-```
+````
 
 The coded solution is also applicable to the Telerik Testing Framework.
 
diff --git a/docs/advanced-topics/coded-samples/general/cookies.md b/docs/advanced-topics/coded-samples/general/cookies.md
index 39c0ed11..d0a4a2a8 100644
--- a/docs/advanced-topics/coded-samples/general/cookies.md
+++ b/docs/advanced-topics/coded-samples/general/cookies.md
@@ -1,14 +1,14 @@
 ---
 title: Cookies
 page_title: Get/Set Cookies in Code
-description: "Get/Set Cookies in Code in Test Studio test."
+description: "Learn how to get and set browser cookies in Test Studio coded tests using C# or VB.NET. This article provides sample code for creating, setting, retrieving, and logging cookies during automated test execution."
 position: 1
 ---
-#Get/Set Cookies in Code#
+# Get/Set Cookies in Code
 
 Here is a working code sample:
 
-```C#
+````C#
 Manager.LaunchNewBrowser();
  
 const string url = "http://www.google.com";
@@ -26,8 +26,8 @@ foreach (Cookie cookie in ActiveBrowser.Cookies.GetCookies("http://www.google.co
 {
     Log.WriteLine(cookie.Name);
 }
-```
-```VB
+````
+````VB
 Manager.LaunchNewBrowser()
  
 Const  url As String = "http://www.google.com"
@@ -44,4 +44,4 @@ Log.WriteLine(count.ToString())
 For Each cookie As Cookie In ActiveBrowser.Cookies.GetCookies("http://www.google.com")
     Log.WriteLine(cookie.Name)
 Next
-```
+````
diff --git a/docs/advanced-topics/coded-samples/general/custom-scripts-before-after.md b/docs/advanced-topics/coded-samples/general/custom-scripts-before-after.md
index 445173cf..3f474312 100644
--- a/docs/advanced-topics/coded-samples/general/custom-scripts-before-after.md
+++ b/docs/advanced-topics/coded-samples/general/custom-scripts-before-after.md
@@ -1,16 +1,16 @@
 ---
 title: Custom Scripts Before/After Test
 page_title: Custom Scripts Before/After Test
-description: "Add Custom Scripts Before/After Test execution in Test Studio. Execute certain actions before or after each test run in Test Studio."
+description: "Learn how to execute custom scripts before or after a test run in Test Studio by overriding BaseTest methods. This article explains how to use OnBeforeTestStarted and OnAfterTestCompleted for setup, cleanup, and accessing test results in both Standalone and Visual Studio plugin environments."
 position: 1
 ---
-# Execute Custom Scripts Before/After the Test Run #
+# Execute Custom Scripts Before/After the Test Run 
 
 * *I would like to invoke a custom script once the test finishes. The custom script must have access to newly-generated test results.*
 
 * *I would like to invoke a custom script just before the test starts executing.*
 
-## Solution ##
+## Solution 
 
 Override the **OnAfterTestCompleted(TestResult result)** method for the "after" script and the **OnBeforeTestStarted()** method for the "before" script. They are both members of the BaseTest class that are invoked once the test finishes or before it starts. 
 
@@ -21,7 +21,7 @@ Override the **OnAfterTestCompleted(TestResult result)** method for the "after"
  
 First, create a coded step in order to generate a code-behind file. Then open the code-behind class and add the override definition inside the BaseTest class.
 
-### Standalone version ###
+### Standalone version 
 
 1. If your test doesn't contain any coded steps, add a <a href="/features/custom-steps/script-step" target="_blank">Script Step</a> in order to generate the code-behind file.
 2. Once you add the script step, click **View Class** to make the BaseTest class visible.
@@ -32,7 +32,7 @@ First, create a coded step in order to generate a code-behind file. Then open th
 
 ![Override definition][2]
 
-### Visual Studio plugin ###
+### Visual Studio plugin 
 
 1. If your test doesn't contain any coded steps, click the <a href="/advanced-topics/coded-steps/code-behind-file" target="_blank">Add Code-Behind File button</a>.
 2. If you test contains a coded step, right click it and select **View Code** to go to the code-behind file.
@@ -41,39 +41,39 @@ First, create a coded step in order to generate a code-behind file. Then open th
 
 3. Write the override definition inside the BaseTest (but not inside another method/coded step).
 
-### The Override Definition ###
+### The Override Definition 
 
 The TestResult object lets you access the test results from the run that just finished (i.e. the one invoking the **OnAfterTestCompleted** method):
 
-```C#
+````C#
 public override void OnAfterTestCompleted(TestResult result)
 {
     string overall = Convert.ToString(result.Result);
     Log.WriteLine(overall);
     result.ExportToResultFile(@"C:\", result.TestName);
 }
-```
-```VB
+````
+````VB
 Public Overrides Sub OnAfterTestCompleted(result As TestResult)
 	Dim overall As String = Convert.ToString(result.Result)
 	Log.WriteLine(overall)
 	result.ExportToResultFile("C:\", result.TestName)
 End Sub
-```
+````
 
 The **OnBeforeTestStarted** method allows you to perform actions required for the initialization of your test (starting scripts, etc.):
 
-```C#
+````C#
 public override void OnBeforeTestStarted(BeforeTestStartedArgs args)
 {
     this.ExecuteTest("Folder1\\WebTest2.tstest");
 }
-```
-```VB
+````
+````VB
 Public Overrides Sub OnBeforeTestStarted(BeforeTestStartedArgs args)
 	Me.ExecuteTest("Folder1\WebTest2.tstest")
 End Sub
-```
+````
 
 You can use logic from assemblies in these methods. First add references to the assemblies. For Test Studio Standalone version, see the article on how to <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">Add an Assembly Reference</a>.
 
diff --git a/docs/advanced-topics/coded-samples/general/data-driven-find-expressions.md b/docs/advanced-topics/coded-samples/general/data-driven-find-expressions.md
index 838e5de9..7e1b7e84 100644
--- a/docs/advanced-topics/coded-samples/general/data-driven-find-expressions.md
+++ b/docs/advanced-topics/coded-samples/general/data-driven-find-expressions.md
@@ -1,48 +1,70 @@
 ---
-title: Data Driven Find Expressions
-page_title: Data Driven Find Expressions
-description: "Data Driven Find Expressions in Test Studio test. Select different value from a drop down for each test run. Parameterize or data drive how an element in Test Studio test is found."
-previous_url: /user-guide/code-samples/general/data-driven-find-expressions.aspx, /user-guide/code-samples/general/data-driven-find-expressions
+title: Data Driven Find Expressions in Code
+page_title: Data Driven Find Expressions in Coded Step
+description: "Learn how to parameterize element find expressions in Test Studio coded steps for data-driven testing. This article demonstrates how to use data sources to dynamically locate and interact with elements, such as selecting different values from a dropdown in each test iteration."
 position: 1
 ---
-# Data Driven Find Expressions #
+# Data Driven Find Expressions 
 
-*I would like to data drive a find expression and use it to perform an action against or verify an element.*
+*I need to data drive an element's find expression and use it to perform an action against or verify an element.*
 
-> After 2012 R2, you can create <a href="/features/elements-explorer/find-element#data-driven" target="_blank">data driven find expressions without code</a>.
+> __Tip!__ <a href="/automated-tests/elements/find-element#data-driven-find-expression" target="_blank">Data driven find expressions</a> is also available directly in elements Edit mode.
 
-## Solution ##
+## Solution 
 
-The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/combobox/index" target="_blank">Telerik demo site</a>.
+The example below uses a page from the <a href="https://demos.telerik.com/aspnet-mvc/listbox" target="_blank">Telerik UI for ASP.NET MVC demo site</a>. 
+ 
+1. Create a test and navigate to the demo page.
+2. The ListBox on the left side holds a list of names under the _Employees_ list. 
+3. Select a name and choose the button to move it on the right. 
+4. The selected name is now moved to the right under the _Developers_ list. 
+5. Do consecutive iterations for each of the names in the list on the left.
 
-1.&nbsp; Record a *Navigate* to step.
-2.&nbsp; Open the drop-down for the ComboBox.
-3.&nbsp; Locate the parent element in the DOM Explorer (see below). Here the Unordered List holds all the child List Item elements. Right click it and select **Add to Project Elements**.
+## Solution
 
-![Add to Project][1]
+1. Create a test and <a href="/getting-started/first-test#start-a-recording-session" target="_blank">record the __Navigate__ step</a>.
+   
+2. Prepare the data table - for this example I use the internal data source and it looks like this.
 
-4.&nbsp; Insert a <a href="/features/custom-steps/script-step" target="_blank">Script Step</a>.
-5.&nbsp; Here's what the Local <a href="/features/data-driven-testing/local-data-driven-test" target="_blank">Data table</a> looks like:
+    ![Data source](/img/advanced-topics/coded-samples/general/data-driven-find-expressions/data-source.png)
 
-![Data table][2]
+3. Explore the list of items and its structure using the <a href="/features/recorder/highlighting-menu/element-options#locate-in-dom" target="_blank">Advanced Recording Tools</a>.
+   
+    ![Highlight Items from list to explore](/img/advanced-topics/coded-samples/general/data-driven-find-expressions/explore-item-in-dom.png)
 
-6.&nbsp; We will use the Find.ByContent method in the coded step. More information can be found in our <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements" target="_blank">Finding Page Elements</a> article. Here's the code for our Script Step:
+4. Based on the DOM tree the items from the list are identified as `ListItems` with specific `InnerText` property and `class=k-list-item`. These element's attributes are used when <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements" target="_blank">defining the find expression for the element in code</a>. 
+   
+5. <a href="/automated-tests/coded-tests/coded-step" target="_blank">Create a coded step</a> in the test. 
+   
+6. Start with <a href="/advanced-topics/coded-samples/general/attach-data-columns" target="_blank">getting the value from the data source</a> and store into a variable. 
 
-```C#
-HtmlListItem listItem = Pages.TelerikExtensionsForASP.UnorderedList.Find.ByContent<HtmlListItem>(Data["Col1"].ToString());
-Assert.IsNotNull(listItem);
-listItem.Click();
-```
-```VB
-Dim listItem As HtmlListItem = Pages.TelerikExtensionsForASP.UnorderedList.Find.ByContent(Of HtmlListItem)(Data("Col1").ToString())
-Assert.IsNotNull(listItem)
-listItem.Click()
-```
+7. Next use the value of that variable to define the string, which needs to be used in the find expression definition. 
 
-7.&nbsp; Test Studio uses the data table to find the element in the list, performs an Assert on it, and then clicks it.
+8. Form the find expression definition and assert a matching element exists on the page. 
+   
+9.  Click the matching element. 
+
+    __Complete coded step looks like this:__ 
+
+    ```C#
+    // Get current iteration value from data source
+    var dataIterVal = Data["EmplNames"];
+            
+    // Define a string which adds the value taken from data source as inner text for the find expression
+    string defForFE = "InnerText="+dataIterVal.ToString();
+    
+    // Search for the list item element using find expression with the help of the defined string value           
+    HtmlListItem nameToSelect = Find.ByExpression<HtmlListItem>("class=k-list-item", defForFE );
+    Assert.IsNotNull(nameToSelect);
+    
+    // Click the corresponding item from list
+    nameToSelect.MouseClick(ArtOfTest.WebAii.Core.MouseClickType.LeftClick, 0, 0, ArtOfTest.Common.OffsetReference.AbsoluteCenter);
+    ```
+
+
+
+10.&nbsp; Switch back to the test steps and record the click on the button to move the selected item on the right. With this the scenario is complete. 
+
+    ![Recorded step to move the item on the right](/img/advanced-topics/coded-samples/general/data-driven-find-expressions/recorded-step-to-move-right.png)
 
-![Execute test][3]
 
-[1]: /img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig1.png
-[2]: /img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig2.png
-[3]: /img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig3.png
diff --git a/docs/advanced-topics/coded-samples/general/execution-extensions.md b/docs/advanced-topics/coded-samples/general/execution-extensions.md
index d6cb6f28..125614b7 100644
--- a/docs/advanced-topics/coded-samples/general/execution-extensions.md
+++ b/docs/advanced-topics/coded-samples/general/execution-extensions.md
@@ -1,8 +1,8 @@
 ---
 title: Execution Extensions
 page_title: Execution Extension
-description: "Test Studio has enhanced extensibility support for test execution. Integrate Test Studio better into your environment that contains custom results reporting and code defect tracking. Extend the Test Studio test execution with custom coded solutions in Execution Extension"
-previous_url: /user-guide/code-samples/general/execution-extensions.aspx, /user-guide/code-samples/general/execution-extensions
+description: "Learn how to extend and customize Test Studio’s test execution process using Execution Extensions. This article provides step-by-step guidance on building and deploying custom execution extensions in C# or VB.NET, including practical examples for custom result reporting and data source integration. It explains the IExecutionExtension interface, details each method’s purpose, and covers deployment scenarios for local, remote, and CI environments"
+
 position: 1
 ---
 # Execution Extension 
@@ -30,38 +30,38 @@ Also add the following **.NET** references (these are required for the demonstra
 3.&nbsp; Add the following using statements to the class file:
 
 	
-```C#
+````C#
 using System.IO;
 using System.Data;
 using System.Data.OleDb;
 using System.Windows.Forms;
 using ArtOfTest.WebAii.Design.Execution;
-```
-```VB
+````
+````VB
 Imports System.IO
 Imports System.Data
 Imports System.Data.OleDb
 Imports System.Windows.Forms
 Imports ArtOfTest.WebAii.Design.Execution
-```
+````
 
 4.&nbsp; The *ArtOfTest.WebAii.Design.Execution* namespace contains an IExecutionExtension that the class library needs to inherit and implement:
 
-```C#
+````C#
 namespace ClassLibrary1
 {
 	public class Class1 : IExecutionExtension
 	{
 	}
 }
-```
-```VB
+````
+````VB
 Namespace ClassLibrary1
 	Public Class Class1
 		Implements IExecutionExtension
 	End Class
 End Namespace
-```
+````
 
 5.&nbsp; Right click on **IExecutionExtension** and select **Implement Interface > Implement Interface**. This displays all the methods and notifications exposed by Test Studio. Here are definitions for each **IExecutionExtension** member:
 
@@ -70,7 +70,7 @@ End Namespace
  - The rest of the functions, which you're not using, should be left empty (remove *throw new NotImplementedException*).
 
 
-```C#
+````C#
 namespace ClassLibrary1
 {
     public class Class1 : IExecutionExtension
@@ -126,8 +126,8 @@ namespace ClassLibrary1
         #endregion
     }
 }
-```
-```VB
+````
+````VB
 Namespace ClassLibrary1
 	Public Class Class1
 		Implements IExecutionExtension
@@ -176,7 +176,7 @@ Namespace ClassLibrary1
 		#End Region
 	End Class
 End Namespace
-```
+````
 
 A few notes about the code above:
 	
@@ -191,7 +191,7 @@ A few notes about the code above:
 6.&nbsp; For the first example, we'll add code to the **OnAfterTestListCompleted** method to write the result of a test list as a basic string to a text file:
 
 	
-```C#
+````C#
 public void OnAfterTestListCompleted(RunResult result)
 {
 	string msg = string.Format("TestList '{0}' completed on '{1}'. ({2}/{3}) Passed", result.Name, result.EndTime, result.PassedCount, result.TestResults.Count);
@@ -199,15 +199,15 @@ public void OnAfterTestListCompleted(RunResult result)
 	file.WriteLine(msg);
 	file.Close();
 }
-```
-```VB
+````
+````VB
 Public Sub OnAfterTestListCompleted(result As RunResult)
 	Dim msg As String = String.Format("TestList '{0}' completed on '{1}'. ({2}/{3}) Passed", result.Name, result.EndTime, result.PassedCount, result.TestResults.Count)
 	Dim file As New StreamWriter("c:\test-list-results.txt")
 	file.WriteLine(msg)
 	file.Close()
 End Sub
-```
+````
 
 7.&nbsp; Compile the class library.
 
@@ -223,7 +223,7 @@ Let's see another example using the **OnInitializeDataSource** method. This assu
 
 1.&nbsp; Add the following code to that method:
 
-```C#
+````C#
 public System.Data.DataTable OnInitializeDataSource(ExecutionContext executionContext)
 {
     System.Data.DataTable table = null;
@@ -252,8 +252,8 @@ public System.Data.DataTable OnInitializeDataSource(ExecutionContext executionCo
     thread.Join();
     return table;
 }
-```
-```VB
+````
+````VB
 Public Function OnInitializeDataSource(executionContext As ExecutionContext) As System.Data.DataTable
 	Dim table As System.Data.DataTable = Nothing
 	Dim thread = New System.Threading.Thread(Function(obj) 
@@ -277,11 +277,11 @@ End Function)
 	thread.Join()
 	Return table
 End Function
-```
+````
 
 2.&nbsp; Now add the following *ImportExcelXLS* method within the same public class:
 
-```C#
+````C#
 private static DataSet ImportExcelXLS(string FileName, bool hasHeaders)
 {
     string HDR = hasHeaders ? "Yes" : "No";
@@ -318,8 +318,8 @@ private static DataSet ImportExcelXLS(string FileName, bool hasHeaders)
     }
     return output;
 }
-```
-```VB
+````
+````VB
 Private Shared Function ImportExcelXLS(FileName As String, hasHeaders As Boolean) As DataSet
 	Dim HDR As String = If(hasHeaders, "Yes", "No")
 	Dim strConn As String = Nothing
@@ -349,7 +349,7 @@ Private Shared Function ImportExcelXLS(FileName As String, hasHeaders As Boolean
 	End Using
 	Return output
 End Function
-```
+````
 
 3.&nbsp; Rebuild the class library, copy the resulting DLL file, and paste it into the Plugins folder (overwriting the existing file).
 
@@ -359,17 +359,17 @@ End Function
 
  - Press Cancel to use the original data source.
 
-##Remote Execution Behavior##
+## Remote Execution Behavior
 
 It was mentioned above in terms of the scope for variables, that some methods are executed only on the machine, where the scheduling server for the current remote setup is located. It is important to know how will the execution extension behave in case of different execution scenarios. For all of the listed configurations the built custom dll file needs to be copied in the **C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\** folder on each remote machine.
 
-###Scheduling Server Setup###
+### Scheduling Server Setup
 
 This feature allows only one machine to have a running <a href="/features/scheduling-test-runs/create-scheduling-server" target="_blank">scheduling server</a> and multiple machines to be connected to it and serve as <a href="/features/scheduling-test-runs/create-execution-server" target="_blank">execution clients</a>. In this case **the complete set of execution extension methods will be executed on the scheduling server machine** only.
 
 All execution machines will **not execute *OnBeforeTestListStarted()* and _OnAfterTestListCompleted()_** and will only recognize the *OnBeforeTestStarted()* and *OnAfterTestCompleted()*.
 
-###CI Setup###
+### CI Setup
 
 In the context of <a href="/advanced-topics/build-server/continious-integration-overview" target="_blank">Continuous Integration</a> setup - running test lists using the <a href="/features/test-runners/artoftest-runner" target="_blank">ArtOfTest.Runner.exe</a> with **the *list* option, will execute all methods** in the extension.
 
diff --git a/docs/advanced-topics/coded-samples/general/extend-basewebaiitest-class.md b/docs/advanced-topics/coded-samples/general/extend-basewebaiitest-class.md
index 70c2463f..d094dabb 100644
--- a/docs/advanced-topics/coded-samples/general/extend-basewebaiitest-class.md
+++ b/docs/advanced-topics/coded-samples/general/extend-basewebaiitest-class.md
@@ -1,10 +1,10 @@
 ---
 title: Extend BaseWebAiiTest Class
 page_title: Extend BaseWebAiiTest Class
-description: "How to Extend BaseWebAiiTest Class Functionality in Test Studio coded projects."
+description: "Learn how to extend the BaseWebAiiTest class in Test Studio to add shared methods and functionality across all coded tests. Step-by-step guide with C# and VB.NET examples for improved code reuse and maintainability."
 position: 1
 ---
-# How to Extend BaseWebAiiTest Class Functionality #
+# How to Extend BaseWebAiiTest Class Functionality 
 
 A possible scenario is to use same functionality in most of the tests in the project. It is possible to implement a method which will be available in each code behind test files in the project. The approach to this problem is to extend the <a href="https://docs.telerik.com/teststudioapi/html/T_ArtOfTest_WebAii_Design_BaseWebAiiTest.htm" target="_blank">BaseWebAiiTest</a> class and all test files to inherit from the new extended class.
 
@@ -14,7 +14,7 @@ Steps to implement such approach are as follows:
 
 2.&nbsp; Add a <a href="/features/coded-steps/standalone-code-file" target="_blank">stand alone class file</a> *ExtendedBaseWebAiiTest* which inherits from the abstract class *BaseWebAiiTest*. A sample implementation of such file containing the method *PrintMessage()* is given below:
 
-```C#
+````C#
 	using ArtOfTest.WebAii.Design;
 	
 	namespace ExtendBaseWebAiiTestProject
@@ -28,8 +28,8 @@ Steps to implement such approach are as follows:
         	}
     	}
 	}
-```
-```VB
+````
+````VB
 	Imports ArtOfTest.WebAii.Design
 	
 	Namespace ExtendBaseWebAiiTestProject
@@ -42,7 +42,7 @@ Steps to implement such approach are as follows:
 	        End Sub
 	    End Class
 	End Namespace
-```
+````
 
 3.&nbsp; Close the project and edit project settings file (Settings.aiis - located in the project folder) to use *ExtendedBaseWebAiiTest* as a base class to each test in the project as shown on the next screen-shot:
 
@@ -50,7 +50,7 @@ Steps to implement such approach are as follows:
 
 4.&nbsp; Re-open the project, add a WebTest and a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> inside. Then in the step it will be available the *PrintMessage()* defined in the *ExtendedBaseWebAiiTest* class. Below is given a sample of the code behind file of the WebTest.
 
-```C#
+````C#
 	using ArtOfTest.WebAii.Core;
 	using ArtOfTest.WebAii.Design.Execution;
 	
@@ -65,8 +65,8 @@ Steps to implement such approach are as follows:
 	        }
 	    }
 	}
-```
-```VB
+````
+````VB
 	Imports ArtOfTest.WebAii.Core
 	Imports ArtOfTest.WebAii.Design.Execution
 	
@@ -81,6 +81,6 @@ Steps to implement such approach are as follows:
 	        End Sub
 	    End Class
 	End Namespace
-```
+````
 
 [1]: /img/advanced-topics/coded-samples/general/extend-BaseWebAiiTest-class/fig1.png
diff --git a/docs/advanced-topics/coded-samples/general/external-log-file.md b/docs/advanced-topics/coded-samples/general/external-log-file.md
index 8906d240..d4c1df4c 100644
--- a/docs/advanced-topics/coded-samples/general/external-log-file.md
+++ b/docs/advanced-topics/coded-samples/general/external-log-file.md
@@ -1,14 +1,14 @@
 ---
 title: External Log File
 page_title: External Log File
-description: "Store the Test Studio test results to an external location."
+description: "Learn how to save Test Studio test execution logs to external files, including text and Excel formats. Step-by-step code examples show how to customize result storage for better reporting and analysis."
 position: 1
 ---
-#External Log File#
+# External Log File
 
 *I would like to save the test execution log to an external file on disk.*
 
-##Solution##
+## Solution
 
 Overwrite the *OnAfterTestCompleted* method for individual tests in order to perform logic on Test Results. See our KB article on <a href="/advanced-topics/coded-samples/general/custom-scripts-before-after" target="_blank">Executing Custom Scripts Before/After</a> your Test Run for more information.
 
@@ -24,9 +24,9 @@ We have code samples for two file types:
 
 *	<a href="#excel-file">Excel File</a>
 
-##Text File##
+## Text File
 
-```C#
+````C#
 public IList<AutomationStepResult> stepResults { get; set; }
 public override void OnAfterTestCompleted(TestResult result)
 {
@@ -45,8 +45,8 @@ public override void OnAfterTestCompleted(TestResult result)
     file.WriteLine("Total Test Result: "+ overall);
     file.Close();
 }
-```
-```VB
+````
+````VB
 Public Property stepResults() As IList(Of AutomationStepResult)
     Get
         Return m_stepResults
@@ -72,7 +72,7 @@ Public Overrides Sub OnAfterTestCompleted(result As TestResult)
     file.WriteLine("Total Test Result: " & overall)
     file.Close()
 End Sub
-```
+````
 
 Finally you'll need to <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">Add an Assembly Reference</a> for *ArtOfTest.Common.Design*. If it is already present, remove it and add it again. Add it from the \**Test Studio\Bin** directory:
 
@@ -80,13 +80,13 @@ Finally you'll need to <a href="/advanced-topics/coded-steps/add-assembly-refere
 
  
 
-##Excel File##
+## Excel File
 
 * You'll need to add a reference to *Microsoft.Office.Interop.Excel.dll*. If it isn't already on your machine, ensure you download the version from Microsoft that matches your Office suite.
 
 * You'll need to create the Excel file on disk first.
 
-```C#
+````C#
 public override void OnAfterTestCompleted(TestResult result)
 {
     string passed = Convert.ToString(result.TotalPassedSteps);
@@ -121,8 +121,8 @@ public override void OnAfterTestCompleted(TestResult result)
     GC.Collect();
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp);
 }
-```
-```VB
+````
+````VB
 Public Overrides Sub OnAfterTestCompleted(result As TestResult)
     Dim passed As String = Convert.ToString(result.TotalPassedSteps)
     Dim notRunSteps As String = Convert.ToString(result.TotalNumberOfNotRunSteps)
@@ -155,9 +155,9 @@ Public Overrides Sub OnAfterTestCompleted(result As TestResult)
     GC.Collect()
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp)
 End Sub
-```
+````
 
-##How to find and use Office PIA's without Visual Studio installed
+## How to find and use Office PIA's without Visual Studio installed
 
 1.&nbsp; Make sure that during the installation of Microsoft Office .NET Programmability Support was selected.
 
diff --git a/docs/advanced-topics/coded-samples/general/extracted-variables-in-code.md b/docs/advanced-topics/coded-samples/general/extracted-variables-in-code.md
index 82d18777..5d7f28a0 100644
--- a/docs/advanced-topics/coded-samples/general/extracted-variables-in-code.md
+++ b/docs/advanced-topics/coded-samples/general/extracted-variables-in-code.md
@@ -1,7 +1,7 @@
 ---
 title: Extracted Variables in Code
 page_title: Get/Set Extracted Variables in Code
-description: "Get/Set Extracted Variables in Code in Test Studio coded test. Extract text from page, modify it and use it again in the Test Studio test recorded steps."
+description: "Get/Set Extracted Variables in Code in Test Studio coded test. Learn how to get and set extracted variables in Test Studio coded tests. Step-by-step examples show how to capture, modify, and reuse values from UI elements in your automated test workflows."
 position: 1
 ---
 # Get/Set Extracted Variables in Code
@@ -14,25 +14,25 @@ The extracted variable can be used in a coded step as well - that way you can mo
 
 Use the *GetExtractedValue()* method to use the value of an extracted variable in a coded step:
 
-```C#
+````C#
 object myData = GetExtractedValue("ExtrVarName");
-```
-```VB
+````
+````VB
 Dim myData As Object = GetExtractedValue("ExtrVarName")
-```
+````
 
 ## Set a Value to an Extracted Variable
 
 Use the *SetExtractedValue()* method to set the value of an extraction variable so it can be used later in a standard action or verification step:
 
-```C#
+````C#
 string newValue = "newValueToAssign";
 SetExtractedValue("ExtrVarName", newValue);
-```
-```VB
+````
+````VB
 Dim newValue As String = "newValueToAssign"
 SetExtractedValue("ExtrVarName", newValue)
-```
+````
 
 ## Example of Using the Extracted Variables in Code
 
@@ -47,7 +47,7 @@ To explore the example you can download a <a href="/demoslibrary/Get-Set-Extr-Va
 
 The baseline of code to use should look similar to the one below:
 
-```C#
+````C#
 // Assign the value of the extracted variable from the recorded step 'ExtractedVar' to a variable to use in the code
 var extrVariableInCode = GetExtractedValue("ExtractedVar");
 
@@ -56,8 +56,8 @@ string newValue = "newValueToAssign";
 
 // Assign the modified variable to a new extracted variable
 SetExtractedValue("ModifiedExtrVariable", newValue);
-```
-```VB
+````
+````VB
 ' Assign the value of the extracted variable from the recorded step 'ExtractedVar' to a variable to use in the code
 Dim extrVariableInCode As Object = GetExtractedValue("ExtractedVar")
 
@@ -66,4 +66,4 @@ Dim newValue As String = "newValueToAssign"
 
 ' Assign the modified variable to a new extracted variable
 SetExtractedValue("ModifiedExtrVariable", newValue)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/fail-the-test.md b/docs/advanced-topics/coded-samples/general/fail-the-test.md
index 7e03ec6f..2817a621 100644
--- a/docs/advanced-topics/coded-samples/general/fail-the-test.md
+++ b/docs/advanced-topics/coded-samples/general/fail-the-test.md
@@ -1,20 +1,20 @@
 ---
 title: Fail the Test
 page_title: Fail the Test
-description: "How to Fail the Test on a Condition in Test Studio."
+description: "Learn how to programmatically fail a test in Test Studio using assert statements or exceptions. Includes practical C# and VB.NET examples for handling test conditions and error scenarios."
 position: 1
 ---
-# How to Fail the Test on a Condition #
+# How to Fail the Test on a Condition 
 
-There are two ways to accomplish this: *Assert* and *Throw New Exception* statements. Any unhandled exception within the coded step will fail the test step (and test) immediately.
+*There are two ways to accomplish this: **Assert** and **Throw New Exception** statements. Any unhandled exception within the coded step will fail the test step (and test) immediately.*
 
-## Assert Statements ##
+## Assert Statements 
 
 This is most easily achieved with standard (and non-coded) <a href="/features/verifications/advanced-verification" target="_blank">Verification</a> and <a href="/features/verifications/Wait" target="_blank">Wait</a> steps. You can resort to code, however, for more in-depth scenarios. See <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-asserts" target="_blank">here</a> for more information.
  
 The following code contains basic examples for demonstration purposes:
 
-```C#
+````C#
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-mvc/grid");
 HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
 Assert.IsNotNull(table);
@@ -22,8 +22,8 @@ Assert.IsNotNull(table);
 int r = table.Rows.Count;
 Assert.AreEqual(r, 10);
 Assert.IsTrue(table.InnerText.Contains("Mario"));
-```
-```VB
+````
+````VB
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-mvc/grid")
 Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
 Assert.IsNotNull(table)
@@ -31,13 +31,13 @@ Assert.IsNotNull(table)
 Dim r As Integer = table.Rows.Count
 Assert.AreEqual(r, 10)
 Assert.IsTrue(table.InnerText.Contains("Mario"))
-```
+````
 
-## Throw New Exception ##
+## Throw New Exception 
 
 When an *Assert* statement is not appropriate, you can throw your own exception. In the example below, the *FileNotFoundException* will result in failure if the specified file does not exist on disk.
 
-```C#
+````C#
 string fileName = "C:\\test.txt";
  
 if (System.IO.File.Exists(fileName) == true)
@@ -48,8 +48,8 @@ else
 {
     throw new System.IO.FileNotFoundException("File does not exist: ", fileName);
 }
-```
-```VB
+````
+````VB
 Dim fileName As String = "C:\test.txt"
  
 If System.IO.File.Exists(fileName) = True Then
@@ -57,4 +57,4 @@ If System.IO.File.Exists(fileName) = True Then
 Else
     Throw New System.IO.FileNotFoundException("File does not exist: ", fileName)
 End If
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/framework-in-console-app.md b/docs/advanced-topics/coded-samples/general/framework-in-console-app.md
index 6898472a..4e67e44d 100644
--- a/docs/advanced-topics/coded-samples/general/framework-in-console-app.md
+++ b/docs/advanced-topics/coded-samples/general/framework-in-console-app.md
@@ -3,12 +3,13 @@ title: Framework in Console App
 page_title: Framework in Console App
 description: "Test Studio - create a console application that performs UI automation tasks by using the Telerik Testing Framework."
 position: 1
+publish: false
 ---
-#Create a Console Application that Utilizes the Telerik Testing Framework#
+# Create a Console Application that Utilizes the Telerik Testing Framework
 
 *I would like to create a console application that performs UI automation tasks by using the Telerik Testing Framework. This application can run without the use of a test runner. It cannot be considered a real "test," but an application that utilizes a specific API.*
 
-##Solution##
+## Solution
 
 **Note**: At a minimum, the Telerik Testing Framework or Run-Time Edition must be installed on the machine where you intend to run the test.
 
@@ -23,13 +24,6 @@ In order to access the Telerik Testing Framework API, add the necessary assembly
 	* Telerik.Webaii.Controls.Html
 	* ArtOfTest.Webaii.Design
 
-
-* Silverlight
-
-	* Telerik.Webaii.Xaml
-	* ArtOfTest.Webaii
-	* ArtOfTest.Webaii.Design
-
 * WPF
 
 	* Telerik.Webaii.Xaml.WPF
@@ -51,7 +45,7 @@ Once you've added the assembly references, change the .NET Framework version of
 
 The application gets values from *Yahoo! Finance* and outputs them to the console screen. Here's the sole class that holds the logic for the application:
 
-```C#
+````C#
 class Program
     {
         //The URL to navigate to
@@ -91,8 +85,8 @@ class Program
             Console.Read();
         }
     }
-```
-```VB
+````
+````VB
  Class Program
         'The URL to navigate to
         Shared ReadOnly url As String = "http://finance.yahoo.com/"
@@ -131,4 +125,4 @@ class Program
             Console.Read()
         End Sub
     End Class
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/generate-random-number.md b/docs/advanced-topics/coded-samples/general/generate-random-number.md
index cccd6a57..5941dee0 100644
--- a/docs/advanced-topics/coded-samples/general/generate-random-number.md
+++ b/docs/advanced-topics/coded-samples/general/generate-random-number.md
@@ -1,21 +1,20 @@
 ---
 title: Generate Random Number
 page_title: Generate Random Number
-description: "Generate Random Number in Test Studio coded test."
-previous_url: /user-guide/code-samples/general/random-number-input.aspx, /user-guide/code-samples/general/random-number-input
+description: "Learn how to generate random numbers in Test Studio coded tests using the .NET System.Random class. Includes practical examples for input controls and automated test scenarios."
 position: 1
 ---
-#Generate Random Number#
+# Generate Random Number
 
 *I would like to generate a random number in Test Studio. This number will be used in an input control or for a similar purpose.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The .NET Framework provides the <a href="http://msdn.microsoft.com/en-us/library/system.random.aspx" target="_blank">System.Random</a> class which can be used to generate random numbers.
 
 In this example, we'll navigate to <a href="http://demos.telerik.com/aspnet-ajax/listview/examples/paging/pagingwithraddatapager/defaultcs.aspx" target="_blank">this Telerik demo page</a> and use the DataPager control to navigate to a random page number between 1 and 10.
 
-```C#
+````C#
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/datapager/examples/firstlook/defaultcs.aspx");
              
 System.Random random = new  System.Random();
@@ -23,8 +22,8 @@ int randomPage = random.Next(1, 11);
              
 Find.ByExpression<HtmlInputText>("id=~TextBox_text").Text = randomPage.ToString();
 Find.ByExpression<HtmlInputControl>("id=~GoToPageButton").Click();
-```
-```VB
+````
+````VB
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/datapager/examples/firstlook/defaultcs.aspx")
  
 Dim random As New System.Random()
@@ -32,4 +31,4 @@ Dim randomPage As Integer = random.[Next](1, 11)
  
 Find.ByExpression(Of HtmlInputText)("id=~TextBox_text").Text = randomPage.ToString()
 Find.ByExpression(Of HtmlInputControl)("id=~GoToPageButton").Click()
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/generate-random-text.md b/docs/advanced-topics/coded-samples/general/generate-random-text.md
index d104009c..ad6e8db5 100644
--- a/docs/advanced-topics/coded-samples/general/generate-random-text.md
+++ b/docs/advanced-topics/coded-samples/general/generate-random-text.md
@@ -1,29 +1,28 @@
 ---
 title: Generate Random Text
 page_title: Generate Random Text
-description: "Generate Random Text in Test Studio coded test. Progress Telerik Testing Framework generate random text and enter it in search box."
-previous_url: /user-guide/code-samples/general/generate-random-text.aspx, /user-guide/code-samples/general/generate-random-text
+description: "Learn how to generate random text in Test Studio coded tests using .NET’s System.Random class. Includes step-by-step examples for creating random strings and automating input scenarios."
 position: 1
 ---
-#Generate Random Text#
+# Generate Random Text
 
-I would like to generate random text in Test Studio. This text will be used in an input control or for a similar purpose.
+*I would like to generate random text in Test Studio. This text will be used in an input control or for a similar purpose.*
 
-##Solution##
+## Solution
 
 There are two possible approaches: with or without code.
 
-##Without code##
+## Without code
 
 See our article on the <a href="/features/verifications/Extraction" target="_blank">Extraction</a> feature.
 
-##With code##
+## With code
 
 The .NET Framework provides the <a href="http://msdn.microsoft.com/en-us/library/system.random.aspx" target="_blank">System.Random</a> class which can be used to generate random text.
 
 In this example, we'll navigate to Bing.com and enter random text into the search box.
 
-```C#
+````C#
 ActiveBrowser.NavigateTo("http://www.bing.com");
  
 //Define the length of the text
@@ -36,8 +35,8 @@ string randomText = new String(Enumerable.Repeat(charSet, length).Select(set =>
  
 Find.ById<HtmlInputSearch>("sb_form_q").Text = randomText;
 Find.ById<HtmlInputSubmit>("sb_form_go").Click();
-```
-```VB
+````
+````VB
 ActiveBrowser.NavigateTo("http://www.bing.com")
  
 'Define the length of the text
@@ -50,6 +49,6 @@ Dim randomText As String = New [String](Enumerable.Repeat(charSet, length).[Sele
  
 Find.ById(Of HtmlInputSearch)("sb_form_q").Text = randomText
 Find.ById(Of HtmlInputSubmit)("sb_form_go").Click()
-```
+````
 
 __See also:__ Check our blog post <a href="https://www.telerik.com/blogs/how-can-i-input-random-data-into-my-test-run" target="_blank">**How to input random data in your test**</a>.
diff --git a/docs/advanced-topics/coded-samples/general/get-project-path.md b/docs/advanced-topics/coded-samples/general/get-project-path.md
index 5f3ccba9..5c7bf09c 100644
--- a/docs/advanced-topics/coded-samples/general/get-project-path.md
+++ b/docs/advanced-topics/coded-samples/general/get-project-path.md
@@ -1,23 +1,23 @@
 ---
 title: Get Project Path
 page_title: Get Project Path
-description: "Get Project root Path in Test Studio coded test."
+description: "Learn how to retrieve the current Test Studio project path in coded tests. Includes code examples for accessing the project directory and data source file locations for flexible test automation."
 position: 1
 ---
-#Get Current Test Project Path#
+# Get Current Test Project Path
 
 *I would like to get the path (in the context of the file system) to which the current test project belongs.*
 
-##Solution##
+## Solution
 
 This is doable with a coded solution. Create a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> inside of a test:
 
-```C#
+````C#
 this.ExecutionContext.DeploymentDirectory;
-```
-```VB
+````
+````VB
 Me.ExecutionContext.DeploymentDirectory
-```
+````
 
 ![Current path][1]
 
@@ -31,12 +31,12 @@ However, when running tests from the Visual Studio <a href="/getting-started/tes
 
 You might also want to get the path of the data source files attached to your test project. When a project contains a data source, it's stored in **Project Folder\Data**. For instance, your test might be data bound to an Excel file by the name of **excelSample.xlsx**. This file will be stored under **Project Folder\Data\excelSample.xlsx**. Here's how to get this path in code:
 
-```C#
+````C#
 string dataSourcePath = this.ExecutionContext.DeploymentDirectory + @"\Data\excelSample.xlsx";
-```
-```VB
+````
+````VB
 Dim dataSourcePath As String = Me.ExecutionContext.DeploymentDirectory + "\Data\excelSample.xlsx"
-```
+````
 
 It's still possible to edit or replace it from that location in a coded step. This will work even if the test is data bound to the file in question. 
 
diff --git a/docs/advanced-topics/coded-samples/general/grayed-out-controls.md b/docs/advanced-topics/coded-samples/general/grayed-out-controls.md
index 3ef5ba24..5e3e8227 100644
--- a/docs/advanced-topics/coded-samples/general/grayed-out-controls.md
+++ b/docs/advanced-topics/coded-samples/general/grayed-out-controls.md
@@ -1,14 +1,14 @@
 ---
 title: Grayed Out Controls
 page_title: Grayed Out Controls
-description: "Dealing with Grayed Out Controls in Test Studio."
+description: "Learn how to handle grayed out or disabled controls in Test Studio automated tests. Find solutions for waiting out loading screens and ensuring reliable UI automation when elements are temporarily unavailable."
 position: 1
 ---
-#Dealing with Grayed Out Controls#
+# Dealing with Grayed Out Controls
 
 *My application contains "grayed out" (i.e. visible but not functioning) controls, like buttons. These controls cause unpredictable behavior when performing UI automation.*
 
-##Solution##
+## Solution
 
 The crux of the matter is that Test Studio cannot recognize whether a control is, in fact, grayed out and thus unavailable. "Grayed out" it used somewhat figuratively in this context - there are a lot of ways to signify that an element is not currently available to the user. Usually it's a gray transparent screen that covers the background or an AJAX loading animation. This is a typical implementation for modal dialogs, but also for AJAX loading screens and others.
 
@@ -30,7 +30,7 @@ Determine which DOM element represents the loading screen and then wait for this
 
 If you're using the Telerik Testing Framework, this is harder to implement. This is because you will need to manually determine which element represents the AJAX loading screen. In the demo app, this is a DIV element with an ID of RadAjaxLoadingPanel1Panel1. Once you've determined that, you can write the test that waits for it to not exist. Here's the code that triggers the AJAX loading screen and then waits for it to not exist:
 
-```C#
+````C#
 // Launch a browser instance
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer);
  
@@ -44,8 +44,8 @@ Find.ById<HtmlInputButton>("Button1").Click();
 Find.ById("RadAjaxLoadingPanel1Panel1").Wait.ForExistsNot(10000);
  
 //Now we're free to click around the page without worrying whether the click will actually occur
-```
-```VB
+````
+````VB
 ' Launch a browser instance
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer)
  
@@ -59,6 +59,6 @@ Find.ById(Of HtmlInputButton)("Button1").Click()
 Find.ById("RadAjaxLoadingPanel1Panel1").Wait.ForExistsNot(10000)
  
 'Now we're free to click around the page without worrying whether the click will actually occur
-```
+````
 
 [1]: /img/advanced-topics/coded-samples/general/grayed-out-controls/fig1.png
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/invoke-application.md b/docs/advanced-topics/coded-samples/general/invoke-application.md
index 0e7ad3ed..8fda7e7a 100644
--- a/docs/advanced-topics/coded-samples/general/invoke-application.md
+++ b/docs/advanced-topics/coded-samples/general/invoke-application.md
@@ -1,29 +1,29 @@
 ---
 title: Invoke Application
 page_title: How to Invoke an Application
-description: "How to Invoke an Application from a test step in Test Studio."
+description: "Learn how to launch desktop applications or batch files from Test Studio coded steps. Includes code examples for invoking executables with arguments and tips for custom automation scenarios."
 position: 1
 ---
-#How to Invoke an Application#
+# How to Invoke an Application
 
-I want to invoke a desktop application (i.e. an .exe file) from a test step.
+_I want to invoke a desktop application (i.e. an .exe file) from a test step._
 
-##Solution##
+## Solution
 
 You can write your own code in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> that triggers the application you need. Here's a simple example taken from <a href="http://www.csharp-station.com/HowTo/ProcessStart.aspx" target="_blank">this article</a>:
 
-```C#
+````C#
 System.Diagnostics.Process notePad = new System.Diagnostics.Process();
 notePad.StartInfo.FileName   = "notepad.exe";
 notePad.StartInfo.Arguments = @"c:\myText.txt";
 notePad.Start();
-```
-```VB
+````
+````VB
 Dim notePad As New System.Diagnostics.Process()
 notePad.StartInfo.FileName = "notepad.exe"
 notePad.StartInfo.Arguments = "c:\myText.txt"
 notePad.Start()
-```
+````
 
 * In the above sample, **C:\myText.txt** is the argument fed to **notepad.exe**. If you want to test this sample code, you'll need to create this file on your local disk first. Otherwise, the notepad application will throw a *file can't be found* error.
 
diff --git a/docs/advanced-topics/coded-samples/general/invoke-web-service-call.md b/docs/advanced-topics/coded-samples/general/invoke-web-service-call.md
deleted file mode 100644
index f062e197..00000000
--- a/docs/advanced-topics/coded-samples/general/invoke-web-service-call.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Invoke Web Service Call
-page_title: Invoke a Web Service Call
-description: "Invoke a Web Service Call from a coded step in Test Studio."
-previous_url: /user-guide/code-samples/general/invoke-web-service-call.aspx
-position: 1
----
-#Invoke a Web Service Call#
-
-*I would like to invoke a web service call from a coded step in Test Studio and verify its response.*
-
-##Solution##
-
-Below you will find a code sample which demonstrates one possible solution for this automation challenge. This sample requires that you add references to the following assemblies:
-
-* System.Net
-
-* System.IO
-
-* System.Xml
-
-See this <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">article</a>. which explains how to add an assembly reference in Test Studio (Standalone version).
-
-```C#
-// Create the WebRequest object we'll use for sending the request
-WebRequest request = WebRequest.Create("http://money.service.msn.com/StockQuotes.aspx?v=1&symbols=$INDU,AAPL,NFLX");
-request.Method = "GET";
-  
-// Send the request and read the response
-using (WebResponse response = request.GetResponse())
-{
-    // Verify the status code is OK
-    Assert.AreEqual<string>("OK", ((HttpWebResponse)response).StatusDescription);
-    // Get the stream containing content returned by the server.
-    using (Stream responseStream = response.GetResponseStream())
-    {
-        // Parse the response into an XML document and validate we got the data expected
-        // It should look like this:
-  
-        // <?xml version="1.0" ?>
-        // <quotesdata>
-        // <ticker symbol="$INDU" ... </quotesdata>
-  
-        XmlDocument doc = new XmlDocument();
-        doc.Load(responseStream);
-        Assert.AreEqual<int>(2, doc.ChildNodes.Count);
-        Assert.AreEqual<int>(3, doc.ChildNodes[1].ChildNodes.Count);
-        XmlNode aapl = doc.SelectSingleNode("/quotesdata/ticker[@symbol=\"AAPL\"]");
-        XmlNode nflx = doc.SelectSingleNode("/quotesdata/ticker[@symbol=\"NFLX\"]");
-        XmlNode indu = doc.SelectSingleNode("/quotesdata/ticker[@symbol=\"$INDU\"]");
-        Assert.IsNotNull(aapl);
-        Assert.IsNotNull(nflx);
-        Assert.IsNotNull(indu);
-    }
-}
-```
-```VB
-' Create the WebRequest object we'll use for sending the request
-Dim request As WebRequest = WebRequest.Create("http://money.service.msn.com/StockQuotes.aspx?v=1&symbols=$INDU,AAPL,NFLX")
-request.Method = "GET"
- 
-' Send the request and read the response
-Using response As WebResponse = request.GetResponse()
-    ' Verify the status code is OK
-    Assert.AreEqual(Of String)("OK", DirectCast(response, HttpWebResponse).StatusDescription)
-    ' Get the stream containing content returned by the server.
-    Using responseStream As Stream = response.GetResponseStream()
-        ' Parse the response into an XML document and validate we got the data expected
-        ' It should look like this:
- 
-        ' <?xml version="1.0" ?>
-        ' <quotesdata>
-        ' <ticker symbol="$INDU" ... </quotesdata>
- 
-        Dim doc As New XmlDocument()
-        doc.Load(responseStream)
-        Assert.AreEqual(Of Integer)(2, doc.ChildNodes.Count)
-        Assert.AreEqual(Of Integer)(3, doc.ChildNodes(1).ChildNodes.Count)
-        Dim aapl As XmlNode = doc.SelectSingleNode("/quotesdata/ticker[@symbol=""AAPL""]")
-        Dim nflx As XmlNode = doc.SelectSingleNode("/quotesdata/ticker[@symbol=""NFLX""]")
-        Dim indu As XmlNode = doc.SelectSingleNode("/quotesdata/ticker[@symbol=""$INDU""]")
-        Assert.IsNotNull(aapl)
-        Assert.IsNotNull(nflx)
-        Assert.IsNotNull(indu)
-    End Using
-End Using
-```
diff --git a/docs/advanced-topics/coded-samples/general/load-testing-extensions.md b/docs/advanced-topics/coded-samples/general/load-testing-extensions.md
deleted file mode 100644
index b657a784..00000000
--- a/docs/advanced-topics/coded-samples/general/load-testing-extensions.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Load Testing Extensions
-page_title: Load Testing Extensions
-description: "Load Testing Extensions in Test Studio."
-position: 1
-publish: false
----
-#Load Testing Extensions#
-
-A load testing plugin is similar to other <a href="/advanced-topics/coded-samples/general/execution-extensions" target="_blank">execution extensions</a>, but implements a different set of interfaces. Instead of a class that implements the IExecutionExtension interface, implement one or more of the following interfaces:
-
-* **ILoadAgentPlugin**
-
-* **ILoadAgentPluginHttpRequest**
-
-* **ILoadAgentPluginVirtualUser**
-
-Each of these has its own set of functions that extend load testing functionality. For example: 
-
-The below code creates a new, randomly-named file every time Test Studio creates a new Virtual User during load testing The code overrides all the extensible load functions, but only gives **VirtualUserAllocated** an implementation. The rest of the functions do nothing, and the exceptions they throw are benign. This class requires an assembly reference to *Telerik.TestStudio.Load.Common.dll*.
-
-```C#
-using System;
-using System.Collections.Generic;
-using System.Linq;
-using System.Text;
- 
- 
-using System.IO;
-using System.Data;
-using System.Data.OleDb;
-using System.Windows.Forms;
-using ArtOfTest.WebAii.Design.Execution;
-using Telerik.TestStudio.Load.Interfaces.Load.API;
- 
-namespace ClassLibrary1
-{
-    public class Class1 : ILoadAgentPlugin, ILoadAgentPluginHttpRequest, ILoadAgentPluginVirtualUser
-    {
- 
-        public void VirtualUserAllocated(Guid userProfileId, Guid virtualUserId)
-        {
-            Random random = new Random();
-            int randomNumber = random.Next(0, 5000);
- 
-            File.Create("c:\\test\\" + randomNumber.ToString());
-        }
- 
-        public void VirtualUserDeallocated(Guid userProfileId, Guid virtualUserId)
-        {
-            // Your custom implementation here
-        }
- 
-        public void AfterResponseReceived(Guid virtualUserId, int currentStepIndex, System.Net.HttpWebResponse response)
-        {
-            // Your custom implementation here
-        }
- 
-        public void BeforeRequestSent(Guid virtualUserId, int currentStepIndex, System.Net.HttpWebRequest request)
-        {
-            // Your custom implementation here
-        }
- 
-        public string OverrideOutgoingUrl(Guid virtualUserId, int currentStepIndex, string url)
-        {
-            // Your custom implementation here
-        }
- 
-        public void UserProfileAllocated(Guid profileRunID, string profileFriendlyName)
-        {
-            // Your custom implementation here
-        }
-    }
-}
-```
diff --git a/docs/advanced-topics/coded-samples/general/log-clipboard-text.md b/docs/advanced-topics/coded-samples/general/log-clipboard-text.md
index 88447120..f3d887ba 100644
--- a/docs/advanced-topics/coded-samples/general/log-clipboard-text.md
+++ b/docs/advanced-topics/coded-samples/general/log-clipboard-text.md
@@ -1,14 +1,14 @@
 ---
 title: Log Clipboard Text
 page_title: Log Clipboard Text
-description: "Log copied text from the Clipboard and output it during test execution in Test Studio."
+description: "Learn how to log and output clipboard text during Test Studio test execution. Step-by-step code examples show how to access and display clipboard content in automated tests."
 position: 1
 ---
-#Log Clipboard Text#
+# Log Clipboard Text
 
 *My test copies text into the Clipboard and I would like to log its content.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution:
 
@@ -17,7 +17,7 @@ This is possible with a coded solution:
  
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the Dynamic Pages Reference region:
 
-```C#
+````C#
 using System.Windows.Forms;
 using System.Threading;
  
@@ -49,8 +49,8 @@ namespace TestProject8
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports System.Windows.Forms
 Imports System.Threading
  
@@ -78,4 +78,4 @@ Namespace TestProject8
         End Sub
     End Class
 End Namespace
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/log-error-dialogs.md b/docs/advanced-topics/coded-samples/general/log-error-dialogs.md
index 9ee810ab..aba89780 100644
--- a/docs/advanced-topics/coded-samples/general/log-error-dialogs.md
+++ b/docs/advanced-topics/coded-samples/general/log-error-dialogs.md
@@ -1,16 +1,16 @@
 ---
 title: Log Error Dialogs
 page_title: Log Error Dialogs
-description: "Log Random appearing Error Dialogs and automatically handle these during a Test Studio test run."
+description: "Learn how to automatically capture and log random error dialogs during Test Studio test runs. Includes code examples for handling and recording dialog messages that appear unpredictably."
 position: 1
 ---
-#Log Error Dialogs#
+# Log Error Dialogs
 
-*My application can potentially display a dialog containing an error message during test execution. The dialog can appear multiple times and will not always appear at the same point in the test, therefore I cannot use a standard Dialog Handler step.
+*My application can potentially display a dialog containing an error message during test execution. The dialog can appear multiple times and will not always appear at the same point in the test, therefore I cannot use a standard Dialog Handler step.*
 
 I want to capture these error messages and automatically handle these dialogs if they appear.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The stipulation is that the dialog is displayed the same way and has the same title in each browser:
 
@@ -24,7 +24,7 @@ This is possible with a coded solution. The stipulation is that the dialog is di
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the Dynamic Pages Reference region:
 
-```C#
+````C#
 using System.Threading;
 using System.Windows.Forms;
 using ArtOfTest.WebAii.Win32.Dialogs;
@@ -67,8 +67,8 @@ namespace TestProject7
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports System.Threading
 Imports System.Windows.Forms
 Imports ArtOfTest.WebAii.Win32.Dialogs
@@ -106,6 +106,6 @@ Namespace TestProject7
         End Sub
     End Class
 End Namespace
-```
+````
 
 [1]: /img/advanced-topics/coded-samples/general/log-error-dialogs/fig1.png
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/mouse-wheel-scroll.md b/docs/advanced-topics/coded-samples/general/mouse-wheel-scroll.md
index 4a98fbbe..8e01917f 100644
--- a/docs/advanced-topics/coded-samples/general/mouse-wheel-scroll.md
+++ b/docs/advanced-topics/coded-samples/general/mouse-wheel-scroll.md
@@ -3,18 +3,19 @@ title: Mouse Wheel Scroll
 page_title: Mouse Wheel Scroll
 description: "Invoke desktop mouse scroll actions in Test Studio test run."
 position: 1
+publish: false
 ---
-#Mouse Wheel Scroll#
+# Mouse Wheel Scroll
 
 *I need to invoke desktop mouse scroll actions on an HTML element (typically a scroll bar).*
 
-##Solution##
+## Solution
 
 This is doable with a coded solution. The code is desktop-based, which means it is not associated with an element in your Test Project. Because of this you will need to make sure that the intended target element has focus within the browser before the attempted mouse scroll action. Typically you can give an element focus by invoking a mouse click on it (via regular, non-coded step). Here's an example:
 
-```C#
+````C#
 Manager.Desktop.Mouse.TurnWheel(100, MouseWheelTurnDirection.Backward);
-```
-```VB
+````
+````VB
 Manager.Desktop.Mouse.TurnWheel(100, MouseWheelTurnDirection.Backward)
-```
+````
diff --git a/docs/advanced-topics/coded-samples/general/non-iterative-data-driving.md b/docs/advanced-topics/coded-samples/general/non-iterative-data-driving.md
index 37a475bd..a07e7c04 100644
--- a/docs/advanced-topics/coded-samples/general/non-iterative-data-driving.md
+++ b/docs/advanced-topics/coded-samples/general/non-iterative-data-driving.md
@@ -1,15 +1,14 @@
 ---
 title: Non-iterative Data Driving
 page_title: Non-iterative Data Driving
-description: "Test Studio - data drive a step in a test script to select a different sequential row from the data source by each test run. Non-iterative Data Driving in Test Studio"
-previous_url: /user-guide/code-samples/general/non-iterative-data-driven-testing.aspx, /user-guide/code-samples/general/non-iterative-data-driven-testing
+description: "Learn how to implement non-iterative data driving in Test Studio by selecting a different data row on each test run. Step-by-step guide with code samples for managing row selection using XML and Excel."
 position: 1
 ---
-#Non-iterative Data Driving#
+# Non-iterative Data Driving
 
 *Is there a way to data drive a step in a test script so that each time the script is run, the test step will select a different sequential row from the data source?*
 
-##Solution##
+## Solution
 
 The solution is to save the number of the row into an XML file. Each time you execute the test, read the number of the row from the XML file and tell Test Studio to use this row from your data source.
 
@@ -21,12 +20,12 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 1.3 Write the following code into the file:
 
-```XML
+````XML
 	<?xmlversion="1.0" encoding="UTF-8"?>
 		<IterationValue> 
 		<numVal>0</numVal>
 	</IterationValue>
-```
+````
 
 2.&nbsp; Create your data source, if you don't have one already. In my case this is an Excel file called "foo.xlsx" containing numbers from 1 to 20.
 
@@ -47,7 +46,7 @@ The solution is to save the number of the row into an XML file. Each time you ex
 
 3.5 Create a method which will save the row number into the XML file:
 
-```C#
+````C#
 public void SaveValue(int numVal)
 {
     string path = @"C:\Box\NextRowOnEachRun\IterationValue.xml";
@@ -55,19 +54,19 @@ public void SaveValue(int numVal)
     e.Add(new XElement("numVal", numVal));
     e.Save(path);
 }
-```
-```VB
+````
+````VB
 Public Sub SaveValue(numVal As Integer)
 	Dim path As String = "C:\Box\NextRowOnEachRun\IterationValue.xml"
 	Dim e As New XElement("IterationValue")
 	e.Add(New XElement("numVal", numVal))
 	e.Save(path)
 End Sub
-```
+````
 
 3.6 Create a method which will load the row number from the XML file:
 
-```C#
+````C#
 public int LoadValue()
 {
     string path = @"C:\Box\NextRowOnEachRun\IterationValue.xml";
@@ -77,8 +76,8 @@ public int LoadValue()
 
     return numVal;
 }
-```
-```VB
+````
+````VB
 Public Function LoadValue() As Integer
 	Dim path As String = "C:\Box\NextRowOnEachRun\IterationValue.xml"
 	Dim e As XElement = XElement.Load(path)
@@ -87,11 +86,11 @@ Public Function LoadValue() As Integer
 
 	Return numVal
 End Function
-```
+````
 
 3.7 Create a method which will read the row from the Excel file:
 
-```C#
+````C#
 public string ReadingExcel()
 {
 	int rowValue = LoadValue();
@@ -113,8 +112,8 @@ public string ReadingExcel()
 
 	return value;
 }
-```
-```VB
+````
+````VB
 Public Function ReadingExcel() As String
 	Dim rowValue As Integer = LoadValue()
 	Dim input As String = "C:\Box\NextRowOnEachRun\foo.xlsx"
@@ -136,11 +135,11 @@ Public Function ReadingExcel() As String
 
 	Return value
 End Function
-```
+````
 
 See <a href="http://screencast.com/t/bqt6zXOj" target="_blank">this video</a> to see how this sample works.
 
-##How to find and use Office PIA's without Visual Studio installed
+## How to find and use Office PIA's without Visual Studio installed
 
 1.&nbsp; Make sure that during the installation of Microsoft Office .NET Programmability Support was selected.
 
diff --git a/docs/advanced-topics/coded-samples/general/open-and-read-pdf-file-wpf-desktop.md b/docs/advanced-topics/coded-samples/general/open-and-read-pdf-file-wpf-desktop.md
index b8c99258..c1c90999 100644
--- a/docs/advanced-topics/coded-samples/general/open-and-read-pdf-file-wpf-desktop.md
+++ b/docs/advanced-topics/coded-samples/general/open-and-read-pdf-file-wpf-desktop.md
@@ -1,9 +1,9 @@
 ---
 title: Read Saved PDF File - WPF and Desktop Tests
 page_title: Read Saved PDF File - WPF and Desktop Tests
-description: "Open a saved locally PDF file in Test Studio WPF and Desktop Tests and read its content. The tested application creates a PDF file and let's you save it locally on the hard disc. How to open that PDF file and read its content from WPF or Desktop test?"
+description: "Learn how to open and read the contents of a saved PDF file in Test Studio WPF and Desktop tests using iTextSharp. Step-by-step guide with code examples for validating PDF content in automated scenarios."
 position: 1
-publish: true
+published: true
 ---
 # Read Saved PDF File 
 
@@ -23,75 +23,75 @@ The described approach using a 3rd party and open source dll is applicable for W
 
 3. <a href="/automated-tests/coded-tests/coded-step" target="_blank">Create a coded step in your test and add the following *usings*, or *Imports* for VB.Net, on top:
 
-    ```C#
-    using iTextSharp.text.pdf;
-    using iTextSharp.text.pdf.parser;
-    using System.IO;
-    ```
-    ```VB
-    Imports iTextSharp.text.pdf
-    Imports iTextSharp.text.pdf.parser
-    Imports System.IO
-    ```
+````C#
+using iTextSharp.text.pdf;
+using iTextSharp.text.pdf.parser;
+using System.IO;
+````
+````VB
+Imports iTextSharp.text.pdf
+Imports iTextSharp.text.pdf.parser
+Imports System.IO
+````
 
 4. The below snippet opens a PDF file, which is stored locally on the disc, then reads and outputs its content to the test execution log file. The sample uses <a href="https://docs.microsoft.com/en-us/dotnet/api/system.text.stringbuilder?view=netframework-4.8" target="_blank">C# StringBuidler Class</a> to append the text from the PDF file. 
 
-    ```C#
-    // Define the name of the file to open
-    string fileName = "C:\\pathToYourPDF\\PDFName.pdf";
+````C#
+// Define the name of the file to open
+string fileName = "C:\\pathToYourPDF\\PDFName.pdf";
 
-    // Define the file to store the read from PDF content
-    StringBuilder text = new StringBuilder();
+// Define the file to store the read from PDF content
+StringBuilder text = new StringBuilder();
 
-    // Verify if the PDF file exists and open it
-    if (File.Exists(fileName))
-        {
-        // Initilize the pdfReader
-        PdfReader pdfReader = new PdfReader(fileName);
-
-        // Go through the pages of the PDF file, read its content and append it
-        for (int page = 1; page <= pdfReader.NumberOfPages; page++)
-            {
-                ITextExtractionStrategy strategy = new SimpleTextExtractionStrategy();
-                string currentText = PdfTextExtractor.GetTextFromPage(pdfReader, page, strategy);
-
-                currentText = Encoding.UTF8.GetString(ASCIIEncoding.Convert(Encoding.Default, Encoding.UTF8, Encoding.Default.GetBytes(currentText)));
-                text.Append(currentText);
-            }
+// Verify if the PDF file exists and open it
+if (File.Exists(fileName))
+    {
+    // Initilize the pdfReader
+    PdfReader pdfReader = new PdfReader(fileName);
 
-        // Output the collected text in the test execution log file
-        Log.WriteLine(text.ToString());
+    // Go through the pages of the PDF file, read its content and append it
+    for (int page = 1; page <= pdfReader.NumberOfPages; page++)
+        {
+            ITextExtractionStrategy strategy = new SimpleTextExtractionStrategy();
+            string currentText = PdfTextExtractor.GetTextFromPage(pdfReader, page, strategy);
 
-        // Close the pdfReader
-        pdfReader.Close();
+            currentText = Encoding.UTF8.GetString(ASCIIEncoding.Convert(Encoding.Default, Encoding.UTF8, Encoding.Default.GetBytes(currentText)));
+            text.Append(currentText);
         }
-    ```
-    ```VB
-    ' Define the name of the file to open
-    Dim fileName AsString = "folder\\pdfFileName.pdf"
-
-    ' Define the file to store the read from PDF content
-    Dim text AsNew StringBuilder()
-
-    ' Verify if the PDF file exists and open it
-    If File.Exists(fileName)
-        Then
-            ' Initilize the pdfReader
-            Dim pdfReader AsNew PdfReader(fileName)
-
-            ' Go through the pages of the PDF file, read its content and append it
-            For page AsInteger = 1 To pdfReader.NumberOfPages
-
-                Dim strategy As ITextExtractionStrategy = New SimpleTextExtractionStrategy()
-                Dim currentText AsString = PdfTextExtractor.GetTextFromPage(pdfReader, page, strategy)
-
-                currentText = Encoding.UTF8.GetString(ASCIIEncoding.Convert(Encoding.[Default], Encoding.UTF8, Encoding.[Default].GetBytes(currentText)))
-                text.Append(currentText)
-            Next
-        ' Output the collected text in the test execution log file
-        Log.WriteLine(text.ToString())
-
-        ' Close the pdfReader
-        pdfReader.Close()
-    EndIf
-    ```
+
+    // Output the collected text in the test execution log file
+    Log.WriteLine(text.ToString());
+
+    // Close the pdfReader
+    pdfReader.Close();
+    }
+````
+````VB
+' Define the name of the file to open
+Dim fileName AsString = "folder\\pdfFileName.pdf"
+
+' Define the file to store the read from PDF content
+Dim text AsNew StringBuilder()
+
+' Verify if the PDF file exists and open it
+If File.Exists(fileName)
+    Then
+        ' Initilize the pdfReader
+        Dim pdfReader AsNew PdfReader(fileName)
+
+        ' Go through the pages of the PDF file, read its content and append it
+        For page AsInteger = 1 To pdfReader.NumberOfPages
+
+            Dim strategy As ITextExtractionStrategy = New SimpleTextExtractionStrategy()
+            Dim currentText AsString = PdfTextExtractor.GetTextFromPage(pdfReader, page, strategy)
+
+            currentText = Encoding.UTF8.GetString(ASCIIEncoding.Convert(Encoding.[Default], Encoding.UTF8, Encoding.[Default].GetBytes(currentText)))
+            text.Append(currentText)
+        Next
+    ' Output the collected text in the test execution log file
+    Log.WriteLine(text.ToString())
+
+    ' Close the pdfReader
+    pdfReader.Close()
+EndIf
+````
diff --git a/docs/advanced-topics/coded-samples/general/override-app-config.md b/docs/advanced-topics/coded-samples/general/override-app-config.md
index c6a5b9b1..e76310a4 100644
--- a/docs/advanced-topics/coded-samples/general/override-app-config.md
+++ b/docs/advanced-topics/coded-samples/general/override-app-config.md
@@ -3,12 +3,13 @@ title: Override app.config
 page_title: Override app.config
 description: "Override Test Studio app.config to get tue run-time configuration settings in Visual Studio."
 position: 1
+publish: false
 ---
-#Override the app.config File in a Test Studio Project#
+# Override the app.config File in a Test Studio Project
 
 *I would like Visual Studio to load the app.config file to get its run-time configuration settings.*
 
-##Solution##
+## Solution
 
 > The app.config only applies to projects in Visual Studio as expained <a href="http://msdn.microsoft.com/en-us/library/a65txexh.aspx" target="_blank">here</a>.
 
@@ -20,7 +21,7 @@ However, this doesn't work with a default Test Studio project. A Test Studio pro
 
 * *System.Configuration*
 
-```C#
+````C#
 Assembly me = Assembly.GetExecutingAssembly();
 Configuration config = ConfigurationManager.OpenExeConfiguration(me.ManifestModule.Assembly.Location);
   
@@ -29,8 +30,8 @@ string name = config.AppSettings.Settings["LoginName"].Value;
 string pw = config.AppSettings.Settings["Pass"].Value;
 string UserId = config.AppSettings.Settings["UserId"].Value;
 string conn = config.ConnectionStrings.ConnectionStrings["ConnectionString"].ConnectionString;
-```
-```VB
+````
+````VB
 Dim [me] As Assembly = Assembly.GetExecutingAssembly()
 Dim config As Configuration = ConfigurationManager.OpenExeConfiguration([me].ManifestModule.Assembly.Location)
  
@@ -39,4 +40,4 @@ Dim name As String = config.AppSettings.Settings("LoginName").Value
 Dim pw As String = config.AppSettings.Settings("Pass").Value
 Dim UserId As String = config.AppSettings.Settings("UserId").Value
 Dim conn As String = config.ConnectionStrings.ConnectionStrings("ConnectionString").ConnectionString
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/random-row.md b/docs/advanced-topics/coded-samples/general/random-row.md
index c138bd6c..da41ce6d 100644
--- a/docs/advanced-topics/coded-samples/general/random-row.md
+++ b/docs/advanced-topics/coded-samples/general/random-row.md
@@ -1,15 +1,14 @@
 ---
 title: Random Row
 page_title: Random Row
-description: "Data drive a Test Studio test with random row from the data source for each test run execution iteration."
-previous_url: /user-guide/code-samples/general/random-row.aspx, user-guide/code-samples/general/random-row.aspx, /user-guide/code-samples/general/random-row.aspx, user-guide/code-samples/general/random-row
+description: "Learn how to data drive Test Studio tests by selecting a random row from an Excel data source on each run. Includes step-by-step code examples for dynamic test input."
 position: 1
 ---
-#Random Row from Excel Data Source#
+# Random Row from Excel Data Source
 
 *Is there a way to data drive a step in a test script so that each time the script is run, the test step will select a random row from the Excel data source?*
 
-##Solution##
+## Solution
 
 In code, generate a random number based on the number of rows. Then use the corresponding text from that row's cell in the applicable test step.
 
@@ -22,7 +21,7 @@ In code, generate a random number based on the number of rows. Then use the corr
 
 	* **Note:** Ensure you <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">Add an Assembly Reference</a> to *Microsoft.Office.Interop.Excel*. You can download a version of that file on Microsoft's website that matches your version of MS Office.
 
-```C#
+````C#
 Random random = new Random();
 int num = random.Next(1, 6);
  
@@ -37,8 +36,8 @@ app.Quit();
 app = null;
  
 Pages.Bing.SbFormQText.Text = value;
-```
-```VB
+````
+````VB
 Dim random As New Random()
 Dim num As Integer = random.[Next](1, 6)
  
@@ -55,9 +54,9 @@ app.Quit()
 app = Nothing
  
 Pages.Bing.SbFormQText.Text = value
-```
+````
 
-##How to find and use Office PIA's without Visual Studio installed
+## How to find and use Office PIA's without Visual Studio installed
 
 1.&nbsp; Make sure that during the installation of Microsoft Office .NET Programmability Support was selected.
 
diff --git a/docs/advanced-topics/coded-samples/general/relative-dialog-path.md b/docs/advanced-topics/coded-samples/general/relative-dialog-path.md
index 5ece6f44..015d4d9c 100644
--- a/docs/advanced-topics/coded-samples/general/relative-dialog-path.md
+++ b/docs/advanced-topics/coded-samples/general/relative-dialog-path.md
@@ -1,39 +1,39 @@
 ---
 title: Relative Dialog Path
 page_title: Relative Dialog Path
-description: "Use relative paths in a Test Studio test - upload/download dialog handling."
+description: "Learn how to use relative file paths for upload and download dialogs in Test Studio coded tests. Includes code examples for building dynamic paths based on the test execution directory."
 position: 1
 ---
 
-#Use Relative Paths in File Upload/Downloads#
+# Use Relative Paths in File Upload/Downloads
 
 *I need to upload/download a file to a path relative to my test execution folder. I don't want to use an absolute file path.*
 
-##Solution##
+## Solution
 
 This can only be done in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a>. The key is to use this.ExecutionContext.DeploymentDirectory. This property identifies the folder the test is running in. You want to use it in a coded step to create an absolute path for file upload/download like this:
 
-```C#
+````C#
 public void RelativePathDownloadStep()
 {
     Directory.CreateDirectory(System.IO.Path.Combine(this.ExecutionContext.DeploymentDirectory, "download"));
     string fullPath = System.IO.Path.Combine(this.ExecutionContext.DeploymentDirectory, "download\\myfile.txt");
     Pages.ThinkbroadbandDownload.IconDownload5MBPngImage.Download(false, DownloadOption.Save, fullPath, 30000);
 }
-```
-```VB
+````
+````VB
 Public Sub RelativePathDownloadStep()
 	Directory.CreateDirectory(System.IO.Path.Combine(Me.ExecutionContext.DeploymentDirectory, "download"))
 	Dim fullPath As String = System.IO.Path.Combine(Me.ExecutionContext.DeploymentDirectory, "download\myfile.txt")
 	Pages.ThinkbroadbandDownload.IconDownload5MBPngImage.Download(False, DownloadOption.Save, fullPath, 30000)
 End Sub
-```
+````
 
 You'll have to <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">add an assembly reference</a> to *System.Windows.Forms.dll* and to include the following line at the top of your code file to use the given sample:
 
-```C#
+````C#
 using System.IO;
-```
-```VB
+````
+````VB
 Imports System.IO
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/send-keystrokes.md b/docs/advanced-topics/coded-samples/general/send-keystrokes.md
index fa1fbdd3..1278de99 100644
--- a/docs/advanced-topics/coded-samples/general/send-keystrokes.md
+++ b/docs/advanced-topics/coded-samples/general/send-keystrokes.md
@@ -1,17 +1,16 @@
 ---
 title: Send Keystrokes
 page_title: Send Keystrokes
-description: "Send key press or combination of key presses in Test Studio test run. "
-previous_url: /user-guide/code-samples/general/send-keystrokes.aspx, /user-guide/code-samples/general/send-keystrokes
+description: "Learn how to send keystrokes, type text, and perform key combinations in Test Studio coded tests. Includes C# and VB.NET examples for simulating keyboard input during automated test runs."
 position: 1
 ---
-#Send Keystrokes#
+# Send Keystrokes
 
-##Problem 1##
+## Problem 1
 
 *I want to press Enter key.*
 
-##Solution 1##
+## Solution 1
 
 This is possible with a coded solution:
 
@@ -20,7 +19,7 @@ This is possible with a coded solution:
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the *Dynamic Pages Reference* region:
 
-```C#
+````C#
 using System.Windows.Forms;
  
 namespace TestProject8
@@ -35,8 +34,8 @@ namespace TestProject8
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports System.Windows.Forms
  
 Namespace TestProject8
@@ -51,13 +50,13 @@ Namespace TestProject8
         End Sub
     End Class
 End Namespace
-```
+````
 
-##Problem 2##
+## Problem 2
 
 *I want to type text with keystrokes.*
 
-##Solution 2##
+## Solution 2
 
 This is possible with a coded solution:
 
@@ -66,7 +65,7 @@ This is possible with a coded solution:
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the *Dynamic Pages Reference* region:
 
-```C#
+````C#
 using System.Windows.Forms;
  
 namespace TestProject8
@@ -81,8 +80,8 @@ namespace TestProject8
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports System.Windows.Forms
  
 Namespace TestProject8
@@ -97,16 +96,16 @@ Namespace TestProject8
         End Sub
     End Class
 End Namespace
-```
+````
 
 
 > <a href="http://msdn.microsoft.com/en-us/library/system.windows.forms.sendkeys(v=vs.110).aspx" target="_blank">Here</a> you can find the list with key codes.
 
-##Problem 3##
+## Problem 3
 
 *I want to perform combination of key presses like Ctrl+A.*
 
-##Solution 3##
+## Solution 3
 
 This is possible with a coded solution:
 
@@ -115,7 +114,7 @@ This is possible with a coded solution:
 
 Here is the full code-behind file, excluding the standard *using/Imports* statements and the *Dynamic Pages Reference* region:
 
-```C#
+````C#
 using System.Windows.Forms;
  
 namespace TestProject8
@@ -130,8 +129,8 @@ namespace TestProject8
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports System.Windows.Forms
  
 Namespace TestProject8
@@ -146,5 +145,5 @@ Namespace TestProject8
         End Sub
     End Class
 End Namespace
-```
+````
 
diff --git a/docs/advanced-topics/coded-samples/general/skip-iteration.md b/docs/advanced-topics/coded-samples/general/skip-iteration.md
index 86773840..356a280a 100644
--- a/docs/advanced-topics/coded-samples/general/skip-iteration.md
+++ b/docs/advanced-topics/coded-samples/general/skip-iteration.md
@@ -1,14 +1,14 @@
 ---
 title: Skip Iteration
 page_title: Skip Iteration
-description: "Skip one or more iterations in a data driven Test Studio test execution."
+description: "Learn how to skip specific iterations in data-driven Test Studio tests based on custom conditions. Step-by-step guide with code examples for conditional test execution and data source inheritance."
 position: 1
 ---
-#How to Skip a Specific Iteration While Executing a Data-Bound Test#
+# How to Skip a Specific Iteration While Executing a Data-Bound Test
 
 *You're executing a data-driven test. You need to skip one or more iterations based on a specific condition.*
 
-##Solution##
+## Solution
 
 You'll need to create two tests. Let's call them **MainTest** and **Subtest**. Put the actual test steps you want to invoke (i.e. your test) in Subtest.
 
@@ -18,28 +18,28 @@ Now it's time to bind your test to a data source. Make **MainTest** (which is st
 
 After this add **Subtest** via the <a href="/features/custom-steps/test-as-step" target="_blank">Test as Step</a> feature in MainTest. However, we're going to do that in a coded step. Here's what the code looks like: 
 
-```C#
+````C#
 this.ExecuteTest("Subtest.tstest");
-```
-```VB
+````
+````VB
 Me.ExecuteTest("Subtest.tstest")
-```
+````
 
 For each iteration of **MainTest**, Test Studio will attempt to implement this code and run **SubTest**. Now we can implement conditional logic which determines whether we execute the above logic. In effect, this will control whether a given iteration executes the **SubTest**. If it doesn't, the iteration is effectively skipped - it will invoke no actions of any consequence. We'll skip the iteration even though it won't seem so from **MainTest**'s point of view (i.e. all the iterations will be listed in **MainTest**'s Log file).
  
 Let's say we want to implement a data-driven test that navigates to <a href="http://www.random.org/" target="_blank">random.org</a>, generates a random number, and executes some steps if the number is even. First we record the required steps in MainTest. A step will <a href="/advanced-topics/coded-samples/general/extracted-variables-in-code" target="_blank">Extract</a> the generated number in a variable we're going to name num. Now we check whether this value is even and execute SubTest if it is:
 
-```C#
+````C#
 if (Convert.ToInt16(this.GetExtractedValue("num")) % 2 == 0 )
 {
      this.ExecuteTest("SubTest.tstest");
 }
-```
-```VB
+````
+````VB
 If Convert.ToInt16(Me.GetExtractedValue("num")) Mod 2 = 0 Then
     Me.ExecuteTest("SubTest.tstest")
 End If
-```
+````
 
 If you want to access data from your data source, set the **SubTest** to inherit its parent's data source:
 
diff --git a/docs/advanced-topics/coded-samples/general/use-elements-from-repository-in-utility-class.md b/docs/advanced-topics/coded-samples/general/use-elements-from-repository-in-utility-class.md
index 2027f501..6f331c40 100644
--- a/docs/advanced-topics/coded-samples/general/use-elements-from-repository-in-utility-class.md
+++ b/docs/advanced-topics/coded-samples/general/use-elements-from-repository-in-utility-class.md
@@ -1,18 +1,18 @@
 ---
 title: Using Elements From Elements Repository In A Utility Class
 page_title: Using Elements From Repository In A Utility Class
-description: "Use Elements From Repository In A Utility Class in Test Studio code file."
+description: "Learn how to access and use elements from the Test Studio Elements Repository within a utility class. Includes best practices, code examples, and important considerations for standalone code files."
 position: 1
 ---
-#How to Use Elements From Repository In A Utility Class#
+# How to Use Elements From Repository In A Utility Class
 
 *I would like to use elements recorded in the <a href="/knowledge-base/project-configuration-kb/element-repository" target="_blank">Elements repository</a> in my standalone code class file.*
 
-##Solution##
+## Solution
 
 We do not recommend using elements from the repository in a <a href="/features/coded-steps/standalone-code-file" target="_blank">standalone class file</a>. If there is a specific scenario you could not avoid you could refer to the example below. You would need to add references to ***ArtOfTest.WebAii.Core.dll*** and ***ArtOfTest.WebAii.Design.dll*** and include *using* statements for these in the code file. The ***Utility class*** inherits the ***BaseWebAiiTest*** and requires definition for region ***[Dynamic Pages Reference]***.
 
-```C#
+````C#
 using ArtOfTest.WebAii.Core;
 using ArtOfTest.WebAii.Design;
 
@@ -44,8 +44,8 @@ namespace SomeTestProject
         }
     }
 }
-```
-```VB
+````
+````VB
 Imports ArtOfTest.WebAii.Core
 Imports ArtOfTest.WebAii.Design
 
@@ -73,21 +73,21 @@ Namespace SomeTestProject
 	End Class
 End Namespace
 
-```
+````
 
 In a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> you would need to create an instance of this class in order to use its methods as shown below:
 
-```C#
+````C#
 // create an instance of the class
 var MyClass = new Utility();
 
 // call a method of this class
 MyClass.DoSomething();
-```
-```VB
+````
+````VB
 // create an instance of the class
 Dim [MyClass] = New Utility()
 
 // call a method of this class
 [MyClass].DoSomething()
-```
+````
diff --git a/docs/advanced-topics/coded-samples/general/use-external-dll-in-vs.md b/docs/advanced-topics/coded-samples/general/use-external-dll-in-vs.md
index 82cababc..c5232b04 100644
--- a/docs/advanced-topics/coded-samples/general/use-external-dll-in-vs.md
+++ b/docs/advanced-topics/coded-samples/general/use-external-dll-in-vs.md
@@ -1,14 +1,14 @@
 ---
 title: Use External DLL in VS
 page_title: Use External DLL in VS
-description: "Use External DLL in the Test Studio project from the Visual Studio solution."
+description: "Learn how to reference and use external DLLs in Test Studio projects within Visual Studio. Step-by-step guidance and sample solution for integrating custom libraries and global functions."
 position: 1
 ---
-# Use External DLL in VS #
+# Use External DLL in VS 
 
 *I need to reference and use an external DLL that contains global functions from a coded step in Visual Studio.*
 
-## Solution ##
+## Solution 
 
 You'll find an attached sample Visual Studio Solution attached at bottom of the page. The solution contains two projects. One is a Test Studio project and the other is a "normal" Class Library Project. We use functions from the Class Library inside a coded step in the test project.
 
diff --git a/docs/advanced-topics/coded-samples/general/using-the-http-proxy.md b/docs/advanced-topics/coded-samples/general/using-the-http-proxy.md
index 21442001..582ad5e7 100644
--- a/docs/advanced-topics/coded-samples/general/using-the-http-proxy.md
+++ b/docs/advanced-topics/coded-samples/general/using-the-http-proxy.md
@@ -1,11 +1,10 @@
 ---
 title: Using the HTTP Proxy
 page_title: Using the HTTP Proxy
-description: "Use the HTTP Proxy in Test Studio coded tests."
-previous_url: /user-guide/code-samples/general/using_the_http_proxy.aspx, /user-guide/code-samples/general/using_the_http_proxy
+description: "Learn how to enable and use the HTTP proxy in Test Studio coded tests. Includes setup instructions and code examples for intercepting HTTP requests and responses."
 position: 1
 ---
-#Using the HTTP Proxy in Test Studio#
+# Using the HTTP Proxy in Test Studio
 
 The Telerik Testing *Framework ArtOfTest.WebAii.Messaging.Http* namespace contains classes to intercept HTTP requests and responses. However, using these classes in a Test Studio coded step and executing against browsers other than Internet Explorer, the HTTP proxy may not become enabled. To use this code in a Test Studio test, <a href="/features/project-settings/General" target="_blank">enable the HTTP proxy</a> in the Test Studio Project Settings.
 
@@ -14,10 +13,10 @@ The Telerik Testing *Framework ArtOfTest.WebAii.Messaging.Http* namespace contai
 The project setting 'Use http proxy' enables the HTTP proxy for the use of the HTTP proxy classes in Test Studio coded steps. It functions like the following line from the HTTP Proxy code sample, which is only necessary in Telerik Testing Framework tests:
 
 
-```C#
+````C#
 // Override the settings you want. For example:
 settings.Web.UseHttpProxy = true;
-```
+````
 
 
 [1]: /img/advanced-topics/coded-samples/general/using-the-http-proxy/fig1.png
diff --git a/docs/advanced-topics/coded-samples/general/utility-class-in-standalone.md b/docs/advanced-topics/coded-samples/general/utility-class-in-standalone.md
index 162ec93b..cda03660 100644
--- a/docs/advanced-topics/coded-samples/general/utility-class-in-standalone.md
+++ b/docs/advanced-topics/coded-samples/general/utility-class-in-standalone.md
@@ -1,21 +1,21 @@
 ---
 title: Utility Class In Test Studio Standalone
 page_title: Utility Class In Test Studio Standalone
-description: "Utility Class Helper class file In Test Studio Standalone project"
-previous_url: /user-guide/code-samples/general/utility-in-standalone.aspx, /user-guide/code-samples/general/utility-in-standalone
+description: "Learn how to create and use a utility class in Test Studio Standalone projects for global variables and reusable functions. Includes code examples for file operations and element actions."
+
 position: 1
 ---
-# How To Use A Utility Class In Test Studio Standalone Version #
+# How To Use A Utility Class In Test Studio Standalone Version 
 
-## Problem ##
+## Problem 
 
 *I would like to create/use global variables and/or functions in Test Studio Standalone version and access these from all tests within the current project.*
 
-## Solution ##
+## Solution 
 
 <a href="/features/coded-steps/standalone-code-file" target="_blank">Here</a> you could read how to create a standalone code file within a Test Studio project. Below are listed two examples how a class file named *Utility* could be adjusted to cover two  common scenarios: ***write text to external file*** and ***perform certain action against an element***. The provided sample code requires reference to ***System.IO.dll*** and  ***ArtOfTest.WebAii.Controls.HtmlControls.dll*** added in the project settings and the respective *using* statements in the code. Note that the namespace of the standalone code file must be the same as the namespace of the project.
 
-```C#
+````C#
 using System.IO;
 using ArtOfTest.WebAii.Controls.HtmlControls;
 
@@ -42,8 +42,8 @@ namespace YourTestProjectNamespace
         }
 	}
 }
-```
-```VB
+````
+````VB
 Imports System.IO
 Imports ArtOfTest.WebAii.Controls.HtmlControls
 
@@ -72,15 +72,15 @@ Namespace YourTestProjectNamespace
 		End Sub
 	End Class
 End Namespace
-```
+````
 
 Once the code file is ready for use compile the project to build the assembly. Then you'll be able to access the functions/variables within your *Utility* class from all tests in this project. Note that the Test Studio code editor will not auto-complete references to the contents of the *Utility* class.
 
-### How To Use Methods And Variables From The Utility Class File ###
+### How To Use Methods And Variables From The Utility Class File 
 
 The code sample below demonstrates how the global methods and variables could be accessed in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a>. 
 
-```C#
+````C#
 //set value to the global variable
 Utility.valueHolder = 2;
 
@@ -95,8 +95,8 @@ HtmlControl searchBtn = Find.ById<HtmlControl>("controlId");
 
 //call Utility class method to perform click on element using the predefined static function
 Utility.ClickOnElement(searchBtn);
-```
-```VB
+````
+````VB
 Utility.valueHolder = 2
 
 Log.WriteLine("Value from Utility class:" + Utility.valueHolder.ToString())
@@ -106,4 +106,4 @@ Utility.writeToFile("c:\myNewText200.txt", "some content")
 Dim searchBtn As HtmlControl = Find.ById(Of HtmlControl)("sb_form_go")
 
 Utility.clickOnElement(searchBtn)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/verify-not-empty.md b/docs/advanced-topics/coded-samples/general/verify-not-empty.md
index 0fd988ea..a440a07b 100644
--- a/docs/advanced-topics/coded-samples/general/verify-not-empty.md
+++ b/docs/advanced-topics/coded-samples/general/verify-not-empty.md
@@ -1,28 +1,30 @@
 ---
 title: Verify Not Empty
 page_title: Verify The Text Content of an Element is Not Empty
-description: "Verify the text content of an element is not empty in Test Studio test run."
+description: "Learn how to verify that the text content of an element is not empty in Test Studio tests. Includes code examples for checking and asserting non-empty values during automated test runs."
 position: 1
 ---
-# Verify Not Empty #
+# Verify Not Empty 
 
 *I would like to verify the text content of an element is not empty. In other words, that it contains one or more characters.*
 
+## Solution
+
 This is possible with a coded solution. The example below is against <a href="http://www.w3schools.com/html/html_tables.asp" target="_blank">this W3Schools site</a>.
 
-```C#
+````C#
 HtmlTable table = Find.ByTagIndex<HtmlTable>("table", 0);
 HtmlTableRow row = table.Rows[0];
 HtmlTableCell cell = row.Cells[1];
  
 Log.WriteLine(cell.TextContent);
 Assert.IsTrue(cell.TextContent.Length > 0);
-```
-```VB
+````
+````VB
 Dim table As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
 Dim row As HtmlTableRow = table.Rows(0)
 Dim cell As HtmlTableCell = row.Cells(1)
  
 Log.WriteLine(cell.TextContent)
 Assert.IsTrue(cell.TextContent.Length > 0)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/general/wait-for-element-in-code.md b/docs/advanced-topics/coded-samples/general/wait-for-element-in-code.md
index 0eb2b0e8..170258b6 100644
--- a/docs/advanced-topics/coded-samples/general/wait-for-element-in-code.md
+++ b/docs/advanced-topics/coded-samples/general/wait-for-element-in-code.md
@@ -1,54 +1,65 @@
 ---
 title: Wait for Element in Code
 page_title: Wait for Element in Code
-description: "Wait for Element in Coded Test Studio test."
-previous_url: /user-guide/code-samples/general/wait-for-element-to-exist-in-code.aspx, /user-guide/code-samples/general/wait-for-element-to-exist-in-code
+description: "Learn how to wait for elements in Test Studio coded tests using custom timeouts and best practices. Includes code examples for HTML and WPF elements to ensure reliable test execution."
 position: 1
 ---
-#Wait for Element in Code#
+# Wait for Element in Code
 
 *In a coded step you need to wait for an element to exist before performing an action or a verification against that element. Perhaps you selected to "Customize Step in Code" and the default element wait time is not sufficient.*
 
-##Solution##
+## Solution
 
 After customizing a step in code you may have code that looks like this for an HTML element:
 
-```C#
+````C#
 //Check 'VehicleCheckBox0' to be 'False'
 Pages.HTMLFormsAndInput.VehicleCheckBox0.Check(true, true);
-```
+````
 
 
 Or like this for a WPF element:
 
 
-```C#
+````C#
 //LeftClick on CheckBoxCheckbox
 Pages.Pale2.App.CheckBoxCheckbox.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick, true, true, 8, 7, ArtOfTest.Common.OffsetReference.TopLeftCorner, ArtOfTest.Common.ActionPointUnitType.Pixel, ((System.Windows.Forms.Keys)(0)));
-```
+````
 
 
 In the above code sample, the parts **Pages.HTMLFormsAndInput.VehicleCheckBox0 and Pages.Pale2.App.CheckBoxCheckbox** actually perform an implied Find under the hood. This implied Find uses the global timeout setting of 10 seconds by default. If the element does not exist within this 10 seconds, your test fails indicating an "element not found" error.
  
 You might think you could avoid this by calling the **Wait.ForExists** function on the element like this:
 
-```C#
+````C#
 Pages.HTMLFormsAndInput.VehicleCheckBox0.Wait.ForExists(30000);
-```
+````
 
 
 However, **Pages.HTMLFormsAndInput.VehicleCheckBox0** performs the implied Find using the global timeout setting prior to calling the **Wait.ForExists function**. 
 Instead, for HTML elements, you should precede your line of code with an **ActiveBrowser.WaitForElement** call that uses the Find Expression for the element you need to wait for:
 
-```C#
+````C#
 ActiveBrowser.WaitForElement(Pages.HTMLFormsAndInput.Expressions.VehicleCheckBox0, 33000, false);
  
 //Check 'VehicleCheckBox0' to be 'False'
 Pages.HTMLFormsAndInput.VehicleCheckBox0.Check(true, true);
-```
+````
 
 In this sample, **Pages.HTMLFormsAndInput.Expressions.VehicleCheckBox0** returns the Find Expression associated with the **VehicleCheckBox0** element, then calls **WaitForElement** with a 33 second timeout parameter. This will have the desired effect of waiting 33 seconds for the element to exist prior to acting on it.
  
+For **Silverlight** elements, precede your line of code with something like this:
+
+````C#
+CheckBox cbox = Pages.SilverlightGridControl.SilverlightApp.Get<CheckBox>(Pages.SilverlightGridControl.SilverlightApp.Expressions.Item0Checkbox, true, 33000);
+ 
+//LeftClick on CheckBoxCheckbox
+Pages.Pale2.SilverlightApp.CheckBoxCheckbox.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick, true, true, 8, 7, ArtOfTest.Common.OffsetReference.TopLeftCorner, ArtOfTest.Common.ActionPointUnitType.Pixel, ((System.Windows.Forms.Keys)(0)));
+````
+
+
+In this sample, **Pages.SilverlightGridControl.SilverlightApp.Expressions.Item0Checkbox** returns the Find Expression associated with the Item0Checkbox element. The Find Expression is used in the Get method with a 33 second timeout parameter to wait for the element to exist and return it as an object. This will have the desired effect of waiting 33 seconds for the element to exist prior to acting on it.
+
 
 
 
diff --git a/docs/advanced-topics/coded-samples/general/write-into-data-source.md b/docs/advanced-topics/coded-samples/general/write-into-data-source.md
index 9cd30a96..607cd9dc 100644
--- a/docs/advanced-topics/coded-samples/general/write-into-data-source.md
+++ b/docs/advanced-topics/coded-samples/general/write-into-data-source.md
@@ -1,7 +1,7 @@
 ---
 title: Write into Data Source
 page_title: Write into Data Source
-description: "Write into external Data Source Excel file during a Test Studio test run."
+description: "Learn how to write data into an external Excel data source during a Test Studio test run. Step-by-step code examples for updating Excel files based on test results."
 position: 1
 ---
 # Write into Data Source
@@ -14,12 +14,20 @@ This is possible with a coded solution. Here's an example:
 
 Let's automate <a href="http://www.checkdomain.com/" target ="_blank">checkdomain.com</a> to check whether the domains listed in an Excel file are still available. We'll write Registered or Available into the first column of the Excel file for each domain name.
 
-<table id="no-table">
-	<tr>
-		<td>![Before Test Run][1] <br><br>**Before Test Run**</td>
-		<td>![After Test Run][2] <br><br>**After Test Run**</td>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td style="text-align: center;">
+
+![Before Test Run][1]
+<strong>Before Test Run</strong>
+</td>
+		<td style="text-align: center;">
+
+![After Test Run][2]
+<strong>After Test Run</strong>
+        </td>
 	</tr>
-<table>
+</table>
 
 Here's a sample test that automates this case:
 
@@ -29,7 +37,7 @@ Here's a sample test that automates this case:
 
 Here's the code from that sample:
 
-```C#
+````C#
     string dataSourcePath = this.ExecutionContext.DeploymentDirectory + @"\Data\domainResults.xlsx";
     string myPath = "C:\\domainResults.xlsx";
 
@@ -63,8 +71,8 @@ Here's the code from that sample:
     excelApp.Quit();
     GC.Collect();
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp);
-```
-```VB
+````
+````VB
     Dim dataSourcePath As String = Me.ExecutionContext.DeploymentDirectory + "\Data\domainResults.xlsx"
     Dim myPath As String = "C:\domainResults.xlsx"
     
@@ -95,7 +103,7 @@ Here's the code from that sample:
     excelApp.Quit()
     GC.Collect()
     System.Runtime.InteropServices.Marshal.ReleaseComObject(excelApp)
-```
+````
 
 ## How to Find and Use Office PIA's
 
diff --git a/docs/advanced-topics/coded-samples/html/add-tag-to-iframe.md b/docs/advanced-topics/coded-samples/html/add-tag-to-iframe.md
index 00e5c63c..4d477bf9 100644
--- a/docs/advanced-topics/coded-samples/html/add-tag-to-iframe.md
+++ b/docs/advanced-topics/coded-samples/html/add-tag-to-iframe.md
@@ -1,11 +1,11 @@
 ---
 title: Add Tag to iFrame
 page_title: Add Tag to iFrame
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/tagframe.aspx, /user-guide/code-samples/html/tagframe
+description: "Learn how to add custom tags to iframes in Test Studio, either by modifying HTML or dynamically through coded steps, to improve frame identification during automated testing."
+
 position: 1
 ---
-#Add Tag to iFrame#
+# Add Tag to iFrame
 
 To help Test Studio locate your iframes, you can add a custom tag to the iframe. You can then add this tag to the <a href="/getting-started/test-recording/Frames" target="_blank">frame properties</a> in your test. There are two ways to add a tag to an iframe:
 
@@ -13,41 +13,41 @@ To help Test Studio locate your iframes, you can add a custom tag to the iframe.
 
 * Add the tag dynamically in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a>.
 
-##Add a Tag to a iframe in HTML##
+## Add a Tag to a iframe in HTML
 
 To add a tag to a iframe in your application's HTML, add the 'testStudioTag' attribute to the frame element. For example:
 
-```HTML
+````HTML
 <iframe src="http://www.example.com" testStudioTag="ExampleTag"></iframe>
-```
+````
 
-##Add a Tag Dynamically in Code##
+## Add a Tag Dynamically in Code
 
 If it is not possible to add custom tags to your iframes, you can add them at runtime using a coded step.
 
 1. Add the following using directive to your <a href="/advanced-topics/coded-steps/code-behind-file" target="_blank">code-behind file</a>:
 
-	```C#
-	using ArtOfTest.WebAii.Design.Extensions;
-	```
+````C#
+using ArtOfTest.WebAii.Design.Extensions;
+````
 
 2. Call the **myFrame()** method on the frame object in a coded step. For example:
 
-	```C#
-	[CodedStep(@"Tag Frame with 'MyCustomTag'")]
-	public void WebTest1_CodedStep()
+````C#
+[CodedStep(@"Tag Frame with 'MyCustomTag'")]
+public void WebTest1_CodedStep()
+{
+	Browser myFrame = this.ActiveBrowser.Frames[0] as Browser;
+	if (myFrame != null )
 	{
-	    Browser myFrame = this.ActiveBrowser.Frames[0] as Browser;
-	    if (myFrame != null )
-	    {
-	        myFrame.TagFrame("MyCustomTag");
-	    }          
-	}
-	```
+		myFrame.TagFrame("MyCustomTag");
+	}          
+}
+````
 
 To tag a nested iframe, ensure the entire DOM is built, so that Test Studio can access the iframes. For example:
 
-```C#
+````C#
 [CodedStep(@"Tag nested frame with 'MyCustomTag'")]
 public void WebTest1_CodedStep()
 {
@@ -59,8 +59,8 @@ public void WebTest1_CodedStep()
         myFrame.TagFrame("MyCustomTag");
     }           
 }
-```
+````
 
-##See also##
+## See also
 
 * <a href="/getting-started/test-recording/Frames" target="_blank">Recording Frames</a>
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/html/ajax-calendar-random-date.md b/docs/advanced-topics/coded-samples/html/ajax-calendar-random-date.md
index 43525790..77807948 100644
--- a/docs/advanced-topics/coded-samples/html/ajax-calendar-random-date.md
+++ b/docs/advanced-topics/coded-samples/html/ajax-calendar-random-date.md
@@ -1,19 +1,18 @@
 ---
 title: AJAX Calendar Random Date
 page_title: AJAX Calendar Random Date
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/ajax-calendar-random-date-selection.aspx, /user-guide/code-samples/html/ajax-calendar-random-date-selection
+description: "Learn how to select a random date from an AJAX calendar using Test Studio's automated testing capabilities, with example in C#"
 position: 1
 ---
-#AJAX Calendar - Random Date Selection#
+# AJAX Calendar - Random Date Selection
 
 *I would like to select a random date from an Ajax Calendar.*
 
-##Solution##
+## Solution
 
 The code below will show you how to select a random date from the Calendar on <a href="http://www.weekendesk.fr/week-end/4398/week-end-a-Courseulles-sur-Mer-Normandie-Week-ends_gourmands" target="_blank">this site</a>.
 
-```C#
+````C#
 //We scroll to the date picker so that we can see the click occuring. //Pages.WeekEndCourseullesSurMer.WeekendFormFormTag is a definiton which Test Studio automatically generated.
 Pages.WeekEndCourseullesSurMer.WeekendFormFormTag.ScrollToVisible(ScrollToVisibleType.ElementBottomAtWindowBottom);
               
@@ -50,8 +49,8 @@ while (randomNum != 0)
  
 //Click on the node after we reach it in the list.
 l.Value.MouseClick();
-```
-```VB
+````
+````VB
 'We scroll to the date picker so that we can see the click occuring. //Pages.WeekEndCourseullesSurMer.WeekendFormFormTag is a definiton which Test Studio automatically generated.
 Pages.WeekEndCourseullesSurMer.WeekendFormFormTag.ScrollToVisible(ScrollToVisibleType.ElementBottomAtWindowBottom)
  
@@ -85,4 +84,4 @@ End While
  
 'Click on the node after we reach it in the list.
 l.Value.MouseClick()
-```
+````
diff --git a/docs/advanced-topics/coded-samples/html/async-upload-dialog.md b/docs/advanced-topics/coded-samples/html/async-upload-dialog.md
deleted file mode 100644
index dd78b57d..00000000
--- a/docs/advanced-topics/coded-samples/html/async-upload-dialog.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: AsyncUpload Dialog
-page_title: AsyncUpload Dialog
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/handling-radasynchdialog.aspx, /user-guide/code-samples/html/handling-radasynchdialog
-position: 1
----
-#How to Handle the AsyncUpload Dialog#
-
-There are differences in how RadAsyncUpload is interpreted across different browsers. AsyncUpload is built over Silverlight in Internet Explorer, but rendered in HTML5 in the other browsers (Firefox, Safari, and Chrome). This greatly affects cross-browser UI Automation. You can work around the problem by using a coded step to handle the dialog:
-
-```C#
-public void Upload(int index, string filePath)
-{
-FileUploadDialog uploadDialog = new FileUploadDialog(OwnerBrowser, filePath, DialogButton.OPEN, this.UploadDialogTitle);
-Manager.Current.DialogMonitor.AddDialog(uploadDialog);
-Manager.Current.DialogMonitor.Start();
-this.FileSelect(index);
-OwnerBrowser.WaitUntilReady();
-uploadDialog.WaitUntilHandled();
-Manager.Current.DialogMonitor.Stop();
-Manager.Current.DialogMonitor.RemoveDialog(uploadDialog);
-}
-```
-```VB
-Public Sub Upload(index As Integer, filePath As String)
-    Dim uploadDialog As New FileUploadDialog(OwnerBrowser, filePath, DialogButton.OPEN, Me.UploadDialogTitle)
-    Manager.Current.DialogMonitor.AddDialog(uploadDialog)
-    Manager.Current.DialogMonitor.Start()
-    Me.FileSelect(index) 
-    OwnerBrowser.WaitUntilReady()
-    uploadDialog.WaitUntilHandled()
-    Manager.Current.DialogMonitor.[Stop]()
-    Manager.Current.DialogMonitor.RemoveDialog(uploadDialog)
-End Sub
-```
-
-
diff --git a/docs/advanced-topics/coded-samples/html/common-find-expressions.md b/docs/advanced-topics/coded-samples/html/common-find-expressions.md
index c06bdeb6..47cec54a 100644
--- a/docs/advanced-topics/coded-samples/html/common-find-expressions.md
+++ b/docs/advanced-topics/coded-samples/html/common-find-expressions.md
@@ -1,15 +1,14 @@
 ---
 title: Common HTML Find Expressions
 page_title: Common HTML Find Expressions
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/common-find-expressions.aspx, /user-guide/code-samples/html/common-find-expressions
+description: "Learn how to use common HTML find expressions in Test Studio to locate and interact with elements like hyperlinks using C#, with examples for partial matches, exact matches, XPath, and data-driven expressions."
 position: 1
 ---
-#Common HTML Find Expressions#
+# Common HTML Find Expressions
 
 *I would like to click on a hyperlink based on its text value. I prefer to do this in code and not by editing an existing element's <a href="/features/elements-explorer/find-element" target="_blank">Find Settings</a>*.
 
-##Solution##
+## Solution
 
 Let's use <a href="http://www.wikipedia.org/" target="_blank">wikipedia.org</a> as an example. First we'll find and click the top bold English link.
 
@@ -17,7 +16,7 @@ Let's use <a href="http://www.wikipedia.org/" target="_blank">wikipedia.org</a>
 
 Here's the HTML code for that link:
 
-```HTML
+````HTML
 <a href="//en.wikipedia.org/" title="English — Wikipedia — The Free Encyclopedia">
 <strong>English</strong>
 <br>
@@ -25,20 +24,20 @@ Here's the HTML code for that link:
 <br>
 <small>3 907 000+ articles</small>
 </a>
-```
+````
 
 The anchor element has no direct TextContent, so we'll need to locate by a partial match on InnerText:
 
-```C#
+````C#
 HtmlAnchor a = Find.ByExpression<HtmlAnchor>("InnerText=~English", "tagname=a");
 Assert.IsNotNull(a);
 a.Click();
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("InnerText=~English", "tagname=a")
 Assert.IsNotNull(a)
 a.Click()
-```
+````
 
 If we locate by an exact match on TextContent, the bottom *English* link will found.
 
@@ -46,49 +45,49 @@ If we locate by an exact match on TextContent, the bottom *English* link will fo
 
 Here's the HTML code for that link:
 
-```HTML
+````HTML
 <a href="//en.wikipedia.org/" lang="en">English</a>
-```
+````
 
 Here's how to locate and click that link:
 
-```C#
+````C#
 HtmlAnchor a = Find.ByExpression<HtmlAnchor>("TextContent=English", "tagname=a");
 Assert.IsNotNull(a);
 a.Click();
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("TextContent=English", "tagname=a")
 Assert.IsNotNull(a)
 a.Click()
-```
+````
 
 The following attributes apply to both links, however Test Studio returns the first HtmlAnchor that matches. In this case, that's the top bold *English* link.
 
-```C#
+````C#
 HtmlAnchor a = Find.ByExpression<HtmlAnchor>("tagname=a", "href=//en.wikipedia.org/");
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("tagname=a", "href=//en.wikipedia.org/")
-```
+````
 
 You can find it by xpath:
 
-```C#
+````C#
 HtmlAnchor a = Find.ByXPath<HtmlAnchor>("//*[@id=\"www-wikipedia-org\"]/div[5]/div/a[2]");
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ByXPath(Of HtmlAnchor)("//*[@id=""www-wikipedia-org""]/div[5]/div/a[2]")
-```
+````
 
 You can also data drive the find expression:
 
-```C#
+````C#
 HtmlAnchor a = Find.ByExpression<HtmlAnchor>("tagname=a", "textcontent=" + Data["Col1"].ToString());
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ByExpression(Of HtmlAnchor)("tagname=a", "textcontent=" + Data("Col1").ToString())
-```
+````
 
 
 [1]: /img/advanced-topics/coded-samples/html/common-find-expressions/fig1.png
diff --git a/docs/advanced-topics/coded-samples/html/conditional-dialog-handling.md b/docs/advanced-topics/coded-samples/html/conditional-dialog-handling.md
index 5f7b399b..18ffb887 100644
--- a/docs/advanced-topics/coded-samples/html/conditional-dialog-handling.md
+++ b/docs/advanced-topics/coded-samples/html/conditional-dialog-handling.md
@@ -1,18 +1,22 @@
 ---
 title: Conditional Dialog Handling
 page_title: Conditional Dialog Handling
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/conditional-dialog-handling.aspx, /user-guide/code-samples/html/conditional-dialog-handling
+description: "Learn how to conditionally handle dialogs in Test Studio using C# and VB.NET. This guide provides a coded solution to manage dialogs dynamically during automated testing, ensuring seamless test execution."
 position: 1
 ---
-#Conditionally Handling Dialog#
+# Conditionally Handling Dialog
 
 ***I would like to conditionally handle a dialog. If it appears, I'd like to handle it normally. If it doesn't, I'd like to continue with test execution.***
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The action that potentially triggers the dialog must be included in the code.
 
+ __Tip!__
+><br>
+><br>
+> The example shows handling an alert dialog in a web test. Though the sample can be adjusted to implement any of the <a href="/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers" target="_blank">available built-in dialog handlers</a> including WPF dialogs. 
+
 ```C#
 ActiveBrowser.NavigateTo("http://www.w3schools.com/js/tryit.asp?filename=tryjs_alert");
  
@@ -38,8 +42,8 @@ catch (TimeoutException)
 Manager.DialogMonitor.RemoveDialog(ad);
  
 ActiveBrowser.NavigateTo("http://www.bing.com");
-```
-```VB
+````
+````VB
 ActiveBrowser.NavigateTo("http://www.w3schools.com/js/tryit.asp?filename=tryjs_alert")
  
 
@@ -59,5 +63,5 @@ End Try
 Manager.DialogMonitor.RemoveDialog(ad)
  
 ActiveBrowser.NavigateTo("http://www.bing.com")
-```
+````
 
diff --git a/docs/advanced-topics/coded-samples/html/dynamic-grid.md b/docs/advanced-topics/coded-samples/html/dynamic-grid.md
index 3cc8afbc..474f41ae 100644
--- a/docs/advanced-topics/coded-samples/html/dynamic-grid.md
+++ b/docs/advanced-topics/coded-samples/html/dynamic-grid.md
@@ -1,16 +1,16 @@
 ---
 title: Dynamic Grid
 page_title: Dynamic Grid
-description: "Automating a dynamic grid - how to overcome the challenge that the content of the cells in grid changes? The recorded elements use the text content of cells which changes and I can't execute the tests unless if I don't change the find expressions of elements.  How can avoid constant update of grid elements?"
+description: "Learn how to automate dynamic grids in Test Studio, handle changing cell content, and avoid constant updates to element find expressions. Step-by-step guide with code examples for reliable grid automation."
 position: 1
 ---
-#Automating a Dynamically Generated Grid#
+# Automating a Dynamically Generated Grid
 
 You need to automate an ASP .NET Grid control like the one seen <a href="http://demos.telerik.com/aspnet-ajax/grid/examples/client/selecting/defaultcs.aspx" target="_blank">here</a>.
 
 **Note:** this is a Telerik-manufactured RadControl but this solution applies to generic/custom grids as well.
 
-##Solution##
+## Solution
 
 This can be achieved in both the Standalone version and Visual Studio plugin through a coded solution. We will use <a href="http://demos.telerik.com/aspnet-ajax/grid/examples/client/selecting/defaultcs.aspx" target="_blank">this grid</a> to demonstrate how to do it.
 
@@ -32,11 +32,11 @@ Going back to Test Studio, you will notice a new element has appeared in Project
 
 ![Add to project][3]
 
-##Outputting the content of each (visible) cell to the Log
+## Outputting the content of each (visible) cell to the Log
 
 Create a new coded step and add the following lines that go through each (visible) cell in the Grid:
 
-```C#
+````C#
 foreach (HtmlTableRow r in Pages.TelerikWebUIGridRow.ContentPlaceholder1RadGrid1Table.AllRows)
 {
     foreach(HtmlTableCell c in r.Cells)
@@ -44,11 +44,11 @@ foreach (HtmlTableRow r in Pages.TelerikWebUIGridRow.ContentPlaceholder1RadGrid1
         Log.WriteLine("Cell found. TextContent: "+c.TextContent);  
     }
 }
-```
+````
 
 This is C# code, the VB code will follow the same logic only transcribed in the corresponding syntax. Make sure the coded steps executes at a point in your test when the page congaing the Grid is loaded in the Active Browser.
 
-##Locate a specific row and click on a specific cell in that row
+## Locate a specific row and click on a specific cell in that row
 
 Let's look at the grid in the below image. Let's imagine we want to get the row that contains the Contact Name "Thomas Hardy" and from there we want to click the checkbox in the same Row:
 
@@ -56,9 +56,8 @@ Let's look at the grid in the below image. Let's imagine we want to get the row
 
 In this example we want to click a checkbox but the nested control in the grid may be any other type. To adjust it you will need to change the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements" target="_blank">Find.ByXX statement</a>. For this example we again use the definition of the Grid that we've stored in the Project's Elements Explorer (as seen in Solution 1 of this article). Here's the code:
 
-```C#
-//The variable that will store the row which contains the name cell and the checkbox cell
-HtmlTableRow containerRow=null; 
+````C#
+HtmlTableRow containerRow=null; //The variable that will store the row that contains the name cell and the checkbox cell
 
 foreach (HtmlTableRow r in Pages.TelerikWebUIGridRow.ContentPlaceholder1RadGrid1Table.AllRows)
 {
@@ -89,10 +88,9 @@ Assert.IsNotNull(checkbox);
 // Scroll the element to be visible and click on it
 checkbox.ScrollToVisible(ScrollToVisibleType.ElementCenterAtWindowCenter);
 checkbox.MouseClick();
-```
+````
 
 [1]: /img/advanced-topics/coded-samples/html/dynamic-grid/fig1.png
 [2]: /img/advanced-topics/coded-samples/html/dynamic-grid/fig2.png
 [3]: /img/advanced-topics/coded-samples/html/dynamic-grid/fig3.png
 [4]: /img/advanced-topics/coded-samples/html/dynamic-grid/fig4.png
-[5]: /img/advanced-topics/coded-samples/html/dynamic-grid/fig5.png
diff --git a/docs/advanced-topics/coded-samples/html/extract-an-attribute.md b/docs/advanced-topics/coded-samples/html/extract-an-attribute.md
index 85b4e652..c6cc07f1 100644
--- a/docs/advanced-topics/coded-samples/html/extract-an-attribute.md
+++ b/docs/advanced-topics/coded-samples/html/extract-an-attribute.md
@@ -1,45 +1,44 @@
 ---
 title: Extract an Attribute
 page_title: Extract an Attribute
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/extract-an-attribute.aspx, /user-guide/code-samples/html/extract-an-attribute
+description: "Learn how to extract individual HTML attributes in Test Studio using C# and VB.NET. This guide provides a coded solution to retrieve attribute values and use them later in automated tests through data binding."
 position: 1
 ---
-#Extract an Individual HTML Attribute#
+# Extract an Individual HTML Attribute
 
 *I would like to extract an individual HTML attribute and use it later in the test.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. First, be aware that if you're simply verifying the value for a specific attribute, that can be accomplished without code using an <a href="/features/verifications/advanced-verification" target="_blank">Advanced Verification</a>.
 
 HTML elements are formatted the following way:
 
-```
+````
 <tagname attribute="value">content</tagname>
-```
+````
 
 
-```HTML
+````HTML
 <a href="http://www.google.com" lang="en" id="googleLink">Go to Google</a>
-```
+````
 
 
 Here's how to set the value of the *lang* attribute (*which is en*) to a string. That string is then set as an <a href="/advanced-topics/coded-samples/general/extracted-variables-in-code" target="_blank">extracted value</a> to use later in the test through data binding (either attached to an <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">input value</a> or a <a href="/features/data-driven-testing/attach-columns-verifications" target="_blank">verification</a>).
 
-```C#
+````C#
 HtmlAnchor a = Find.ById<HtmlAnchor>("googleLink");
 Assert.IsNotNull(a);
  
 string atr = a.Attributes.Single(x => x.Name == "lang").Value;
 Log.WriteLine(atr);
 SetExtractedValue("extraction", atr);
-```
-```VB
+````
+````VB
 Dim a As HtmlAnchor = Find.ById(Of HtmlAnchor)("googleLink")
 Assert.IsNotNull(a)
  
 Dim atr As String = a.Attributes.[Single](Function(x) x.Name = "lang").Value
 Log.WriteLine(atr)
 SetExtractedValue("extraction", atr)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/html/image-comparison.md b/docs/advanced-topics/coded-samples/html/image-comparison.md
index 4d37a948..c22f1c59 100644
--- a/docs/advanced-topics/coded-samples/html/image-comparison.md
+++ b/docs/advanced-topics/coded-samples/html/image-comparison.md
@@ -1,19 +1,19 @@
 ---
 title: Image Comparison
 page_title: Image Comparison
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to perform image comparisons in Test Studio using C# and VB.NET. This guide provides a coded solution to compare browser images with stored images, allowing tolerance levels for automated testing."
 previous_url: /user-guide/code-samples/html/image-comparison.aspx, /user-guide/code-samples/html/image-comparison
 position: 1
 ---
-#Perform an Image Comparison in Code#
+# Perform an Image Comparison in Code
 
 *I would like to compare a specific image from the browser to one stored on disk.*
 
-##Solution##
+## Solution
 
 Here is sample code showing how to perform an image comparison:
 
-```C#
+````C#
 HtmlImage img = Find.ById<HtmlImage>("myImageId");
 System.Drawing.Bitmap actualbmp = img.Capture();
   
@@ -21,8 +21,8 @@ ArtOfTest.Common.PixelMap expected = ArtOfTest.Common.PixelMap.FromBitmap(expect
 ArtOfTest.Common.PixelMap actual = ArtOfTest.Common.PixelMap.FromBitmap(actualbmp);
  
 Assert.IsTrue(expected.Compare(actual, 5.0));
-```
-```VB
+````
+````VB
 Dim img As HtmlImage = Find.ById(Of HtmlImage)("myImageId")
 Dim actualbmp As System.Drawing.Bitmap = img.Capture()
 
@@ -30,6 +30,6 @@ Dim expected As ArtOfTest.Common.PixelMap = ArtOfTest.Common.PixelMap.FromBitmap
 Dim actual As ArtOfTest.Common.PixelMap = ArtOfTest.Common.PixelMap.FromBitmap(actualbmp)
 
 Assert.IsTrue(expected.Compare(actual, 5.0))
-```
+````
 
 In the above code I am getting the image of the "myImageId" element from the browser and comparing it to the expected image stored on disk named "myExpected.png". The comparison is allowing a 5% tolerance, meaning there may be up to a 5% difference in the image or else the Assert fails and the test aborts.
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/html/jquery-events-do-not-fire.md b/docs/advanced-topics/coded-samples/html/jquery-events-do-not-fire.md
index b9f87b7a..481d7119 100644
--- a/docs/advanced-topics/coded-samples/html/jquery-events-do-not-fire.md
+++ b/docs/advanced-topics/coded-samples/html/jquery-events-do-not-fire.md
@@ -1,38 +1,43 @@
 ---
 title: jQuery Events Do Not Fire
 page_title: jQuery Events Do Not Fire
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/jquery-events-do-not-fire.aspx, /user-guide/code-samples/html/jquery-events-do-not-fire
+description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 1
+publish: false
 ---
-#jQuery Events Do Not Fire During Test Execution#
-
-**Note:** As of 2012 R1 SP1, use the TriggerjQueryEvent <a href="/features/test-maintenance/test-step-properties" target="_blank">Test Step Property</a> to trigger jQuery events for HTML drop-down menus. Minimum supported jQuery version is 1.4.
+# jQuery Events Do Not Fire During Test Execution 
 
 In some cases, Test Studio does not automatically call local jQuery events. You must add a coded step to make the local jQuery event fire manually.
 
 Inputting text into <a href="http://www.w3schools.com/jquery/tryit.asp?filename=tryjquery_event_change" target="_blank">this</a> simple HTML text box triggers a jQuery event that changes the background color of the text box.
 
-<table id="no-table">
+<table id="no-table" style="border:none;">
 	<tr>
-		<td>![Before Selection][1] </br></br>**Before Selection**</td>
-		<td>![Available Selections][2] </br></br>**Available Selections**</td>
-		<td>![After Selection][3] </br></br>**After Selection**</td>
-	</tr>
-<table>
+		<td style="text-align: center;">
+		
+![Before Selection][1] </br></br>**Before Selection**</td>
+<td style="text-align: center;">
+
+![Available Selections][2] </br></br>**Available Selections**</td>
+<td style="text-align: center;">
+
+![After Selection][3] </br></br>**After Selection**</td>
+
+</tr>
+</table>
 
 This is the HTML for the text input element:
 
-```HTML
+````HTML
 Enter your name: <input class="field" type="text">
-```
+````
 
 
 Invoke the script that changes the background color with the following coded step:
 
-```C#
+````C#
 Pages.TryitEditorV220.FrameIframeResult.Text.AsjQueryControl().InvokejQueryEvent(ArtOfTest.WebAii.jQuery.jQueryControl.jQueryControlEvents.change);
-```
+````
 
 * The guideline is to always pair the two steps together. Immediately after performing the change step (input, radio button, etc.), run the coded step that calls the .change function for that element.
 
diff --git a/docs/advanced-topics/coded-samples/html/partial-attributes-search-fails.md b/docs/advanced-topics/coded-samples/html/partial-attributes-search-fails.md
index ab703893..d1beaa85 100644
--- a/docs/advanced-topics/coded-samples/html/partial-attributes-search-fails.md
+++ b/docs/advanced-topics/coded-samples/html/partial-attributes-search-fails.md
@@ -1,41 +1,41 @@
 ---
 title: Partial Attributes Search Fails
 page_title: Partial Attributes Search Fails
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to resolve issues with partial attribute searches in Test Studio when locating controls by type. This guide provides a detailed explanation and a coded solution using C# to ensure accurate element identification."
 previous_url: /user-guide/code-samples/html/search-control-type-by-partial-attributes-fails.aspx, /user-guide/code-samples/html/search-control-type-by-partial-attributes-fails
 position: 1
 ---
-#Partial Attributes Search by Control Type Fails#
+# Partial Attributes Search by Control Type Fails
 
-##PROBLEM##
+## PROBLEM
 
 A partial search of control by attribute may return null even with correct partial search syntax. For example a HtmlInputButton search on the page having a complex ID containing some specific string should be located successfully using the following syntax:
 
-```C#
+````C#
 HtmlInputButton button = Find.ById<HtmlInputButton>("~MyButtonIDPart");
-```
+````
 
 
 Although the next example works:
 
 
-```C#
+````C#
 HtmlInputButton button = Find.ById<HtmlInputButton>("SomeButtonIDPart_MyButtonIDPart");
-```
+````
 
-##DESCRIPTION##
+## DESCRIPTION
 
 The framework locates the first element matching the given attribute search criteria. Next, it compares the control type of the element and returns that element if the control type matches. If it does not, it simply returns null.
  
 In the first example, the framework returns null if there is another element that matches the given attribute search criteria and it is found before the target element. The control type does not match.
 
-##Solution##
+## Solution
 
-A simple solution is available. Use Find.AllByAttributes<Control Type> overload and return the first (and actually the only completely matching control):
+A simple solution is available. Use `Find.AllByAttributes<Control Type>` overload and return the first (and actually the only completely matching control):
 
-```C#
+````C#
 HtmlInputButton button = Find.AllByAttributes<HtmlInputButton>("id=~MyButtonIDPart")[0];
-```
+````
 
 
 
diff --git a/docs/advanced-topics/coded-samples/html/radwindow-width-height.md b/docs/advanced-topics/coded-samples/html/radwindow-width-height.md
index 0503f2af..1fbd8c44 100644
--- a/docs/advanced-topics/coded-samples/html/radwindow-width-height.md
+++ b/docs/advanced-topics/coded-samples/html/radwindow-width-height.md
@@ -1,21 +1,21 @@
 ---
 title: RadWindow Width & Height
 page_title: RadWindow Width & Height
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to retrieve the width and height of a RadWindow in Test Studio using C#. This guide provides two approaches: accessing properties directly or invoking JavaScript for precise measurements during automated testing."
 previous_url: /user-guide/code-samples/html/getting-radwindow-width-and-height.aspx, /user-guide/code-samples/html/getting-radwindow-width-and-height
 position: 1
 ---
-#Getting RadWindow Width and Height#
+# Getting RadWindow Width and Height
 
 *You need to get the RadWindow width or height property.*
 
-##Solution##
+## Solution
 
 First you need to get a reference to the RadWindow control by ID. Once you get it there are two options for getting the width/height. The first option is to use the relevant width/height properties of the RadWindow. The second is by invoking a straight JavaScript on the page.
 
 Here is the standard approach:
 
-```C#
+````C#
 Manager.LaunchNewBrowser();
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx");
 Find.ById<HtmlInputSubmit>("Button3").MouseClick();
@@ -25,8 +25,8 @@ RadWindow window = Find.ById<RadWindow>("RadWindowWrapper_RadWindow_ContentTempl
  
 //First Option
 Assert.AreEqual(300, window.Width);
-```
-```VB
+````
+````VB
 Manager.LaunchNewBrowser()
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx")
 Find.ById(Of HtmlInputSubmit)("Button3").MouseClick()
@@ -35,11 +35,11 @@ ActiveBrowser.RefreshDomTree()
 Dim window As RadWindow = Find.ById(Of RadWindow)("RadWindowWrapper_RadWindow_ContentTemplate")
 
 Assert.AreEqual(300, window.Width)
-```
+````
 
 Invoking JavaScript on the page:
 
-```C#
+````C#
 Manager.LaunchNewBrowser();
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx");
 Find.ById<HtmlInputSubmit>("Button3").MouseClick();
@@ -50,8 +50,8 @@ RadWindow window = Find.ById<RadWindow>("RadWindowWrapper_RadWindow_ContentTempl
 //Second Option
 string windowWidth = this.ActiveBrowser.Actions.InvokeScript(String.Format("$telerik.getBounds($find('RadWindow_ContentTemplate').get_popupElement()).width"));
 Assert.AreEqual("300", windowWidth);
-```
-```VB
+````
+````VB
 Manager.LaunchNewBrowser()
 ActiveBrowser.NavigateTo("http://demos.telerik.com/aspnet-ajax/window/examples/contenttemplatevsnavigateurl/defaultcs.aspx")
 Find.ById(Of HtmlInputSubmit)("Button3").MouseClick()
@@ -61,4 +61,4 @@ Dim window As RadWindow = Find.ById(Of RadWindow)("RadWindowWrapper_RadWindow_Co
 
 Dim windowWidth As String = Me.ActiveBrowser.Actions.InvokeScript([String].Format("$telerik.getBounds($find('RadWindow_ContentTemplate').get_popupElement()).width"))
 Assert.AreEqual("300", windowWidth)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/html/table-searching-paging.md b/docs/advanced-topics/coded-samples/html/table-searching-paging.md
index 80ae67a4..10957103 100644
--- a/docs/advanced-topics/coded-samples/html/table-searching-paging.md
+++ b/docs/advanced-topics/coded-samples/html/table-searching-paging.md
@@ -1,19 +1,19 @@
 ---
 title: Table Searching & Paging
 page_title: Table Searching & Paging
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to search and navigate through HTML tables with paging in Test Studio using C# and VB.NET. This guide provides a coded solution to locate specific content across multiple pages efficiently."
 previous_url: /user-guide/code-samples/html/table-search-and-paging.aspx, /user-guide/code-samples/html/table-search-and-paging
 position: 1
 ---
-#HTML Table Searching and Paging#
+# HTML Table Searching and Paging
 
 *I would like to search an HTML table for specific content and continue through the pages until it is found.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/grid/index" target="_blank">Telerik demo site</a>.
 
-```C#
+````C#
 HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
 HtmlSpan next = Find.ByExpression<HtmlSpan>("class=k-icon k-i-arrow-e");
 HtmlAnchor a = Find.ByExpression<HtmlAnchor>("title=Go to the next page");
@@ -52,8 +52,8 @@ while (false == found && false == disabled)
     System.Threading.Thread.Sleep(1000);
     table.Refresh();
 }
-```
-```VB
+````
+````VB
 Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
 Dim [next] As HtmlSpan = Find.ByExpression(Of HtmlSpan)("class=k-icon k-i-arrow-e")
 Dim a As HtmlAnchor =
@@ -87,4 +87,4 @@ While False = found AndAlso False = disabled
     System.Threading.Thread.Sleep(1000)
     table.Refresh()
 End While
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/html/table-sum-average.md b/docs/advanced-topics/coded-samples/html/table-sum-average.md
index e02a7158..7ce0cae7 100644
--- a/docs/advanced-topics/coded-samples/html/table-sum-average.md
+++ b/docs/advanced-topics/coded-samples/html/table-sum-average.md
@@ -1,19 +1,19 @@
 ---
 title: Table Sum & Average
 page_title: Table Sum & Average
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to calculate the sum and average of values in an HTML table column using Test Studio. This guide provides a coded solution in C# for efficient data processing in automated testing."
 previous_url: /user-guide/code-samples/html/table-sum-and-average.aspx, /user-guide/code-samples/html/table-sum-and-average
 position: 1
 ---
-#HTML Table Sum and Average#
+# HTML Table Sum and Average
 
 *I would like to get the sum and the average of the values in a certain column of an HTML table.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The example below is against <a href="http://www.w3schools.com/html/html_tables.asp" target="_blank">this W3Schools site</a>.
 
-```C#
+````C#
 HtmlTable table = Find.ByTagIndex<HtmlTable>("table", 0);
  
 double r = table.Rows.Count;
@@ -36,8 +36,8 @@ Log.WriteLine("Sum: " + sum.ToString());
 double average = sum / r;
 Log.WriteLine("Average: " + average.ToString());
 Assert.IsTrue(sum == 90);
-```
-```VB
+````
+````VB
 Dim table As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
  
 Dim r As Double = table.Rows.Count
@@ -59,6 +59,6 @@ Log.WriteLine("Sum: " + sum.ToString())
 Dim average As Double = sum / r
 Log.WriteLine("Average: " + average.ToString())
 Assert.IsTrue(sum = 90)
-```
+````
 
 
diff --git a/docs/advanced-topics/coded-samples/html/verify-dialog-text-chrome.md b/docs/advanced-topics/coded-samples/html/verify-dialog-text-chrome.md
index 97cb2b70..aca580b9 100644
--- a/docs/advanced-topics/coded-samples/html/verify-dialog-text-chrome.md
+++ b/docs/advanced-topics/coded-samples/html/verify-dialog-text-chrome.md
@@ -1,8 +1,9 @@
 ---
 title: Verify Dialog Text In Chrome
 page_title: Verify Dialog Text In Chrome
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to verify dialog text in Google Chrome during automated testing with Test Studio. This guide provides a coded solution using the AutomationElement class in C# and VB.NET for precise dialog handling and text verification."
 position: 1
+publish: false
 ---
 # How to Verify Dialog Text in Chrome
 
@@ -24,7 +25,7 @@ This could be achieved in a coded solution. The code will both handle the dialog
 > <br>
 > The last three could be usually found in *'C:\Program Files (x86)\Reference Assemblies\Microsoft\Framework\.NETFramework\v4.5\'*.
 
-```C# 
+````C# 
 [CodedStep(@"New Coded Step")]
         public void WebTest_CodedStep()
         {
@@ -54,8 +55,8 @@ This could be achieved in a coded solution. The code will both handle the dialog
             // handle the dialog
             Manager.Desktop.KeyBoard.KeyPress(Keys.Enter);
         }
-```
-```VB 
+````
+````VB 
 <CodedStep("New Coded Step")> _
 Public Sub WebTest_CodedStep()
 	System.Threading.Thread.Sleep(1000)
@@ -81,18 +82,18 @@ Public Sub WebTest_CodedStep()
 	' handle the dialog
 	Manager.Desktop.KeyBoard.KeyPress(Keys.Enter)
 End Sub
-```
+````
 
 Ensure you __add the following *using or Imports* statements__ to the top of the code-behind file.Scroll to the top of the code file and add these lines:
 
-```C#
+````C#
 using System.Windows.Automation;
 using ArtOfTest.Common.Extensions;
 using System.Windows.Forms;
-```
-```VB
+````
+````VB
 Imports System.Windows.Automation
 Imports ArtOfTest.Common.Extensions
 Imports System.Windows.Forms
-```
+````
 
diff --git a/docs/advanced-topics/coded-samples/html/verify-dialog-text.md b/docs/advanced-topics/coded-samples/html/verify-dialog-text.md
deleted file mode 100644
index 0fde964c..00000000
--- a/docs/advanced-topics/coded-samples/html/verify-dialog-text.md
+++ /dev/null
@@ -1,102 +0,0 @@
----
-title: Verify Dialog Text
-page_title: Verify Dialog Text
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/html/verify-dialog-text.aspx, /user-guide/code-samples/html/verify-dialog-text
-position: 1
----
-#How to Verify Dialog Text (Internet Explorer only)#
-
-*I would like to verify the text of a <a href="/features/dialogs-and-popups/Dialogs" target="_blank">Dialog</a> that is fired from the browser during test execution.*
-
-##Solution##
-
-This is possible with a coded solution. The code serves two purposes. It handles the dialog and verifies the text within it. The first part is the standard way to handle dialogs in code as seen <a href="/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs" target="_blank">here</a>. The second part uses a <a href="http://msdn.microsoft.com/en-us/library/ms173171(v=vs.80).aspx" target="_blank">delegate</a> to implement a custom handler for the dialog.
- 
-**Note:** This code requires an assembly reference to System.Windows.Forms. <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">Here</a> is an article on how to add an assembly reference in the Standalone version.
-
-```C#
-string dialogText;
- 
-[CodedStep(@"Navigate then verify text in popup dialog")]
-public void VerifyDialogText_CodedStep()
-{
-    ActiveBrowser.NavigateTo("http://www.w3schools.com/JS/tryit.asp?filename=tryjs_alert");
- 
-    // Click the button to fire the Alert Dialog inside the browser
-    FrameInfo myFrame = new FrameInfo("iframeResult", "", "", 0);
-    Browser frame = ActiveBrowser.Frames[myFrame];
-    HtmlButton tryItButton = frame.Find.ByTagIndex<HtmlButton>("button", 0);
-    Assert.IsNotNull(tryItButton);
-    
-    
-    // Initialize custom 'Alert' dialog handler
-    AlertDialog alertDialog = AlertDialog.CreateAlertDialog(ActiveBrowser, DialogButton.OK);
-    Manager.DialogMonitor.Start();
-    alertDialog.HandlerDelegate = MyCustomAlertHandler;
-    Manager.DialogMonitor.AddDialog(alertDialog);
-    tryItButton.Click();
-    
-    // Wait Until Dialog is Handled.
-    alertDialog.WaitUntilHandled(20000);
-
-    // Validate the text that was captured by the custom dialog handler
-    Assert.AreEqual<string>("I am an alert box!", dialogText);
-}
- 
-public void MyCustomAlertHandler(IDialog dialog)
-{
-    // Capture the text displayed in the dialog. The contents will be validated by the main thread.
-    dialogText = dialog.Window.AllChildren[dialog.Window.AllChildren.Count - 1].Caption;
-    Log.WriteLine("Dialog text: " + dialogText);
- 
-    Manager.Desktop.KeyBoard.KeyPress(Keys.Enter);
-    dialog.HandleCount++;
-}
-```
-```VB
-Private dialogText As String
- 
-<CodedStep("Navigate then verify text in popup dialog")> _
-Public Sub VerifyDialogText_CodedStep()
-    ActiveBrowser.NavigateTo("http://www.w3schools.com/JS/tryit.asp?filename=tryjs_alert")
- 
-    
-    Dim alertDialog__1 As AlertDialog = AlertDialog.CreateAlertDialog(ActiveBrowser, DialogButton.OK)
-    alertDialog__1.HandlerDelegate = AddressOf MyCustomAlertHandler
-    Manager.DialogMonitor.AddDialog(alertDialog__1)
- 
-    
-    Dim tryItButton As HtmlButton = ActiveBrowser.Frames("view").Find.ByTagIndex(Of HtmlButton)("button", 0)
-    Assert.IsNotNull(tryItButton)
-    tryItButton.Click()
- 
-    
-    alertDialog__1.WaitUntilHandled(5000)
- 
-    
-    Assert.AreEqual(Of String)("I am an alert box!", dialogText)
-End Sub
- 
-Public Sub MyCustomAlertHandler(dialog As IDialog)
-    
-    dialogText = dialog.Window.AllChildren(dialog.Window.AllChildren.Count - 1).Caption
-    Log.WriteLine(Convert.ToString("Dialog text: ") & dialogText)
- 
-    Manager.Desktop.KeyBoard.KeyPress(Keys.Enter)
-    dialog.HandleCount += 1
-End Sub
-```
-
-
-Ensure you add the following *using or Imports* statements to the top of the code-behind file. Click the **View Entire Code Behind File** button, scroll to the top of the code, and add these lines:
-
-```C#
-using ArtOfTest.WebAii.Win32.Dialogs;
-using System.Windows.Forms;
-```
-```VB
-Imports ArtOfTest.WebAii.Win32.Dialogs
-Imports System.Windows.Forms
-```
-
diff --git a/docs/advanced-topics/coded-samples/html/verify-sort-order-html.md b/docs/advanced-topics/coded-samples/html/verify-sort-order-html.md
index 301acdc0..e83e73cb 100644
--- a/docs/advanced-topics/coded-samples/html/verify-sort-order-html.md
+++ b/docs/advanced-topics/coded-samples/html/verify-sort-order-html.md
@@ -1,21 +1,21 @@
 ---
 title: Verify Sort Order
 page_title: Verify Sort Order
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to verify the sort order of an HTML table column in Test Studio using C#. This guide provides a coded solution to ensure data is sorted correctly during automated testing."
 previous_url: /user-guide/code-samples/html/verify-sort-order.aspx, /user-guide/code-samples/html/verify-sort-order
 position: 1
 ---
-#Verify Sort Order in an HTML Table#
+# Verify Sort Order in an HTML Table
 
 *I would like to sort a column in an HTML Table and verify the content is in the correct order.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. The example below is against this <a href="http://demos.telerik.com/aspnet-mvc/grid/index" target="_blank">Telerik demo site</a>.
  
 Let's verify the first column, Order ID, is in sequential order:
 
-```C#
+````C#
 //Get the table.
 HtmlTable table = Find.ByExpression<HtmlTable>("id=Grid", "|", "tagIndex=table:1");
  
@@ -43,8 +43,8 @@ for (int j = 0; j < list.Count; j++)
         Assert.IsTrue(list[j+1].CompareTo(list[j]) >= 0);
     }
 }
-```
-```VB
+````
+````VB
 Dim table As HtmlTable = Find.ByExpression(Of HtmlTable)("id=Grid", "|", "tagIndex=table:1")
  
 Dim r As Integer = table.Rows.Count
@@ -66,4 +66,4 @@ For j As Integer = 0 To list.Count - 1
         Assert.IsTrue(list(j + 1).CompareTo(list(j)) >= 0)
     End If
 Next
-```
+````
diff --git a/docs/advanced-topics/coded-samples/html/verify-style.md b/docs/advanced-topics/coded-samples/html/verify-style.md
index 7f15ad13..b9023e62 100644
--- a/docs/advanced-topics/coded-samples/html/verify-style.md
+++ b/docs/advanced-topics/coded-samples/html/verify-style.md
@@ -1,21 +1,21 @@
 ---
 title: Verify Style
 page_title: Verify Style
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to verify and extract HTML element styles in Test Studio using C# and VB.NET. This guide provides a coded solution for style verification and data extraction to enhance automated testing workflows."
 previous_url: /user-guide/code-samples/html/verify-style.aspx, /user-guide/code-samples/html/verify-style
 position: 1
 ---
-#Verify HTML Style#
+# Verify HTML Style
 
 *I would like to verify an HTML element's style and extract it for use later in the test.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. First, be aware that if you're simply verifying a style, that can be accomplished without code using an <a href="/features/verifications/advanced-verification" target="_blank">Advanced Verification</a>.
 
 The example below is against <a href="http://www.w3schools.com/html/tryit.asp?filename=tryhtml_styles_font-family" target="_blank">this W3Schools site</a>. Two styles are verified, retrieved as strings, and set as <a href="/advanced-topics/coded-samples/general/extracted-variables-in-code" target="_blank">extracted values</a> to use later in the test through data binding (either attached to an <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">input value</a> or a <a href="/features/data-driven-testing/attach-columns-verifications" target="_blank">verification</a>).
 
-```C#
+````C#
 Browser frame = ActiveBrowser.Frames["view"];
 HtmlControl paragraph = frame.Find.ByTagIndex<HtmlControl>("p", 0);
 Assert.IsNotNull(paragraph);
@@ -30,8 +30,8 @@ SetExtractedValue("colorVar", color);
  
 paragraph.AssertStyle().Font(HtmlStyleFont.Family, "verdana", HtmlStyleType.Computed, StringCompareType.Exact);
 paragraph.AssertStyle().ColorAndBackground(HtmlStyleColorAndBackground.Color, "#FF0000", HtmlStyleType.Computed, StringCompareType.Exact);
-```
-```VB
+````
+````VB
 Dim frame As Browser = ActiveBrowser.Frames("view")
 Dim paragraph As HtmlControl = frame.Find.ByTagIndex(Of HtmlControl)("p", 0)
 Assert.IsNotNull(paragraph)
@@ -46,4 +46,4 @@ SetExtractedValue("colorVar", color)
  
 paragraph.AssertStyle().Font(HtmlStyleFont.Family, "verdana", HtmlStyleType.Computed, StringCompareType.Exact)
 paragraph.AssertStyle().ColorAndBackground(HtmlStyleColorAndBackground.Color, "#FF0000", HtmlStyleType.Computed, StringCompareType.Exact)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/samples/use-external-dll/MultiprojectSample.zip b/docs/advanced-topics/coded-samples/samples/use-external-dll/MultiprojectSample.zip
old mode 100644
new mode 100755
diff --git a/docs/advanced-topics/coded-samples/silverlight/change-find-strategy.md b/docs/advanced-topics/coded-samples/silverlight/change-find-strategy.md
deleted file mode 100644
index a82a44d7..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/change-find-strategy.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Change Find Strategy
-page_title:  Change Find Strategy
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/change-find-strategy.aspx, /user-guide/code-samples/silverlight/change-find-strategy
-position: 1
----
-#Change Silverlight Find Strategy#
-
-The default behavior of Test Studio and the Telerik Testing Framework is to time out after a certain interval if the element is not found.
- 
-*I would like to avoid the Timeout Exception and perform a different set of steps depending on whether the element is found.*
-
-##Solution##
-
-This is possible with a coded solution. Change the SilverlightApp or any FrameworkElement VisualFind.Strategy value to WhenNotVisibleReturnNull.
-
-The example below is against this <a href="http://www.silverlight.net/content/samples/sl4/toolkitcontrolsamples/run/default.html" target="_blank">Silverlight demo site</a>. After navigating there, click DataGrid in the left-hand menu. Then add a coded step:
-
-```C#
-SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
-FindStrategy originalStrategy = app.Find.Strategy;
- 
-try
-{
-    app.Find.Strategy = FindStrategy.WhenNotVisibleReturnNull;
-    string gridName = "dataGrid";
-    DataGrid grid = app.Find.ByName<DataGrid>(gridName);
-     
-    if (grid != null)
-    {
-        grid.Wait.ForVisible();
-        //Perform actions on the DataGrid
-    }
-    else   
-    {
-        //You can throw an exception, or perform alternative steps
-        throw new ArgumentException(string.Format("Unable to find the DataGrid named '{0}'!", gridName));
-    }
-}
-finally
-{
-    app.Find.Strategy = originalStrategy;
-}
-```
-
-```VB
-Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
-Dim originalStrategy As FindStrategy = app.Find.Strategy
- 
-Try
-    app.Find.Strategy = FindStrategy.WhenNotVisibleReturnNull
-    Dim gridName As String = "dataGrid"
-    Dim grid As DataGrid = app.Find.ByName(Of DataGrid)(gridName)
- 
-    If grid IsNot Nothing Then
-       
-        grid.Wait.ForVisible()
-    Else
-       
-        Throw New ArgumentException(String.Format("Unable to find the DataGrid named '{0}'!", gridName))
-    End If
-Finally
-    app.Find.Strategy = originalStrategy
-End Try
-```
-
-**Note:** As is, the IF portion is executed. You can disable step two (treeview item 'DataGrid' select action) to see the ELSE portion execute.
diff --git a/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-all-text.md b/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-all-text.md
deleted file mode 100644
index 585c4dbe..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-all-text.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Verify All Text
-page_title: Verify All Text
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-#Verify All Text in a Silverlight ComboBox#
-
-This is possible with a coded solution:
-
-```C#
-ComboBox cb = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox;
- 
-string full = cb.TextBlockContent.ToString();
-full = full.Trim();
- 
-Log.WriteLine(full);
-Assert.AreEqual(full, "All Add Delete Edit Navigation None");
-```
-
-```VB
-Dim cb As ComboBox = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox
- 
-Dim full As String = cb.TextBlockContent.ToString()
-full = full.Trim()
- 
-Log.WriteLine(full)
-Assert.AreEqual(full, "All Add Delete Edit Navigation None")
-```
-
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-specific-text.md b/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-specific-text.md
deleted file mode 100644
index 284210eb..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/combobox-automation/verify-specific-text.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Verify Specific Text
-page_title: Verify Specific Text
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-#Verify Silverlight ComboBox Contains Specific Text#
-
-I would like to iterate through a Silverlight ComboBox and verify that it contains specific text strings.
-
-##Solution##
-
-This is possible with a coded solution:
-
-```C#
-ComboBox cb = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox;
-bool found = cb.TextBlockContent.Contains(Data["Col1"].ToString());
- 
-Log.WriteLine("Match found: " + found.ToString());
-Assert.IsTrue(found);
-```
-
-```VB
-Dim cb As ComboBox = Pages.SilverlightToolkitSamples.SilverlightApp.Item0Combobox
-Dim found As Boolean = cb.TextBlockContent.Contains(Data("Col1").ToString())
- 
-Log.WriteLine("Match found: " + found.ToString())
-Assert.IsTrue(found)
-```
\ No newline at end of file
diff --git a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/go-through-all-grid-cells.md b/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/go-through-all-grid-cells.md
deleted file mode 100644
index 5b607841..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/go-through-all-grid-cells.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Go Through All Grid Cells
-page_title: Go Through All Grid Cells
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/radgridview/go-through-cells.aspx, /user-guide/code-samples/silverlight/radgridview/go-through-cells
-position: 1
----
-## Welcome to Test Studio##
-
-*I'd like to go through each cell in a Silverlight RadGridView in order to perform some action or verification.*
-
-##Solution##
-
-This is possible with a coded solution. Here's an example:
-
-Because of the dynamic nature of the Grid control, it's not practical to record a "static" test (i.e. with pre-recorded regular steps) because any changes in the Grid content can cause the test to fail. The sample project attached to the end of this article contains two tests:
-
-* **GoThroughAllCellsInGrid**
-
-* **GoThroughAllVisibleCells**
-
-The first test uses code to go through all the visible cells in the grid (as opposed to all the cells contained within the grid) in a <a href="http://demos.telerik.com/silverlight/#DataVirtualization/FirstLook" target="_blank">Silverlight Demo</a>. It writes the text content of each cell into the test log. You can modify the logic in order to implement another type of verification against the text content. Below is the coded step that does this. Keep in mind that when working with Silverlight in coded steps in Test Studio, you'll need to set the test to Enable Silverlight = true in order to run it from Quick Execution:
-
-![SL enabled][1]
-
-The code can be resued in a Telerik Testing Framework test, but you'll need to add the following line of code:
-
-```
-Settings.Current.Web.EnableSilverlight = true;
-```
-
-```C#
-SilverlightApp app = ActiveBrowser.SilverlightApps()[0]; //Get Silverlight app              
-  
-Telerik.WebAii.Controls.Xaml.RadGridView rgv = app.Find.ByType<Telerik.WebAii.Controls.Xaml.RadGridView>(); //Get RadGrid
-int rowCounter = 1;
-  
-foreach (Telerik.WebAii.Controls.Xaml.GridViewRow gRow in rgv.Rows) { //Loop to go through all the rows
-      
-  Log.WriteLine("<-------------Start of row "+rowCounter.ToString()+"------------->"); //Write row number to log
-      
-  int cellCounter = 1;  
-    foreach(Telerik.WebAii.Controls.Xaml.GridViewCell gCell in gRow.Cells) { //Nested loop; Goes through all the cells within each row
-          
-     Log.WriteLine("Cell "+ cellCounter.ToString()+": "+gCell.Text);   //We output the cell text to the log; 
-        //You can implement any type of verification you like against the text here
-          
-        cellCounter++;
-    }
-    rowCounter++;
-}
-```
-```VB
-Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
-'Get Silverlight app              
-Dim rgv As Telerik.WebAii.Controls.Xaml.RadGridView = app.Find.ByType(Of Telerik.WebAii.Controls.Xaml.RadGridView)()
-
-Dim rowCounter As Integer = 1
-  
-For Each gRow As Telerik.WebAii.Controls.Xaml.GridViewRow In rgv.Rows
-    
-    Log.WriteLine("<-------------Start of row " + rowCounter.ToString() + "------------->")
-
-    Dim cellCounter As Integer = 1
-    For Each gCell As Telerik.WebAii.Controls.Xaml.GridViewCell In gRow.Cells
-         Log.WriteLine("Cell " + cellCounter.ToString() + ": " + gCell.Text)
-         cellCounter += 1
-    Next
-    rowCounter += 1
-Next
-```
-
-The second test, **GoThroughAllCellsInGrid**, scrolls through the Grid and goes through all its cells, not just the ones that are currently visible. Basically it combines the above code with the code from <a href="/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling" target="_blank">this article</a>.
-
-* Download the <a href="http://docs.telerik.com/teststudio/demoslibrary/RADGridViewAutomation_C.zip">C# project</a>.
-
-[1]: /img/advanced-topics/coded-samples/silverlight/radgridview-automation/go-through-all-grid-cells/fig1.png
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling-paging.md b/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling-paging.md
deleted file mode 100644
index 1488d100..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling-paging.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Scrolling & Paging
-page_title: Scrolling & Paging
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/radgridview/find-element-scrolling-and-paging.aspx, /user-guide/code-samples/silverlight/radgridview/find-element-scrolling-and-paging
-position: 1
----
-#RadGridView Scrolling & Paging #
-
-I have a lot of data contained in a RadGridView with scrolling and paging. I need to find a specific element in the Grid. To find it, I need to scroll down through the entire GridView and go through every page verifying the data.
-
-![Paging][1]
-
-##Solution##
-
-This is possible with a coded solution. To accomplish the main goal, we need to combine the solutions of the two sub-problems (Scrolling and Paging) seen here and here. We need to take the following steps to implement the solution:
-
-1. Change the default <a href="/advanced-topics/coded-samples/silverlight/change-find-strategy" target="_blank">Find Strategy</a> of the Grid to *WhenNotVisibleReturnNull*, otherwise the Find method will return a *FindElementException* if the element is not found.
-
-2. Scroll down to the bottom of the Grid.
-
-3. Go through the Grid page by page, repeating step two until the desired element is found
-
-The following code demonstrates how to accomplished this on a <a href="http://demos.telerik.com/silverlight/#GridView/PagingLargeData" target="_blank">Telerik demo site</a>.
-
-```C#
-public FrameworkElement FindElementByTextContent(string content)
-{
-    int extentHeight; // The total height of the grid, visible plus non-visible     
-    int rowHeight; // The height of the row
-    int viewPortHeight; // The height of the visible part of the grid
-    int verticalOffset = 0; // Holds the current vertical offset in the viewport
-     
-    // Copy the RadGridView into a local variable as a shortcut
-    RadGridView grid = Pages.TelerikGridViewFor.SilverlightApp.GridViewRadgridview;
-     
-    // Grab the VirtualizingPanel contained in the RadGridView. This is used to control the viewable portion of the grid.
-    FrameworkElement VirtualizingPanel = grid.Find.ByType("GridViewVirtualizingPanel");
-     
-    // Detect the extent height, view port height and the row height
-    extentHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ExtentHeight", typeof(int)));
-    rowHeight = (int)grid.GetProperty(new AutomationProperty("RowHeight", typeof(int)));
-    viewPortHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ViewportHeight", typeof(int)));
-     
-    //Save the original find Find Strategy
-    FindStrategy originalStrategy = grid.Find.Strategy;
-     
-    //Change the Find Strategy for the RadGridView
-    grid.Find.Strategy = FindStrategy.WhenNotVisibleReturnNull;
-     
-    // Scroll through each RadGridView page until the element is found or until the "Next Page" is no longer Enabled  
-    do
-    {
-        verticalOffset = 0;
-        VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0);
-        while (verticalOffset < extentHeight)
-        {          
-                FrameworkElement fe = grid.Find.ByTextContent(content);
-                if(fe != null)
-                {  
-                    //Return the original strategy
-                    grid.Find.Strategy = originalStrategy;
-                     
-                    //Return the element
-                    return fe;
-                }
-                
-                verticalOffset += viewPortHeight;
-                VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset); 
-          
-        }
-        Pages.TelerikGridViewFor.SilverlightApp.MoveToNextPageButtonRadbutton.User.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick);
-    }
-    while(Pages.TelerikGridViewFor.SilverlightApp.MoveToNextPageButtonRadbutton.IsEnabled);
-     
-    //Return the original strategy
-    grid.Find.Strategy = originalStrategy;
-    return null;
-}
-```
-
-```VB
-Public Function FindElementByTextContent(content As String) As FrameworkElement
-    
-    Dim extentHeight As Integer
-    
-    Dim rowHeight As Integer
-   
-    Dim viewPortHeight As Integer
-    
-    Dim verticalOffset As Integer = 0
- 
-    
-    Dim grid As RadGridView = Pages.TelerikGridViewFor.SilverlightApp.GridViewRadgridview
- 
-    
-    Dim VirtualizingPanel As FrameworkElement = grid.Find.ByType("GridViewVirtualizingPanel")
- 
-    
-    extentHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ExtentHeight", GetType(Integer))))
-    rowHeight = CInt(grid.GetProperty(New AutomationProperty("RowHeight", GetType(Integer))))
-    viewPortHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ViewportHeight", GetType(Integer))))
- 
-    
-    Dim originalStrategy As FindStrategy = grid.Find.Strategy
- 
-    
-    grid.Find.Strategy = FindStrategy.WhenNotVisibleReturnNull
- 
-    
-    Do
-        verticalOffset = 0
-        VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0)
-        While verticalOffset < extentHeight
-            Dim fe As FrameworkElement = grid.Find.ByTextContent(content)
-            If fe IsNot Nothing Then
-                
-                grid.Find.Strategy = originalStrategy
- 
-                
-                Return fe
-            End If
- 
-            verticalOffset += viewPortHeight
- 
-            VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset)
-        End While
-        Pages.TelerikGridViewFor.SilverlightApp.MoveToNextPageButtonRadbutton.User.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick)
-    Loop While Pages.TelerikGridViewFor.SilverlightApp.MoveToNextPageButtonRadbutton.IsEnabled
- 
-    
-    grid.Find.Strategy = originalStrategy
-    Return Nothing
-End Function
-```
-
-
-Place this in the code-behind and then call this method from a coded step.
-
-[1]: /img/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling-paging/fig1.png
-
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling.md b/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling.md
deleted file mode 100644
index 64e898ca..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling.md
+++ /dev/null
@@ -1,96 +0,0 @@
----
-title: Scrolling
-page_title: Scrolling
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/radgridview/scrolling.aspx, /user-guide/code-samples/silverlight/radgridview/scrolling
-position: 1
----
-#RadGridView Scrolling#
-
-> This issue can now be resolved <a href="/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel" target="_blank">without code</a>.
-
-*I need to scroll down through the entire GridView verifying the data, because currently only the rows presented in the Visual Tree can be tested.*
-
-##Solution##
-
-This is a limitation of the Visual Tree contained in the Silverlight engine. Silverlight puts into the Visual Tree only the UI components necessary to render the page on the screen.
- 
-Here is an example. Let's say you have a grid that holds 100 rows of data but can only display 20 at a time. Silverlight typically will only put 22 rows of UI elements in the Visual Tree (20 visible plus one above and one below). The only way to get all 100 rows is to scroll down through the entire grid. 
- 
-The following code demonstrates how to accomplished this on a <a href="http://demos.telerik.com/silverlight/#GridView/UIVirtualization" target="_blank">Telerik demo page</a>.
-
-```C#
-int verticalOffset = 0; // Holds the current vertical offset in the viewport
-int viewPortHeight; // The height of the visible part of the grid
-int extentHeight; // The total height of the grid, visible plus non-visible
-
-// Copy the RadGridView into a local variable as a shortcut
-RadGridView grid = Pages.TelerikGridViewFor.SilverlightApp.RadGridView1Radgridview;
-// Grab the VirtualizingPanel contained in the RadGridView. This is used to control the viewable portion of the grid.
-FrameworkElement VirtualizingPanel = grid.Find.ByType("GridViewVirtualizingPanel");
-
-// Detect the view port height and the extent height
-viewPortHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ViewportHeight", typeof(int)));
-extentHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ExtentHeight", typeof(int)));
-
-Dictionary<string, int> rowsHash = new Dictionary<string, int>();
-// Make sure it is scrolled to the very top
-// Walk through the entire grid verifying the data
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0);
-int rowNum = 0;
-while (verticalOffset < extentHeight)
-{
-grid.Refresh();
-	foreach (GridViewRow r in grid.Rows)
-	{
-	string rowId = r.Cells[2].Text;
-		if (!rowsHash.Keys.Contains(rowId))
-			{
-				rowsHash.Add(rowId, rowNum++);
-				Console.WriteLine(r.Cells[0].Text + ", " + r.Cells[1].Text + ", " + r.Cells[2].Text + ", " + r.Cells[3].Text + ", " + r.Cells[4].Text + ", " + r.Cells[5].Text + ", " + r.Cells[6].Text);
-			}
-    }
-// Scroll down one page
-verticalOffset += viewPortHeight;
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset);
-}
-```
-
-```VB
-
-Dim verticalOffset As Integer = 0
-' Holds the current vertical offset in the viewport
-Dim viewPortHeight As Integer
-' The height of the visible part of the grid
-Dim extentHeight As Integer
-' The total height of the grid, visible plus non-visible
-' Copy the RadGridView into a local variable as a shortcut
-Dim grid As RadGridView = Pages.TelerikGridViewFor.SilverlightApp.RadGridView1Radgridview
-' Grab the VirtualizingPanel contained in the RadGridView. This is used to control the viewable portion of the grid.
-Dim VirtualizingPanel As FrameworkElement = grid.Find.ByType("GridViewVirtualizingPanel")
-
-' Detect the view port height and the extent height
-viewPortHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ViewportHeight", GetType(Integer))))
-extentHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ExtentHeight", GetType(Integer))))
-
-Dim rowsHash As New Dictionary(Of String, Integer)()
-' Make sure it is scrolled to the very top
-' Walk through the entire grid verifying the data
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0)
-Dim rowNum As Integer = 0
-While verticalOffset < extentHeight
-grid.Refresh()
-For Each r As GridViewRow In grid.Rows
-Dim rowId As String = r.Cells(2).Text
-If Not rowsHash.Keys.Contains(rowId) Then
-rowsHash.Add(rowId, System.Math.Max(System.Threading.Interlocked.Increment(rowNum),rowNum - 1))
-Console.WriteLine(r.Cells(0).Text + ", " + r.Cells(1).Text + ", " + r.Cells(2).Text + ", " + r.Cells(3).Text + ", " + r.Cells(4).Text + ", " + r.Cells(5).Text + ", " + r.Cells(6).Text)
-End If
-Next
-' Scroll down one page
-verticalOffset += viewPortHeight
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset)
-End While
-```
-
-Due to the volume of data contained in the sample RadGridView, this test will take hours to run through it all. But it shows all the necessary steps.  
diff --git a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/total-rows-count.md b/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/total-rows-count.md
deleted file mode 100644
index d5f5f0c5..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/total-rows-count.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Total Rows Count
-page_title: Total Rows Count
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/radgridview/total-rows-count.aspx, /user-guide/code-samples/silverlight/radgridview/total-rows-count
-position: 1
----
-#RadGridView Total Rows Count #
-
-*I need to get the total number of rows contained in a RadGridView. The Rows.Count property of the RadGridView only returns the number of rows on the current page.*
-
-##Solution##
-
-The only way to get the total rows count is by calculating the number of rows per page and adding them to the running total.
-
-The following code demonstrates how to get the rows count of the RadGridView shown on this <a href="http://demos.telerik.com/silverlight/#GridView/PagingLargeData" target="_blank">Telerik demo site</a>. We use a Do/While loop in code which exits once the "Next Page" button is no longer Enabled. Then the row count is performed once more to account for the last page.
-
-```C#
-int extentHeight; // The total height of the grid, visible plus non-visible
-int rowHeight; // The height of the row
-  
-// Copy the RadGridView into a local variable as a shortcut
-RadGridView grid = Pages.TelerikGridViewFor2.SilverlightApp.GridViewRadgridview;
-  
-// Grab the VirtualizingPanel contained in the RadGridView. This is used to control the viewable portion of the grid.
-FrameworkElement VirtualizingPanel = grid.Find.ByType("GridViewVirtualizingPanel");
-  
-// Detect the extent height and the row height
-extentHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ExtentHeight", typeof(int)));
-rowHeight = (int)grid.GetProperty(new AutomationProperty("RowHeight", typeof(int)));
-  
-int totalPageRows = 0;    
-int totalOverallRows = 0;
-// Calculate the total overall rows until the "Next Page" is no longer Enabled 
-do
-{
-totalPageRows = (extentHeight/rowHeight);
-totalOverallRows = totalPageRows + totalOverallRows;
-      
-Pages.TelerikGridViewFor2.SilverlightApp.MoveToNextPageButtonRadbutton.User.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick);
-}
-while(Pages.TelerikGridViewFor2.SilverlightApp.MoveToNextPageButtonRadbutton.IsEnabled);
-  
-totalPageRows = (extentHeight/rowHeight);
-totalOverallRows = totalPageRows + totalOverallRows;
-  
-// Show the result
-Log.WriteLine("Total Number of Rows: "+ totalOverallRows.ToString());
-```
-
-```VB
-Dim extentHeight As Integer
-
-Dim rowHeight As Integer
-
-
-Dim grid As RadGridView = Pages.TelerikGridViewFor2.SilverlightApp.GridViewRadgridview
- 
-
-Dim VirtualizingPanel As FrameworkElement = grid.Find.ByType("GridViewVirtualizingPanel")
- 
-
-extentHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ExtentHeight", GetType(Integer))))
-rowHeight = CInt(grid.GetProperty(New AutomationProperty("RowHeight", GetType(Integer))))
- 
-Dim totalPageRows As Integer = 0
-Dim totalOverallRows As Integer = 0
- 
-Do
-    totalPageRows = (extentHeight / rowHeight)
-    totalOverallRows = totalPageRows + totalOverallRows
- 
-    Pages.TelerikGridViewFor2.SilverlightApp.MoveToNextPageButtonRadbutton.User.Click(ArtOfTest.WebAii.Core.MouseClickType.LeftClick)
-Loop While Pages.TelerikGridViewFor2.SilverlightApp.MoveToNextPageButtonRadbutton.IsEnabled
- 
-totalPageRows = (extentHeight / rowHeight)
-totalOverallRows = totalPageRows + totalOverallRows
- 
-
-Log.WriteLine("Total Number of Rows: " + totalOverallRows.ToString())
-```
diff --git a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/verify-specific-column.md b/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/verify-specific-column.md
deleted file mode 100644
index 2a2816c5..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/radgridview-automation/verify-specific-column.md
+++ /dev/null
@@ -1,109 +0,0 @@
----
-title: Verify Specific Column
-page_title: Verify Specific Column
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/radgridview/verify-data-in-specific-column.aspx, /user-guide/code-samples/silverlight/radgridview/verify-data-in-specific-column
-position: 1
----
-#RadGridView Verify Data in a Specific Column#
-
-*I need to find the correct column of a GridView based on something other than index, such as text content or a data driven variable.*
-
-
-##Solution##
-
-Here is how to accomplish this on a <a href="http://demos.telerik.com/silverlight/#GridView/Totals" target="_blank">Telerik demo site</a>.. First you need to retrieve all the Header Row Cells from the Grid and iterate through each one looking for a specific string. Each time it isn't found, the integer idx is increased by one. Once a match is made, idx will equal the index of the target column. Then you can use that integer to identify the column later:
-
-```C#
-int verticalOffset = 0; // Holds the current vertical offset in the viewport
-int viewPortHeight; // The height of the visible part of the grid
-int extentHeight; // The total height of the grid, visible plus non-visible
-  
-// Copy the RadGridView into a local variable as a shortcut
-RadGridView grid = Pages.TelerikGridViewFor1.SilverlightApp.RadGridView1Radgridview;
-  
-// Grab the VirtualizingPanel contained in the RadGridView. This is used to control the viewable portion of the grid.
-FrameworkElement VirtualizingPanel = grid.Find.ByType("GridViewVirtualizingPanel");
-  
-// Detect the view port height and the extent height
-viewPortHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ViewportHeight", typeof(int)));
-extentHeight = (int)VirtualizingPanel.GetProperty(new AutomationProperty("ExtentHeight", typeof(int)));
-   
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0);
-  
-//get the Header Row Cells and iterate through them
-IList<GridViewHeaderCell> headers = grid.HeaderRow.HeaderCells;
-int idx = 0; 
-foreach(GridViewHeaderCell header in headers)
-{
-      //Instead of a sting (here it's "Unit Price"), you can use a variable
-      if(header.Text.Equals("Unit Price", StringComparison.CurrentCultureIgnoreCase))  
-      {
-          break;
-      }
-      idx++; 
-}
-Assert.IsTrue(idx < headers.Count, string.Format("Column {0} not found", "Unit Price"));
-      
-// Walk through the entire grid verifying the data
-while (verticalOffset < extentHeight)
-{
-      foreach (GridViewRow r in grid.Rows)
-      {
-            //Here the integer "idx" is used in place of the actual index number 
-            Assert.AreEqual<string>(Data["State"].ToString(), r.Cells[idx].Text.Substring(0,1));
-      }
-  
-      // Scroll down one page
-      verticalOffset += viewPortHeight;
-      VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset);
-}
-```
-
-```VB
-
-Dim verticalOffset As Integer = 0
-
-Dim viewPortHeight As Integer
-
-Dim extentHeight As Integer
-  
-
-Dim grid As RadGridView = Pages.TelerikGridViewFor1.SilverlightApp.RadGridView1Radgridview
-  
-
-Dim VirtualizingPanel As FrameworkElement = grid.Find.ByType("GridViewVirtualizingPanel")
-  
-
-viewPortHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ViewportHeight", GetType(Integer))))
-extentHeight = CInt(VirtualizingPanel.GetProperty(New AutomationProperty("ExtentHeight", GetType(Integer))))
-  
-VirtualizingPanel.InvokeMethod("SetVerticalOffset", 0)
-  
-
-Dim headers As IList(Of GridViewHeaderCell) = grid.HeaderRow.HeaderCells
-Dim idx As Integer = 0
-For Each header As GridViewHeaderCell In headers
-    'Instead of a sting (here it's "Unit Price"), you can use a variable
-    If header.Text.Equals("Unit Price", StringComparison.CurrentCultureIgnoreCase) Then
-        Exit For
-    End If
-    idx += 1
-Next
-Assert.IsTrue(idx < headers.Count, String.Format("Column {0} not found", "Unit Price"))
-  
-
-While verticalOffset < extentHeight
-    For Each r As GridViewRow In grid.Rows
-        'Here the integer "idx" is used in place of the actual index number 
-        Assert.AreEqual(Of String)(Data("State").ToString(), r.Cells(idx).Text.Substring(0, 1))
-    Next
-  
-    
-    verticalOffset += viewPortHeight
-    VirtualizingPanel.InvokeMethod("SetVerticalOffset", verticalOffset)
-End While
-```
-
-
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/select-listbox-item-by-text.md b/docs/advanced-topics/coded-samples/silverlight/select-listbox-item-by-text.md
deleted file mode 100644
index 2d9116cb..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/select-listbox-item-by-text.md
+++ /dev/null
@@ -1,151 +0,0 @@
----
-title: Select Listbox Item by Text
-page_title: Select Listbox Item by Text
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/select-listbox-item-by-text.aspx, /user-guide/code-samples/silverlight/select-listbox-item-by-text
-position: 1
----
-#Select Listbox Item by Text in Silverlight#
-
-
-*I have a listbox contained in my Silverlight application. I want to be able to find and select an item contained in the listbox by its text, not by its index. I can't use select by index because the position of the item that needs to be selected may change at any time.*
-
-##Solution##
-
-This is a tricky one to solve. There are two subtle problems that need to be dealt with before accomplishing the end goal:
-
-1. Silverlight loves to virtualize data contained in data containers such as a listbox. This means the Silverlight visual tree only contains the data necessary to render the UI. Let's assume your list box shows 5 items at a time. Even though your list box may contain 100 items, the visual tree will only contain 6 or 7 items at a time in it. To further complicate this, after scrolling down so you can see items 50 to 55, the visual tree will only contain something like items 50 to 56, not 1 to 56.
-
-2. The ScrollToVisible function doesn't scroll data containers, only the browser window. We'll have to come up with a different method of scrolling the list box.
-
-The solution is to use this approach in a **loop**:
-
-1. Scan what is currently in the Silverlight visual tree looking for the right item.
-
-2. If not found, scroll the contents of the listbox down by one page of data and repeat the scan.
-
-3. When the item is found, scroll it to the top of list box so we can reliably click on it to select it.
-
-My sample Silverlight application to test contains this XAML code to render my listbox:
-
-```XAML
-<ListBox AutomationProperties.AutomationId="lb001" Height="117" HorizontalAlignment="Left" Margin="23,102,0,0" Name="listBox1" VerticalAlignment="Top" Width="281">
-    <ListBoxItem Content="Item 1" />
-    <ListBoxItem Content="Item 2" />
-    <ListBoxItem Content="Item 3" />
-    <ListBoxItem Content="Item 4" />
-    <ListBoxItem Content="Item 5" />
-    <ListBoxItem Content="Item 6" />
-    <ListBoxItem Content="Item 7" />
-    <ListBoxItem Content="Item 8" />
-    <ListBoxItem Content="Item 9" />
-    <ListBoxItem Content="Item 10" />
-    <ListBoxItem Content="Item 11" />
-    <ListBoxItem Content="Item 12" />
-    <ListBoxItem Content="Item 13" />
-    <ListBoxItem Content="Item 14" />
-    <ListBoxItem Content="Item 15" />
-    <ListBoxItem Content="Item 16" />
-    <ListBoxItem Content="Item 17" />
-    <ListBoxItem Content="Item 18" />
-    <ListBoxItem Content="Item 19" />
-    <ListBoxItem Content="Item 20" />
-    <ListBoxItem Content="Item 21" />
-    <ListBoxItem Content="Item 22" />
-    <ListBoxItem Content="Item 23" />
-    <ListBoxItem Content="Item 24" />
-    <ListBoxItem Content="Item 25" />
-    <ListBoxItem Content="Item 26" />
-    <ListBoxItem Content="Item 27" />
-    <ListBoxItem Content="Item 28" />
-    <ListBoxItem Content="Item 29" />
-    <ListBoxItem Content="Item 30" />
-    <ListBoxItem Content="Item 31" />
-    <ListBoxItem Content="Item 32" />
-    <ListBoxItem Content="Item 33" />
-    <ListBoxItem Content="Item 34" />
-    <ListBoxItem Content="Item 35" />
-    <ListBoxItem Content="Item 36" />
-    <ListBoxItem Content="Item 37" />
-    <ListBoxItem Content="Item 38" />
-    <ListBoxItem Content="Item 39" />
-    <ListBoxItem Content="Item 40" />
-    <ListBoxItem Content="Item 41" />
-    <ListBoxItem Content="Item 42" />
-    <ListBoxItem Content="Item 43" />
-    <ListBoxItem Content="Item 44" />
-    <ListBoxItem Content="Item 45" />
-    <ListBoxItem Content="Item 46" />
-    <ListBoxItem Content="Item 47" />
-    <ListBoxItem Content="Item 48" />
-    <ListBoxItem Content="Item 49" />
-    <ListBoxItem Content="Item 50" />
-    <ListBoxItem Content="Item 51" />
-    <ListBoxItem Content="Item 52" />
-    <ListBoxItem Content="Item 53" />
-    <ListBoxItem Content="Item 54" />
-    <ListBoxItem Content="Item 55" />
-    <ListBoxItem Content="Item 56" />
-    <ListBoxItem Content="Item 57" />
-    <ListBoxItem Content="Item 58" />
-    <ListBoxItem Content="Item 59" />
-</ListBox>
-```
-
-To help make the code necessary to accomplish our search task more modular, let's define a function that takes a listbox, a string to search for and finds and returns the listbox item want. Here is that function:
-
-```C#
-private static ListBoxItem FindListboxItemByText
-    (string itemToFind, ListBox myLB)
-{
-    // We may have to scroll the list box to find the item we want, so get the scroll viewer attached to the listbox
-    ScrollViewer scroller = myLB.Find.ByType<ScrollViewer>();
-    IList<ListBoxItem> items;
-    double scrollPos = 0;
- 
-    do
-    {
-        // Get all list box items currently contained in the visual tree
-        items = myLB.Find.AllByType<ListBoxItem>();
- 
-        // Iterate through each list box item looking for the one we want
-        for (int i = 0; i < items.Count; i++)
-        {
-            if (items[i].Text.Equals(itemToFind))
-            {
-               // We found the one we want. Scroll it to the top (in case it's outside the listbox's viewport) then return it to the caller.
-                scroller.InvokeMethod("ScrollToVerticalOffset", i);
-                return items[i];
-            }
-        }
- 
-        // We didn't find it, scroll down by a page worth of data to populate the VisualTree with the next page of data and try again.
-        scrollPos += scroller.ViewportHeight;
-        scroller.InvokeMethod("ScrollToVerticalOffset", scrollPos);
-        myLB.Refresh(); // Refresh our cached copy of the listbox.
-    }
-    while (scrollPos <= scroller.ExtentHeight);
- 
-    // We scanned the entire list and didn't find the right item to select.
-    return null;
-}
-```
-
-We call this resusable function from a coded step like this:
-
-
-```C#
-[CodedStep("Select a listbox item by text")]
-public void SelectListItemByTextCodedStep()
-{
-    string itemToFind = "Item 42";
- 
-    SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
-    ListBox myLB = app.Find.ByAutomationId<ListBox>("lb001");
- 
-    ListBoxItem item = FindListboxItemByText(itemToFind, myLB);
-    Assert.IsNotNull(item, "\"" + itemToFind + "\" not found in the listbox.");
-    item.User.Click();
-}
-```
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/verify-colors-in-silverlight.md b/docs/advanced-topics/coded-samples/silverlight/verify-colors-in-silverlight.md
deleted file mode 100644
index 0d3225d6..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/verify-colors-in-silverlight.md
+++ /dev/null
@@ -1,85 +0,0 @@
----
-title: Verify Colors in Silverlight
-page_title: Verify Colors in Silverlight
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-#Verify Colors in Silverlight#
-
-I would like to add a color verificaiton for an element in a Silverlight application.
-
-##Solution##
-
-The code below demonstrates this approach against this <a href="http://demos.telerik.com/silverlight/#TreeView/Performance" target="_blank">Telerik demo site</a>. It gets the first item in the menu and verifies that its foreground color macthes pre-defined values:
-
-```C#
-Manager.Settings.Web.EnableSilverlight = true; 
-Manager.LaunchNewBrowser(); 
-ActiveBrowser.NavigateTo("http://demos.telerik.com/silverlight/#TreeView/Performance"); 
-SilverlightApp app = ActiveBrowser.SilverlightApps()[0]; 
-app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy; 
-Button b = app.Find.ByAutomationId<Button>("button"); 
-b.Wait.ForExists(60000); 
-b.User.Click();
-  
-FrameworkElement installerElem = app.Find.ByTextContent("^Installer Branc"); 
-installerElem.Wait.ForExists(30000); 
-TextBlock installer= installerElem.CastAs<TextBlock>();
-Log.WriteLine(installer.Text);
-Dictionary<string, string> props = installerElem.GetProperties();
-Assert.IsTrue(props.ContainsKey("Text"));
-Log.WriteLine("Text = " + installerElem.TextContent);
-ArtOfTest.WebAii.Silverlight.UI.Brush textblockBrush = (Brush)installerElem.GetProperty(new AutomationProperty("Foreground", typeof(Brush)));
- 
-if (textblockBrush is SolidColorBrush)
-{
-    Color actualColor = ((SolidColorBrush)textblockBrush).Color;
-    Assert.AreEqual<Byte>(255, actualColor.A, "Error: alpha color does not match expected.");
-    Assert.AreEqual<Byte>(105, actualColor.B, "Error: red color does not match expected.");
-    Assert.AreEqual<Byte>(72, actualColor.G, "Error: green color does not match expected.");
-    Assert.AreEqual<Byte>(40, actualColor.R, "Error: blue color does not match expected.");
-}
-else
-{
-    // If it's not a SolidColorBrush what is it? How do we handle it?
-    throw new ApplicationException("Expecting a SolidColorBrush, but got a " + textblockBrush.GetType().ToString());
-}
-```
-
-```VB
-Manager.Settings.Web.EnableSilverlight = True
-Manager.LaunchNewBrowser()
-ActiveBrowser.NavigateTo("http://demos.telerik.com/silverlight/#TreeView/Performance")
-Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
-  
-app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy
-Dim b As Button = app.Find.ByAutomationId(Of Button)("button")
-b.Wait.ForExists(60000)  
-b.User.Click()    
-  
-Dim installerElem As FrameworkElement = app.Find.ByTextContent("^Installer Branc")
-installerElem.Wait.ForExists(30000)
-Dim installer As TextBlock = installerElem.CastAs(Of TextBlock)()
-Log.WriteLine(installer.Text)      
-  
-Dim props As Dictionary(Of String, String) = installerElem.GetProperties()
-Assert.IsTrue(props.ContainsKey("Text"))
-  
-Log.WriteLine("Text = " + installerElem.TextContent)
-  
-Dim textblockBrush As ArtOfTest.WebAii.Silverlight.UI.Brush = DirectCast(installerElem.GetProperty(New AutomationProperty("Foreground", GetType(Brush))), Brush)
-  
-If TypeOf textblockBrush Is SolidColorBrush Then
-    Dim actualColor As Color = DirectCast(textblockBrush, SolidColorBrush).Color
-    Assert.AreEqual(Of [Byte])(255, actualColor.A, "Error: alpha color does not match expected.")
-    Assert.AreEqual(Of [Byte])(105, actualColor.B, "Error: red color does not match expected.")
-    Assert.AreEqual(Of [Byte])(72, actualColor.G, "Error: green color does not match expected.")
-    Assert.AreEqual(Of [Byte])(40, actualColor.R, "Error: blue color does not match expected.")
-Else
-    Throw New ApplicationException("Expecting a SolidColorBrush, but got a " + textblockBrush.[GetType]().ToString())
-End If
-```
-
-
-
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/verify-sort-order.md b/docs/advanced-topics/coded-samples/silverlight/verify-sort-order.md
deleted file mode 100644
index c82a836f..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/verify-sort-order.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Verify Sort Order
-page_title: Verify Sort Order
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/silverlight/verify-sort-order.aspx, /user-guide/code-samples/silverlight/verify-sort-order
-position: 1
----
-#Verify Sort Order in a Silverlight DataGrid#
-
-I would like to sort a column in a Silverlight DataGrid and verify the content is in the correct order.
-
-##Solution##
-
-This is possible with a coded solution. The example below is against <a href="http://silverlight.codeplex.com/downloads/get/119862" target="_blank">a Silverlight toolkit sample</a>.
- 
-After navigating there, click DataGrid in the left-hand menu. Then click the **FirstName** column header to sort that column. Finally, add a coded step:
-
-```C#
-//Get the data grid.
-SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
-DataGrid grid = app.Find.ByAutomationId<DataGrid>("dataGrid");
- 
-int r = grid.Rows.Count;
-List<string> list = new List<string>();
- 
-//Place the TextBlock content of the FirstName cell from each row into the string list.
-for (int i = 0; i < r; i++)
-{
-    DataGridRow row = grid.Rows[i];
-    DataGridCell cell = row.Cells[2];   
-    list.Add(cell.TextBlockContent);
-    Log.WriteLine(cell.TextBlockContent);
-}
- 
-//Assert each string in the list is greater than the string before it.
-for (int j = 0; j < list.Count; j++)
-{
-    if (j+1 == list.Count)
-    {
-        break;
-    }
-    else
-    {
-        Assert.IsTrue(list[j+1].CompareTo(list[j]) >= 0);
-    }
-}
-```
-
-```VB
-
-Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
-Dim grid As DataGrid = app.Find.ByAutomationId(Of DataGrid)("dataGrid")
- 
-Dim r As Integer = grid.Rows.Count
-Dim list As New List(Of String)()
- 
-
-For i As Integer = 0 To r - 1
-    Dim row As DataGridRow = grid.Rows(i)
-    Dim cell As DataGridCell = row.Cells(2)
-    list.Add(cell.TextBlockContent)
-    Log.WriteLine(cell.TextBlockContent)
-Next
- 
-
-For j As Integer = 0 To list.Count - 1
-    If j + 1 = list.Count Then
-        Exit For
-    Else
-        Assert.IsTrue(list(j + 1).CompareTo(list(j)) >= 0)
-    End If
-Next
-```
-
-
diff --git a/docs/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox.md b/docs/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox.md
deleted file mode 100644
index 7f0299b0..00000000
--- a/docs/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Verify Text in Rich TextBox
-page_title: Verify Text in Rich TextBox
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-#Verify Text in a Silverlight RichTextBox#
-*
-I cannot verify all the text or its properties in my Silverlight RichTextBox. The contents are either not visible or each word is contained in an individual TextBlock in the Visual Tree.*
-
-##Solution##
-
-The <a href="http://msdn.microsoft.com/en-us/library/system.windows.controls.richtextbox%28v=vs.95%29.aspx" target="_blank">Silverlight RichTextBox</a> is tricky to work with. It is a "container" type of control, meaning it contains other <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.block%28v=vs.95%29.aspx" target="_blank">"block" elements</a>, usually the <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.paragraph%28v=vs.95%29.aspx" target="_blank">Paragraph</a> or <a href="http://msdn.microsoft.com/en-us/library/system.windows.documents.section%28v=vs.95%29.aspx" target="_blank">Section</a>. It is these block elements that hold the actual text displayed in the RichTextBox. Thus, to fetch the displayed text, you must enumerate through the individual blocks and fetch the text from each block element.
-
-To make matters worse, the contents of the RichTextBox may not be contained in the Silverlight Visual Tree. You have to get the Xaml property and parse the contents yourself. Here is an example. Let's assume that you have this in the XAML file for your Silverlight application:
-
-```XAML
-<RichTextBox AutomationProperties.AutomationId="richTextBox1" Name="richTextBox1" Margin="310,6,6,235">
-    <Paragraph FontSize="11" FontFamily="Portable User Interface" Foreground="#FF000000" FontWeight="Normal" FontStyle="Normal" FontStretch="Normal" TextAlignment="Left">
-        <Run FontWeight="Bold" Text="Now is the time for all good men to come to the aid of their country." />
-    </Paragraph>
-</RichTextBox>
-```
-
-
-The application will show text as shown below.
-
-![SL app][1]
-
-However in DOM Explorer all you see is this:
-
-```XAML
-<?xml version="1.0"?>
-<richtextbox Name="richTextBox1" AutomationId="richTextBox1" Uid="16157963">
-  <grid Name="RootElement" Uid="37840511">
-    <border Name="Border" Uid="34030663">
-      <border Name="MouseOverBorder" Uid="33607346">
-        <scrollviewer Name="ContentElement" AutomationId="ContentElement" Uid="63386473">
-          <border Uid="54749715">
-            <grid Uid="35909463">
-              <scrollcontentpresenter Name="ScrollContentPresenter" Uid="5020285">
-                <richtextboxview BaseType="RichTextBoxView" Uid="22985394" />
-              </scrollcontentpresenter>
-              <rectangle Uid="26673201" />
-              <scrollbar Name="VerticalScrollBar" AutomationId="VerticalScrollBar" Uid="45182569" />
-              <scrollbar Name="HorizontalScrollBar" AutomationId="HorizontalScrollBar" Uid="3989940" />
-            </grid>
-          </border>
-        </scrollviewer>
-      </border>
-    </border>
-    <border Name="DisabledVisualElement" Uid="38732217" />
-    <border Name="FocusVisualElement" Uid="13045638" />
-  </grid>
-</richtextbox>
-```
-
-Notice that there's no text in the DOM view, even though it is specified in the XAML and displayed in the application. We have to use code to fetch the XAML that the RichTextBox holds as data, then parse out the text buried in it. Here's an example:
-
-```C#
-// Fetch the XAML property of the RichTextBox
-string rtbContents = (string)Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(new AutomationProperty("Xaml", typeof(string)));
- 
-// Load it into an XmlDocument for easier parsing
-XmlDocument doc = new System.Xml.XmlDocument();
-doc.LoadXml(rtbContents);
- 
-// Find all "Run" nodes as this is where the text is buried
-XmlNodeList runNodes = doc.GetElementsByTagName("Run");
- 
-// Display the Text attribute of each run node
-foreach(XmlNode runNode in runNodes)
-{
-    Log.WriteLine(runNode.Attributes["Text"].Value);
-}
-```
-
-```VB
-Dim rtbContents As String = DirectCast(Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(New AutomationProperty("Xaml", GetType(String))), String)
-  
-Dim doc As XmlDocument = New System.Xml.XmlDocument()
-doc.LoadXml(rtbContents)
-  
-Dim runNodes As XmlNodeList = doc.GetElementsByTagName("Run")
-  
-For Each runNode As XmlNode In runNodes
-    Log.WriteLine(runNode.Attributes("Text").Value)
-Next
-```
-
-Here's how to verify the text is bold:
-
-```C#
-string rtbContents = (string)Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(new AutomationProperty("Xaml", typeof(string)));
-Log.WriteLine(rtbContents);
-  
-// Load the RTB contents into an XElement for parsing
-XElement xElem = XElement.Parse(rtbContents);
- 
-// Find the <Run node.
-XElement runElem = xElem.Descendants().First((e) => "Run".Equals(e.Name.LocalName));
- 
-// Fetch the FontWeight attribute
-XAttribute attr = runElem.Attribute("FontWeight");
-Log.WriteLine(attr.Value);
- 
-// Verify it is Bold
-Assert.AreEqual<string>("Bold", attr.Value);
-```
-
-```VB
-Dim rtbContents As String = DirectCast(Pages.SilverlightAppTesting.SilverlightApp.RichTextBox1Richtextbox.GetProperty(New AutomationProperty("Xaml", GetType(String))), String)
-Log.WriteLine(rtbContents)
-  
-
-Dim xElem As XElement = XElement.Parse(rtbContents)
-  
-
-Dim runElem As XElement = xElem.Descendants().First(Function(e) "Run".Equals(e.Name.LocalName))
-  
-
-Dim attr As XAttribute = runElem.Attribute("FontWeight")
-Log.WriteLine(attr.Value)
-  
-
-Assert.AreEqual(Of String)("Bold", attr.Value)
-```
-
-[1]: /img/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox/fig1.png
diff --git a/docs/advanced-topics/coded-samples/wpf/automate-clickonce-app.md b/docs/advanced-topics/coded-samples/wpf/automate-clickonce-app.md
index 6ae8f7d6..0cc7c8b5 100644
--- a/docs/advanced-topics/coded-samples/wpf/automate-clickonce-app.md
+++ b/docs/advanced-topics/coded-samples/wpf/automate-clickonce-app.md
@@ -1,8 +1,7 @@
 ---
 title: Automate ClickOnce App
 page_title: Automate ClickOnce App
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-
+description: "Learn how to automate ClickOnce WPF applications in Test Studio. This guide provides a coded solution in C# to handle dynamic app paths, ensuring seamless automated testing workflows for ClickOnce deployments."
 position: 5
 ---
 # Automate "ClickOnce" WPF Application
@@ -16,25 +15,25 @@ To automate a WPF application it is necessary to <a href="/features/testing-type
 
 It is necessary to create a <a href="/features/coded-steps/standalone-code-file" target="_blank">stand alone class file</a> (*Utility*) which static property (*pathFile*) will be used to store the path to the latest app version:
 
-```C#
+````C#
 public class Utility
 {
     public static string pathFile = string.Empty;
 }
-```
-```VB
+````
+````VB
 Public Class Utility
 
     Public Shared pathFile As String = String.Empty
 
 End Class
-```
+````
 
 <br/>
 
 The following scenario assumes that the app is downloaded form a web destination, installed and ran from a browser. In such case the first test in the list will be a Web test that will complete the app installation part. At the end of the installation the latest app version will be up and running. This test have to end with a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> that will save in a variable path to the new application as given below:
 
-```C#
+````C#
 // check if there is running process with same name
 var runningApp = System.Diagnostics.Process.GetProcesses().Where(p => p.ProcessName == "YourClickOnceWpfApp");
 
@@ -46,8 +45,8 @@ Log.WriteLine(proc.MainModule.FileName.ToString());
 
 // save the full path to a common variable
 Utility.pathFile = proc.MainModule.FileName.ToString();
-```
-```VB
+````
+````VB
 
 Dim runningApp = System.Diagnostics.Process.GetProcesses().Where(Function(p) p.ProcessName = "YourClickOnceWpfApp")
 
@@ -57,14 +56,14 @@ Log.WriteLine(proc.MainModule.FileName.ToString())
 
 Utility.pathFile = proc.MainModule.FileName.ToString()
 
-```
+````
 
 <br/>
 
 Next step is to create a WPF test that begins with a coded step and is configured to run a dummy WPF app. In the coded step the initially started mock app will be closed. Then depending on the latest version state (running/stoped) Test Studio will connect to or open it for next test steps execution:
 
 
-```C#
+````C#
 // Shut down "mock" app
 ActiveApplication.Quit();
 
@@ -81,8 +80,8 @@ else
     // or - launch new application
     Manager.LaunchNewApplication(Utility.pathFile);
 }
-```
-```VB
+````
+````VB
 
 ActiveApplication.Quit()
 
@@ -98,7 +97,7 @@ Else
 
 End If
 
-```
+````
 
 <br/>
 
diff --git a/docs/advanced-topics/coded-samples/wpf/connect-to-running-app.md b/docs/advanced-topics/coded-samples/wpf/connect-to-running-app.md
index 51b516dd..1449f512 100644
--- a/docs/advanced-topics/coded-samples/wpf/connect-to-running-app.md
+++ b/docs/advanced-topics/coded-samples/wpf/connect-to-running-app.md
@@ -1,21 +1,20 @@
 ---
 title: Connect to Running App
 page_title: Connect to Running App
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/wpf/connect-to-running-wpf-app.aspx, /user-guide/code-samples/wpf/connect-to-running-wpf-app
+description: "Learn how to connect to a running WPF application in Test Studio. This guide provides a coded solution in C# to execute tests on an active app instance or launch a new one if needed, enhancing automated testing workflows."
 position: 1
 ---
-#Connect to a Running WPF Application#
+# Connect to a Running WPF Application
 
 *I would like to connect to an already running WPF application and execute the test there, instead of launching a new instance of the app.*
 
-##Solution##
+## Solution
 
 When you Quick Execute or execute a Test List, a new instance of the app launches from its pre-configured location.
  
 To work around this limitation, create a mock application to feed to Test Studio. Then insert a coded step as the first step of the test. Use the following code which closes the mock application and connects to the desired application if it's running. If not, a new instance is launched. This solution is applicable for both Test Studio Standalone version and the Visual Studio plugin.
 
-```C#
+````C#
 ActiveApplication.Quit();
 var runningApp = System.Diagnostics.Process.GetProcesses().Where(p => p.ProcessName == "WPFHelloWorld");
   
@@ -29,8 +28,8 @@ else
 }
  
 Manager.ActiveApplication.MainWindow.RefreshVisualTrees();
-```
-```VB
+````
+````VB
 ActiveApplication.Quit()
 Dim runningApp = System.Diagnostics.Process.GetProcesses().Where(Function(p) p.ProcessName = "WPFHelloWorld")
  
@@ -41,7 +40,7 @@ Else
 End If
  
 Manager.ActiveApplication.MainWindow.RefreshVisualTrees()
-```
+````
 
 
 
diff --git a/docs/advanced-topics/coded-samples/wpf/go-through-grid-cells.md b/docs/advanced-topics/coded-samples/wpf/go-through-grid-cells.md
index 12e087da..2a87839d 100644
--- a/docs/advanced-topics/coded-samples/wpf/go-through-grid-cells.md
+++ b/docs/advanced-topics/coded-samples/wpf/go-through-grid-cells.md
@@ -1,15 +1,14 @@
 ---
 title: Go Through Grid Cells
 page_title: Go Through Grid Cells
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/wpf/go-through-cells.aspx, /user-guide/code-samples/wpf/go-through-cells
+description: "Learn how to iterate through each cell in a WPF RadGridView using Test Studio. This guide provides a coded solution in C# to perform actions or verifications on grid cells during automated testing."
 position: 4
 ---
-#Go Through Each Cell in a WPF RadGridView#
+# Go Through Each Cell in a WPF RadGridView
 
 *I would like to go through each cell in a WPF RadGridView and perform some action or verification.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. Here's an example that goes through all the visible cells in a WPF demo grid (as opposed to all the cells contained in the grid). It writes the text content of each cell into the test log.
 
@@ -17,7 +16,11 @@ This is possible with a coded solution. Here's an example that goes through all
 ><br>
 > The application used to build the sample code is the official <a href="https://demos.telerik.com/wpf/" target="_blank">Telerik UI for WPF Controls Demo app</a>. 
 
-```C#
+> **Note** 
+><br>
+> The application used to build the sample code is the official <a href="https://demos.telerik.com/wpf/" target="_blank">Telerik UI for WPF Controls Demo app</a>. 
+
+````C#
 WpfApplication app = Manager.ActiveApplication;
 Assert.IsNotNull(app);
  
@@ -38,8 +41,8 @@ foreach (Telerik.WebAii.Controls.Xaml.Wpf.GridViewRow gRow in grid.Rows)
     }
     rowCounter++;
 }
-```
-```VB
+````
+````VB
 Dim app As WpfApplication = Manager.ActiveApplication
 Assert.IsNotNull(app)
  
@@ -58,7 +61,7 @@ For Each gRow As Telerik.WebAii.Controls.Xaml.Wpf.GridViewRow In grid.Rows
     Next
     rowCounter += 1
 Next
-```
+````
 
 
 
diff --git a/docs/advanced-topics/coded-samples/wpf/go-through-radtreeview.md b/docs/advanced-topics/coded-samples/wpf/go-through-radtreeview.md
index d7b239cc..e3f5d128 100644
--- a/docs/advanced-topics/coded-samples/wpf/go-through-radtreeview.md
+++ b/docs/advanced-topics/coded-samples/wpf/go-through-radtreeview.md
@@ -1,19 +1,18 @@
 ---
 title: Go Through RadTreeView
 page_title: Go Through RadTreeView
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/wpf/go-through-radtreeview.aspx, /user-guide/code-samples/wpf/go-through-radtreeview
+description: "Learn how to iterate through nodes in a WPF RadTreeView using Test Studio. This guide provides a coded solution in C# to expand nodes, refresh the tree, and locate specific matches during automated testing."
 position: 3
 ---
-#Go Through Each Node in a WPF RadTreeView#
+# Go Through Each Node in a WPF RadTreeView
 
 *I would like to go through each node in a WPF RadTreeView until a match is made.*
 
-##Solution##
+## Solution
 
 This is possible with a coded solution. You'll expand each node and refresh the tree until you find your match.
 
-```C#
+````C#
 WpfApplication app = Manager.ActiveApplication;
 Assert.IsNotNull(app);
 Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView tree = app.MainWindow.Find.ByName<Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView>("treeView");
@@ -53,8 +52,8 @@ while (found == false)
         break;
     }
 }
-```
-```VB
+````
+````VB
 Dim app As WpfApplication = Manager.ActiveApplication
 Assert.IsNotNull(app)
 Dim tree As Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView = app.MainWindow.Find.ByName(Of Telerik.WebAii.Controls.Xaml.Wpf.RadTreeView)("treeView")
@@ -86,6 +85,6 @@ While found = False
         Exit While
     End If
 End While
-```
+````
 
 
diff --git a/docs/advanced-topics/coded-samples/wpf/parameterize-wpf-app.md b/docs/advanced-topics/coded-samples/wpf/parameterize-wpf-app.md
index 9d244490..f646f99f 100644
--- a/docs/advanced-topics/coded-samples/wpf/parameterize-wpf-app.md
+++ b/docs/advanced-topics/coded-samples/wpf/parameterize-wpf-app.md
@@ -1,17 +1,16 @@
 ---
 title: Parameterize WPF App
 page_title: Parameterize WPF App
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/code-samples/wpf/parameterize-wpf-app-location.aspx, /user-guide/code-samples/wpf/parameterize-wpf-app-location
+description: "Learn how to parameterize the location of a WPF application in Test Studio. This guide provides a coded solution in C# to handle dynamic app paths, enabling flexible and efficient automated testing workflows."
 position: 2
 ---
-#Parameterize the Location of a WPF Application#
+# Parameterize the Location of a WPF Application
 
 Currently Test Studio is rigged that you cannot run a WPF Test unless you provide a definite (non-parameterized) location for the application under testing.
 
 ![Configure WPF path][1]
 
-##Solution##
+## Solution
 
 To work around this limitation, create a mock application to feed to Test Studio. Then change the application under testing in a coded step. This allows you to use a parameterization method of your choosing for the app's location. This solution is applicable for both Test Studio Standalone version and the Visual Studio plugin.
 
@@ -25,7 +24,7 @@ To work around this limitation, create a mock application to feed to Test Studio
 
 Let's assume that the "real" application is in the following location: **C:\myapps\Go.exe**. Here's the code:
 
-```C#
+````C#
 //Shut down "mock" app
 ActiveApplication.Quit();
  
@@ -43,8 +42,8 @@ WpfApplication app = Manager.LaunchNewApplication(pinfo);
  
 //Check whether we connected successfully
 Assert.IsNotNull(app);
-```
-```VB
+````
+````VB
 ActiveApplication.Quit()
  
 
@@ -58,15 +57,15 @@ Dim app As WpfApplication = Manager.LaunchNewApplication(pinfo)
  
 
 Assert.IsNotNull(app)
-```
+````
 
 
 You can extend this code to include parameterization for the app's location. You can use data binding, for instance. Let's say your test is bound to a data sheet with a column named "paths":
 
 
-```C#
+````C#
 var pinfo = new System.Diagnostics.ProcessStartInfo(Data["paths"]);
-```
+````
 
 
 Of course this is only one of the possible solutions you can implement. If you need to use additional assemblies, <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">here</a> is how to do that in the Standalone version.
diff --git a/docs/archived-docs/elements/find-element-archive.md b/docs/archived-docs/elements/find-element-archive.md
deleted file mode 100644
index 0856bf84..00000000
--- a/docs/archived-docs/elements/find-element-archive.md
+++ /dev/null
@@ -1,163 +0,0 @@
----
-title: Modifying Elements Find Expression
-page_title: Modifying Elements Find Expression (Archive)
-description: "Archived element find expressions and how to change this"
-position: 0
----
-# (Archive) Element's Find Expressions
-
-> __Note__
-> <br>
-> <br>
-> The workflow described below is valid, if editing elements in __Test Studio Dev Edition__ (Visual Studio Plugin).
-> <br>
-> <br>
-> <a href="/automated-tests/elements/find-element" target="_blank">Read here for editing elements in __Test Studio IDE__</a>.
-
-In certain scenarios the automatically generated <a href="/features/elements-explorer/elements-find-expression" target="_blank">find expression</a> may be ineffective, because locates multiple elements on the active window, or may use dynamically generated attributes, which are unreliable by the next test execution. In such cases you may require adjusting the find expression manually, so that it reflects the specifics of the application under test.
-
-## Version 2018 R3 and Earlier (Both Standalone Application and Visual Studio Plugin)
-
-When a web page element has an action recorded against it, or you explicitly add an element to the Elements pane, a **Find Expression** is generated that Test Studio uses to find that specific element on the web page.
-
-To change how an element is found, right click on the element in the Explorer and select **Edit Element**.
-
-![Edit Element][1]
-
-In the VS plugin, click the **Show Element Explorer** icon in the toolbar and locate the Explorer at the bottom of the screen.
-
-![Edit Element VS][2]
-
-Select **Edit in Live** to directly open the <a href="#find-element">Find element</a> dialog for the page open in the current recorder.
-
-![Edit in live][3]
-
-The **Find Element** splash screen appears. You have three options for how to locate the element:
-
-![Find Element][4]
-
-**Find in the Live Version** - find the element using the latest version of a new browser window, an existing test step, or an application that you currently have open.
-
-- **New Browser** - this will launch a new instance of your application. You may need to manually navigate to the element. Click **Browse & Navigate** to proceed.
-- **Existing Test Step** - use an existing step from a test to get to the element. Click **Choose Test Step** to proceed.
-- **Current Page** - select where the element is available from a list of currently running browser instances or WPF applications. Click **Go** to proceed.
-
-![Find Element][5]
-
-**Find in the Cached Version** - if your test failed, you can find the element using the cached version of the application at the time of failure. Accessible only through the **Resolve Failure** tab in the Step Failure Details.
-
-**Find Without Connection** - choose this option to find the element without connecting to the application.
-
-> To skip this splash screen the next time you load the Find Element dialog, check the box at the bottom and click Close.
-
-The <a name="find-element">Find Element</a> dialog appears. The Element Name, Element Type, and Connection Status are at the top.
-
-![Find Element][6]
-
-The **Change Element** link opens the **Select New Element dialog**.
-
-![Change Element][7]
-
-In the Select Html Element dialog, you can open the Find Element dialog for a different element in the Elements Repository.
-
-![Select HTML Element][8]
-
-The **Connection Options** button takes you back to the **Find Element** splash screen.
-
-![Connection Options][9]
-
-**The Suggestions and DOM** views are on the left side.
-
-- **Suggestions** - these are the suggested items to help you find the element in the application. Click an item to add it to your **Find Settings**.
-
-![Suggestions][10]
-
-- **DOM** - use the DOM as a reference when creating your Find Settings. This view is helpful in determining where your element is located relative to the DOM tree. 
-
-![DOM][11]
-
-The **Find Settings** view is on the right side. You can edit these settings by typing in new properties, selecting a new modifier in the drop-down menu, or changing the values. Click Validate to confirm whether the element can be found using the current Find Settings.
-
-<table id="no-table">
-<tr>
-<td>![Element Found][12]</td>
-<td>![Element Not Found][13]</td>
-</tr>
-<table>
-
-## Data-driven find logic
-
-<a name="data-driven"></a>Here, you can also <a href="/features/data-driven-testing/overview" target="_blank">data drive</a> the element find expression. If your test has an attached data source, the value fields of the find expressions for your elements will include a drop-down list displaying columns from your data source.
-
-![Data drive find exp][14]
-
-Selecting a column data binds the column to the value of the find expression rule.
-
-![Data drive find exp][15]
-
-If the element was not found, click the **Troubleshoot** button. Choose a suggested fix from the Troubleshoot screen.
-
-![Troubleshoot][16]
-
-There are three additional buttons in the upper right of the **Find Element** dialog:
-
-![Additional Buttons][17]
-
-- **Select New Element** - choose this option if the incorrect element was selected for this step. This will clear your current settings and <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> provides new filters for the new element. 
-
-![Select New Element][18]
-
-- **Advanced** - edit the Find Settings using a string-based expression builder. 
-
-![Advanced][19]
-
-- **Reset** - restores fields to their original settings. 
-
-![Reset][20]
-
-Once you've confirmed you are targeting the correct element and it is correctly found, click Save and Close. If the modified element is used by multiple automation steps, you are prompted to select the steps you want to persist changes to.
-
-![Test Case Selector][21]
-
-[1]: /img/features/elements-explorer/find-element/fig1.png
-[2]: /img/features/elements-explorer/find-element/fig2.png
-[3]: /img/features/elements-explorer/find-element/fig3.png
-[4]: /img/features/elements-explorer/find-element/fig4.png
-[5]: /img/features/elements-explorer/find-element/fig5.png
-[6]: /img/features/elements-explorer/find-element/fig6.png
-[7]: /img/features/elements-explorer/find-element/fig7.png
-[8]: /img/features/elements-explorer/find-element/fig8.png
-[9]: /img/features/elements-explorer/find-element/fig9.png
-[10]: /img/features/elements-explorer/find-element/fig10.png
-[11]: /img/features/elements-explorer/find-element/fig11.png
-[12]: /img/features/elements-explorer/find-element/fig12.png
-[13]: /img/features/elements-explorer/find-element/fig13.png
-[14]: /img/features/elements-explorer/find-element/fig14.png
-[15]: /img/features/elements-explorer/find-element/fig15.png
-[16]: /img/features/elements-explorer/find-element/fig16.png
-[17]: /img/features/elements-explorer/find-element/fig17.png
-[18]: /img/features/elements-explorer/find-element/fig18.png
-[19]: /img/features/elements-explorer/find-element/fig19.png
-[20]: /img/features/elements-explorer/find-element/fig20.png
-[21]: /img/features/elements-explorer/find-element/fig21.png
-[101]: /img/features/elements-explorer/find-element/fig101.png
-[102]: /img/features/elements-explorer/find-element/fig102.png
-[103]: /img/features/elements-explorer/find-element/fig103.png
-[104]: /img/features/elements-explorer/find-element/fig104.gif
-[105]: /img/features/elements-explorer/find-element/fig105.png
-[106]: /img/features/elements-explorer/find-element/fig106.png
-[107]: /img/features/elements-explorer/find-element/fig107.png
-[108]: /img/features/elements-explorer/find-element/fig108.png
-[109]: /img/features/elements-explorer/find-element/fig109.png
-[110]: /img/features/elements-explorer/find-element/fig110.png
-[111]: /img/features/elements-explorer/find-element/fig111.png
-[112]: /img/features/elements-explorer/find-element/fig112.png
-[113]: /img/features/elements-explorer/find-element/fig113.png
-[114]: /img/features/elements-explorer/find-element/fig114.png
-[115]: /img/features/elements-explorer/find-element/fig115.png
-[116]: /img/features/elements-explorer/find-element/fig116.png
-[117]: /img/features/elements-explorer/find-element/fig117.png
-[118]: /img/features/elements-explorer/find-element/fig118.png
-[119]: /img/features/elements-explorer/find-element/fig119.png
-[120]: /img/features/elements-explorer/find-element/fig120.png
-[130]: /img/features/elements-explorer/find-element/fig130.png
\ No newline at end of file
diff --git a/docs/archived-docs/generate-application-log-archive.md b/docs/archived-docs/generate-application-log-archive.md
deleted file mode 100644
index f839524d..00000000
--- a/docs/archived-docs/generate-application-log-archive.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Generate Application Log
-page_title: Generate Application Log (Archive)
-description: (Archive) Generate application log.
-position: 1
----
-# How to Generate a Test Studio Application Log #
-
-> __Tip__
-> <br>
-> <br>
-> Find <a href="/knowledge-base/best-practices-kb/generate-application-log" target="_blank">here</a> the latest instructions how to generate the application log from the different Test Studio components.
-
-*I'm experiencing an issue with the Test Studio application (as opposed to an automation challenge). I need to generate an application log file for troubleshooting purposes.*
-
-Test Studio supports logging. The logs are stored in a plain text file in the **"Logs"** folder in the product's installation folder, by default in **"C:\Program Files (x86)\Progress\Test Studio\Logs"**. This feature is initially turned off and you will need to manually turn it on. Please note that this log monitors "application" events. The log will not be of much value in troubleshooting true automation problems (e.g. the test doesn't press the button in my Login page).
- 
-You might be asked by the Telerik Support team to provide an application log for a particular problem. The best practice here would be to clear the log (if not empty to begin with) and enable it. After this, trigger the problematic behavior and subsequently send the log.
-
-
-## **Standalone version 2016 R2 Version and Earlier** ##
-
-1.&nbsp; Click the **Help** tab.
-
-2.&nbsp; Click **Enable** in the Logging ribbon.
-
-![Enable log][1]
-
-3.&nbsp; This will turn on logging. After you experience the issue, open the log by clicking the **View Log** button.
-
-![View log][2]
-
-## Run-Time edition ##
-
-### Through Standalone version ###
-
-1.&nbsp; Click **Status** in the **Test tab**.
-
-![Status button][3]
-
-2.&nbsp; Double click on the remote machine that you are interested in:
-
-![Remote machine][4]
-
-3.&nbsp; The remote machine log related controls are placed on the right side of the window as shown on the next screenshot. Press on the **Logging** button to enable it. The **View Log** button will open the current log file at the current state. If click on **Clear Log** button - all previous messages will be deleted.
-
-![View log][9]
-
-### **Standalone version 2017 R1 Version and Earlier** ###
-
- Click at Logging tab and enable log in. This will turn on logging. After you experience the issue, open the log by clicking the View Log button.
-
-![View log][5]
-
-### Through the registry on the remote machine ###
-
-If you use only Runtime version you will need to manually edit the **Registry** on the machine. Load <a href="http://support2.microsoft.com/kb/136393" target="_blank">Regedit</a> and find the Test Studio folder. The default path is:
-
-* **Computer\HKEY_CURRENT_USER\Software\Wow6432Node\Telerik\Test Studio**
-
-![Registyry][6]
-
-Find (or create) the TraceLogEnabled key in this folder. Double click it and change the Value data to 1. You should also see the TraceLogPath value. This is where the log will be stored. Ensure you include the file name and type:
-
-* **C:\Temp\TraceLog\log.txt**
-
-Find out more about <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log" target="_blank">using the application log</a> in our troubleshooting guide.
-
-[1]: /img/knowledge-base/best-practices-kb/generate-application-log/fig1.png
-[2]: /img/knowledge-base/best-practices-kb/generate-application-log/fig2.png
-[3]: /img/knowledge-base/best-practices-kb/generate-application-log/fig3.png
-[4]: /img/knowledge-base/best-practices-kb/generate-application-log/fig4.png
-[5]: /img/knowledge-base/best-practices-kb/generate-application-log/fig5.png
-[6]: /img/knowledge-base/best-practices-kb/generate-application-log/fig6.png
-[7]: /img/knowledge-base/best-practices-kb/generate-application-log/fig7.png
-[8]: /img/knowledge-base/best-practices-kb/generate-application-log/fig8.png
-[9]: /img/knowledge-base/best-practices-kb/generate-application-log/fig9.png
-
-
diff --git a/docs/archived-docs/recorder/recorder-overview-archive.md b/docs/archived-docs/recorder/recorder-overview-archive.md
deleted file mode 100644
index a8fb2b80..00000000
--- a/docs/archived-docs/recorder/recorder-overview-archive.md
+++ /dev/null
@@ -1,129 +0,0 @@
----
-title: Overview
-page_title: Recording Overview
-description: "Archived documentation 2020 R2 and earlier"
-position: 0
----
-# Test Recording #
-
-> **Note**
-> <br>
-> Information about the Recorder in the latest release of Test Studio can be found <a href="/general-information/test-recording/overview" target="_blank">here</a>.
-
-There are two ways to initiate recording. You can either launch a new browser instance with the recording toolbar attached, or you can attach the recording toolbar to an existing browser instance (applicable for IE only or WPF application).
-
-## **From Version 2016 R3 Until Version 2020 R3** ##
-
-## Launch New Recording Browser ##
-
-> **Note**
-> <br>
-> Once a recording session is started **do not start another instance of the same browser** until the session is finished!
-
-1.&nbsp;  Double click the newly created test to open it. Click the ***Record*** button in the *Tests* ribbon or press **CTRL+R**.
-
-<table id=no-table>
-	<tr>
-		<td>![Test Studio][10] <br><br>**Standalone version**</td>
-		<td>![VS][11] <br><br>**VS plugin**</td>
-	</tr>
-<table>
-
-2.&nbsp; In the next dialog type the URL you want to navigate to, select the recording browser and press Enter or the *Record* button. You can choose a URL from your recent URLs.
-
-> **Note**: Selecting the recording browser will be skipped if you have already set a preferred browser from the <a href="/getting-started/test-execution/quick-execution" target="_blank">Test ribbon</a>.
-
-![Choose browser][12]
-
-If you enable **Save my choice for the future** or you have set a preferred browser from the <a href="/getting-started/test-execution/quick-execution" target="_blank">Test ribbon</a> the ***Record*** button in the Test Studio project will display the icon for the selected default browser.
-
-![Choose preferred browser][13]
-
-3.&nbsp; Once the selected browser navigates to the desired page, the recorder gets attached to it, a navigate step gets recorded in the Steps pane and you can continue recording the next actions as per the required scenario.
-
-![Attached recorder][14]
-
-## Attach to Existing Instance (Applicable for IE Only or WPF Application) ##
-
-Click the drop-down arrow on the ***Record*** button to see a list of available IE browser instances or WPF applications. Select one to attach the recorder to that instance.
-
-<table id=no-table>
-	<tr>
-		<td>![Attach to running browser][15] <br><br>**Web Test - Internet Explorer only**</td>
-		<td>![Attach to running WPF instance][16] <br><br>**WPF Test - connect to running WPF application instance**</td>
-	</tr>
-<table>
-
-## **2016 R2 Version and Earlier** ##
-
-## Launch New Recording Browser ##
-
-1.&nbsp; Click the __Record__ button or press __CTRL+R__.
-	
-<table id=no-table>
-	<tr>
-		<td>![Test Studio][1] <br><br>**Standalone version**</td>
-		<td>![VS][2] <br><br>**VS plugin**</td>
-	</tr>
-<table>
-
-2.&nbsp; Choose the recording browser.
-
-![Choose browser][3]
-
-Note: As of the 2014.4.1211 version Safari cannot be used for test recording.
-
-If you enable __Save my choice for the future__, the Record button in <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> Standalone will display the icon for the default browser.
-
-![Choose browser][4]
-
-You can select a different recording browser later from the __Record__ button drop-down.
-
-<table id="no-table">
-	<tr>
-		<td>![Test Studio][5] <br><br>**Standalone version**</td>
-		<td>![VS][6] <br><br>**VS plugin**</td>
-	</tr>
-<table>
-
-3.&nbsp; Enter a URL and press Enter/Start Recording button. A recording step is added to the Steps pane and the recorder is attached to the browser.
-
-![Start recording][7]
-
-![Attaching the recorder][8]
-
-## Attach to Existing Instance ##
-
-Click the drop-down arrow on the __Record__ button to see a list of available browser instances or WPF applications. Select one to attach the recorder to that instance.
-
-![Attaching the recorder][9]
-
-> You cannot connect to an existing Silverlight Out-of-Browser application for Out-of-Browser tests.
-
-To end recording, simply close the IE window or WPF application that has the recording toolbar attached
-
-4.&nbsp; **Compare Mode** determines which mode to use when adding a page node to the Elements Explorer. Compare Mode can be checked against the page's Title or one of multiple settings that look at various parts of a URL. Please see <a href="/features/project-settings/recording-options#elements-page-compare-mode" target="_blank">this article</a> for more information.
-
-![CompareMode][13]
-
-## See also ##
-
-* <a href="/features/project-settings/browsers" target="_blank">Calibrate Browsers</a>
-
-[1]: /img/archived-docs/test-recording/overview/fig1.png
-[2]: /img/archived-docs/test-recording/overview/fig2.png
-[3]: /img/archived-docs/test-recording/overview/fig3.png
-[4]: /img/archived-docs/test-recording/overview/fig4.png
-[5]: /img/archived-docs/test-recording/overview/fig5.png
-[6]: /img/archived-docs/test-recording/overview/fig6.png
-[7]: /img/archived-docs/test-recording/overview/fig7.png
-[8]: /img/archived-docs/test-recording/overview/fig8.png
-[9]: /img/archived-docs/test-recording/overview/fig9.png
-[13]: /img/archived-docs/test-execution/quick-execution/fig13.png
-[10]: /img/archived-docs/test-recording/overview/fig10.png
-[11]: /img/archived-docs/test-recording/overview/fig11.png
-[12]: /img/archived-docs/test-recording/overview/fig12.png
-[13]: /img/archived-docs/test-recording/overview/fig13.png
-[14]: /img/archived-docs/test-recording/overview/fig14.png
-[15]: /img/archived-docs/test-recording/overview/fig15.png
-[16]: /img/archived-docs/test-recording/overview/fig15a.png
diff --git a/docs/archived-docs/recorder/recording-toolbar-archive.md b/docs/archived-docs/recorder/recording-toolbar-archive.md
deleted file mode 100644
index 15979af6..00000000
--- a/docs/archived-docs/recorder/recording-toolbar-archive.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Recording Toolbar
-page_title: Recording Toolbar
-description: "Archived documentation 2020 R2 and earlier"
-position: 1
----
-# Recording Toolbar Version 2020 R2 and Earlier#
-
-> **Note**
-> <br>
-> Information about the Recording Toolbar in the latest release of Test Studio can be found <a href="/features/recorder/compact-recording-toolbar" target="_blank">here</a>.
-
-Once a recording session is started the ***Recorder Toolbar*** gets connected to the browser/WPF application instance.
-
-![Attaching the recorder][1]
-
-## DOM Explorer Options ##
-
-Below are listed its features related to the <a href="/features/recorder/dom-explorer" target="_blank">DOM explorer</a> and how you could use these during recording:
-
-<table id="no-table" >
-	<tr cellspacing="10">
-		<td cellspacing="1">![Enable/Disable Hover Over Highlighting][2]<br></td>
-		<td>**Enable/Disable Hover Over Highlighting** (Use keyboard shortcut -press "*Pause/Break*" button to toggle)</td>
-	</tr>
-	<tr cellspacing="10">
-		<td>![Pause Recording][3]</td>
-		<td>**Pause Recording** (Use keyboard shortcut - press "*Print Screen*" button to toggle)</td>
-	</tr>
-	<tr>
-		<td>![Start Recording][4]</td>
-		<td>**Start Recording** (Use keyboard shortcut - press "*Print Screen*" button to toggle)</td>
-	</tr>
-	<tr>
-		<td>![Reconnect Recorder][5]
-		<td>**Reconnect Recorder** - Restores communication between Test Studio and the recording browser window or WPF app, if necessary</td>
-	</tr>
-	<tr>
-		<td>![Navigation panel][6]</td>
-		<td>**Navigation panel** - Type URL to record and navigate to, Refresh the Browser, use the arrows to navigate Back or Forward</td>
-	</tr>
-	<tr>
-		<td>![Dock/Undock][7] / ![Dock/Undock][8]</td>
-		<td>**Undock/Dock** - Undock the recorder toolbar from the browser/WPF window or dock it back</td>
-	</tr>
-	<tr>
-		<td>![Add to elements repository][9]</td>
-		<td>**Add To Elements Repository** - Add a single or multiple elements to the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a>)</td>
-	</tr>
-	<tr>
-		<td>![Manual Refresh of the DOM][12]</td>
-		<td>**Manual Refresh of the DOM** - Used when auto-refresh is paused and the DOM tree is changed</td>
-	</tr>
-	<tr>
-		<td>![Freeze DOM tree][11] / ![Unfreeze DOM tree][11a]</td>
-		<td>**Freeze/Unfreeze DOM tree** - Pause/Resume the DOM tree auto-refresh option</td>
-	</tr>
-	<tr>
-		<td>![Elements tree/tag view][10]</td>
-		<td>**Elements Tree/Tag View** - Whether to display the elements as tree view or tag view</td>
-	</tr>
-<table>
-
-## Step Builder Options ##
-
-On the right side of the recording toolbar you can find the ***Actions*** and ***Verifications*** steps from the <a href="/getting-started/test-recording/step-suggestions" target="_blank">Step Builder</a>. Adding steps during recording is necessary in some special occasions - if you need a <a href="/features/recorder/mouse-actions/drag-and-drop" target="_blank">drag&drop step</a> or an <a href="/features/recorder/verifications/advanced-verification" target="_blank">advanced verification</a>.
-
-Other possible scenarios when is recommended to use the Step Builder from the **Recorder Toolbar** are usually related to specific applications and how these are built. If *Record&Playback* doesn't work out of the box usually the structure of application does not allow recognition of separate elements identified by unique attributes. Then the only option left is to manually select the correct element in DOM explorer and add the necessary steps.
-
-**See also:**
-
-* <a href="/features/elements-menu/overview" target="_blank">Elements Menu</a>
-
-* <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a>
-
-* <a href="/features/verifications/overview" target="_blank">Verifications</a>
-
-[1]: /img/archived-docs/test-recording/recording-toolbar/fig1.png
-[2]: /img/archived-docs/test-recording/recording-toolbar/fig2.png
-[3]: /img/archived-docs/test-recording/recording-toolbar/fig3.png
-[4]: /img/archived-docs/test-recording/recording-toolbar/fig4.png
-[5]: /img/archived-docs/test-recording/recording-toolbar/fig5.png
-[6]: /img/archived-docs/test-recording/recording-toolbar/fig6.png
-[7]: /img/archived-docs/test-recording/recording-toolbar/fig7.png
-[8]: /img/archived-docs/test-recording/recording-toolbar/fig8.png
-[9]: /img/archived-docs/test-recording/recording-toolbar/fig9.png
-[10]: /img/archived-docs/test-recording/recording-toolbar/fig10.png
-[11]: /img/archived-docs/test-recording/recording-toolbar/fig11-lock.png
-[11a]: /img/archived-docs/test-recording/recording-toolbar/fig11-unlock.png
-[12]: /img/archived-docs/test-recording/recording-toolbar/fig12-refresh.png
diff --git a/docs/archived-docs/recorder/silverlight-out-of-browser-archive.md b/docs/archived-docs/recorder/silverlight-out-of-browser-archive.md
deleted file mode 100644
index e6fc060d..00000000
--- a/docs/archived-docs/recorder/silverlight-out-of-browser-archive.md
+++ /dev/null
@@ -1,56 +0,0 @@
----
-title: Silverlight Out-of-Browser
-page_title: Create a Silverlight Out-of-Browser Test (Standalone)
-description: "Test Studio Create a Silverlight Out-of-Browser Test"
-position: 1
----
-# Create a Silverlight Out-of-Browser Test (Standalone) 
-
-Test Studio supports Silverlight Out-of-Browser applications and below you can read how to create a test for that type of app.
-
-> __Important!__
-><br>
-><br>
-> As of Test Studio release __R3 2020 SP1 (v.2020.3.1209)__ Silverlight Out-of-Browser testing in Test Studio is no longer visible in the main Test Studio user interface. If you want to continue using it, see <a href="#enable-silverlight-out-of-browser-in-test-studio-2020-r3-sp-release">here</a> how to enable it.
-
-__Important Notes:__
-
-* If you are testing a Silverlight In-Browser web application, we recommend treating it as a standard <a href="/automated-tests/recording/overview" target="_blank">Web Test</a> with no additional configuration.
-
-* See <a href="http://msdn.microsoft.com/en-us/library/dd550721(v=vs.95).aspx" target="_blank">here</a> for what constitutes Out-of-Browser.
-
-* Once a Silverlight Out-of-Browser application is configured for recording, Test Studio modifies its shortcut to point directly to the application's location on disk. This replaces the Microsoft "offline://" notation. The side effect of this is that your application will not detect that it is running in Out-of-Browser mode and code must be written in the application to work around this limitation.
-
-* Test Studio does not support the Web Browser control in Silverlight Out-of-Browser applications.
-
-## How to Configure a Test for Silverlight Out-Of-Browser
-
-1. <a href="/getting-started/create-test-standalone/add-test" target="_blank">Add a Web Test</a> to your test project. 
-
-2. Click the __Out-Of-Browser__ icon in the __Silverlight__ ribbon.
-
-	![OOB button][4]
-
-3. Check the __Configure this test to run against a Silverlight application__ box in Out-Of-Browser options.
-4. Browse for the Local Application Directory or drag and drop a link to your Silverlight application.
-5. Select __Silverlight Out-of-Browser__ under __Recording Host__.
-
-	![Recording host][5]
-
-6. Click __Record__ to launch the out-of-browser app with the recording toolbar docked at the top.
-7. Notice that steps are added to the test as actions are taken within the application.
-
-![Recording][6]
-
-## Enable Silverlight Out-Of-Browser in Test Studio 2020 R3 SP Release
-
-The icon to configure a test for __Silverlight-Out-Of-Browser__ application testing is __removed in Test Studio release R3 SP 2020 (v.2020.3.1209)__. You still can bring up the icon back in the product.
-
-Open the Windows Registry Editor and navigate to key _HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Telerik\TestStudio_. Add a new string type key named _ShowSilverlightOutOfBrowser_ and set its value to _true_. Restart Test Studio and the Silverlight-Out-Of-Browser icon will appear back in the _Test Ribbon_.
-
-[1]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig1.png
-[2]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig2.png
-[3]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig3.png
-[4]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig4.png
-[5]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig5.png
-[6]: /img/general-information/create-test-standalone/silverlight-out-of-browser/fig6.png
diff --git a/docs/archived-docs/recorder/silverlight-out-of-browser-vs-plugin-archive.md b/docs/archived-docs/recorder/silverlight-out-of-browser-vs-plugin-archive.md
deleted file mode 100644
index 9f3b5169..00000000
--- a/docs/archived-docs/recorder/silverlight-out-of-browser-vs-plugin-archive.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Silverlight Out-of-Browser
-page_title: Create a Silverlight Out-of-Browser Test (VS plugin)
-description: "Test Studio Create a Silverlight Out-of-Browser Test (VS plugin)"
-position: 3
-publish: false
----
-# Create a Silverlight Out-of-Browser Test (VS plugin) #
-
-Test Studio supports Silverlight Out-of-Browser applications and below you can read how to create a test for that type of app.
-
-> __Important!__
-><br>
-><br>
-> As of Test Studio release __R3 2020 SP1 (v.2020.3.1209)__ Silverlight Out-of-Browser testing in Test Studio is no longer visible in the main Test Studio user interface. If you want to continue using it, see <a href="#enable-silverlight-out-of-browser-in-test-studio-2020-r3-sp-release">here</a> how to enable it.
-
-__Important Notes:__
-
-* If you are testing a Silverlight In-Browser web application, we recommend treating it as a standard <a href="/automated-tests/recording/overview" target="_blank">Web Test</a> with no additional configuration.
-
-* See <a href="http://msdn.microsoft.com/en-us/library/dd550721(v=vs.95).aspx" target="_blank">here</a> for what constitutes Out-of-Browser.
-
-* Once a Silverlight Out-of-Browser application is configured for recording, Test Studio modifies its shortcut to point directly to the application's location on disk. This replaces the Microsoft "offline://" notation. The side effect of this is that your application will not detect that it is running in Out-of-Browser mode and code must be written in the application to work around this limitation.
-
-* Test Studio does not support the Web Browser control in Silverlight Out-of-Browser applications.
-
-1. Launch Test Studio.
-2. Click __Telerik > Test Studio > Create New Test Project__.
-
-	![Create test project][1]
-
-3. Choose __Telerik > Test > VB or C# Test Studio Project__, name the project, and click __OK__.<br> 
-
-	**Note:** As of version 2015.3.1202 Test Studio projects will appear only under **.NET Framework 4.5** or higher.
-
-	![Create C#/VB project][2]
-
-
-4. A Web Test is added to the project. Open it and click the __Configure Silverlight App__ icon in the toolbar.
-
-	![Configure SL App][3]
-
-5. Check the __Configure this test to run against a Silverlight application__ box in Out-Of-Browser options.
-6. Browse for the Local Application Directory or drag and drop a link to your Silverlight application.
-7. Select __Silverlight Out-of-Browser__ under __Recording Host__.
-
-	![Recording host][4]
-
-8. Click __Record__ to launch the out-of-browser app with the recording toolbar docked at the top.
-
-![Recording test][5]
-
-Notice that steps are added to the test as actions are taken within the application.
-
-## Enable Silverlight Out-Of-Browser in Test Studio 2020 R3 SP Release
-
-The icon to configure a test for __Silverlight-Out-Of-Browser__ application testing is __removed in Test Studio release R3 SP 2020 (v.2020.3.1209)__. You still can bring up the icon back in the product.
-
-Open the Windows Registry Editor and navigate to key _HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Telerik\TestStudio_. Add a new string type key named _ShowSilverlightOutOfBrowser_ and set its value to _true_. Restart Test Studio and the Silverlight-Out-Of-Browser icon will appear back in the _test options_.
-
-[1]: /img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig1.png
-[2]: /img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig2.png
-[3]: /img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig3.png
-[4]: /img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig4.png
-[5]: /img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig5.png
diff --git a/docs/archived-docs/recorder/step-suggestions-archive.md b/docs/archived-docs/recorder/step-suggestions-archive.md
deleted file mode 100644
index 823c29b3..00000000
--- a/docs/archived-docs/recorder/step-suggestions-archive.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Step Builder
-page_title: Step Builder
-description: "Archived documentation 2020 R2 and earlier"
-position: 1
----
-# Step Builder Version 2020 R2 and Earlier#
-
-> **Note**
-> <br>
-> Information about the Step Builder during recording in the latest release of Test Studio can be found <a href="/features/recorder/advanced-recording-tools/element-steps/steps-overview" target="_blank">here</a>.
-
-The Step Builder provides options for adding steps based on the selected element in the DOM tree during a recording session.
-
-![Step Builder In Record Mode][6]
-
-The Step Builder on project level can also be used to build steps against already recorded elements in the Elements repository.
-
-1.&nbsp; Click the **Step Builder** tab in the lower right corner.
-
-2.&nbsp; The **Step Builder** pane appears. Now select an element from the <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a>  to see the suggested action and verification steps for it.
-
-3.&nbsp; Select the action or verification you want to create and click **Add Step** button.
-
-<table id="no-table">
-	<tr>
-		<td>![TS][4] <br><br>**Standalone version**</td>
-		<td>![VS][2] <br><br>**VS plugin**</td>
-	</tr>
-<table>
-
-4.&nbsp; Or insert a <a href="/features/custom-steps/overview" target="_blank">custom step</a> from the **General** section.
-
-![Custom steps][5]
-
-> If you work very frequently with the Step Builder you can <a href="/features/custom-layout/custom-layout" target="_blank">dock</a> it as a separate pane.
-
-[1]: /img/archived-docs/test-recording/step-suggestions/fig1.png
-[2]: /img/archived-docs/test-recording/step-suggestions/fig2.png
-[3]: /img/archived-docs/test-recording/step-suggestions/fig3.png
-[4]: /img/archived-docs/test-recording/step-suggestions/fig4.png
-[5]: /img/archived-docs/test-recording/step-suggestions/fig5.png
-[6]: /img/archived-docs/test-recording/step-suggestions/step-builder-recorder.png
diff --git a/docs/archived-docs/results/migrate-database-archive.md b/docs/archived-docs/results/migrate-database-archive.md
deleted file mode 100644
index 0e04199b..00000000
--- a/docs/archived-docs/results/migrate-database-archive.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Migrate from SQL to MongoDB
-page_title: Migrate from SQL to MongoDB
-description: "Test Studio MongoDB storage service. Transfer old SQL results (prior 15th of October 2015) to the new Mongo database"
-position: 4
----
-# Migrate from SQL to MongoDB
-
-Since Test Studio R3 release in October 2015 (v.2015.3.1015) we have introduced a new improved storage server using MongoDB database instead of SQL database. You will be able to transfer your old results (prior 15th of October 2015) to the new Mongo database using <a href="http://docs.telerik.com/teststudio/downloads/DbMigratorExe.zip">this tool</a>. 
-
-> Note that you must have the <a href="http://docs.telerik.com/teststudio/features/scheduling-test-runs/create-storage-server" target="_blank">Storage Server</a> already configured.
-
-Once you download the tool, extract the content on your hard drive and run the DBMigrator.exe
-
-![DBMigrator.exe][1]
-
-The tool will open and you will have to fill the following fields:
-
-![Mogration tool][2]
-
-- Source - this should be the SQL connection string you were using to connect to your SQL database
-- Destination - this is the new MongoDB connection string
-
-> You can get both connection strings from the following file: **CloudStorageSelfHost.exe.config** located in:
-> *C:\Program Files (x86)\Progress\Test Studio\StorageService*
-
- 
-
-Once you fill the fields as demonstrated above click the **Migrate** button. You will have to allow certain time (depends on how large is your database) in order to migrate the results to the MongoDB database.
-
-![wait][3]
-
-Once done you should be able to view your scheduling results in the <a href="http://docs.telerik.com/teststudio/getting-started/test-results/calendar" target="_blank">Calendar</a> after clicking the Reload button.
-
-[1]: /img/features/scheduling-test-runs/migrate-database/fig1.png
-[2]: /img/features/scheduling-test-runs/migrate-database/fig2.png
-[3]: /img/features/scheduling-test-runs/migrate-database/fig3.png
\ No newline at end of file
diff --git a/docs/archived-docs/results/reports-archive.md b/docs/archived-docs/results/reports-archive.md
deleted file mode 100644
index ce2b0162..00000000
--- a/docs/archived-docs/results/reports-archive.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Test List Reports 
-page_title: Test List Reports
-description: "Test Studio Test List Results Reports. Generate report based on the test list results"
-position: 6
----
-# Reports 
-
-With the expanded reporting functionality, spotting test pass/failure trends and identifying weak spots in tested applications is swift and effortless. From the **Reports** tab, you have the ability to:
-
-* To explore test list results over time.
-
-* Experience enhanced visualization of test results through interactive graphs and charts.
-
-* Export reports as a PNG image or HTML file.
-
-* Leave comments within reports.
-
-## 2016 R3 Version and Earlier
-
-Select a test list from the first drop-down menu, specify a date range, and enable or disable the pass/fail lines. A bar graph is populated with Run Results on the X-axis by date/time and number of Tests in List on the Y-axis.
-
-![Charts][1]
-
-You can generate more meaningful graphs that support drill-downs, as well as having single test list results displayed in easy-to-read pie charts.
-
-To do so, click on the bar for which you want more information, and you are taken to the **Results** tab.
-
-* Switch between the pie chart report and the calendar view.
-
-* View previous and next results for the selected test list.
-
-* Add comments.
-
-* Drill down further into each test and its steps in the **Test Results** pane.
-
-![Pie][2]
-
-[1]: /img/general-information/test-results/reports/fig1.png
-[2]: /img/general-information/test-results/reports/fig2.png
\ No newline at end of file
diff --git a/docs/archived-docs/results/visual-studio-2012-and-later-test-list.md b/docs/archived-docs/results/visual-studio-2012-and-later-test-list.md
deleted file mode 100644
index a7f2d7a5..00000000
--- a/docs/archived-docs/results/visual-studio-2012-and-later-test-list.md
+++ /dev/null
@@ -1,50 +0,0 @@
----
-title: Test Lists in Visual Studio 2010 
-page_title: Test Lists in Visual Studio 2010
-description: "Test Studio Test Lists in Visual Studio. test lists are deprecated in Visual Studio 2012"
-position: 10
----
-# Test Lists in Visual Studio 2010 (Deprecated)
-
-Although test lists are deprecated in Visual Studio 2012 you can still use them:
-
-1. From the Solution Explorer right click the **Solution** and select **Add -> New item**.
-
-	![Add item][1]
-
-2. Type in the text box 'TestList.vsmdi' or any other item name that ends with '.vsmdi' and click add.
-
-	![Add .vsmdi file][2]
-
-	**Note:** make sure not to click on any item as it would overwrite your input.
-
-3. The .vsmdi file is created in 'Solution Items' sub folder right under your solution.
-
-	![Solution items][3]
-
-4. Double click TestList.vsmdi and which brings up the 'Test List Editor' in Visual Studio.
-
-	![Test List Editor][4]
-
-5. Right click **Lists of Tests** and select **New Test List**.
-
-	![Create new test list][5]
-
-6. Name the Test List and click **OK**.
-
-	![Name the test][6]
-
-7. Click **All Loaded Tests** and drag the test you want into the **TestList1**. You can use Ctrl/Shift + Click to select multiple tests.
-
-	![Add test to the test list][7]
-
-> You can only create a test list and edit it in Visual Studio 2012 and later. In order to execute the test list you need to use <a href="/features/test-runners/mstest" target="_blank">**MSTest**</a> via the command line.
-	
-
-[1]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig1.png
-[2]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig2.png
-[3]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig3.png
-[4]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig4.png
-[5]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig5.png
-[6]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig6.png
-[7]: /img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig7.png
diff --git a/docs/archived-docs/upload-latest-files-archive.md b/docs/archived-docs/upload-latest-files-archive.md
deleted file mode 100644
index 2e6ba360..00000000
--- a/docs/archived-docs/upload-latest-files-archive.md
+++ /dev/null
@@ -1,22 +0,0 @@
----
-title: Upload To Storage
-page_title: Upload Latest Project Files
-description: You have recurring test list scheduled and you need to make some change in the test list such as editing a particular test case, add or remove tests etc. You can force uploading the changes to the database
-position: 7
----
-# Upload Latest Project Files to Storage Database
-
-## Automatic Upload of Recent Changes
-
-If you continue working within a project in which there are upcoming scheduled test lists and you attempt to save these, you will get a <a href="/features/scheduling-test-runs/schedule-execution#automatically-upload-changed-project-files-to-storage" target="_blank">notification for automatic upload of the changes</a>.
-
-Once you choose an option and select to not be prompted in the future, the selected option will be applied by each next *Save All* action performed in the project. However, you may need to change your initial selection and here are the steps to follow to get prompted with that message again:
-
-1. Open the project's root folder and open the *Settings.aiis* file with a text editor (Notepad++ for example). 
-2. Find the Project ID value and note it somewhere.
-3. Go to *C:\Users\\\<yourUserName>\AppData\Roaming\ArtOfTest* folder and locate a file named *PerUserSettings.json*.
-4. Open that file with a text editor again and locate the Project ID under "SkipUploadScheduledJobToStoragePromptPerProject" setting. Delete the project's id and save the file.
-
-Then when you start the project again, make any change and select Save All, the dialog will prompt you again and you could choose the desired option to automatically update the files. That way all changes will be reflected in the database whenever you *Save All*.
-
-[1]: /img/knowledge-base/scheduling-kb/upload-latest-files/fig1.png
\ No newline at end of file
diff --git a/docs/automated-tests/coded-tests/add-assembly-reference.md b/docs/automated-tests/coded-tests/add-assembly-reference.md
index 38c34abd..38e7b367 100644
--- a/docs/automated-tests/coded-tests/add-assembly-reference.md
+++ b/docs/automated-tests/coded-tests/add-assembly-reference.md
@@ -28,8 +28,6 @@ Once the external class library is referenced in the project you need to add `us
 
 ![List the dll in Code behind][5]
 
-[1]: /img/advanced-topics/coded-steps/add-assembly-reference/fig1.png
 [2]: /img/advanced-topics/coded-steps/add-assembly-reference/fig2.png
 [3]: /img/advanced-topics/coded-steps/add-assembly-reference/fig3.png
-[4]: /img/advanced-topics/coded-steps/add-assembly-reference/fig4.png
 [5]: /img/advanced-topics/coded-steps/add-assembly-reference/fig5.png
\ No newline at end of file
diff --git a/docs/automated-tests/coded-tests/compile-project.md b/docs/automated-tests/coded-tests/compile-project.md
index e9a23935..89d430c5 100644
--- a/docs/automated-tests/coded-tests/compile-project.md
+++ b/docs/automated-tests/coded-tests/compile-project.md
@@ -24,5 +24,4 @@ The output of the compilation process is displayed in the <a href="/features/cod
 ![Output panel][2]
 
 [1]: /img/features/coded-steps/compile-project/fig1.png
-[2]: /img/features/coded-steps/compile-project/fig2.png
-[3]: /img/features/coded-steps/compile-project/fig3.png
\ No newline at end of file
+[2]: /img/features/coded-steps/compile-project/fig2.png
\ No newline at end of file
diff --git a/docs/automated-tests/coded-tests/output-panel.md b/docs/automated-tests/coded-tests/output-panel.md
index e028f8d8..d9655da5 100644
--- a/docs/automated-tests/coded-tests/output-panel.md
+++ b/docs/automated-tests/coded-tests/output-panel.md
@@ -30,9 +30,7 @@ Under the **Source Control** tab can be found information about the actions take
 
 ![Source Control][4]
 
-
 [1]: /img/features/coded-steps/output-panel/fig1.png
 [2]: /img/features/coded-steps/output-panel/fig2.png
 [3]: /img/features/coded-steps/output-panel/fig3.png
 [4]: /img/features/coded-steps/output-panel/fig4.png
-[5]: /img/features/coded-steps/compile-project/fig1.png
diff --git a/docs/automated-tests/continuous-integration/continious-integration-overview.md b/docs/automated-tests/continuous-integration/continious-integration-overview.md
index 10f3f62a..16f01fe8 100644
--- a/docs/automated-tests/continuous-integration/continious-integration-overview.md
+++ b/docs/automated-tests/continuous-integration/continious-integration-overview.md
@@ -22,7 +22,7 @@ This article provides the requirements from Test Studio perspective to setup the
     
     __Tip:__ The only exception is if the executed tests are <a href="/automated-tests/headless/headless-test-execution" target="_blank">web test run in headless browser mode</a>. 
 
-* CI agent app running in console mode. 
+* CI agent app running in __console mode__. 
     
     __Tip:__ The only exception is if the executed tests are web test run in headless browser mode.
 
@@ -52,16 +52,16 @@ This article provides the requirements from Test Studio perspective to setup the
 
     > __Tip__
     > <br>
-    > Use the Test Studio built-in options to control the user session. These options are available in the <a href="/advanced-topics/build-server/ts-test-runner-app" target="_blank">Test Studio Test Runner application</a> which gets installed with the Run-time Edition. 
+    > Use the __Test Studio built-in options to control the user session__. These options are available in the <a href="/advanced-topics/build-server/ts-test-runner-app" target="_blank">Test Studio Test Runner application</a> which gets installed with the Run-time Edition. 
 
 ## Examples of Implementing Test Studio Tests in Different CI Pipelines
 
 Find out few examples of setting a pipeline on specific platform and follow the instructions on how to implement Test Studio test runs in it. 
 
-* <a href="/advanced-topics/build-server/azure-devops" target="_blank">Azure DevOps Classic Pipeline using self-hosted agent</a>
+* <a href="/advanced-topics/build-server/azdo/azdo-pipelines-and-test-studio-tests" target="_blank">Azure DevOps pipelines </a>
+* * <a href="/advanced-topics/build-server/docker-container-testing" target="_blank">Testing in Docker Container</a> - applicable for headless browser testing only. 
 * <a href="/advanced-topics/build-server/jenkins-ci" target="_blank">Jenkins CI</a>
 * <a href="/advanced-topics/build-server/team-city-builds" target="_blank">TeamCity</a>
-* <a href="/advanced-topics/build-server/bamboo" target="_blank">Bamboo</a>
 * <a href="/advanced-topics/build-server/cruise-control.net-builds" target="_blank">CruiseControl .Net</a>
-* <a href="/advanced-topics/build-server/docker-container-testing" target="_blank">Testing in Docker Container</a> - applicable for headless browser testing only. 
-* <a href="/advanced-topics/build-server/microsoft-hosted-agent-testing" target="_blank">Azure DevOps Classic Pipeline using Microsoft-hosted agent</a> - applicable for headless browser testing only.
+* <a href="/advanced-topics/build-server/bamboo" target="_blank">Bamboo</a>
+
diff --git a/docs/automated-tests/customize-project/built-in-help-tools/guided-tutorials.md b/docs/automated-tests/customize-project/built-in-help-tools/guided-tutorials.md
deleted file mode 100644
index 92ec1a76..00000000
--- a/docs/automated-tests/customize-project/built-in-help-tools/guided-tutorials.md
+++ /dev/null
@@ -1,42 +0,0 @@
----
-title: Guided Tutorials
-page_title: Guided Tutorials
-description: "Test Studio guided tutorials. Get started with Test Studio with interactive guided tutorials. "
-position: 1
-publish: false
----
-# Guided Tutorials
-
-Have a smooth getting started experience with the guided interactive tutorials built-in in Test Studio.
-
-## Start a Guided Tutorial
-
-You can start a tutorial from the Test Studio [**Welcome Screen**](/automated-tests/customize-project/welcome-screen#get-started) or from within the product.
-
-<table id="no-table">
-<tr>
-<td>![Welcome Screen][1]<br>**Start from Welcome Screen**</td>
-<td>![In-product][2]<br>**Start In-Product**</td>
-<tr>
-<table>
-
-## Scenarios to Guide You Through
-
-Each of the interactive scenarios will guide you through the minimum required steps to start automating tests with Test Studio:
-
-- record a test
-- execute a successful test
-- explore the [step failure details]() after executing a failing test
-
-When you start a tutorial, the Test Studio window gets grayed out, while the element on focus stays active, and you see a hint with the required action.
-
-![Start Tutorial][3]
-
-The hints popup contains information about the upcoming steps and allows you to stop the tutorial at any time. You can also use the *'Escape'* button on your keyboard to end the tutorial.
-
-![Tutorial Message][4]
-
-[1]: /img/automated-tests/customize-project/guided-tutorials/fig1.png
-[2]: /img/automated-tests/customize-project/guided-tutorials/fig2.png
-[3]: /img/automated-tests/customize-project/guided-tutorials/fig3.png
-[4]: /img/automated-tests/customize-project/guided-tutorials/fig4.png
diff --git a/docs/automated-tests/customize-project/built-in-help-tools/in-product-guides.md b/docs/automated-tests/customize-project/built-in-help-tools/in-product-guides.md
index 25b12486..a588fbda 100644
--- a/docs/automated-tests/customize-project/built-in-help-tools/in-product-guides.md
+++ b/docs/automated-tests/customize-project/built-in-help-tools/in-product-guides.md
@@ -16,20 +16,17 @@ The areas for which a guide is available have the __Rocket__ icon in the ribbon.
 
 Guides are available for __Elements__ and __Tests__ panes. The __Rocket__ icon appears in the upper ribbon, which is active for an opened test or when you modify an element's find expression or image. 
 
-<table id=web-test>
-	<tr>![Tests Ribbon Web test][2]</tr>
-	<tr>Tests Ribbon Guide</tr>
-<table>
-
-<table id=elements>
-	<tr>![Element Ribbon][2a]</tr>
-    <tr>Elements Ribbon Guide</tr>
-<table>
-
-<table id=load-test>
-	<tr>![Tests Ribbon Load Test][2b]</tr>
-	<tr>Tests Ribbon Guide for Load Test</tr>
-<table>
+<table id=web-test style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+	
+![Tests Ribbon Web test][2]<br> Tests Ribbon Guide</tr>
+<tr style="text-align: center; background-color: transparent; border:none;">
+
+![Element Ribbon][2a]<br>Elements Ribbon Guide</tr>
+<tr style="text-align: center; background-color: transparent; border:none;">
+
+![Tests Ribbon Load Test][2b]<br>Tests Ribbon Guide for Load Test</tr>
+</table>
 
 The Rocket icon is also available in the __[Project Explorer](/features/project-explorer/overview)__ and __[Element Explorer](/features/elements-explorer/overview)__.
 
diff --git a/docs/automated-tests/customize-project/custom-layout.md b/docs/automated-tests/customize-project/custom-layout.md
index 479ccc64..0bbca19a 100644
--- a/docs/automated-tests/customize-project/custom-layout.md
+++ b/docs/automated-tests/customize-project/custom-layout.md
@@ -77,12 +77,16 @@ If you want to place the panel separately, you can use the arrows on the right,
 
 If you select the center of the target panel, the undocked panel will appear as a tab next to the target panel.
 
-<table id=no-table>
-	<tr>
-		<td>![choose center][5]</td>
-		<td>![tabs][6]</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="background-color: transparent; border:none;">
+		<td>
+
+![choose center][5]</td>
+<td>
+
+![tabs][6]</td>
+</tr>
+</table>
 
 ### Hide or Show a Panel
 
@@ -150,7 +154,7 @@ Test Studio comes with a __Light__ and __Dark__ theme. Choose the one that suits
 [4a]: /img/automated-tests/customize-project/custom-layout/fig4a.png
 [5]: /img/automated-tests/customize-project/custom-layout/fig5.png
 [6]: /img/automated-tests/customize-project/custom-layout/fig6.png
-[7]: /img/automated-tests/customize-project/custom-layout/fig7.png
+
 [8a]: /img/automated-tests/customize-project/custom-layout/fig8a.png
 [8]: /img/automated-tests/customize-project/custom-layout/unpin-pane.gif
 [8b]: /img/automated-tests/customize-project/custom-layout/show-and-pin-pane.gif
diff --git a/docs/automated-tests/customize-project/welcome-screen.md b/docs/automated-tests/customize-project/welcome-screen.md
index 51692a47..4442d30e 100644
--- a/docs/automated-tests/customize-project/welcome-screen.md
+++ b/docs/automated-tests/customize-project/welcome-screen.md
@@ -92,10 +92,10 @@ The __News Feed__ section lists important news related to the product, links to
 
 ![Newsfeed][7]
 
-[1]: /img/automated-tests/customize-project/welcome-screen/fig1.png
-[2]: /img/automated-tests/customize-project/welcome-screen/fig2.png
-[3]: /img/automated-tests/customize-project/welcome-screen/fig3.png
+
+
+
 [4]: /img/automated-tests/customize-project/welcome-screen/fig4.png
 [5]: /img/automated-tests/customize-project/welcome-screen/fig5.png
-[6]: /img/automated-tests/customize-project/welcome-screen/fig6.png
+
 [7]: /img/automated-tests/customize-project/welcome-screen/fig7.png
diff --git a/docs/automated-tests/data-drive-test/data-binding-in-code.md b/docs/automated-tests/data-drive-test/data-binding-in-code.md
index 45d3bb74..1a9f6cb4 100644
--- a/docs/automated-tests/data-drive-test/data-binding-in-code.md
+++ b/docs/automated-tests/data-drive-test/data-binding-in-code.md
@@ -11,59 +11,49 @@ Test Studio allows you to insert any custom code in the tests - that includes th
 Given that, you may need to use the values from the data source in coded steps and this article describes how to access the data columns through code.
 
 
-#### __[C#]__
-
-	{{region }}
-
+````C#
 	//Reference a column by name
 	Pages.Bing.SbFormQText.Text = Data["Numbers"].ToString();
 
 	//Reference a column by index (zero based)
 	Pages.Bing.SbFormQText.Text = Data[0].ToString();
-
-	{{endregion}}
-
-#### __[VB]__
-
-	{{region }}
-
+````
+````VB
 	'Reference a column by name
 	Pages.Bing.SbFormQText.Text = Data("Numbers").ToString()
 
 	'Reference a column by index (zero based)
 	Pages.Bing.SbFormQText.Text = Data(0).ToString()
+````
 
-	{{endregion}}
-
-
-```C#
+````C#
 //Reference a column by name
 Pages.Bing.SbFormQText.Text = Data["Col1"].ToString();
   
 //Reference a column by index (zero based)
 Pages.Bing.SbFormQText.Text = Data[0].ToString();
-```
-```VB
+````
+````VB
 'Reference a column by name
 Pages.Bing.SbFormQText.Text = Data("Col1").ToString()
  
 'Reference a column by index (zero based)
 Pages.Bing.SbFormQText.Text = Data(0).ToString()
-```
+````
 
 This method can also be applied to a **Verification**:
 
-```C#
+````C#
 //Reference a column by name
 Assert.IsTrue(ActiveBrowser.ContainsText(Data["Col1"].ToString()));
   
 //Reference a column by index (zero based)
 Assert.IsTrue(ActiveBrowser.ContainsText(Data[0].ToString()));
-```
-```VB
+````
+````VB
 'Reference a column by name
 Assert.IsTrue(ActiveBrowser.ContainsText(Data("Col1").ToString()))
  
 'Reference a column by index (zero based)
 Assert.IsTrue(ActiveBrowser.ContainsText(Data(0).ToString()))
-```
+````
diff --git a/docs/automated-tests/data-drive-test/data-driven-image-verification.md b/docs/automated-tests/data-drive-test/data-driven-image-verification.md
index 6ad5ef87..9ba7afdd 100644
--- a/docs/automated-tests/data-drive-test/data-driven-image-verification.md
+++ b/docs/automated-tests/data-drive-test/data-driven-image-verification.md
@@ -14,7 +14,7 @@ To data bind an <a href="/features/recorder/verifications/image-verification" ta
 
 1. Perform the verification in a <a href="/features/custom-steps/script-step" target="_blank">coded step</a> as demonstrated below:
 
-```C#
+````C#
 // get an image of MyImage element        
 System.Drawing.Bitmap bitmap = Pages.MyPage.MyImage.Capture();
 
@@ -39,8 +39,8 @@ double tolerance = 10D;
 
 // Assert statement 
 ArtOfTest.Common.UnitTesting.Assert.IsTrue(tolerance >= compareValue); 
-```
-```VB
+````
+````VB
 
 Dim bitmap As System.Drawing.Bitmap = Pages.MyPage.MyImage.Capture()
 
@@ -59,7 +59,7 @@ Dim compareValue As Double = (histogram.Compare(histogramToCompare) * 100)
 Dim tolerance As Double = 10.0
 
 ArtOfTest.Common.UnitTesting.Assert.IsTrue(tolerance >= compareValue)
-```
+````
 
 To complete this scenario using the provided sample:
 
diff --git a/docs/automated-tests/data-drive-test/ddt-results.md b/docs/automated-tests/data-drive-test/ddt-results.md
index 5c0ca052..90d17e94 100644
--- a/docs/automated-tests/data-drive-test/ddt-results.md
+++ b/docs/automated-tests/data-drive-test/ddt-results.md
@@ -35,16 +35,20 @@ Click the **Execute** button in the **Test** ribbon. The test steps are executed
 
 - The summary shows the result for the selected iteration.
 
-<table id="no-table">
-<tr>
-<td>![Test Studio product iteration](/img/automated-tests/data-drive-test/ddt-results/ts-product-iteration.png)</td>
-<td>![Random string product iteration](/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png)</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Test Studio product iteration](/img/automated-tests/data-drive-test/ddt-results/ts-product-iteration.png)</td>
+<td>
+
+![Random string product iteration](/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png)</td>
 </tr>
-<tr>
-<td>_Test Studio product iteration_</td>
-<td>_Random string product iteration_</td>
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>Test Studio product iteration</td>
+<td>Random string product iteration</td>
 </tr>
-<table>
+</table>
 
 - The drop-down menu contains a list with all iterations and shows the used value from the data table.
 - Expand the drop-down menu to view the list and select an iteration to see the results for it.
@@ -54,16 +58,20 @@ Click the **Execute** button in the **Test** ribbon. The test steps are executed
 - *Test Studio* and *Kendo* were both part of the text in the first listed search result, thus the verification that the search is valid was successful.
 - The random string did not appear in the first listed search result, so the last iteration failed.
 
-<table id="no-table">
-<tr>
-<td>![Kendo product iteration](/img/automated-tests/data-drive-test/ddt-results/kendo-product-iteration.png)</td>
-<td>![Random string product iteration](/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png)</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Kendo product iteration](/img/automated-tests/data-drive-test/ddt-results/kendo-product-iteration.png)</td>
+<td>
+
+![Random string product iteration](/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png)</td>
 </tr>
-<tr>
-<td>_Kendo product iteration_</td>
-<td>_Random string product iteration_</td>
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>Kendo product iteration</td>
+<td>Random string product iteration</td>
 </tr>
-<table>
+</table>
 
 ### Execution Log Results
 
diff --git a/docs/automated-tests/data-drive-test/help-file-for-docs.md b/docs/automated-tests/data-drive-test/help-file-for-docs.md
deleted file mode 100644
index 4940d610..00000000
--- a/docs/automated-tests/data-drive-test/help-file-for-docs.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Help file
-page_title: help file
-position: 1
-publish: false
----
-
-
-## Local data binding
-open the <a href="/features/test-maintenance/test-step-properties" target="_blank">_Step Properties pane_</a>. 
-
-1. The ___Bindings___ property is the first in the list. Click the three dots button on the right to open the step fields that you can bind to data.
-
-    ![enter-text-properties](/img/automated-tests/data-drive-test/local-data-driven-test/enter-text-properties.png)
-
-    > __Note__
-    ><br>
-    ><br>
-    > Depending on the <a href="/automated-tests/customize-project/custom-layout" target="_blank">project layout</a> you are using, the _Properties pane_ can have a different location within your project.
-
-    The _Enter text_ step allows only its ___Text___ field to be data driven and, thus, this is the only one listed.
-
-1. Click on the drop-down next to the  ___Text___ field to expand the data source columns list. In this scenario a single column is in the list - the _`productName`_, so select this one.
-
-    ![select-column](/img/automated-tests/data-drive-test/local-data-driven-test/select-column.png)
-
-1. Click the _Set_ button to confirm the selection and close the _Properties pane_.
-
-    ![set-binding](/img/automated-tests/data-drive-test/local-data-driven-test/set-binding.png)
-
-    > __Tip__
-    ><br>
-    ><br>
-    > See <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">How to bind a step to a data source column</a> for more information.
-
-1. Apply the same sequence of steps for the wait step. We add a wait step to verify that the search action is completed successfully. Note that the field that you need to bind in the wait step properties is `TextToMatch`.
-
-    ![wait-step-binding](/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-binding.png)
-
-
-## External data source binding
-
-1. Click on the __Enter text__ step (number 3. for the current scenario) and open the <a href="/features/test-maintenance/test-step-properties" target="_blank">_Step Properties pane_</a>.
-
-1. The ___Bindings___ property is the first in the list. Click the three dots button on the right to open the step fields that you can bind to data.
-
-    ![enter-text-properties](/img/automated-tests/data-drive-test/local-data-driven-test/enter-text-properties.png)
-
-    > __Note__
-    ><br>
-    ><br>
-    > Depending on the <a href="/automated-tests/customize-project/custom-layout" target="_blank">project layout</a> you are using, the _Properties pane_ can have a different location within your project.
-
-    The _Enter text_ step allows only its _Text_ field to be data driven and this is the only one listed.
-
-1. Click on the drop-down next to the  ___Text___ field to expand the data source columns list. In this scenario a single column is in the list - the _`productName`_, so select this one.
-
-    ![select-column](/img/automated-tests/data-drive-test/local-data-driven-test/select-column.png)
-
-1. Click on the _Set_ button to confirm the selection and close the _Properties pane_.
-
-    ![set-binding](/img/automated-tests/data-drive-test/local-data-driven-test/set-binding.png)
-
-    > __Tip__
-    ><br>
-    ><br>
-    > See <a href="/features/data-driven-testing/attach-columns-input-values" target="_blank">How to bind a step to a data source column</a> for more information.
-
-1. Apply the same sequence of steps for the wait step. We add a wait step to verify that the search action is completed successfully. Note that the field that you need to bind in the wait step properties is ___`TextToMatch`___.
-
-    ![wait-step-binding](/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-binding.png)
\ No newline at end of file
diff --git a/docs/automated-tests/desktop-testing/demo-desktop-test.md b/docs/automated-tests/desktop-testing/demo-desktop-test.md
index 11e662a3..fbf05f00 100644
--- a/docs/automated-tests/desktop-testing/demo-desktop-test.md
+++ b/docs/automated-tests/desktop-testing/demo-desktop-test.md
@@ -57,15 +57,15 @@ Launch the Inspect tool and highlight the desired element to reveal its properti
 
 Make sure you have the following using statements included: 
 
-```C#
+````C#
     using ArtOfTest.WebAii.DesktopAutomation; 
     using ArtOfTest.WebAii.DesktopAutomation.Controls; 
     using ArtOfTest.WebAii.DesktopAutomation.FindExpressions; 
-```
+````
 
 By following the below code flow, users can automate the selection of a radio button within a Windows desktop application using the Test Studio Framework.
 
-```C#
+````C#
     //The code begins by obtaining the root element of the desktop using ‘DesktopElement.FromDesktopRoot()’. 
 
     var desktop = DesktopElement.FromDesktopRoot(); 
@@ -84,7 +84,7 @@ By following the below code flow, users can automate the selection of a radio bu
     //Finally, the code selects the radio button: 
 
     radioButton.Select(); 
-```
+````
 
 ### DesktopInvokePattern Example
 
@@ -92,7 +92,7 @@ Test Studio also provides support for invoking patterns on desktop applications.
 
 Here are the general steps to use the `DesktopInvokePattern` with the radio button from the  above example. 
 
-```C#
+````C#
     //Find the targer UI element 
     var desktop = DesktopElement.FromDesktopRoot(); 
 
@@ -104,7 +104,7 @@ Here are the general steps to use the `DesktopInvokePattern` with the radio butt
 
     //Invoke the desired action 
     invokePattern.Invoke(); 
-```
+````
 
 ## Automation Properties
 
diff --git a/docs/automated-tests/desktop-testing/desktop-app-user-model-id.md b/docs/automated-tests/desktop-testing/desktop-app-user-model-id.md
index 1b638c4e..f158a7ce 100644
--- a/docs/automated-tests/desktop-testing/desktop-app-user-model-id.md
+++ b/docs/automated-tests/desktop-testing/desktop-app-user-model-id.md
@@ -20,7 +20,7 @@ The <a href="https://docs.microsoft.com/en-us/windows/win32/shell/appids" target
 
 2.&nbsp; __Copy the below script and paste__ it in the PowerShell console. Press __Enter__ to execute it.
 
-```
+````
 $listOfAppUserModelIds = @()
 
 foreach ($app in get-AppxPackage)
@@ -39,7 +39,7 @@ foreach ($app in get-AppxPackage)
 }
 
 $listOfAppUserModelIds
-```
+````
 ![Paste script in PowerShell console](/img/automated-tests/desktop-testing/user-model-id/fig2.png)
 
 3.&nbsp; The script iterates through the installed applications and __outputs a list with their User Model ID__ - every app ID is on a new line. 
@@ -57,7 +57,7 @@ Usually the name of the application is part of the User Model ID and you can use
 
 Let's use the _Windows Calculator_ app as an example - the filter parameter for this application is `| Select-String -Pattern 'Calculator'` and is added on the last line.
 
-```
+````
 $listOfAppUserModelIds = @()
 
 foreach ($app in get-AppxPackage)
@@ -76,7 +76,7 @@ foreach ($app in get-AppxPackage)
 }
 
 $listOfAppUserModelIds | Select-String -Pattern 'Calculator'
-```
+````
 ![Filtered list of app ids in PowerShell console](/img/automated-tests/desktop-testing/user-model-id/fig4.png)
 
 >__Note__
diff --git a/docs/automated-tests/elements/element-repository.md b/docs/automated-tests/elements/element-repository.md
index 11422ca2..c09346f1 100644
--- a/docs/automated-tests/elements/element-repository.md
+++ b/docs/automated-tests/elements/element-repository.md
@@ -16,7 +16,7 @@ When a test project is loaded, all the elements from all tests are merged into t
 
 With this approach there should be no problem having two people working on the same test project at the same time. As soon as person two gets the latest files from the source control repository and reloads the test project, the elements from any newly created tests will automatically get merged into the Element Repository for person two.
 
-### What is the Pages.g.cs/vb file? Do I need to merge the Pages.g.cs/vb file created by different developers? ###
+### What is the Pages.g.cs/vb file? Do I need to merge the Pages.g.cs/vb file created by different developers? 
 
 The Pages.g.cs file (or Pages.g.vb file in VB test projects) is normally a hidden file. It is automatically generated by Test Studio and is only used by coded test steps. Test Studio generates this file from the elements contained in the element repository, which are displayed in the Elements Explorer.
 
@@ -32,8 +32,8 @@ You do not, and should not ever change its contents. Any changes you try to make
 
 Since this file is automatically generated, it should not be checked into your source control repository. Test Studio does all the work to generate and maintain this file for you.
 
-### How is the Element Repository used during test execution? ###
+### 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.
 
-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).
+During test execution, the root Page node is not actually used to locate the element. The execution engine only uses the Frame, 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/automated-tests/elements/find-element.md b/docs/automated-tests/elements/find-element.md
index e7370958..2bf05785 100644
--- a/docs/automated-tests/elements/find-element.md
+++ b/docs/automated-tests/elements/find-element.md
@@ -13,7 +13,7 @@ In certain scenarios the automatically generated <a href="/features/elements-exp
 
 To verify what find expression for an element was automatically generated and edit it, if necessary, use the <a href="/features/elements-explorer/overview#element-context-menu" target="_blank">Element's Explorer context menu</a> or double click on the same element.
 
-<table id="no-table">
+<table id="no-table" style="border:none;">
 	<tr>
 		<td><img src="/img/features/elements-explorer/find-element/fig101.png" alt="Edit Element"></td>
 		<td><img src="/img/features/elements-explorer/find-element/fig102.png" alt="Edit Element Double Click"></td>
@@ -173,31 +173,30 @@ To filter an element's find expression using the column name from parent data so
 
 ![Bind Coded variable][120]
 
-[1]: /img/features/elements-explorer/find-element/fig1.png
-[2]: /img/features/elements-explorer/find-element/fig2.png
-[3]: /img/features/elements-explorer/find-element/fig3.png
-[4]: /img/features/elements-explorer/find-element/fig4.png
-[5]: /img/features/elements-explorer/find-element/fig5.png
-[6]: /img/features/elements-explorer/find-element/fig6.png
-[7]: /img/features/elements-explorer/find-element/fig7.png
-[8]: /img/features/elements-explorer/find-element/fig8.png
-[9]: /img/features/elements-explorer/find-element/fig9.png
-[10]: /img/features/elements-explorer/find-element/fig10.png
-[11]: /img/features/elements-explorer/find-element/fig11.png
-[12]: /img/features/elements-explorer/find-element/fig12.png
-[13]: /img/features/elements-explorer/find-element/fig13.png
-[14]: /img/features/elements-explorer/find-element/fig14.png
-[15]: /img/features/elements-explorer/find-element/fig15.png
-[16]: /img/features/elements-explorer/find-element/fig16.png
-[17]: /img/features/elements-explorer/find-element/fig17.png
-[18]: /img/features/elements-explorer/find-element/fig18.png
-[19]: /img/features/elements-explorer/find-element/fig19.png
-[20]: /img/features/elements-explorer/find-element/fig20.png
-[21]: /img/features/elements-explorer/find-element/fig21.png
-[101]: /img/features/elements-explorer/find-element/fig101.png
-[102]: /img/features/elements-explorer/find-element/fig102.png
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
+
 [103]: /img/features/elements-explorer/find-element/fig103.png
-[104]: /img/features/elements-explorer/find-element/fig104.gif
 [105]: /img/features/elements-explorer/find-element/fig105.png
 [106]: /img/features/elements-explorer/find-element/fig106.png
 [107]: /img/features/elements-explorer/find-element/fig107.png
diff --git a/docs/automated-tests/elements/frames.md b/docs/automated-tests/elements/frames.md
index 615722b2..36750c5c 100644
--- a/docs/automated-tests/elements/frames.md
+++ b/docs/automated-tests/elements/frames.md
@@ -49,13 +49,13 @@ These are frames, which have different __FrameInfo__ properties each time when t
 
 This usually happens when any of the frame properties are dynamic and don't match next time when the page and frame are loaded. There is an error message listed in the <a href="/automated-tests/test-results/analyze-quick-run-results#generate-the-quick-execution-log" target="_blank">test execution log</a>:
 
-   ```
-   Unable to find the target host (Browser/SilverlightApp) to locate an element. Failure: Waiting for frame '[Frame:id=<>,name=<>,src=<>,UseQuery:False]' timed out.
-   Error: Wait for condition has timed out
-      InnerException:
-   System.Exception: Unable to find the target host (Browser/SilverlightApp) to locate an element.
-   Failure: Waiting for frame '[Frame:id=<>,name=<>,src=<>,UseQuery:False]' timed out. Error: Wait for condition has timed out
-   ```
+````
+Unable to find the target host (Browser/SilverlightApp) to locate an element. Failure: Waiting for frame '[Frame:id=<>,name=<>,src=<>,UseQuery:False]' timed out.
+Error: Wait for condition has timed out
+   InnerException:
+System.Exception: Unable to find the target host (Browser/SilverlightApp) to locate an element.
+Failure: Waiting for frame '[Frame:id=<>,name=<>,src=<>,UseQuery:False]' timed out. Error: Wait for condition has timed out
+````
 
 * ___How can the dynamic frame be identified for each test run?___
 
diff --git a/docs/automated-tests/elements/merge-page-nodes.md b/docs/automated-tests/elements/merge-page-nodes.md
index 2092a8b2..37f5c53b 100644
--- a/docs/automated-tests/elements/merge-page-nodes.md
+++ b/docs/automated-tests/elements/merge-page-nodes.md
@@ -4,13 +4,13 @@ page_title: Merge Page Nodes
 description: Merge Page Nodes in Test Studio elements repository. Each time I start a recording session I get a new element recorded for the same control under different page node in the elements explorer. The element uses the same find expression, but the page URL differs as it has dynamically generated part. How can I reuse the same recorded element
 position: 7
 ---
-#Merge Page Nodes#
+# Merge Page Nodes
 
 * <a href="/knowledge-base/project-configuration-kb/merge-page-nodes#page-nodes">Page nodes</a>
 * <a href="/knowledge-base/project-configuration-kb/merge-page-nodes#frames">Frame nodes</a>
-* <a href="/knowledge-base/project-configuration-kb/merge-page-nodes#silverlightapps">Silverlight apps</a>
 
-##Page Nodes##
+
+## Page Nodes
 
 The default for the **Compare Mode** in <a href="/features/project-settings/recording-options" target="_blank">Project Settings > Recording</a> is *FullPathAndQuery*. Depending on your application, this can cause duplication in the Elements Explorer. Although the page node is not used to locate an element during execution, it's best to consolidate duplicate page nodes for organizational and maintenance purposes. For example:
 
@@ -51,7 +51,7 @@ The default for the **Compare Mode** in <a href="/features/project-settings/reco
 
 If *FullPath* is not applicable to your project, review the <a href="/features/project-settings/recording-options" target="_blank">Project Settings > Recording Options</a> page and select the Compare Mode that best suits your needs.
 
-##Frames##
+## Frames
 
 An element directly under a page node is located entirely by its Find Settings. Conversely, an element within a frame must be located via the frame first.
 
@@ -67,13 +67,6 @@ An element directly under a page node is located entirely by its Find Settings.
 
 	![Merge nodes][9]
 
-##SilverlightApps##
-
-Like frames, an element within a SilverlightApp must be located via the SilverlightApp first. Unlike a frame node, a SilverlightApp node has Find Settings just like a regular element, which can be changed via the <a href="/features/elements-explorer/find-element" target="_blank">Find Element</a> dialog.
-
-![SL find properties][10]
-
-![SL application][11]
 
 [1]: /img/knowledge-base/project-configuration-kb/merge-page-nodes/fig1.png
 [2]: /img/knowledge-base/project-configuration-kb/merge-page-nodes/fig2.png
diff --git a/docs/automated-tests/elements/overview.md b/docs/automated-tests/elements/overview.md
index 2d54e10b..91cfc609 100644
--- a/docs/automated-tests/elements/overview.md
+++ b/docs/automated-tests/elements/overview.md
@@ -5,38 +5,44 @@ description: "Elements Explorer in Test Studio. Elements in the Elements Explore
 previous_url: /user-guide/elements-pane-overview.aspx, /user-guide/elements-pane-overview
 position: 0
 ---
-# Elements Explorer #
+# Elements Explorer 
 
 The Elements Explorer in a Test Studio project is the visual representation of all elements recorded or manually added during the <a href="/general-information/test-recording/overview" target="_blank">Test Recording process</a>.
 
 The Elements Explorer pane provides a one-stop shop to view all elements used in the project and edit the way they are found during execution. You can find the Elements Explorer under/next to the Project's Explorer on the left bottom pane.
 
-<table id=no-table>
-	<tr>
-		<td>![Standalone Version][1] <br><br>**Standalone version**</td>
-		<td>![VS Plugin][2] <br><br>**VS plugin**</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Standalone Version][1] <br><br>**Standalone version**</td>
+<td>
+
+![VS Plugin][2] <br><br>**VS plugin**</td>
+</tr>
+</table>
 
 > __Tip__
 > <br>
 > <br>
 > Although elements may be used in several tests and test steps, each element with unique find expression is shown only once in the Elements Explorer.
 
-## Hierarchy of Recorded Elements ##
+## Hierarchy of Recorded Elements 
 
 The elements are organized under Page nodes (and also <a href="/general-information/test-recording/frames" target="_blank">Frame nodes</a> if there are frames used in the web page) for web applications and Application and Window Caption nodes for WPF applications.
 
-<table id="no-table">
-<tr>
-<td>![HTML Tree View][4]<br>**HTML Tree View**</td>
-<td>![Silverlight Tree View][5]<br>**Silverlight Tree View**</td>
-<td>![WPF Tree View][6]<br> **WPF Tree View**</td>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![HTML Tree View][4]<br>**HTML Tree View**</td>
+<td>
+
+![WPF Tree View][6]<br>**WPF Tree View**</td>
 </tr>
-<table>
+</table>
 
 - The HTML tree view is organized by **Page > Frame > Test Regions > Element**.
-- The Silverlight tree view is organized by **Page > Frame > SilverlightApp > Element**.
 - The WPF tree view is organized by **Application > Window > Element**.
 
 The hierarchy is maintained according to where the element is located on the page. For example, if there are no frames or regions, then elements for that particular page will be listed under the Page node.
@@ -50,9 +56,9 @@ Each element in the Elements Explorer is tied to a step from the project. The la
 - __If I select a step in the test, how do I know which element it uses?__ - when a step is selected in the test, its target element gets marked with a red arrow sign in front of its name. The target element is also listed in the <a href="/features/test-maintenance/test-step-properties#elements" target="_blank">step properties</a> under _Primary Target_ property.
 - __Can I change the element, which a step uses?__ - the element can be <a href="/features/test-maintenance/change-step-target-element" target="_blank">changed with another existing element by editing the _Primary Target_ step property</a>. Alternatively, you can <a href="/automated-tests/elements/find-element" target="_blank">change the find expression</a> of the element in Test Studio and that way change the element. which will be located on the page.
 
-## Element's Explorer Context Menu ##
+## Element's Explorer Context Menu 
 
-### Page Node Context Menu ###
+### Page Node Context Menu 
 
 Right click a Page node to see a context menu with these active choices:
 
@@ -63,7 +69,7 @@ Right click a Page node to see a context menu with these active choices:
 - **Load Page** - loads the URL to which the page belongs in the recording window.
 - **Properties** - makes the Properties pane active.
 
-### Element Context Menu ###
+### Element Context Menu 
 
 Each Element node has a context menu with these active choices:
 
@@ -80,7 +86,7 @@ Each Element node has a context menu with these active choices:
 - **Load Page** - loads the URL to which the element belongs in the recording window.
 - **Properties** - makes the Properties pane active.
 
-## Element's Explorer Menu Bar ##
+## Element's Explorer Menu Bar 
 
 The Elements menu bar ![Elements bar][3] has the following buttons:
 
diff --git a/docs/automated-tests/elements/using-chained-find-expressions.md b/docs/automated-tests/elements/using-chained-find-expressions.md
index 69e524cb..5c4a306b 100644
--- a/docs/automated-tests/elements/using-chained-find-expressions.md
+++ b/docs/automated-tests/elements/using-chained-find-expressions.md
@@ -95,7 +95,7 @@ This can help you see how the chained find expression will work against the DOM.
 
 ![Locate in DOM][11]
 
-##See Also##
+## See Also
 
 * <a href="http://www.telerik.com/videos/teststudio/test-studio---flexible-locators-" target="_blank">Watch a video tutorial on chained find expressions</a>
 
diff --git a/docs/automated-tests/execute-apitest/add-api-test-as-step.md b/docs/automated-tests/execute-apitest/add-api-test-as-step.md
index 0b764c22..998cf844 100644
--- a/docs/automated-tests/execute-apitest/add-api-test-as-step.md
+++ b/docs/automated-tests/execute-apitest/add-api-test-as-step.md
@@ -20,12 +20,16 @@ Double click it to trigger the ___'Select API test'___ dialog.
 
 The available options are either to create a new test or import an existing one.
 
-<table id="no-table">
-	<tr>
-		<td>![Create an API Test][3]</td>
-		<td>![Add existing API test][4]</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+![Create an API Test][3]</td>
+<td>
+		
+![Add existing API test][4]</td>
+</tr>
+</table>
 
 ## Create Test
 
@@ -55,6 +59,4 @@ Once the test is imported click on it and then the _Select_ button. If there are
 [4]: /img/features/execute-apitest/add-api-test-as-step/import-existing.png
 [5]: /img/features/execute-apitest/add-api-test-as-step/browse-apitest.png
 [6]: /img/features/execute-apitest/add-api-test-as-step/warning.png
-[7]: /img/features/execute-apitest/add-api-test-as-step/select-test.png
-[8]: /img/features/execute-apitest/add-api-test-as-step/fig8.png
-[9]: /img/features/execute-apitest/add-api-test-as-step/fig9.png
\ No newline at end of file
+[7]: /img/features/execute-apitest/add-api-test-as-step/select-test.png
\ No newline at end of file
diff --git a/docs/automated-tests/headless/headless-test-execution.md b/docs/automated-tests/headless/headless-test-execution.md
index f711255f..770647a8 100644
--- a/docs/automated-tests/headless/headless-test-execution.md
+++ b/docs/automated-tests/headless/headless-test-execution.md
@@ -20,7 +20,7 @@ Running web tests in __headless browser mode uses a web browser to run the scrip
 > Find out further advantages of <a href="https://www.telerik.com/blogs/what-is-headless-browser-testing-when-and-why-use-it" target="_blank">headless testing in this Test Studio blog post</a>.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## How to Execute Test in Headless Browser Mode?
diff --git a/docs/automated-tests/load/advanced-topics/manage-windows-auth.md b/docs/automated-tests/load/advanced-topics/manage-windows-auth.md
index 5e7c4e16..f0dd3575 100644
--- a/docs/automated-tests/load/advanced-topics/manage-windows-auth.md
+++ b/docs/automated-tests/load/advanced-topics/manage-windows-auth.md
@@ -3,8 +3,14 @@ title: Manage Windows Authentication
 page_title: Manage Windows Authentication
 description: "Manage Windows Authentication in Test Studio load test. The tested application supports Windows Authentication - can use that in Test Studio load test"
 position: 0
-publish: false
+published: false
 ---
+__Note__
+Currently the feature is not available in the product visually!!! It is hidden and not accessible for the customers!!! 
+Redirect is added to avoid getting to the article online. 
+
+
+
 # Manage Windows Authentication
 
 If the target application supports Windows Authentication, you can configure your load test to connect using a Windows Authentication identity.
@@ -39,7 +45,7 @@ If your test is <a href="/features/data-driven-testing/bind-test-data-source" ta
 
 ![Bind Win Auth][5]
 
-[1]: /img/features/testing-types/load-testing/manage-windows-auth/fig1.png
+
 [2]: /img/features/testing-types/load-testing/manage-windows-auth/fig2.png
 [3]: /img/features/testing-types/load-testing/manage-windows-auth/fig3.png
 [4]: /img/features/testing-types/load-testing/manage-windows-auth/fig4.png
diff --git a/docs/automated-tests/load/designing-load-tests/dynamic-targets-custom.md b/docs/automated-tests/load/designing-load-tests/dynamic-targets-custom.md
deleted file mode 100644
index bcca4685..00000000
--- a/docs/automated-tests/load/designing-load-tests/dynamic-targets-custom.md
+++ /dev/null
@@ -1,117 +0,0 @@
----
-title: Dynamic Targets - Custom
-page_title: Dynamic Targets - Custom
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 8
-publish: false
----
-# Custom Dynamic Targets
-
-Based on the HTTP traffic there might be targets which are not detected by Test Studio as dynamic but still these will be required to accomplish meaningful scenario. Or any of the auto-detected dynamic targets is not listed for transfer to a desired request.
-
-To handle such scenarios Test Studio implemented the ability to add __Custom Dynamic Targets__. The Custom Dynamic Targets are available in the _Choose Dynamic Targets_ view where all auto-detected are listed as well - once a <a href="/features/testing-types/load-testing/capturing-traffic" target="_blank">user profile is captured</a> or opened <a href="/features/testing-types/load-testing/modifying-tests" target="_blank">to be modified</a> click the ___Choose Dynamic Targets___ button. 
-
-![Choose Dynamic Targets][5]
-
-Once any custom targets are added to the user profile these will be displayed under the list with all auto-detected dynamic targets. To add a custom dynamic target use the ___Add Dynamic Target___ button. 
-
-![Add Dynamic Targets][6]
-
-## Source Section Properties
-
-- **Step**: Step to take the target from. Any step which contains a HTTP request can be selected. The Think time steps are filtered out and not displayed in the dropdown.
-- **Response**: Which part of the HTTP response to be used - Body, Headers or Cookie. Select the necessary part of the HTTP response and verify its content.
-- **Content**: Displays the content of the selected response part.
-- **Search Type**: The type of search to be used in the content of the selected response - FullText, Regex, JSON, XML. Select any of the provided options to search for the necessary value from the response.
-- **Starts after/before|Regex|JSON path|XPath**: Provide the search query to locate the desired value in the response.
-- **Search Result**: Click to show the reuslt based on the search query.
-- **Current Value**: Display the current reuslt based on the search query.
-
-<table id="no-table">
-	<tr>
-		<td>__Source Body__<br>![Source Section Properties][7]</td>
-		<td>__Source Headers__<br>![Source Section Properties][8]</td>
-    </tr>
-    <tr>
-        <td>__Source Cookie__<br>![Source Section Properties][9]</td>
-	</tr>
-<table>
-
-### Search Options
-
-- ___FullText___ - use strings which surround the desired value to locate it in response. 
-
-__Example:__ The head section of a HTTP response's body is:
-
-
-```
-<html>
-<head><title>Example ASP Scripts</title></head>
-```
-
-To get the actual title you may use __Starts after:__ \<title\> and __Ends before:__ \</title\>
-
-- ___Regex___ - use <a href="https://docs.microsoft.com/en-us/dotnet/standard/base-types/regular-expression-language-quick-reference" target="_blank">regular expression</a> to locate the desired value in response body, header or cookie.
-
-> __Note!__ Test Studio uses \<val\> to express the first match in response!
-
-__Example:__ The cookie of a HTTP response is the following string and the requirement is to get the domain name value only:
-
-```
-_EDGE_S=SID=04D5974D8509631807D39B2484BF62E4; path=/; httponly; domain=bing.com
-```
-
-The only possible approach is to use the partial search using Regex. The standard regex for extracting the desired value looks like this:
-
-```
-domain=(.*?)$
-```
-
-
-This returns the following match information:
-
-
-```
-Full match	65-80	`domain=bing.com`
-Group 1.	72-80	`bing.com`
-```
-
-Using that standard regular expression in Test Studio will return the _Full match_ instead the value in _Group 1_. Therefore Test Studio uses \<val\> to express the first match group and the regular expression becomes:
-
-
-```
-domain=(?<val>.*?)$
-```
-
-
-- ___JSON___ - use <a href="http://goessner.net/articles/JsonPath/index.html#e3" target="_blank">JSONPath</a> to locate the desired value in response.
-
-- ___XML___ - use <a href="https://msdn.microsoft.com/en-us/library/ms256122(v=vs.110).aspx" target="_blank">XPath</a> to locate the desired value in response.
-
-## Destination Section Properties
-
-
-- **Step**: Step to pass the target to. Any step that follows the selected one for source and contains a HTTP request could be selected for destination step. The Think time steps are filtered out and not displayed in the dropdown.
-- **Field Type**: In what part of the HTTP request to include the custom dynamic target - Query Paramater, Header, Cookie, POST data, URL.
-- **Field Name**: The name of the dynamic target which will be used in the HTTP request.
-
-![Destination Section Properties][10]
-
-## Important Notes
-
-> __Note!__ The custom dynamic value will be added to the destination HTTP request even if there is no such parameter, cookie or header existing in the recorded request.
-<br>
-> __Note!__ If there are both autodetected and custom dynamic values for a single destination step, the last set target will be used in the request. Disable/Enable of a dynamic target will update the order of set targets. 
-<br>
-> __Note!__ As of now there is no visual representation for any custom dynamic targets within the __Edit User Profile__ view. To verify if the HTTP requests are built as you expect you could use <a href="https://www.telerik.com/fiddler" target="_blank">Fiddler</a> to capture the traffic of a sample load test execution and inspect these.
-
-[1]: /img/features/testing-types/load-testing/dynamic-targets/fig1.png
-[2]: /img/features/testing-types/load-testing/dynamic-targets/fig2.png
-[3]: /img/features/testing-types/load-testing/dynamic-targets/fig3.png
-[4]: /img/features/testing-types/load-testing/dynamic-targets/fig4.png
-[5]: /img/features/testing-types/load-testing/dynamic-targets/fig5.png
-[6]: /img/features/testing-types/load-testing/dynamic-targets/fig6.png
-[7]: /img/features/testing-types/load-testing/dynamic-targets/fig7.png
-[8]: /img/features/testing-types/load-testing/dynamic-targets/fig7a.png
-[9]: /img/features/testing-types/load-testing/dynamic-targets/fig7b.png
-[10]: /img/features/testing-types/load-testing/dynamic-targets/fig8.png
diff --git a/docs/automated-tests/load/designing-load-tests/dynamic-targets.md b/docs/automated-tests/load/designing-load-tests/dynamic-targets.md
index 39e8b3ae..6787963d 100644
--- a/docs/automated-tests/load/designing-load-tests/dynamic-targets.md
+++ b/docs/automated-tests/load/designing-load-tests/dynamic-targets.md
@@ -75,15 +75,21 @@ __See Also:__ A sample scenario to cover with the help of custom dynamic targets
 - **Search Result**: Click to show the result based on the search query.
 - **Current Value**: Display the current result based on the search query.
 
-<table id="no-table">
-	<tr>
-		<td>__Source Body__<br>![Source Section Properties][7]</td>
-		<td>__Source Headers__<br>![Source Section Properties][8]</td>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+__Source Body__<br>![Source Section Properties][7]</td>
+		<td>
+		
+__Source Headers__<br>![Source Section Properties][8]</td>
     </tr>
-    <tr>
-        <td>__Source Cookie__<br>![Source Section Properties][9]</td>
-	</tr>
-<table>
+    <tr style="text-align: center; background-color: transparent; border:none;">
+        <td>
+
+__Source Cookie__<br>![Source Section Properties][9]</td>
+</tr>
+</table>
 
 ### Search Options
 
@@ -91,10 +97,10 @@ __See Also:__ A sample scenario to cover with the help of custom dynamic targets
 
 __Example:__ The head section of a HTTP response's body is:
 
-```
+````
 <html>
 <head><title>Example ASP Scripts</title></head>
-```
+````
 
 To get the actual title you may use __Starts after:__ \<title\> and __Ends before:__ \</title\>
 
@@ -104,28 +110,28 @@ To get the actual title you may use __Starts after:__ \<title\> and __Ends befor
 
 __Example:__ The cookie of a HTTP response is the following string and the requirement is to get the domain name value only:
 
-```
+````
 _EDGE_S=SID=04D5974D8509631807D39B2484BF62E4; path=/; httponly; domain=bing.com
-```
+````
 
 The only possible approach is to use the partial search using Regex. The standard regex for extracting the desired value looks like this:
 
-```
+````
 domain=(.*?)$
-```
+````
 
 This returns the following match information:
 
-```
+````
 Full match	65-80	`domain=bing.com`
 Group 1.	72-80	`bing.com`
-```
+````
 
 Using that standard regular expression in Test Studio will return the _Full match_ instead the value in _Group 1_. Therefore Test Studio uses \<val\> to express the first match group and the regular expression becomes:
 
-```
+````
 domain=(?<val>.*?)$
-```
+````
 
 - ___JSON___ - use <a href="http://goessner.net/articles/JsonPath/index.html#e3" target="_blank">JSONPath</a> to locate the desired value in response.
 
@@ -145,13 +151,13 @@ In some cases the dynamic parameter is built by a value from any previous HTTP r
 
 In Test Studio load module you can create such dynamic target using the available append options allowed in the Destination section's **Field Name** text box. All of these use the following template, where ___Prefix and Suffix are optional___:
 
-```
+````
 Query Parameter, Cookie, Header
 'ParamName:Prefix{value}Suffix'
 
 URL
 'Prefix{value}Suffix'
-```
+````
 
 > __Note!__ Keep in mind that **blank spaces in the *Field Name* text box are considered valid character** and thus are included in the final string. Therefore, leave intervals in the text only if these are expected.
 
@@ -168,16 +174,24 @@ URL
 	* __Ex.:__ http://google.com/{value} - if the extracted value is _test_, the URL will be appended as _http://google.com/test_.
 	* __Ex.:__ http://google.com/{value}/id=1379 - if the extracted value is _test_, the URL will be appended as _http://google.com/test/id=1379_.
 
-<table id="no-table">
-	<tr>
-		<td>__Append Query Parameter__<br>![Append Query Parameter][11]</td>
-		<td>__Append Header__<br>![Append Header][12]</td>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+__Append Query Parameter__<br>![Append Query Parameter][11]</td>
+<td>
+
+__Append Header__<br>![Append Header][12]</td>
     </tr>
-    <tr>
-        <td>__Append Cookie__<br>![Append Cookie][13]</td>
-		<td>__Append URL__<br>![Append URL][14]</td>
-	</tr>
-<table>
+    <tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+		
+__Append Cookie__<br>![Append Cookie][13]</td>
+<td>
+
+__Append URL__<br>![Append URL][14]</td>
+</tr>
+</table>
 
 > __Note!__ The above examples only represent how to append some predefined text before or after the dynamic value for the different types of destination fields. These are no real example of working HTTP calls.
 
diff --git a/docs/automated-tests/load/designing-load-tests/modifying-tests.md b/docs/automated-tests/load/designing-load-tests/modifying-tests.md
index e3821d17..2ff78282 100644
--- a/docs/automated-tests/load/designing-load-tests/modifying-tests.md
+++ b/docs/automated-tests/load/designing-load-tests/modifying-tests.md
@@ -95,6 +95,3 @@ Click the _'magnifier'_ icon in the __Edit User Profile__ window to expand the _
 [9]: /img/features/testing-types/load-testing/modifying-tests/fig9.png
 [10]: /img/features/testing-types/load-testing/modifying-tests/fig10.png
 [11]: /img/features/testing-types/load-testing/modifying-tests/fig11.png
-[12]: /img/features/testing-types/load-testing/modifying-tests/fig12.png
-[13]: /img/features/testing-types/load-testing/modifying-tests/fig13.png
-[14]: /img/features/testing-types/load-testing/modifying-tests/fig14.png
\ No newline at end of file
diff --git a/docs/automated-tests/load/designing-load-tests/test-settings.md b/docs/automated-tests/load/designing-load-tests/test-settings.md
index ddf713eb..e0b070a7 100644
--- a/docs/automated-tests/load/designing-load-tests/test-settings.md
+++ b/docs/automated-tests/load/designing-load-tests/test-settings.md
@@ -46,8 +46,8 @@ Any changes in the Test Settings will appear in the _Users Over Time_ graph.
 
 ![Time Graph][6]
 
-[1]: /img/features/testing-types/load-testing/test-settings/fig1.png
-[2]: /img/features/testing-types/load-testing/test-settings/fig2.png
+
+
 [3]: /img/features/testing-types/load-testing/test-settings/fig3.png
 [4]: /img/features/testing-types/load-testing/test-settings/fig4.png
 [4a]: /img/features/testing-types/load-testing/test-settings/fig4a.png
diff --git a/docs/automated-tests/load/load-testing-results/analyzing-results.md b/docs/automated-tests/load/load-testing-results/analyzing-results.md
index 70972b1c..385357d5 100644
--- a/docs/automated-tests/load/load-testing-results/analyzing-results.md
+++ b/docs/automated-tests/load/load-testing-results/analyzing-results.md
@@ -163,7 +163,7 @@ padding: 8px;
 <tr>
 	<td>Responses Received per Second</td><td>The number of HTTP responses received per second across all virtual users. </td>
 </tr>
-<table>
+</table>
 
 [1a]: /img/features/testing-types/load-testing/analyzing-results/fig1a.png
 [1]: /img/features/testing-types/load-testing/analyzing-results/fig1.png
diff --git a/docs/automated-tests/load/overview.md b/docs/automated-tests/load/overview.md
index 4a6eca4d..1ba0a68e 100644
--- a/docs/automated-tests/load/overview.md
+++ b/docs/automated-tests/load/overview.md
@@ -11,7 +11,7 @@ The Load Testing feature in Test Studio Standalone enables you to assess how you
 ![Load Test][1]
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## What is Load Testing in Test Studio?
diff --git a/docs/automated-tests/load/running-load-test/running-tests.md b/docs/automated-tests/load/running-load-test/running-tests.md
index d09494d8..14fd18ca 100644
--- a/docs/automated-tests/load/running-load-test/running-tests.md
+++ b/docs/automated-tests/load/running-load-test/running-tests.md
@@ -87,7 +87,7 @@ padding: 8px;
 <tr>
 	<td>> 60 hours</td><td>10 minutes</td>
 </tr>
-<table>
+</table>
 
 ## Test Run Goals
 
@@ -119,7 +119,3 @@ The “Run Locally” button will be disabled if any of the following prerequisi
 [5]: /img/features/testing-types/load-testing/running-tests/fig5.png
 [6]: /img/features/testing-types/load-testing/running-tests/fig6.png
 [7]: /img/features/testing-types/load-testing/running-tests/fig7.png
-[8]: /img/features/testing-types/load-testing/running-tests/fig8.png
-
-
-
diff --git a/docs/automated-tests/performance/gather-perfomance-data.md b/docs/automated-tests/performance/gather-perfomance-data.md
index aa531ad1..e13679ed 100644
--- a/docs/automated-tests/performance/gather-perfomance-data.md
+++ b/docs/automated-tests/performance/gather-perfomance-data.md
@@ -1,95 +1,74 @@
 ---
 title: Gather Performance Data
 page_title: Gather Performance Data
-description: "Gather Performance Data from performance test run in Test Studio."
-position: 1
+description: "Gather Performance Data Counters on the Execution machine during a performance test run in Test Studio."
+position: 8
 ---
 # Gather Performance Data
 
-> The target machine to be monitored must have either <a href="/general-information/test-studio-run-time" target="_blank">**Run Time edition**</a> or Test Studio installed on it. The <a href="/features/scheduling-test-runs/create-execution-server" target="_blank">execution server</a> needs to be running before Test Studio can connect to it for performance monitoring.
+> The target machine to be monitored must have either <a href="/general-information/test-studio-run-time" target="_blank">**Run Time edition**</a> or Test Studio installed on it. The <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Test Studio Execution Client</a> needs to be running before Test Studio can connect to it for performance monitoring.
 
-1.&nbsp; Click the Performance tab.
+The below instruction assumes that you already have configured a performance run and you only need to add performance counters to be monitored. 
 
-2.&nbsp; Read the **Introduction** to Performance Testing.
+1. Click the **Configure** button in the **Set Up** ribbon.
 
-![Introduction][1]
+    ![Click configure button][15]
 
-3.&nbsp; Click **Get Started** to continue. 
+2. Click **Continue to Step 2 >** button in the **Configure Performance Settings** window. 
 
-4.&nbsp; Ensure you have a valid automated test candidate loaded for the Performance Run.
+    ![Continue to step 2](/img/features/testing-types/performance-testing/gather-perfomance-data/continue-to-step-2.png)
 
-5.&nbsp; Click the **Configure** button under section **2: Set Up**.
+3. Check the **Gather Computer Performance Data** checkbox.
 
-![Set Up][2]
+4. Click the **Add a computer** button.
 
-6.&nbsp; Set the location to save the results under section **1: Specify Save Results Folder**.
+    ![Add a computer][4]
 
-![Results folder][3]
+5. Set a friendly name for this machine configuration, then enter the actual machine name or IP address. The machine must be running the Test Studio Profiling Service, e.g. the Test Studio Execution client.
 
-> To gather additional Performance Counter data, continue to step 7. If not, skip to step 8. 
+6. Click the **Connect** button to confirm a connection can be established. 
 
-7.&nbsp; Click Continue to Step 2. Under section 2: **Gather Performance Counter Data**:
+    ![Connect][5]
+    
+    > __Tip__ 
+    > <br> 
+    > If the connection fails, go to the **Help** tab and click the **View Log** button in the **Logging** ribbon. The **Enable** button must be selected beforehand for the log to populate with information. If it is not useful for you, submit the generated log zipped into a support thread. 
+    > <br> 
+    > ![View Log][6]
+    > <br>
+    > <br>
+    > __Note!__ The most common reason that the connection cannot be made is that the Profiler Service is not running on the computer you entered. That computer must have <a href="/general-information/test-studio-run-time" target="_blank">Run-Time Edition</a> installed and the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Test Studio Execution Client</a> running. 
 
-a. Check the **Gather Computer Performance Data** box.
+7. In the section labeled **Select the system resources that you want to monitor** choose from the list with __Available Counters__. Select an entire group, or expand the group to select specific counters within it.
 
-b. Click the **Add a computer** button.
+    ![Available Counters][8]
 
-![Add a computer][4]
+> __Note!__ 
+> ><br>
+> It is up to you and your team to decide which Performance Counters to use for your application depending on the monitoring you need. 
 
-c. Set a friendly name for this server configuration, then enter the actual machine name or IP address. The machine must be running the Test Studio Profiling Service.
 
-d. Click the **Connect** button to confirm a connection can be established. 
+8. You can save this set of performance counters as a template, click ![Disk][12].
 
-![Connect][5]
+    ![Save New Template][13]
 
-e. If the validation fails, go to the **Help** tab and click the **View Log** button in the **Logging** ribbon. The **Enable** button must be selected beforehand for the log to populate with information. 
+9. Click **Done Editing** when finished. Click **Cancel** to revert changes. Click **Delete** to remove this server configuration.
 
-![View Log][6]
+10. To import a previously saved template of performance counters, click ![Folder][9] .
 
->  Note: The most common reason for a validation failure is that the Profiler Service is not running on the computer you entered. That computer must have <a href="/general-information/test-studio-run-time" target="_blank">Run-Time Edition</a> installed. You can check by showing the Test Studio Test Runner from that machine's System Tray. 
+    ![Saved template][10]
 
-![Test Runner][7]
+Select the template you wish to use. You can view the performance counters included in this template. Click __Add__ to use this template.
 
-f. Move below to the section labeled **Select the system resources that you want to monitor**.
-g. Choose from the Available Counters. Select an entire group, or expand the group to select specific counters within it.
+    ![Add Template][11]
 
-![Available Counters][8]
 
-> It is up to you and your developers to decide which Performance Counters to use for your application. The selections made above were chosen for demonstration purposes. See here for more information.
+11. You can monitor Performance Counters on more than one machine. Click the **Add a computer** button to gather performance data on another machine.
 
-h. To import a previously saved template of performance counters, click ![Folder][9] .
+    ![Monitor multiple machines](/img/features/testing-types/performance-testing/gather-perfomance-data/monitor-multiple-machines.png)
 
-![Saved template][10]
+12. When finished click **Save** and continue to initiating the performance test run. 
 
-Select the template you wish to use. You can view the performance counters included in this template. Click add to use this template.
-
-![Add Template][11]
-
-i. To save this set of performance counters as a template, click ![Disk][12].
-
-![Save New Template][13]
-
-j. Click **Done Editing** when finished. Click **Cancel** to revert changes. Click **Delete** to remove this server configuration.
-
-k. Click the **Add a computer** button to gather performance data on multiple machines.
-
-l. Click **Save** when finished.
-
-8.&nbsp; Click the **Quick Run** button under section **3: Quick Performance Run**. 
-
-![Run][14]
-
-9.&nbsp; To make configuration changes before your next Performance Run, click the **Configure** button in the **Set Up** ribbon.
-
-![configure][15]
-
-10.&nbsp; To execute your next Performance Run, select a browser type and click Run in the Quick Performance Run ribbon.
-
-![Run][16]
-
-[1]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png
-[2]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png
-[3]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png
 [4]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig4.png
 [5]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig5.png
 [6]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig6.png
@@ -102,4 +81,3 @@ l. Click **Save** when finished.
 [13]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig13.png
 [14]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png
 [15]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig15.png
-[16]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig16.png
\ No newline at end of file
diff --git a/docs/automated-tests/performance/open-port-on-server.md b/docs/automated-tests/performance/open-port-on-server.md
index aa28f7c8..e55cfe90 100644
--- a/docs/automated-tests/performance/open-port-on-server.md
+++ b/docs/automated-tests/performance/open-port-on-server.md
@@ -2,7 +2,7 @@
 title: How to Open Port on Server
 page_title: Performance Testing - Open Port on Server
 description: "Open Port on Server for a performance test in Test Studio project."
-position: 8
+position: 9
 ---
 # Open Port on Server for Test Studio Performance Testing
 
diff --git a/docs/automated-tests/performance/overview.md b/docs/automated-tests/performance/overview.md
index 6e805558..e326dd6b 100644
--- a/docs/automated-tests/performance/overview.md
+++ b/docs/automated-tests/performance/overview.md
@@ -10,6 +10,14 @@ How responsive is my application? What are the bottlenecks in my application? Ho
 
 All these are questions, which <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> answers with the Performance testing functionality.
 
+> __Feature Deprecation Notice__
+> <br>
+> <br>
+> __Performance Testing is scheduled for deprecation in the Test Studio 2026 Q1 release__.
+> <br>
+> <br>
+> If you currently rely on this feature, we encourage you to share your concerns or feedback with us via a support thread. Your input is valuable and will help us ensure a smooth transition and continued support for your testing needs.
+
 ## What is Performance Testing in Test Studio
 
 Automated functional testing tools help you build automated tests for your critical end-user scenarios. Once automated with Test Studio, these scenarios can be run automatically to help you discover any regressions. Functional correctness of your application is one measure of quality, another quite important one is performance testing.
@@ -20,13 +28,13 @@ Automated functional testing tools help you build automated tests for your criti
 
 - **In-Depth Analysis** - Analyze your results by comparing Client vs. Server time. Trace your code at the step level to pinpoint the exact line of code that is causing the biggest bottleneck. 
 
-> If profiling a remote server, it needs at minimum the Test Studio Run-Time edition installed on it with the Profiler Service enabled. The versions of Test Studio run locally and remotely on the server must match. Also ensure the correct inbound and outbound <a href="/features/testing-types/performance-testing/open-port-on-server" target="_blank">port is open</a> on the remote server.
+> If profiling a remote server, it needs at minimum the Test Studio Run-Time edition installed on it with the Test Studio Execution Client running. The versions of Test Studio used locally and remotely on the server must match. Also ensure the correct inbound and outbound <a href="/features/testing-types/performance-testing/open-port-on-server" target="_blank">port is open</a> on the remote server.
 
 ## Select a Valid Automated Web Test
 
 Which web tests make good candidates for Performance Testing?
 
-- Specific user scenarios with little to no verification steps or timeouts.
+- Specific user scenarios with less verification steps and no hard-coded timeouts.
 
 - All variables are removed to prevent interference.
 
@@ -34,7 +42,7 @@ Which web tests make good candidates for Performance Testing?
 
 Once you designate a good candidate test, go to the **Performance** tab and get started:
 
-1.&nbsp;  <a href="/features/testing-types/performance-testing/gather-perfomance-data" target="_blank">Gather Performance Data</a> - Configure settings and create the Performance Run.
+1.&nbsp;  <a href="/automated-tests/performance/performance-run" target="_blank">Initiate Performance Run</a> - Configure settings and initiate the Performance Run.
 
 2.&nbsp; <a href="/features/testing-types/performance-testing/history-view" target="_blank">History View</a> - Visualize metrics over time, achieve performance goals, and use the Benchmark feature to establish a performance baseline. 
 
@@ -42,4 +50,6 @@ Once you designate a good candidate test, go to the **Performance** tab and get
 
 4.&nbsp; <a href="/features/testing-types/performance-testing/details-view" target="_blank">Details View</a> - View an in-depth analysis of each test step, the entire test, or a custom interval.
 
-5.&nbsp; <a href="/features/testing-types/performance-testing/compare-view" target="_blank">Compare View</a> - Put two Performance Runs side by side and identify potential regressions or bottlenecks using delta threshold.
\ No newline at end of file
+5.&nbsp; <a href="/features/testing-types/performance-testing/compare-view" target="_blank">Compare View</a> - Put two Performance Runs side by side and identify potential regressions or bottlenecks using delta threshold.
+
+6.&nbsp;  <a href="/features/testing-types/performance-testing/gather-perfomance-data" target="_blank">Gather Performance Counters Data</a> - Configure settings to gather additional data from Performance Counters on selected machine.
\ No newline at end of file
diff --git a/docs/automated-tests/performance/performance-run.md b/docs/automated-tests/performance/performance-run.md
new file mode 100644
index 00000000..c9c77a7b
--- /dev/null
+++ b/docs/automated-tests/performance/performance-run.md
@@ -0,0 +1,62 @@
+---
+title: Initiate Performance Run
+page_title: Initiate Performance Run
+description: "How to initiate a performance run based on a web test."
+position: 1
+---
+# Initiate Performance Run
+
+> The target machine to be monitored must have either <a href="/general-information/test-studio-run-time" target="_blank">**Run Time edition**</a> or Test Studio installed on it. The <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Test Studio Execution Client</a> needs to be running before Test Studio can connect to it for performance monitoring.
+
+1. Choose a web test to run in performance mode. 
+2. Click the Performance tab.
+3. See the **Introduction** to Performance Testing and hit the **Get Started** button to continue. 
+
+    ![Introduction][1]
+
+4. Click the **Configure** button under section **2: Set Up**.
+
+    ![Set Up][2]
+
+    > __Tip!__
+    > <br>
+    > The same window is accessed from the Tools ribbon using the **Configure** button.
+
+5. Set the location to save the results under section **1: Specify Save Results Folder**.
+
+    ![Specify Results folder][3]
+
+6. Hit the **Save** button to confirm the configuration. 
+
+    ![Confirm configuration for performance test run](/img/features/testing-types/performance-testing/gather-perfomance-data/fig3-saveButton.png)
+
+7. Select the desired browser to execute the web test in performance mode from the Tools ribbon - click on the browser icon. 
+
+    ![Choose browser to use for the performance run](/img/features/testing-types/performance-testing/gather-perfomance-data/choose-browser.png)
+
+8.  Click the **Quick Run** button under section **3: Quick Performance Run**. 
+
+    ![Run][14]
+
+    > __Tip!__
+    > <br>
+    > The same action is triggered from the Tools ribbon using the **Run** button.
+
+9. To make configuration changes before your next Performance Run, click the **Configure** button in the **Set Up** ribbon.
+
+    ![configure][15]
+
+10. To execute your next Performance Run, select a browser type and click Run in the Quick Performance Run ribbon.
+
+    ![Run][16]
+
+> __Tip!__
+> <br>
+> You can gather additional Performance Counter data for the execution machine - see <a href="/automated-tests/performance/gather-perfomance-data" target="_blank">here how to acivate and configure Performance Counters</a>. 
+
+[1]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png
+[2]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png
+[3]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png
+[14]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png
+[15]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig15.png
+[16]: /img/features/testing-types/performance-testing/gather-perfomance-data/fig16.png
\ No newline at end of file
diff --git a/docs/automated-tests/recording/hover-over-highlighting.md b/docs/automated-tests/recording/hover-over-highlighting.md
index 55695c3e..290f14e5 100644
--- a/docs/automated-tests/recording/hover-over-highlighting.md
+++ b/docs/automated-tests/recording/hover-over-highlighting.md
@@ -95,16 +95,10 @@ In certain occasions you may need to scroll the page and change the visible part
 
 There are additional actions and verifications you can add against the selected element. For example, you can add mouse actions and <a href="/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification" target="_blank">advanced verification steps</a> for attribute, image or text from image.
 
-[1]: /img/features/recorder/compact-recording-toolbar/anim1.gif
-[2]: /img/features/recorder/compact-recording-toolbar/fig2.png
-[3]: /img/features/recorder/compact-recording-toolbar/fig3.png
-[4]: /img/features/recorder/compact-recording-toolbar/fig4.png
+
+
+
+
 [5]: /img/features/recorder/compact-recording-toolbar/fig5.png
 [6]: /img/features/recorder/compact-recording-toolbar/fig6.png
 [7]: /img/features/recorder/compact-recording-toolbar/fig7.png
-[8]: /img/features/recorder/compact-recording-toolbar/fig8.png
-[9]: /img/features/recorder/compact-recording-toolbar/fig9.png
-[10]: /img/features/recorder/compact-recording-toolbar/fig10.png
-[11]: /img/features/recorder/compact-recording-toolbar/fig11.png
-[12]: /img/features/recorder/compact-recording-toolbar/fig12.png
-[13]: /img/features/recorder/compact-recording-toolbar/fig13.png
diff --git a/docs/automated-tests/recording/overview.md b/docs/automated-tests/recording/overview.md
index 95934cc3..592e9d1d 100644
--- a/docs/automated-tests/recording/overview.md
+++ b/docs/automated-tests/recording/overview.md
@@ -9,7 +9,7 @@ position: 0
 The __Compact Recording Toolbar__ in Test Studio is the key element in recording tests. Once attached to an application it detects how you act upon the app and represent your actions as automated steps in the test. It also gives access to a variety of useful features enabling you for an entirely codeless testing experience.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 This article guides you trough the __recording workflow for web and WPF tests__ and how you can get the most out of it.
@@ -127,11 +127,13 @@ To stop the current recording session __close the automated browser or WPF/deskt
 
 The specifics of the recording process allow to __attach a recorder and trigger a recording session to an already running WPF application__. To start such recording session you need to use the dropdown under the __Record__ button - in the list you can see all compatible processes, to which Test Studio recorder can be attached. Select one and wait for the __Compact Recorder__ to attach to the application.
 
-<table id=no-table>
-	<tr>
-		<td>![Attach to running WPF instance][7] <br><br>**WPF Test - connect to running WPF application instance**</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+![Attach to running WPF instance][7] <br><br>**WPF Test - connect to running WPF application instance**</td>
+</tr>
+</table>
 
 > **Note**
 > <br>
@@ -161,14 +163,14 @@ Below you can find a short description of each button in the toolbar (in the ord
 * <a href="https://www.telerik.com/videos/teststudio/test-recorder-for-wpf-video-tutorial-test-studio" target="_blank">WPF Test Recorder Video Tutorial</a>.
 
 [1]: /img/automated-tests/recording/overview/fig1.png
-[2]: /img/automated-tests/recording/overview/fig2.png
+
 [3]: /img/automated-tests/recording/overview/fig3.png
-[4]: /img/automated-tests/recording/overview/fig4.png
+
 [5]: /img/automated-tests/recording/overview/fig5.png
 [5a]: /img/automated-tests/recording/overview/fig5a.png
 [6]: /img/automated-tests/recording/overview/fig6.png
 [10]: /img/automated-tests/recording/overview/fig10.png
 [11]: /img/automated-tests/recording/overview/fig11.png
 [12]: /img/automated-tests/recording/overview/fig12.png
-[8]: /img/features/recorder/test-recorder/fig6.png
+
 [7]: /img/features/recorder/test-recorder/fig7.png
diff --git a/docs/automated-tests/recording/pdf-validation.md b/docs/automated-tests/recording/pdf-validation.md
index b0826e0c..9b7b7de0 100644
--- a/docs/automated-tests/recording/pdf-validation.md
+++ b/docs/automated-tests/recording/pdf-validation.md
@@ -11,7 +11,7 @@ PDF files are commonly used for generating reports and documents across differen
 Find out how to open a PDF file in the browser and record the scenario actions in a Test Studio test.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Enable Edge Browser for PDF Validation
@@ -93,7 +93,7 @@ Comparing the content of two PDF files is not a straight-forward scenario, but c
 1. Data drive these verification steps using the extracted variables from the downloaded file. 
 1. Execute the test and it will use the values extracted from the downloaded file to verify if this is the same with the content of the existing PDF file.
 
-## See also ##
+## See also 
 
 * 
 
@@ -102,5 +102,4 @@ Comparing the content of two PDF files is not a straight-forward scenario, but c
 [2a]: /img/automated-tests/recording/validate-pdf/fig2a.png
 [2b]: /img/automated-tests/recording/validate-pdf/fig2b.png
 [3]: /img/automated-tests/recording/validate-pdf/fig3.png
-[4]: /img/automated-tests/recording/validate-pdf/fig4.png
-[5]: /img/automated-tests/recording/validate-pdf/fig5.png
\ No newline at end of file
+[4]: /img/automated-tests/recording/validate-pdf/fig4.png
\ No newline at end of file
diff --git a/docs/automated-tests/recording/recording-dialogs.md b/docs/automated-tests/recording/recording-dialogs.md
index b83ca9de..69b24994 100644
--- a/docs/automated-tests/recording/recording-dialogs.md
+++ b/docs/automated-tests/recording/recording-dialogs.md
@@ -54,23 +54,23 @@ JavaScript generates three type of popup messages and these are as follows:
 
 To try out these types of dialogs you can use the _'Try It Yourself'_ buttons on each example for the <a href="https://www.w3schools.com/js/js_popup.asp" target="_blank">W3School JavaScript Popup Boxes</a> page. Here are the steps recorded in a test for each of the dialog boxes.
 
-<table id=no-table>
-<tr>
-<td>![Alert dialog](/img/automated-tests/recording/dialogs/alert-dialog-step.png)<br>__Handle Alert Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/alert-dialog-step.png" alt="Alert dialo"><br><strong>Handle Alert Dialog</strong></td>
 </tr>
-<table>
+</table>
 
-<table id=no-table>
-<tr>
-<td>![Confirm dialog](/img/automated-tests/recording/dialogs/confirm-dialog-step.png)<br>__Handle Confirm Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/confirm-dialog-step.png" alt="Confirm dialog"><br><strong>Handle Confirm Dialog</strong></td>
 </tr>
-<table>
+</table>
 
-<table id=no-table>
-<tr>
-<td>![Prompt dialog](/img/automated-tests/recording/dialogs/prompt-dialog-step.png)<br>__Handle Prompt Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/prompt-dialog-step.png" alt="Prompt dialog"><br><strong>Handle Prompt Dialog</strong></td>
 </tr>
-<table>
+</table>
 
 > __Tip__
 ><br>
@@ -88,11 +88,11 @@ Due to the specifics of this dialog and the Test Studio recording process flow,
 3. One option is to enter the valid credentials to login to the page and then <a href="/features/dialogs-and-popups/dialogs#add-a-handle-dialog-step-manually" target="_blank">manually insert the step to handle the Logon dialog</a>.
 4. The other option is to __first cancel the logon dialog__ - there is no step added in the test because the recorder is not yet active. Once the page returns the message that access is denied, the Test Studio recorder gets attached to the browser. On __manually refreshing the page__ from the browser, the __logon dialog prompts again__ and this time, while you enter your credentials to access the page, Test Studio __records your actions and adds the step__ in the test.
 
-<table id=no-table>
-<tr>
-<td>![Logon dialog](/img/automated-tests/recording/dialogs/logon-dialog-step.png)<br>__Handle Logon Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/logon-dialog-step.png" alt="Logon dialog"><br><strong>Handle Prompt Dialog</strong></td>
 </tr>
-<table>
+</table>
 
 ## Download and Upload File Dialogs in Web Test
 
@@ -111,11 +111,11 @@ The Upload File opens a __Open__ dialog in Windows File Explorer in which the us
 
 Test Studio fetches the selected folder and file and automatically populates the complete file path into the __Handle Upload dialog__ step. 
 
-<table id=no-table>
-<tr>
-<td>![Upload dialog](/img/automated-tests/recording/dialogs/upload-dialog-step.png)<br>__Handle Upload Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/upload-dialog-step.png" alt="Upload dialog"><br><strong>Handle Prompt Dialog</strong></td>
 </tr>
-<table>
+</table>
 
 > __Tip!__
 ><br>
@@ -133,11 +133,12 @@ The Download File dialog opens a __SaveAs__ dialog in Windows File Explorer in w
 
 Handling of a download dialog typically requires handling a sequence of dialogs - the browser prompts to download a file and the File Explorer lets you choose the destination path; optionally, handling a prompt message that a file with the same name already exists in the selected folder - the existing file is overwritten in such case. Test Studio fetches all actions taken and automatically records the __Handle Download dialog__ step and populates the complete file path and name. 
 
-<table id=no-table>
-<tr>
-<td>![Download dialog](/img/automated-tests/recording/dialogs/download-dialog-step.png)<br>__Handle Download Dialog__</td>
+<table id=no-table style="background-color: transparent; border:none;">
+<tr style="background-color: transparent; border:none;">
+<td style="background-color: transparent; border:none;"><img src="/img/automated-tests/recording/dialogs/download-dialog-step.png" alt="Download dialog"><br><strong>Handle Prompt Dialog</strong></td>
 </tr>
-<table>
+</table>
+
 
 > __Tip!__
 ><br>
@@ -149,7 +150,7 @@ Handling of a download dialog typically requires handling a sequence of dialogs
 
 ## SaveFile and OpenFile Dialogs in WPF Test
 
-The SaveFile and OpenFile actions usually require more than one single interaction with the dialog. Test Studio recording process detects the user actions to choose a folder and file and represents these into a single step to handle the dialog. 
+The __SaveFile__ and __OpenFile__ actions usually require more than one single interaction with the dialog. Test Studio recording process detects the user actions to choose a folder and file and represents these into a single step to handle the dialog. 
 
 > __Note__
 ><br>
@@ -176,13 +177,19 @@ The OpenFile action opens a __OpenFile__ dialog in Windows File Explorer in whic
 
 ### SaveFile Dialog
 
-The Download File dialog opens a __SaveAs__ dialog in Windows File Explorer in which the user browses to a specific folder and enters name for the file to be downloaded. Handling the download dialog typically requires interacting with a sequence of dialogs - the application prompts to download a file and the File Explorer lets you choose the destination path; optionally, handling a prompt message that a file with the same name already exists in the selected folder - the existing file is overwritten in such case. Test Studio fetches all actions taken and automatically records the __Handle SaveFile dialog__ step and populates the complete file path and name. 
+The Download File dialog opens a __SaveAs__ dialog in Windows File Explorer in which the user browses to a specific folder and enters name for the file to be downloaded. Handling the download dialog typically requires interacting with a sequence of dialogs - the application prompts to download a file and the File Explorer lets you choose the destination path. Test Studio fetches all actions taken and automatically records the __Handle SaveFile dialog__ step and populates the complete file path and name. 
+
+ __Note!__
+><br>
+><br>
+> Optionally, you may see an additional dialog that a file with the same name already exists in the selected folder where you can choose whether to overwrite the file. This dialog is recognized as a generic type of dialog and needs to be handled only if it appears - this scenario is supported only in a coded step as described <a href="/advanced-topics/coded-samples/html/conditional-dialog-handling" target="_blank">here</a>. 
 
 <table id=no-table>
 <tr>
 <td>![SaveFile dialog](/img/automated-tests/recording/dialogs/saveFile-dialog-step.png)<br>__Handle SaveFile Dialog__</td>
 </tr>
-<table>
+</table>
+
 
 > __Tip!__
 ><br>
diff --git a/docs/automated-tests/responsive/responsive-test.md b/docs/automated-tests/responsive/responsive-test.md
index f1a9a970..4b2934b9 100644
--- a/docs/automated-tests/responsive/responsive-test.md
+++ b/docs/automated-tests/responsive/responsive-test.md
@@ -16,12 +16,16 @@ The __Responsive Web test__ in Test Studio is a separate type of test, which req
 
 To add a __Responsive Web test__ to your project, use the respective type of test to create. You can use the option both from the Project Ribbon or from the <a href="/features/project-explorer/overview#project-context-menu-options" target="_blank">Project Explorer context menu</a>.
 
-<table id="no-table">
-	<tr>
-		<td>![Project Ribbon][1] <br><br>**Project Ribbon**</td>
-		<td>![Project Explorer][2] <br><br>**Project Explorer**</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Project Ribbon][1] <br><br>**Project Ribbon**</td>
+<td>
+		
+![Project Explorer][2] <br><br>**Project Explorer**</td>
+</tr>
+</table>
 
 ## Configure a Device to Simulate
 
diff --git a/docs/automated-tests/scheduling-results/scheduling-results.md b/docs/automated-tests/scheduling-results/scheduling-results.md
index 073902c1..bad72b4f 100644
--- a/docs/automated-tests/scheduling-results/scheduling-results.md
+++ b/docs/automated-tests/scheduling-results/scheduling-results.md
@@ -48,4 +48,3 @@ The <a href="/general-information/test-results/executive-dashboard" target="_bla
 [2]: /img/automated-tests/scheduling-results/scheduling-results/fig2.png
 [3]: /img/automated-tests/scheduling-results/scheduling-results/fig3.png
 [4]: /img/automated-tests/scheduling-results/scheduling-results/fig4.png
-[5]: /img/automated-tests/scheduling-results/scheduling-results/fig5.png
\ No newline at end of file
diff --git a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server.md b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server.md
index a9670a6b..e1e8bd2d 100644
--- a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server.md
+++ b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server.md
@@ -101,6 +101,20 @@ This section appears only if there is an <a href="/features/dialogs-and-popups/d
 
 ![Dialog Handler Update][6c]
 
+1. Click the __Update__ button next to the __New update available__ notification.
+
+2. Hitting the __Update__ button triggers the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server" target="_blank">Test Studio Services Cofigurator application</a> where you need to switch to its <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#browsers-tab" target="_blank">__Browsers__ tab</a>. 
+
+    > __Note!__ 
+    ><br> 
+    > Running the Browser support update through the Test Studio Services Config Wizard requires admin rights. 
+
+    ![Browser Update available](/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png)
+
+3. After the update, restart Test Studio Execution Client for the changes to take effect.
+
+    ![Browser Update available](/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-restart-after-update.png)
+
 ## User Session Configuration
 
 Test Studio requires active user session for executing functional UI tests such as automated tests for WPF and desktop application, and web tests executed in headful browser mode. 
@@ -178,14 +192,14 @@ The Run on start up option allows you to decide whether the Test Studio Session
 [1a]: /img/features/scheduling-test-runs/create-execution-server/fig1a.png
 [2]: /img/features/scheduling-test-runs/create-execution-server/fig2.png
 [2a]: /img/features/scheduling-test-runs/create-execution-server/fig2-configure-button.png
-[3]: /img/features/scheduling-test-runs/create-execution-server/fig3.png
-[4]: /img/features/scheduling-test-runs/create-execution-server/fig4.png
-[5]: /img/features/scheduling-test-runs/create-execution-server/fig5.png
+
+
+
 [6]: /img/features/scheduling-test-runs/create-execution-server/fig6.png
 [6a]: /img/features/scheduling-test-runs/create-execution-server/fig6a.png
 [6b]: /img/features/scheduling-test-runs/create-execution-server/fig6b.png
 [6c]: /img/features/scheduling-test-runs/create-execution-server/fig6c.png
-[7]: /img/features/scheduling-test-runs/create-execution-server/fig7.png
+
 [8]: /img/features/scheduling-test-runs/create-execution-server/fig8.png
 [8a]: /img/features/scheduling-test-runs/create-execution-server/start-session-monitor-win-menu.png
 [8b]: /img/features/scheduling-test-runs/create-execution-server/start-session-monitor-config.png
diff --git a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server.md b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server.md
index f3f2d4f5..cdd4d46f 100644
--- a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server.md
+++ b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server.md
@@ -15,12 +15,14 @@ The below article describes the configuration steps.
   - [Start the Test Studio Scheduling Config Wizard](#start-the-test-studio-scheduling-config-wizard)
   - [Configure the Test Studio Services](#configure-the-test-studio-services)
     - [Communication Tab](#communication-tab)
+    - [Encryption Tab](#encryption-tab)
     - [MongoDB Tab](#mongodb-tab)
     - [Storage Tab](#storage-tab)
     - [Scheduling Tab](#scheduling-tab)
     - [Automatic Email Notification for Scheduled Executions](#automatic-email-notification-for-scheduled-executions)
     - [Executive Dashboard Tab](#executive-dashboard-tab)
     - [Execution Server Tab](#execution-server-tab)
+    - [Browsers Tab](#browsers-tab)
   - [Finish the Test Studio Services Configuration](#finish-the-test-studio-services-configuration)
 
 > __Important__
@@ -54,17 +56,19 @@ You can start the Scheduling config wizard in any of the following ways:
 > - Storage Service: 8492
 > - Execution Machine(s): 55555
 
-There are few tabs in the __Scheduling configuration wizard__, which provide the configuration details for each of the components of the Scheduling setup.
+There are a few tabs in the __Scheduling configuration wizard__, which provide the configuration details for each of the components of the Scheduling setup.
 
 Go through each tab to setup the Test Studio services:
 <!-- no toc -->
   * [Communication Tab](#communication-tab)
+  * [Encryption Tab](#encryption-tab)
   * [MongoDB Tab](#mongodb-tab)
   * [Storage Tab](#storage-tab)
   * [Scheduling Tab](#scheduling-tab)
   * [Automatic Email for Scheduled Test Lists](#automatic-email-for-scheduled-test-lists)
   * [Executive Dashboard Tab](#executive-dashboard-tab)
   * [Execution Server Tab](#execution-server-tab)
+  * [Browsers Tab](#browsers-tab)
 
   
 ### Communication Tab 
@@ -108,6 +112,56 @@ The **Replace Key** section lets you **Generate** a new key. Once generated, the
 <div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
 <br>
 
+### Encryption Tab
+
+The Encryption tab lets you manage the **Encryption Key** which is used to secure sensitive data across the Test Studio projects including: 
+
+- Passwords for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests; SMTP credentials if used in the Scheduling configuration;
+- Password steps recorded in automated tests when the _'Encrypt'_ step property is enabled. 
+
+> **Note**
+> <br>
+> <br>
+> The same __encryption key must be imported on all machines__ where Test Studio product is in use. This is __mandatory__ to ensure encrypted data remains accessible and test execution is not disrupted.
+
+![Encryption tab](/img/features/scheduling-test-runs/create-scheduling-server/encryption-tab.png)
+
+The **Current Key** section indicates which is the key in use. Test Studio installation uses a default encryption key and you see the current key is the __Default Key Loaded__. In this configuration you can't copy or see the key. 
+
+![Default Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-default-key.png)
+
+> **Tip**
+> <br>
+> <br>
+> We __strongly recommend to generate a new encryption key__ and replace it for all machines in the setup.
+><br>
+> See <a href="/knowledge-base/project-configuration-kb/generate-encryption-key" target="_blank">here step-by-step instructions on updating the communication key</a>.
+
+Once a custom key is generated and imported, the **Current Key** section allows you to copy the value of the key using the __Copy to Clipboard__ button, or see it using the __Show__ button (for the cases when copying is not an option). 
+
+![Custom Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-custom-key.png)
+
+The **Replace Key** section lets you **Generate** a new key. Once generated, the new value is populated in the text field and is ready to be imported. Hit the **Import** button to replace the current key with the new one. 
+
+![Replace Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-generate-key.png)
+
+> **Note**
+> <br>
+> <br>
+> When __importing a custom encryption key for the first time__ some of the encrypted data becomes inaccessible. To __continue using your Test Studio projects in such case you must__: 
+> * __re-enter all passwords__ for connecting to source control repository or bug tracking systems, and SMTP settings if used in Scheduling configuration;
+> * all projects on the machine are upgraded to use the new key for password steps in automated tests when the _'Encrypt'_ step property is enabled and for database connection strings used in data driven tests - __no further interaction is needed__ for these.
+
+> If you decide to __regenerate the encryption key and import a new one__ all encrypted data becomes inaccessible. To __continue using your Test Studio projects in such case you must__: 
+> * __re-enter all passwords__ for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests, and SMTP settings if used in Scheduling configuration;
+> * __re-record all password steps__ in automated tests when the _'Encrypt'_ step property is enabled.
+
+> See <a href="/knowledge-base/project-configuration-kb/generate-encryption-key" target="_blank">here step-by-step instructions on updating the encryption key</a>.
+
+<br>
+<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
+<br>
+
 ### MongoDB Tab
 
 The **MongoDB** tab contains the details required for the MongoDB database, which is used as a storage database in the Scheduling configuration.
@@ -206,6 +260,20 @@ The default populated values point to the local machine Scheduling service - _lo
 <div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
 <br>
 
+### Browsers Tab
+
+When available, the __Browser support update__ notification appears along with the __Update__ button and indicates that you must update Test Studio.
+
+![Browser Update available](/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png)
+
+Hit the __Update__ button to trigger the update. After the update, __restart Test Studio__ for the changes to take effect.
+
+![Restart required](/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-restart-after-update.png)
+
+<br>
+<div><a style="float:right" href="#configure-the-test-studio-services">Back to top of section</a></div>
+<br>
+
 ## Finish the Test Studio Services Configuration
 
 When all necessary settings are applied and all services are reported running, close the wizard window to finish the Scheduling Services setup.
@@ -223,7 +291,7 @@ When all necessary settings are applied and all services are reported running, c
 [4]: /img/features/scheduling-test-runs/create-scheduling-server/fig5new.png
 [5a]: /img/features/scheduling-test-runs/create-scheduling-server/fig5a.png
 [6]: /img/features/scheduling-test-runs/create-scheduling-server/fig4new.png
-[7]: /img/features/scheduling-test-runs/create-scheduling-server/fig7.png
+
 [10]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab.png
 [101]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png
 [102]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png
diff --git a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime.md b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime.md
index 195068e1..29c5976f 100644
--- a/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime.md
+++ b/docs/automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime.md
@@ -53,12 +53,3 @@ Few things to consider when choosing an Execution Server machine:
 ## See Also
 
 * <a href="https://www.telerik.com/blogs/test-studio-step-by-step-running-tests-remotely" target="_blank">Test Studio Step-by-Step: Running Tests Remotely</a>
-
-[1]: /img/features/scheduling-test-runs/install-runtime/fig1.png
-[2]: /img/features/scheduling-test-runs/install-runtime/fig2.png
-[3]: /img/features/scheduling-test-runs/install-runtime/fig3.png
-[4]: /img/features/scheduling-test-runs/install-runtime/fig4.png
-[5]: /img/features/scheduling-test-runs/install-runtime/fig5.png
-[6]: /img/features/scheduling-test-runs/install-runtime/fig6.png
-[7]: /img/features/scheduling-test-runs/install-runtime/fig7.png
-[8]: /img/features/scheduling-test-runs/install-runtime/fig8.png
\ No newline at end of file
diff --git a/docs/automated-tests/scheduling/overview.md b/docs/automated-tests/scheduling/overview.md
index cd625031..c34952a1 100644
--- a/docs/automated-tests/scheduling/overview.md
+++ b/docs/automated-tests/scheduling/overview.md
@@ -142,5 +142,4 @@ When these prerequisites are complete - including the case when all these compon
 
 * <a href="https://www.telerik.com/blogs/architecture-remote-execution-test-studio" target="_blank">The Architecture of Remote Execution With Test Studio</a>
 
-[10]: /img/features/scheduling-test-runs/overview/fig1.png
 [1]: /img/automated-tests/scheduling/overview/scheduling-setup-revamp.png
\ No newline at end of file
diff --git a/docs/automated-tests/scheduling/remote-scheduled-run.md b/docs/automated-tests/scheduling/remote-scheduled-run.md
index 2f030884..59d3562f 100644
--- a/docs/automated-tests/scheduling/remote-scheduled-run.md
+++ b/docs/automated-tests/scheduling/remote-scheduled-run.md
@@ -258,7 +258,6 @@ A confirmation message appears when the connection is successful. Confirm the co
 [33]: /img/features/scheduling-test-runs/remote-run-all-in-one/configure-execution-server-button.png
 [4]: /img/features/scheduling-test-runs/remote-run-all-in-one/fig4.png
 [5]: /img/features/scheduling-test-runs/remote-run-all-in-one/fig5.png
-[6]: /img/features/scheduling-test-runs/remote-run-all-in-one/fig6.png
 [10]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab.png
 [101]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png
 [102]: /img/features/scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png
diff --git a/docs/automated-tests/scheduling/schedule-execution.md b/docs/automated-tests/scheduling/schedule-execution.md
index e64581a2..db5ae435 100644
--- a/docs/automated-tests/scheduling/schedule-execution.md
+++ b/docs/automated-tests/scheduling/schedule-execution.md
@@ -121,4 +121,3 @@ To further customize the email notification, click the **Edit** button and input
 [10]: /img/features/scheduling-test-runs/schedule-execution/fig10.png
 [11]: /img/features/scheduling-test-runs/schedule-execution/fig11.png
 [12]: /img/features/scheduling-test-runs/schedule-execution/fig12.png
-[13]: /img/features/scheduling-test-runs/schedule-execution/fig13.png
\ No newline at end of file
diff --git a/docs/automated-tests/scheduling/stop-cancel-scheduled-job.md b/docs/automated-tests/scheduling/stop-cancel-scheduled-job.md
index 7229cd44..786b5a51 100644
--- a/docs/automated-tests/scheduling/stop-cancel-scheduled-job.md
+++ b/docs/automated-tests/scheduling/stop-cancel-scheduled-job.md
@@ -14,12 +14,16 @@ If a test list is scheduled to be executed any time in the future or is set for
 
 In the Results tab when you hover over a scheduled job, a small X button appears. After clicking that Test Studio will prompt you for deleting the scheduled job.
 
-<table id="no-table">
-<tr>
-<td>![X button][1]</td>
-<td>![Delete Series][2]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![X button][1]</td>
+<td>
+
+![Delete Series][2]</td>
 </tr>
-<table>
+</table>
 
 ## Delete the Physical File That Represents the Scheduled Job
 
@@ -37,6 +41,3 @@ __C:\Windows\ServiceProfiles\LocalService\AppData\Roaming\Telerik\TestStudio\Sch
 
 [1]: /img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig1.png
 [2]: /img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig2.png
-[3]: /img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig3.png
-[4]: /img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig4.png
-[5]: /img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig5.png
diff --git a/docs/automated-tests/source-control/git/branch-management.md b/docs/automated-tests/source-control/git/branch-management.md
index 6ab41a07..674072db 100644
--- a/docs/automated-tests/source-control/git/branch-management.md
+++ b/docs/automated-tests/source-control/git/branch-management.md
@@ -2,7 +2,7 @@
 title: Branch Management For Git
 page_title: Branch Management For Git
 description: "Test Studio Git integration Branch Management For Git Source Control"
-publish: true
+published: true
 position: 4
 ---
 # Branch Management For Git Source Control
diff --git a/docs/automated-tests/source-control/git/connect-to-git.md b/docs/automated-tests/source-control/git/connect-to-git.md
index ce457813..b73458bf 100644
--- a/docs/automated-tests/source-control/git/connect-to-git.md
+++ b/docs/automated-tests/source-control/git/connect-to-git.md
@@ -2,7 +2,7 @@
 title: Connect Project To Git
 page_title: Connect Project To Git
 description: "Connect Test Studio Project To Git Source control repository. Use Personal Access token to connect to Git repo accessed with 2FA (two factor authentication). Unable to connect to Git. Error connecting to Git, too many redirects or authentication replays"
-publish: true
+published: true
 position: 2
 ---
 # Connect Project To Git
diff --git a/docs/automated-tests/source-control/git/open-git-project.md b/docs/automated-tests/source-control/git/open-git-project.md
index 864fd640..e6310e73 100644
--- a/docs/automated-tests/source-control/git/open-git-project.md
+++ b/docs/automated-tests/source-control/git/open-git-project.md
@@ -2,7 +2,7 @@
 title: Open Git Project
 page_title: Open Git Project
 description: "Open Test Studio Project To Git Source control repository. Use Personal Access token to connect to Git repo accessed with 2FA (two factor authentication). Unable to connect to Git. Error connecting to Git, too many redirects or authentication replays"
-publish: true
+published: true
 position: 1
 ---
 # Open Git Project
@@ -10,7 +10,7 @@ position: 1
 **Open** Git project in the terms of Test Studio is equal to __cloning an existing repository__. This option creates a local copy of the remote project in the specified folder during establishing connection.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 Follow the steps to open a Test Studio project stored into a remote Git repository.
diff --git a/docs/automated-tests/source-control/git/supported-git-commands.md b/docs/automated-tests/source-control/git/supported-git-commands.md
index fea81ee2..ddcc9c26 100644
--- a/docs/automated-tests/source-control/git/supported-git-commands.md
+++ b/docs/automated-tests/source-control/git/supported-git-commands.md
@@ -40,7 +40,7 @@ Or alternatively from the Source Control ribbon
 
 [1]: /img/features/source-control/git/supported-git-commands/fig1.png
 [2]: /img/features/source-control/git/supported-git-commands/fig2.png
-[5]: /img/features/source-control/git/open-git-project/fig5.png
+
 [6]: /img/features/source-control/open-tfs-project/fig6.png
 [7]: /img/features/source-control/open-tfs-project/fig7.png
 [8]: /img/features/source-control/open-tfs-project/fig8.png
diff --git a/docs/automated-tests/source-control/sc-alternatives.md b/docs/automated-tests/source-control/sc-alternatives.md
index 11077520..78a0e03b 100644
--- a/docs/automated-tests/source-control/sc-alternatives.md
+++ b/docs/automated-tests/source-control/sc-alternatives.md
@@ -2,7 +2,7 @@
 title: Source Control Alternatives
 page_title: Alternative File-Based Source Control Systems
 description: "Alternative File-Based Source Control Systems. Test Studio can interact with any file-based source control system"
-position: 2
+position: 5
 ---
 # Alternative File-Based Source Control Systems
 
diff --git a/docs/automated-tests/test-list-results/analyze-test-list-results.md b/docs/automated-tests/test-list-results/analyze-test-list-results.md
index 26183c77..9d856bee 100644
--- a/docs/automated-tests/test-list-results/analyze-test-list-results.md
+++ b/docs/automated-tests/test-list-results/analyze-test-list-results.md
@@ -31,7 +31,7 @@ The **Test Results** panel allows you to traverse test execution results, drilli
 
 ## Failed Test List Result
 
-If one test in the test list fails, the overall status of the test list is reported as _Failed_. To find out details about what caused the failure, you can drill down to the failing test and step. The faulty step will be marked with red cross sign to indicate that it wasn't successfully executed. Double click the red cross and open the <a href="/automated-tests/test-results/step-failure-details" target="_blank">step failure details</a>, which provide useful information for the failure.
+If one test in the test list fails, the overall status of the test list is reported as _Failed_. To find out details about what caused the failure, you can drill down to the failing test and step. The faulty step will be marked with red cross sign to indicate that it wasn't successfully executed. __Double click the red cross and open the <a href="/automated-tests/test-results/step-failure-details" target="_blank">step failure details</a>__, which provide useful information for the failure.
 
 ![Step results][2a]
 
@@ -114,7 +114,7 @@ Click the _'Screen Recording Info'_ icon for any of the tests which triggered vi
 [1a]: /img/automated-tests/test-list-results/analyze-test-results/fig1a.png
 [2]: /img/automated-tests/test-list-results/analyze-test-results/fig2.png
 [2a]: /img/automated-tests/test-list-results/analyze-test-results/fig2a.png
-[3]: /img/automated-tests/test-list-results/analyze-test-results/fig3.png
+
 [4]: /img/automated-tests/test-list-results/analyze-test-results/fig4.png
 [5]: /img/automated-tests/test-list-results/analyze-test-results/fig5.png
 [6]: /img/automated-tests/test-list-results/analyze-test-results/fig6.png
diff --git a/docs/automated-tests/test-list-results/calendar.md b/docs/automated-tests/test-list-results/calendar.md
index 138312dd..5e399eaa 100644
--- a/docs/automated-tests/test-list-results/calendar.md
+++ b/docs/automated-tests/test-list-results/calendar.md
@@ -40,8 +40,8 @@ Double click a test list result entry to view its details displayed on the right
 
 ![drill down test list result][6]
 
-[1]: /img/automated-tests/test-list-results/calendar/fig1.png
-[2]: /img/automated-tests/test-list-results/calendar/fig2.png
+
+
 [3]: /img/automated-tests/test-list-results/calendar/fig3.png
 [4]: /img/automated-tests/test-list-results/calendar/fig4.png
 [5]: /img/automated-tests/test-list-results/calendar/fig5.png
diff --git a/docs/automated-tests/test-list-results/export-test-results.md b/docs/automated-tests/test-list-results/export-test-results.md
index 63715f2c..1519d001 100644
--- a/docs/automated-tests/test-list-results/export-test-results.md
+++ b/docs/automated-tests/test-list-results/export-test-results.md
@@ -136,11 +136,11 @@ All of the supported export file types can be directly __sent via email__. Selec
 * **Submit Bug**: Load the <a href="/features/integration/bug-tracking/submit-bug" target="_blank">Submit Bug</a> dialog and log a bug about the failed result in your previously configured bug tracking application.
 
 
-[1]: /img/automated-tests/test-list-results/export-test-results/fig1.png
-[2]: /img/automated-tests/test-list-results/export-test-results/fig2.png
+
+
 [3]: /img/automated-tests/test-list-results/export-test-results/fig3.png
-[4]: /img/automated-tests/test-list-results/export-test-results/fig4.png
-[5]: /img/automated-tests/test-list-results/export-test-results/fig5.png
+
+
 [6]: /img/automated-tests/test-list-results/export-test-results/fig6.png
 [7]: /img/automated-tests/test-list-results/export-test-results/fig7.png
 [8]: /img/automated-tests/test-list-results/export-test-results/fig8.png
diff --git a/docs/automated-tests/test-lists/rerun-failed-tests.md b/docs/automated-tests/test-lists/rerun-failed-tests.md
index 2f262daa..eaf3a9a3 100644
--- a/docs/automated-tests/test-lists/rerun-failed-tests.md
+++ b/docs/automated-tests/test-lists/rerun-failed-tests.md
@@ -23,7 +23,6 @@ The <a href="/automated-tests/test-list-results/analyze-test-list-results#automa
 ><br>
 > The tests need to be designed as autonomous tests - if these are dependent on the previous tests in the list, this setting will not be applicable.
 
-[1]: /img/automated-tests/test-lists/test-list-runs-specifics/fig1.png
-[2]: /img/automated-tests/test-lists/test-list-runs-specifics/fig2.png
+
+
 [3]: /img/automated-tests/test-lists/test-list-runs-specifics/fig3.png
-[4]: /img/automated-tests/test-lists/test-list-runs-specifics/fig4.png
diff --git a/docs/automated-tests/test-lists/test-list-video-recording.md b/docs/automated-tests/test-lists/test-list-video-recording.md
index 8b056e40..402047c4 100644
--- a/docs/automated-tests/test-lists/test-list-video-recording.md
+++ b/docs/automated-tests/test-lists/test-list-video-recording.md
@@ -76,5 +76,5 @@ Click _"Other Options.."_ -> Uncheck _"Display encoder status"_
 
 [1]: /img/automated-tests/test-lists/test-list-runs-specifics/fig1.png
 [2]: /img/automated-tests/test-lists/test-list-runs-specifics/fig2.png
-[3]: /img/automated-tests/test-lists/test-list-runs-specifics/fig3.png
+
 [4]: /img/automated-tests/test-lists/test-list-runs-specifics/fig4.png
diff --git a/docs/automated-tests/test-lists/test-lists-standalone.md b/docs/automated-tests/test-lists/test-lists-standalone.md
index 785469e1..fb1f1f5c 100644
--- a/docs/automated-tests/test-lists/test-lists-standalone.md
+++ b/docs/automated-tests/test-lists/test-lists-standalone.md
@@ -14,7 +14,7 @@ Test Studio provides two options for a test list - a static one, which contains
 * <a href="#dynamic-test-lists">Dynamic Test List</a> 
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## <strong>Static Test Lists</strong>
@@ -42,12 +42,16 @@ The **Performance** test list type allows you to execute **performance runs for
 
 The **Manual** type of list allows you to add only **manual** tests and execute them together (the rest of the tests are greyed out). Run the manual tests sequentially or toggle back and forth between them using the **Previous** and **Next** buttons at the bottom.
 
-<table id="no-table">
-	<tr>
-		<td>![Previous][2]</td>
-		<td>![Next][3]</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+![Previous][2]</td>
+<td>
+		
+![Next][3]</td>
+</tr>
+</table>
 
 ## <strong>Dynamic Test Lists</strong>
 
@@ -69,7 +73,7 @@ These criteria can be used when <a href="/features/test-lists/create-test-lists#
 ><br>
 > Each time you trigger a dynamic list execution, Test Studio queries the project and executes the tests, that __meet the criteria of the _Rules___. Thus, if there are new tests added after the test list creation, and these meet the criteria of the rules, they will be included in the test list upon execution.
 
-## See also ##
+## See also 
 
 * <a href="http://blogs.telerik.com/automated-testing-tools/posts/13-09-23/power-of-dynamic-test-lists" target="_blank">Power of Dynamic Test Lists</a>
 
@@ -77,10 +81,7 @@ These criteria can be used when <a href="/features/test-lists/create-test-lists#
 [2]: /img/automated-tests/test-lists/test-lists-types/fig2.png
 [3]: /img/automated-tests/test-lists/test-lists-types/fig3.png
 [4]: /img/automated-tests/test-lists/test-lists-types/fig4.png
-[5]: /img/automated-tests/test-lists/test-lists-types/fig5.png
+
 [6]: /img/automated-tests/test-lists/test-lists-types/fig6.png
-[7]: /img/automated-tests/test-lists/test-lists-types/fig7.png
+
 [8]: /img/automated-tests/test-lists/test-lists-types/fig8.png
-[9]: /img/automated-tests/test-lists/test-lists-types/fig2_FilterTestsByType.png
-[10]: /img/automated-tests/test-lists/test-lists-types/fig2_searchField.png
-[11]: /img/automated-tests/test-lists/test-lists-types/fig2_collapse.png
diff --git a/docs/automated-tests/test-lists/test-lists-type-standalone.md b/docs/automated-tests/test-lists/test-lists-type-standalone.md
deleted file mode 100644
index c003b99f..00000000
--- a/docs/automated-tests/test-lists/test-lists-type-standalone.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Test Lists Type (Standalone)
-page_title: Test Lists Type (Standalone)
-description: "Test Studio Test Lists Type automated test list execute load test in a test list. execute performance tests in a test list "
-position: 2
-publish: false
----
-# Test Lists Type (Standalone) #
-
-With the introduction of Performance, Load and Manual Testing, you now have the ability to designate a Test List Type.
-
-![Test list type][1]
-
-## Automated ##
-
-The **Automated** Test List Type is the standard to execute one or more **Web**, **Load** or **WPF** Tests. Manual Tests cannot be added.
-
-## Manual ##
-
-Add one or more **Manual** Tests and execute them together. Automated Tests cannot be added. Run them sequentially or toggle back and forth between tests using the **Previous** and **Next** buttons at the bottom.
-
-<table id="no-table">
-	<tr>
-		<td>![Previous][2]</td>
-		<td>![Next][3]</td>
-	</tr>
-<table>
-
-## Performance ##
-
-Create **Performance** Runs for one or more Web Tests. Click **Configure** to edit the <a href="/features/testing-types/performance-testing/gather-perfomance-data" target="_blank">settings</a> of each Run.
-
-![Configure][4]
-
-[1]: /img/general-information/test-execution/test-lists-type-standalone/fig1.png
-[2]: /img/general-information/test-execution/test-lists-type-standalone/fig2.png
-[3]: /img/general-information/test-execution/test-lists-type-standalone/fig3.png
-[4]: /img/general-information/test-execution/test-lists-type-standalone/fig4.png
-
diff --git a/docs/automated-tests/test-results/step-failure-details.md b/docs/automated-tests/test-results/step-failure-details.md
index cf548662..36fe0c4b 100644
--- a/docs/automated-tests/test-results/step-failure-details.md
+++ b/docs/automated-tests/test-results/step-failure-details.md
@@ -8,14 +8,20 @@ position: 1
 
 The Step Failure Details dialog collects all the information related to the failed test step. This includes failure details, screenshots, and a snapshot of the DOM. The Step Failure Details section lists handy suggestion how you can resolve the specific error.
 
-Let's use a simple test as a baseline, which navigates to bing.com and verifies the text content of the _Images_ link. The one demonstrated below is modified to look for _'ImagesModifiedToFail'_ instead of _'Images'_ so that it actually fails.
+Let's use any sample test which fails as an example for the below article. 
 
 ## Step Failure Details Section
 
-<a href="/automated-tests/test-execution/quick-execution" target="_blank">Execute the sample test</a> and wait for the run to finish. The overall result of the test run is reported failed and the failing step is marked in the test. The __Step Failure Details__ section, displayed under, provides an overview of the __reason for the failure__, the __images__, and __suggestions__ what options you have to troubleshoot the error.
+<a href="/automated-tests/test-execution/quick-execution" target="_blank">Execute the sample test</a> and wait for the run to finish. The overall result of the test run is reported failed and the failing step is marked in the test. The __Step Failure Details__ section displayed under provides an overview of the __reason for the failure__, the __images__, and __suggestions__ what options you have to troubleshoot the error.
 
 ![Step Failure Details Section][10]
 
+<!-- no toc -->
+- [Failure Reason Section](#failure-reason-section)
+- [Suggestions Section](#suggestions-section)
+- [Images Section](#images-section)
+
+
 ### Failure Reason Section
 
 The __Failure Reason__ section shows a summary of the error, which caused the failure. In it you have quick access to the following details:
@@ -23,11 +29,15 @@ The __Failure Reason__ section shows a summary of the error, which caused the fa
 - [DOM tree on failure](#page-dom-tab),
 - [Resolve failure suggestions](#resolve-failure-tab),
 - __Copy__ button to get the error log in clipboard,
-- [export the overall step failure details](#how-to-export-the-step-failure-details),
-- trigger the form to submit a bug, if you have <a href="/features/integration/bug-tracking/configuration" target="_blank">configured a bug tracking tool</a> for the project.
+- [Export the overall step failure details](#how-to-export-the-step-failure-details),
+- Trigger the form to submit a bug, if you have <a href="/features/integration/bug-tracking/configuration" target="_blank">configured a bug tracking tool</a> for the project.
 
 ![Failure Reason Section][11]
 
+<br>
+<div><a style="float:right" href="#step-failure-details-section">Back to top of section</a></div>
+<br>
+
 ### Suggestions Section
 
 The __Suggestion__ section hints you with handy features in Test Studio for __troubleshooting a failing test__ and these are based on the specific error. Among these are
@@ -39,6 +49,10 @@ The __Suggestion__ section hints you with handy features in Test Studio for __tr
 
 ![Suggestion Section][12]
 
+<br>
+<div><a style="float:right" href="#step-failure-details-section">Back to top of section</a></div>
+<br>
+
 ### Images Section
 
 The __Images__ section lists the __state of the application at the time of failure__ compared to what was captured when the test steps were recorded. The images are often useful to identify that certain step gets executed before the application is in the correct state to accept the action. Such timing issues are usually resolved by adding <a href="/features/recorder/advanced-recording-tools/element-steps/verifications/wait" target="_blank">wait steps</a> or <a href="/features/custom-steps/execution-delay" target="_blank">execution delays</a> before the action is sent towards the page.
@@ -49,6 +63,10 @@ If you click the magnifier icon, the images are opened in full size and can be z
 
 ![Suggestion Section][14]
 
+<br>
+<div><a style="float:right" href="#step-failure-details-section">Back to top of section</a></div>
+<br>
+
 ## How to Open the Step Failure Details Window?
 
 Execute the sample test and wait until it fails. Hover the mouse over the red cross next to the failed step - a **Step Failure Summary** will popup for a while.
@@ -63,9 +81,16 @@ Click on the red cross to open the overall **Step Failure Details** with possibl
 
 The failure dialog provides a variety of useful details, which can be used for the different failure scenarios, divided in few tabs. Let's have an overview for each of these tabs and how these can help us find the solution for the failing step.
 
+<!-- no toc -->
+- [Failure Tab](#failure-tab)
+- [Images Tab](#images-tab)
+- [Page DOM Tab](#page-dom-tab)
+- [Resolve Failure Tab](#resolve-failure-tab)
+
+
 ### Failure Tab
 
-The **'Failure'** tab provides a summarized information for the encountered error - sometimes this can be quite descriptive, and other times it could be more generic.
+The **Failure** tab provides a summarized information for the encountered error - sometimes this can be quite descriptive, and other times it could be more generic.
 
 ![The failure tab][3]
 
@@ -83,15 +108,23 @@ From this view you can also access other useful options:
 
 * **Resolve**: navigates to the ***'Resolve Failure'*** tab, where you will get suggestions to apply a fix depending on the error.
 
+<br>
+<div><a style="float:right" href="#what-to-look-for-in-the-step-failure-details">Back to top of section</a></div>
+<br>
+
 ### Images Tab
 
-The **'Images'** tab displays two screenshots of the browser: the state at time of failure and the expected state. Storyboard must be enabled in <a href="/features/project-settings/recording-options" target="_blank">Project Settings</a> for the expected state image to appear.
+The **Images** tab displays two screenshots of the browser: the state at time of failure and the expected state. Storyboard must be enabled in <a href="/features/project-settings/recording-options" target="_blank">Project Settings</a> for the expected state image to appear.
 
 ![Images tab][4]
 
+<br>
+<div><a style="float:right" href="#what-to-look-for-in-the-step-failure-details">Back to top of section</a></div>
+<br>
+
 ### Page DOM Tab
 
-The **'Page DOM'** tab displays a snapshot of the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure" target="_blank">DOM state</a> at the time of failure. You can use it to locate the element in the DOM tree and check its state, content, etc.
+The **Page DOM** tab displays a snapshot of the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure" target="_blank">DOM state</a> at the time of failure. You can use it to locate the element in the DOM tree and check its state, content, etc.
 
 ![Page DOM tab][5]
 
@@ -108,6 +141,10 @@ The DOM on Failure is most helpful in situations where a test does not properly
 
 The DOM on Failure provides a record of the elements that Test Studio could see in the browser at the time the test failed. Compare with <a href="/features/elements-explorer/find-element" target="_blank">the find logic</a> of the element that Test Studio expects to be in the browser during the failed step. This helps to identify which element should have been targeted, why the incorrect element may have been targeted, or what state the browser may have been in instead of the correct state.
 
+<br>
+<div><a style="float:right" href="#what-to-look-for-in-the-step-failure-details">Back to top of section</a></div>
+<br>
+
 ### Resolve Failure Tab
 
 The **'Resolve Failure'** tab provides the opportunity to identify and correct the issue that caused the failure. For validation steps, the Sentence Verification Builder allows you to reload the page, make changes to the verification sentence, and re-run the verification until the verification passes.
@@ -122,11 +159,21 @@ If the element was located on the page using the backup search recorded for it,
 
 ![Resolve Failure tab missing element troubleshoot][8]
 
+<br>
+<div><a style="float:right" href="#what-to-look-for-in-the-step-failure-details">Back to top of section</a></div>
+<br>
+
 ## How to Export the Step Failure Details?
 
-When a test is failing and you need to share the identified faulty behavior with a team mate, developer, or the Test Studio Support team, you can easily __export the complete set of failure details into a single zipped file__. The archive contains the failed step log, the complete test execution log, a screenshot of the web page and a snapshot of the DOM tree at the time of failure. To get the zipped file, click on the __Export__ button on the _Failure_ tab and choose a folder where to store it.
+When a test is failing and you need to share the identified faulty behavior with a team mate, developer, or the Test Studio Support team, you can easily __export the complete set of failure details into a single zipped file__. The archive contains the failed step log, the complete test execution log, a screenshot of the web page and a snapshot of the DOM tree at the time of failure.
+
+- One option to get the zipped folder is to use the __Export__ button in the __Failure Reason Section__. 
+
+    ![failure section export button](/img/automated-tests/test-results/new-step-failure-details/failure-section-export-button.png)
+
+- The other option to get the zipped file is to use the __Export__ button on the __Failure__ tab in the Step Failure window and choose a folder where to store it.
 
-![Export the step failure details][9]
+    ![Export the step failure details][9]
 
 [10]: /img/automated-tests/test-results/new-step-failure-details/new1.png
 [11]: /img/automated-tests/test-results/new-step-failure-details/new2.png
@@ -134,7 +181,6 @@ When a test is failing and you need to share the identified faulty behavior with
 [13]: /img/automated-tests/test-results/new-step-failure-details/new4.png
 [14]: /img/automated-tests/test-results/new-step-failure-details/new5.png
 
-[1]: /img/automated-tests/test-results/step-failure-details/fig1.png
 [2]: /img/automated-tests/test-results/new-step-failure-details/fig2.png
 [2a]: /img/automated-tests/test-results/new-step-failure-details/fig2a.png
 [3]: /img/automated-tests/test-results/step-failure-details/fig3.png
diff --git a/docs/automated-tests/troubleshooting/element-not-found.md b/docs/automated-tests/troubleshooting/element-not-found.md
index 6c28deaf..0bbc4184 100644
--- a/docs/automated-tests/troubleshooting/element-not-found.md
+++ b/docs/automated-tests/troubleshooting/element-not-found.md
@@ -36,11 +36,11 @@ Upon <a href="/automated-tests/test-execution/quick-execution" target="_blank">e
 
 Looking at the <a href="/automated-tests/test-results/step-failure-details" target="_blank">step failure details</a> and the <a href="/automated-tests/test-results/step-failure-details#images-section" target="_blank">images</a>, we can clearly see the correct page is loaded, the element is there, but the test failed with the following failure reason:
 
-```
+````
 Attempting to find [Html] element using Find logic  (Html): 
 [id 'Exact' 1fe4125d-59c9-51c3-ba05-59d1e602d1dc] AND [tagname 'Exact' input]
 Unable to locate element. Search failed!
-```
+````
 
 ## Troubleshoot the 'Element Not Found' Error
 
@@ -64,9 +64,9 @@ Click on __Update Filters__ button to replace the id in the find expression with
 
 The Test Studio find expression builder lists all attributes of the opened element and any of these can be added in the find expression. If we look closely at the _input_ element, we see its __name__ attribute is unique and, if it is used in the find expression instead of the __id__, finding the element in test runtime gets more robust.
 
-```HTML
+````HTML
 <input class="form-control" type="text" placeholder="User Name" name="UserName" id="041a3438-f784-c57c-1805-72a73d88ff1d">
-```
+````
 
 Remove the __id__ filter from the current find expression and add the __name__ filter instead.
 
diff --git a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-application-log.md b/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-application-log.md
deleted file mode 100644
index 4b1251f2..00000000
--- a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-application-log.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Using the Application Log
-page_title: Using the Test Studio Application Log
-description: "Using the Test Studio Application Log. How helps me the Test Studio application log. What errors can be identified in the Test Studio Application Log. "
-previous_url: /user-guide/troubleshooting_guide/troubleshooting_tools/using_the_application_log.aspx, /user-guide/troubleshooting_guide/troubleshooting_tools/using_the_application_log
-position: 1
-publish: false
----
-# Using the Test Studio Application Log
-
-**What is the application log?**
-
-The <a href="https://www.telerik.com/teststudio" target="_blank">Test Studio</a> application log is a record of log messages recorded by Test Studio throughout runtime. All records in the application log, are designed to indicate important events and help pinpoint where problems may occur. This is distinct from the execution log, which only records the attempted steps and encountered exceptions during test execution.
-
-**When to turn on the application log?**
-
-Whenever Test Studio behaves differently than expected, an application log can give more information about why. This is especially true for situations other than test failure or code compilation. For example:
-
-- Test Studio generates error messages;
-
-- Test Studio closes unexpectedly;
-
-- Test Studio stops responding;
-
-- Test Studio interacts with other software (TeamPulse, TFS, QC) differently than expected;
-
-- A Test Studio execution browser closes unexpectedly or stops responding during execution;
-
-- Test Studio cannot connect to a browser.
-
-**Generating the application log.**
-
-You can <a href="/knowledge-base/best-practices-kb/generate-application-log" target="_blank">generate an application log</a> from the help tab.
-
-**What to look for in the application log.**
-
-The application log can be useful in many ways to Test Studio support engineers and developers. Users with issues should look for exceptions. 
-
-![Log][1]
-
-These are usually accompanied with error messages that may guide you in troubleshooting. If you are not familiar with the error message, try searching our documentation for it. If you still cannot understand the error, consider attaching a copy of the log to a <a href="/knowledge-base/best-practices-kb/submit-support-ticket" target="_blank">support ticket</a>. 
-
-[1]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log/fig1.png
\ No newline at end of file
diff --git a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-dom-on-failure.md b/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-dom-on-failure.md
deleted file mode 100644
index 6edf3814..00000000
--- a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-dom-on-failure.md
+++ /dev/null
@@ -1,39 +0,0 @@
----
-title: Using the DOM on Failure
-page_title: Using the DOM on Failure
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Using the DOM on Failure
-
-
-**What is the DOM on Failure?**
-
-The DOM on failure is a copy of the state of the <a href="/features/elements-menu/dom-explorer" target="_blank">DOM</a> for the execution browser at the time a test fails. The DOM on Failure is available after test failure as part of the <a href="/getting-started/test-results/step-failure-details" target="_blank">failure details</a>. 
-
-![Page DOM][1]
-
-> If similar issues occur with a test that passes, find the relevant element using the <a href="/features/elements-menu/dom-explorer" target="_blank">DOM Explorer</a>.
-
-**When to use the DOM on Failure**
-
-The DOM on Failure is most helpful in situations where a test does not properly locate and act on a particular element. This includes any of the following, when unexpected:
-
-- ‘Element does not exist’ exceptions;
-
-- ‘Element not found’ exceptions;
-
-- ‘Timed out waiting for element’ exceptions;
-
-- Test execution targets incorrect element.
-
-**Exporting the DOM on Failure**
-
-In the <a href="/getting-started/test-results/step-failure-details" target="_blank">Step Failure Details</a> window, you can choose to export results to file, including the DOM on Failure.
-
-**What to look for in the DOM on Failure**
-
-The DOM on Failure provides a record of the elements that Test Studio could see in the browser at the time the test failed. Compare with <a href="/features/elements-explorer/find-element" target="_blank">the find logic</a> of the element that Test Studio expects to be in the browser during the failed step. This helps to identify which element should have been targeted, why the incorrect element may have been targeted, or what state the browser may have been in instead of the correct state.
-
-[1]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure/fig1.png
\ No newline at end of file
diff --git a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-execution-log.md b/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-execution-log.md
deleted file mode 100644
index 9bdb3504..00000000
--- a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-execution-log.md
+++ /dev/null
@@ -1,54 +0,0 @@
----
-title: Using the Test Execution Log
-page_title: Using the Test Execution Log in Test Studio
-description: "What is the Test Execution log in Test Studio and how to use this. How can the Execution log help me in troubleshooting failures. Test Studio Test execution failures and how to resolve these. What causes a Test Studio test failure. "
-previous_url: /user-guide/troubleshooting_guide/troubleshooting_tools/using_the_execution_log.aspx, /user-guide/troubleshooting_guide/troubleshooting_tools/using_the_execution_log
-position: 1
-publish: false
----
-# Using the Test Execution Log in Test Studio
-
-The execution log in <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> is a generated after a <a href="/getting-started/first-execution#quick-test-execution" target="_blank">quick test execution</a>. It is also included in the thorough <a href="/getting-started/test-results/step-failure-details" target="_blank">step failure details</a>.
-
-You can pull it out by clicking **View Log** button in the test view
-
-![View Log][1]
-
-or from failure details:
-
-![Step failure details][2]
-
-## What Details Contains the Execution Log? 
-
-The execution log is a record of the steps executed in the test, whether they passed or failed, and if they failed, why. It records what actions a step takes and what elements it acts upon. It includes all steps in one sequence, regardless of whether they are part of the main parent test or a test as step.
-
-![log][3]
-
-It says what errors arose in the case of a failure, giving detailed information on where the error occurred, and whether the error caused the test to fail.
-
-![log][4]
-
-For these reasons, the execution log is an excellent resource for forming a clear story of what led to a failure.
-
-## When to Export the Execution Log?
-
-Anytime a test fails unexpectedly and without clear explanation, the execution log can help in determining the cause. This includes any of the following, when unexpected:
-
--          The test closes after waiting;
-
--          A step fails unexpectedly and the test continues;
-
--          The test fails without executing any steps;
-
-## How to Export the Execution Log?
-
-In the Step Failure Details window, you can choose to export results to file, including the execution log.
-
-## What to Look for in the Execution Log?
-
-The Execution Log lists four main types of information. Two of these, the action taken by the step and the element acted upon by the step, are included in the Test view. However, they can still be useful if the recipient of the execution log does not have access to the associated test (for example, the Test Studio support team). The other two categories of information are step execution properties (including whether to continue on failure and whether to break on execution) and error information. Each of these pieces of information is contained elsewhere in Test Studio, the Execution log provides a sequential summary of the entire test leading up to failure.
-
-[1]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig1.png
-[2]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig2.png
-[3]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig3.png
-[4]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig4.png
diff --git a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-visual-debugger.md b/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-visual-debugger.md
deleted file mode 100644
index cbc33916..00000000
--- a/docs/automated-tests/troubleshooting/troubleshooting-tools-tg/using-the-visual-debugger.md
+++ /dev/null
@@ -1,60 +0,0 @@
----
-title: Using the Visual Debugger
-page_title: Using the Visual Debugger
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Using the Visual Debugger
-
-**What is the Visual Debugger?**
-
-The <a href="/getting-started/test-execution/visual-debugger" target="_blank">Visual Debugger</a> is a set of options for debugging a test while test execution is paused. These options allow you to navigate a test, view debugging information for the current step, and report bugs.
-
-![Debug options][1]
-
-**When to use the Visual Debugger**
-
-The Visual Debugger is helpful in situations where a test does not behave as expected, especially when it is not clear at which step a particular problem occurred. It is also helpful for slowing down test execution and observing test behavior step by step.
-
-First, you can use the visual debugger to help identify why a step did not act upon the correct element. This includes diagnosing:
-
-- ‘Element does not exist’ exceptions;
-
-- ‘Element not found’ exceptions;
-
-- ‘Timed out waiting for element’ exceptions.
-
-
-Even if a test step passes, you can still use the visual debugger to analyze its behavior.
-
-Lastly, you can use the Visual Debugger to record instances in which your target application behaves unexpectedly.
-
-**How to use the Visual Debugger**
-
-![Coded step][2]
-
-The most commonly used feature of the Visual Debugger is the step status message and progress bar, which show which step is being executed, the description of that step, and what fraction of the test steps have completed. Keep your eye on this to help follow any test execution in Test Studio. This way, if you find a problem with one of your test steps, you will know which step to change.
-
-![buttons][3]
-
-The bottom row of buttons provides options for controlled execution of the test. The Visual Debugger allows you to replay steps and move through your test one step at a time. This is helpful for careful observation of test behavior. Specifically, it can help identify which test step is putting the target application in a particular state.
-
-![icons][4]
-
-The top row of buttons provides options for analyzing and recording information about the current test step.
-
-- ‘Open the DOM Explorer’ displays the <a href="/features/elements-menu/dom-explorer" target="_blank">DOM Explorer</a> for the currently displayed page. This can help identify the correct find logic for a particular element, or whether a desired element is missing.
-
-- ‘Capture an image of the current page and its DOM creates a complete record of the current state of the application. You can use this record to compare to the find logic for the step, or to communicate the state of the application to a third party, such as a developer or <a href="/knowledge-base/best-practices-kb/submit-support-ticket" target="_blank">Test Studio support engineer</a>.
-
-- ‘Diagnose the currently failed step’ shows the <a href="/features/elements-explorer/find-element" target="_blank">find logic</a> for the current step. In combination with the DOM Explorer, this find logic can help diagnose steps that fail due to faulty find expressions.
-
-- ‘View the current execution log’ displays the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log" target="_blank">execution log</a> at the time of the current step. Since the execution log contains details on step failure, it can act as a starting point in your debugging. For example, if the failure log contains an ‘Element does not exist’ exception, you can check to see if the element is missing altogether or whether the step used bad find logic.
-
-- ‘Submit Bug’ opens the <a href="/features/integration/bug-tracking/submit-bug" target="_blank">Submit a Bug</a> dialog, so you can easily record any bugs in the target application during debugging.
-
-[1]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig1.png
-[2]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig2.png
-[3]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig3.png
-[4]: /img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig4.png
diff --git a/docs/automated-tests/troubleshooting/use-annotated-run.md b/docs/automated-tests/troubleshooting/use-annotated-run.md
index 44ee9dc1..7535cbc0 100644
--- a/docs/automated-tests/troubleshooting/use-annotated-run.md
+++ b/docs/automated-tests/troubleshooting/use-annotated-run.md
@@ -28,13 +28,13 @@ Upon <a href="/automated-tests/test-execution/quick-execution" target="_blank">e
 
 The standard troubleshooting implies to refer the <a href="/automated-tests/test-results/step-failure-details" target="_blank">step failure details</a> for more information and you can see the following failure message:
 
-```
+````
 Unable to locate element by Find Expression!
 Attempting to find [Html] element using 
 Find logic 
  (Html): [tagname 'Exact' span] AND [TextContent 'Exact' Impressive]
 Unable to locate element. Search failed!
-```
+````
 
 Based on this message, you find out that Test Studio is looking for a _span_ element with _Text Content_, which is exactly _Impressive_. As the find expression seems to be pointing to a specific element, Test Studio should not have a troubles to locate the element and this doesn't look as the reason for the failure.
 
diff --git a/docs/automated-tests/troubleshooting/visual-debugger.md b/docs/automated-tests/troubleshooting/visual-debugger.md
index b27680f7..44da9e04 100644
--- a/docs/automated-tests/troubleshooting/visual-debugger.md
+++ b/docs/automated-tests/troubleshooting/visual-debugger.md
@@ -86,6 +86,3 @@ Once finished with debugging process for the current step, you have few options
 * __Resume normal execution__ using the *Play* button.
 
 	![Visual Debugger Resume normal execution](/img/automated-tests/troubleshooting/visual-debugger/fig12.png)
-
-[1]: /img/general-information/test-execution/visual-debugger/fig1.png
-[2]: /img/general-information/test-execution/visual-debugger/fig2.png
\ No newline at end of file
diff --git a/docs/automated-tests/vs-plugin/preview-code.md b/docs/automated-tests/vs-plugin/preview-code.md
deleted file mode 100644
index fcd2d9a8..00000000
--- a/docs/automated-tests/vs-plugin/preview-code.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Preview Code (VS plugin)
-page_title: Preview Code (VS plugin)
-description: "Preview Code (VS plugin) in Test Studio Plugin for Visual Studio."
-position: 7
-publish: false
----
-# Preview Code (VS plugin) #
-
-Use the **Preview Code** button to see the corresponding code for your Test Studio test.
-
-![Preview Code][1]
-
-[1]: /img/advanced-topics/coded-steps/preview-code/fig1.png
-
-
diff --git a/docs/automated-tests/vs-plugin/test-explorer-settings.md b/docs/automated-tests/vs-plugin/test-explorer-settings.md
index aaa1a62b..d6a272b5 100644
--- a/docs/automated-tests/vs-plugin/test-explorer-settings.md
+++ b/docs/automated-tests/vs-plugin/test-explorer-settings.md
@@ -32,9 +32,3 @@ __3.&nbsp;__ To use these Test Studio specific settings for the test runs initia
 ![Set run settings for Test Explorer 2019 and 2022](/img/knowledge-base/visual-studio-kb/test-explorer-settings/run-settings-vs22.png)
 
 __4.&nbsp;__ You can store the file in the project root folder and use the option __Auto Detect runsettings Files__. The alternative is to specify the file from an external location through the __Select Solution Wide runsettings File__.
-
-
-[1]: /img/knowledge-base/visual-studio-kb/test-explorer-settings/fig1.png
-[2]: /img/knowledge-base/visual-studio-kb/test-explorer-settings/fig2.png
-[3]: /img/knowledge-base/visual-studio-kb/test-explorer-settings/fig3.png
-[4]: /img/knowledge-base/visual-studio-kb/test-explorer-settings/fig4.png
\ No newline at end of file
diff --git a/docs/automated-tests/vs-plugin/test-results-vs.md b/docs/automated-tests/vs-plugin/test-results-vs.md
index b075ffea..06429ce5 100644
--- a/docs/automated-tests/vs-plugin/test-results-vs.md
+++ b/docs/automated-tests/vs-plugin/test-results-vs.md
@@ -27,7 +27,7 @@ When executing the tests from the <a href="/getting-started/test-execution/vs-20
 
 ![View test results 2012][6]
 
-[3]: /img/general-information/test-results/test-results-vs/fig3.png
-[4]: /img/general-information/test-results/test-results-vs/fig4.png
-[5]: /img/general-information/test-results/test-results-vs/fig5.png
+
+
+
 [6]: /img/general-information/test-results/test-results-vs/fig6.png
diff --git a/docs/automated-tests/vs-plugin/web-test.md b/docs/automated-tests/vs-plugin/web-test.md
index 2bfd1862..c1212518 100644
--- a/docs/automated-tests/vs-plugin/web-test.md
+++ b/docs/automated-tests/vs-plugin/web-test.md
@@ -48,12 +48,9 @@ The <a href="/automated-tests/test-execution/quick-execution" target="_blank">__
 
 If you want to use the Visual Studio Test Explorer to execute the Test Studio tests, check <a href="/automated-tests/vs-plugin/vs-test-explorer" target="_blank">this topic</a>.
 
-[1]: /img/general-information/create-test-vsplugin/web-test/fig1.png
-[2]: /img/general-information/create-test-vsplugin/web-test/fig2.png
-[3]: /img/general-information/create-test-vsplugin/web-test/fig3.png
-[4]: /img/general-information/create-test-vsplugin/web-test/fig4.png
-[5]: /img/general-information/create-test-vsplugin/web-test/fig5.png
+
+
+
+
+
 [6]: /img/general-information/create-test-vsplugin/web-test/fig6.png
-[7]: /img/general-information/create-test-vsplugin/web-test/fig7.png
-[11]: /img/general-information/create-test-vsplugin/wpf-test/fig11.png
-[12]: /img/general-information/create-test-vsplugin/wpf-test/fig12.png
\ No newline at end of file
diff --git a/docs/automated-tests/vs-plugin/wpf-test.md b/docs/automated-tests/vs-plugin/wpf-test.md
index 6144291b..a3951c62 100644
--- a/docs/automated-tests/vs-plugin/wpf-test.md
+++ b/docs/automated-tests/vs-plugin/wpf-test.md
@@ -52,12 +52,9 @@ The <a href="/automated-tests/test-execution/quick-execution" target="_blank">__
 
 If you want to use the Visual Studio Test Explorer to execute the Test Studio tests, check <a href="/automated-tests/vs-plugin/vs-test-explorer" target="_blank">this topic</a>.
 
-[1]: /img/general-information/create-test-vsplugin/wpf-test/fig1.png
-[2]: /img/general-information/create-test-vsplugin/wpf-test/fig2.png
+
+
 [3]: /img/general-information/create-test-vsplugin/wpf-test/fig3.png
 [4]: /img/general-information/create-test-vsplugin/wpf-test/fig4.png
 [5]: /img/general-information/create-test-vsplugin/wpf-test/fig5.png
 [6]: /img/general-information/create-test-vsplugin/wpf-test/fig6.png
-[7]: /img/general-information/create-test-vsplugin/wpf-test/fig7.png
-[11]: /img/general-information/create-test-vsplugin/wpf-test/fig11.png
-[12]: /img/general-information/create-test-vsplugin/wpf-test/fig12.png
\ No newline at end of file
diff --git a/docs/bin/Intelligencia.UrlRewriter.dll b/docs/bin/Intelligencia.UrlRewriter.dll
old mode 100644
new mode 100755
diff --git a/docs/dbbrowser/dbbrowser.zip b/docs/dbbrowser/dbbrowser.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/DDTSkipIteration_C.zip b/docs/demoslibrary/DDTSkipIteration_C.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/DDTSkipIteration_VB.zip b/docs/demoslibrary/DDTSkipIteration_VB.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/Get-Set-Extr-Var-in-Code.zip b/docs/demoslibrary/Get-Set-Extr-Var-in-Code.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/RADGridViewAutomation_C.zip b/docs/demoslibrary/RADGridViewAutomation_C.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/SchedulingApiDocumentation.zip b/docs/demoslibrary/SchedulingApiDocumentation.zip
old mode 100644
new mode 100755
diff --git a/docs/demoslibrary/TestSettings1.zip b/docs/demoslibrary/TestSettings1.zip
old mode 100644
new mode 100755
diff --git a/docs/docfx/filterConfig.yml b/docs/docfx/filterConfig.yml
new file mode 100644
index 00000000..1a0b81b4
--- /dev/null
+++ b/docs/docfx/filterConfig.yml
@@ -0,0 +1,4 @@
+apiRules:
+- exclude:
+    type: Method
+    uidRegex: ^System\.Object\..*$
\ No newline at end of file
diff --git a/docs/docfx/metadata-config.json b/docs/docfx/metadata-config.json
new file mode 100644
index 00000000..1e136fd4
--- /dev/null
+++ b/docs/docfx/metadata-config.json
@@ -0,0 +1,37 @@
+{
+  "metadata": [{
+            "src": [
+                {
+                    "files": [
+			// "Src/ArtOfTest.InternetExplorer.dll",
+			"Src/ArtOfTest.ShDocVw.dll",
+			"Src/ArtOfTest.WebAii.Design.dll",
+			"Src/ArtOfTest.WebAii.dll",
+			"Src/ArtOfTest.WebAii.Messaging.dll",
+			"Src/Telerik.TestingFramework.Controls.KendoUI.Angular.dll",
+			"Src/Telerik.TestingFramework.Controls.KendoUI.dll",
+			"Src/Telerik.TestingFramework.Controls.TelerikUI.Blazor.dll",
+			"Src/Telerik.TestingFramework.Hosts.Common.dll",
+			"Src/Telerik.TestingFramework.Interop.dll",
+			"Src/Telerik.TestStudio.Analytics.dll",
+			"Src/Telerik.TestStudio.Aws.dll",
+			"Src/Telerik.TestStudio.BaseUI.dll",
+			"Src/Telerik.TestStudio.Core.dll",
+			"Src/Telerik.TestStudio.Interfaces.dll",
+			"Src/Telerik.TestStudio.NativeWrappers.dll",
+			"Src/Telerik.TestStudio.OCR.dll",
+			"Src/Telerik.TestStudio.Shared.dll",
+			"Src/Telerik.TestStudio.SourceControl.dll",
+			"Src/Telerik.TestStudio.Theme.dll",
+			"Src/Telerik.TestStudio.Translators.Common.dll",
+			"Src/Telerik.VisualStudio.Detection.dll",
+			"Src/Telerik.WebAii.Controls.Html.dll",
+			"Src/Telerik.WebAii.Controls.Xaml.dll",
+			"Src/Telerik.WebAii.Controls.Xaml.Wpf.dll"
+                    ]
+                }
+            ],
+            "dest": "metadata",
+            "filter": "filterConfig.yml"
+  }]
+}
\ No newline at end of file
diff --git a/docs/docs-builder.yml b/docs/docs-builder.yml
new file mode 100644
index 00000000..e4c88de4
--- /dev/null
+++ b/docs/docs-builder.yml
@@ -0,0 +1,2243 @@
+top-navigation-product: test-studio
+path-prefix: /teststudio/documentation
+product-id: 846
+product-name: Telerik Test Studio
+product-url: https://www.telerik.com/teststudio
+search-engine-id: 001595215763381649090:ymztq4og6vc
+cta-overview: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+cta-intro: "@ProductLink is a test automation platform for web, WPF, and responsive web applications, supporting UI, functional, load, and RESTful API testing. Sign up for a free 30-day trial!"
+default-title-prefix: Telerik Test Studio
+avatar-path: ./images/avatar-ninja.svg
+no-results-image-path: ./images/ninja-no-results.svg
+primary-color:
+    light: "#1D8800"
+    dark: "#68BF51"
+
+product-code: TESTSTUDIO
+product-trial-url: https://www.telerik.com/try/test-studio-ultimate
+contribute-url: https://github.com/telerik/teststudio-docs/edit/master/docs
+enable-tabbed-code-blocks: true
+pdf-cover-png-path: ./images/pdf-cover.png
+img-max-width: 100%
+table-layout: fixed
+disable-html-redirect: true
+
+
+meta:
+## Test Studio Documentation Main Nodes:
+    prerequisites:
+        title: "Installation and Setup"
+        position: 3
+    getting-started:
+        title: "Getting Started"
+        position: 4
+    automated-tests:
+        title: "Automated Tests with Test Studio"
+        position: 5 
+    features:
+        title: "Features"
+        position: 6
+    advanced-topics:
+        title: "Advanced Topics"
+        position: 7
+    knowledge-base:
+        title: "Knowledge Base"
+        position: 8
+    troubleshooting-guide:
+        title: "Troubleshooting Guide"
+        position: 9
+    testing-framework:
+        title: "Testing Framework"
+        position: 10
+    security:
+        title: "Security"
+        position: 11
+    copyright:
+        title: "Product Documentation Copyright Notice"
+        position: 14
+    faq:
+        title: "FAQ"
+        position: 15
+    license-server:
+        title: "License Server"
+        position: 16
+        hidden: true
+    api:
+        title: API Reference
+        position: 1000
+        pdfHidden: true
+
+# Installation and Setup
+    prerequisites/installation:
+        title: "Install Test Studio"
+        position: 1
+    prerequisites/license-activation:
+        title: "Activate Test Studio License"
+        position: 2
+    prerequisites/configure-your-browser:
+        title: "Configure Browsers for Test Automation"
+        position: 3
+
+# Getting Started
+    getting-started/first-project:
+        title: "Launch Test Studio"
+        position: 1
+    getting-started/first-test:
+        title: "Record Tests in Test Studio"
+        position: 2
+    getting-started/first-execution:
+        title: "Execute Your First Test"
+        position: 3
+    getting-started/analyze-the-results:
+        title: "Review the Results and Debug Test Failures"
+        position: 4
+    getting-started/next-steps:
+        title: "Next Steps"
+        position: 5
+    
+
+# Automated Tests with Test Studio
+    automated-tests/customize-project:
+        title: "Customize Your Project"
+        position: 1        
+# ... Customize Your Project
+    automated-tests/customize-project/built-in-help-tools:
+        title: "Help Tools in Test Studio"
+        position: 10
+
+    automated-tests/recording:
+        title: "Record Tests in Test Studio"
+        position: 2
+    automated-tests/test-execution:
+        title: "Execute Tests in Test Studio"
+        position: 3
+    automated-tests/test-results:
+        title: "Explore Test Results"
+        position: 4
+    automated-tests/troubleshooting:
+        title: "Troubleshoot a Failing Test"
+        position: 5
+    automated-tests/elements:
+        title: "Elements in Test Studio"
+        position: 6
+    automated-tests/data-drive-test:
+        title: "Data Driven Automated Tests"
+        position: 7
+    automated-tests/test-lists:
+        title: "Test Lists in Test Studio"
+        position: 8
+    automated-tests/test-list-results:
+        title: "Results from Test List Runs"
+        position: 9
+    automated-tests/scheduling:
+        title: "Schedule Tests in Test Studio"
+        position: 10        
+# ... Scheduling Test Runs
+    automated-tests/scheduling/multiple-machines-scheduling-setup:
+        title: "Remote Scheduled Execution (Multiple Machines Setup)"
+        position: 4
+    automated-tests/scheduling/advanced-topics:
+        title: "Scheduling Setup Advanced Topics"
+        position: 20
+
+    automated-tests/scheduling-results:
+        title: "Results from Scheduled Test Executions"
+        position: 11
+# ... Scheduling Test Runs
+    automated-tests/scheduling-results/dashboard:
+        title: "Executive Dashboard"
+        position: 5
+
+    automated-tests/headless:
+        title: "Headless Test Executions"
+        position: 12
+    automated-tests/responsive:
+        title: "Web Responsive Tests in Test Studio"
+        position: 13
+    automated-tests/desktop-testing:
+        title: "Desktop Tests in Test Studio"
+        position: 14
+    automated-tests/wpf:
+        title: "WPF Tests in Test Studio"
+        position: 15
+    automated-tests/load:
+        title: "Load Tests in Test Studio"
+        position: 16
+# ... Load Testing
+    automated-tests/load/designing-load-tests:
+        title: "Design Your Load Test"
+        position: 5
+    automated-tests/load/running-load-test:
+        title: "Execute Load Test"
+        position: 6
+    automated-tests/load/load-testing-results:
+        title: "Load Test Results"
+        position: 7
+    automated-tests/load/advanced-topics:
+        title: "Advanced Topics for Load Test"
+        position: 8
+
+    automated-tests/performance:
+        title: "Performance Tests in Test Studio"
+        position: 17
+    automated-tests/execute-apitest:
+        title: "Implement API test as Step"
+        position: 18
+    automated-tests/vs-plugin:
+        title: "Test Studio Plugin for Visual Studio"
+        position: 18
+    automated-tests/coded-tests:
+        title: "Coded Tests in Test Studio"
+        position: 19
+    automated-tests/source-control:
+        title: "Source Control Options in Test Studio"
+        position: 20
+# ... Source Control        
+    automated-tests/source-control/git:
+        title: "Git"
+        position: 2
+    automated-tests/source-control/tfs:
+        title: "TFS"
+        position: 3
+
+    automated-tests/continuous-integration:
+        title: "Test Studio Tests in CI Builds"
+        position: 21
+
+# Features
+    features/recorder:
+        title: "Recorder"
+        position: 1
+# ... Recorder section
+    features/recorder/highlighting-menu:
+        title: "Highlighting Menu Options"
+        position: 2
+    features/recorder/advanced-recording-tools:
+        title: "Advanced Recording Tools"
+        position: 3
+# ... Highlighting Menu Options section
+    features/recorder/highlighting-menu/quick-steps:
+        title: "Quick Steps"
+        position: 1
+# ... Advanced Recording Tools section
+    features/recorder/advanced-recording-tools/element-steps:
+        title: "Element Steps Tab"
+        position: 2
+# ... Element Steps Tab section
+    features/recorder/advanced-recording-tools/element-steps/actions:
+        title: "Advanced Actions"
+        position: 2
+    features/recorder/advanced-recording-tools/element-steps/verifications:
+        title: "Advanced Verifications"
+        position: 3
+
+    features/elements-explorer:
+        title: "Elements"
+        position: 2
+    features/test-lists:
+        title: "Test Lists"
+        position: 3
+    features/data-driven-testing:
+        title: "Data Driven Testing"
+        position: 4
+    features/custom-steps:
+        title: "Step Builder Pane"
+        position: 5
+# ... Step Builder section
+    features/custom-steps/all-tests-common:
+        title: "All Tests Common Steps"
+        position: 1
+    features/custom-steps/web-test-common:
+        title: "Web Test Specific Steps"
+        position: 2
+    features/custom-steps/wpf-common:
+        title: "WPF Test Specific Steps"
+        position: 3
+    features/custom-steps/desktop-common:
+        title: "Desktop Test Specific Steps"
+        position: 4
+
+    features/dialogs-and-popups:
+        title: "Handle Dialogs & Popups Steps"
+        position: 6
+    features/logical-steps:
+        title: "Logical/Conditional Steps"
+        position: 7
+    features/random-gens-steps:
+        title: "Random Generators Steps"
+        position: 8
+    features/test-maintenance:
+        title: "Test Maintenance"
+        position: 9
+    features/project-settings:
+        title: "Project Settings"
+        position: 10
+    features/project-explorer:
+        title: "Project Explorer"
+        position: 11
+    features/integration:
+        title: "Integration"
+        position: 12
+# ... Integration section
+    features/integration/bug-tracking:
+        title: "Bug Tracking"
+        position: 1
+    features/integration/quality-center:
+        title: "Quality Center"
+        position: 2
+
+    features/test-runners:
+        title: "Test Runners"
+        position: 13
+    features/testing-types:
+        title: "Testing Types"
+        position: 14
+# ... Testing Types section
+    features/testing-types/manual-testing:
+        title: "Manual Testing"
+        position: 1
+    features/testing-types/exploratory-testing:
+        title: "Exploratory Testing"
+        position: 2 
+
+    features/azure-dev-ops-mapper:
+        title: "Azure DevOps Mapper"
+        position: 15
+    
+# Advanced Topics
+    advanced-topics/build-server:
+        title: "Build Server"
+        position: 1
+    advanced-topics/coded-samples:
+        title: "Coded Samples"
+        position: 2
+  
+# ... Coded Samples section
+    advanced-topics/coded-samples/general:
+        title: "General"
+        position: 1
+    advanced-topics/coded-samples/html:
+        title: "HTML"
+        position: 2
+    advanced-topics/coded-samples/silverlight:
+        title: "Silverlight"
+        position: 3
+    advanced-topics/coded-samples/wpf:
+        title: "WPF"
+        position: 4
+
+# ... Silverlight section
+    advanced-topics/coded-samples/silverlight/combobox-automation:
+        title: "ComboBox Automation"
+        position: 10
+    advanced-topics/coded-samples/silverlight/radgridview-automation:
+        title: "RadGridView Automation"
+        position: 11
+
+# Knowledge Base section
+    knowledge-base/best-practices-kb:
+        title: "Best Practices"
+        position: 3
+    knowledge-base/browsers-kb:
+        title: "Browsers"
+        position: 4
+    knowledge-base/data-driven-testing-kb:
+        title: "Data Driven Testing"
+        position: 5
+    knowledge-base/dialogs-and-popups-kb:
+        title: "Dialogs and Popups"
+        position: 6
+    knowledge-base/load-testing-kb:
+        title: "Load Testing"
+        position: 7
+    knowledge-base/product-notices-kb:
+        title: "Product Notices"
+        position: 8
+    knowledge-base/project-configuration-kb:
+        title: "Project Configuration"
+        position: 9
+    knowledge-base/scheduling-kb:
+        title: "Scheduling"
+        position: 10
+    knowledge-base/test-automation-kb:
+        title: "Test Automation"
+        position: 11
+    knowledge-base/test-execution-kb:
+        title: "Test Execution"
+        position: 12
+    knowledge-base/test-recording-kb:
+        title: "Test Recording"
+        position: 13
+    knowledge-base/verification-kb:
+        title: "Verification"
+        position: 14
+    knowledge-base/visual-studio-kb:
+        title: "Visual Studio"
+        position: 15
+
+# Troubleshooting Guide section
+    troubleshooting-guide/browser-inconsistencies-tg:
+        title: "Browser Inconsistencies"
+        position: 1
+    troubleshooting-guide/cannot-launch-test-studio-tg:
+        title: "Cannot Launch Test Studio"
+        position: 2
+    troubleshooting-guide/installation-problems-tg:
+        title: "Installation Problems"
+        position: 3
+    troubleshooting-guide/load-testing-problems-tg:
+        title: "Load Testing Problems"
+        position: 4
+    troubleshooting-guide/network-related-problems-tg:
+        title: "Network Related Problems"
+        position: 5
+    troubleshooting-guide/recording-problems-tg:
+        title: "Recording Problems"
+        position: 6
+    troubleshooting-guide/scheduling-issues-tg:
+        title: "Scheduling Issues"
+        position: 7
+    troubleshooting-guide/source-control-problems-tg:
+        title: "Source Control Problems"
+        position: 8
+    troubleshooting-guide/test-execution-problems-tg:
+        title: "Test Execution Problems"
+        position: 9
+    troubleshooting-guide/visual-studio-tg:
+        title: "Visual Studio"
+        position: 10
+
+# ... Test Execution Problems section
+    troubleshooting-guide/test-execution-problems-tg/chrome-tg:
+        title: "Chrome"
+        position: 1
+    troubleshooting-guide/test-execution-problems-tg/firefox-tg:
+        title: "Firefox"
+        position: 2
+    troubleshooting-guide/test-execution-problems-tg/safari-tg:
+        title: "Safari"
+        position: 3
+    troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg:
+        title: "Silverlight WPF"
+        position: 4
+
+# Testing Framework section
+    testing-framework/write-tests-in-code:
+        title: "Write Tests in Code"
+        position: 20
+
+# ... Write Tests in Code section
+    testing-framework/write-tests-in-code/intermediate-topics-wtc:
+        title: "Intermediate Topics"
+        position: 1
+    testing-framework/write-tests-in-code/advanced-topics-wtc:
+        title: "Advanced Topics"
+        position: 2
+    testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc:
+        title: "Silverlight/WPF Automation"
+        position: 3
+
+# ... Intermediate Topics section
+    testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc:
+        title: "Element Identification"
+        position: 20
+    testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc:
+        title: "HTML Control Suite"
+        position: 21
+    testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc:
+        title: "Settings & Configuration"
+        position: 22
+
+# ... Advanced Topics section
+    testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc:
+        title: "Javascript"
+        position: 20
+    testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc:
+        title: "Test Regions"
+        position: 21
+    testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc:
+        title: "WPF/HTML Dialogs and Popups"
+        position: 22
+
+
+redirects: 
+-
+    from: "^/?$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/archived-docs/(.*)$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/automated-tests/troubleshooting/troubleshooting-tools-tg/(.*)$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/knowledge-base/silverlight-kb/(.*)$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/test-studio-mobile/(.*)$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/online-api-reference/(.*)$"
+    to: "/api"
+    type: Permanent
+-
+    from: "^/online-api-reference-1-1/(.*)$"
+    to: "/api"
+    type: Permanent
+-
+    from: "^/online-api-reference-2-0/(.*)$"
+    to: "/api"
+    type: Permanent
+-
+    from: "^/teststudioapi/(.*)$"
+    to: "/api"
+    type: Permanent
+-
+    from: "^/user-guide/overview\\.aspx$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/user-guide/overview$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/user-guide\\.aspx$"
+    to: "/welcome"
+    type: Permanent
+-
+    from: "^/test-studio-for-apis(.*)$"
+    to: "https://www.telerik.com/teststudio-apis/documentation"
+    type: Permanent
+-
+    from: "^/general-information/installation/vs2017-compatibility$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/general-information/installation/configure-windows-server$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/general-information/installation/manual-download$"
+    to: "/prerequisites/installation/manual-download"
+-
+    from: "^/general-information/installation/install-procedure$"
+    to: "/prerequisites/installation/install-procedure"
+-
+    from: "^/general-information/installation/add-services$"
+    to: "/prerequisites/installation/add-services"
+-
+    from: "^/general-information/installation/activating-your-license$"
+    to: "/prerequisites/license-activation/activating-your-license"
+-
+    from: "^/general-information/installation/manual-activation$"
+    to: "/prerequisites/license-activation/manual-activation"
+-
+    from: "^/general-information/installation/check-for-updates$"
+    to: "/prerequisites/installation/check-for-updates"
+-
+    from: "^/general-information/installation/re-activating-your-license$"
+    to: "/prerequisites/license-activation/re-activating-your-license"
+-
+    from: "^/getting-started/installation-and-activation$"
+    to: "/prerequisites/installation/install-procedure"
+-
+    from: "^/user-guide/data-driven-testing/attach-columns-to-input-values\\.aspx$"
+    to: "/features/data-driven-testing/attach-columns-input-values"
+-
+    from: "^/user-guide/data-driven-testing/attach-columns-to-input-values$"
+    to: "/features/data-driven-testing/attach-columns-input-values"
+-
+    from: "^/user-guide/data-driven-testing/attach-columns-to-verifications\\.aspx$"
+    to: "/features/data-driven-testing/attach-columns-input-values"
+-
+    from: "^/user-guide/data-driven-testing/attach-columns-to-verifications$"
+    to: "/features/data-driven-testing/attach-columns-input-values"
+-
+    from: "^/features/data-driven-testing/attach-columns-verifications$"
+    to: "/features/data-driven-testing/attach-columns-input-values"
+-
+    from: "^/features/data-driven-testing/multi-level-tests$"
+    to: "/automated-tests/data-drive-test/multi-level-tests"
+-
+    from: "^/features/data-driven-testing/test-list-results$"
+    to: "/automated-tests/data-drive-test/ddt-results#test-list-results"
+-
+    from: "^/features/data-driven-testing/quick-execute-resultS$"
+    to: "/automated-tests/data-drive-test/ddt-results#quick-execution-results"
+-
+    from: "^/user-guide/data-driven-testing/manage-data-source\\.aspx$"
+    to: "/features/data-driven-testing/manage-external-data-source"
+-
+    from: "^/user-guide/data-driven-testing/manage-data-source$"
+    to: "/features/data-driven-testing/manage-external-data-source"
+-
+    from: "^/user-guide/data-driven-testing/add-a-data-source\\.aspx$"
+    to: "/features/data-driven-testing/add-data-source"
+-
+    from: "^/user-guide/data-driven-testing/add-a-data-source$"
+    to: "/features/data-driven-testing/add-data-source"
+-
+    from: "^/user-guide/data-driven-testing/local-data-driven-test$"
+    to: "/automated-tests/data-drive-test/local-data-driven-test"
+- 
+    from: "^/user-guide/data-driven-testing/local-data-driven-test\\.aspx$"
+    to: "/automated-tests/data-drive-test/local-data-driven-test"
+- 
+    from: "^/features/data-driven-testing/local-data-driven-test$"
+    to: "/automated-tests/data-drive-test/local-data-driven-test"
+- 
+    from: "^/features/data-driven-testing/local-data-driven-tes$"
+    to: "/automated-tests/data-drive-test/local-data-driven-test"
+-
+    from: "^/features/custom-layout/custom-layout$"
+    to: "/automated-tests/customize-project/custom-layout"
+-
+    from: "^/general-information/start-a-project/welcome-screen$"
+    to: "/automated-tests/customize-project/welcome-screen"
+-
+    from: "^/user-guide/code-samples/html/dynamic-grid\\.aspx$"
+    to: "/advanced-topics/coded-samples/html/dynamic-grid"
+-
+    from: "^/testing-framework/api-reference/api-reference$"
+    to: "/testing-framework/api-reference"
+-
+    from: "^/testing-framework/api-reference$"
+    to: "/api"
+-
+    from: "^/user-guide/troubleshooting_guide/visual-studio/missing-assembly-references\\.aspx$"
+    to: "/troubleshooting-guide/visual-studio-tg/missing-assembly-references"
+-
+    from: "^/user-guide/troubleshooting_guide/visual-studio/missing-assembly-references$"
+    to: "/troubleshooting-guide/visual-studio-tg/missing-assembly-references"
+-
+    from: "^/user-guide/overview/test-studio-vs-framework\\.aspx$"
+    to: "/test-studio-editions"
+-
+    from: "^/user-guide/overview/test-studio-vs-framework$"
+    to: "/test-studio-editions"
+-
+    from: "^/general-information/test-studio-framework$"
+    to: "/test-studio-editions"
+-
+    from: "^/introduction/test-studio-framework$"
+    to: "/test-studio-editions"
+-
+    from: "^/introduction/test-studio-run-time$"
+    to: "/test-studio-editions"
+-
+    from: "^/user-guide/overview/for-developers\\.aspx$"
+    to: "/welcome"
+-
+    from: "^/user-guide/overview/for-developers$"
+    to: "/welcome"
+-
+    from: "^/general-information/for-developers$"
+    to: "/welcome"
+-
+    from: "^/introduction/for-developers$"
+    to: "/welcome"
+-
+    from: "^/user-guide/overview/webui_for_qa_testers\\.aspx$"
+    to: "/welcome"
+-
+    from: "^/user-guide/overview/webui_for_qa_testers$"
+    to: "/welcome"
+-
+    from: "^/general-information/for-qa-tester$"
+    to: "/welcome"
+-
+    from: "^/introduction/for-qa-tester$"
+    to: "/welcome"
+-
+    from: "^/user-guide/overview/for-team-leads\\.aspx$"
+    to: "/welcome"
+-
+    from: "^/user-guide/overview/for-team-leads$"
+    to: "/welcome"
+-
+    from: "^/general-information/for-team-leads$"
+    to: "/welcome"
+-
+    from: "^/introduction/for-team-leads$"
+    to: "/welcome"
+-
+    from: "^/features/testing-types/wpf-testing/wpf-test$"
+    to: "/automated-tests/wpf/wpf-test"
+-
+    from: "^/features/testing-types$"
+    to: "/features/testing-types/manual-testing/overview"
+-
+    from: "^/user-guide/verifications/image-verification\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification"
+-
+    from: "^/user-guide/verifications/image-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification"
+-
+    from: "^/features/verifications/image-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification"
+-
+    from: "^/features/recorder/verifications/image-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification"
+-
+    from: "^/user-guide/knowledge-base/test-execution/using-baseurl\\.aspx$"
+    to: "/knowledge-base/test-execution-kb/base-url"
+-
+    from: "^/user-guide/knowledge-base/test-execution/using-baseurl$"
+    to: "/knowledge-base/test-execution-kb/base-url"
+-
+    from: "^/user-guide/getting-started/using-telerik-testing-framework\\.aspx$"
+    to: "/testing-framework/getting-started"
+-
+    from: "^/user-guide/getting-started/using-telerik-testing-framework$"
+    to: "/testing-framework/getting-started"
+-
+    from: "^/user-guide/test-runners/artoftestrunner\\.aspx$"
+    to: "/features/test-runners/artoftest-runner"
+-
+    from: "^/user-guide/test-runners/artoftestrunner$"
+    to: "/features/test-runners/artoftest-runner"
+-
+    from: "^/user-guide/command-line-test-execution/artoftestrunner\\.aspx$"
+    to: "/features/test-runners/artoftest-runner"
+-
+    from: "^/user-guide/command-line-test-execution/artoftestrunner$"
+    to: "/features/test-runners/artoftest-runner"
+-
+    from: "^/user-guide/code-samples/general/extracted-variables-in-code$"
+    to: "/advanced-topics/coded-samples/general/extracted-variables-in-code"
+-
+    from: "^/user-guide/code-samples/general/extracted-variables-in-code\\.aspx$"
+    to: "/advanced-topics/coded-samples/general/extracted-variables-in-code"
+-
+    from: "^/user-guide/modifying-tests/convert-all-steps-to-code$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/user-guide/modifying-tests/convert-all-steps-to-codes\\.aspx$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/features/test-maintenance/convert-steps-code$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/user-guide/coded_steps/code-behind-file$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-code-behind-file"
+-
+    from: "^/user-guide/coded_steps/code-behind-file\\.aspx$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-code-behind-file"
+-
+    from: "^/advanced-topics/coded-steps/code-behind-file$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-code-behind-file"
+-
+    from: "^/user-guide/coded_steps/add-an-assembly-reference$"
+    to: "/automated-tests/coded-tests/add-assembly-reference"
+-
+    from: "^/user-guide/coded_steps/add-an-assembly-reference\\.aspx$"
+    to: "/automated-tests/coded-tests/add-assembly-reference"
+-
+    from: "^/advanced-topics/coded-steps/add-assembly-reference$"
+    to: "/automated-tests/coded-tests/add-assembly-reference"
+-
+    from: "^/user-guide/coded_steps$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/user-guide/coded_steps\\.aspx$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/advanced-topics/coded-steps/coded-step$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/user-guide/modifying-tests/change-test-step-properties$"
+    to: "/features/test-maintenance/change-test-step-properties"
+-
+    from: "^/user-guide/modifying-tests/change-test-step-properties\\.aspx$"
+    to: "/features/test-maintenance/change-test-step-properties"
+-
+    from: "^/features/test-maintenance/change-test-step-properties$"
+    to: "/features/test-maintenance/test-step-properties"
+-
+    from: "^/user-guide/modifying-tests/test-test-step-context-menu$"
+    to: "/features/test-maintenance/test-step-context-menu"
+-
+    from: "^/user-guide/modifying-tests/test-test-step-context-menu\\.aspx$"
+    to: "/features/test-maintenance/test-step-context-menu"
+-
+    from: "^/user-guide/modifying-tests/test-properties-vs-plugin$"
+    to: "/features/test-maintenance/test-properties-vs"
+-
+    from: "^/user-guide/modifying-tests/test-properties-vs-plugin\\.aspx$"
+    to: "/features/test-maintenance/test-properties-vs"
+-
+    from: "^/features/test-maintenance/test-properties-vs-plugin$"
+    to: "/features/test-maintenance/test-properties-vs"
+-
+    from: "^/user-guide/modifying-tests/test-properties$"
+    to: "/features/test-maintenance/test-properties-standalone"
+-
+    from: "^/user-guide/modifying-tests/test-properties\\.aspx$"
+    to: "/features/test-maintenance/test-properties-standalone"
+-
+    from: "^/features/test-maintenance/test-properties$"
+    to: "/features/test-maintenance/test-properties-standalone"
+-
+    from: "^/user-guide/modifying-tests/storyboard$"
+    to: "/features/test-maintenance/storyboard"
+-
+    from: "^/user-guide/modifying-tests/storyboard\\.aspx$"
+    to: "/features/test-maintenance/storyboard"
+-
+    from: "^/user-guide/modifying-tests/steps-pane-overview$"
+    to: "/features/test-maintenance/steps-pane"
+-
+    from: "^/user-guide/modifying-tests/steps-pane-overview\\.aspx$"
+    to: "/features/test-maintenance/steps-pane"
+-
+    from: "^/features/test-maintenance/steps-pane-overview$"
+    to: "/features/test-maintenance/steps-pane"
+-
+    from: "^/user-guide/modifying-tests/search_test_steps$"
+    to: "/features/test-maintenance/search-test-steps"
+-
+    from: "^/user-guide/modifying-tests/search_test_steps\\.aspx$"
+    to: "/features/test-maintenance/search-test-steps"
+-
+    from: "^/user-guide/modifying-tests/reorder-test-steps$"
+    to: "/features/test-maintenance/reorder-test-steps"
+-
+    from: "^/user-guide/modifying-tests/reorder-test-steps\\.aspx$"
+    to: "/features/test-maintenance/reorder-test-steps"
+-
+    from: "^/user-guide/modifying-tests/change-step-target-element$"
+    to: "/features/test-maintenance/change-step-target-element"
+-
+    from: "^/user-guide/modifying-tests/change-step-target-element\\.aspx$"
+    to: "/features/test-maintenance/change-step-target-element"
+-
+    from: "^/getting-started/create-test-standalone/wpf-test$"
+    to: "/automated-tests/wpf/wpf-test"
+-
+    from: "^/index$"
+    to: "/welcome"
+-
+    from: "^/features/scheduling-test-runs/change-service-account$"
+    to: "/features/scheduling-test-runs/advanced-topics/change-service-account"
+-
+    from: "^/features/scheduling-test-runs/tts-command-line-client$"
+    to: "/features/scheduling-test-runs/advanced-topics/tts-command-line-client"
+-
+    from: "^/features/scheduling-test-runs/using-service-api$"
+    to: "/features/scheduling-test-runs/advanced-topics/using-service-api"
+-
+    from: "^/user-guide/knowledge-base/project-configuration/register-certificate-for-https-connection$"
+    to: "/knowledge-base/project-configuration-kb/register-certificate"
+-
+    from: "^/user-guide/knowledge-base/project-configuration/register-certificate-for-https-connection\\.aspx$"
+    to: "/knowledge-base/project-configuration-kb/register-certificate"
+-
+    from: "^/getting-started/test-results/step-failure-details$"
+    to: "/general-information/test-results/step-failure-details"
+-
+    from: "^/user-guide/test-results/step-failure-details$"
+    to: "/general-information/test-results/step-failure-details"
+-
+    from: "^/user-guide/test-results/step-failure-details\\.aspx$"
+    to: "/general-information/test-results/step-failure-details"
+-
+    from: "^/user-guide/project-settings/translators$"
+    to: "/features/project-settings/translators"
+-
+    from: "^/user-guide/project-settings/translators\\.aspx$"
+    to: "/features/project-settings/translators"
+-
+    from: "^/user-guide/project-settings/script-options$"
+    to: "/features/project-settings/script-options"
+-
+    from: "^/user-guide/project-settings/script-options\\.aspx$"
+    to: "/features/project-settings/script-options"
+-
+    from: "^/features/test-maintenance/project-files-context-menu$"
+    to: "/features/project-explorer/overview"
+-
+    from: "^/features/project-settings/identification-logic$"
+    to: "/features/project-settings/find-logic"
+-
+    from: "^/user-guide/project-settings/browsers$"
+    to: "/features/project-settings/browsers"
+-
+    from: "^/user-guide/project-settings/browsers\\.aspx$"
+    to: "/features/project-settings/browsers"
+-
+    from: "^/user-guide/project-settings/recording-options$"
+    to: "/features/project-settings/recording-options"
+-
+    from: "^/user-guide/project-settings/recording-options\\.aspx$"
+    to: "/features/project-settings/recording-options"
+-
+    from: "^/user-guide/project-settings$"
+    to: "/features/project-settings/overview"
+-
+    from: "^/user-guide/project-settings\\.aspx$"
+    to: "/features/project-settings/overview"
+-
+    from: "^/features/project-settings/others$"
+    to: "/features/project-settings/general"
+-
+    from: "^/user-guide/overview/test-studio-vs-run-time\\.aspx$"
+    to: "/test-studio-editions"
+-
+    from: "^/user-guide/overview/test-studio-vs-run-time$"
+    to: "/test-studio-editions"
+-
+    from: "^/general-information/test-studio-run-time$"
+    to: "/test-studio-editions"
+-
+    from: "^/features/scheduling-test-runs/migrate-database$"
+    to: "/features/scheduling-test-runs/advanced-topics/migrate-database"
+-
+    from: "^/user-guide/scheduling-test-runs/telerik-teststudio-commandline-client\\.aspx$"
+    to: "/features/scheduling-test-runs/advanced-topics/tts-command-line-client"
+-
+    from: "^/user-guide/scheduling-test-runs/telerik-teststudio-commandline-client$"
+    to: "/features/scheduling-test-runs/advanced-topics/tts-command-line-client"
+-
+    from: "^/user-guide/installation/change_storage_service_account\\.aspx$"
+    to: "/features/scheduling-test-runs/advanced-topics/change-service-account"
+-
+    from: "^/user-guide/scheduling-test-runs/change-service-account\\.aspx$"
+    to: "/features/scheduling-test-runs/advanced-topics/change-service-account"
+-
+    from: "^/user-guide/scheduling-test-runs/change-service-account$"
+    to: "/features/scheduling-test-runs/advanced-topics/change-service-account"
+-
+    from: "^/user-guide/scheduling-test-runs/service-apis\\.aspx$"
+    to: "/features/scheduling-test-runs/advanced-topics/using-service-api"
+-
+    from: "^/user-guide/scheduling-test-runs/service-apis$"
+    to: "/features/scheduling-test-runs/advanced-topics/using-service-api"
+-
+    from: "^/user-guide/scheduling-test-runs/cancel-scheduled-job\\.aspx$"
+    to: "/features/scheduling-test-runs/stop-cancel-scheduled-job"
+-
+    from: "^/user-guide/scheduling-test-runs/cancel-scheduled-job$"
+    to: "/features/scheduling-test-runs/stop-cancel-scheduled-job"
+-
+    from: "^/user-guide/scheduling-test-runs/scheduling-results\\.aspx$"
+    to: "/features/scheduling-test-runs/scheduling-results"
+-
+    from: "^/user-guide/scheduling-test-runs/scheduling-results$"
+    to: "/features/scheduling-test-runs/scheduling-results"
+-
+    from: "^/user-guide/scheduling-test-runs/run-list-remotely\\.aspx$"
+    to: "/features/scheduling-test-runs/run-list-remotely"
+-
+    from: "^/user-guide/scheduling-test-runs/run-list-remotely$"
+    to: "/features/scheduling-test-runs/run-list-remotely"
+-
+    from: "^/user-guide/scheduling-test-runs/machine-status\\.aspx$"
+    to: "/features/scheduling-test-runs/connect-to-scheduling-server"
+-
+    from: "^/user-guide/scheduling-test-runs/machine-status$"
+    to: "/features/scheduling-test-runs/connect-to-scheduling-server"
+-
+    from: "^/user-guide/scheduling-test-runs/connect-a-project-to-a-scheduling-server\\.aspx$"
+    to: "/features/scheduling-test-runs/view-execution-status"
+-
+    from: "^/user-guide/scheduling-test-runs/connect-a-project-to-a-scheduling-server$"
+    to: "/features/scheduling-test-runs/view-execution-status"
+-
+    from: "^/features/scheduling-test-runs/create-execution-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-an-execution-server\\.aspx$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-an-execution-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server"
+-
+    from: "^/features/scheduling-test-runs/create-storage-server$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-storage-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-storage-server\\.aspx$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-storage-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-storage-server$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-storage-server"
+-
+    from: "^/features/scheduling-test-runs/create-scheduling-server$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-a-scheduling-server\\.aspx$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/user-guide/scheduling-test-runs/create-a-scheduling-server$"
+    to: "/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/user-guide/scheduling-test-runs\\.aspx$"
+    to: "/features/scheduling-test-runs/overview"
+-
+    from: "^/user-guide/scheduling-test-runs$"
+    to: "/features/scheduling-test-runs/overview"
+-
+    from: "^/features/scheduling-test-runs/local-run-all-in-one$"
+    to: "/features/scheduling-test-runs/local-scheduled-run"
+-
+    from: "^/features/scheduling-test-runs/remote-run-all-in-one$"
+    to: "/features/scheduling-test-runs/remote-scheduled-run"
+-
+    from: "^/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-edgechromium$"
+    to: "/general-information/configure-your-browser/edge-chromium"
+-
+    from: "^/features/testing-types/load-testing/adding-user-profiles$"
+    to: "/automated-tests/load/designing-load-tests/adding-user-profiles"
+-
+    from: "^/features/testing-types/load-testing/capturing-traffic$"
+    to: "/automated-tests/load/designing-load-tests/adding-user-profiles#capturing-traffic"
+-
+    from: "^/features/testing-types/load-testing/importing-traffic$"
+    to: "/automated-tests/load/designing-load-tests/adding-user-profiles#importing-traffic"
+-
+    from: "^/features/testing-types/load-testing/modifying-tests$"
+    to: "/automated-tests/load/designing-load-tests/modifying-tests"
+-
+    from: "^/features/testing-types/load-testing/designing-tests$"
+    to: "/features/testing-types/load-testing/designing-load-tests/getting-started"
+-
+    from: "^/features/testing-types/load-testing/think-times$"
+    to: "/automated-tests/load/designing-load-tests/modifying-tests#addremovechange-the-think-times"
+-
+    from: "^/features/testing-types/load-testing/test-settings$"
+    to: "/features/testing-types/load-testing/designing-load-tests/test-settings"
+-
+    from: "^/general-information/test-execution/vs-2012-test-explorer$"
+    to: "/general-information/test-execution/vs-test-explorer"
+-
+    from: "^/features/testing-types/load-testing/filter-user-profile$"
+    to: "/automated-tests/load/designing-load-tests/modifying-tests#filter-user-profile"
+-
+    from: "^/features/testing-types/load-testing/add-custom-cookies$"
+    to: "/automated-tests/load/designing-load-tests/modifying-tests#insert-a-custom-cookie-into-a-user-profile"
+-
+    from: "^/features/testing-types/load-testing/managing-vu$"
+    to: "/features/testing-types/load-testing/designing-load-tests/managing-vu"
+-
+    from: "^/user-guide/load-testing/load-managing-users\\.aspx$"
+    to: "/features/testing-types/load-testing/designing-load-tests/managing-vu"
+-
+    from: "^/features/testing-types/load-testing/dynamic-targets$"
+    to: "/automated-tests/load/designing-load-tests/dynamic-targets"
+-
+    from: "^/features/testing-types/load-testing/configure-remote-device$"
+    to: "/features/testing-types/load-testing/advanced-topics/configure-remote-device"
+-
+    from: "^/user-guide/load-testing/designing-load-tests/adding-user-profiles/capture-remote-traffic\\.aspx$"
+    to: "/features/testing-types/load-testing/advanced-topics/configure-remote-device"
+-
+    from: "^/features/testing-types/load-testing/monitor-perf-metrics$"
+    to: "/features/testing-types/load-testing/advanced-topics/monitor-perf-metrics"
+-
+    from: "^/features/testing-types/load-testing/data-driving$"
+    to: "/features/testing-types/load-testing/advanced-topics/data-driving"
+-
+    from: "^/features/testing-types/load-testing/manage-windows-auth$"
+    to: "/automated-tests/load/configuring-load-tests-quick-guide"
+-
+    from: "^/features/testing-types/load-testing/advanced-topics/manage-windows-auth$"
+    to: "/automated-tests/load/configuring-load-tests-quick-guide"
+-
+    from: "^/automated-tests/load/advanced-topics/manage-windows-auth$"
+    to: "/automated-tests/load/configuring-load-tests-quick-guide"
+-
+    from: "^/user-guide/load-testing/load-running-tests\\.aspx$"
+    to: "/features/testing-types/load-testing/running-load-test/running-tests"
+-
+    from: "^/features/testing-types/load-testing/running-tests$"
+    to: "/features/testing-types/load-testing/running-load-test/running-tests"
+-
+    from: "^/features/testing-types/load-testing/analyzing-results$"
+    to: "/features/testing-types/load-testing/load-testing-results/analyzing-results"
+-
+    from: "^/user-guide/load-testing/load-analyzing-results\\.aspx$"
+    to: "/features/testing-types/load-testing/load-testing-results/analyzing-results"
+-
+    from: "^/features/testing-types/load-testing/troubleshooting-results-errors$"
+    to: "/features/testing-types/load-testing/load-testing-results/troubleshooting-results-errors"
+-
+    from: "^/features/testing-types/load-testing/export-results$"
+    to: "/features/testing-types/load-testing/load-testing-results/export-results"
+-
+    from: "^/features/testing-types/load-testing/best-practices$"
+    to: "/features/testing-types/load-testing/running-load-test/best-practices"
+-
+    from: "^/features/testing-types/load-testing/remote-load-test-execution$"
+    to: "/features/testing-types/load-testing/running-load-test/remote-load-test-execution"
+-
+    from: "^/user-guide/configure-your-browser/chrome\\.aspx$"
+    to: "/general-information/configure-your-browser/chrome"
+-
+    from: "^/user-guide/configure-your-browser/chrome$"
+    to: "/general-information/configure-your-browser/chrome"
+-
+    from: "^/getting-started/configure-your-browser/chrome$"
+    to: "/general-information/configure-your-browser/chrome"
+-
+    from: "^/general-information/configure-your-browser/chrome$"
+    to: "/prerequisites/configure-your-browser/chrome"
+-
+    from: "^/getting-started/configure-your-browser/edgechromium$"
+    to: "/general-information/configure-your-browser/edge-chromium"
+-
+    from: "^/general-information/configure-your-browser/edge-chromium$"
+    to: "/prerequisites/configure-your-browser/edge-chromium"
+-
+    from: "^/getting-started/configure-your-browser/edge$"
+    to: "/general-information/configure-your-browser/edge"
+-
+    from: "^/general-information/configure-your-browser/edge$"
+    to: "/prerequisites/configure-your-browser/edge"
+-
+    from: "^/user-guide/configure-your-browser/firefox\\.aspx$"
+    to: "/general-information/configure-your-browser/firefox"
+-
+    from: "^/user-guide/configure-your-browser/firefox$"
+    to: "/general-information/configure-your-browser/firefox"
+-
+    from: "^/getting-started/configure-your-browser/firefox$"
+    to: "/general-information/configure-your-browser/firefox"
+-
+    from: "^/general-information/configure-your-browser/firefox$"
+    to: "/prerequisites/configure-your-browser/firefox"
+-
+    from: "^/user-guide/configure-your-browser/internet-explorer\\.aspx$"
+    to: "/system-requirements"
+-
+    from: "^/user-guide/configure-your-browser/internet-explorer$"
+    to: "/system-requirements"
+-
+    from: "^/getting-started/configure-your-browser/internet-explorer$"
+    to: "/system-requirements"
+-
+    from: "^/general-information/configure-your-browser/internet-explorer$"
+    to: "/system-requirements"
+-
+    from: "^/prerequisites/configure-your-browser/internet-explorer$"
+    to: "/prerequisites/configure-your-browser/edge-chromium"
+-
+    from: "^/user-guide/configure-your-browser/safari\\.aspx$"
+    to: "/general-information/configure-your-browser/safari"
+-
+    from: "^/getting-started/configure-your-browser/safari$"
+    to: "/general-information/configure-your-browser/safari"
+-
+    from: "^/general-information/configure-your-browser/safari$"
+    to: "/prerequisites/configure-your-browser/safari"
+-
+    from: "^/getting-started/create-test-standalone/load-test$"
+    to: "/general-information/create-test-standalone/add-test"
+-
+    from: "^/getting-started/create-test-standalone/manual-test$"
+    to: "/general-information/create-test-standalone/add-test"
+-
+    from: "^/getting-started/create-test-standalone/web-test$"
+    to: "/general-information/create-test-standalone/add-test"
+-
+    from: "^/getting-started/create-test-standalone/add-test$"
+    to: "/general-information/create-test-standalone/add-test"
+-
+    from: "^/getting-started/create-test-standalone/silverlight-out-of-browser$"
+    to: "/general-information/create-test-standalone/silverlight-out-of-browser"
+-
+    from: "^/getting-started/create-test-vsplugin/silverlight-out-of-browser$"
+    to: "/general-information/create-test-vsplugin/silverlight-out-of-browser"
+-
+    from: "^/user-guide/create-a-test-vs-plugin/web-test\\.aspx$"
+    to: "/general-information/create-test-vsplugin/web-test"
+-
+    from: "^/user-guide/create-a-test-vs-plugin/web-test$"
+    to: "/general-information/create-test-vsplugin/web-test"
+-
+    from: "^/getting-started/create-test-vsplugin/web-test$"
+    to: "/general-information/create-test-vsplugin/web-test"
+-
+    from: "^/user-guide/create-a-test-vs-plugin/wpf-test\\.aspx$"
+    to: "/general-information/create-test-vsplugin/wpf-test"
+-
+    from: "^/user-guide/create-a-test-vs-plugin/wpf-test$"
+    to: "/general-information/create-test-vsplugin/wpf-test"
+-
+    from: "^/getting-started/create-test-vsplugin/wpf-test$"
+    to: "/general-information/create-test-vsplugin/wpf-test"
+-
+    from: "^/user-guide/installation/activating-your-license\\.aspx$"
+    to: "/prerequisites/license-activation/activating-your-license"
+-
+    from: "^/user-guide/installation/activating-your-license$"
+    to: "/prerequisites/license-activation/activating-your-license"
+-
+    from: "^/getting-started/installation/activating-your-license$"
+    to: "/prerequisites/license-activation/activating-your-license"
+-
+    from: "^/getting-started/installation/add-services$"
+    to: "/prerequisites/installation/add-services"
+-
+    from: "^/user-guide/installation/check_for_updates\\.aspx$"
+    to: "/prerequisites/installation/check-for-updates"
+-
+    from: "^/user-guide/installation/check_for_updates$"
+    to: "/prerequisites/installation/check-for-updates"
+-
+    from: "^/getting-started/installation/check-for-updates$"
+    to: "/prerequisites/installation/check-for-updates"
+-
+    from: "^/user-guide/installation/configure-windows-server\\.aspx$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/user-guide/installation/configure-windows-server$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/getting-started/installation/configure-windows-server$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/user-guide/installation/install-procedure\\.aspx$"
+    to: "/prerequisites/installation/install-procedure"
+-
+    from: "^/user-guide/installation/install-procedure$"
+    to: "/prerequisites/installation/install-procedure"
+-
+    from: "^/getting-started/installation/install-procedure$"
+    to: "/prerequisites/installation/install-procedure"
+-
+    from: "^/user-guide/installation/manual-activation\\.aspx$"
+    to: "/prerequisites/license-activation/manual-activation"
+-
+    from: "^/user-guide/installation/manual-activation$"
+    to: "/prerequisites/license-activation/manual-activation"
+-
+    from: "^/getting-started/installation/manual-activation$"
+    to: "/prerequisites/license-activation/manual-activation"
+-
+    from: "^/user-guide/installation/manual_download\\.aspx$"
+    to: "/prerequisites/installation/manual-download"
+-
+    from: "^/user-guide/installation/manual_download$"
+    to: "/prerequisites/installation/manual-download"
+-
+    from: "^/getting-started/installation/manual-download$"
+    to: "/prerequisites/installation/manual-download"
+-
+    from: "^/getting-started/installation/personal-data$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/user-guide/installation/re-activate-your-license\\.aspx$"
+    to: "/prerequisites/license-activation/re-activating-your-license"
+-
+    from: "^/user-guide/installation/re-activate-your-license$"
+    to: "/prerequisites/license-activation/re-activating-your-license"
+-
+    from: "^/getting-started/installation/re-activating-your-license$"
+    to: "/prerequisites/license-activation/re-activating-your-license"
+-
+    from: "^/getting-started/installation/vs2017-compatability$"
+    to: "/prerequisites/installation/installation-consideration"
+-
+    from: "^/getting-started/start-a-project/in-product-tips-tricks$"
+    to: "/general-information/start-a-project/in-product-tips-tricks"
+-
+    from: "^/getting-started/start-a-project/welcome-screen$"
+    to: "/automated-tests/customize-project/welcome-screen"
+-
+    from: "^/user-guide/test-execution/quick-execution\\.aspx$"
+    to: "/general-information/test-execution/quick-execution"
+-
+    from: "^/user-guide/test-execution/quick-execution$"
+    to: "/general-information/test-execution/quick-execution"
+-
+    from: "^/getting-started/test-execution/quick-execution$"
+    to: "/general-information/test-execution/quick-execution"
+-
+    from: "^/getting-started/test-execution/test-list-execution$"
+    to: "/automated-tests/test-lists/test-list-execution"
+-
+    from: "^/user-guide/test-execution/test-list-settings\\.aspx$"
+    to: "/general-information/test-execution/test-list-settings"
+-
+    from: "^/user-guide/test-execution/test-list-settings$"
+    to: "/general-information/test-execution/test-list-settings"
+-
+    from: "^/getting-started/test-execution/test-list-settings$"
+    to: "/general-information/test-execution/test-list-settings"
+-
+    from: "^/user-guide/test-execution/standalone-test-lists\\.aspx$"
+    to: "/general-information/test-execution/test-lists-standalone"
+-
+    from: "^/user-guide/test-execution/standalone-test-lists$"
+    to: "/general-information/test-execution/test-lists-standalone"
+-
+    from: "^/getting-started/test-execution/test-lists-standalone$"
+    to: "/general-information/test-execution/test-lists-standalone"
+-
+    from: "^/user-guide/test-execution/standalone-test-list-type\\.aspx$"
+    to: "/general-information/test-execution/test-lists-type-standalone"
+-
+    from: "^/user-guide/test-execution/standalone-test-list-type$"
+    to: "/general-information/test-execution/test-lists-type-standalone"
+-
+    from: "^/getting-started/test-execution/test-lists-type-standalone$"
+    to: "/general-information/test-execution/test-lists-type-standalone"
+-
+    from: "^/user-guide/test-execution/visual-debugger\\.aspx$"
+    to: "/general-information/test-execution/visual-debugger"
+-
+    from: "^/user-guide/test-execution/visual-debugger$"
+    to: "/general-information/test-execution/visual-debugger"
+-
+    from: "^/getting-started/test-execution/visual-debugger$"
+    to: "/general-information/test-execution/visual-debugger"
+-
+    from: "^/getting-started/test-execution/visual-studio-2012-and-later-test-list$"
+    to: "/general-information/test-execution/visual-studio-2012-and-later-test-list"
+-
+    from: "^/user-guide/test-execution/visual-studio-2012-test-explorer\\.aspx$"
+    to: "/general-information/test-execution/vs-test-explorer"
+-
+    from: "^/user-guide/test-execution/visual-studio-2012-test-explorer$"
+    to: "/general-information/test-execution/vs-test-explorer"
+-
+    from: "^/getting-started/test-execution/vs-2012-test-explorer$"
+    to: "/general-information/test-execution/vs-test-explorer"
+-
+    from: "^/user-guide/recording-tests/frames\\.aspx$"
+    to: "/general-information/test-recording/frames"
+-
+    from: "^/user-guide/recording-tests/frames$"
+    to: "/general-information/test-recording/frames"
+-
+    from: "^/getting-started/test-recording/frames$"
+    to: "/general-information/test-recording/frames"
+-
+    from: "^/user-guide/recording-tests\\.aspx$"
+    to: "/general-information/test-recording/overview"
+-
+    from: "^/user-guide/recording-tests$"
+    to: "/general-information/test-recording/overview"
+-
+    from: "^/getting-started/test-recording/overview$"
+    to: "/general-information/test-recording/overview"
+-
+    from: "^/user-guide/recording-tests/recording-toolbar\\.aspx$"
+    to: "/general-information/test-recording/recording-toolbar"
+-
+    from: "^/user-guide/recording-tests/recording-toolbar$"
+    to: "/general-information/test-recording/recording-toolbar"
+-
+    from: "^/getting-started/test-recording/recording-toolbar$"
+    to: "/general-information/test-recording/recording-toolbar"
+-
+    from: "^/user-guide/recording-tests/step-suggestions\\.aspx$"
+    to: "/general-information/test-recording/step-suggestions"
+-
+    from: "^/user-guide/recording-tests/step-suggestions$"
+    to: "/general-information/test-recording/step-suggestions"
+-
+    from: "^/getting-started/test-recording/step-suggestions$"
+    to: "/general-information/test-recording/step-suggestions"
+-
+    from: "^/user-guide/recording-tests/translators\\.aspx$"
+    to: "/general-information/test-recording/translators"
+-
+    from: "^/user-guide/recording-tests/translators$"
+    to: "/general-information/test-recording/translators"
+-
+    from: "^/getting-started/test-recording/translators$"
+    to: "/general-information/test-recording/translators"
+-
+    from: "^/getting-started/test-results/quick-execute-test-step$"
+    to: "/general-information/test-results/quick-execute-test-step"
+-
+    from: "^/general-information/test-results/executive-dashboard$"
+    to: "/general-information/test-results/dashboard/overview"
+-
+    from: "^/general-information/test-recording/step-suggestions$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/steps-overview"
+-
+    from: "^/general-information/test-recording/recording-toolbar$"
+    to: "/features/recorder/compact-recording-toolbar"
+-
+    from: "^/features/recorder/dom-explorer$"
+    to: "/features/recorder/advanced-recording-tools/dom-explorer"
+-
+    from: "^/user-guide/elements-menu/dom-explorer\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/dom-explorer"
+-
+    from: "^/user-guide/elements-menu/dom-explorer$"
+    to: "/features/recorder/advanced-recording-tools/dom-explorer"
+-
+    from: "^/features/elements-menu/dom-explorer$"
+    to: "/features/recorder/advanced-recording-tools/dom-explorer"
+-
+    from: "^/general-information/test-recording/frames$"
+    to: "/features/elements-explorer/frames"
+-
+    from: "^/general-information/test-recording/translators$"
+    to: "/features/recorder/translators"
+-
+    from: "^/features/recorder/mouse-actions/drag-and-drop$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop"
+-
+    from: "^/features/recorder/advanced-recording-tools/element-steps/actions/scroll-actions$"
+    to: "/features/recorder/highlighting-menu/scroll-actions"
+-
+    from: "^/features/recorder/mouse-actions/relative-mouse-actions$"
+    to: "/features/recorder/highlighting-menu/mouse-actions"
+-
+    from: "^/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/actions/adv-mouse-actions"
+-
+    from: "^/features/recorder/verifications/advanced-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification"
+-
+    from: "^/user-guide/verifications/advanced-verification\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification"
+-
+    from: "^/user-guide/verifications/advanced-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification"
+-
+    from: "^/features/verifications/advanced-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification"
+-
+    from: "^/features/recorder/verifications/extraction$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/extraction"
+-
+    from: "^/user-guide/verifications/data-bind-an-extraction-step\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/extraction"
+-
+    from: "^/user-guide/verifications/data-bind-an-extraction-step$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/extraction"
+-
+    from: "^/features/verifications/Extraction$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/extraction"
+-
+    from: "^/features/verifications/Extraction.html$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/extraction"
+-
+    from: "^/features/recorder/advanced-recording-tools/element-steps/verifications/extraction$"
+    to: "/features/recorder/highlighting-menu/quick-steps/extraction"
+-
+    from: "^/features/recorder/verifications/overview$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications"
+-
+    from: "^/user-guide/verifications\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications"
+-
+    from: "^/user-guide/verifications$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications"
+-
+    from: "^/features/verifications/overview$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications"
+-
+    from: "^/features/recorder/verifications/quick-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification"
+-
+    from: "^/user-guide/verifications/quick-verification\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification"
+-
+    from: "^/user-guide/verifications/quick-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification"
+-
+    from: "^/features/verifications/quick-verification$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification"
+-
+    from: "^/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification$"
+    to: "/features/recorder/highlighting-menu/quick-steps/quick-verification"
+-
+    from: "^/features/recorder/verifications/text-from-image$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image"
+-
+    from: "^/features/recorder/verifications/wait$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/wait"
+-
+    from: "^/user-guide/verifications/wait\\.aspx$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/wait"
+-
+    from: "^/user-guide/verifications/wait$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/wait"
+-
+    from: "^/features/verifications/wait$"
+    to: "/features/recorder/advanced-recording-tools/element-steps/verifications/wait"
+-
+    from: "^/features/recorder/advanced-recording-tools/element-steps/verifications/wait$"
+    to: "/features/recorder/highlighting-menu/quick-steps/wait"
+-
+    from: "^/features/recorder/overview$"
+    to: "/automated-tests/recording/overview"
+-
+    from: "^/features/elements-menu/overview$"
+    to: "/automated-tests/recording/hover-over-highlighting"
+-
+    from: "^/general-information/test-execution/quick-execution$"
+    to: "/automated-tests/test-execution/quick-execution"
+-
+    from: "^/user-guide/test-results/test-as-step-results\\.aspx$"
+    to: "/automated-tests/test-results/quick-execute-test-step"
+-
+    from: "^/user-guide/test-results/test-as-step-results$"
+    to: "/automated-tests/test-results/quick-execute-test-step"
+-
+    from: "^/getting-started/test-results/quick-execution-test-step$"
+    to: "/automated-tests/test-results/quick-execute-test-step"
+-
+    from: "^/general-information/test-results/analyze-quick-run-results$"
+    to: "/automated-tests/test-results/analyze-quick-run-results"
+-
+    from: "^/features/recorder/test-recorder$"
+    to: "/automated-tests/recording/overview"
+-
+    from: "^/general-information/start-a-project/guided-tutorials$"
+    to: "/automated-tests/customize-project/built-in-help-tools/in-product-guides"
+-
+    from: "^/automated-tests/customize-project/built-in-help-tools/guided-tutorials$"
+    to: "/automated-tests/customize-project/built-in-help-tools/in-product-guides"
+-
+    from: "^/general-information/start-a-project/in-product-tips-tricks$"
+    to: "/automated-tests/customize-project/built-in-help-tools/in-product-tips-tricks"
+-
+    from: "^/general-information/start-a-project/in-product-guides$"
+    to: "/automated-tests/customize-project/built-in-help-tools/in-product-guides"
+-
+    from: "^/general-information/test-recording/overview$"
+    to: "/automated-tests/recording/overview"
+-
+    from: "^/features/elements-explorer/overview$"
+    to: "/automated-tests/elements/overview"
+-
+    from: "^/features/elements-explorer/elements-find-expression$"
+    to: "/automated-tests/elements/elements-find-expression"
+-
+    from: "^/features/elements-explorer/find-element$"
+    to: "/automated-tests/elements/find-element"
+-
+    from: "^/features/elements-explorer/find-element-by-image$"
+    to: "/automated-tests/elements/find-element-by-image"
+-
+    from: "^/features/elements-explorer/frames$"
+    to: "/automated-tests/elements/frames"
+-
+    from: "^/knowledge-base/project-configuration-kb/using-chained-find-expressions$"
+    to: "/automated-tests/elements/using-chained-find-expressions"
+-
+    from: "^/knowledge-base/project-configuration-kb/element-repository$"
+    to: "/automated-tests/elements/element-repository"
+-
+    from: "^/knowledge-base/project-configuration-kb/merge-page-nodes$"
+    to: "/automated-tests/elements/merge-page-nodes"
+-
+    from: "^/general-information/create-test-standalone/add-test$"
+    to: "/getting-started/first-test#add-a-test-to-the-project"
+-
+    from: "^/general-information/create-test-standalone/silverlight-out-of-browser$"
+    to: "/welcome"
+-
+    from: "^/general-information/create-test-vsplugin/web-test$"
+    to: "/automated-tests/vs-plugin/web-test"
+-
+    from: "^/general-information/create-test-vsplugin/wpf-test$"
+    to: "/automated-tests/vs-plugin/wpf-test"
+-
+    from: "^/general-information/create-test-vsplugin/silverlight-out-of-browser$"
+    to: "/welcome"
+-
+    from: "^/general-information/test-execution/test-list-execution$"
+    to: "/automated-tests/test-lists/test-list-execution"
+-
+    from: "^/general-information/test-execution/test-lists-standalone$"
+    to: "/automated-tests/test-lists/test-lists-standalone"
+-
+    from: "^/general-information/test-execution/test-lists-type-standalone$"
+    to: "/automated-tests/test-lists/test-lists-standalone"
+-
+    from: "^/general-information/test-execution/test-lists-in-vs-2017-2019$"
+    to: "/automated-tests/vs-plugin/test-lists-in-vs-2017-2019"
+-
+    from: "^/general-information/test-execution/test-list-settings$"
+    to: "/features/test-lists/test-list-settings"
+-
+    from: "^/general-information/test-execution/vs-test-explorer$"
+    to: "/automated-tests/vs-plugin/vs-test-explorer"
+-
+    from: "^/general-information/test-execution/visual-debugger$"
+    to: "/automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run"
+-
+    from: "^/general-information/test-execution/visual-studio-2012-and-later-test-list$"
+    to: "/welcome"
+-
+    from: "^/general-information/test-results/analyze-test-list-results$"
+    to: "/automated-tests/test-list-results/analyze-test-list-results"
+-
+    from: "^/general-information/test-results/export-test-results$"
+    to: "/automated-tests/test-list-results/export-test-results"
+-
+    from: "^/general-information/test-results/step-failure-details$"
+    to: "/automated-tests/test-results/step-failure-details"
+-
+    from: "^/general-information/test-results/quick-execute-test-step$"
+    to: "/automated-tests/test-results/quick-execute-test-step"
+-
+    from: "^/general-information/test-results/calendar$"
+    to: "/automated-tests/test-list-results/calendar"
+-
+    from: "^/general-information/test-results/reports$"
+    to: "/automated-tests/test-list-results/reports"
+-
+    from: "^/general-information/test-results/dashboard/overview$"
+    to: "/automated-tests/scheduling-results/dashboard/overview"
+-
+    from: "^/general-information/test-results/dashboard/installation-and-configuration$"
+    to: "/automated-tests/scheduling-results/dashboard/installation-and-configuration"
+-
+    from: "^/general-information/test-results/dashboard/results$"
+    to: "/automated-tests/scheduling-results/dashboard/results"
+-
+    from: "^/general-information/test-results/dashboard/reports$"
+    to: "/automated-tests/scheduling-results/dashboard/reports"
+-
+    from: "^/general-information/test-results/dashboard/about-page$"
+    to: "/automated-tests/scheduling-results/dashboard/about-page"
+-
+    from: "^/general-information/test-results/test-results-vs$"
+    to: "/automated-tests/vs-plugin/test-results-vs"
+-
+    from: "^/features/coded-steps/preview-code$"
+    to: "/automated-tests/vs-plugin/convert-steps-code"
+-
+    from: "^/features/coded-steps/convert-steps-code$"
+    to: "/automated-tests/vs-plugin/convert-steps-code#convert-all-steps-to-code"
+-
+    from: "^/features/testing-types/responsive-test$"
+    to: "/automated-tests/responsive/responsive-test"
+-
+    from: "^/features/testing-types/wpf-test$"
+    to: "/automated-tests/wpf/wpf-test"
+-
+    from: "^/user-guide/load-testing\\.aspx$"
+    to: "/automated-tests/load/overview"
+-
+    from: "^/user-guide/load-testing$"
+    to: "/automated-tests/load/overview"
+-
+    from: "^/user-guide/performance/compare-view\\.aspx$"
+    to: "/automated-tests/performance/compare-view"
+-
+    from: "^/user-guide/performance/compare-view$"
+    to: "/automated-tests/performance/compare-view"
+-
+    from: "^/features/testing-types/performance-testing/compare-view$"
+    to: "/automated-tests/performance/compare-view"
+-
+    from: "^/features/testing-types/performance-testing/details-view$"
+    to: "/automated-tests/performance/details-view"
+-
+    from: "^/user-guide/performance/details-view\\.aspx$"
+    to: "/automated-tests/performance/details-view"
+-
+    from: "^/user-guide/performance/details-view$"
+    to: "/automated-tests/performance/details-view"
+-
+    from: "^/features/testing-types/performance-testing/export-results$"
+    to: "/automated-tests/performance/export-results"
+-
+    from: "^/user-guide/performance/export_results\\.aspx$"
+    to: "/automated-tests/performance/export-results"
+-
+    from: "^/user-guide/performance/export_results$"
+    to: "/automated-tests/performance/export-results"
+-
+    from: "^/features/testing-types/performance-testing/gather-perfomance-data$"
+    to: "/automated-tests/performance/gather-perfomance-data"
+-
+    from: "^/user-guide/performance/gather-performance-data\\.aspx$"
+    to: "/automated-tests/performance/gather-perfomance-data"
+-
+    from: "^/user-guide/performance/gather-performance-data$"
+    to: "/automated-tests/performance/gather-perfomance-data"
+-
+    from: "^/features/testing-types/performance-testing/history-view$"
+    to: "/automated-tests/performance/history-view"
+-
+    from: "^/user-guide/performance/history-view\\.aspx$"
+    to: "/automated-tests/performance/history-view"
+-
+    from: "^/user-guide/performance/history-view$"
+    to: "/automated-tests/performance/history-view"
+-
+    from: "^/features/testing-types/performance-testing/open-port-on-server$"
+    to: "/automated-tests/performance/open-port-on-server"
+-
+    from: "^/user-guide/performance/open-port-on-server\\.aspx$"
+    to: "/automated-tests/performance/open-port-on-server"
+-
+    from: "^/user-guide/performance/open-port-on-server$"
+    to: "/automated-tests/performance/open-port-on-server"
+-
+    from: "^/features/testing-types/performance-testing/overview-button$"
+    to: "/automated-tests/performance/overview-button"
+-
+    from: "^/user-guide/performance/overview\\.aspx$"
+    to: "/automated-tests/performance/overview-button"
+-
+    from: "^/user-guide/performance/overview$"
+    to: "/automated-tests/performance/overview-button"
+-
+    from: "^/features/testing-types/performance-testing/overview$"
+    to: "/automated-tests/performance/overview"
+-
+    from: "^/user-guide/performance\\.aspx$"
+    to: "/automated-tests/performance/overview"
+-
+    from: "^/user-guide/performance$"
+    to: "/automated-tests/performance/overview"
+-
+    from: "^/features/testing-types/load-testing/overview$"
+    to: "/automated-tests/load/overview"
+-
+    from: "^/features/testing-types/load-testing/running-load-test/running-tests$"
+    to: "/automated-tests/load/running-load-test/running-tests"
+-
+    from: "^/features/testing-types/load-testing/running-load-test/remote-load-test-execution$"
+    to: "/automated-tests/load/running-load-test/remote-load-test-execution"
+-
+    from: "^/features/testing-types/load-testing/running-load-test/best-practices$"
+    to: "/automated-tests/load/running-load-test/best-practices"
+-
+    from: "^/features/testing-types/load-testing/load-testing-results/analyzing-results$"
+    to: "/automated-tests/load/load-testing-results/analyzing-results"
+-
+    from: "^/features/testing-types/load-testing/load-testing-results/export-results$"
+    to: "/automated-tests/load/load-testing-results/export-results"
+-
+    from: "^/features/testing-types/load-testing/load-testing-results/troubleshooting-results-errors$"
+    to: "/automated-tests/load/load-testing-results/troubleshooting-results-errors"
+-
+    from: "^/features/testing-types/load-testing/advanced-topics/monitor-perf-metrics$"
+    to: "/automated-tests/load/advanced-topics/monitor-perf-metrics"
+-
+    from: "^/features/testing-types/load-testing/advanced-topics/data-driving$"
+    to: "/automated-tests/load/advanced-topics/data-driving"
+-
+    from: "^/features/testing-types/load-testing/advanced-topics/configure-remote-device$"
+    to: "/automated-tests/load/advanced-topics/configure-remote-device"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/getting-started$"
+    to: "/automated-tests/load/designing-load-tests/getting-started"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/adding-user-profiles$"
+    to: "/automated-tests/load/designing-load-tests/adding-user-profiles"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/modifying-tests$"
+    to: "/automated-tests/load/designing-load-tests/modifying-tests"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/dynamic-targets$"
+    to: "/automated-tests/load/designing-load-tests/dynamic-targets"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/test-settings$"
+    to: "/automated-tests/load/designing-load-tests/test-settings"
+-
+    from: "^/features/testing-types/load-testing/designing-load-tests/managing-vu$"
+    to: "/automated-tests/load/designing-load-tests/managing-vu"
+-
+    from: "^/features/scheduling-test-runs/overview$"
+    to: "/automated-tests/scheduling/overview"
+-
+    from: "^/features/scheduling-test-runs/local-scheduled-run$"
+    to: "/automated-tests/scheduling/remote-scheduled-run"
+-
+    from: "^/features/scheduling-test-runs/remote-scheduled-run$"
+    to: "/automated-tests/scheduling/remote-scheduled-run"
+-
+    from: "^/features/scheduling-test-runs/multiple-machines-scheduling-setup/install-runtime$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime"
+-
+    from: "^/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-scheduling-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-storage-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-storage-server"
+-
+    from: "^/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-execution-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server"
+-
+    from: "^/features/scheduling-test-runs/connect-to-scheduling-server$"
+    to: "/automated-tests/scheduling/connect-to-scheduling-server"
+-
+    from: "^/features/scheduling-test-runs/view-execution-status$"
+    to: "/automated-tests/scheduling/view-execution-status"
+-
+    from: "^/features/scheduling-test-runs/run-list-remotely$"
+    to: "/automated-tests/scheduling/run-list-remotely"
+-
+    from: "^/features/scheduling-test-runs/schedule-execution$"
+    to: "/automated-tests/scheduling/schedule-execution"
+-
+    from: "^/features/scheduling-test-runs/scheduling-results$"
+    to: "/automated-tests/scheduling-results/scheduling-results"
+-
+    from: "^/features/scheduling-test-runs/stop-cancel-scheduled-job$"
+    to: "/automated-tests/scheduling/stop-cancel-scheduled-job"
+-
+    from: "^/features/scheduling-test-runs/advanced-topics/change-service-account$"
+    to: "/automated-tests/scheduling/advanced-topics/change-service-account"
+-
+    from: "^/features/scheduling-test-runs/advanced-topics/tts-command-line-client$"
+    to: "/automated-tests/scheduling/advanced-topics/tts-command-line-client"
+-
+    from: "^/features/scheduling-test-runs/advanced-topics/using-service-api$"
+    to: "/automated-tests/scheduling/advanced-topics/using-service-api"
+-
+    from: "^/features/scheduling-test-runs/advanced-topics/migrate-database$"
+    to: "/welcome"
+-
+    from: "^/features/coded-steps/standalone-code-file$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-standalone-code-file"
+-
+    from: "^/features/coded-steps/compile-project$"
+    to: "/automated-tests/coded-tests/compile-project"
+-
+    from: "^/features/source-control/sc-alternatives$"
+    to: "/automated-tests/source-control/sc-alternatives"
+-
+    from: "^/features/source-control/checkin-guidelines$"
+    to: "/automated-tests/source-control/checkin-guidelines"
+-
+    from: "^/features/source-control/git/overview-git$"
+    to: "/automated-tests/source-control/git/overview-git"
+-
+    from: "^/features/source-control/git/open-git-project$"
+    to: "/automated-tests/source-control/git/open-git-project"
+-
+    from: "^/features/source-control/git/connect-to-git$"
+    to: "/automated-tests/source-control/git/connect-to-git"
+-
+    from: "^/features/source-control/git/supported-git-commands$"
+    to: "/automated-tests/source-control/git/supported-git-commands"
+-
+    from: "^/features/source-control/git/branch-management$"
+    to: "/automated-tests/source-control/git/branch-management"
+-
+    from: "^/features/source-control/tfs/overview-tfs$"
+    to: "/automated-tests/source-control/tfs/overview-tfs"
+-
+    from: "^/features/source-control/tfs/connect-to-tfs$"
+    to: "/automated-tests/source-control/tfs/connect-to-tfs"
+-
+    from: "^/features/source-control/tfs/disconnect-from-tfs$"
+    to: "/automated-tests/source-control/tfs/disconnect-from-tfs"
+-
+    from: "^/features/source-control/tfs/open-tfs-project$"
+    to: "/automated-tests/source-control/tfs/open-tfs-project"
+-
+    from: "^/features/source-control/tfs/team-foundation-service$"
+    to: "/automated-tests/source-control/tfs/team-foundation-service"
+-
+    from: "^/features/source-control/tfs/project-item-options-tfs$"
+    to: "/automated-tests/source-control/tfs/project-item-options-tfs"
+-
+    from: "^/advanced-topics/build-server/continious-integration-overview$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/advanced-topics/build-server/vs-team-services-builds$"
+    to: "/advanced-topics/build-server/azure-devops"
+-
+    from: "^/advanced-topics/build-server/mtm$"
+    to: "/advanced-topics/build-server/azure-devops"
+-
+    from: "^/advanced-topics/build-server/build-servers-test-execution$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log$"
+    to: "/automated-tests/troubleshooting/failing-test#test-studio-application-log"
+-
+    from: "^/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure$"
+    to: "/automated-tests/troubleshooting/failing-test#step-failure-details"
+-
+    from: "^/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log$"
+    to: "/automated-tests/troubleshooting/failing-test#execution-log-on-failure"
+-
+    from: "^/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger$"
+    to: "/automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run"
+-
+    from: "^/features/dialogs-and-popups/dialog-handler-updater$"
+    to: "/prerequisites/configure-your-browser/browser-support-updater"
+-
+    from: "^/getting-started/test-results/analyze-test-results$"
+    to: "/automated-tests/test-list-results/analyze-test-list-results"
+-
+    from: "^/user-guide/data-driven-testing\\.aspx$"
+    to: "/automated-tests/data-drive-test/what-is-ddt"
+-
+    from: "^/user-guide/data-driven-testing$"
+    to: "/automated-tests/data-drive-test/what-is-ddt"
+-
+    from: "^/features/data-driven-testing/overview$"
+    to: "/automated-tests/data-drive-test/what-is-ddt"
+-
+    from: "^/user-guide/add-custom-step/test-as-step\\.aspx$"
+    to: "/features/custom-steps/test-as-step"
+-
+    from: "^/user-guide/add-custom-step/script-step\\.aspx$"
+    to: "/features/custom-steps/script-step"
+-
+    from: "^/user-guide/modifying-tests/properties-pane\\.aspx$"
+    to: "/features/test-maintenance/test-properties-standalone"
+-
+    from: "^/user-guide/knowledge-base/data-driven-testing/extracted-variables-in-code\\.aspx$"
+    to: "/advanced-topics/coded-samples/general/extracted-variables-in-code"
+-
+    from: "^/getting-started/test-execution/visual-studio-test-list$"
+    to: "/automated-tests/vs-plugin/test-lists-in-vs-2017-2019"
+-
+    from: "^/user-guide/code-samples/general/relative-dialog-path$"
+    to: "/advanced-topics/coded-samples/general/relative-dialog-path"
+-
+    from: "^/user-guide/code-samples/html/ajax-postback$"
+    to: "/testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support"
+-
+    from: "^/user-guide/code-samples/html/dynamic-grid$"
+    to: "/advanced-topics/coded-samples/html/dynamic-grid"
+-
+    from: "^/user-guide/knowledge-base/data-driven-testing/repeating-actions-for-multiple-users$"
+    to: "/knowledge-base/data-driven-testing-kb/multiple-users-with-login"
+-
+    from: "^/user-guide/knowledge-base/dialogs-popups/unexpected-dialog-action$"
+    to: "/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action"
+-
+    from: "^/user-guide/knowledge-base/project-configuration/element-repository$"
+    to: "/automated-tests/elements/element-repository"
+-
+    from: "^/user-guide/knowledge-base/scheduling/resolve-common-scheduling-issues$"
+    to: "/troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely"
+-
+    from: "^/user-guide/knowledge-base/silverlight/automate-silverlight-tests-in-tfs-builds$"
+    to: "/knowledge-base/silverlight-kb/automate-in-tfs-builds"
+-
+    from: "^/user-guide/knowledge-base/silverlight/out-of-browser-and-elevated-trust$"
+    to: "/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust"
+-
+    from: "^/user-guide/knowledge-base/test-automation/ample-timeouts$"
+    to: "/knowledge-base/test-automation-kb/ample-timetouts"
+-
+    from: "^/user-guide/knowledge-base/test-automation/dynamically-generated-id-attributes$"
+    to: "/knowledge-base/test-automation-kb/dynamic-ids"
+-
+    from: "^/user-guide/knowledge-base/test-automation/invoke-mouse-hover$"
+    to: "/knowledge-base/test-automation-kb/invoke-mouse-hover"
+-
+    from: "^/user-guide/knowledge-base/test-execution/execute-custom-scripts-before-after-test$"
+    to: "/advanced-topics/coded-samples/general/custom-scripts-before-after"
+-
+    from: "^/user-guide/knowledge-base/verification/verify-the-disabled-attribute-html$"
+    to: "/knowledge-base/verification-kb/disabled-attribute-html"
+-
+    from: "^/user-guide/knowledge-base/verification/verify-tool-tips$"
+    to: "/knowledge-base/verification-kb/verify-html-tool-tips"
+-
+    from: "^/user-guide/troubleshooting_guide/installation-problems/create-installer-log-file$"
+    to: "/troubleshooting-guide/installation-problems-tg/create-installer-log-file"
+-
+    from: "^/user-guide/troubleshooting_guide/recording-problems/hover-over-highlighting-is-misaligned$"
+    to: "/troubleshooting-guide/recording-problems-tg/highlighting-misaligned"
+-
+    from: "^/user-guide/troubleshooting_guide/recording-problems/namespace-reservation$"
+    to: "/welcome"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/cannot-execute-in-chrome$"
+    to: "/prerequisites/configure-your-browser/browser-configuration"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/invoke-blind-mouse-click$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/localhost-dynamic-ports$"
+    to: "/automated-tests/test-execution/quick-execution"
+-
+    from: "^/user-guide/troubleshooting_guide/visual-studio/enable-deployment$"
+    to: "/automated-tests/vs-plugin/test-explorer-settings"
+-
+    from: "^/troubleshooting-guide/visual-studio-tg/enable-deployment$"
+    to: "/automated-tests/vs-plugin/test-explorer-settings"
+-
+    from: "^/features/coded-steps/coded-step$"
+    to: "/automated-tests/coded-tests/coded-step"
+-
+    from: "^/features/coded-steps/code-behind-file$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-code-behind-file"
+-
+    from: "^/features/coded-steps/output-panel$"
+    to: "/automated-tests/coded-tests/output-panel"
+-
+    from: "^/features/coded-steps/add-assembly-reference$"
+    to: "/automated-tests/coded-tests/add-assembly-reference"
+-
+    from: "^/automated-tests/coded-tests/standalone-code-file$"
+    to: "/automated-tests/coded-tests/coded-step#which-is-the-standalone-code-file"
+-
+    from: "^/user-guide/dialogs-and-popups/dialogs$"
+    to: "/features/dialogs-and-popups/dialogs"
+-
+    from: "^/user-guide/dialogs-and-popups/dialogs\\.aspx$"
+    to: "/features/dialogs-and-popups/dialogs"
+-
+    from: "^/user-guide/dialogs-and-popups/html-popups\\.aspx$"
+    to: "/features/dialogs-and-popups/html-popups"
+-
+    from: "^/user-guide/dialogs-and-popups/html-popups$"
+    to: "/features/dialogs-and-popups/html-popups"
+-
+    from: "^/user-guide/dialogs-and-popups/modal-popups\\.aspx$"
+    to: "/features/dialogs-and-popups/html-popups#modal-popups"
+-
+    from: "^/user-guide/dialogs-and-popups/modal-popups$"
+    to: "/features/dialogs-and-popups/html-popups#modal-popups"
+-
+    from: "^/personal-data$"
+    to: "https://www.progress.com/legal/privacy-policy"
+-
+    from: "^/knowledge-base/visual-studio-kb/test-explorer-settings$"
+    to: "/automated-tests/vs-plugin/test-explorer-settings"
+-
+    from: "^/automated-tests/vs-plugin/preview-code$"
+    to: "/automated-tests/vs-plugin/convert-steps-code"
+-
+    from: "^/user-guide/test-results/test-results-vs-plugin\\.aspx$"
+    to: "/automated-tests/vs-plugin/test-results-vs"
+-
+    from: "^/user-guide/test-results/test-results-vs-plugin$"
+    to: "/automated-tests/vs-plugin/test-results-vs"
+-
+    from: "^/getting-started/test-results/test-results-vs$"
+    to: "/automated-tests/vs-plugin/test-results-vs"
+-
+    from: "^/features/dialogs-and-popups/modal-popups$"
+    to: "/features/dialogs-and-popups/html-popups#modal-popups"
+-
+    from: "^/prerequisites/configure-your-browser/edge$"
+    to: "/prerequisites/configure-your-browser/edge-chromium"
+-
+    from: "^/knowledge-base/test-execution-kb/run-mobile-test-in-web-test$"
+    to: "/welcome"
+-
+    from: "^/user-guide/knowledge-base/best-practices/generate-application-log\\.aspx$"
+    to: "/knowledge-base/best-practices-kb/generate-application-log"
+-
+    from: "^/user-guide/knowledge-base/best-practices/generate-application-log$"
+    to: "/knowledge-base/best-practices-kb/generate-application-log"
+-
+    from: "^/user-guide/add-custom-step/comment\\.aspx$"
+    to: "/features/custom-steps/all-tests-common/comment"
+-
+    from: "^/user-guide/add-custom-step/comment$"
+    to: "/features/custom-steps/all-tests-common/comment"
+-
+    from: "^/features/custom-steps/comment$"
+    to: "/features/custom-steps/all-tests-common/comment"
+-
+    from: "^/user-guide/add-custom-step/custom-annotation\\.aspx$"
+    to: "/features/custom-steps/all-tests-common/custom-annotation"
+-
+    from: "^/user-guide/add-custom-step/custom-annotation$"
+    to: "/features/custom-steps/all-tests-common/custom-annotation"
+-
+    from: "^/features/custom-steps/custom-annotation$"
+    to: "/features/custom-steps/all-tests-common/custom-annotation"
+-
+    from: "^/features/custom-steps/execution-delay$"
+    to: "/features/custom-steps/all-tests-common/execution-delay"
+-
+    from: "^/features/custom-steps/inspection-point$"
+    to: "/features/custom-steps/all-tests-common/inspection-point"
+-
+    from: "^/features/custom-steps/manual-step$"
+    to: "/features/custom-steps/all-tests-common/manual-step"
+-
+    from: "^/features/custom-steps/script-step$"
+    to: "/features/custom-steps/all-tests-common/script-step"
+-
+    from: "^/features/custom-steps/test-as-step$"
+    to: "/features/custom-steps/all-tests-common/test-as-step"
+-
+    from: "^/features/custom-steps/navigate-to$"
+    to: "/features/custom-steps/web-test-common/navigate-to"
+-
+    from: "^/features/custom-steps/open-pdf$"
+    to: "/features/custom-steps/web-test-common/open-pdf"
+-
+    from: "^/features/custom-steps/maximize-browser$"
+    to: "/features/custom-steps/web-test-common/maximize-browser"
+-
+    from: "^/features/custom-steps/clear-browser-cache$"
+    to: "/features/custom-steps/web-test-common/clear-browser-cache"
+-
+    from: "^/features/custom-steps/browser-refresh$"
+    to: "/features/custom-steps/web-test-common/browser-refresh"
+-
+    from: "^/features/custom-steps/capture-browser$"
+    to: "/features/custom-steps/web-test-common/capture-browser"
+-
+    from: "^/features/custom-steps/wait-for-url$"
+    to: "/features/custom-steps/web-test-common/wait-for-url"
+-
+    from: "^/features/custom-steps/check-js-errors$"
+    to: "/features/custom-steps/web-test-common/check-js-errors"
+-
+    from: "^/user-guide/add-custom-step/change-window-state\\.aspx$"
+    to: "/features/custom-steps/wpf-common/change-window-state"
+-
+    from: "^/user-guide/add-custom-step/change-window-state$"
+    to: "/features/custom-steps/wpf-common/change-window-state"
+-
+    from: "^/features/custom-steps/change-window-state$"
+    to: "/features/custom-steps/wpf-common/change-window-state"
+-
+    from: "^/features/execute-apitest/add-api-test-as-step$"
+    to: "/automated-tests/execute-apitest/add-api-test-as-step"
+-
+    from: "^/features/execute-apitest/edit-integrated-api-project$"
+    to: "/automated-tests/execute-apitest/edit-integrated-api-project"
+-
+    from: "^/features/execute-apitest/passing-variables$"
+    to: "/automated-tests/execute-apitest/passing-variables"
+-
+    from: "^/knowledge-base/scheduling-kb/upload-latest-files$"
+    to: "/automated-tests/scheduling/upload-latest-files"
+-
+    from: "^/user-guide/scheduling-test-runs/schedule-test-execution\\.aspx$"
+    to: "/automated-tests/scheduling/schedule-execution"
+-
+    from: "^/user-guide/scheduling-test-runs/schedule-test-execution$"
+    to: "/automated-tests/scheduling/schedule-execution"
+-
+    from: "^/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files$"
+    to: "/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers"
+-
+    from: "^/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value$"
+    to: "/automated-tests/recording/overview#how-to-add-steps-in-the-test"
+-
+    from: "^/troubleshooting-guide/browser-inconsistencies-tg/html-button$"
+    to: "/features/recorder/highlighting-menu/quick-steps/quick-verification"
+-
+    from: "^/user-guide/troubleshooting_guide/recording-problems/hover-over-highlighting-is-misaligned\\.aspx$"
+    to: "/troubleshooting-guide/recording-problems-tg/highlighting-misaligned"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/if-else-logical-step-fails\\.aspx$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/if-else-logical-step-fails$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/missing-page-elements\\.aspx$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/missing-page-elements"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/pages-not-defined\\.aspx$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/pages-not-defined"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/unable-to-locate-element\\.aspx$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element"
+-
+    from: "^/user-guide/troubleshooting_guide/test-execution-problems/unable-to-locate-element$"
+    to: "/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element"
+-
+    from: "^/advanced-topics/build-server/tfs-builds$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome$"
+    to: "/prerequisites/configure-your-browser/chrome"
+-
+    from: "^/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff$"
+    to: "/prerequisites/configure-your-browser/firefox"
+-
+    from: "^/knowledge-base/scheduling-kb/maintain-scheduling-services$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/knowledge-base/test-execution-kb/locked-machine$"
+    to: "/knowledge-base/scheduling-kb/locked-machine"
+-
+    from: "^/knowledge-base/scheduling-kb/keep-active-session$"
+    to: "/knowledge-base/test-execution-kb/keep-active-session"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/continuous-integration-environments\\.aspx$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/continuous-integration-environments$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/prerequisites/configure-your-browser/safari$"
+    to: "/prerequisites/configure-your-browser/browser-configuration"
+-
+    from: "^/advanced-topics/build-server/tfs-2017-builds$"
+    to: "/advanced-topics/build-server/azure-devops"
+-
+    from: "^/user-guide/command-line-test-execution\\.aspx$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/user-guide/command-line-test-execution$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/team-foundation-server-builds$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/team-foundation-server-builds\\.aspx$"
+    to: "/automated-tests/continuous-integration/continious-integration-overview"
+-
+    from: "^/automated-tests/scheduling/multiple-machines-scheduling-setup/create-storage-server$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/automated-tests/scheduling/advanced-topics/using-service-api$"
+    to: "/automated-tests/scheduling/overview"
+-
+    from: "^/automated-tests/scheduling/advanced-topics/change-service-account$"
+    to: "/automated-tests/scheduling/overview"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/cruisecontrol-net\\.aspx$"
+    to: "/advanced-topics/build-server/cruise-control.net-builds"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/cruisecontrol-net$"
+    to: "/advanced-topics/build-server/cruise-control.net-builds"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/teamcity\\.aspx$"
+    to: "/advanced-topics/build-server/team-city-builds"
+-
+    from: "^/user-guide/command-line-test-execution/continuous-integration/teamcity$"
+    to: "/advanced-topics/build-server/team-city-builds"
+-
+    from: "^/knowledge-base/scheduling-kb/non-domain-environment$"
+    to: "/automated-tests/scheduling/overview"
+-
+    from: "^/knowledge-base/silverlight-kb/automate-in-tfs-builds$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/verification-kb/verify-silverlight-combobox-items$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/verification-kb/verify-silverlight-tool-tips$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/silverlight-kb/testing-framework-with-silverlight-oob-and-elevated-trust$"
+    to: "/welcome"
+-
+    from: "^/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest$"
+    to: "/automated-tests/data-drive-test/what-is-ddt"
+-
+    from: "^/knowledge-base/project-configuration-kb/anonymous-access-error-when-connecting-to-team-foundation-service$"
+    to: "/automated-tests/source-control/checkin-guidelines"
+-
+    from: "^/knowledge-base/visual-studio-kb/convert-trx-to-html$"
+    to: "/welcome"
+-
+    from: "^/troubleshooting-guide/scheduling-issues-tg/no-change-button$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"
+-
+    from: "^/troubleshooting-guide/scheduling-issues-tg/scheduling-service-shuts-down$"
+    to: "/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"
diff --git a/docs/downloads/DbMigratorExe.zip b/docs/downloads/DbMigratorExe.zip
old mode 100644
new mode 100755
diff --git a/docs/downloads/Jenkins_Plugin_Mobilestudio.zip b/docs/downloads/Jenkins_Plugin_Mobilestudio.zip
old mode 100644
new mode 100755
diff --git a/docs/downloads/Jenkins_Plugin_Teststudio.zip b/docs/downloads/Jenkins_Plugin_Teststudio.zip
old mode 100644
new mode 100755
diff --git a/docs/downloads/OCR_tesseract.4.1.0x64.zip b/docs/downloads/OCR_tesseract.4.1.0x64.zip
old mode 100644
new mode 100755
diff --git a/docs/downloads/Progress_TestStudio_Extension.zip b/docs/downloads/Progress_TestStudio_Extension.zip
old mode 100644
new mode 100755
diff --git a/docs/downloads/TelerikTestRunner.zip b/docs/downloads/TelerikTestRunner.zip
old mode 100644
new mode 100755
diff --git a/docs/faq.md b/docs/faq.md
index 9eeef11c..ce312876 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -6,451 +6,274 @@ position: 101
 previous_url: /user-guide/faq.aspx, /user-guide/faq
 ---
 
-<style>
-p.trigger{
-    margin-bottom:7px;
-    margin-top:-5px;
-}
-
-.toggle_container{
-    margin-bottom:10px;
-}
-
-.toggle_container p{
-    margin:0px;
-}
-
-.toggle_container{
-    
-    clear: both;
-    font-size:100%;
-}
-</style>
-
 # Test Studio Users Frequently Asked Questions 
 
 ## Contacting Technical Support Officer
 
-<p class="trigger"><a href="#">Overview of the ticketing system</a></p>
-<div class="toggle_container">
-<div class="block">
-<p>Once you <a href="http://www.telerik.com/account/support-tickets.aspx" target="_blank">submit a support ticket</a>, the system automatically notifies the Telerik support officers and creates a thread in your support history. Our engineers will then review your ticket and respond within the guaranteed response time. The reply will be appended to your support thread and, for your extra convenience, you will also receive an e-mail with all the information.<br><br>
-
-You do not need to follow up with us, if the provided answer solves your issue. However, we recommend that you do so, as this will help the support officers close the issue faster.<br><br>
-
-In case you need to continue the thread and provide some additional information, you should log into <a href="http://www.telerik.com/account.aspx" target="_blank">Your Account</a>, go to the respective thread and post your reply via the web interface.<br><br>
-
-Note that titles of unread support tickets will show up in bold text, while those of already reviewed replies will not.<br><br>
-
-In order for us to make the ticketing system more effective, we need your cooperation. We kindly ask that you create a new thread for each incident/inquiry of a different nature and for each different product line. In case you open a ticket for one product, but your questions are for another one, we will move the thread under the relevant category, but you may not receive a timely response.</p>
-</div>
-</div>
-
-<p class="trigger"><a href="#">Using the available support resources</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Your Account offers several exclusive resources to evaluators and customers of Telerik products:
-		<ul>
-		<li><a href="http://www.telerik.com/support/demos" target="_blank">Online demos</a></li>
-		<li><a href="http://www.telerik.com/support" target="_blank">Support and Learning</a></li>
-		<li><a href="http://www.telerik.com/forums" target="_blank">Forums</a></li>
-		<li>Support ticket system</li>
-		<li>Bug reporting tool</li>
-		<li>Feature request tool</li>
-		<li>Feedback form</li><br>
-As with any other system, there are some guidelines to follow in order for you to get a quality support experience:<br><br>
-		<li>Review the publicly available resources prior to submitting a support ticket. We have various resources (online demos, documentation, knowledge base, code library, videos, forums, etc.) with thousands of examples/threads and there is a good chance that the answer to your inquiry/issue is already there.</li>
-		<li>Start a support thread for each different issue that you face. This will make things simpler and also, it will be easier for you to track the progress of all your incidents.</li>
-		<li>Do not enter support incidents in "Feature requests".</li>
-		<li>Before submitting a "Bug report" entry, please make sure that you have provided us with enough information, so that we can reproduce the problem. The more details you send, the easier it will be for us to isolate the problem and resolve it.</li>
-		<li>Please do not use “General feedback” to post your technical problems. The purpose of this section is to allow you to send us feedback on our site, our products, and our services.</li><br><br>
-		Note: After we reproduce a bug or add a feature request to our ToDo list, we will add Telerik points to your account and send out a notification.
-		</ul>
-		</p>		
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Creating a new bug report - guidelines</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Sometimes it is difficult to make a distinction between a support incident and a bug report. However, if you feel that there is a generic problem with any of our products that can be reproduced, you should definitely consider opening a "Bug report".<br><br>
-
-		While submitting a "Bug report" entry, please make sure you give us as many details as possible. As a start, please provide the steps required to reproduce the error, as well as some information about your environment (OS, .NET framework, browser, and so on).<br><br>
-
-		Additionally, if you feel that screenshots or some other visual material will help us understand the issue better, please do not hesitate to attach those to the thread. A runnable project that exhibits the problem would be appreciated as well.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Starting a new support ticket - guidelines</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Telerik strives to constantly improve its services. In order to help us provide you with a quick and accurate response, please follow the guidelines below when submitting a support ticket:
-		<ul>
-		<li>Describe your question in detail. Although we are familiar with most of the problems people are having, there is always a chance that you are the first one to report an issue. Sending us as much information as possible will help us identify the source and provide you with a fix or workaround.</li>
-		<li>Provide step by step instructions on how to reproduce the error.</li>
-		<li>Send us the stack trace of the exception you are receiving (if applicable)</li>
-		<li>Attach the source code that generates the exception you are receiving.</li>
-		<li>Attach a screenshot of the observed behavior and a screenshot of the expected behavior (if applicable).</li>
-		<li>Attach a simple runnable project (zipped, no 3rd party controls), which isolates and demonstrates your problem.</li>
-		<br>
-		The zipped project should contain:<br><br>
-		<li>The /bin folder with the respective version of the Telerik assembly (or specify that version exactly without sending the dll itself).</li>
-		<li>The ascx/aspx page, together with the codebehind, which reproduces the error.</li>
-		<li>A backup of your database (if needed).</li>
-		<li>Other necessary resources (classes, css files, etc., if applicable) or specific instructions for your particular case.</li>
-		<li>Please, exclude/remove all 3rd party controls.</li>
-		<li>The project should run in a test environment without major modifications.</li>
-		</ul></p>
-    </div>
-</div>
+### Overview of the ticketing system
+
+Once you <a href="http://www.telerik.com/account/support-tickets.aspx" target="_blank">submit a support ticket</a>, the system automatically notifies the Telerik support officers and creates a thread in your support history. Our engineers will then review your ticket and respond within the guaranteed response time. The reply will be appended to your support thread and, for your extra convenience, you will also receive an e-mail with all the information.
+
+You do not need to follow up with us, if the provided answer solves your issue. However, we recommend that you do so, as this will help the support officers close the issue faster.
+
+In case you need to continue the thread and provide some additional information, you should log into <a href="http://www.telerik.com/account.aspx" target="_blank">Your Account</a>, go to the respective thread and post your reply via the web interface.
+
+Note that titles of unread support tickets will show up in bold text, while those of already reviewed replies will not.
+
+In order for us to make the ticketing system more effective, we need your cooperation. We kindly ask that you create a new thread for each incident/inquiry of a different nature and for each different product line. In case you open a ticket for one product, but your questions are for another one, we will move the thread under the relevant category, but you may not receive a timely response.
+
+
+### Using the available support resources
+
+Your Account offers several exclusive resources to evaluators and customers of Telerik products:
+		
+- <a href="http://www.telerik.com/support/demos" target="_blank">Online demos</a>
+- <a href="http://www.telerik.com/support" target="_blank">Support and Learning</a>
+- <a href="http://www.telerik.com/forums" target="_blank">Forums</a>
+- Support ticket system
+- Bug reporting tool
+- Feature request tool
+- Feedback form
+
+As with any other system, there are some guidelines to follow in order for you to get a quality support experience:
+
+- Review the publicly available resources prior to submitting a support ticket. We have various resources (online demos, documentation, knowledge base, code library, videos, forums, etc.) with thousands of examples/threads and there is a good chance that the answer to your inquiry/issue is already there.
+- Start a support thread for each different issue that you face. This will make things simpler and also, it will be easier for you to track the progress of all your incidents.
+- Do not enter support incidents in "Feature requests".
+- Before submitting a "Bug report" entry, please make sure that you have provided us with enough information, so that we can reproduce the problem. The more details you send, the easier it will be for us to isolate the problem and resolve it.
+- Please do not use “General feedback” to post your technical problems. The purpose of this section is to allow you to send us feedback on our site, our products, and our services.
+
+> **Note**
+>
+> After we reproduce a bug or add a feature request to our ToDo list, we will add Telerik points to your account and send out a notification.
+
+
+### Creating a new bug report - guidelines
+
+Sometimes it is difficult to make a distinction between a support incident and a bug report. However, if you feel that there is a generic problem with any of our products that can be reproduced, you should definitely consider opening a "Bug report".
+
+While submitting a "Bug report" entry, please make sure you give us as many details as possible. As a start, please provide the steps required to reproduce the error, as well as some information about your environment (OS, .NET framework, browser, and so on).
+
+Additionally, if you feel that screenshots or some other visual material will help us understand the issue better, please do not hesitate to attach those to the thread. A runnable project that exhibits the problem would be appreciated as well.
+
+### Starting a new support ticket - guidelines
+Telerik strives to constantly improve its services. In order to help us provide you with a quick and accurate response, please follow the guidelines below when submitting a support ticket:
+
+- Describe your question in detail. Although we are familiar with most of the problems people are having, there is always a chance that you are the first one to report an issue. Sending us as much information as possible will help us identify the source and provide you with a fix or workaround.
+- Provide step by step instructions on how to reproduce the error.
+- Send us the stack trace of the exception you are receiving (if applicable)
+- Attach the source code that generates the exception you are receiving.
+- Attach a screenshot of the observed behavior and a screenshot of the expected behavior (if applicable).
+- Attach a simple runnable project (zipped, no 3rd party controls), which isolates and demonstrates your problem.
+		
+The zipped project should contain:
+- The /bin folder with the respective version of the Telerik assembly (or specify that version exactly without sending the dll itself).
+- The ascx/aspx page, together with the codebehind, which reproduces the error.
+- A backup of your database (if needed).
+- Other necessary resources (classes, css files, etc., if applicable) or specific instructions for your particular case.
+- Please, exclude/remove all 3rd party controls.
+- The project should run in a test environment without major modifications.
+
+
+
 
 ## Test Studio Licensing
 
-<p class="trigger"><a href="#">What license do I get with Test Studio?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio is offered with a User License with Subscription and Priority Support which gives a specific machine rights to build, modify and execute tests. Test Studio can be installed on multiple machines as long as it’s only activated on one machine at a time (assuming a single license is purchased). If you need to move the license to another machine, a simple, one-click deactivation will free-up the license so it may be activated on another machine. There is no limit to the number of times this process can be performed and no need to get in touch with us, it just works.<br><br>
-		The User License with Subscription and Priority Support offers free updates and priority support for 1 year. </p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Do I need a license key to install Test Studio and/or Test Studio Run-Time?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>While technically a license key is indeed required, we take care of this for you. When activating your license of Test Studio with our ‘Automatic Activation’ option – you simply enter your Telerik.com credentials and we will auto-create the license key for you.<br><br> 
-
-		Please follow the installation instructions provided in your purchase notification e-mail to successfully activate your license.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Can I move my license from one machine to another?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Yes, you can. Test Studio utilizes a per-machine licensing model. This means your license can be activated multiple times on different machines, but not simultaneously. To swap a license between multiple machines - Install Test Studio on each machine, activate one of those instances with your license and use it. When you want to migrate the license to a different machine, deactivate the current instance. Then activate Test Studio on the other machine. <a href="http://www.telerik.com/purchase/teststudio" target="_blank">Read more</a>.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How many users can work with one Test Studio product license?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>There are no restrictions on the number of users who can work with the same Test Studio or Test Studio Run-Time license as long as the software is used on the licensed machine only and only one user is using the software at any given time. Please note, however, that only 1 user per license will be allowed to access our support system.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Am I entitled to free version updates as part of my Test Studio and/or Test Studio Run-Time license?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Yes, our Test Studio and Test Studio Run-Time licenses come with subscription which entitles you to version updates for 1 year from the purchase date.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Can I use the Test Studio and/or Test Studio Run-Time software after my subscription expires?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Yes. Test Studio and Test Studio Run-Time software does not expire so you can use the version you own indefinitely. If you decide not to renew your subscription you will stop receiving version updates and support.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">I just need to run tests, which license should I purchase?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>If you just need to run tests, not create or edit them, then you can opt for a Test Studio Run-Time license. This is a low-cost license that was designed to run tests built with Test Studio on machines that do not have a full license of Test Studio installed.<br><br>
-
-		Test Studio Run-Time license can be used on Build Servers (including continuous integration setups) and Test Lab machines where test execution is all that is needed.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Is support included with the Test Studio product licenses?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio includes a <a href="http://www.telerik.com/purchase/support-plans/teststudio" target="_blank">Priority Support Package</a> which guarantees that your support inquiries will be answered within 24h (Mon-Fri).<br><br>
-
-		Our Test Studio Run-Time license complements the Test Studio license and does not include a support package. To access our support engineers, please use the account where your Test Studio license is registered.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How is Test Studio Run-Time licensed?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio Run-Time license gives a specific machine rights to execute tests created with a full Test Studio license. The Run-Time license does not allow the creation or modification of tests. </p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How long will my support package for Test Studio be valid?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>The support package for Test Studio expires 1 year from the date of your purchase. To receive another year of priority support, you need to renew your subscription. Note that the subscription renewal will also entitle you to another 12 months of product updates. If you decide not to renew your subscription, you will still be able to use the community forum and KB articles, but you will not be able to take advantage of the priority support resources.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Do I get source code with the Test Studio product licenses?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>No, source code is not included with Test Studio and Test Studio Run-Time licenses.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How does your licensing handle redistribution rights?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Redistribution rights are not included with Test Studio and Test Studio Run-Time licenses. </p>
-    </div>
-</div>
+### What license do I get with Test Studio?
+
+Test Studio is offered with a User License with Subscription and Priority Support which gives a specific machine rights to build, modify and execute tests. Test Studio can be installed on multiple machines as long as it’s only activated on one machine at a time (assuming a single license is purchased). If you need to move the license to another machine, a simple, one-click deactivation will free-up the license so it may be activated on another machine. There is no limit to the number of times this process can be performed and no need to get in touch with us, it just works.
+The User License with Subscription and Priority Support offers free updates and priority support for 1 year. 
+
+### Do I need a license key to install Test Studio and/or Test Studio Run-Time?
+
+While technically a license key is indeed required, we take care of this for you. When activating your license of Test Studio with our ‘Automatic Activation’ option – you simply enter your Telerik.com credentials and we will auto-create the license key for you. 
+
+Please follow the installation instructions provided in your purchase notification e-mail to successfully activate your license.
+
+### Can I move my license from one machine to another?
+
+Yes, you can. Test Studio utilizes a per-machine licensing model. This means your license can be activated multiple times on different machines, but not simultaneously. To swap a license between multiple machines - Install Test Studio on each machine, activate one of those instances with your license and use it. When you want to migrate the license to a different machine, deactivate the current instance. Then activate Test Studio on the other machine. <a href="http://www.telerik.com/purchase/teststudio" target="_blank">Read more</a>.
+
+### How many users can work with one Test Studio product license?
+
+There are no restrictions on the number of users who can work with the same Test Studio or Test Studio Run-Time license as long as the software is used on the licensed machine only and only one user is using the software at any given time. Please note, however, that only 1 user per license will be allowed to access our support system.
+
+### Am I entitled to free version updates as part of my Test Studio and/or Test Studio Run-Time license?
+
+Yes, our Test Studio and Test Studio Run-Time licenses come with subscription which entitles you to version updates for 1 year from the purchase date.
+
+### Can I use the Test Studio and/or Test Studio Run-Time software after my subscription expires?
+
+Yes. Test Studio and Test Studio Run-Time software does not expire so you can use the version you own indefinitely. If you decide not to renew your subscription you will stop receiving version updates and support.
+
+### I just need to run tests, which license should I purchase?
+
+If you just need to run tests, not create or edit them, then you can opt for a Test Studio Run-Time license. This is a low-cost license that was designed to run tests built with Test Studio on machines that do not have a full license of Test Studio installed.
+
+Test Studio Run-Time license can be used on Build Servers (including continuous integration setups) and Test Lab machines where test execution is all that is needed.
+
+### Is support included with the Test Studio product licenses?
+
+Test Studio includes a <a href="http://www.telerik.com/purchase/support-plans/teststudio" target="_blank">Priority Support Package</a> which guarantees that your support inquiries will be answered within 24h (Mon-Fri).
+
+Our Test Studio Run-Time license complements the Test Studio license and does not include a support package. To access our support engineers, please use the account where your Test Studio license is registered.
+
+### How is Test Studio Run-Time licensed?
+
+Test Studio Run-Time license gives a specific machine rights to execute tests created with a full Test Studio license. The Run-Time license does not allow the creation or modification of tests. 
+
+### How long will my support package for Test Studio be valid?
+
+The support package for Test Studio expires 1 year from the date of your purchase. To receive another year of priority support, you need to renew your subscription. Note that the subscription renewal will also entitle you to another 12 months of product updates. If you decide not to renew your subscription, you will still be able to use the community forum and KB articles, but you will not be able to take advantage of the priority support resources.
+
+### Do I get source code with the Test Studio product licenses?
+
+No, source code is not included with Test Studio and Test Studio Run-Time licenses.
+
+### How does your licensing handle redistribution rights?
+
+Redistribution rights are not included with Test Studio and Test Studio Run-Time licenses. 
 
 ## Support Plans
 
-<p class="trigger"><a href="#">What does my support package include?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Your Test Studio license comes with 1 year of subscription and priority support which guarantees you 24 hour response time to your support inquiries (Monday – Friday). Test Studio subscriptions also include access to all product updates released within your subscription period.</p>
-    </div>
-</div>
+### What does my support package include?
+
+Your Test Studio license comes with 1 year of subscription and priority support which guarantees you 24 hour response time to your support inquiries (Monday – Friday). Test Studio subscriptions also include access to all product updates released within your subscription period.
+
+### Can I submit support inquiries while I’m using the trial version?
 
-<p class="trigger"><a href="#">Can I submit support inquiries while I’m using the trial version?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>During your Test Studio 30-day trial period not only can you take advantage of all available resources and forum posts but you can also submit a ticket to our support team. Please note that trial support inquiries have a 72 hour response time (Monday – Friday), however often times they are answered much quicker. To obtain support, please visit our <a href="http://www.telerik.com/account/support-tickets/available-support-list.aspx" target="_blank">online ticketing system</a>.</p>
-    </div>
-</div>
+During your Test Studio 30-day trial period not only can you take advantage of all available resources and forum posts but you can also submit a ticket to our support team. Please note that trial support inquiries have a 72 hour response time (Monday – Friday), however often times they are answered much quicker. To obtain support, please visit our <a href="http://www.telerik.com/account/support-tickets/available-support-list.aspx" target="_blank">online ticketing system</a>.
 
 ## License Keys
 
+### Do I need a license key to run RadControls?
 
-<p class="trigger"><a href="#">Do I need a license key to install Test Studio / Test Studio Run-Time Edition?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Yes, our Test Studio licenses work with license keys. Upon purchase your license key will be generated. To activate it you will need to provide your login credentials upon starting the product on your machine. For version 2010.1 or earlier the license keys are available in <a href="http://www.telerik.com/account.aspx" target="_blank">Your Account</a> -> Download and Manage your products -> Manage Activation Keys (for the respective Test Studio license). To successfully activate your license, please follow the instructions provided in your purchase notification letter. You can also watch our  <a href="http://www.telerik.com/videos/teststudio/test-studio---product-activation" target="_blank">video tutorial</a> for activating your Test Studio license.</p>
-    </div>
-</div>
+No, you don’t. None of the RadControls suites (ASP.NET AJAX, Telerik Extensions for ASP.NET MVC, WinForms, Silverlight, WPF, Windows Phone), as well as Telerik Reporting, Telerik OpenAccess ORM, Telerik JustCode and Telerik JustMock utilize license keys. This applies to both, trial and purchased licenses.
 
+### Do I need a license key to install Test Studio / Test Studio Run-Time Edition?
 
+Yes, our Test Studio licenses work with license keys. Upon purchase your license key will be generated. To activate it you will need to provide your login credentials upon starting the product on your machine. For version 2010.1 or earlier the license keys are available in <a href="http://www.telerik.com/account.aspx" target="_blank">Your Account </a> -> Download and Manage your products -> Manage Activation Keys (for the respective Test Studio license). To successfully activate your license, please follow the instructions provided in your purchase notification letter. You can also watch our <a href="http://www.telerik.com/videos/teststudio/test-studio---product-activation" target="_blank">video tutorial for activating your Test Studio license</a>.
 
 ## Administrative Level Access
 
-<p class="trigger"><a href="#why-test-studio-requires-administrative-level-access.">Does Test Studio Require Administrative Level Access?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio features do not require administrative rights to function properly. </p>
-        <p>Only certain configuration tasks require to be initiated from Windows Administrator account. Here is a list of these:</p>
-        <ul>
-        <li><strong>1. <a href="/prerequisites/installation/install-procedure" target="_blank">Test Studio installation</a></strong> – initial install, modification of existing installation, uninstall.</li>
-        <li><strong>2. <a href="/automated-tests/scheduling/overview" target="_blank">Configuration of the Test Studio Services</a></strong> – Test Studio starts Windows services and registers certain ports to be available for non-admin users.</li>
-        </ul>
-    </div>
-</div>
+### Does Test Studio Require Administrative Level Access?
 
+Test Studio features do not require administrative rights to function properly. 
+Only certain configuration tasks require to be initiated from Windows Administrator account. Here is a list of these:
+- 1. <a href="/prerequisites/installation/install-procedure" target="_blank">Test Studio installation</a> – initial install, modification of existing installation, uninstall.
+- 2. <a href="/automated-tests/scheduling/overview" target="_blank">Configuration of the Test Studio Services</a> – Test Studio starts Windows services and registers certain ports to be available for non-admin users.
 
 ## Installation 
 
-<p class="trigger"><a href="#">I want to just copy the Test Studio DLL's to a new machine instead of running the installer.</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Setting up Test Studio or the Testing Framework so that it is fully functional requires much more than just copying a few DLL's into the right folder. Browser extensions must be installed, registry settings must be made, some DLL's must be added to the Global Assembly Cache. The only way to get it setup properly is to run the installer. Otherwise something won't work right: test project compiles may fail, the recorder may fail to attach, tests may fail to run in a specific browser, if you're trying to use Microsoft Test Manager you may get strange error messages.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Can I do an automatic silent install?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>In theory it should be possible. Our installer is a .msi file. You should be able to use <a href="https://support.microsoft.com/kb/314881" target="_blank">Microsoft's MSIEXEC command line tool</a>, with correct command line parameters to do a silent install. DISCLAIMER: we do not officially support this. If you can get it to work then great. If not we're unable to guide you on how to make it work.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Can I run my test scripts on a remote machine which does not have Test Studio installed?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>No, Test Studio must be installed on the remote machine in order to be able to run tests on it. You must run the installer for the product you intend to use on the remote machine:
-		<ul>
-		<li>Test Studio Functional</li>
-		<li>Test Studio Load.</li>
-		<li>Send us the stack trace of the exception you are receiving (if applicable)</li>
-		<li>Test Studio Run-Time - this is the most commonly product used on remote machines. It comes with our Scheduler, Storage Service and Execution Server. Everything you need to run Test Studio tests remotely. It is only missing the Test Studio IDE used for opening, creating and editing tests.</li>
-		<li>Testing Framework</li>
-		</ul></p>
-    </div>
-</div>
+### I want to just copy the Test Studio DLL's to a new machine instead of running the installer.
+
+Setting up Test Studio or the Testing Framework so that it is fully functional requires much more than just copying a few DLL's into the right folder. Browser extensions must be installed, registry settings must be made, some DLL's must be added to the Global Assembly Cache. The only way to get it setup properly is to run the installer. Otherwise something won't work right: test project compiles may fail, the recorder may fail to attach, tests may fail to run in a specific browser, if you're trying to use Microsoft Test Manager you may get strange error messages.
+
+### Can I do an automatic silent install?
+
+In theory it should be possible. Our installer is a .msi file. You should be able to use <a href="https://support.microsoft.com/kb/314881" target="_blank">Microsoft's MSIEXEC command line tool</a>, with correct command line parameters to do a silent install. DISCLAIMER: we do not officially support this. If you can get it to work then great. If not we're unable to guide you on how to make it work.
+
+### Can I run my test scripts on a remote machine which does not have Test Studio installed?
+
+No, Test Studio must be installed on the remote machine in order to be able to run tests on it. You must run the installer for the product you intend to use on the remote machine:
+
+- Test Studio Functional
+- Test Studio Load.
+- Send us the stack trace of the exception you are receiving (if applicable)
+- Test Studio Run-Time - this is the most commonly product used on remote machines. It comes with our Scheduler, Storage Service and Execution Server. Everything you need to run Test Studio tests remotely. It is only missing the Test Studio IDE used for opening, creating and editing tests.
+- Testing Framework
 
 ## Activation
 
-<p class="trigger"><a href="#">How do I activate Test Studio?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>There are two ways to activate Test Studio::
-		<ul>
-		<li><a href="/getting-started/installation/activating-your-license" target="_blank">Automatic Activation</a> - for a computer that has an Internet connection.</li>
-		<li><a href="/getting-started/installation/manual-activation" target="_blank">Manual Activation</a> - for a computer that does not have an Internet connection.</li>
-		</ul></p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">My computer does not have an Internet connection. How do I activate Test Studio on it?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>You can use any computer that has an Internet connection and a web browser and follow our <a href="/getting-started/installation/manual-activation" target="_blank">Manual Activation</a> process to activate Test Studio on your computer that does not have an Internet connection.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Can I transfer my Test Studio license to another machine?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Yes. Simply follow the <a href="/knowledge-base/activation-kb/swap-license" target="_blank">Swap License</a> procedure.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Is there a limit to the number of times I can transfer my Test Studio license?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>No there is no limit. You can transfer your license between machines as many times as you need to.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">When I try to activate Test Studio on my machine it tells me there are no free slots available?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>If you purchased 5 licenses for Test Studio, then you can have up to 5 machines in your organization all activated at the same time. When you try to activate a 6th machine you will get this message. You must deactivate one of your other machines before you can activate the new one.<br><br>
-		There are other reasons that can cause no free activation slots to become available, for example your machine crashed while it was activated, or you want to use Test Studio at home but forgot to deactivate it at work. When this happens you can use the <a href="http://www.telerik.com/account/your-products/testing-tools-manage-license-keys.aspx" target="_blank">Manage License Keys Page</a> to delete the errant activation freeing up a slot in the process.</p>
-    </div>
-</div>
+### How do I activate Test Studio?
 
-## Test Recording
+There are two ways to activate Test Studio::
+
+- <a href="/getting-started/installation/activating-your-license" target="_blank">Automatic Activation</a> - for a computer that has an Internet connection.
+- <a href="/getting-started/installation/manual-activation" target="_blank">Manual Activation</a> - for a computer that does not have an Internet connection.
+
+### My computer does not have an Internet connection. How do I activate Test Studio on it?
+
+You can use any computer that has an Internet connection and a web browser and follow our <a href="/getting-started/installation/manual-activation" target="_blank">Manual Activation</a> process to activate Test Studio on your computer that does not have an Internet connection.
 
+### Can I transfer my Test Studio license to another machine?
 
+Yes. Simply follow the <a href="/knowledge-base/activation-kb/swap-license" target="_blank">Swap License</a> procedure.
 
+### Is there a limit to the number of times I can transfer my Test Studio license?
 
-<p class="trigger"><a href="#">Can I automate CAPTCHA?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio cannot be used to automate it. CAPTCHA is specifically designed to ensure the response is generated by a person and not a computer.<br><br>The best we can offer in terms of testing phase for an application is as follows: 
-        <ul>
-		<li>Whitelist company test IP. Adding your company or test machine’s IP to the trusted list and allow these IP to pass the CAPTCHA.</li>
-		<li>Turn off the CAPTCHA on the test environment, for example if you have testing, staging, and production.</li>
-        </ul>
-    </div>
-</div>
+No there is no limit. You can transfer your license between machines as many times as you need to.
+
+### When I try to activate Test Studio on my machine it tells me there are no free slots available?
+
+If you purchased 5 licenses for Test Studio, then you can have up to 5 machines in your organization all activated at the same time. When you try to activate a 6th machine you will get this message. You must deactivate one of your other machines before you can activate the new one.
+There are other reasons that can cause no free activation slots to become available, for example your machine crashed while it was activated, or you want to use Test Studio at home but forgot to deactivate it at work. When this happens you can use the <a href="http://www.telerik.com/account/your-products/testing-tools-manage-license-keys.aspx" target="_blank">Manage License Keys Page</a> to delete the errant activation freeing up a slot in the process.
+
+## Test Recording
+
+### Can I automate CAPTCHA?
+
+Test Studio cannot be used to automate it. CAPTCHA is specifically designed to ensure the response is generated by a person and not a computer.The best we can offer in terms of testing phase for an application is as follows: 
+- Whitelist company test IP. Adding your company or test machine’s IP to the trusted list and allow these IP to pass the CAPTCHA.
+- Turn off the CAPTCHA on the test environment, for example if you have testing, staging, and production.
 
 ## Source Control
 
-<p class="trigger"><a href="#">What source control systems does Test Studio support?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio has built-in support for Git-based repositories. However you can use other source control systems as well. Since all Test Studio projects are file based, you can use any source control system outside of Test Studio that will check files in and out.</p>
-    </div>
-</div>
+### What source control systems does Test Studio support?
 
+Test Studio has built-in support for Git-based repositories. However you can use other source control systems as well. Since all Test Studio projects are file based, you can use any source control system outside of Test Studio that will check files in and out.
 
 ## Test Execution
 
+### My selected browser opens but nothing happens. The test script does not start.
 
-<p class="trigger"><a href="#">My selected browser opens but nothing happens. The test script does not start.</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p> <a href="/knowledge-base/best-practices-kb/generate-application-log#operate-with-logging-in-standalone-version" target="_blank">Generate the Test Studio application log</a> and submit a ticket to provide details for the occurence. 
-		</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Is there a way I can run my tests in different versions of the same browser on the same machine</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>No. You can only install one version of the browser on a machine at a time. Test Studio will run the test in whatever version is currently installed. There is no mechanism to instruct Test Studio to run the test in a specific browser version such as IE 8.<br><br>
-		However you can have multiple different browsers installed on the same machine at the same time. Then Test Studio can run your tests in each of the available browsers, one browser at a time (not concurrently on the same machine). 
-        </p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How do I run my tests in different browser versions?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>To run your tests in multiple versions of the same browser requires you to setup multiple machines. Test Studio can only use the version of the browser that is currently installed on one machine. If you want to do something like run your tests in Chrome v.130, v.131, and v.133 requires you to setup 3 different machines (which can be VM's) each with a different version of Chrome installed on it.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How can I create a performance test with N concurrent users?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>A <a href="/features/testing-types/performance-testing/Overview" target="_blank">Test Studio Performance test</a> will only do one user at a time. It is not possible create this type of test with more than one user.<br><br>
-		To stress your web server with multiple users you must create and execute a <a href="/features/testing-types/load-testing/Overview" target="_blank">Test Studio Load test</a>.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How do I automate testing of a PDF file?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio provides a <a href="/automated-tests/recording/pdf-validation" target="_blank">built-in mechanism to valiate PDF file</a> as part of a web test. </p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">Why are compilation errors being thrown by tests that have no relationship with the script that is being run?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>The reason is that the whole project and pages.g.cs/vb is compiled before the run.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">When I build I get this build error: "Pages.g.cs/vb" was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter.</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>This happens when you add the Test Studio automatically generated file Pages.g.cs/vb to your Visual Studio project. This is unnecessary because our Visual Studio plug-in will automatically include this file in all compiles. By adding it to you Visual Studio project file, it creates duplicate compile references, and hence this error. Simply remove the Pages.g.cs/vb file from your Visual Studio project to fix this build error.</p>
-    </div>
-</div>
-
-
-<p class="trigger"><a href="#">How do I run tests in parallel/How do I run tests in multiple browsers?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>We have a <a href="/knowledge-base/test-execution-kb/multi-browsers" target="_blank">detailed KB article</a> that explains how to do this.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How to handle Autocomplete input boxes?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Autocomplete boxes generally require that <a href="/features/test-maintenance/test-step-properties" target="_blank">SimulateRealTyping</a> is checked when entering text.</p>
-    </div>
-</div>
-
-<p class="trigger"><a href="#">How to detect JavaScript errors?</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Test Studio provides a <a href="/features/custom-steps/web-test-common/check-js-errors" target="_blank">built-in mechanism to check for JS errors</a> as part of a web test.</p>
-    </div>
-</div>
+<a href="/knowledge-base/best-practices-kb/generate-application-log#operate-with-logging-in-standalone-version" target="_blank">Generate the Test Studio application log</a> and submit a ticket to provide details for the occurence. 
+	
+### Is there a way I can run my tests in different versions of the same browser on the same machine
 
-## Test List Scheduling
+No. You can only install one version of the browser on a machine at a time. Test Studio will run the test in whatever version is currently installed. There is no mechanism to instruct Test Studio to run the test in a specific browser version such as IE 8.
+However you can have multiple different browsers installed on the same machine at the same time. Then Test Studio can run your tests in each of the available browsers, one browser at a time (not concurrently on the same machine). 
+
+### How do I run my tests in different browser versions?
+
+To run your tests in multiple versions of the same browser requires you to setup multiple machines. Test Studio can only use the version of the browser that is currently installed on one machine. If you want to do something like run your tests in Chrome v.130, v.131, and v.133 requires you to setup 3 different machines (which can be VM's) each with a different version of Chrome installed on it.
+
+### How can I create a performance test with N concurrent users?
 
+A <a href="/features/testing-types/performance-testing/Overview" target="_blank">Test Studio Performance test</a> will only do one user at a time. It is not possible create this type of test with more than one user.
+To stress your web server with multiple users you must create and execute a <a href="/features/testing-types/load-testing/Overview" target="_blank">Test Studio Load test</a>.
 
+### How do I automate testing of a PDF file?
 
-<p class="trigger"><a href="#">I can see test list results on one machine but not the other.</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Check that all machines are <a href="/features/scheduling-test-runs/connect-to-scheduling-server" target="_blank">connected to the scheduling server</a>. Projects that are configured to "Run Locally" will only show the results loaded from the local set of result files. It will not show results stored in the scheduling server, even when the local machine is your scheduling server.</p>
-    </div>
-</div>
+Test Studio provides a <a href="/automated-tests/recording/pdf-validation" target="_blank">built-in mechanism to valiate PDF file</a> as part of a web test. 
 
-<p class="trigger"><a href="#">How to select which browser to run test list in</a></p>
-<div class="toggle_container">
-   <div class="block">
-        <p>Select the test list you want to execute and click on Edit Settings.<br><br>
-		Under the Web tab select the execution browser.
-		</p>
-    </div>
-</div>
+### Why are compilation errors being thrown by tests that have no relationship with the script that is being run?
 
+The reason is that the whole project and pages.g.cs/vb is compiled before the run.
 
-<script>
+### When I build I get this build error: "Pages.g.cs/vb" was specified more than once in the "Sources" parameter. Duplicate items are not supported by the "Sources" parameter.
+
+This happens when you add the Test Studio automatically generated file Pages.g.cs/vb to your Visual Studio project. This is unnecessary because our Visual Studio plug-in will automatically include this file in all compiles. By adding it to you Visual Studio project file, it creates duplicate compile references, and hence this error. Simply remove the Pages.g.cs/vb file from your Visual Studio project to fix this build error.
+
+### How do I run tests in parallel/How do I run tests in multiple browsers?
+
+We have a <a href="/knowledge-base/test-execution-kb/multi-browsers" target="_blank">detailed KB article</a> that explains how to do this.
+
+### How to handle Autocomplete input boxes?
+
+Autocomplete boxes generally require that <a href="/features/test-maintenance/test-step-properties" target="_blank">SimulateRealTyping</a> is checked when entering text.
+
+### How to detect JavaScript errors?
+
+Test Studio provides a <a href="/features/custom-steps/web-test-common/check-js-errors" target="_blank">built-in mechanism to check for JS errors</a> as part of a web test.
+
+## Test List Scheduling
 
-window.addEventListener('DOMContentLoaded', function () {
+### I can see test list results on one machine but not the other.
 
-window.animateScrollTo = function(e) {
-    e.preventDefault();
-};
+Check that all machines are <a href="/features/scheduling-test-runs/connect-to-scheduling-server" target="_blank">connected to the scheduling server</a>. Projects that are configured to "Run Locally" will only show the results loaded from the local set of result files. It will not show results stored in the scheduling server, even when the local machine is your scheduling server.
 
-$("body p.trigger > a[href^='#']").on('click', window.animateScrollTo);
+### How to select which browser to run test list in
 
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(){
-        $(this).toggleClass("active").next().slideToggle("normal");
-    });
-});
-</script>
+Select the test list you want to execute and click on Edit Settings.
+Under the Web tab select the execution browser.
diff --git a/docs/features/azure-dev-ops-mapper/azure-results-sync.md b/docs/features/azure-dev-ops-mapper/azure-results-sync.md
index 08711da7..e3887539 100644
--- a/docs/features/azure-dev-ops-mapper/azure-results-sync.md
+++ b/docs/features/azure-dev-ops-mapper/azure-results-sync.md
@@ -28,9 +28,9 @@ position: 3
 
 # Local Machine Example
 
-```cmd 
+````batch 
 "c:\Program Files (x86)\Progress\Test Studio\Bin\AzureResultsMapper\Telerik.TestStudio.AzureResultsSync.exe" url=https://dev.azure.com/my-org token=<MY-TOKEN> map="<PATH-MAPPING-FILE>" aiiresult="<PATH-MAPPING-FILE>"
-```
+````
 
 # Azure DevOps Example
 
@@ -38,7 +38,7 @@ In the scenario of building a CI pipeline the test list run needs to be set thro
 
 Below is an example pipeline with only these two jobs:
 
-```yml
+````yml
 jobs:
   - job: Run and Upload Results
     steps:
@@ -58,7 +58,7 @@ jobs:
           script: |
             "c:\Program Files (x86)\Progress\Test Studio\Bin\AzureResultsMapper\Telerik.TestStudio.AzureResultsSync.exe" url=https://dev.azure.com/prgs-devtools map=$(System.DefaultWorkingDirectory)\TestingProjects\HTMLProject\MapperPipeline\AzDoMap.tsazdo aiiresult=$(System.DefaultWorkingDirectory)\TestingProjects\HTMLProject\MapperPipeline\Results\myResult.aiiresult
 
-```
+````
 
 - The __'Run Test Studio tests'__ task executes a test list with the ArtOfTest.Runner.exe and stores the results in file named myResult.aiiresult.
 - The __'Upload results'__ task converts the Test Studio results from myResult.aiiresult file and uploads them as new Azure DevOps run. 
diff --git a/docs/features/custom-steps/overview.md b/docs/features/custom-steps/overview.md
index dfacad90..3f2ad806 100644
--- a/docs/features/custom-steps/overview.md
+++ b/docs/features/custom-steps/overview.md
@@ -40,12 +40,16 @@ The __General__ section in the __Step Builder__ is divided in three sub-sections
 
 - The __Common__ section consists of different steps suggestions based on the type of test - web, desktop or WPF.
 
-<table id="no-table">
-	<tr>
-		<td>![Common web test steps][5] <br><br>**Web Test**</td>
-		<td>![Common WPF test steps][7] <br><br>**WPF Test**</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Common web test steps][5] <br><br>**Web Test**</td>
+<td>
+
+![Common WPF test steps][7] <br><br>**WPF Test**</td>
+</tr>
+</table>
 
 1. [Test as Step](/features/custom-steps/test-as-step) - run an existing test as a single step.
 1. [API Test as Step](/features/execute-apitest/add-api-test-as-step) - run an existing API test as a single step.
diff --git a/docs/features/data-driven-testing/add-data-source.md b/docs/features/data-driven-testing/add-data-source.md
index 1bf581e6..2b91882c 100644
--- a/docs/features/data-driven-testing/add-data-source.md
+++ b/docs/features/data-driven-testing/add-data-source.md
@@ -58,13 +58,13 @@ In the below section you can read how to prepare the XML file and add it to the
 
 XML files are type of documents that both humans and machines can read. The structure of the document is defined by tags and Test Studio uses these to define the data source values. Here is an example of a basic XML file with two columns:
 
-```xml
+````XML
 <Searches>
    <Search UserName="john.smith" Password="johnspass" />
    <Search UserName="bob.brown" Password="bobspass" />
    <Search UserName="sam.jones" Password="samspass" />
 </Searches>
-```
+````
 
 *Search* is the equivalent of an Excel Sheet. *UserName* and *Password* translate as the column names.
 
@@ -113,12 +113,7 @@ Adding a database source requires additional details compared to adding an Excel
 > Find examples for **[How to connect to a SQL Database](/features/data-driven-testing/sql-database-example)** and **[How to connect to an Oracle Database](/features/data-driven-testing/oracle-db-example)**.
 
 [1]: /img/features/data-driven-testing/add-data-source/fig1.png
-[2]: /img/features/data-driven-testing/add-data-source/fig2.png
-[3]: /img/features/data-driven-testing/add-data-source/fig3.png
 [4]: /img/features/data-driven-testing/add-data-source/fig4.png
-[5]: /img/features/data-driven-testing/add-data-source/fig5.png
-[6]: /img/features/data-driven-testing/add-data-source/fig6.png
-[7]: /img/features/data-driven-testing/add-data-source/fig7.png
 [8]: /img/features/data-driven-testing/add-data-source/fig8.png
 [9]: /img/features/data-driven-testing/add-data-source/fig9.png
 [9a]: /img/features/data-driven-testing/add-data-source/fig9a.png
diff --git a/docs/features/data-driven-testing/attach-columns-verifications.md b/docs/features/data-driven-testing/attach-columns-verifications.md
deleted file mode 100644
index f33734e4..00000000
--- a/docs/features/data-driven-testing/attach-columns-verifications.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Attach Columns to Verifications
-page_title: Attach Columns to Verifications
-description: "How to set the values from the data source to be used in the test steps in Test Studio. Set a column from the data source/excel/csv/database to verify different text by each test run in Test Studio. Parameterize the test in Test Studio. Parameterize the values verified on a page in a Test Studio test run"
-
-position: 4
-publish: false
----
-keep for the redirects
diff --git a/docs/features/data-driven-testing/bind-test-data-source.md b/docs/features/data-driven-testing/bind-test-data-source.md
index ab9215e7..d8170014 100644
--- a/docs/features/data-driven-testing/bind-test-data-source.md
+++ b/docs/features/data-driven-testing/bind-test-data-source.md
@@ -20,16 +20,24 @@ Choose a test from the _Project Explorer_ and click the __Bind Test__ button fro
 
 The **Bind test to data source** dialog opens with the option to choose a data source. Click the **Select Data Source** drop-down and select the one you have  defined. If your source is an Excel spreadsheet, choose which sheet from the spreadsheet to use. Once you select a sheet, the data from that sheet will be read and displayed in the dialog. Check out that the __first row of the spreadsheet is used to define the column names__.
 
-<table id="no-table">
-<tr>
-<td>!![Bind test to data source window][3]</td>
-<td>![Select Data Source][4]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Bind test to data source window][3]</td>
+<td>
+
+![Select Data Source][4]</td>
 </tr>
-<tr>
-<td>Choose Data Source to Bind</td>
-<td>Excel Sheet Selected</td>
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+**Choose Data Source to Bind**</td>
+<td>
+
+**Excel Sheet Selected**</td>
 </tr>
-<table>
+</table>
 
 > __Note__
 ><br>
@@ -47,12 +55,16 @@ If you need to use only part of the rows in an Excel sheet, you can enable the *
 - If left unchecked, all data rows will be used during the test run.
 - To limit which rows to use, check that box and select which rows you want to use by clicking the numeric up/down counters, and then **Update** to apply changes.
 
-<table id="no-table">
-<tr>
-<td>![filter data][5]</td>
-<td>![filter data][6]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![filter data][5]</td>
+<td>
+
+![filter data][6]</td>
 </tr>
-<table>
+</table>
 
 ### Use Specific Data from SQL Data Source
 
@@ -77,8 +89,8 @@ To remove the external data source associated with a test, right click that test
 
 ![Remove Data Binding][8]
 
-[1]: /img/features/data-driven-testing/bind-test-data-source/fig1.png
-[2]: /img/features/data-driven-testing/bind-test-data-source/fig2.png
+
+
 [3]: /img/features/data-driven-testing/bind-test-data-source/fig3.png
 [4]: /img/features/data-driven-testing/bind-test-data-source/fig4.png
 [5]: /img/features/data-driven-testing/bind-test-data-source/fig5.png
diff --git a/docs/features/data-driven-testing/manage-external-data-source.md b/docs/features/data-driven-testing/manage-external-data-source.md
index ec592857..89fa9025 100644
--- a/docs/features/data-driven-testing/manage-external-data-source.md
+++ b/docs/features/data-driven-testing/manage-external-data-source.md
@@ -44,4 +44,3 @@ Then, you can open the _Manage Data Source_ dialog, choose the data file to dele
 [1]: /img/features/data-driven-testing/manage-external-data-source/fig1.png
 [2]: /img/features/data-driven-testing/manage-external-data-source/fig2.png
 [3]: /img/features/data-driven-testing/manage-external-data-source/fig3.png
-[4]: /img/features/data-driven-testing/manage-external-data-source/fig4.png
diff --git a/docs/features/data-driven-testing/manage-local-data.md b/docs/features/data-driven-testing/manage-local-data.md
index 010366b0..e466dee5 100644
--- a/docs/features/data-driven-testing/manage-local-data.md
+++ b/docs/features/data-driven-testing/manage-local-data.md
@@ -38,12 +38,16 @@ Test Studio provides few options to easily modify a data table.
 
 - __Add a row/Delete the last row__ or __Add a column/Delete the last column__
 
-<table id="no-table">
-<tr>
-<td>![Add/Delete Row][22]<br>Add/Delete Row</td>
-<td>![Add/Delete Column][23]<br>Add/Delete Column</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Add/Delete Row][22]<br>Add/Delete Row</td>
+<td>
+
+![Add/Delete Column][23]<br>Add/Delete Column</td>
 </tr>
-<table>
+</table>
 
 [2]: /img/features/data-driven-testing/local-data-driven-test/fig2.png
 [4]: /img/features/data-driven-testing/local-data-driven-test/fig4.png
diff --git a/docs/features/data-driven-testing/oracle-db-example.md b/docs/features/data-driven-testing/oracle-db-example.md
index 149e046c..e900c47d 100644
--- a/docs/features/data-driven-testing/oracle-db-example.md
+++ b/docs/features/data-driven-testing/oracle-db-example.md
@@ -28,9 +28,9 @@ Once the table is created it is possible to connect to it and use it for data-dr
 
 4.&nbsp; Here's an example for **Connection String**:
 
-```
+````
 Data Source=XE;User Id=SYSTEM;Password=pass;
-```
+````
 
 It is possible to create many different connection strings. See <a href="https://www.connectionstrings.com/oracle/" target="_blank">here</a> for more examples.
 
diff --git a/docs/features/data-driven-testing/overview.md b/docs/features/data-driven-testing/overview.md
deleted file mode 100644
index 397315e2..00000000
--- a/docs/features/data-driven-testing/overview.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Overview
-page_title: Data Driven Testing Overview
-description: "Data Driven Testing in Test Studio. Parameterize the test in Test Studio. Use iterated data in a Test Studio test"
-position: 0
-publish: false 
----
-# Data Driven Testing
-
-Data Driven Testing is a testing methodology in which the same sequence of test steps are performed repeatedly, using a data source to drive the input values of those steps and/or the values to expect, when performing verification steps. 
-
-Test Studio supports can be used for data driven testing. It supports five different external data sources:
-
-- [Local Data Source](/features/data-driven-testing/local-data-driven-test)
-- [Excel spreadsheet](/features/data-driven-testing/add-data-source#add-an-excel-spreadsheet)
-- [XML file](/features/data-driven-testing/add-data-source#add-an-xml-file)
-- [CSV file](/features/data-driven-testing/add-data-source#add-a-csv-file)
-- [SQL database](/features/data-driven-testing/add-data-source#add-a-database-source)
-
-Create an external data driven test by following these steps:
-
-1. [Add a data source to your test project](/features/data-driven-testing/add-data-source) - select from where to get the data.
-1. [Bind the data source to your test](/features/data-driven-testing/bind-test-data-source)- since you may have multiple data source definitions in your test project, you need to bind your data driven test to a specific data source.
-1. [Attach the data source columns to input values](/features/data-driven-testing/attach-columns-input-values) - connect the inputs of your test  to specific columns of the data source.
-1. [Attach the data source columns to verifications](/features/data-driven-testing/attach-columns-verifications) - connect the expected values of verifications to specific columns of the data source
diff --git a/docs/features/data-driven-testing/sql-database-example.md b/docs/features/data-driven-testing/sql-database-example.md
index 1934d71a..133c958a 100644
--- a/docs/features/data-driven-testing/sql-database-example.md
+++ b/docs/features/data-driven-testing/sql-database-example.md
@@ -25,9 +25,9 @@ Now we can connect to it and use it for data-driven testing.
 
 4.&nbsp; Here's an example for **Connection String**:
 
-```
+````
 Data Source=MACHINENAME\SQLEXPRESS; Initial Catalog=myFirstDB; Integrated Security=true;
-```
+````
 
 - Data Source is the name of the SQL Server.
 - Initial Catalog is the named of the Database.
diff --git a/docs/features/dialogs-and-popups/modal-popups.md b/docs/features/dialogs-and-popups/modal-popups.md
deleted file mode 100644
index 5f478901..00000000
--- a/docs/features/dialogs-and-popups/modal-popups.md
+++ /dev/null
@@ -1,9 +0,0 @@
----
-title: Modal Popups
-page_title: Modal Popups
-description: "There is a modal popup displayed in the tested page - how can I automate modal popup windows in Test Studio tests. Connect to modal popup window during Test Studio test run/execution"
-publish: false
-position: 1
----
-
-
diff --git a/docs/features/elements-explorer/element-mapping.md b/docs/features/elements-explorer/element-mapping.md
index 656c72dc..432b493e 100644
--- a/docs/features/elements-explorer/element-mapping.md
+++ b/docs/features/elements-explorer/element-mapping.md
@@ -8,24 +8,32 @@ position: 6
 
 Once your application is ready for testing you can map your <a href="/features/elements-explorer/predefined-elements" target="_blank">predefined elements</a> to the actual elements. In order to proceed select the predefined element you would like to map and select Element Mapping button:
 
-<table id="no-table">
-	<tr>
-		<td>![Element Mapping TS][6] <br><br>**Standalone version**</td>
-		<td>![Element Mapping TS][15] <br><br>**VS plugin**</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Element Mapping TS][6] <br><br>**Standalone version**</td>
+<td>
+		
+![Element Mapping TS][15] <br><br>**VS plugin**</td>
+</tr>
+</table>
 
 The mapping dialog window appears allowing you to select between a Web or WPF test.
 
 * For Web: type New URL or choose from Recent URLs and click **Start Mapping** button. 
 * For WPF: select new WPF app using the browse button or choose from Recent Apps and click **Start Mapping** button.
 
-<table id="no-table">
-<tr>
-<td>![Web][7] <br><br>**Web**</td>
-<td>![WPF][8] <br><br>**WPF**</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Web][7] <br><br>**Web**</td>
+<td>
+
+![WPF][8] <br><br>**WPF**</td>
 <tr>
-<table>
+</table>
 
 > The example shown here is for a Web test, but for a WPF test the actions are exactly the same.
 
diff --git a/docs/features/elements-explorer/predefined-elements.md b/docs/features/elements-explorer/predefined-elements.md
index 7a262c02..b68268ac 100644
--- a/docs/features/elements-explorer/predefined-elements.md
+++ b/docs/features/elements-explorer/predefined-elements.md
@@ -32,8 +32,6 @@ Once created you can edit the properties of the element such as ControlType, Fri
 
 ![Edit Element's properties][4]
 
-> If you are using Silverlight, please make sure you change the **TechnologyType** to **Silverlight** in order to be able to create the appropriate steps.
-
 You can also use the <a href="/getting-started/test-recording/step-suggestions" target="_blank">Step Builder</a> to create various steps against the element such as actions and verifications:
 
 ![Actions/Verifications][5]
@@ -56,8 +54,6 @@ Once created you can edit the properties of the element such as ControlType, Fri
 
 ![Edit Element's properties][19]
 
-> If you are using Silverlight, please make sure you change the **TechnologyType** to **Silverlight** in order to be able to create the appropriate steps.
-
 You can also use the <a href="/getting-started/test-recording/step-suggestions" target="_blank">Step Builder</a> to create various steps against the element such as actions and verifications:
 
 ![Actions/Verifications][20]
diff --git a/docs/features/integration/bug-tracking/configuration.md b/docs/features/integration/bug-tracking/configuration.md
index 7455d36b..06df034b 100644
--- a/docs/features/integration/bug-tracking/configuration.md
+++ b/docs/features/integration/bug-tracking/configuration.md
@@ -29,12 +29,16 @@ Connect with bug tracking applications to track bugs you encounter while testing
 
 4.&nbsp; Enter the Server URL and click the **Connect** button.
 
-<table id=no-table>
-	<tr>
-		<td>![TFS service Online][5] <br><br>Azure DevOps (Online TFS Service)</td>
-		<td>![TFS server on premise][6] <br><br>TFS Server on-premise</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![TFS service Online][5] <br><br>Azure DevOps (Online TFS Service)</td>
+<td>
+		
+![TFS server on premise][6] <br><br>TFS Server on-premise</td>
+</tr>
+</table>
 
 Enter valid credentials when prompted. The below example requires username and password for the Azure DevOps service. 
 
@@ -42,12 +46,16 @@ Enter valid credentials when prompted. The below example requires username and p
 
 5.&nbsp; Once the connection to the server is successfully established, select the **Team Project** for Azure DevOps, and the **Team Project Collection** and **Team Project** for on-premise server, then click **Save**.
 
-<table id=no-table>
-	<tr>
-		<td>![TFS service Online][8] <br><br>Azure DevOps (Online TFS Service)</td>
-		<td>![TFS server on premise][9] <br><br>TFS Server on-premise</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+
+![TFS service Online][8] <br><br>Azure DevOps (Online TFS Service)</td>
+<td>
+		
+![TFS server on premise][9] <br><br>TFS Server on-premise</td>
+</tr>
+</table>
 
 ## Jira Server
 
@@ -128,4 +136,3 @@ Click **Advanced Settings** ![Advanced settings button][20] to set whether to at
 [30]: /img/features/integration/bug-tracking/configuration/bug-report-icon-navigate-JIRA.png
 [20]: /img/features/integration/bug-tracking/configuration/advanced-settings.png
 [21]: /img/features/integration/bug-tracking/configuration/choose-advanced-settings.png
-[22]: /img/features/integration/bug-tracking/configuration/import-from-exploratory.png
diff --git a/docs/features/integration/bug-tracking/custom-plugin.md b/docs/features/integration/bug-tracking/custom-plugin.md
index 687e342f..f2eeefc7 100644
--- a/docs/features/integration/bug-tracking/custom-plugin.md
+++ b/docs/features/integration/bug-tracking/custom-plugin.md
@@ -25,24 +25,24 @@ Test Studio uses its plugins model to run the Bug Trackers. The type of Bug Trac
 
 3.&nbsp; Add the following using statement to the class file:
 
-```C#
+````C#
 using ArtOfTest.WebAii.Design.Extensibility.BugTracking;
-```
+````
 
 4.&nbsp; The *ArtOfTest.WebAii.Design.Extensibility.BugTracking* namespace contains **IBugTracker** that the class needs 	to implement:
 
-```C#
+````C#
 namespace ClassLibrary1
 {
     public class Class2 : IBugTracker
     {
     }
 }
-```
+````
 
 5.&nbsp; Right click on IBugTracker and select Implement Interface > Implement Interface. This displays all the methods   	and notifications exposed by Test Studio. Here are definitions for each IBugTracker member:
 
-```C#
+````C#
 	namespace ClassLibrary1
 	{
 		public class Class2 : IBugTracker
@@ -119,7 +119,7 @@ namespace ClassLibrary1
         #endregion
     }
     }
-```
+````
 
 6.&nbsp; Any implementation beyond this is specific to the actual Bug Tracking application you're using.
 
@@ -151,7 +151,7 @@ The **IBugTrackerConnectionUI** interface exposes additional methods to further
 
 Create another class and implement the **IBugTrackerConnectionUI** interface. Here are the definitions for each **IBugTrackerConnectionUI** member:
 
-```C#
+````C#
         public class Class3 : IBugTrackerConnectionUI
                 {
     	#region IBugTrackerConnectionUI Members
@@ -218,4 +218,4 @@ Create another class and implement the **IBugTrackerConnectionUI** interface. He
 	 
 	    #endregion
 		}
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/features/integration/bug-tracking/jira-custom-fields.md b/docs/features/integration/bug-tracking/jira-custom-fields.md
index e999eb14..52aef8be 100644
--- a/docs/features/integration/bug-tracking/jira-custom-fields.md
+++ b/docs/features/integration/bug-tracking/jira-custom-fields.md
@@ -18,12 +18,12 @@ In order to denote your required fields and what to fill them with, create a fil
 
 Open it with a text editor, like Notepad, and insert the following content:
 
-```json
+````JSON
 {
 "IssueTypeName": "Defect",
 "Fields" : {"assignee": {"name": "username" }, "labels": ["defect"],  "customfield_10401":{"required custom field": "value"}, "customfield_10402":{"another required custom field": "value"} }
 }
-```
+````
 
 In JIRA, custom fields are referenced by "customfield_" + the id of the custom field. In the above example there are two custom fields referrenced with their names and respective values. 
 
diff --git a/docs/features/integration/bug-tracking/launch-bug-dialog.md b/docs/features/integration/bug-tracking/launch-bug-dialog.md
index 6f4a375e..f2e87cb8 100644
--- a/docs/features/integration/bug-tracking/launch-bug-dialog.md
+++ b/docs/features/integration/bug-tracking/launch-bug-dialog.md
@@ -40,12 +40,16 @@ Execute a test list and drill down into the failed result.
 - Click **Submit Bug** in the **Export** ribbon.
 - Click **Submit Bug** in the **Test Results** pane.
 
-<table id="no-table">
-<tr>
-<td>![Export][4]</td>
-<td>![Test Results][5]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Export][4]</td>
+<td>
+
+![Test Results][5]</td>
 </tr>
-<table>
+</table>
 
 [1]: /img/features/integration/bug-tracking/launch-bug-dialog/fig1.png
 [2]: /img/features/integration/bug-tracking/launch-bug-dialog/step-righ-click-menu-bug.png
diff --git a/docs/features/integration/bug-tracking/tfs-custom-fields.md b/docs/features/integration/bug-tracking/tfs-custom-fields.md
index de0a5da6..d6c048cc 100644
--- a/docs/features/integration/bug-tracking/tfs-custom-fields.md
+++ b/docs/features/integration/bug-tracking/tfs-custom-fields.md
@@ -33,7 +33,7 @@ Where *BugTrackingName* is the name of the required field and *NULL* is its curr
 
 4.&nbsp; Open it with a text editor, like Notepad, and insert the following content:
 
-```xml
+````XML
 <?xml version="1.0" encoding="utf-8"?>
 <TFSMappings xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
   <TemplateName>BugNew1</TemplateName>
@@ -44,7 +44,7 @@ Where *BugTrackingName* is the name of the required field and *NULL* is its curr
     </FieldMapping>
   </Fields>
 </TFSMappings>
-```
+````
 
 5.&nbsp; Submit the bug once again through Test Studio. It should succeed:
 
diff --git a/docs/features/integration/quality-center/integration.md b/docs/features/integration/quality-center/integration.md
index 84b658ae..435d8db5 100644
--- a/docs/features/integration/quality-center/integration.md
+++ b/docs/features/integration/quality-center/integration.md
@@ -56,13 +56,13 @@ Open a File Explorer and navigate to the Test Studio installation _Bin_ sub-fold
 1. Open the file with a text editor (like Notepad++).
 1. In the _appSettings_ section add a key _ShowQCPlugin_ and set its value to true. See example below.
 
-	```
-	<appSettings>
-		<add key="CommandLineRun" value="True" />
-		<add key="PersistOnEachStep" value="False" />
-		<add key="ShowQCPlugin" value="False" />
-	</appSettings>
-	```
+````
+<appSettings>
+	<add key="CommandLineRun" value="True" />
+	<add key="PersistOnEachStep" value="False" />
+	<add key="ShowQCPlugin" value="False" />
+</appSettings>
+````
 
 1. Restart Test Studio and the QC button will be back in the _Project Ribbon_.
 
@@ -72,4 +72,3 @@ Open a File Explorer and navigate to the Test Studio installation _Bin_ sub-fold
 [4]: /img/features/integration/quality-center/integration/fig4.png
 [5]: /img/features/integration/quality-center/integration/fig5.png
 [6]: /img/features/integration/quality-center/integration/fig6.png
-[7]: /img/features/integration/quality-center/integration/fig7.png
\ No newline at end of file
diff --git a/docs/features/logical-steps/if-else.md b/docs/features/logical-steps/if-else.md
index 5ebc2d87..baf934e9 100644
--- a/docs/features/logical-steps/if-else.md
+++ b/docs/features/logical-steps/if-else.md
@@ -44,12 +44,16 @@ In this article you can find the following topics:
 
 8.&nbsp; Choose **Conditions** in the <a href="/getting-started/test-recording/step-suggestions" target="_blank">**Step Builder**</a> and add **if...else** step.
 
-<table id="no-table">
-<tr>
-<td>![Standalone][4]<br>**Standalone version**</td>
-<td>![VS Plugin][5]<br>**VS Plugin**</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Standalone][4]<br>**Standalone version**</td>
+<td>
+
+![VS Plugin][5]<br>**VS Plugin**</td>
 <tr>
-<table>
+</table>
 
 9.&nbsp; From the drop down in the IF step select the previously recorded verification.
 
diff --git a/docs/features/logical-steps/loop.md b/docs/features/logical-steps/loop.md
index fc6a980b..65fb3b10 100644
--- a/docs/features/logical-steps/loop.md
+++ b/docs/features/logical-steps/loop.md
@@ -23,12 +23,16 @@ Walk--through of creating a loop process.
 
 6.&nbsp; Choose **Conditions** in the <a href="/getting-started/test-recording/step-suggestions" target="_blank">**Step Builder**</a> and add **loop** step.
 
-<table id="no-table">
-<tr>
-<td>![Standalone][2]<br>**Standalone version**</td>
-<td>![VS Plugin][3]<br>**VS Plugin**</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Standalone][2]<br>**Standalone version**</td>
+<td>
+
+![VS Plugin][3]<br>**VS Plugin**</td>
 <tr>
-<table>
+</table>
 
 7.&nbsp; Set the *Count* of the Loop step to 5.
 
diff --git a/docs/features/logical-steps/while-loop.md b/docs/features/logical-steps/while-loop.md
index 1d5b81b9..1457c8bd 100644
--- a/docs/features/logical-steps/while-loop.md
+++ b/docs/features/logical-steps/while-loop.md
@@ -39,12 +39,16 @@ Walk--through of <a href="/features/logical-steps/while-loop#Build-a-While-loop"
 
 9.&nbsp; Choose **Conditions** in the <a href="/getting-started/test-recording/step-suggestions" target="_blank">**Step Builder**</a> and add **while...loop** step.  
 
-<table id="no-table">
-<tr>
-<td>![Standalone][4]<br>**Standalone version**</td>
-<td>![VS Plugin][5]<br>**VS Plugin**</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Standalone][4]<br>**Standalone version**</td>
+<td>
+
+![VS Plugin][5]<br>**VS Plugin**</td>
 <tr>
-<table>
+</table>
 
 10.&nbsp; Choose the verification we've already added from the dropdown of the While step.
 
diff --git a/docs/features/project-explorer/search-tests.md b/docs/features/project-explorer/search-tests.md
index 4292b830..2127209c 100644
--- a/docs/features/project-explorer/search-tests.md
+++ b/docs/features/project-explorer/search-tests.md
@@ -3,7 +3,7 @@ title: Search And Filter Tests
 page_title: Search And Filter Tests
 description: "Search for a test in Test Studio. Filter tests containing a key word in Test Studio."
 previous_url: /features/test-maintenance/search-tests
-publish: true
+published: true
 position: 1
 ---
 # Search Project Tests
diff --git a/docs/features/project-settings/general.md b/docs/features/project-settings/general.md
index a33f7e04..96e7836c 100644
--- a/docs/features/project-settings/general.md
+++ b/docs/features/project-settings/general.md
@@ -44,9 +44,5 @@ This property is useful for large projects, which contain multiple tests. If ena
 
 This property allows you to bring up the project in the same state when it was last closed. If enabled, by next launch of the project, any tests and code files not closed, will be automatically opened.
 
-## SL Connect Timeout
-
-The amount of time in milliseconds to wait for Test Studio to connect to a Silverlight application.
 
 [1]: /img/features/project-settings/general/fig1.png
-[2]: /img/features/project-settings/general/fig2.png
diff --git a/docs/features/project-settings/overview.md b/docs/features/project-settings/overview.md
index 021d343c..d85ce9e2 100644
--- a/docs/features/project-settings/overview.md
+++ b/docs/features/project-settings/overview.md
@@ -14,12 +14,16 @@ Use the **Project Settings** to configure how tests are recorded, fine tune how
 
 On the **Project** ribbon in Test Studio Standalone version find the **Settings** button which opens the Project Settings window. In the Visual Studio plugin, the gear icon in the toolbar loads the same Project Settings window.
 
-<table id="no-table">
-<tr>
-<td>![Standalone][1]<br>**Standalone version**</td>
-<td>![VS Plugin][2]<br>**VS Plugin**</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Standalone][1]<br>**Standalone version**</td>
+<td>
+
+![VS Plugin][2]<br>**VS Plugin**</td>
 <tr>
-<table>
+</table>
 
 The available settings are divided in few areas:
 
diff --git a/docs/features/project-settings/theme.md b/docs/features/project-settings/theme.md
index fa460a57..d0f2cf98 100644
--- a/docs/features/project-settings/theme.md
+++ b/docs/features/project-settings/theme.md
@@ -13,52 +13,76 @@ The default theme of Test Studio is **Light**. You can change it to **Dark** and
 The screenshots below show different views from Test Studio in both themes.
 
 Project theme settings
-<table id="no-table">
-<tr>
-<td>![Light Settings][1]</td>
-<td>![Dark Settings][2]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light Settings][1]</td>
+<td>
+
+![Dark Settings][2]</td>
 </tr>
-<table>
+</table>
 
 Test Studio Welcome screen
-<table id="no-table">
-<tr>
-<td>![Light Welcome][3]</td>
-<td>![Dark Welcome][4]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light Welcome][3]</td>
+<td>
+
+![Dark Welcome][4]</td>
 </tr>
-<table>
+</table>
 
 Test Studio test development
-<table id="no-table">
-<tr>
-<td>![Light Test Studio][5]</td>
-<td>![Dark Test Studio][6]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light Test Studio][5]</td>
+<td>
+
+![Dark Test Studio][6]</td>
 </tr>
-<table>
+</table>
 
 Test Studio Test Runner
-<table id="no-table">
-<tr>
-<td>![Light Test Runner][7]</td>
-<td>![Dark Test Runner][8]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light Test Runner][7]</td>
+<td>
+
+![Dark Test Runner][8]</td>
 </tr>
-<table>
+</table>
 
 Schedule a test list for remote execution
-<table id="no-table">
-<tr>
-<td>![Light TestList][9]</td>
-<td>![Dark TestList][10]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light TestList][9]</td>
+<td>
+
+![Dark TestList][10]</td>
 </tr>
-<table>
+</table>
 
 Visual Studio integration with matching theme colors
-<table id="no-table">
-<tr>
-<td>![Light Visual Studio][11]</td>
-<td>![Dark Visual Studio][12]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![Light Visual Studio][11]</td>
+<td>
+
+![Dark Visual Studio][12]</td>
 </tr>
-<table>
+</table>
 
 [1]: /img/features/project-settings/theme/fig1.png
 [2]: /img/features/project-settings/theme/fig2.png
diff --git a/docs/features/project-settings/translators.md b/docs/features/project-settings/translators.md
index f2d93c88..09a68109 100644
--- a/docs/features/project-settings/translators.md
+++ b/docs/features/project-settings/translators.md
@@ -1,7 +1,7 @@
 ---
 title: Translators Project Settings
 page_title: Translators Project Settings
-description: "Test Studio comes with built-in translators for the Telerik components. Test Studio provides Basic translators for HTML, Silverlight, and WPF, and translators built specifically for Telerik AJAX and Silverlight RadControls, KendoUI for jQuery and KendoUI for Angular, Telerik UI for Blazor"
+description: "Test Studio comes with built-in translators for the Telerik components. Test Studio provides Basic translators for HTML, and WPF, and translators built specifically for Telerik AJAX and RadControls, KendoUI for jQuery and KendoUI for Angular, Telerik UI for Blazor"
 position: 8
 ---
 # Translators Project Settings
@@ -14,756 +14,203 @@ This section of the <a href="/features/project-settings/overview" target="_blank
 
 ![Translators Project Settings][1]
 
+<!-- no toc -->
+- [Choose the correct version of translators used in the tested application](#select-the-version-of-the-telerik-components-under-test)
+- [How to find out which is the correct version](#how-to-know-which-is-the-version-of-components-used-in-the-tested-page)
+- [Mapping of translators versions to the Test Studio releases](#test-studio-mapping-to-ui-components-versions)
+- [Find out which components are covered by translators in Test Studio](#available-translators)
+
 ## Select the Version of the Telerik Components under Test
 
 The __Telerik Components Under Test__ section lets you instruct the translators' version to match the version of the UI components in the tested page for this project. This setting applies to both the <a href="/automated-tests/recording/recording-telerik-kendo-ui-components" target="_blank">recording</a> and quick execution flows and allows you to smoothly create tests and run these for various applications. The same setting is exposed in the <a href="/features/test-lists/test-list-settings" target="_blank">test list settings</a> and can be set individually per test list.
 
 ![Telerik Components Under Test Version][2]
 
-### How to Know Which is the Version of Components Used in the Tested Page?
+> __Note!__
+> <br> 
+> __Test Studio supports the latest version of Telerik and Kendo UI components, as well as versions released within the past two years__.
+> <br>
+> <br>
+> All previous versions are marked with __*__ to indicate these are no longer supported. You can continue using these archived versions but in case any misbehavior is identified it will not be addressed. 
+
+## How to Know Which is the Version of Components Used in the Tested Page?
 
 As Quality Assurance Engineer you often don't know what type and version of UI components was used to create the application you need to automate. And since there is no convenient way to identify the version of the components in an already built and deployed application, the __most reliable approach is to contact the development team__ and discuss the topic internally.
 
-### Test Studio Mapping to UI Components Versions
-
-In the below grid you can find the versions of the supported UI components matching the translators versions from the list.
-
-<p id="Blazor">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Telerik UI for Blazor<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2.27.0</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">3.0.0</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">3.1.0</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">3.3.0</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">3.4.0</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">3.6.0</td>
-        </tr>
-        <tr>
-            <td>R12023</td>
-            <td colspan="6" style="text-align:center;">4.0.0</td>
-        </tr>
-        <tr>
-            <td>R12023SP1</td>
-            <td colspan="6" style="text-align:center;">4.1.0</td>
-        </tr>
-        <tr>
-            <td>R22023</td>
-            <td colspan="6" style="text-align:center;">4.3.0</td>
-        </tr>
-        <tr>
-            <td>R32023</td>
-            <td colspan="6" style="text-align:center;">4.6.0</td>
-        </tr>
-        <tr>
-            <td>R22024</td>
-            <td colspan="6" style="text-align:center;">6.0.0</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-
-<p id="asp.net ajax">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Telerik UI for ASP.NET AJAX<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2021.3.914</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">2022.1.119</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.1.302</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">2022.2.511</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.2.622</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">2022.3.913</td>
-        </tr>
-        <tr>
-            <td>R12023</td>
-            <td colspan="6" style="text-align:center;">2023.1.117</td>
-        </tr>
-        <tr>
-            <td>R12023SP1</td>
-            <td colspan="6" style="text-align:center;">2023.1.314</td>
-        </tr>
-        <tr>
-            <td>R22023</td>
-            <td colspan="6" style="text-align:center;">2023.2.606</td>
-        </tr>
-        <tr>
-            <td>R32023</td>
-            <td colspan="6" style="text-align:center;">2023.3.1010</td>
-        </tr>
-        <tr>
-            <td>R22024</td>
-            <td colspan="6" style="text-align:center;">2024.2.513</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-
-<p id="jQuery">
-<table class="Tbl k-table">
-    <colgroup>
-        <col width="50%" />
-        <col width="50%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="6" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Kendo UI for jQuery<td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr>
-            <td>R32021</td>
-            <td colspan="6" style="text-align:center;">2021.3.914</td>
-        </tr>
-        <tr>
-            <td>R12022</td>
-            <td colspan="6" style="text-align:center;">2022.1.119</td>
-        </tr>
-        <tr>
-            <td>R12022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.1.301</td>
-        </tr>
-        <tr>
-            <td>R22022</td>
-            <td colspan="6" style="text-align:center;">2022.2.510</td>
-        </tr>
-        <tr>
-            <td>R22022SP1</td>
-            <td colspan="6" style="text-align:center;">2022.2.621</td>
-        </tr>
-        <tr>
-            <td>R32022</td>
-            <td colspan="6" style="text-align:center;">2022.3.913</td>
-        </tr>
-        <tr>
-            <td>R12023</td>
-            <td colspan="6" style="text-align:center;">2023.1.117</td>
-        </tr>
-        <tr>
-            <td>R12023SP1</td>
-            <td colspan="6" style="text-align:center;">2023.1.314</td>
-        </tr>
-        <tr>
-            <td>R22023</td>
-            <td colspan="6" style="text-align:center;">2023.2.606</td>
-        </tr>
-        <tr>
-            <td>R32023</td>
-            <td colspan="6" style="text-align:center;">2023.3.1010</td>
-        </tr>
-        <tr>
-            <td>R22024</td>
-            <td colspan="6" style="text-align:center;">2024.2.514</td>
-        </tr>
-    </tbody>
-</table>
-</p>
-<p>
-
-<script type="text/javascript">
-        function showHideRowAngList(row) {
-            $("#" + row).toggle();
-            $('#expand'+row[row.length-1]).text(function (i, oldText) {
-        return $.trim(oldText) == 'Click to expand the list of translators' ? 'Collapse' : 'Click to expand the list of translators';
-		});
-        }
-</script>
-
-<style>
-    #Angular .hidden_row {
-            display: none;
-        }
-</style>
-
-<p id="Angular">
-<table class="Tbl k-table" id="Angular">
-    <colgroup>
-        <col width="30%" />
-        <col width="70%" />
-    </colgroup>
-    <thead>
-        <tr>
-			<td colspan="2" style="color:white;text-align:center;background-color:#70757d;font-weight:bold;text-align:left;">Kendo UI for Angular</td>
-        </tr>
-    </thead>
-    <tbody>
-        <tr onclick="showHideRowAngList('hidden_row1');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R32021</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand1">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row1" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">5.1.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>                        
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">5.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">7.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">1.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">7.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.3.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">5.1.1</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRowAngList('hidden_row2');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R12022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand2">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row2" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">3.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.4.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.0</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRowAngList('hidden_row3');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R12022SP1</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand3">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row3" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">7.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">6.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">6.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.7</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">3.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.5.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">8.0.7</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">6.5.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">6.0.2</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRowAngList('hidden_row4');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R22022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand4">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row4" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.0.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.0.0</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRowAngList('hidden_row5');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R22022SP1</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand5">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row5" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.0.2</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">9.0.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.2</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr onclick="showHideRowAngList('hidden_row6');">
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;">R32022</td>
-            <td style="color:white;text-align:center;background-color:#9ca3ad;font-weight:bold;text-align:left;cursor: pointer;"><span id="expand6">Click to expand the list of translators</span></td>
-        </tr>
-        <tr id="hidden_row6" class="hidden_row">
-            <td colspan=4>
-                <table>
-                    <colgroup>
-                        <col width="33%" />
-                        <col width="34%" />
-                        <col width="33%" />
-                    </colgroup>
-                    <thead>
-                        <tr>
-                            <td style="font-weight:bold;text-align:left;">Translator Name</td>
-                            <td style="font-weight:bold;text-align:left;">Component Name</td>
-                            <td style="font-weight:bold;text-align:center;">Component Version</td>
-                        </tr>
-                    </thead>
-                    <tbody>
-                        <tr>
-                            <td>KendoAngularAutoComplete</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                            <td>KendoAngularButton</td>
-                            <td>kendo-angular-buttons</td>
-                            <td colspan="6" style="text-align:center;">8.1.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularComboBox</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDialog</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularDropdownList</td>
-                            <td>kendo-angular-dropdowns</td>
-                            <td colspan="6" style="text-align:center;">7.2.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularGrid</td>
-                            <td>kendo-angular-grid</td>
-                            <td colspan="6" style="text-align:center;">7.3.1</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularInputs</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">10.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPager</td>
-                            <td>kendo-angular-pager</td>
-                            <td colspan="6" style="text-align:center;">4.0.5</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularPanelBar</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularSwitch</td>
-                            <td>kendo-angular-inputs</td>
-                            <td colspan="6" style="text-align:center;">10.0.0</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularTabStrip</td>
-                            <td>kendo-angular-layout</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                        <tr>
-                            <td>KendoAngularWindow</td>
-                            <td>kendo-angular-dialog</td>
-                            <td colspan="6" style="text-align:center;">7.1.3</td>
-                        </tr>
-                    </tbody>
-                </table>
-            </td>
-        </tr>
-        <tr>
-            <td>R12023</td>
-            <td colspan="6" style="text-align:center;">11.0.0</td>
-        </tr>
-        <tr>
-            <td>R12023SP1</td>
-            <td colspan="6" style="text-align:center;">11.4.0</td>
-        </tr>
-        <tr>
-            <td>R22023</td>
-            <td colspan="6" style="text-align:center;">13.0.0</td>
-        </tr>
-        <tr>
-            <td>R32023</td>
-            <td colspan="6" style="text-align:center;">14.0.0</td>
-        </tr>
-        <tr>
-            <td>R22024</td>
-            <td colspan="6" style="text-align:center;">16.0.0</td>
-        </tr>
-    </tbody>
-</table>
-</p>
+## Test Studio Mapping to UI Components Versions
+
+Find the versions of the supported UI components matching the translators versions from the lists.
+
+## Telerik UI for Blazor
+
+| Release    | Version  |
+|------------|----------|
+| R32021     | 2.27.0   |
+| R12022     | 3.0.0    |
+| R12022SP1  | 3.1.0    |
+| R22022     | 3.3.0    |
+| R22022SP1  | 3.4.0    |
+| R32022     | 3.6.0    |
+| R12023     | 4.0.0    |
+| R12023SP1  | 4.1.0    |
+| R22023     | 4.3.0    |
+| R32023     | 4.6.0    |
+| R22024     | 6.0.0    |
+| R22024SP1  | 6.0.2    |
+| R42024     | 7.0.0    |
+| R22025     | 9.0.0    |
+
+## Telerik UI for ASP.NET AJAX
+
+| Release    | Version      |
+|------------|--------------|
+| R32021     | 2021.3.914   |
+| R12022     | 2022.1.119   |
+| R12022SP1  | 2022.1.302   |
+| R22022     | 2022.2.511   |
+| R22022SP1  | 2022.2.622   |
+| R32022     | 2022.3.913   |
+| R12023     | 2023.1.117   |
+| R12023SP1  | 2023.1.314   |
+| R22023     | 2023.2.606   |
+| R32023     | 2023.3.1010  |
+| R22024     | 2024.2.513   |
+| R22024SP1  | 2024.3.805   |
+| R42024     | 2024.4.1113  |
+| R22025     | 2025.2.528   |
+
+## Kendo UI for jQuery
+
+| Release    | Version      |
+|------------|--------------|
+| R32021     | 2021.3.914   |
+| R12022     | 2022.1.119   |
+| R12022SP1  | 2022.1.301   |
+| R22022     | 2022.2.510   |
+| R22022SP1  | 2022.2.621   |
+| R32022     | 2022.3.913   |
+| R12023     | 2023.1.117   |
+| R12023SP1  | 2023.1.314   |
+| R22023     | 2023.2.606   |
+| R32023     | 2023.3.1010  |
+| R22024     | 2024.2.514   |
+| R22024SP1  | 2024.2.514   |
+| R42024     | 2024.4.1112  |
+| R22025     | 2025.2.528   |
+
+## Kendo UI for Angular
+
+| Release R32021           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 6.3.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 5.1.1             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 5.4.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 5.4.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 7.4.0             |
+| KendoAngularPager        | kendo-angular-pager        | 1.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.3.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 7.4.0             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.3.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 5.1.1             |
+
+| Release R12022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 7.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 6.0.0             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 6.0.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 6.0.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 8.0.0             |
+| KendoAngularPager        | kendo-angular-pager        | 3.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.4.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 8.0.0             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.4.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 6.0.0             |
+
+| Release R12022SP1        |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularButton       | kendo-angular-buttons      | 7.0.3             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularDialog       | kendo-angular-dialog       | 6.0.2             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 6.0.1             |
+| KendoAngularGrid         | kendo-angular-grid         | 6.1.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 8.0.7             |
+| KendoAngularPager        | kendo-angular-pager        | 3.0.2             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 6.5.1             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 8.0.7             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 6.5.1             |
+| KendoAngularWindow       | kendo-angular-dialog       | 6.0.2             |
+
+| Release R22022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.0.0             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.0.1             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.0.1             |
+| KendoAngularInputs       | kendo-angular-inputs       | 9.0.1             |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.0.1             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 9.0.1             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.0.1             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.0.0             |
+
+| Release R22022SP1        |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.0.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.1.2             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.0.2             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.2.0             |
+| KendoAngularInputs       | kendo-angular-inputs       | 9.0.3             |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.0             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.1.0             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 9.0.3             |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.1.0             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.1.2             |
+
+| Release R32022           |                            |                   |
+|--------------------------|----------------------------|-------------------|
+| **Translator Name**      | **Component Name**         | **Component Version** |
+| KendoAngularAutoComplete | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularButton       | kendo-angular-buttons      | 8.1.0             |
+| KendoAngularComboBox     | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularDialog       | kendo-angular-dialog       | 7.1.3             |
+| KendoAngularDropdownList | kendo-angular-dropdowns    | 7.2.0             |
+| KendoAngularGrid         | kendo-angular-grid         | 7.3.1             |
+| KendoAngularInputs       | kendo-angular-inputs       | 10.0.0            |
+| KendoAngularPager        | kendo-angular-pager        | 4.0.5             |
+| KendoAngularPanelBar     | kendo-angular-layout       | 7.1.3             |
+| KendoAngularSwitch       | kendo-angular-inputs       | 10.0.0            |
+| KendoAngularTabStrip     | kendo-angular-layout       | 7.1.3             |
+| KendoAngularWindow       | kendo-angular-dialog       | 7.1.3             |
+
+| Release    | Version  |
+|------------|----------|
+| R12023     | 11.0.0   |
+| R12023SP1  | 11.4.0   |
+| R22023     | 13.0.0   |
+| R32023     | 14.0.0   |
+| R22024     | 16.0.0   |
+| R22024SP1  | 16.3.0   |
+| R42024     | 17.0.1   |
+| R22025     | 19.1.0   |
+
 
 ## Available Translators
 
-The __Available Translators__ section lists __all built-in translators__ that are currently available in Test Studio. All translators are enabled by default, which is the __recommended setup__. Each of the built-in translators can be disabled and not used while recording and executing tests, but we strongly recommend contacting the Test Studio Support Team before  applying changes to the enabled translators.
+The __Available Translators__ section lists __all built-in translators__ that are currently available in Test Studio. All translators are enabled by default, which is the __recommended setup__. Each of the built-in translators can be disabled and not used while recording and executing tests, but we strongly recommend contacting the Test Studio Support Team before applying changes to the enabled translators.
 
 ![Available Translators][3]
 
diff --git a/docs/features/recorder/advanced-recording-tools/dom-explorer.md b/docs/features/recorder/advanced-recording-tools/dom-explorer.md
index 7a8c9510..d7cfeb58 100644
--- a/docs/features/recorder/advanced-recording-tools/dom-explorer.md
+++ b/docs/features/recorder/advanced-recording-tools/dom-explorer.md
@@ -18,7 +18,7 @@ Find further details about the DOM Explorer functions:
 - [Searching with RegEx](#regular-expressions)
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Toolbar Options
diff --git a/docs/features/recorder/advanced-recording-tools/element-steps/steps-overview.md b/docs/features/recorder/advanced-recording-tools/element-steps/steps-overview.md
index 41acdad1..f4e3b707 100644
--- a/docs/features/recorder/advanced-recording-tools/element-steps/steps-overview.md
+++ b/docs/features/recorder/advanced-recording-tools/element-steps/steps-overview.md
@@ -60,7 +60,7 @@ Verifications in Test Studio allow you to:
 - Build these measurements in an interactive manner without code.
 - Detect if elements are in a particular state (e.g. is visible, exists).
 - Detect if attributes and properties compare with specific values.
-- Verify content, attributes, images, image texts, styles, visibility, drop-down list selections, checkboxes, radio buttons, tables and Silverlight property values.
+- Verify content, attributes, images, image texts, styles, visibility, drop-down list selections, checkboxes, radio buttons, tables and property values.
 
 Test Studio implements verification through "sentences" that compare a portion of an element to a value, such as:
 
diff --git a/docs/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification.md b/docs/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification.md
index f8d8d912..e4c2a3d8 100644
--- a/docs/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification.md
+++ b/docs/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification.md
@@ -9,7 +9,7 @@ position: 4
 You can build an image verification against specific elements for pixel-by-pixel visual verifications in tests. The image verification feature is based on an element’s visual rendering rather than the properties or attributes of that element. An application with rich graphic rendering can leverage this functionality to automate some of its test scenarios that have always needed manual visual inspection to verify. The image verification in Test Studio allows you to refine your verification area down to the pixel level within an element and also assign a threshold for the matching.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Best practices
diff --git a/docs/features/recorder/compact-recording-toolbar.md b/docs/features/recorder/compact-recording-toolbar.md
index bf9fe6a2..73f7ece2 100644
--- a/docs/features/recorder/compact-recording-toolbar.md
+++ b/docs/features/recorder/compact-recording-toolbar.md
@@ -24,7 +24,7 @@ Place the mouse cursor over the dots in the left or top of the __Recording Toolb
 
 ![Move Compact Recording Toolbar][1]
 
-## Enable Hover Over Highlighting ##
+## Enable Hover Over Highlighting 
 
 ![Enable Highlighting Button][2]
 
@@ -36,7 +36,7 @@ Place the mouse cursor over the dots in the left or top of the __Recording Toolb
 >
 > The __keyboard shortcut to toggle the highlighting on or off is the *Pause/Break* key__. It can be helpful in situation when you need to keep the focus on the hovered element.
 
-## Pause/Resume Recording Mode ##
+## Pause/Resume Recording Mode 
 
 Once the **Compact Recording Toolbar** is attached to the tested application, it is in active recording mode and has a red border all around. You can pause the recording, by pressing the **Pause** button.
 
@@ -50,7 +50,7 @@ When in paused mode, you see the **Record** button which allows you to return to
 >
 > The __keyboard shortcut to pause or resume the recording is the *Print Screen* key__.
 
-## Advanced Recording Tools ##
+## Advanced Recording Tools 
 
 ![Show Advanced Recording Tools][10]
 
@@ -58,25 +58,29 @@ From the **Compact Recording Toolbar** you can also access the <a href="/feature
 
 ![Advanced Recording Tools][11]
 
-## Toolbar Orientation ##
+## Toolbar Orientation 
 
 Choose between vertical and horizontal **Compact Recording Toolbar** and move it around inside or outside the tested application.
 
-<table id=no-table>
-	<tr>
-		<td>![Horizontal Toolbar][12]</td>
-		<td>![Vertical Toolbar][13]</td>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Horizontal Toolbar][12]</td>
+<td>
+
+![Vertical Toolbar][13]</td>
 	</tr>
-<table>
+</table>
 
 [1]: /img/features/recorder/compact-recording-toolbar/anim1.gif
 [1a]: /img/features/recorder/compact-recording-toolbar/fig1.png
 [2]: /img/features/recorder/compact-recording-toolbar/fig2.png
 [3]: /img/features/recorder/compact-recording-toolbar/fig3.png
-[4]: /img/features/recorder/compact-recording-toolbar/fig4.png
-[5]: /img/features/recorder/compact-recording-toolbar/fig5.png
-[6]: /img/features/recorder/compact-recording-toolbar/fig6.png
-[7]: /img/features/recorder/compact-recording-toolbar/fig7.png
+
+
+
+
 [8]: /img/features/recorder/compact-recording-toolbar/fig8.png
 [9]: /img/features/recorder/compact-recording-toolbar/fig9.png
 [10]: /img/features/recorder/compact-recording-toolbar/fig10.png
diff --git a/docs/features/recorder/highlighting-menu/quick-steps/extraction.md b/docs/features/recorder/highlighting-menu/quick-steps/extraction.md
index 3d7ff939..dd5b7a18 100644
--- a/docs/features/recorder/highlighting-menu/quick-steps/extraction.md
+++ b/docs/features/recorder/highlighting-menu/quick-steps/extraction.md
@@ -114,4 +114,3 @@ The implementation of verification steps allows you to convert any text based ch
 [6]: /img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig6.png
 [7]: /img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig7.png
 [8]: /img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig8.png
-[9]: /img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig9.png
diff --git a/docs/features/recorder/test-recorder.md b/docs/features/recorder/test-recorder.md
deleted file mode 100644
index 1c99e426..00000000
--- a/docs/features/recorder/test-recorder.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: Test Recorder
-page_title: Test Recorder
-description: "Overview of the recording feature in Test Studio. Codeless test step recording. Automate test scenarios without code. Codeless automation."
-position: 10
-publish: false
----
-
-# Test Recorder #
-
-The **Test Recorder** is a powerful feature in Test Studio. You can use it to built codeless tests with common actions and verifications or more advanced steps against a specific element in the DOM tree. All that functionality comes in a compact and customizable recorder, which is attached to the browser or WPF application. The recorded steps have a lot of configurations to help you automate your application without writing code.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-In this section you will learn in details about all features of the Test Studio Recorder. How to start it and how it can help you automate your application with stable and reliable tests. 
-
-## Start Recording ##
-
-There are two ways to initiate recording. You can either launch a new browser or WPF app instance with the compact recording toolbar attached, or you can attach the compact recording toolbar to an existing instance (applicable for IE only or WPF application). 
-
-> **Note**
->
-> To stop the recording session, close the browser or WPF application.
-
-### Launch New Recording ###
-
-1.&nbsp;  Open the test by double clicking on it. Click the **Record** button in the **Tests** tab or press **CTRL+R**.
-
-<table id=no-table>
-	<tr>
-		<td>![Test Studio][1] <br><br>**Standalone version**</td>
-		<td>![VS][2] <br><br>**VS plugin**</td>
-	</tr>
-<table>
-
-2.&nbsp; Type the URL you want to navigate to or select it from recent URLs. Choose the recording browser (for web tests) and press Enter or the *Record* button in that window.
-
-![Choose browser][3]
-
-If you enable **Save my choice for the future** or set a preferred browser from the <a href="/general-information/test-execution/quick-execution#preferred-browser" target="_blank">Test ribbon</a> the **Record** button will display the icon for the selected browser.
-
-![Choose preferred browser][4]
-
-3.&nbsp; Once the selected browser navigates to the specified URL or the WPF application is started, the <a href="/features/recorder/compact-recording-toolbar" target="_blank">**Compact Recording Toolbar**</a> will attach to it. A navigate step is added in the Steps pane and you can continue recording the next actions as per the required scenario.
-
-![Attached recorder][5]
-
-> **Note**
-> <br>
-> Once a recording session is started **do not start another instance of the same browser or WPF application** until the session is finished!
-
-### Attach to Existing Instance (Applicable for IE or WPF Application) ###
-
-Click the drop-down arrow on the **Record** button to see a list of available IE browser instances or WPF applications. Select one to attach the recorder to that instance.
-
-<table id=no-table>
-	<tr>
-		<td>![Attach to running browser][6] <br><br>**Web Test - Internet Explorer only**</td>
-		<td>![Attach to running WPF instance][7] <br><br>**WPF Test - connect to running WPF application instance**</td>
-	</tr>
-<table>
-
-## See also ##
-
-* <a href="/features/recorder/compact-recording-toolbar" target="_blank">Compact Recording Toolbar</a>
-
-[1]: /img/general-information/test-recording/overview/fig1.png
-[2]: /img/general-information/test-recording/overview/fig2.png
-[3]: /img/general-information/test-recording/overview/fig3.png
-[4]: /img/general-information/test-recording/overview/fig4.png
-[5]: /img/general-information/test-recording/overview/fig5.png
-[6]: /img/features/recorder/test-recorder/fig6.png
-[7]: /img/features/recorder/test-recorder/fig7.png
diff --git a/docs/features/recorder/translators.md b/docs/features/recorder/translators.md
index 86d6dada..39aee02c 100644
--- a/docs/features/recorder/translators.md
+++ b/docs/features/recorder/translators.md
@@ -11,11 +11,13 @@ Test Studio comes with __dedicated support for the Telerik and Kendo UI componen
 
 You can read further about the built-in translators in this article.
 
-- [What Are the Built-in Test Studio Translators?](#what-are-the-built-in-test-studio-translators)
-- [When Do I Need to Use the Translators?](#when-do-i-need-to-use-the-translators)
-- [How Can I Use the Built-in Translators?](#how-can-i-use-the-built-in-translators)
-- [Which Telerik and Kendo UI Components are Supported?](#which-telerik-and-kendo-ui-components-are-supported)
-- [What Is the Translators Versioning and Which Option Should I Choose?](#what-is-the-translators-versioning-and-which-option-should-i-choose)
+- [Test Studio Built-In Translators for Telerik and Kendo UI](#test-studio-built-in-translators-for-telerik-and-kendo-ui)
+  - [What Are the Built-in Test Studio Translators?](#what-are-the-built-in-test-studio-translators)
+  - [When Do I Need to Use the Translators?](#when-do-i-need-to-use-the-translators)
+  - [How Can I Use the Built-in Translators?](#how-can-i-use-the-built-in-translators)
+  - [Which Telerik and Kendo UI Components are Supported?](#which-telerik-and-kendo-ui-components-are-supported)
+  - [What Is the Translators Versioning and Which Option Should I Choose?](#what-is-the-translators-versioning-and-which-option-should-i-choose)
+  - [See Also](#see-also)
 
 ## What Are the Built-in Test Studio Translators?
 
@@ -42,7 +44,7 @@ Examples are:
 
 ## Which Telerik and Kendo UI Components are Supported?
 
-Test Studio comes with basic translators for __HTML, Silverlight and WPF__, and exclusively  built translators for __Telerik AJAX and Silverlight components, Telerik UI for Blazor, Kendo UI for Angular and Kendo UI for jQuery__. These translators have a ”base” or ”generic” group of intrinsic translators that are used whenever a more specific translator is not available.
+Test Studio comes with basic translators for __HTML and WPF__, and exclusively  built translators for __Telerik AJAX, Telerik UI for Blazor, Kendo UI for Angular and Kendo UI for jQuery__ components. These translators have a ”base” or ”generic” group of intrinsic translators that are used whenever a more specific translator is not available.
 
 A list of all supported components can be found in the <a href="/features/project-settings/Translators" target="_blank">Project Settings -> Translators</a> dialog. The translators for all components are enabled by default. You can choose to disable a specific translator, or a group of translators, but this is not a recommended practice if not advised otherwise by the Test Studio Support Team.
 
@@ -57,6 +59,3 @@ The 2022 releases of the Telerik and Kendo UI components introduced significant
 ## See Also
 
 * <a href="https://www.telerik.com/blogs/automated-testing-of-kendo-ui-made-easy" target="_blank">Automated Testing for Kendo UI Made Easy</a>.
-
-[1]: /img/features/recorder/translators/fig1.png
-[2]: /img/features/recorder/translators/fig2.png
diff --git a/docs/features/test-lists/create-test-lists.md b/docs/features/test-lists/create-test-lists.md
index 8d2676f7..49699289 100644
--- a/docs/features/test-lists/create-test-lists.md
+++ b/docs/features/test-lists/create-test-lists.md
@@ -109,9 +109,9 @@ Once you have created a test list, you can <a href="/automated-tests/test-lists/
 [1]: /img/features/test-lists/create-test-list/fig1.png
 [2]: /img/features/test-lists/create-test-list/fig2.png
 [2a]: /img/features/test-lists/create-test-list/fig2a.png
-[3]: /img/features/test-lists/create-test-list/fig3.png
-[4]: /img/features/test-lists/create-test-list/fig4.png
-[5]: /img/features/test-lists/create-test-list/fig5.png
+
+
+
 [6]: /img/features/test-lists/create-test-list/fig6.png
 [7]: /img/features/test-lists/create-test-list/fig7.png
 [8]: /img/features/test-lists/create-test-list/fig8.png
diff --git a/docs/features/test-lists/test-list-settings.md b/docs/features/test-lists/test-list-settings.md
index f123b546..4a10f1bb 100644
--- a/docs/features/test-lists/test-list-settings.md
+++ b/docs/features/test-lists/test-list-settings.md
@@ -84,7 +84,7 @@ All settings are listed below with additional details on their usage.
 	* **UseBrowserExtension** - enable or disable using browser extension (for Chrome and Edge browsers).
 	* **WebComponents** - enable or disable WebComponents support. When creating a test list, the setting gets the value set on project level in the <a href="/features/project-settings/general#web-components" target="_blank">Project Settings General tab</a>. After that the setting is independent from the project level setting.
 * ***HttpProxy***
-	* **UseHttpProxy** - whether to use the built-in HTTP proxy during automation. Enabling Silverlight will automatically enable the HTTP proxy.
+	* **UseHttpProxy** - whether to use the built-in HTTP proxy during automation. 
 * ***Log***
 	* **EnableScriptLogging** - whether to enable script logging.
 	* **VerboseHttpProxy** - whether the HTTP proxy produces a high level of tracing output.
@@ -92,10 +92,7 @@ All settings are listed below with additional details on their usage.
 	* **ExecutingBrowsers** - Select the browsers against which you will execute the test list. Supported in Test Studio Standalone version only.
 * ***Navigation***
 	* **BaseUrl** - The BaseURL to use for all NavigateTo commands. When set, NavigateTo steps should use a relative URL (i.e. "~/default.aspx").
-* ***Silverlight***
-	* **EnableSilverlight** - whether to enable Silverlight automation. Enabling Silverlight will automatically enable the HTTP proxy.
-	* **SilverlightApplicationPath** - the web address or local directory from which to load a Silverlight application.
-	* **SilverlightConnectTimeout** - the amount of time to wait for a Silverlight application to load before timing out.
+
 
 ## WPF Tab
 
diff --git a/docs/features/test-maintenance/test-properties-standalone.md b/docs/features/test-maintenance/test-properties-standalone.md
index 9d13dbc8..022e1586 100644
--- a/docs/features/test-maintenance/test-properties-standalone.md
+++ b/docs/features/test-maintenance/test-properties-standalone.md
@@ -17,7 +17,6 @@ Go the **Project Tab**, click on a test and the pane to the right will instantly
 - **BrowserType** - sets the browser the test executes on. Overrides the Settings.DefaultBrowser.
 - **DisableDialogMonitoring** - whether to disable dialog monitoring and handling.
 - **ReuseAppWindow** - useful in data-driven execution to define the number of iterations to reuse the application window. By default ('0') keeps the same application open during the entire test run.
-- **SilverlightEnabled** - whether to enable Silverlight automation for this test case.
 - **StopTestListOnFailure** - gets or sets whether to stop test list execution if this test fails.
 - **WebKitExecutionDelay** - explicit commands delay in milliseconds for the WebKit browsers (Safari & Chrome).
 
diff --git a/docs/features/test-maintenance/test-properties-vs.md b/docs/features/test-maintenance/test-properties-vs.md
index 14db04fd..67d5fd64 100644
--- a/docs/features/test-maintenance/test-properties-vs.md
+++ b/docs/features/test-maintenance/test-properties-vs.md
@@ -4,9 +4,9 @@ page_title: Test Properties (VS Plugin)
 description: "Test Studio Test Properties in Visual Studio Plugin"
 position: 1
 ---
-# Test Properties (VS Plugin) #
+# Test Properties (VS Plugin) 
 
-## 2017 R2 Version or Later ##
+## 2017 R2 Version or Later 
 
 <a href="/features/test-maintenance/test-properties-standalone" target="_blank">Test properties</a> can be reviewed from a button in the test ribbon as shown on the following screenshot.
 
@@ -19,7 +19,6 @@ Here are the test properties with a brief description of each:
 - **BrowserType** - sets the browser the test executes on. Overrides the Settings.DefaultBrowser.
 - **DisableDialogMonitoring** - whether to disable dialog monitoring and handling.
 - **ReuseAppWindow** - useful in data-driven execution to define the number of iterations to reuse the application window. By default ('0') keeps the same application open during the entire test run.
-- **SilverlightEnabled** - whether to enable Silverlight automation for this test case.
 - **StopTestListOnFailure** - gets or sets whether to stop test list execution if this test fails.
 - **WebKitExecutionDelay** - explicit commands delay in milliseconds for the WebKit browsers (Safari & Chrome).
 
@@ -60,9 +59,9 @@ Here are the test properties with a brief description of each:
 
 > *Indicates field is read-only.
 
-## 2017 R1 Version and Earlier ##
+## 2017 R1 Version and Earlier 
 
-### Visual Studio 2012 ###
+### Visual Studio 2012 
 
 1. <a href="/getting-started/test-execution/visual-studio-2012-and-later-test-list" target="_blank">Create a **.vsmdi** file.</a>
 
@@ -96,7 +95,6 @@ Here are the test properties with a brief description of each:
 - Project - test project that contains this test.
 - Project Area - nod in the team project hierarchy to which this test belongs.
 - Project Relative Path - path on disk to the project file, relative to the solution.
-- SilverlightEnabled - enabled Silverlight automation on this test.
 - Solution - solution that contains the test project to which this test belongs.
 - Test Categories - list of test categories assigned to this test.
 - Test Enabled - true = enabled; false = disabled.
diff --git a/docs/features/test-maintenance/test-step-context-menu.md b/docs/features/test-maintenance/test-step-context-menu.md
index c775cb5a..235b13f8 100644
--- a/docs/features/test-maintenance/test-step-context-menu.md
+++ b/docs/features/test-maintenance/test-step-context-menu.md
@@ -8,12 +8,16 @@ position: 1
 
 Each test step provides further actions that can be taken in the right mouse button context menu. Note that some of the items will show up or will be enabled only for certain test step types.
 
-<table id="no-table">
-<tr>
-<td>![1][1]</td>
-<td>![2][2]</td>
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![1][1]</td>
+<td>
+
+![2][2]</td>
 </tr>
-<table>
+</table>
 
 ---
 
diff --git a/docs/features/test-maintenance/test-step-properties.md b/docs/features/test-maintenance/test-step-properties.md
index 1ddf6fb2..b6208509 100644
--- a/docs/features/test-maintenance/test-step-properties.md
+++ b/docs/features/test-maintenance/test-step-properties.md
@@ -47,117 +47,193 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AltKey**</td><td>Whether to hold the Alt key while clicking.</td><td>To execute an Alt + Click.</td>
+	<td>
+
+**AltKey**</td><td>Whether to hold the Alt key while clicking.</td><td>To execute an Alt + Click.</td>
 </tr>
 <tr>
-	<td>**AnnotationText**</td><td>The text to use for annotation.</td><td>With a Custom Annotation step.</td>
+	<td>
+
+**AnnotationText**</td><td>The text to use for annotation.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**BaseUrl**</td><td>The BaseURL to use when a global base is missing.</td><td> </td>
+	<td>
+
+**BaseUrl**</td><td>The BaseURL to use when a global base is missing.</td><td> </td>
 </tr>
 <tr>
-	<td>**CaptureType**</td><td>The type of window to capture.</td><td>With a Browser/Desktop Capture step.</td>
+	<td>
+
+**CaptureType**</td><td>The type of window to capture.</td><td>With a Browser/Desktop Capture step.</td>
 </tr>
 <tr>
-	<td>**ClickPoint / Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To click the target element based on specific offset coordinates instead of at absolute center.</td>
+	<td>
+
+**ClickPoint / Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To click the target element based on specific offset coordinates instead of at absolute center.</td>
 </tr>
 <tr>
-	<td>**ClosesBrowser**</td><td>ndicates to the automation that this action will force the browser to close. Typical for HTML pop-ups.</td><td>With a Click step that closes an HTML pop-up.</td>
+	<td>
+
+**ClosesBrowser**</td><td>ndicates to the automation that this action will force the browser to close. Typical for HTML pop-ups.</td><td>With a Click step that closes an HTML pop-up.</td>
 </tr>
 <tr>
-	<td>**ControlKey**</td><td>Whether to hold the <em>Ctrl</em> key while clicking.</td><td>To execute a Ctrl + Click. </td>
+	<td>
+
+**ControlKey**</td><td>Whether to hold the <em>Ctrl</em> key while clicking.</td><td>To execute a Ctrl + Click. </td>
 </tr>
 <tr>
-	<td>**Desktop Command Type**</td><td> The mouse action type.</td><td></td>
+	<td>
+
+**Desktop Command Type**</td><td> The mouse action type.</td><td></td>
 </tr>
 <tr>
-	<td>**DisplayLocation**</td><td>The location to display the annotation relative to the browser window.</td><td>With a Custom Annotation step.</td>
+	<td>
+
+**DisplayLocation**</td><td>The location to display the annotation relative to the browser window.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**DisplayTime**</td><td> The length of time in milliseconds to display the annotation.</td><td>With a Custom Annotation step.</td>
+	<td>
+
+**DisplayTime**</td><td> The length of time in milliseconds to display the annotation.</td><td>With a Custom Annotation step.</td>
 </tr>
 <tr>
-	<td>**Encrypt**</td><td>When set, will encrypt text typed into input control.<br>Once set to true, cannot be changed back to false.<br>'Text' property cannot be modified and current step cannot be converted to code. </td><td>With a <em>Set text</em> step on a password field. </td>
+	<td>
+
+**Encrypt**</td><td>When set, will encrypt text typed into input control.<br>Once set to true, cannot be changed back to false.<br>'Text' property cannot be modified and current step cannot be converted to code. </td><td>With a <em>Set text</em> step on a password field. </td>
 </tr>
 <tr>
-	<td>**EventType**</td><td>The Javascript event type to invoke.</td><td></td>
+	<td>
+
+**EventType**</td><td>The Javascript event type to invoke.</td><td></td>
 </tr>
 <tr>
-	<td>**FileNamePrefix**</td><td>The file name prefix to use to save the capture on disk.</td><td>To edit the file name for a browser or desktop Capture image.</td>
+	<td>
+
+**FileNamePrefix**</td><td>The file name prefix to use to save the capture on disk.</td><td>To edit the file name for a browser or desktop Capture image.</td>
 </tr>
 <tr>
-	<td>**FireKeyEvents**</td><td>Whether to fire <em>KeyDown</em> and <em>KeyUp</em> events during simulated typing.</td><td>If target input element requires these events to be fired.</td>
+	<td>
+
+**FireKeyEvents**</td><td>Whether to fire <em>KeyDown</em> and <em>KeyUp</em> events during simulated typing.</td><td>If target input element requires these events to be fired.</td>
 </tr>
 <tr>
-	<td>**Focus**</td><td>Scroll element into view before performing an action on it.</td><td>For action steps that require the element be scrolled into view before being acted upon.</td>
+	<td>
+
+**Focus**</td><td>Scroll element into view before performing an action on it.</td><td>For action steps that require the element be scrolled into view before being acted upon.</td>
 </tr>
 <tr>
-	<td>**HandleButton**</td><td>The button to click to handle this dialog.</td><td>To change the button clicked in the dialog.</td>
+	<td>
+
+**HandleButton**</td><td>The button to click to handle this dialog.</td><td>To change the button clicked in the dialog.</td>
 </tr>
 <tr>
-	<td>**HandleTimeout**</td><td>The timeout in milliseconds for the dialog to be handled once it is detected.</td><td>Increase if dialog is not fully handled within time set.</td>
+	<td>
+
+**HandleTimeout**</td><td>The timeout in milliseconds for the dialog to be handled once it is detected.</td><td>Increase if dialog is not fully handled within time set.</td>
 </tr>
 <tr>
-	<td>**InitializationTime**</td><td>The fixed time to wait in milliseconds before the handling of the dialog starts.</td><td>Increase if dialog needs longer to initialize.</td>
+	<td>
+
+**InitializationTime**</td><td>The fixed time to wait in milliseconds before the handling of the dialog starts.</td><td>Increase if dialog needs longer to initialize.</td>
 </tr>
 <tr>
-	<td>**IsPassword**</td><td>Whether the text field is a password.</td><td>To mask the password in the step description. </td>
+	<td>
+
+**IsPassword**</td><td>Whether the text field is a password.</td><td>To mask the password in the step description. </td>
 </tr>
 <tr>
-	<td>**KeyHoldTime**</td><td>The length of time in milliseconds to hold each key down when <em>SimulateRealTyping</em> is true.</td><td>To slow down or speed up typing.</td>
+	<td>
+
+**KeyHoldTime**</td><td>The length of time in milliseconds to hold each key down when <em>SimulateRealTyping</em> is true.</td><td>To slow down or speed up typing.</td>
 </tr>
 <tr>
-	<td>**Modifier Keys**</td><td>Any modifier keys held while clicking.</td><td>If the click step requires a modifier key to be held.</td>
+	<td>
+
+**Modifier Keys**</td><td>Any modifier keys held while clicking.</td><td>If the click step requires a modifier key to be held.</td>
 </tr>
 <tr>
-	<td>**MouseButton**</td><td>The clicked mouse button.</td><td>With a Mouse Action Desktop Command step.</td>
+	<td>
+
+**MouseButton**</td><td>The clicked mouse button.</td><td>With a Mouse Action Desktop Command step.</td>
 </tr>
 <tr>
-	<td>**NavigateUrl**</td><td>The URL for the Navigate step.</td><td>To edit the target URL.</td>
+	<td>
+
+**NavigateUrl**</td><td>The URL for the Navigate step.</td><td>To edit the target URL.</td>
 </tr>
 <tr>
-	<td>**OverrideFile**</td><td>Whether to override the image file if it exists.</td><td>To create new or override existing browser or desktop Capture images.</td>
+	<td>
+
+**OverrideFile**</td><td>Whether to override the image file if it exists.</td><td>To create new or override existing browser or desktop Capture images.</td>
 </tr>
 <tr>
-	<td>**Recorded Text Content**</td><td> Text to use when <em>SimulateRealTyping</em> is false.</td><td>To edit input text.</td>
+	<td>
+
+**Recorded Text Content**</td><td> Text to use when <em>SimulateRealTyping</em> is false.</td><td>To edit input text.</td>
 </tr>
 <tr>
-	<td>**ScrollToVisibleType**</td><td>Scroll element to visible type.</td><td>To set a Scroll step to window top, center or bottom.</td>
+	<td>
+
+**ScrollToVisibleType**</td><td>Scroll element to visible type.</td><td>To set a Scroll step to window top, center or bottom.</td>
 </tr>
 <tr>
-	<td>**SearchByImageFirst**</td><td>Search by image before searching by element's find expression.</td><td>**ParentSetting** will inherit Project or Test List settings. **True** and **False** overrides Project and Test List settings.</td>
+	<td>
+
+**SearchByImageFirst**</td><td>Search by image before searching by element's find expression.</td><td>
+
+**ParentSetting** will inherit Project or Test List settings. **True** and **False** overrides Project and Test List settings.</td>
 </tr>
 <tr>
-	<td>**ShiftKey**</td><td>Whether to hold the Shift key while clicking.</td><td>To execute a Shift + Click.</td>
+	<td>
+
+**ShiftKey**</td><td>Whether to hold the Shift key while clicking.</td><td>To execute a Shift + Click.</td>
 </tr>
 <tr>
-	<td>**SimulateRealClick**</td><td>Whether to perform the click using the mouse rather than directly invoking a click on the DOM element.</td><td>If the click target requires a real click to trigger an event or validation.</td>
+	<td>
+
+**SimulateRealClick**</td><td>Whether to perform the click using the mouse rather than directly invoking a click on the DOM element.</td><td>If the click target requires a real click to trigger an event or validation.</td>
 </tr>
 <tr>
-	<td>**SimulateRealTyping**</td><td>Whether to simulate real text typing one character at a time.</td><td>If input field requires real typing to trigger an event or validation.</td>
+	<td>
+
+**SimulateRealTyping**</td><td>Whether to simulate real text typing one character at a time.</td><td>If input field requires real typing to trigger an event or validation.</td>
 </tr>
 <tr>
-	<td>**SimulateRealUser**</td><td>Whether to simulate real user actions.</td><td>For Silverlight/WPF action steps.</td>
+	<td>
+
+**SimulateRealUser**</td><td>Whether to simulate real user actions.</td><td>For Silverlight/WPF action steps.</td>
 </tr>
 <tr>
-	<td>**Text**</td><td>Text entered into input control.</td><td>To edit the input text.</td>
+	<td>
+
+**Text**</td><td>Text entered into input control.</td><td>To edit the input text.</td>
 </tr>
 <tr>
-	<td>**TimeBetweenKeyPresses**</td><td>The pause in milliseconds between key presses to use when SimulateRealUser is set.</td><td>To increase or decrease the typing speed.</td>
+	<td>
+
+**TimeBetweenKeyPresses**</td><td>The pause in milliseconds between key presses to use when SimulateRealUser is set.</td><td>To increase or decrease the typing speed.</td>
 </tr>
 <tr>
-	<td>**Typed Text**</td><td>Text that will be played back when <em>SimulateRealUser</em> is true.</td><td>To edit the typed text.</td>
+	<td>
+
+**Typed Text**</td><td>Text that will be played back when <em>SimulateRealUser</em> is true.</td><td>To edit the typed text.</td>
 </tr>
 <tr>
-	<td>**Typing Delay**</td><td>The pause between key presses when <em>SimulateRealUser</em> is set.</td><td>To increase or decrease the typing speed. </td>
+	<td>
+
+**Typing Delay**</td><td>The pause between key presses when <em>SimulateRealUser</em> is set.</td><td>To increase or decrease the typing speed. </td>
 </tr>
 <tr>
-	<td>**Use Offset**</td><td>Whether to click at a specific point within the target element or the center of it.</td><td>With a Click step. </td>
+	<td>
+
+**Use Offset**</td><td>Whether to click at a specific point within the target element or the center of it.</td><td>With a Click step. </td>
 </tr>
 <tr>
-	<td>**WaitTime**</td><td>Time to wait in milliseconds.</td><td>With an Execution Delay step. </td>
+	<td>
+
+**WaitTime**</td><td>Time to wait in milliseconds.</td><td>With an Execution Delay step. </td>
 </tr>
-<table>
+</table>
 
 ## Comment
 
@@ -166,9 +242,11 @@ padding: 8px;
 	<th>Property</th><th>Property</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Comment**</td><td>The text comment to display as a single test step in the test log.</td><td>To insert a comment into the test log next to the step. </td>
+	<td>
+
+**Comment**</td><td>The text comment to display as a single test step in the test log.</td><td>To insert a comment into the test log next to the step. </td>
 </tr>
-<table>
+</table>
 
 ## Data Driven
 
@@ -177,9 +255,11 @@ padding: 8px;
 	<th>Property</th><th>Property</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**(Bindings)**</td><td>Bind data driven properties against a data source. Click the drop-down to see properties that support data binding.</td><td>To data bind the step to a specific column from the data source.</td>
+	<td>
+
+**(Bindings)**</td><td>Bind data driven properties against a data source. Click the drop-down to see properties that support data binding.</td><td>To data bind the step to a specific column from the data source.</td>
 </tr>
-<table>
+</table>
 
 ## Dialog Indentification
 
@@ -188,15 +268,21 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ChildWindowTextContent**</td><td>A partial text that might be found on the dialog.</td><td>If two dialogs have similar titles, further distinguish them by adding this property. </td>
+	<td>
+
+**ChildWindowTextContent**</td><td>A partial text that might be found on the dialog.</td><td>If two dialogs have similar titles, further distinguish them by adding this property. </td>
 </tr>
 <tr>
-	<td>**DialogTitle**</td><td>The dialog title to look for to identify the dialog.</td><td>To edit the identifying dialog title. </td>
+	<td>
+
+**DialogTitle**</td><td>The dialog title to look for to identify the dialog.</td><td>To edit the identifying dialog title. </td>
 </tr>
 <tr>
-	<td>**MatchPartialTitle**</td><td>Whether to use partial text matching to match the dialog title.</td><td>To match an exact or partial dialog title. </td>
+	<td>
+
+**MatchPartialTitle**</td><td>Whether to use partial text matching to match the dialog title.</td><td>To match an exact or partial dialog title. </td>
 </tr>
-<table>
+</table>
 
 ## Download
 
@@ -205,9 +291,11 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DownloadPath**</td><td>The download location to set for the download dialog.</td><td>To change where a file is saved by the Download dialog handler step. </td>
+	<td>
+
+**DownloadPath**</td><td>The download location to set for the download dialog.</td><td>To change where a file is saved by the Download dialog handler step. </td>
 </tr>
-<table>
+</table>
 
 ## Drag Settings
 
@@ -216,9 +304,11 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To start the drag from an offset of the source element, as opposed to absolute center. </td>
+	<td>
+
+**Offset**</td><td>ClickUnitType - the unit of point to use: percentage or pixel.<br>OffSetReference - the reference point of screen to use for the click.<br>X - the x-axis offset from reference point.<br>Y - the y-axis offset from reference point.</td><td>To start the drag from an offset of the source element, as opposed to absolute center. </td>
 </tr>
-<table>
+</table>
 
 ## Drop Settings
 
@@ -227,15 +317,21 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DragDropWindowData**</td><td>Used when entire window is considered the drop target.</td><td>To edit the window coordinates where the source element is dropped when using window target.</td>
+	<td>
+
+**DragDropWindowData**</td><td>Used when entire window is considered the drop target.</td><td>To edit the window coordinates where the source element is dropped when using window target.</td>
 </tr>
 <tr>
-	<td>**DropOffset**</td><td>The offset to use for the drop target.</td><td>To drop the source element to offset coordinates of the target element. </td>
+	<td>
+
+**DropOffset**</td><td>The offset to use for the drop target.</td><td>To drop the source element to offset coordinates of the target element. </td>
 </tr>
 <tr>
-	<td>**DropTargetType**</td><td>The type of drop target to use for the drag drop.</td><td>To drop the source element to a window or element target. Element targets tend to be more reliable. </td>
+	<td>
+
+**DropTargetType**</td><td>The type of drop target to use for the drag drop.</td><td>To drop the source element to a window or element target. Element targets tend to be more reliable. </td>
 </tr>
-<table>
+</table>
 
 ## Elements
 
@@ -244,24 +340,36 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Drag Element**</td><td>Key of the element to use for the drag.</td><td>To change the source element to drag. </td>
+	<td>
+
+**Drag Element**</td><td>Key of the element to use for the drag.</td><td>To change the source element to drag. </td>
 </tr>
 <tr>
-	<td>**Drop Element**</td><td>Key of the element to use for the drop.</td><td>To change the target element to drop onto. </td>
+	<td>
+
+**Drop Element**</td><td>Key of the element to use for the drop.</td><td>To change the target element to drop onto. </td>
 </tr>
 <tr>
-	<td>**PrimaryTarget**</td><td>The primary automation element that this step is targeting.</td><td>To change the element the step is based on. </td>
+	<td>
+
+**PrimaryTarget**</td><td>The primary automation element that this step is targeting.</td><td>To change the element the step is based on. </td>
 </tr>
 <tr>
-	<td>**SecondaryTarget**</td><td>The primary automation element that this step is targeting. Used only for steps that require two targets, like a drag and drop.</td><td>Only in drag and drop scenarios. </td>
+	<td>
+
+**SecondaryTarget**</td><td>The primary automation element that this step is targeting. Used only for steps that require two targets, like a drag and drop.</td><td>Only in drag and drop scenarios. </td>
 </tr>
 <tr>
-	<td>**Virtualizing Container**</td><td>The object containing this element, if any.</td><td>(Silverlight only) </td>
+	<td>
+
+**Virtualizing Container**</td><td>The object containing this element, if any.</td><td>(Silverlight only) </td>
 </tr>
 <tr>
-	<td>**Virtualizing Container Offset**</td><td>The offset to scroll the virtualizing container to before searching for the target element of this step.</td><td>(Silverlight only) </td>
+	<td>
+
+**Virtualizing Container Offset**</td><td>The offset to scroll the virtualizing container to before searching for the target element of this step.</td><td>(Silverlight only) </td>
 </tr>
-<table>
+</table>
 
 ## Execution
 
@@ -270,30 +378,46 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AjaxTimeout** </td><td>The timeout to wait for pending AJAX requests. </td><td>If the test step relies on an AJAX postback to complete before proceeding. </td>
+	<td>
+
+**AjaxTimeout** </td><td>The timeout to wait for pending AJAX requests. </td><td>If the test step relies on an AJAX postback to complete before proceeding. </td>
 </tr>
 <tr>
-	<td>**EnsureElementsClickable**</td><td>Whether to ensure the target element of this action is visible and clickable before performing the action.</td><td></td>
+	<td>
+
+**EnsureElementsClickable**</td><td>Whether to ensure the target element of this action is visible and clickable before performing the action.</td><td></td>
 </tr>
 <tr>
-	<td>**Pause**</td><td>Whether to pause the step during execution. Only respected when running tests from the Test Explorer.</td><td>To pause test execution at a certain point to manually debug. </td>
+	<td>
+
+**Pause**</td><td>Whether to pause the step during execution. Only respected when running tests from the Test Explorer.</td><td>To pause test execution at a certain point to manually debug. </td>
 </tr>
 <tr>
-	<td>**ScrollToVisibleType**</td><td>When 'SimulateRealClick' or 'SimulateRealTyping' is set to 'True', you can specify the scroll direction in order to get the target element into view.</td><td>Choose whether to scroll the element to top, center  or bottom of the page.</td>
+	<td>
+
+**ScrollToVisibleType**</td><td>When 'SimulateRealClick' or 'SimulateRealTyping' is set to 'True', you can specify the scroll direction in order to get the target element into view.</td><td>Choose whether to scroll the element to top, center  or bottom of the page.</td>
 </tr>
 <tr>
-	<td>**UseStepWaitOnElementsTimeout**</td><td>Whether to use step's WaitOnElementsTimeout instead of the global setting.</td><td>To specifically increase one step's element locating timeout. </td>
+	<td>
+
+**UseStepWaitOnElementsTimeout**</td><td>Whether to use step's WaitOnElementsTimeout instead of the global setting.</td><td>To specifically increase one step's element locating timeout. </td>
 </tr>
 <tr>
-	<td>**WaitForNoMotion**</td><td>Wait for the element to stop moving before executing the action.</td><td></td>
+	<td>
+
+**WaitForNoMotion**</td><td>Wait for the element to stop moving before executing the action.</td><td></td>
 </tr>
 <tr>
-	<td>**WaitOnElements**</td><td>Whether to wait on step's elements to exist before executing it.</td><td>The default is True (recommended). False will ignore the Global and per step settings and will execute the step without waiting for the element (not recommended). </td>
+	<td>
+
+**WaitOnElements**</td><td>Whether to wait on step's elements to exist before executing it.</td><td>The default is True (recommended). False will ignore the Global and per step settings and will execute the step without waiting for the element (not recommended). </td>
 </tr>
 <tr>
-	<td>**WaitOnElementsTimeout**</td><td>Number of milliseconds to wait for element to exist if <em>WaitOnElements</em> is true.</td><td>To specifically increase one step's element locating timeout. </td>
+	<td>
+
+**WaitOnElementsTimeout**</td><td>Number of milliseconds to wait for element to exist if <em>WaitOnElements</em> is true.</td><td>To specifically increase one step's element locating timeout. </td>
 </tr>
-<table>
+</table>
 
 ## Extraction
 
@@ -302,9 +426,11 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DataBindVariableName**</td><td>The name with which this extraction is published.</td><td>To change the Extraction variable used for later data binding. </td>
+	<td>
+
+**DataBindVariableName**</td><td>The name with which this extraction is published.</td><td>To change the Extraction variable used for later data binding. </td>
 </tr>
-<table>
+</table>
 
 ## jQuery
 
@@ -313,9 +439,11 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**TriggerjQueryEvent**</td><td>During step execution, attempt to trigger proper jQuery event.</td><td>Step is expected to trigger a jQuery event on the page.</td>
+	<td>
+
+**TriggerjQueryEvent**</td><td>During step execution, attempt to trigger proper jQuery event.</td><td>Step is expected to trigger a jQuery event on the page.</td>
 </tr>
-<table>
+</table>
 
 ## Handle Button
 
@@ -324,15 +452,21 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ButtonId**</td><td>The button ID to use when <em>HandleButtonMethod = ButtonId</em>.</td><td>To edit the button ID used to handle a Generic dialog. </td>
+	<td>
+
+**ButtonId**</td><td>The button ID to use when <em>HandleButtonMethod = ButtonId</em>.</td><td>To edit the button ID used to handle a Generic dialog. </td>
 </tr>
 <tr>
-	<td>**ButtonPartialText**</td><td>The partial button text to use when <em>HandleButtonMethod = ButtonPartialText</em>.</td><td>To edit the partial button text used to handle a Generic dialog. </td>
+	<td>
+
+**ButtonPartialText**</td><td>The partial button text to use when <em>HandleButtonMethod = ButtonPartialText</em>.</td><td>To edit the partial button text used to handle a Generic dialog. </td>
 </tr>
 <tr>
-	<td>**HandleButtonMethod**</td><td>Identification method of the handle method. <em>NoneCloseDialog</em> simply attempts to knock down the dialog using the Close button.</td><td>To change the handle method for a Generic dialog.</td>
+	<td>
+
+**HandleButtonMethod**</td><td>Identification method of the handle method. <em>NoneCloseDialog</em> simply attempts to knock down the dialog using the Close button.</td><td>To change the handle method for a Generic dialog.</td>
 </tr>
-<table>
+</table>
 
 ## Logon
 
@@ -341,12 +475,16 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**Password**</td><td>The password to use to log on.</td><td>To edit the password in a Logon dialog handler step. </td>
+	<td>
+
+**Password**</td><td>The password to use to log on.</td><td>To edit the password in a Logon dialog handler step. </td>
 </tr>
 <tr>
-	<td>**UserName**</td><td>The user name to use to log on.</td><td>To edit the user name in a Logon dialog handler step. </td>
+	<td>
+
+**UserName**</td><td>The user name to use to log on.</td><td>To edit the user name in a Logon dialog handler step. </td>
 </tr>
-<table>
+</table>
 
 ## Manual Properties
 
@@ -355,12 +493,16 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**ExecutionTimeout**</td><td>Timeout in milliseconds to wait for the manual execution, else step will timeout and log a failure.</td><td>To change the time in minutes a Manual step will wait for input. </td>
+	<td>
+
+**ExecutionTimeout**</td><td>Timeout in milliseconds to wait for the manual execution, else step will timeout and log a failure.</td><td>To change the time in minutes a Manual step will wait for input. </td>
 </tr>
 <tr>
-	<td>**ManualDescription**</td><td>Description displayed in <em>Execute Manual Step</em> dialog.</td><td>To edit the message displayed in the Manual step dialog. </td>
+	<td>
+
+**ManualDescription**</td><td>Description displayed in <em>Execute Manual Step</em> dialog.</td><td>To edit the message displayed in the Manual step dialog. </td>
 </tr>
-<table>
+</table>
 
 ## Misc
 
@@ -369,51 +511,81 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**DialogType**</td><td>The type of dialog handled by the step.</td><td>(Read only) </td>
+	<td>
+
+**DialogType**</td><td>The type of dialog handled by the step.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**InvokeSelectionChanged** </td><td>Whether to invoke the OnChange javascript event. </td><td>If the step requires the OnChange event. </td>
+	<td>
+
+**InvokeSelectionChanged** </td><td>Whether to invoke the OnChange javascript event. </td><td>If the step requires the OnChange event. </td>
 </tr>
 <tr>
-	<td>**IsDoubleClick**</td><td>Whether a click step is a single or double click.</td><td>To toggle between single or double click. </td>
+	<td>
+
+**IsDoubleClick**</td><td>Whether a click step is a single or double click.</td><td>To toggle between single or double click. </td>
 </tr>
 <tr>
-	<td>**IsPartial**</td><td>Whether to perform a partial or exact match on the URL.</td><td>With a Wait For Url step. </td>
+	<td>
+
+**IsPartial**</td><td>Whether to perform a partial or exact match on the URL.</td><td>With a Wait For Url step. </td>
 </tr>
 <tr>
-	<td>**LogMessageOnFailure**</td><td>Message to log as part of log content if step fails.</td><td>To insert a custom message in the test log if the step fails. </td>
+	<td>
+
+**LogMessageOnFailure**</td><td>Message to log as part of log content if step fails.</td><td>To insert a custom message in the test log if the step fails. </td>
 </tr>
 <tr>
-	<td>**RequiresSilverlight**</td><td>Whether this step requires Silverlight to be enabled.</td><td></td>
+	<td>
+
+**RequiresSilverlight**</td><td>Whether this step requires Silverlight to be enabled.</td><td></td>
 </tr>
 <tr>
-	<td>**RunsAgainst**</td><td>The browsers this step can run against.</td><td>If a step should only be run for a specific browser type. </td>
+	<td>
+
+**RunsAgainst**</td><td>The browsers this step can run against.</td><td>If a step should only be run for a specific browser type. </td>
 </tr>
 <tr>
-	<td>**RunsAgainstVersion**</td><td>The browser version that this step can run against.</td><td>If a step should only be run for a specific browser version. </td>
+	<td>
+
+**RunsAgainstVersion**</td><td>The browser version that this step can run against.</td><td>If a step should only be run for a specific browser version. </td>
 </tr>
 <tr>
-	<td>**RunsAgainstVersionCompare**</td><td>The compare type of the browser version that this step can run against.</td><td>To change the browser version comparison from Equals to LessThan, for example.</td>
+	<td>
+
+**RunsAgainstVersionCompare**</td><td>The compare type of the browser version that this step can run against.</td><td>To change the browser version comparison from Equals to LessThan, for example.</td>
 </tr>
 <tr>
-	<td>**StepType**</td><td>Step descriptor type.</td><td>(Read only) </td>
+	<td>
+
+**StepType**</td><td>Step descriptor type.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**TestName**</td><td>Name of the test to execute for Test as Step.</td><td>(Read only) </td>
+	<td>
+
+**TestName**</td><td>Name of the test to execute for Test as Step.</td><td>(Read only) </td>
 </tr>
 <tr>
-	<td>**TestPath**</td><td>Test path to use for Test as Step.</td><td></td>
+	<td>
+
+**TestPath**</td><td>Test path to use for Test as Step.</td><td></td>
 </tr>
 <tr>
-	<td>**TestUniqueId**</td><td>Unique ID for Test as Step.</td><td></td>
+	<td>
+
+**TestUniqueId**</td><td>Unique ID for Test as Step.</td><td></td>
 </tr>
 <tr>
-	<td>**Url**</td><td>The URL to wait for.</td><td>With a Wait For Url step. </td>
+	<td>
+
+**Url**</td><td>The URL to wait for.</td><td>With a Wait For Url step. </td>
 </tr>
 <tr>
-	<td>**WaitTimeout**</td><td>The timeout to use for waiting.</td><td>With a Wait For Url step.</td>
+	<td>
+
+**WaitTimeout**</td><td>The timeout to use for waiting.</td><td>With a Wait For Url step.</td>
 </tr>
-<table>
+</table>
 
 ## Upload
 
@@ -422,9 +594,11 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**FileUploadPath**</td><td>The file upload path on disk.</td><td>To change the upload path. </td>
+	<td>
+
+**FileUploadPath**</td><td>The file upload path on disk.</td><td>To change the upload path. </td>
 </tr>
-<table>
+</table>
 
 ## Verification
 
@@ -433,30 +607,46 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**AttributeName** </td><td>The attribute name to verify. </td><td>To change the target attribute to verify. </td>
+	<td>
+
+**AttributeName** </td><td>The attribute name to verify. </td><td>To change the target attribute to verify. </td>
 </tr>
 <tr>
-	<td>**AttributeValue** </td><td>The attribute value to verify. </td><td>To change the attribute's value to verify. </td>
+	<td>
+
+**AttributeValue** </td><td>The attribute value to verify. </td><td>To change the attribute's value to verify. </td>
 </tr>
 <tr>
-	<td>**CompareType**</td><td>The compare type of the text verification.</td><td>To change from an exact to a partial match, for example. </td>
+	<td>
+
+**CompareType**</td><td>The compare type of the text verification.</td><td>To change from an exact to a partial match, for example. </td>
 </tr>
 <tr>
-	<td>**EnsureStateIsCurrent**</td><td>Whether to explicitly refresh the target element on which the verification is performed.</td><td>To eliminate the need to explicitly refresh the DOM tree in a coded step before the verification. </td>
+	<td>
+
+**EnsureStateIsCurrent**</td><td>Whether to explicitly refresh the target element on which the verification is performed.</td><td>To eliminate the need to explicitly refresh the DOM tree in a coded step before the verification. </td>
 </tr>
 <tr>
-	<td>**ExpectedString**</td><td>The expected string to compare against.</td><td>To change the string to verify. </td>
+	<td>
+
+**ExpectedString**</td><td>The expected string to compare against.</td><td>To change the string to verify. </td>
 </tr>
 <tr>
-	<td>**PropertyName**</td><td>The name of the property being verified.</td><td>To change the property to verify. </td>
+	<td>
+
+**PropertyName**</td><td>The name of the property being verified.</td><td>To change the property to verify. </td>
 </tr>
 <tr>
-	<td>**TagSegmentType**</td><td>The segment of the target element to compare.</td><td>To change which attribute the Verification is based on. </td>
+	<td>
+
+**TagSegmentType**</td><td>The segment of the target element to compare.</td><td>To change which attribute the Verification is based on. </td>
 </tr>
 <tr>
-	<td>**Value**</td><td>Represents the expected value of the property.</td><td>To change the value to verify. </td>
+	<td>
+
+**Value**</td><td>Represents the expected value of the property.</td><td>To change the value to verify. </td>
 </tr>
-<table>
+</table>
 
 ## Wait
 
@@ -465,18 +655,26 @@ padding: 8px;
 	<th>Property</th><th>Description</th><th>When To Use</th>
 </tr>
 <tr>
-	<td>**CheckInterval**</td><td>The check interval in milliseconds when acting as a Wait.</td><td>To cause the Wait to check its condition more or less frequently.</td>
+	<td>
+
+**CheckInterval**</td><td>The check interval in milliseconds when acting as a Wait.</td><td>To cause the Wait to check its condition more or less frequently.</td>
 </tr>
 <tr>
-	<td>**IsWaitOnly**</td><td>Whether this descriptor can only be a wait.</td><td>(Read only)</td>
+	<td>
+
+**IsWaitOnly**</td><td>Whether this descriptor can only be a wait.</td><td>(Read only)</td>
 </tr>
 <tr>
-	<td>**SupportsWait**</td><td>Whether this verification supports wait.</td><td>(Read only)</td>
+	<td>
+
+**SupportsWait**</td><td>Whether this verification supports wait.</td><td>(Read only)</td>
 </tr>
 <tr>
-	<td>**Timeout**</td><td>The wait time when acting as a wait.</td><td>To increase or decrease the wait time. </td>
+	<td>
+
+**Timeout**</td><td>The wait time when acting as a wait.</td><td>To increase or decrease the wait time. </td>
 </tr>
-<table>
+</table>
 
 
 [1]: /img/features/test-maintenance/test-step-properties/step-properties.png
diff --git a/docs/features/test-runners/add-path-environment-variables.md b/docs/features/test-runners/add-path-environment-variables.md
index db39b144..c5361410 100644
--- a/docs/features/test-runners/add-path-environment-variables.md
+++ b/docs/features/test-runners/add-path-environment-variables.md
@@ -71,7 +71,7 @@ Below you can find the necessary steps to add the _Bin_ sub-folder to the __PATH
 [4]: /img/features/test-runners/add-path-environment-variables/fig4.png
 [5]: /img/features/test-runners/add-path-environment-variables/fig5.png
 [6]: /img/features/test-runners/add-path-environment-variables/fig6.png
-[7]: /img/features/test-runners/add-path-environment-variables/fig7.png
+
 [8]: /img/features/test-runners/add-path-environment-variables/fig8.png
 [9]: /img/features/test-runners/add-path-environment-variables/fig9.png
 [10]: /img/features/test-runners/add-path-environment-variables/fig10.png
diff --git a/docs/features/test-runners/artoftest-runner.md b/docs/features/test-runners/artoftest-runner.md
index 20253e02..3d1bf6ac 100644
--- a/docs/features/test-runners/artoftest-runner.md
+++ b/docs/features/test-runners/artoftest-runner.md
@@ -52,20 +52,20 @@ The `test` option accepts full file path to an individual test with the **\*.tst
 
 - Run individual test stored in the project root folder: 
 
-```cmd
+````batch
 > "C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 test="D:\Test Studio Projects\July2024\demoTest-AOTRunner.tstest"
-```
+````
 
 ![Run individual test stored in the project root folder][5]
 
 - Run individual test stored in a sub-folder under the project root one: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 test="D:\Test Studio Projects\July2024\inProjectFolder\nestedDemoTest.tstest" 
 root="D:\Test Studio Projects\July2024"
-```
+````
 
 ![Run individual test stored in a sub-folder under the project root one][4]
 
@@ -83,10 +83,10 @@ The `list` option takes the full path to a test list file with the **\*.aiilist*
 
 - Run test list: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist"
-```
+````
 
 ![Run test list][6]
 
@@ -110,10 +110,10 @@ The `out` option defines an alternative folder to store the results to and takes
 
 - Run test list outputting the results in specified folder: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist" out="D:\SharedFolder"
-```
+````
 
 ![Run test list outputting the results in specified folder][7]
 
@@ -125,11 +125,11 @@ The `result` sets specific name for the default result file and takes a file nam
 
 - Run test list outputting the results in specified folder and setting custom name for the result file: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist" out="D:\SharedFolder" 
 result="customName"
-```
+````
 
 ![Run test list outputting the results in specified folder with custom name][8]
 
@@ -145,22 +145,22 @@ Use either the `xml`, or the `html` option to output the result into the corresp
 
 - Run test list outputting the results in xml format: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist" 
 xml
-``` 
+```` 
 
 ![Run test list outputting the results in xml format][9]
 
 - Run test list outputting the results in html format in specified folder and setting custom name for the result files: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist" out="D:\SharedFolder" 
 result="customName" 
 html
-```
+````
 
 ![Run test list outputting the results in html format in specified folder with custom name][10]
 
@@ -176,23 +176,23 @@ Use the `junit` or `junitstep` options to output the result into a `junit(step).
 
 - Run test list outputting the results in junitstep format in specified folder and setting custom name for the result files: 
 
-```cmd
+````batch
 >"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 list="D:\Test Studio Projects\July2024\TestLists\demoList-ArtOfTest.aiilist" 
 out="D:\SharedFolder" 
 result="customName" 
 junitstep
-```
+````
 
 ![Run test list outputting the results in junitstep format in specified folder with custom name][11]
 
 - Run single test outputting the results in junit format: 
 
-```cmd
+````batch
 >>"C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Runner.exe" 
 test="D:\elle\Test Studio Projects\July2024\demoTest-AOTRunner.tstest" 
 junit
-```
+````
 
 ![Run single test outputting the results in junit format][12]
 
@@ -214,7 +214,7 @@ The `settings` option takes the full path to a JSON file containing custom setti
 
 Below is an example of a complete JSON setting file that contains all of Telerik's test/test list run configuration settings. 
 
-```JSON
+````JSON
 {
   "Settings": {
       "__type": "ArtOfTest.WebAii.Core.Settings",
@@ -245,10 +245,7 @@ Below is an example of a complete JSON setting file that contains all of Telerik
             "KillBrowsersBeforeStart": true,
             "AutoCalibrateBrowsers": false,
             "UseHttpProxy": false,
-            "EnableSilverlight": false,
             "VerboseHttpProxy": false,
-            "SilverlightConnectTimeout": 60000,
-            "SilverlightApplicationPath": null,
             "WebComponents": true,
             "UseBrowserExtension": false,
             "ChromiumFirstInteractionDelay": 500,
@@ -306,8 +303,7 @@ Below is an example of a complete JSON setting file that contains all of Telerik
   "WebSettings": null,
   "PropertyBag": null
 }
-
-```
+````
 
 > __Tip__
 ><br>
@@ -367,35 +363,35 @@ padding: 8px;
 	<th>Code</th><th>Title</th><th>Summary</th>
 </tr>
 <tr>
-	<td>**0**</td><td>RUN_TESTS_SUCCESS </td><td>Run is processed and all tests passed.</td>
+	<td><strong>0</strong></td><td>RUN_TESTS_SUCCESS </td><td>Run is processed and all tests passed.</td>
 </tr>
 <tr>
-	<td>**1**</td><td>RUN_TESTS_ERROR</td><td>Run is processed and some tests failed.</td>
+	<td><strong>1</strong></td><td>RUN_TESTS_ERROR</td><td>Run is processed and some tests failed.</td>
 </tr>
 <tr>
-	<td>**2**</td><td>NOT_RUN_UNEXPECTED_ERROR</td><td>Run is not processed due to unexpected error.</td>
+	<td><strong>2</strong></td><td>NOT_RUN_UNEXPECTED_ERROR</td><td>Run is not processed due to unexpected error.</td>
 </tr>
 <tr>
-	<td>**3**</td><td>NOT_RUN_COMPILATION_ERROR</td><td>Run is not processed due to compilation errors.</td>
+	<td><strong>3</strong></td><td>NOT_RUN_COMPILATION_ERROR</td><td>Run is not processed due to compilation errors.</td>
 </tr>
 <tr>
-	<td>**10**</td><td>NOT_RUN_USAGE_INFO</td><td>No run to process, requested usage info.</td>
+	<td><strong>10</strong></td><td>NOT_RUN_USAGE_INFO</td><td>No run to process, requested usage info.</td>
 </tr>
 <tr>
-	<td>**11**</td><td>NOT_RUN_INVALID_COMMAND_ARGS</td><td>No run to process due to general invalid arguments error.</td>
+	<td><strong>11</strong></td><td>NOT_RUN_INVALID_COMMAND_ARGS</td><td>No run to process due to general invalid arguments error.</td>
 </tr>
 <tr>
-	<td>**12**</td><td>NOT_RUN_TEST_NOT_FOUND</td><td>Run is not processed due to invalid test path argument.</td>
+	<td><strong>12</strong></td><td>NOT_RUN_TEST_NOT_FOUND</td><td>Run is not processed due to invalid test path argument.</td>
 </tr>
 <tr>
-	<td>**13**</td><td>NOT_RUN_TESTLIST_NOT_FOUND</td><td>Run is not processed due to invalid test list path argument.</td>
+	<td><strong>13</strong></td><td>NOT_RUN_TESTLIST_NOT_FOUND</td><td>Run is not processed due to invalid test list path argument.</td>
 </tr>
-<table>
+</table>
 
 
 [1]: /img/features/test-runners/artoftest-runner/fig1.png
 [2]: /img/features/test-runners/artoftest-runner/fig2.png
-[3]: /img/features/test-runners/artoftest-runner/fig3.png
+
 [4]: /img/features/test-runners/artoftest-runner/fig4.png
 [5]: /img/features/test-runners/artoftest-runner/fig5.png
 [6]: /img/features/test-runners/artoftest-runner/fig6.png
diff --git a/docs/features/test-runners/manual-runner.md b/docs/features/test-runners/manual-runner.md
deleted file mode 100644
index b2b4ca3c..00000000
--- a/docs/features/test-runners/manual-runner.md
+++ /dev/null
@@ -1,40 +0,0 @@
----
-title: Manual Runner
-page_title: Telerik.TestStudio.ManualRunner
-description: "Test Studio Manual Runner. Run manual test in Test Studio"
-previous_url: /user-guide/test-runners/manual-runner.aspx, /user-guide/test-runners/manual-runner
-position: 1
-publish: false
----
-# Telerik.TestStudio.ManualRunner
-
-You can launch a Manual Test, Manual Test List, or Manual Result file from the command line with *Telerik.TestStudio.ManualRunner*.
-
-Use it with the **path=[file path]** execution option. The file path argument accepts:
-
-
-- Manual Test (.tstest)
-- Manual Test List (.aiilist)
-- Manual Result (.aiiresult)
-
-## Manual Test
-
-Launch the Manual Runner and perform a single Manual Test.
-
-![Test][1]
-
-## Manual Test List
-
-Launch the Manual Runner and perform a series of Manual Tests in a Manual Test List.
-
-![List][2]
-
-## Manual Result
-
-Launch the Manual Runner to load the ending state of a previous Manual Run.
-
-![Result][3]
-
-[1]: /img/features/test-runners/manual-runner/fig1.png
-[2]: /img/features/test-runners/manual-runner/fig2.png
-[3]: /img/features/test-runners/manual-runner/fig3.png
\ No newline at end of file
diff --git a/docs/features/test-runners/mstest.md b/docs/features/test-runners/mstest.md
deleted file mode 100644
index 6267a23f..00000000
--- a/docs/features/test-runners/mstest.md
+++ /dev/null
@@ -1,100 +0,0 @@
----
-title: MSTest
-page_title: MSTest
-description: "Execute Test Studio with the Visual Studio command line runner MSTest. "
-previous_url: /user-guide/test-runners/mstest.aspx, /user-guide/test-runners/mstest
-position: 1
-publish: false
----
-# Executing Tests with MSTest
-
-> Please note that **MSTest** is a command line utility from Microsoft that executes tests created in Visual Studio. This is not a command line tool that is a part of Test Studio. More information you can find <a href="https://msdn.microsoft.com/en-us/library/ms182487.aspx" target="_blank">here</a>.
-
-You can also review our Telerik TV episode on <a href="http://tv.telerik.com/watch/automated-testing-tools/webui-test-studio-executing-webui-tests-with-mstest" target="_blank">Executing Tests with MSTest</a> for a video walk-through of this process.
-
-1.&nbsp; Open Visual Studio. Create a project containing two tests. In this example, I've create two simple Web Tests: GoogleSearch and BingSearch.
-
-2.&nbsp; Click **Test > Windows > Test List Editor**.
-
-![Test List Editor][1]
-
-**Note:** Read <a href="/getting-started/test-execution/visual-studio-2012-and-later-test-list" target="_blank">here</a> how to create test lists in Visual Studio 2012 or later.
-
-3.&nbsp; Right click **List of Tests** and choose **New Test List**.
-
-![New Test List][2]
-
-4.&nbsp; Name the New Test List and click **OK**.
-
-![Create New Test List][3]
-
-5.&nbsp; From the **Test View** pane, drag and drop the tests into the **Test List Editor** and Save the project.
-
-![Test View][4]
-
-6.&nbsp; Close Visual Studio and open the Visual Studio Command Prompt.
-
-7.&nbsp; Navigate to the project's directory.
-
-- **C:\Users\Admin\Documents\Visual Studio 2010\Projects\MSTest-Tutorial\MSTest-Tutorial**
-
-8.&nbsp; To execute a single test, enter the following:
-
-- **mstest /testcontainer:.\GoogleSearch.tstest**
-
-![Execute Test][5]
-
-9.&nbsp; To execute a test list, enter the following:
-
-- **mstest /testlist:SampleTestList /testmetadata:..\MSTest-Tutorial.vsmdi**
-
-![Execute Test List][6]
-
-
-10.&nbsp; Open Visual Studio and load the same project. Go the Solution Explorer pane.
-
-11.&nbsp; Right click "Solution Items"and choose **Add > New Item**.
-
-![Add New Item][7]
-
-12.&nbsp; Highlight **Test Settings** on the left, again in the center, and give it a unique name. Click **Add**.
-
-![Test Settings][8]
-
-13.&nbsp; The **Test Settings** window appears. Click **Telerik Test Studio** on the left, and then click the **Web** tab.
-
-![Web][9]
-
-14.&nbsp; Change the browser to Firefox and click **Apply** and **Close**. Save the project.
-
-15.&nbsp; Close Visual Studio and open the Visual Studio Command Prompt.
-
-16.&nbsp; Navigate to the project's directory:
-
-- **C:\Users\Admin\Documents\Visual Studio 2010\Projects\MSTest-Tutorial\MSTest-Tutorial**
-
-17.&nbsp; To execute a test list with a custom settings file:
- 
-- **mstest /testlist:SampleTestList /testmetadata:..\MSTest-Tutorial.vsmdi /testsettings:..\FF.testsettings**
-
-![Custom Settings][10]
-
-18.&nbsp; To specify the output location for a results file, add: 
-
-- **/resultsfile C:\Path\myResults.trx**
-
-### See also
-* <a href="/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest" target="_blank">How To Use Data Driven Tests With MSTest</a>
-
-
-[1]: /img/features/test-runners/mstest/fig1.png
-[2]: /img/features/test-runners/mstest/fig2.png
-[3]: /img/features/test-runners/mstest/fig3.png
-[4]: /img/features/test-runners/mstest/fig4.png
-[5]: /img/features/test-runners/mstest/fig5.png
-[6]: /img/features/test-runners/mstest/fig6.png
-[7]: /img/features/test-runners/mstest/fig7.png
-[8]: /img/features/test-runners/mstest/fig8.png
-[9]: /img/features/test-runners/mstest/fig9.png
-[10]: /img/features/test-runners/mstest/fig10.png
-
diff --git a/docs/features/testing-types/exploratory-testing/launch-tool.md b/docs/features/testing-types/exploratory-testing/launch-tool.md
deleted file mode 100644
index eaec4c4b..00000000
--- a/docs/features/testing-types/exploratory-testing/launch-tool.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Launch Tool
-page_title: Launch Test Studio Explore Tool
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/exploratory-testing/launch-tool.aspx, /user-guide/exploratory-testing/launch-tool
-position: 2
----
-# Launch Test Studio Explore Tool
-
-When you install Test Studio, the Explore tool is added to Internet Explorer, Firefox, Safari, and Chrome as a browser extension. It can be used even if Test Studio isn't running. Here's how to launch the tool in each browser:
-
-## Internet Explorer
-
-The Explore icon is located in the Command toolbar.
-
-- Click **View > Toolbar > Command bar** and ensure the Command bar is enabled.
-- Click the **Exploratory Testing** button.
-
-![IE][1]
-
-## Chrome
-
-- Click the **Exploratory Testing** button.
-
-![Chrome][4]
-
-## Firefox
-
-- Click the **Exploratory Testing** button.
-
-![FF][2]
-
-## Safari
-
-- Click the **Exploratory Testing** button.
-
-![Safari][3]
-
-
-[1]: /img/features/testing-types/exploratory-testing/launch-tool/fig1.png
-[2]: /img/features/testing-types/exploratory-testing/launch-tool/fig2.png
-[3]: /img/features/testing-types/exploratory-testing/launch-tool/fig3.png
-[4]: /img/features/testing-types/exploratory-testing/launch-tool/fig4.png
\ No newline at end of file
diff --git a/docs/features/testing-types/exploratory-testing/overview.md b/docs/features/testing-types/exploratory-testing/overview.md
deleted file mode 100644
index e2d50b77..00000000
--- a/docs/features/testing-types/exploratory-testing/overview.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Overview
-page_title: Exploratory Testing
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/exploratory-testing.aspx, /user-guide/exploratory-testing
-position: 1
----
-# Exploratory Testing
-
-> This feature is unable to launch for users with non-administrator rights. See <a href="/troubleshooting-guide/recording-problems-tg/cannot-launch-exploratory" target="_blank">here</a> for a potential work-around.
-
-Test Studio Explore is a small tool that will help you be more efficient in doing exploratory testing.
-
-
-- It leverages Test Studio's investment in bug tracking and image capturing to allow you to easily capture bugs and send feedback in your exploratory testing sessions.
-- The tool is designed to be light-weight, handy, and easy to launch and access.
-- Test Studio Explore is available in Internet Explorer, Firefox, Safari, and Chrome.
-	* **IE and Safari** - the tool is automatically installed with Test Studio installation. 
-	* **Firefox** - the tool is deployed along with the Test Studio installation within the respective extension.
-	**NOTE:** A working Exploratory testing extension is only available for Firefox versions 42 and previous due to the signed add-ons policy introduced for Mozilla browser in all newer versions. 
-
-	* **Chrome** - Download the <a href="https://chrome.google.com/webstore/detail/telerik-test-studio-chrom/fhemhbheldeocfphcgnliopkkaapnclg">Telerik Test Studio Chrome Explore extension</a> and enable it to use the tool. 
-
-![Exploratory Testing][1]
-
-There are four buttons on the Explore tool:
-
-
-- Move - click and drag to reposition the tool anywhere on the screen, even outside of the browser.
-- <a href="/features/testing-types/exploratory-testing/provide-feedback" target="_blank">Feedback</a> - provide comments on a web page and submit your assessment.
-- Help - launch this page with your default browser.
-- Close - exit the tool.
-
-
-[1]: /img/features/testing-types/exploratory-testing/overview/fig1.png
\ No newline at end of file
diff --git a/docs/features/testing-types/exploratory-testing/provide-feedback.md b/docs/features/testing-types/exploratory-testing/provide-feedback.md
deleted file mode 100644
index f23e5983..00000000
--- a/docs/features/testing-types/exploratory-testing/provide-feedback.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Provide Feedback
-page_title: Provide Exploratory Testing Feedback
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/exploratory-testing/provide-feedback.aspx, /user-guide/exploratory-testing/provide-feedback
-position: 2
----
-# Provide Exploratory Testing Feedback
-
-
-Click the **Feedback** button to expand the tool, provide comments, and send your assessment.
-
-![Feedback][1]
-
-
-- Title - type a brief and helpful title.
-- Description - write a summary of the issue.
-- Tags - flag your feedback:
-	- Bug - configure a <a href="/features/integration/bug-tracking/Configuration" target="_blank">Bug Tracking</a> application to submit a bug on export.
-	- Important - indicates high priority.
-	- Idea - indicates a suggestion for improvement.
-- Details - automatically attach the following hard-coded information:
-	- Application - the process name of the current browser.
-	- Window - the title of the browser window.
-	- Date & Time - taken when the Feedback button was pressed.
-- Screenshot - include a browser image with notes:
-	- Capture - take a screen shot of the entire browser.
-	- Save - save the current capture.
-	-Annotate - add a rectangular shape, text comment, and change the color of each.
-
-
-Once finished, click Send and choose how to share your feedback: 
-
-![Send][2]
-
-
-- Email - send a message using the default system email client. The subject, body, and attachment are filled in.
-- Export - save a Microsoft Word or HTML document containing the feedback to disk.
-- Submit as Bug - load the <a href="/features/integration/bug-tracking/submit-bug" target="_blank">Submit Bug</a> dialog and log a bug in your previously configured bug tracking application.
-
-
-[1]: /img/features/testing-types/exploratory-testing/provide-feedback/fig1.png
-[2]: /img/features/testing-types/exploratory-testing/provide-feedback/fig2.png
\ No newline at end of file
diff --git a/docs/features/testing-types/manual-testing/convert-automated.md b/docs/features/testing-types/manual-testing/convert-automated.md
index 748c0c99..5abe818b 100644
--- a/docs/features/testing-types/manual-testing/convert-automated.md
+++ b/docs/features/testing-types/manual-testing/convert-automated.md
@@ -2,7 +2,7 @@
 title: Convert to Automated
 page_title: Convert to Automated
 description: "Convert manual Test Studio test to an automated one."
-previous_url: /user-guide/manual-testing/convert-to-automated.aspx, /user-guide/manual-testing/convert-to-automated
+
 position: 4
 ---
 # Convert Manual Test to an Automated
diff --git a/docs/features/testing-types/manual-testing/fast-forward.md b/docs/features/testing-types/manual-testing/fast-forward.md
index e942b3b4..d49afa2e 100644
--- a/docs/features/testing-types/manual-testing/fast-forward.md
+++ b/docs/features/testing-types/manual-testing/fast-forward.md
@@ -2,7 +2,6 @@
 title: Fast Forward Test
 page_title: Fast Forward Manual Test 
 description: "Fast Forward Test Run of a manual test in Test Studio."
-previous_url: /user-guide/manual-testing/fast-forward-test.aspx, /user-guide/manual-testing/fast-forward-test
 position: 3
 ---
 # Fast Forward Test
diff --git a/docs/features/testing-types/manual-testing/import-export.md b/docs/features/testing-types/manual-testing/import-export.md
index 85854091..57f93728 100644
--- a/docs/features/testing-types/manual-testing/import-export.md
+++ b/docs/features/testing-types/manual-testing/import-export.md
@@ -2,7 +2,6 @@
 title: Import and Export Excel Workbooks
 page_title: Import and Export Excel Workbooks
 description: "Import and Export Excel Workbooks for manual tests / manual test steps in Test Studio."
-previous_url: /user-guide/manual-testing/import_and_export_excel.aspx, /user-guide/manual-testing/import_and_export_excel
 position: 5
 ---
 # Import and Export Excel Data
diff --git a/docs/features/testing-types/manual-testing/overview.md b/docs/features/testing-types/manual-testing/overview.md
index 73bb5ca0..c2f45e0d 100644
--- a/docs/features/testing-types/manual-testing/overview.md
+++ b/docs/features/testing-types/manual-testing/overview.md
@@ -2,7 +2,6 @@
 title: Overview
 page_title: Manual Testing
 description: "Manual Testing in Test Studio."
-previous_url: /user-guide/manual-testing.aspx, /user-guide/manual-testing
 position: 1
 ---
 # Manual Testing
diff --git a/docs/features/testing-types/manual-testing/start-test.md b/docs/features/testing-types/manual-testing/start-test.md
index f91f1361..b348b878 100644
--- a/docs/features/testing-types/manual-testing/start-test.md
+++ b/docs/features/testing-types/manual-testing/start-test.md
@@ -2,7 +2,6 @@
 title: Start a Manual Test
 page_title: Start a Manual Test
 description: "Start a Manual Test in Test Studio."
-previous_url: /user-guide/manual-testing/start-a-manual-test.aspx, /user-guide/manual-testing/start-a-manual-test
 position: 2
 ---
 # Start a Manual Test
diff --git a/docs/getting-started/analyze-the-results.md b/docs/getting-started/analyze-the-results.md
index 5b4b2a17..64fa436d 100644
--- a/docs/getting-started/analyze-the-results.md
+++ b/docs/getting-started/analyze-the-results.md
@@ -30,7 +30,7 @@ The <a href="/general-information/test-results/analyze-quick-run-results" target
 
 The results generated from a <a href="/general-information/test-execution/quick-execution" target="_blank">quick execution run</a> will be displayed in the test pane - the successfully executed steps are marked with a green circle and the failed steps are marked with a red circle in front of it.
 
-<table id=no-table>
+<table id="no-table" style="border:none;">
 <colgroup>
         <col width="30%" />
         <col width="30%" />
@@ -45,7 +45,7 @@ The results generated from a <a href="/general-information/test-execution/quick-
 		<td style="text-align:center;">__Step Failed__</td>
 	</tr>
 	</tbody>
-<table>
+</table>
 
 Each failed step provides additional details for the failure, if you hover over the red circle in front of it. By clicking on that red crossed circle, you open the <a href="/general-information/test-results/step-failure-details" target="_blank">**Step Failure Details**</a> dialog. You can see detailed message for the failure, screenshots for the expected image and image at the time of failure, the DOM tree at the time of failure and suggestion how to solve the error.
 
diff --git a/docs/getting-started/first-project.md b/docs/getting-started/first-project.md
index 5515c037..0c68299f 100644
--- a/docs/getting-started/first-project.md
+++ b/docs/getting-started/first-project.md
@@ -22,7 +22,7 @@ Once you have successfully <a href="/prerequisites/installation/install-procedur
 <br><br>
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 > __Tip__
@@ -67,13 +67,13 @@ The <a href="/general-information/start-a-project/welcome-screen#get-started" ta
 
 Creating your first Test Studio project launches the default _Compact_ layout. This consists of useful panels providing a bunch of useful components. To speed up your flawless work with Test Studio, you can refer the below notes for each of these.
 
-- <a href="/features/project-explorer/overview" target="_blank">__Project Explorer__</a> - this is the pane, which displays the structure of the project with all tests, coded files, folders in the project root folder. Provides access to the items properties, allows you to copy, cut and paste these, add new items, etc.
-- <a href="/features/elements-explorer/overview" target="_blank">__Elements Explorer__</a> - this is the pane, which shows all elements referred from the test steps in the project, structured in a tree view, which includes page node, frame, element. Provides access to the elements' find expressions and properties, allows you to edit these.
-- <a href="/features/test-maintenance/steps-pane" target="_blank">__Edit Project Items Pane__</a> - this is the pane, which shows the selected component (test, element, coded file) and allows you to edit it.
-- <a href="/features/coded-steps/output-panel" target="_blank">__Output Pane__</a> - this is the pane, which displays different messages related to your work in the project - syntax or compilation errors when adding code snippets, or messages in regards the Source Control related actions.
-- <a href="/general-information/test-recording/step-suggestions" target="_blank">__Step Builder__</a> - this is the pane, which allows you to add different steps in the tests even if no recording session is currently active.
-- __Properties Pane__ - this is the pane to list the properties of the currently selected item (test, step, element, page node, frame) and allows you to edit these.
-- __Tools Ribbon__ - the Tools Ribbon provides access to various settings in regards the active tab in the project.
+- <a href="/features/project-explorer/overview" target="_blank">Project Explorer</a> - this is the pane, which displays the structure of the project with all tests, coded files, folders in the project root folder. Provides access to the items properties, allows you to copy, cut and paste these, add new items, etc.
+- <a href="/features/elements-explorer/overview" target="_blank">Elements Explorer</a> - this is the pane, which shows all elements referred from the test steps in the project, structured in a tree view, which includes page node, frame, element. Provides access to the elements' find expressions and properties, allows you to edit these.
+- <a href="/features/test-maintenance/steps-pane" target="_blank">Edit Project Items Pane</a> - this is the pane, which shows the selected component (test, element, coded file) and allows you to edit it.
+- <a href="/features/coded-steps/output-panel" target="_blank">Output Pane</a> - this is the pane, which displays different messages related to your work in the project - syntax or compilation errors when adding code snippets, or messages in regards the Source Control related actions.
+- <a href="/general-information/test-recording/step-suggestions" target="_blank">Step Builder</a> - this is the pane, which allows you to add different steps in the tests even if no recording session is currently active.
+- Properties Pane - this is the pane to list the properties of the currently selected item (test, step, element, page node, frame) and allows you to edit these.
+- Tools Ribbon - the Tools Ribbon provides access to various settings in regards the active tab in the project.
 
 ![Project Layout](/img/getting-started/first-project/project-components.png)
 
@@ -94,12 +94,16 @@ One Test Studio project allows you to include different types of tests:
 - <a href="/automated-tests/performance/overview" target="_blank">__Manual Test__</a> - a test in which you can add steps to manually execute against any application. This can be converted to a web test if automating a web page.
 - __Performance Test__ - a Performance test is always related to a valid web test and is being executed on top of this.
 
-<table id=no-table>
-	<tr>
-		<td>![Add new Test from Ribbon](/img/getting-started/first-project/add-new-test1.png) <td>
-		<td>![Add new Test from Project root](/img/getting-started/first-project/add-new-test2.png)</td>
-	</tr>
-<table>
+<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+		<td>
+		
+![Add new Test from Ribbon](/img/getting-started/first-project/add-new-test1.png) <td>
+<td>
+
+![Add new Test from Project root](/img/getting-started/first-project/add-new-test2.png)</td>
+</tr>
+</table>
 
 ## Types of Files in Test Studio Project
 
diff --git a/docs/getting-started/first-test.md b/docs/getting-started/first-test.md
index 39fb844b..5391e59a 100644
--- a/docs/getting-started/first-test.md
+++ b/docs/getting-started/first-test.md
@@ -94,12 +94,16 @@ The click-and-record functionality in Test Studio is designed to record the user
 
 6. The configured application - WPF or Desktop - starts and once it is loaded entirely the <a href="/features/recorder/compact-recording-toolbar" target="_blank">__Test Studio Compact Recording Toolbar__</a> gets attached to it.
 
-    <table id="no-table">
-    <tr>
-    <td> ![Attached recorder WPF app][9] <br><br>Recording WPF Application</td>
-    <td> ![Attached recorder desktop app][10] <br><br>Recording Desktop Application</td>
-    <tr>
-    <table>
+    <table id="no-table" style="border:none;">
+    <tr style="text-align: center; background-color: transparent; border:none;">
+    <td>
+    
+![Attached recorder WPF app][9] <br><br>Recording WPF Application</td>
+<td>
+    
+![Attached recorder desktop app][10] <br><br>Recording Desktop Application</td>
+<tr>
+</table>
 
 7. To __stop the recording session__, close the application instance (browser, desktop or WPF) with the attached Recording Toolbar.
 
diff --git a/docs/getting-started/installation-and-activation.md b/docs/getting-started/installation-and-activation.md
deleted file mode 100644
index ea36713b..00000000
--- a/docs/getting-started/installation-and-activation.md
+++ /dev/null
@@ -1,156 +0,0 @@
----
-title: Installation and Activation
-page_title: Getting started with installing Test Studio
-description: "A step by step guide on how to download, install and activate Test Studio."
-position: 1
-publish: false
----
-# Installation and Activation #
-
-This article explains how to download, install and activate Telerik Test Studio. The process consists of the following steps:
-
-1. [Download Test Studio](#download-test-studio)
-2. [Install Test Studio](#install-test-studio)
-3. [Activate Your License](#activate-your-license)
-
-## Download Test Studio ##
-The easiest way to download the latest version of Test Studio is from <a href=https://www.telerik.com/teststudio target="_blank">the official website</a>.
-
-![Download](/img/getting-started/installation-and-activation/fig00.png)
-
-You can also download Test Studio from your telerik.com account.
-
-1. Navigate to <a href="http://www.telerik.com" target="_blank">Telerik.com</a> and login to your Telerik account.
-
-	![Log In](/img/getting-started/installation-and-activation/fig01.png)
-	
-	![Log In](/img/getting-started/installation-and-activation/fig02.png)
-
-2. To download the latest version of Test Studio, including Service Packs and Latest Internal Builds, open the Manage products menu and select Test Studio.
-
-	![Test Studio product](/img/getting-started/installation-and-activation/fig03.png)
-
-3. From the Test Studio product page, click the __Download__ link.
-
-	![Download](/img/getting-started/installation-and-activation/fig04.png)
-
-4. Select the official release or latest internal build. Download the installer and execute the file to install that version or upgrade an existing Test Studio installation to the newer version.
-
-	![Install](/img/getting-started/installation-and-activation/fig05.png)
-
-## Install Test Studio ##
-
-1. After you have [downloaded the install file](#download-test-studio), locate it using Windows Explorer and double click it to launch the installer.
-2. Click the __Read License Agreement__ to read the  <a href="http://www.telerik.com/purchase/license-agreement/teststudio" target="_blank">Test Studio EULA</a>. When ready click __OK__ and then __I Agree – Continue__ button to confirm you agree with the terms of the license.
-
-	![Setup Wizzard](/img/getting-started/installation-and-activation/fig06.png)
-
-3. To take the defaults, click __Install__ and skip to step 6. Otherwise click the __Customize__ button. <br><br>**Note**: This button is not available when you download the *.exe installer directly from our site. In order to access it you should download the *.msi installer from your Telerik.com account.
-
-	![Install](/img/getting-started/installation-and-activation/fig07.png)
-
-4. Once you select the __Customize__ button, you can choose whether to install some optional components or to change the installation path. After making your selections, click __OK__ to continue
-
-	* To use this machine as a Storage Server and/or Scheduling Server, you need to install the appropriate services at this time or [add these at a later moment](/general-information/installation/add-services).
-	* To add the Storage and Scheduling Services features, <a href="/general-information/installation/add-services" target="_blank">you must complete the installation and perform a change using the installer</a>.
-	* Storage server uses <a href="https://www.mongodb.com" target="_blank">MongoDb</a> as storage database and its minimum requirement is 4GB hard drive space to operate normally.
-	* If you have Visual Studio on the machine, Test Studio plugin for Visual Studio will be also installed for all detected Visual Studio installations.
-
-	![Install services](/img/getting-started/installation-and-activation/fig08.png)
-
-	![Install services](/img/getting-started/installation-and-activation/fig09.png)
-
-	![Install VS plugin](/img/getting-started/installation-and-activation/fig10.png)
-
-5. Review the custom selections and click __OK__ and then __Install__ to start the installation process.
-
-	![Installing](/img/getting-started/installation-and-activation/fig11.gif)
-
-6. When the install is complete, the __Installation Successful__  screen is displayed.
-
-	![Successfully Completed](/img/getting-started/installation-and-activation/fig12.png)
-
-7. Click __Finish__ to exit the installation.
-
-	* Note: When upgrading, users may encounter an error: "Service 'Telerik Scheduling Service' (Telerik Scheduling Service) failed to start. Verify that you have sufficient privileges to start system services." See <a href="/troubleshooting-guide/installation-problems-tg/error-starting-services" target="_blank">Error Starting Services troubleshooting article</a>.
-
-Once you have installed Test Studio, you can <a href="/general-information/installation/check-for-updates" target="_blank">check for updates automatically</a>, or download and install them manually.
-
-## Activate Your License ##
-
-After installing Telerik <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a>, you will be asked to activate your license. During this process, your machine creates its own unique key and provides it to our server. We use this key to generate a unique license key for the installation of the product. This tutorial below describes how to go through this process and provides a guided walk-through. All users, both trial and purchased, will need to activate their product after installation before they can begin using the tool.
- 
-The below process assumes that you have not launched the Standalone or VS plugin version after the installation completed. If you have already launched Test Studio and are ready to input your licensing data (user email and password), skip to step 3.
-
-1. Launch Test Studio:
-	* __Standalone version__: Click Start > Programs > Telerik > Test Studio > Launch Test Studio
-	* __Visual Studio plugin__: Click Start > Programs > Microsoft Visual Studio 20XX > Microsoft Visual Studio 20XX
-	
-
-2. This step is for VS plugin users only. Standalone users can skip to step 3. If you have a project with a Test Studio test in it, open the project within Visual Studio, and then the test. If you do not have a solution or project of this type, perform steps 1-3 listed here to begin activation.
-	
-3. Input the email address and password that correspond to your <a href="https://www.telerik.com/login/v2/telerik?returnurl=%2f" target="_blank">Telerik.com</a> account.
-
-	![Log In screen](/img/getting-started/installation-and-activation/fig13.png)
-
-4.	Click __Login.__
-
-5.	Chose your purchased version and click __Activate Selected Version__ (please note that you can change your version later on).
-
-	![Choose version](/img/getting-started/installation-and-activation/fig14.png)
-
-6.	If you are activating purchased version and you have more than one purchases you will have to choose which license to activate. __NOTE: The following screen does NOT appear if you are activating trial version or have only one purchase.__
-
-	![Choose license](/img/getting-started/installation-and-activation/fig15.png)
-
-7.	Click __Activate Selected License.__ If the activation is successful the you can start using Test Studio.
-
-    ![Activation successful](/img/getting-started/installation-and-activation/fig16.png)
-
-8.	If your machine was freshly imaged or replaced and you need to re-activate your license (__0 seats available__) on the new machine, please visit <a href="/general-information/installation/re-activating-your-license" target="_blank">Re-Activating your License</a> article.
-
-9.	If you perform the above process and you receive the screen below, click on Activate Manually and follow this article for <a href="/general-information/installation/manual-activation" target="_blank">Manual Activation</a>.
-
-	![Couldn't log](/img/getting-started/installation-and-activation/fig17.png)
-
-
-<div><a style="float:right" href="/getting-started/first-project">Go to <strong>Your First Project</strong></a></div>
-
-
-## Test Execution ##
-
-It is time to execute the recorded test or <a href="/general-information/test-execution/test-lists-standalone" target="_blank">test list</a> and observer the execution process. At the end of the execution, you will see which step passed and which failed, along with <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log" target="_blank">the execution log</a>.
-
-> __Note!__ While a test is being executed, **do not start another instance of the same browser or any other application** until the run is finished!
-
-1. Once a test scenario is already recorded, click the **Execute** button in the Test ribbon.
-
-    ![Test Studio](/img/getting-started/first-project/fig08.png)
-
-2. Select Internet Explorer as the execution browser and click **Run**. This step will be skipped if you have already set a preferred browser from the <a href="/general-information/test-execution/quick-execution" target="_blank">Web ribbon</a>.
-
-    ![Select browser](/img/getting-started/first-project/fig09.png)
-
-3. The Test Studio Test Runner first launches a command prompt window and opens the selected browser.
-
-    ![Test Runner](/img/getting-started/first-project/fig10.png)
-
-4. By default in the lower right of your screen there is a ribbon which indicates the current step, includes play and pause ability, and shows additional Debug Options if you set a <a href="/features/test-maintenance/steps-pane" target="_blank">Breakpoint to any step</a>. This is the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger" target="_blank">visual debugger</a> and is a feature you could turn on or off.
-
-    ![Visual Debugger Indicator](/img/getting-started/first-project/fig11.png)
-
-    Click **Debugging Options** icon in the Test ribbon or the Visual Studio toolbar to turn the debugger on/off and customize the Auto-Pause Options, if errors occur during the execution.
-
-    ![Test Studio](/img/getting-started/first-project/fig12.png)
-
-5. Enable the **Toggle Annotation** button to have the browser annotate each step with a brief message and by highlighting that step's element. This will also slow the test run by the configured amount (in milliseconds) between each step. You can set it either from the menu or by entering a custom value.
-
-    ![Toggle Annotation](/img/getting-started/first-project/fig13.png)
-
-## Execution Results ##
-
-When the test execution is complete, there will be an indication for each step if it *Passed* or *Failed*. Test results are automatically generated and details can be reviewed by clicking on **View Log**. 
-
-![View log](/img/getting-started/first-project/fig14.png)
-
-The results from test list executions are available in the **Results** tab.
\ No newline at end of file
diff --git a/docs/getting-started/next-steps.md b/docs/getting-started/next-steps.md
index 1be295a1..6a563b55 100644
--- a/docs/getting-started/next-steps.md
+++ b/docs/getting-started/next-steps.md
@@ -9,36 +9,36 @@ position: 5
 The successful recording and execution of your first test is just the beginning. There are many features that will help you get your automation project to the next level. The documentation is full of details and examples to guide you. Here are some of the most important features in Test Studio:
 
 * The [**Recorder**](/features/recorder/overview) allows you to easily add actions and verifications to the test.
-<br/><br/>
+
 * The [**Elements Explorer**](/features/elements-explorer/overview) shows you all elements in the project and allows you to edit their find logic and filters.
-<br/><br/>
+
 * Different [**Testing Types**](/features/testing-types) can be part of the same project.
-<br/><br/>
+
 * [**Data Driven Testing**](/features/data-driven-testing/overview) uses external data source and executes the test repeatedly for each value.
-<br/><br/>
+
 * [**Dialog Handling**](/features/dialogs-and-popups/dialogs) feature covers all alert, confirm, logon, prompt, file upload and download dialogs.
-<br/><br/>
+
 * [**Test Lists**](/general-information//test-execution/test-list-execution) are collections of test that can be executed as scheduled jobs, both locally and on remote machines.
-<br/><br/>
+
 * [**Scheduling Test Runs**](/features/scheduling-test-runs/overview) on remote execution servers.
-<br/><br/>
+
 * The [**Results Tab**](/general-information/test-results/analyze-test-list-results) provides overview of the executed test lists. You can drill down and investigate the individual test steps.
-<br/><br/>
-* Test Studio supports different [**Continuous Integration and Deployment (CD/CI)**](/advanced-topics/build-server/continious-integration-overview.html) tools and allows you to execute tests when the build completes.
-<br/><br/>
+
+* Test Studio supports different [**Continuous Integration and Deployment (CD/CI)**](/automated-tests/continuous-integration/continious-integration-overview) tools and allows you to execute tests when the build completes.
+
 * [**Custom Step from Step Builder**](/features/custom-steps/overview) is for manually adding a specific step or condition to the test.
-<br/><br/>
+
 * [**Project Settings**](/features/project-settings/overview) have many configurable option to optimize your project performance.
-<br/><br/>
+
 * [**Logical Steps**](/features/logical-steps/if-else) like *If...Else*, *Loop* and *While...Loop* allow you to automate complex scenarios.
-<br/><br/>
+
 * [**Source Control**](/features/source-control/checkin-guidelines) integration with Git and TFS.
-<br/><br/>
+
 * [**Coded Steps**](/features/coded-steps/coded-step) allow you to use your custom code in C# or Visual Basic.
-<br/><br/>
+
 * Enchance you web tests with nested [**API Test as Step**](/features/execute-apitest/add-api-test-as-step).
-<br/><br/>
+
 * [**Mobile Testing**](/test-studio-mobile/overview) is another project type in Test Studio, where you can automate different Android and iOS application.
-<br/><br/>
+
 
 <div><a href="/getting-started/analyze-the-results">Back to <strong>Review The Results and Debug Test Failures</strong></a></div>
\ No newline at end of file
diff --git a/docs/guide/Telerik_Test_Studio_Quick_Start_Guide.pdf b/docs/guide/Telerik_Test_Studio_Quick_Start_Guide.pdf
old mode 100644
new mode 100755
diff --git a/docs/images/2.png b/docs/images/2.png
old mode 100644
new mode 100755
diff --git a/docs/images/anchor.png b/docs/images/anchor.png
old mode 100644
new mode 100755
diff --git a/docs/images/api.png b/docs/images/api.png
old mode 100644
new mode 100755
diff --git a/docs/images/arrow.png b/docs/images/arrow.png
old mode 100644
new mode 100755
diff --git a/docs/images/avatar-ninja.svg b/docs/images/avatar-ninja.svg
new file mode 100755
index 00000000..d98c1b20
--- /dev/null
+++ b/docs/images/avatar-ninja.svg
@@ -0,0 +1 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" width="109.579" height="100" viewBox="0 0 109.579 100"><defs><style>.a{fill:#a3d8f1;}.b{fill:#fff;}.c{fill:#e3f6ff;}.d{fill:#8174f2;}.e{clip-path:url(#a);}.f,.h,.i,.k{fill:none;}.f{stroke:#0c1b38;stroke-width:30px;}.f,.i,.k{stroke-linecap:round;}.f,.h{stroke-miterlimit:10;}.g{fill:#4f5d6c;}.h{stroke:#000;stroke-width:24.468px;}.i{stroke:#0c1121;stroke-width:20.645px;}.i,.k{stroke-linejoin:round;}.j{fill:#0c1121;}.k{stroke:#14254c;stroke-width:45.877px;}.l{fill:#0c1b38;}.m{fill:#e9ac6a;}.n{fill:#e26841;}</style><clipPath id="a"><ellipse class="a" cx="50" cy="50" rx="50" ry="50" transform="translate(-11251.149 -21710)"/></clipPath></defs><path class="b" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><path class="c" d="M50,0A50,50,0,1,1,0,50,50,50,0,0,1,50,0Z" transform="translate(9.579)"/><g transform="translate(0 12.775)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g class="e" transform="translate(11260.729 21710)"><g transform="translate(-12096.358 -23981.338)"><path class="f" d="M3158.423,2368.839c36.843.145,65.382-23.7,68.744-50.983,3-24.348-15.059-43.243-18.055-46.286" transform="translate(-2234.18 -19.121)"/><g transform="translate(939.33 2257.389)"><path class="g" d="M3203.488,2283.094l7.821,11.323-.855,1.8-20.468,1.627-11.668-16.894.855-1.8,13.4-1.065Z" transform="translate(-3178.317 -2278.085)"/></g><g transform="translate(950.734 2192.443)"><path class="g" d="M3222.208,2230.646l14.987-31.541a2.648,2.648,0,0,0-1.258-3.526l-6.063-2.879a2.647,2.647,0,0,0-3.528,1.252l-32.99,69.127,10.849,5.154,6.518-13.412Z" transform="translate(-3193.356 -2192.443)"/></g><g transform="translate(951.545 2227.636)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.991,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 22.12) rotate(-65.013)"/></g><line class="h" x1="0.724" y2="27.18" transform="translate(844.735 2493.343)"/><path d="M3155.778,2444.706l1.234-32.591a34.077,34.077,0,0,0-38.951-35.012h0a34.077,34.077,0,0,0-27.836,43.189l9.06,31.33a28.825,28.825,0,0,0,30.725,20.658h0A28.824,28.824,0,0,0,3155.778,2444.706Z" transform="translate(-2217.373 -44.536)"/><path class="i" d="M2905.35,2587.494l-49.786,32.326" transform="translate(-2160.994 -95.464)"/><path class="j" d="M3142.522,2628.677a7.968,7.968,0,0,0,8.055,8.435l3.028-.039,27.262-.343a4.921,4.921,0,0,0,.692-9.783l-14.5-2.532-14.975-3.078a7.969,7.969,0,0,0-9.56,7.34Z" transform="translate(-2230.335 -103.603)"/><path class="j" d="M2851.56,2628.677a7.969,7.969,0,0,1-8.055,8.435l-3.028-.039-27.262-.343a4.921,4.921,0,0,1-.693-9.783l14.5-2.532,14.975-3.078a7.968,7.968,0,0,1,9.56,7.34Z" transform="translate(-2149.586 -103.603)"/><path class="i" d="M3210.51,2580.636q-9.805,7.145-20.237,14.306-19.106,13.1-37.478,24.294" transform="translate(-2232.82 -93.807)"/><path class="k" d="M3153.983,2510.447c2.631-.136,5.669-.226,9.057-.2,5.714.044,20.339.235,34.771,4.322,13.86,3.926,28.827,8.165,31.9,17.693,3.67,11.374-9.988,29.089-34.05,42.144" transform="translate(-2233.107 -76.797)"/><path class="k" d="M3064.752,2503.885a530.633,530.633,0,0,0-167.838,72.336" transform="translate(-2170.987 -75.261)"/><g transform="translate(900.392 2433.461)"><path class="j" d="M3126.972,2510.262" transform="translate(-3126.972 -2510.262)"/></g><path d="M3177.856,2483.313l-61.336-19.153h0q-15.026,5.272-30.776,10.39-18.815,6.107-36.943,11.419a72.634,72.634,0,0,0,129.055-2.656Z" transform="translate(-2207.69 -65.661)"/><rect class="d" width="57.81" height="19.325" transform="matrix(-0.988, 0.157, -0.157, -0.988, 942.407, 2422.056)"/><g transform="translate(835.308 2508.631)"><path d="M8.291,0h7.822A8.291,8.291,0,0,1,24.4,8.291v4.952A11.413,11.413,0,0,1,12.992,24.656H11.365A11.365,11.365,0,0,1,0,13.291v-5A8.291,8.291,0,0,1,8.291,0Z" transform="translate(0 0.347) rotate(-0.814)"/></g><path class="f" d="M3089.63,2423.256a159.413,159.413,0,0,0-27.3,48.023,161.1,161.1,0,0,0-7.566,76.309" transform="translate(-2208.744 -55.776)"/><g transform="translate(835.63 2284.113)"><path class="d" d="M3069.323,2321.46c-4.692-5.069-5.845-9.417-7.486-11.886-3.02-4.542-11.533-8.116-35.858-3.554q.551,5.872,1.1,11.746c18.109-6.134,26.13-3.972,30.034-.445,1.776,1.6,3.541,4.037,7.484,6.616a25.081,25.081,0,0,0,12.894,3.849A32.051,32.051,0,0,1,3069.323,2321.46Z" transform="translate(-3025.979 -2303.904)"/><path class="d" d="M3025.979,2333.547v10.646c11.927-6.4,20.09-6.311,25.405-4.964,3.669.93,7.343,2.455,13.071,2.433a21.891,21.891,0,0,0,12.15-4.112,32.467,32.467,0,0,1-13.671-2.619c-4.782-2.1-7.1-3.994-9.546-5.285C3048.781,2327.215,3040.771,2326.18,3025.979,2333.547Z" transform="translate(-3025.979 -2313.077)"/></g><g transform="translate(873.087 2289.57)"><path class="l" d="M3114.193,2320.557l-2.984.175a21.267,21.267,0,0,0-19.861,23.857l2.83,22.75a21.268,21.268,0,0,0,22.349,18.605h0a21.268,21.268,0,0,0,20.024-21.088l.154-22.924A21.268,21.268,0,0,0,3114.193,2320.557Z" transform="translate(-3091.019 -2320.52)"/><rect class="d" width="45.527" height="11.326" transform="translate(46.111 27.879) rotate(176.647)"/><rect class="m" width="39.681" height="11.634" rx="5.817" transform="translate(43.547 34.093) rotate(176.647)"/><path class="n" d="M3117.6,2364.1l5.041-.3-.568-9.691Z" transform="translate(-3097.402 -2328.638)"/><g transform="translate(7.384 26.937)"><rect class="b" width="6.105" height="3.243" rx="1.622" transform="matrix(-0.998, 0.058, -0.058, -0.998, 6.284, 4.693)"/><rect class="b" width="6.105" height="3.243" rx="1.622" transform="translate(31.121 3.237) rotate(176.647)"/></g><circle cx="1.643" cy="1.643" r="1.643" transform="translate(7.477 28.64)"/><circle cx="1.643" cy="1.643" r="1.643" transform="translate(32.314 27.185)"/></g></g></g></svg>
\ No newline at end of file
diff --git a/docs/images/close.png b/docs/images/close.png
old mode 100644
new mode 100755
diff --git a/docs/images/column.png b/docs/images/column.png
old mode 100644
new mode 100755
diff --git a/docs/images/getting-started.png b/docs/images/getting-started.png
old mode 100644
new mode 100755
diff --git a/docs/images/howdoi.png b/docs/images/howdoi.png
old mode 100644
new mode 100755
diff --git a/docs/images/icon-telerik-badge.png b/docs/images/icon-telerik-badge.png
old mode 100644
new mode 100755
diff --git a/docs/images/important.png b/docs/images/important.png
old mode 100644
new mode 100755
diff --git a/docs/images/logo.png b/docs/images/logo.png
old mode 100644
new mode 100755
diff --git a/docs/images/menu.png b/docs/images/menu.png
old mode 100644
new mode 100755
diff --git a/docs/images/nav-arrow.png b/docs/images/nav-arrow.png
old mode 100644
new mode 100755
diff --git a/docs/images/ninja-icon.png b/docs/images/ninja-icon.png
old mode 100644
new mode 100755
diff --git a/docs/images/ninja-no-results.svg b/docs/images/ninja-no-results.svg
new file mode 100644
index 00000000..5d84ade5
--- /dev/null
+++ b/docs/images/ninja-no-results.svg
@@ -0,0 +1,47 @@
+<svg xmlns="http://www.w3.org/2000/svg" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.1" id="Layer_1" x="0px" y="0px" style="enable-background:new 0 0 2000 2000;" height="150px" width="106px" xml:space="preserve" viewBox="631.99 547.8 788.26 904.27">
+	<style type="text/css">
+		.st0{fill:none;stroke:#0B1122;stroke-width:47.0486;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st1{fill:#0B1122;}
+		.st2{fill:none;stroke:#14254C;stroke-width:104.5525;stroke-linecap:round;stroke-linejoin:round;stroke-miterlimit:10;}
+		.st3{fill:none;stroke:#0C1B38;stroke-width:78.4143;stroke-linecap:round;stroke-miterlimit:10;}
+		.st4{fill:#8174F2;}
+		.st5{fill:#0C1B38;}
+		.st6{fill:#E7AA6A;}
+		.st7{fill:#E26841;}
+		.st8{fill:#EEF5FF;}
+		.st9{fill:#4F5D6C;}
+	</style>
+	<g>
+		<path class="st0" d="M723.7,1237.5c11.8,47.5,23.5,95,35.3,142.5"/>
+		<path class="st1" d="M788.6,1383c1,16.7-12.4,30.8-29.2,30.6l-11-0.1l-98.8-1.2c-8.6-0.1-16-6.4-17.4-15.1   c-1.5-9.7,5.2-18.8,14.9-20.4l52.6-9.2l54.3-11.2C771.2,1352.8,787.6,1365.4,788.6,1383L788.6,1383z"/>
+		<path class="st2" d="M1034.1,1192.7c-103-137.5-230.5-179.8-283.3-141.7c-56.8,41-26.1,174.6-24,183.3"/>
+		<path class="st3" d="M1010.1,863.6c-105.4-13.1-192.5,68.8-191.7,156.2c0.7,74,64.5,144.9,152.1,154.2"/>
+		<path class="st3" d="M1108,863.6c105.4-13.1,192.5,68.8,191.7,156.2c-0.7,74-64.5,144.9-152.1,154.2"/>
+		<path d="M1204.6,1064.3l4.5-124.8c3-81.4-68-145.8-147.9-134.2l0,0c-77.6,11.3-127.2,89.2-105.4,165.2l34.5,120   c14.8,51.4,63.9,84.8,116.6,79.2h0C1161,1164,1202.6,1119.1,1204.6,1064.3z"/>
+		<path class="st1" d="M932.5,1322.1c-13.7-9.6-32.7-5.6-41.4,8.8l-5.6,9.4l-50.8,84.8c-4.4,7.3-3,17,3.7,22.7   c7.5,6.4,18.8,5.5,25.1-2L899,1406l38-40.3C949.1,1352.8,947,1332.2,932.5,1322.1L932.5,1322.1z"/>
+		<path class="st0" d="M1163.2,1330c-29.1,3.2-59,6.1-89.4,8.6c-55.8,4.5-109.7,7.4-161.7,8.9"/>
+		<path class="st2" d="M1139.4,1174.4c22.6-0.8,55-0.5,93.6,4.7c53.8,7.3,81.3,10.5,103.1,31.2c20.8,19.8,37.3,54.9,30.2,79.4   c-22.1,75.8-274.5,59.3-297.1,57.7"/>
+		<g>
+			<path class="st4" d="M1150.3,749.8c28.6-11.3,48.6-9.1,61.5-11.9c23.7-5.2,52.3-34.8,72.7-143.2c-16.9-4.8-33.7-9.6-50.6-14.4    c-3.8,85.1-25.7,115-46.6,125.5c-9.5,4.8-22.5,8.2-39.6,20.4c-20,14.3-30.8,33.5-36.8,47.4    C1119.2,766.5,1132.4,756.9,1150.3,749.8z"/>
+			<path class="st4" d="M1208.2,565c-14.7-5.7-29.5-11.5-44.2-17.2c7.3,59.9-6.2,93.7-20.4,113.6c-9.8,13.7-22.1,26.5-31.2,50.4    c-8.4,21.8-5.8,43-2.5,57.1c5.3-14.5,14.9-34.5,33-52.6c16.4-16.5,28.1-23.1,37.4-31.1C1197.7,670,1214.9,638.4,1208.2,565z"/>
+		</g>
+		<g>
+			<path class="st5" d="M1080.4,711.3l-10.8,0.4c-44.5,1.5-78.5,40.3-74.2,84.6l8.2,82.7c4,40.4,38.7,70.8,79.3,69.5h0    c40.6-1.3,73.2-34,74.5-74.6l2.7-83.1C1161.4,746.3,1124.9,709.8,1080.4,711.3z"/>
+			
+				<rect x="995.9" y="795.4" transform="matrix(-0.9994 3.316386e-02 -3.316386e-02 -0.9994 2183.395 1595.6785)" class="st4" width="165" height="41.1"/>
+			<path class="st6" d="M1012.5,860.6l132.4-4.4c3.1-0.1,5.6-2.7,5.5-5.9l-1-30.8c-0.1-3.1-2.7-5.6-5.9-5.5l-132.4,4.4    c-3.1,0.1-5.6,2.7-5.5,5.9l1,30.8C1006.7,858.2,1009.3,860.7,1012.5,860.6z"/>
+			<polygon class="st7" points="1065.8,858.8 1084.1,858.2 1082.9,823   "/>
+			<g>
+				<path class="st8" d="M1021.8,850.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1020.2,849.7,1021,850.4,1021.8,850.4z"/>
+				<path class="st8" d="M1112,847.4l18.9-0.6c0.9,0,1.6-0.8,1.5-1.6l-0.3-8.6c0-0.9-0.8-1.6-1.6-1.5l-18.9,0.6     c-0.9,0-1.6,0.8-1.5,1.6l0.3,8.6C1110.4,846.7,1111.1,847.4,1112,847.4z"/>
+			</g>
+			<circle cx="1031.7" cy="849.1" r="6"/>
+			<circle cx="1121.8" cy="846.1" r="6"/>
+		</g>
+		<g>
+			<rect x="906.3" y="1031.2" class="st9" width="371.7" height="269.2"/>
+			<rect x="906.3" y="1293.9" width="371.7" height="24.1"/>
+		</g>
+		<path class="st8" d="M1101.4,1157.7l-14.7-19.5l-2.1,17.8l-19.5,14.7l17.8,2.1l14.7,19.5l2.1-17.8l19.5-14.7L1101.4,1157.7z    M1091.7,1168.6c-1.8-0.2-3.1-1.9-2.9-3.7c0.2-1.8,1.9-3.1,3.7-2.9c1.8,0.2,3.1,1.9,2.9,3.7   C1095.2,1167.5,1093.5,1168.8,1091.7,1168.6z"/>
+	</g>
+</svg>
diff --git a/docs/images/open.png b/docs/images/open.png
old mode 100644
new mode 100755
diff --git a/docs/images/pdf-cover.png b/docs/images/pdf-cover.png
new file mode 100644
index 00000000..ce9967ef
Binary files /dev/null and b/docs/images/pdf-cover.png differ
diff --git a/docs/images/search.png b/docs/images/search.png
old mode 100644
new mode 100755
diff --git a/docs/images/tap-logo1.png b/docs/images/tap-logo1.png
old mode 100644
new mode 100755
diff --git a/docs/images/testStudioLogo.png b/docs/images/testStudioLogo.png
old mode 100644
new mode 100755
diff --git a/docs/images/testStudioLogoOLD2017.png b/docs/images/testStudioLogoOLD2017.png
old mode 100644
new mode 100755
diff --git a/docs/images/tutorials.png b/docs/images/tutorials.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig1.png b/docs/img/advanced-topics/build-server/azure-devops/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig10.png b/docs/img/advanced-topics/build-server/azure-devops/fig10.png
old mode 100644
new mode 100755
index 8b94d9ae..b3c9596a
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig10.png and b/docs/img/advanced-topics/build-server/azure-devops/fig10.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig11.png b/docs/img/advanced-topics/build-server/azure-devops/fig11.png
old mode 100644
new mode 100755
index 29349ec9..d39af8f7
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig11.png and b/docs/img/advanced-topics/build-server/azure-devops/fig11.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig12.png b/docs/img/advanced-topics/build-server/azure-devops/fig12.png
old mode 100644
new mode 100755
index ee5712da..f7b65446
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig12.png and b/docs/img/advanced-topics/build-server/azure-devops/fig12.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig13.png b/docs/img/advanced-topics/build-server/azure-devops/fig13.png
old mode 100644
new mode 100755
index 2e9f43ca..f2b0e511
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig13.png and b/docs/img/advanced-topics/build-server/azure-devops/fig13.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig14.png b/docs/img/advanced-topics/build-server/azure-devops/fig14.png
old mode 100644
new mode 100755
index 1a510c20..b5690011
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig14.png and b/docs/img/advanced-topics/build-server/azure-devops/fig14.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig15.png b/docs/img/advanced-topics/build-server/azure-devops/fig15.png
old mode 100644
new mode 100755
index d158ea3a..ceea7853
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig15.png and b/docs/img/advanced-topics/build-server/azure-devops/fig15.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig16.png b/docs/img/advanced-topics/build-server/azure-devops/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig17.png b/docs/img/advanced-topics/build-server/azure-devops/fig17.png
old mode 100644
new mode 100755
index 47fe6126..cd735ae7
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig17.png and b/docs/img/advanced-topics/build-server/azure-devops/fig17.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig18.png b/docs/img/advanced-topics/build-server/azure-devops/fig18.png
old mode 100644
new mode 100755
index 11c30376..c9f607dc
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig18.png and b/docs/img/advanced-topics/build-server/azure-devops/fig18.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig19.png b/docs/img/advanced-topics/build-server/azure-devops/fig19.png
old mode 100644
new mode 100755
index e0607004..31d0a9e9
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig19.png and b/docs/img/advanced-topics/build-server/azure-devops/fig19.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig2.png b/docs/img/advanced-topics/build-server/azure-devops/fig2.png
old mode 100644
new mode 100755
index 88568359..102e859b
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig2.png and b/docs/img/advanced-topics/build-server/azure-devops/fig2.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig20.png b/docs/img/advanced-topics/build-server/azure-devops/fig20.png
new file mode 100644
index 00000000..01358827
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig20.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig21.png b/docs/img/advanced-topics/build-server/azure-devops/fig21.png
new file mode 100644
index 00000000..db4f4c2f
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig21.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig22.png b/docs/img/advanced-topics/build-server/azure-devops/fig22.png
new file mode 100644
index 00000000..485c382e
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig22.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig23.png b/docs/img/advanced-topics/build-server/azure-devops/fig23.png
new file mode 100644
index 00000000..be17fed5
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig23.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig24.png b/docs/img/advanced-topics/build-server/azure-devops/fig24.png
new file mode 100644
index 00000000..4dec4f3c
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig24.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig25.png b/docs/img/advanced-topics/build-server/azure-devops/fig25.png
new file mode 100644
index 00000000..fdc16491
Binary files /dev/null and b/docs/img/advanced-topics/build-server/azure-devops/fig25.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig3.png b/docs/img/advanced-topics/build-server/azure-devops/fig3.png
old mode 100644
new mode 100755
index b76ef426..d4cec871
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig3.png and b/docs/img/advanced-topics/build-server/azure-devops/fig3.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig4.png b/docs/img/advanced-topics/build-server/azure-devops/fig4.png
old mode 100644
new mode 100755
index 75c29b43..ac0db547
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig4.png and b/docs/img/advanced-topics/build-server/azure-devops/fig4.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig5.png b/docs/img/advanced-topics/build-server/azure-devops/fig5.png
old mode 100644
new mode 100755
index eee862e6..b258a44a
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig5.png and b/docs/img/advanced-topics/build-server/azure-devops/fig5.png differ
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig6.png b/docs/img/advanced-topics/build-server/azure-devops/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig7.png b/docs/img/advanced-topics/build-server/azure-devops/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig8.png b/docs/img/advanced-topics/build-server/azure-devops/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/azure-devops/fig9.png b/docs/img/advanced-topics/build-server/azure-devops/fig9.png
old mode 100644
new mode 100755
index 05b5828d..96cfcca2
Binary files a/docs/img/advanced-topics/build-server/azure-devops/fig9.png and b/docs/img/advanced-topics/build-server/azure-devops/fig9.png differ
diff --git a/docs/img/advanced-topics/build-server/bamboo/Add_new_executable-TestStudio.png b/docs/img/advanced-topics/build-server/bamboo/Add_new_executable-TestStudio.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/Configure_plan.png b/docs/img/advanced-topics/build-server/bamboo/Configure_plan.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/Create_plan.png b/docs/img/advanced-topics/build-server/bamboo/Create_plan.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/JUnit_config.png b/docs/img/advanced-topics/build-server/bamboo/JUnit_config.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/New_JUnit_parser_task.png b/docs/img/advanced-topics/build-server/bamboo/New_JUnit_parser_task.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/New_command_task.png b/docs/img/advanced-topics/build-server/bamboo/New_command_task.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/New_script_task.png b/docs/img/advanced-topics/build-server/bamboo/New_script_task.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/Runner_command_task.png b/docs/img/advanced-topics/build-server/bamboo/Runner_command_task.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/Script_config.png b/docs/img/advanced-topics/build-server/bamboo/Script_config.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/fig1.png b/docs/img/advanced-topics/build-server/bamboo/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/fig2.png b/docs/img/advanced-topics/build-server/bamboo/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/fig3.png b/docs/img/advanced-topics/build-server/bamboo/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/bamboo/fig4.png b/docs/img/advanced-topics/build-server/bamboo/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/build-servers-test-execution/fig1.png b/docs/img/advanced-topics/build-server/build-servers-test-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/cruise-control.NET-builds/fig1.png b/docs/img/advanced-topics/build-server/cruise-control.NET-builds/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/cruise-control.NET-builds/fig2.png b/docs/img/advanced-topics/build-server/cruise-control.NET-builds/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/docker-container-testing/fig1.png b/docs/img/advanced-topics/build-server/docker-container-testing/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/docker-container-testing/fig2.png b/docs/img/advanced-topics/build-server/docker-container-testing/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/docker-container-testing/fig3.png b/docs/img/advanced-topics/build-server/docker-container-testing/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/docker-container-testing/fig4.png b/docs/img/advanced-topics/build-server/docker-container-testing/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig1.png b/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig2.png b/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig3.png b/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig4.png b/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig5.png b/docs/img/advanced-topics/build-server/jenkins-ci-plugin/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig1.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig10.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig11.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig12.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig13.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig2.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig3.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig4.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig5.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig6.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig7.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig8.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/jenkins-ci/fig9.png b/docs/img/advanced-topics/build-server/jenkins-ci/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig1.png b/docs/img/advanced-topics/build-server/mha-testing/fig1.png
old mode 100644
new mode 100755
index b2bba14f..e37bad04
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig1.png and b/docs/img/advanced-topics/build-server/mha-testing/fig1.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig10.png b/docs/img/advanced-topics/build-server/mha-testing/fig10.png
old mode 100644
new mode 100755
index e25eff56..825b409f
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig10.png and b/docs/img/advanced-topics/build-server/mha-testing/fig10.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig11.png b/docs/img/advanced-topics/build-server/mha-testing/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig12.png b/docs/img/advanced-topics/build-server/mha-testing/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig13.png b/docs/img/advanced-topics/build-server/mha-testing/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig14.png b/docs/img/advanced-topics/build-server/mha-testing/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig15.png b/docs/img/advanced-topics/build-server/mha-testing/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig16.png b/docs/img/advanced-topics/build-server/mha-testing/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig2.png b/docs/img/advanced-topics/build-server/mha-testing/fig2.png
old mode 100644
new mode 100755
index 9ca8e6bd..f7159528
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig2.png and b/docs/img/advanced-topics/build-server/mha-testing/fig2.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig3.png b/docs/img/advanced-topics/build-server/mha-testing/fig3.png
old mode 100644
new mode 100755
index f56ec4df..7e4a1452
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig3.png and b/docs/img/advanced-topics/build-server/mha-testing/fig3.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig4.png b/docs/img/advanced-topics/build-server/mha-testing/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig5.png b/docs/img/advanced-topics/build-server/mha-testing/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig6.png b/docs/img/advanced-topics/build-server/mha-testing/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig7.png b/docs/img/advanced-topics/build-server/mha-testing/fig7.png
old mode 100644
new mode 100755
index aa658c77..8c580c5f
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig7.png and b/docs/img/advanced-topics/build-server/mha-testing/fig7.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig8.png b/docs/img/advanced-topics/build-server/mha-testing/fig8.png
old mode 100644
new mode 100755
index 7273e24f..f29bb40c
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig8.png and b/docs/img/advanced-topics/build-server/mha-testing/fig8.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig9.png b/docs/img/advanced-topics/build-server/mha-testing/fig9.png
old mode 100644
new mode 100755
index 858a7aa8..5bdf1e00
Binary files a/docs/img/advanced-topics/build-server/mha-testing/fig9.png and b/docs/img/advanced-topics/build-server/mha-testing/fig9.png differ
diff --git a/docs/img/advanced-topics/build-server/mha-testing/fig9a.png b/docs/img/advanced-topics/build-server/mha-testing/fig9a.png
new file mode 100644
index 00000000..8a1ada6a
Binary files /dev/null and b/docs/img/advanced-topics/build-server/mha-testing/fig9a.png differ
diff --git a/docs/img/advanced-topics/build-server/mtm/fig1.png b/docs/img/advanced-topics/build-server/mtm/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig10.png b/docs/img/advanced-topics/build-server/mtm/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig11.png b/docs/img/advanced-topics/build-server/mtm/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig12.png b/docs/img/advanced-topics/build-server/mtm/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig13.png b/docs/img/advanced-topics/build-server/mtm/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig2.png b/docs/img/advanced-topics/build-server/mtm/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig3.png b/docs/img/advanced-topics/build-server/mtm/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig4.png b/docs/img/advanced-topics/build-server/mtm/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig5.png b/docs/img/advanced-topics/build-server/mtm/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig6.png b/docs/img/advanced-topics/build-server/mtm/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig7.png b/docs/img/advanced-topics/build-server/mtm/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig8.png b/docs/img/advanced-topics/build-server/mtm/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/mtm/fig9.png b/docs/img/advanced-topics/build-server/mtm/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/team-city-builds/New_Build_Feature.png b/docs/img/advanced-topics/build-server/team-city-builds/New_Build_Feature.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/team-city-builds/New_Build_config.png b/docs/img/advanced-topics/build-server/team-city-builds/New_Build_config.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/team-city-builds/New_build_step.png b/docs/img/advanced-topics/build-server/team-city-builds/New_build_step.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/team-city-builds/New_project.png b/docs/img/advanced-topics/build-server/team-city-builds/New_project.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig1.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig2.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig3.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig4.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig5.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig6.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig7.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-2017-builds/fig8.png b/docs/img/advanced-topics/build-server/tfs-2017-builds/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/tfs-builds/fig1.png b/docs/img/advanced-topics/build-server/tfs-builds/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/EmptyBuildDefinition.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/EmptyBuildDefinition.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig2.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig3.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig4.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig5.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig6.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig7.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig8.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/build-server/vs-team-services-builds/fig9.png b/docs/img/advanced-topics/build-server/vs-team-services-builds/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/access-sql-database/fig1.png b/docs/img/advanced-topics/coded-samples/general/access-sql-database/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/add-message-box/fig1.png b/docs/img/advanced-topics/coded-samples/general/add-message-box/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/browser-specific-actions/fig1.png b/docs/img/advanced-topics/coded-samples/general/browser-specific-actions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig1.png b/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig2.png b/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig3.png b/docs/img/advanced-topics/coded-samples/general/custom-scripts-before-after/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/data-source.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/data-source.png
new file mode 100644
index 00000000..86060df8
Binary files /dev/null and b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/data-source.png differ
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/explore-item-in-dom.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/explore-item-in-dom.png
new file mode 100644
index 00000000..0555a322
Binary files /dev/null and b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/explore-item-in-dom.png differ
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig1.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig1.png
deleted file mode 100644
index e6bb6ad6..00000000
Binary files a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig1.png and /dev/null differ
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig2.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig2.png
deleted file mode 100644
index e657a2e7..00000000
Binary files a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig2.png and /dev/null differ
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig3.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig3.png
deleted file mode 100644
index ae7809e4..00000000
Binary files a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/fig3.png and /dev/null differ
diff --git a/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/recorded-step-to-move-right.png b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/recorded-step-to-move-right.png
new file mode 100644
index 00000000..033f95a5
Binary files /dev/null and b/docs/img/advanced-topics/coded-samples/general/data-driven-find-expressions/recorded-step-to-move-right.png differ
diff --git a/docs/img/advanced-topics/coded-samples/general/extend-basewebaiitest-class/fig1.png b/docs/img/advanced-topics/coded-samples/general/extend-basewebaiitest-class/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/external-log-file/fig1.png b/docs/img/advanced-topics/coded-samples/general/external-log-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/get-project-path/fig1.png b/docs/img/advanced-topics/coded-samples/general/get-project-path/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/grayed-out-controls/fig1.png b/docs/img/advanced-topics/coded-samples/general/grayed-out-controls/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/log-error-dialogs/fig1.png b/docs/img/advanced-topics/coded-samples/general/log-error-dialogs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/non-iterative-data-driving/fig1.png b/docs/img/advanced-topics/coded-samples/general/non-iterative-data-driving/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/random-row/fig1.png b/docs/img/advanced-topics/coded-samples/general/random-row/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/random-row/fig2.png b/docs/img/advanced-topics/coded-samples/general/random-row/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/skip-iteration/fig1.png b/docs/img/advanced-topics/coded-samples/general/skip-iteration/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/skip-iteration/fig2.png b/docs/img/advanced-topics/coded-samples/general/skip-iteration/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/using-the-http-proxy/fig1.png b/docs/img/advanced-topics/coded-samples/general/using-the-http-proxy/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/write-into-data-source/fig2.png b/docs/img/advanced-topics/coded-samples/general/write-into-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/general/write-into-data-source/fig3.png b/docs/img/advanced-topics/coded-samples/general/write-into-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/common-find-expressions/fig1.png b/docs/img/advanced-topics/coded-samples/html/common-find-expressions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/common-find-expressions/fig2.png b/docs/img/advanced-topics/coded-samples/html/common-find-expressions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig1.png b/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig2.png b/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig3.png b/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig4.png b/docs/img/advanced-topics/coded-samples/html/dynamic-grid/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig1.png b/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig2.png b/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig3.png b/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig4.png b/docs/img/advanced-topics/coded-samples/html/jQuery-events-do-not-fire/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox/fig1.png b/docs/img/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/wpf/automate-clickonce-app/fig1.png b/docs/img/advanced-topics/coded-samples/wpf/automate-clickonce-app/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-samples/wpf/parameterize-wpf-app/fig1.png b/docs/img/advanced-topics/coded-samples/wpf/parameterize-wpf-app/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig1.png b/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig2.png b/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig3.png b/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig4.png b/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig5.png b/docs/img/advanced-topics/coded-steps/add-assembly-reference/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/code-behind-file/fig1.png b/docs/img/advanced-topics/coded-steps/code-behind-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/code-behind-file/fig2.png b/docs/img/advanced-topics/coded-steps/code-behind-file/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/code-behind-file/fig3.png b/docs/img/advanced-topics/coded-steps/code-behind-file/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/code-behind-file/fig4.png b/docs/img/advanced-topics/coded-steps/code-behind-file/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/coded-step/fig1.png b/docs/img/advanced-topics/coded-steps/coded-step/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/coded-step/fig2.png b/docs/img/advanced-topics/coded-steps/coded-step/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/coded-step/fig3.png b/docs/img/advanced-topics/coded-steps/coded-step/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/coded-step/fig4.png b/docs/img/advanced-topics/coded-steps/coded-step/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/convert-steps-code/fig1.png b/docs/img/advanced-topics/coded-steps/convert-steps-code/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/convert-steps-code/fig2.png b/docs/img/advanced-topics/coded-steps/convert-steps-code/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/convert-steps-code/fig3.png b/docs/img/advanced-topics/coded-steps/convert-steps-code/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/advanced-topics/coded-steps/preview-code/fig1.png b/docs/img/advanced-topics/coded-steps/preview-code/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig1.png b/docs/img/archived-docs/test-recording/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig10.png b/docs/img/archived-docs/test-recording/overview/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig11.png b/docs/img/archived-docs/test-recording/overview/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig12.png b/docs/img/archived-docs/test-recording/overview/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig13.png b/docs/img/archived-docs/test-recording/overview/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig14.png b/docs/img/archived-docs/test-recording/overview/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig15.png b/docs/img/archived-docs/test-recording/overview/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig15a.png b/docs/img/archived-docs/test-recording/overview/fig15a.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig2.png b/docs/img/archived-docs/test-recording/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig3.png b/docs/img/archived-docs/test-recording/overview/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig4.png b/docs/img/archived-docs/test-recording/overview/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig5.png b/docs/img/archived-docs/test-recording/overview/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig6.png b/docs/img/archived-docs/test-recording/overview/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig7.png b/docs/img/archived-docs/test-recording/overview/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig8.png b/docs/img/archived-docs/test-recording/overview/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/overview/fig9.png b/docs/img/archived-docs/test-recording/overview/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig1.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig10.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig11-lock.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig11-lock.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig11-unlock.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig11-unlock.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig12-refresh.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig12-refresh.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig2.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig3.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig4.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig5.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig6.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig7.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig8.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/recording-toolbar/fig9.png b/docs/img/archived-docs/test-recording/recording-toolbar/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/fig1.png b/docs/img/archived-docs/test-recording/step-suggestions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/fig2.png b/docs/img/archived-docs/test-recording/step-suggestions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/fig3.png b/docs/img/archived-docs/test-recording/step-suggestions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/fig4.png b/docs/img/archived-docs/test-recording/step-suggestions/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/fig5.png b/docs/img/archived-docs/test-recording/step-suggestions/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/archived-docs/test-recording/step-suggestions/step-builder-recorder.png b/docs/img/archived-docs/test-recording/step-suggestions/step-builder-recorder.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig1.png b/docs/img/automated-tests/customize-project/custom-layout/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig10.png b/docs/img/automated-tests/customize-project/custom-layout/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig11.png b/docs/img/automated-tests/customize-project/custom-layout/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig12.png b/docs/img/automated-tests/customize-project/custom-layout/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig13.png b/docs/img/automated-tests/customize-project/custom-layout/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig2.png b/docs/img/automated-tests/customize-project/custom-layout/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig2a.png b/docs/img/automated-tests/customize-project/custom-layout/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig2b.png b/docs/img/automated-tests/customize-project/custom-layout/fig2b.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig2c.png b/docs/img/automated-tests/customize-project/custom-layout/fig2c.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig3.png b/docs/img/automated-tests/customize-project/custom-layout/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig4.png b/docs/img/automated-tests/customize-project/custom-layout/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig4a.png b/docs/img/automated-tests/customize-project/custom-layout/fig4a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig5.png b/docs/img/automated-tests/customize-project/custom-layout/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig6.png b/docs/img/automated-tests/customize-project/custom-layout/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig7.png b/docs/img/automated-tests/customize-project/custom-layout/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig8.png b/docs/img/automated-tests/customize-project/custom-layout/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig8a.png b/docs/img/automated-tests/customize-project/custom-layout/fig8a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/fig9.png b/docs/img/automated-tests/customize-project/custom-layout/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/show-and-pin-pane.gif b/docs/img/automated-tests/customize-project/custom-layout/show-and-pin-pane.gif
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/custom-layout/unpin-pane.gif b/docs/img/automated-tests/customize-project/custom-layout/unpin-pane.gif
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/guided-tutorials/fig1.png b/docs/img/automated-tests/customize-project/guided-tutorials/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/guided-tutorials/fig2.png b/docs/img/automated-tests/customize-project/guided-tutorials/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/guided-tutorials/fig3.png b/docs/img/automated-tests/customize-project/guided-tutorials/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/guided-tutorials/fig4.png b/docs/img/automated-tests/customize-project/guided-tutorials/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig1.png b/docs/img/automated-tests/customize-project/in-product-guides/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig2.png b/docs/img/automated-tests/customize-project/in-product-guides/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig2a.png b/docs/img/automated-tests/customize-project/in-product-guides/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig2b.png b/docs/img/automated-tests/customize-project/in-product-guides/fig2b.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig3.png b/docs/img/automated-tests/customize-project/in-product-guides/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig4.png b/docs/img/automated-tests/customize-project/in-product-guides/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/fig5.png b/docs/img/automated-tests/customize-project/in-product-guides/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-guides/tinified.zip b/docs/img/automated-tests/customize-project/in-product-guides/tinified.zip
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-tips-tricks/fig1.png b/docs/img/automated-tests/customize-project/in-product-tips-tricks/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/in-product-tips-tricks/fig2.png b/docs/img/automated-tests/customize-project/in-product-tips-tricks/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig01.png b/docs/img/automated-tests/customize-project/welcome-screen/fig01.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig1.png b/docs/img/automated-tests/customize-project/welcome-screen/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig2.png b/docs/img/automated-tests/customize-project/welcome-screen/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig3.png b/docs/img/automated-tests/customize-project/welcome-screen/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig4.png b/docs/img/automated-tests/customize-project/welcome-screen/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig41.png b/docs/img/automated-tests/customize-project/welcome-screen/fig41.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig5.png b/docs/img/automated-tests/customize-project/welcome-screen/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig6.png b/docs/img/automated-tests/customize-project/welcome-screen/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/customize-project/welcome-screen/fig7.png b/docs/img/automated-tests/customize-project/welcome-screen/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/bind-test-data-source/add-data-source.png b/docs/img/automated-tests/data-drive-test/bind-test-data-source/add-data-source.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/bind-test-data-source/choose-test-to-bind.png b/docs/img/automated-tests/data-drive-test/bind-test-data-source/choose-test-to-bind.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/execution-log.png b/docs/img/automated-tests/data-drive-test/ddt-results/execution-log.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/failed-iteration-execution-log.png b/docs/img/automated-tests/data-drive-test/ddt-results/failed-iteration-execution-log.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/failed-iteration.png b/docs/img/automated-tests/data-drive-test/ddt-results/failed-iteration.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/failed-step-details.png b/docs/img/automated-tests/data-drive-test/ddt-results/failed-step-details.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/iterations-dropdown.png b/docs/img/automated-tests/data-drive-test/ddt-results/iterations-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/iterations-list-test-list.png b/docs/img/automated-tests/data-drive-test/ddt-results/iterations-list-test-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/kendo-product-iteration.png b/docs/img/automated-tests/data-drive-test/ddt-results/kendo-product-iteration.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/modified-data-table.png b/docs/img/automated-tests/data-drive-test/ddt-results/modified-data-table.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/overall-test-list-result.png b/docs/img/automated-tests/data-drive-test/ddt-results/overall-test-list-result.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/quick-run-log.png b/docs/img/automated-tests/data-drive-test/ddt-results/quick-run-log.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/quick-run-results.png b/docs/img/automated-tests/data-drive-test/ddt-results/quick-run-results.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png b/docs/img/automated-tests/data-drive-test/ddt-results/random-product-iteration.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/selected-test-exec-log.png b/docs/img/automated-tests/data-drive-test/ddt-results/selected-test-exec-log.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/test-list-result.png b/docs/img/automated-tests/data-drive-test/ddt-results/test-list-result.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/test-steps.png b/docs/img/automated-tests/data-drive-test/ddt-results/test-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/ddt-results/ts-product-iteration.png b/docs/img/automated-tests/data-drive-test/ddt-results/ts-product-iteration.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/external-data-driven-test/external-data.png b/docs/img/automated-tests/data-drive-test/external-data-driven-test/external-data.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/add-data.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/add-data.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/bound-step.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/bound-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/choose-binding-column.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/choose-binding-column.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/common-testing-approach.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/common-testing-approach.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/confirm-binding.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/confirm-binding.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/create-data-table.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/create-data-table.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/data-bind-dialog.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/data-bind-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/enter-text-properties.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/enter-text-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/execute-data-driven-test.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/execute-data-driven-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/expand-step.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/expand-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/iterations-dropdown.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/iterations-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/record-search-actions.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/record-search-actions.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/rename-column.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/rename-column.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/select-column.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/select-column.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/set-binding.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/set-binding.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/switch-to-local-data.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/switch-to-local-data.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/switch-to-test-steps.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/switch-to-test-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-binding.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-binding.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-bound.png b/docs/img/automated-tests/data-drive-test/local-data-driven-test/wait-step-bound.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/demo-desktop-test/1.png b/docs/img/automated-tests/desktop-testing/demo-desktop-test/1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/demo-desktop-test/2.png b/docs/img/automated-tests/desktop-testing/demo-desktop-test/2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig1.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig2.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig3.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig4.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig5.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig5a.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig6.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/desktop-test/fig7.png b/docs/img/automated-tests/desktop-testing/desktop-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig1.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig2.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig3.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig3a.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig4.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig40.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig40.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig5.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/fig6.png b/docs/img/automated-tests/desktop-testing/recording-specifics/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/recording-specifics/recorded-steps.png b/docs/img/automated-tests/desktop-testing/recording-specifics/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/user-model-id/fig1.png b/docs/img/automated-tests/desktop-testing/user-model-id/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/user-model-id/fig2.png b/docs/img/automated-tests/desktop-testing/user-model-id/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/user-model-id/fig3.png b/docs/img/automated-tests/desktop-testing/user-model-id/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/desktop-testing/user-model-id/fig4.png b/docs/img/automated-tests/desktop-testing/user-model-id/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/headless/fig1.png b/docs/img/automated-tests/headless/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/headless/fig2.png b/docs/img/automated-tests/headless/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/headless/fig3.png b/docs/img/automated-tests/headless/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/alert-dialog-step.png b/docs/img/automated-tests/recording/dialogs/alert-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/alert-dialog.png b/docs/img/automated-tests/recording/dialogs/alert-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/confirm-dialog-step.png b/docs/img/automated-tests/recording/dialogs/confirm-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/confirm-dialog.png b/docs/img/automated-tests/recording/dialogs/confirm-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/download-dialog-step.png b/docs/img/automated-tests/recording/dialogs/download-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/download-dialog.png b/docs/img/automated-tests/recording/dialogs/download-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/logon-dialog-step.png b/docs/img/automated-tests/recording/dialogs/logon-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/openFile-dialog-step.png b/docs/img/automated-tests/recording/dialogs/openFile-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/popup-steps.png b/docs/img/automated-tests/recording/dialogs/popup-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/prompt-dialog-step.png b/docs/img/automated-tests/recording/dialogs/prompt-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/prompt-dialog.png b/docs/img/automated-tests/recording/dialogs/prompt-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/saveFile-dialog-step.png b/docs/img/automated-tests/recording/dialogs/saveFile-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/upload-dialog-step.png b/docs/img/automated-tests/recording/dialogs/upload-dialog-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/dialogs/upload-dialog.png b/docs/img/automated-tests/recording/dialogs/upload-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/highlighting/fig1.png b/docs/img/automated-tests/recording/highlighting/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/highlighting/fig2.png b/docs/img/automated-tests/recording/highlighting/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/highlighting/fig4.png b/docs/img/automated-tests/recording/highlighting/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/highlighting/fig5.png b/docs/img/automated-tests/recording/highlighting/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/highlighting/fig6.png b/docs/img/automated-tests/recording/highlighting/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig1.png b/docs/img/automated-tests/recording/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig10.png b/docs/img/automated-tests/recording/overview/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig11.png b/docs/img/automated-tests/recording/overview/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig12.png b/docs/img/automated-tests/recording/overview/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig2.png b/docs/img/automated-tests/recording/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig3.png b/docs/img/automated-tests/recording/overview/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig4.png b/docs/img/automated-tests/recording/overview/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig5.png b/docs/img/automated-tests/recording/overview/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig5a.png b/docs/img/automated-tests/recording/overview/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/overview/fig6.png b/docs/img/automated-tests/recording/overview/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-frames/fig0.png b/docs/img/automated-tests/recording/recording-frames/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-frames/fig1.png b/docs/img/automated-tests/recording/recording-frames/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-frames/fig2.png b/docs/img/automated-tests/recording/recording-frames/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-frames/fig3.png b/docs/img/automated-tests/recording/recording-frames/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-frames/fig4.png b/docs/img/automated-tests/recording/recording-frames/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-translators/fig1.png b/docs/img/automated-tests/recording/recording-translators/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-translators/fig2.png b/docs/img/automated-tests/recording/recording-translators/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-translators/fig3.png b/docs/img/automated-tests/recording/recording-translators/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/recording-translators/highlight-components.gif b/docs/img/automated-tests/recording/recording-translators/highlight-components.gif
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig1.png b/docs/img/automated-tests/recording/validate-pdf/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig2.png b/docs/img/automated-tests/recording/validate-pdf/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig2a.png b/docs/img/automated-tests/recording/validate-pdf/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig2b.png b/docs/img/automated-tests/recording/validate-pdf/fig2b.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig3.png b/docs/img/automated-tests/recording/validate-pdf/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/fig4.png b/docs/img/automated-tests/recording/validate-pdf/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/recording/validate-pdf/set-default-pdf-viewer.png b/docs/img/automated-tests/recording/validate-pdf/set-default-pdf-viewer.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling-results/scheduling-results/fig1.png b/docs/img/automated-tests/scheduling-results/scheduling-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling-results/scheduling-results/fig2.png b/docs/img/automated-tests/scheduling-results/scheduling-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling-results/scheduling-results/fig3.png b/docs/img/automated-tests/scheduling-results/scheduling-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling-results/scheduling-results/fig4.png b/docs/img/automated-tests/scheduling-results/scheduling-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/overview/fig1.png b/docs/img/automated-tests/scheduling/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/overview/fig1png.png b/docs/img/automated-tests/scheduling/overview/fig1png.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/overview/scheduling-iconography-bright.png b/docs/img/automated-tests/scheduling/overview/scheduling-iconography-bright.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/overview/scheduling-setup-revamp.png b/docs/img/automated-tests/scheduling/overview/scheduling-setup-revamp.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/upload/fig0.png b/docs/img/automated-tests/scheduling/upload/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/upload/fig1.png b/docs/img/automated-tests/scheduling/upload/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/upload/fig2.png b/docs/img/automated-tests/scheduling/upload/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/scheduling/upload/fig3.png b/docs/img/automated-tests/scheduling/upload/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig1.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig2.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig3.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig4.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig5.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/partial-test-execution/fig6.png b/docs/img/automated-tests/test-execution/partial-test-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-execution/execute-test.gif b/docs/img/automated-tests/test-execution/quick-execution/execute-test.gif
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-execution/fig1.png b/docs/img/automated-tests/test-execution/quick-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-execution/fig2.png b/docs/img/automated-tests/test-execution/quick-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-execution/fig3.png b/docs/img/automated-tests/test-execution/quick-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-annotations/fig7.png b/docs/img/automated-tests/test-execution/quick-run-annotations/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-annotations/fig7a.png b/docs/img/automated-tests/test-execution/quick-run-annotations/fig7a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-baseurl/fig12.png b/docs/img/automated-tests/test-execution/quick-run-baseurl/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-baseurl/fig13.png b/docs/img/automated-tests/test-execution/quick-run-baseurl/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-browsers/fig1.png b/docs/img/automated-tests/test-execution/quick-run-browsers/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-browsers/fig2.png b/docs/img/automated-tests/test-execution/quick-run-browsers/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-timeouts/fig10.png b/docs/img/automated-tests/test-execution/quick-run-timeouts/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-visual-debugger/fig1.png b/docs/img/automated-tests/test-execution/quick-run-visual-debugger/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-execution/quick-run-visual-debugger/fig2.png b/docs/img/automated-tests/test-execution/quick-run-visual-debugger/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig1.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig10.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig11.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig12.gif b/docs/img/automated-tests/test-list-results/analyze-test-results/fig12.gif
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig12.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig13.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig1a.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig2.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig2a.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig3.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig31.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig31.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig4.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig5.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig6.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig7.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/analyze-test-results/fig8.png b/docs/img/automated-tests/test-list-results/analyze-test-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig1.png b/docs/img/automated-tests/test-list-results/calendar/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig2.png b/docs/img/automated-tests/test-list-results/calendar/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig3.png b/docs/img/automated-tests/test-list-results/calendar/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig4.png b/docs/img/automated-tests/test-list-results/calendar/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig5.png b/docs/img/automated-tests/test-list-results/calendar/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/calendar/fig6.png b/docs/img/automated-tests/test-list-results/calendar/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig1.png b/docs/img/automated-tests/test-list-results/export-test-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig10.png b/docs/img/automated-tests/test-list-results/export-test-results/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig11.png b/docs/img/automated-tests/test-list-results/export-test-results/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig12.png b/docs/img/automated-tests/test-list-results/export-test-results/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig13.png b/docs/img/automated-tests/test-list-results/export-test-results/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig2.png b/docs/img/automated-tests/test-list-results/export-test-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig3.png b/docs/img/automated-tests/test-list-results/export-test-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig4.png b/docs/img/automated-tests/test-list-results/export-test-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig5.png b/docs/img/automated-tests/test-list-results/export-test-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig6.png b/docs/img/automated-tests/test-list-results/export-test-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig7.png b/docs/img/automated-tests/test-list-results/export-test-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig8.png b/docs/img/automated-tests/test-list-results/export-test-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-list-results/export-test-results/fig9.png b/docs/img/automated-tests/test-list-results/export-test-results/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-execution/fig3.png b/docs/img/automated-tests/test-lists/test-list-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-execution/fig4.png b/docs/img/automated-tests/test-lists/test-list-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-execution/fig5.png b/docs/img/automated-tests/test-lists/test-list-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig1.png b/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig2.png b/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig3.png b/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig4.png b/docs/img/automated-tests/test-lists/test-list-runs-specifics/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig1.png b/docs/img/automated-tests/test-lists/test-lists-types/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig2.png b/docs/img/automated-tests/test-lists/test-lists-types/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig2_FilterTestsByType.png b/docs/img/automated-tests/test-lists/test-lists-types/fig2_FilterTestsByType.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig2_collapse.png b/docs/img/automated-tests/test-lists/test-lists-types/fig2_collapse.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig2_searchField.png b/docs/img/automated-tests/test-lists/test-lists-types/fig2_searchField.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig3.png b/docs/img/automated-tests/test-lists/test-lists-types/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig4.png b/docs/img/automated-tests/test-lists/test-lists-types/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig5.png b/docs/img/automated-tests/test-lists/test-lists-types/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig6.png b/docs/img/automated-tests/test-lists/test-lists-types/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig7.png b/docs/img/automated-tests/test-lists/test-lists-types/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-lists/test-lists-types/fig8.png b/docs/img/automated-tests/test-lists/test-lists-types/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/analyze-quick-run-results/fig1.png b/docs/img/automated-tests/test-results/analyze-quick-run-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/analyze-quick-run-results/fig2.png b/docs/img/automated-tests/test-results/analyze-quick-run-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/analyze-quick-run-results/fig3.png b/docs/img/automated-tests/test-results/analyze-quick-run-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/analyze-quick-run-results/fig4.png b/docs/img/automated-tests/test-results/analyze-quick-run-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/analyze-quick-run-results/fig5.png b/docs/img/automated-tests/test-results/analyze-quick-run-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig1.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig1a.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig2.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig3.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig3a.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig4.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig4a.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig4a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig5.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-quick-run-results/fig5a.png b/docs/img/automated-tests/test-results/new-quick-run-results/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/failure-section-export-button.png b/docs/img/automated-tests/test-results/new-step-failure-details/failure-section-export-button.png
new file mode 100644
index 00000000..c3b128e8
Binary files /dev/null and b/docs/img/automated-tests/test-results/new-step-failure-details/failure-section-export-button.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/fig2.png b/docs/img/automated-tests/test-results/new-step-failure-details/fig2.png
old mode 100644
new mode 100755
index 2b7ce138..b28cf766
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/fig2.png and b/docs/img/automated-tests/test-results/new-step-failure-details/fig2.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/fig2a.png b/docs/img/automated-tests/test-results/new-step-failure-details/fig2a.png
old mode 100644
new mode 100755
index 9a483cad..caeeab80
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/fig2a.png and b/docs/img/automated-tests/test-results/new-step-failure-details/fig2a.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/new1.png b/docs/img/automated-tests/test-results/new-step-failure-details/new1.png
old mode 100644
new mode 100755
index 5764b5a1..ec863297
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/new1.png and b/docs/img/automated-tests/test-results/new-step-failure-details/new1.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/new2.png b/docs/img/automated-tests/test-results/new-step-failure-details/new2.png
old mode 100644
new mode 100755
index 3dff240c..3e522907
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/new2.png and b/docs/img/automated-tests/test-results/new-step-failure-details/new2.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/new3.png b/docs/img/automated-tests/test-results/new-step-failure-details/new3.png
old mode 100644
new mode 100755
index cc0e092c..dd9c8a55
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/new3.png and b/docs/img/automated-tests/test-results/new-step-failure-details/new3.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/new4.png b/docs/img/automated-tests/test-results/new-step-failure-details/new4.png
old mode 100644
new mode 100755
index b4eefbfb..b8ddf052
Binary files a/docs/img/automated-tests/test-results/new-step-failure-details/new4.png and b/docs/img/automated-tests/test-results/new-step-failure-details/new4.png differ
diff --git a/docs/img/automated-tests/test-results/new-step-failure-details/new5.png b/docs/img/automated-tests/test-results/new-step-failure-details/new5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig2.png b/docs/img/automated-tests/test-results/step-failure-details/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig2a.png b/docs/img/automated-tests/test-results/step-failure-details/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig3.png b/docs/img/automated-tests/test-results/step-failure-details/fig3.png
old mode 100644
new mode 100755
index 6104b933..944b9550
Binary files a/docs/img/automated-tests/test-results/step-failure-details/fig3.png and b/docs/img/automated-tests/test-results/step-failure-details/fig3.png differ
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig4.png b/docs/img/automated-tests/test-results/step-failure-details/fig4.png
old mode 100644
new mode 100755
index 9c7f9022..46307ebc
Binary files a/docs/img/automated-tests/test-results/step-failure-details/fig4.png and b/docs/img/automated-tests/test-results/step-failure-details/fig4.png differ
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig5.png b/docs/img/automated-tests/test-results/step-failure-details/fig5.png
old mode 100644
new mode 100755
index 89f17ce5..8229b134
Binary files a/docs/img/automated-tests/test-results/step-failure-details/fig5.png and b/docs/img/automated-tests/test-results/step-failure-details/fig5.png differ
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig6.png b/docs/img/automated-tests/test-results/step-failure-details/fig6.png
old mode 100644
new mode 100755
index e10b2370..90c3f4a6
Binary files a/docs/img/automated-tests/test-results/step-failure-details/fig6.png and b/docs/img/automated-tests/test-results/step-failure-details/fig6.png differ
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig7.png b/docs/img/automated-tests/test-results/step-failure-details/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig8.png b/docs/img/automated-tests/test-results/step-failure-details/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/step-failure-details/fig9.png b/docs/img/automated-tests/test-results/step-failure-details/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/test-as-step-results/fig1.png b/docs/img/automated-tests/test-results/test-as-step-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/test-as-step-results/fig2.png b/docs/img/automated-tests/test-results/test-as-step-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/test-as-step-results/fig3.png b/docs/img/automated-tests/test-results/test-as-step-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/test-results/test-as-step-results/fig4.png b/docs/img/automated-tests/test-results/test-as-step-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/1SampleApp.png b/docs/img/automated-tests/troubleshooting/element-not-found/1SampleApp.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/2RecordedTest.png b/docs/img/automated-tests/troubleshooting/element-not-found/2RecordedTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/3FailingTest.png b/docs/img/automated-tests/troubleshooting/element-not-found/3FailingTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/4EditElement.png b/docs/img/automated-tests/troubleshooting/element-not-found/4EditElement.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/5EditinLive.png b/docs/img/automated-tests/troubleshooting/element-not-found/5EditinLive.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/6DynamicId.png b/docs/img/automated-tests/troubleshooting/element-not-found/6DynamicId.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/7ValidateExpression.png b/docs/img/automated-tests/troubleshooting/element-not-found/7ValidateExpression.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/element-not-found/8TestPasses.png b/docs/img/automated-tests/troubleshooting/element-not-found/8TestPasses.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig1.png b/docs/img/automated-tests/troubleshooting/failing-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig2.png b/docs/img/automated-tests/troubleshooting/failing-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig3.png b/docs/img/automated-tests/troubleshooting/failing-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig4.png b/docs/img/automated-tests/troubleshooting/failing-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig5.png b/docs/img/automated-tests/troubleshooting/failing-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig6.png b/docs/img/automated-tests/troubleshooting/failing-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig7.png b/docs/img/automated-tests/troubleshooting/failing-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig8.png b/docs/img/automated-tests/troubleshooting/failing-test/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/failing-test/fig9.png b/docs/img/automated-tests/troubleshooting/failing-test/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/1Showcase.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/1Showcase.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/2RecordedTest.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/2RecordedTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/3EditElement.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/3EditElement.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/4NewFindExpression.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/4NewFindExpression.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/5ImageSearch.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/5ImageSearch.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/6ParentElement.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/6ParentElement.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/7ChainedFindExpression.png b/docs/img/automated-tests/troubleshooting/handle-dynamic-attributes/7ChainedFindExpression.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/update-verification/1Buttons.png b/docs/img/automated-tests/troubleshooting/update-verification/1Buttons.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/update-verification/2EditValue.png b/docs/img/automated-tests/troubleshooting/update-verification/2EditValue.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/1WebApp.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/1WebApp.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/2RecordedTest.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/2RecordedTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/3StepFails.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/3StepFails.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/4StepFailureDetails.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/4StepFailureDetails.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/5EnableAnnotations.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/5EnableAnnotations.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/6ExecuteButton.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/6ExecuteButton.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/7AnnotatedClick.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/7AnnotatedClick.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-annotated-run/8TestPasses.png b/docs/img/automated-tests/troubleshooting/use-annotated-run/8TestPasses.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/1Scenario.png b/docs/img/automated-tests/troubleshooting/use-partial-run/1Scenario.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/2Recordedtest.png b/docs/img/automated-tests/troubleshooting/use-partial-run/2Recordedtest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/3Failingtest.png b/docs/img/automated-tests/troubleshooting/use-partial-run/3Failingtest.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/4RuntoHere.png b/docs/img/automated-tests/troubleshooting/use-partial-run/4RuntoHere.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/5RunSelected.png b/docs/img/automated-tests/troubleshooting/use-partial-run/5RunSelected.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/6Step2passing.png b/docs/img/automated-tests/troubleshooting/use-partial-run/6Step2passing.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/use-partial-run/7TestPassing.png b/docs/img/automated-tests/troubleshooting/use-partial-run/7TestPassing.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig1.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig10.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig11.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig12.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig2.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig3.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig4.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig5.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig6.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig7.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig8.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/troubleshooting/visual-debugger/fig9.png b/docs/img/automated-tests/troubleshooting/visual-debugger/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/code-options-in-vs/generate-unit-test.png b/docs/img/automated-tests/vs-plugin/code-options-in-vs/generate-unit-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/code-options-in-vs/preview-code.png b/docs/img/automated-tests/vs-plugin/code-options-in-vs/preview-code.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/code-options-in-vs/unit-test-generated.png b/docs/img/automated-tests/vs-plugin/code-options-in-vs/unit-test-generated.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/filter-project-types.png b/docs/img/automated-tests/vs-plugin/create-project/filter-project-types.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/new-project-created.png b/docs/img/automated-tests/vs-plugin/create-project/new-project-created.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/project-config.png b/docs/img/automated-tests/vs-plugin/create-project/project-config.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/test-studio-specific-panes.png b/docs/img/automated-tests/vs-plugin/create-project/test-studio-specific-panes.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/test-studio-test-specific-options.png b/docs/img/automated-tests/vs-plugin/create-project/test-studio-test-specific-options.png
old mode 100644
new mode 100755
diff --git a/docs/img/automated-tests/vs-plugin/create-project/vs-start-screen.png b/docs/img/automated-tests/vs-plugin/create-project/vs-start-screen.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig1.png b/docs/img/features/azure-dev-ops-mapper/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig2.png b/docs/img/features/azure-dev-ops-mapper/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig3.png b/docs/img/features/azure-dev-ops-mapper/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig4.png b/docs/img/features/azure-dev-ops-mapper/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig5.png b/docs/img/features/azure-dev-ops-mapper/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig6.png b/docs/img/features/azure-dev-ops-mapper/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig7.png b/docs/img/features/azure-dev-ops-mapper/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/azure-dev-ops-mapper/fig8.png b/docs/img/features/azure-dev-ops-mapper/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/code-behind-file/fig1.png b/docs/img/features/coded-steps/code-behind-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/code-behind-file/fig4.png b/docs/img/features/coded-steps/code-behind-file/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/code-behind-file/fig5.png b/docs/img/features/coded-steps/code-behind-file/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/code-behind-file/fig6.png b/docs/img/features/coded-steps/code-behind-file/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/add-coded-step.gif b/docs/img/features/coded-steps/coded-steps/add-coded-step.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/add-second-coded-step.gif b/docs/img/features/coded-steps/coded-steps/add-second-coded-step.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig1.png b/docs/img/features/coded-steps/coded-steps/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig10.png b/docs/img/features/coded-steps/coded-steps/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig11.png b/docs/img/features/coded-steps/coded-steps/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig12.png b/docs/img/features/coded-steps/coded-steps/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig2.png b/docs/img/features/coded-steps/coded-steps/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig3.png b/docs/img/features/coded-steps/coded-steps/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig4.png b/docs/img/features/coded-steps/coded-steps/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/coded-steps/fig5.png b/docs/img/features/coded-steps/coded-steps/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/compile-project/fig1.png b/docs/img/features/coded-steps/compile-project/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/compile-project/fig2.png b/docs/img/features/coded-steps/compile-project/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/compile-project/fig3.png b/docs/img/features/coded-steps/compile-project/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/output-panel/fig1.png b/docs/img/features/coded-steps/output-panel/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/output-panel/fig2.png b/docs/img/features/coded-steps/output-panel/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/output-panel/fig3.png b/docs/img/features/coded-steps/output-panel/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/output-panel/fig4.png b/docs/img/features/coded-steps/output-panel/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/standalone-code-file/fig1.png b/docs/img/features/coded-steps/standalone-code-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/standalone-code-file/fig2.png b/docs/img/features/coded-steps/standalone-code-file/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/standalone-code-file/fig3.png b/docs/img/features/coded-steps/standalone-code-file/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/coded-steps/standalone-code-file/fig4.png b/docs/img/features/coded-steps/standalone-code-file/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/api-test-as-step/api-test.png b/docs/img/features/custom-steps/api-test-as-step/api-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture-window/extended-menu-capture-window.png b/docs/img/features/custom-steps/capture-window/extended-menu-capture-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture-window/fig3.png b/docs/img/features/custom-steps/capture-window/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture-window/step-builder-capture-window.png b/docs/img/features/custom-steps/capture-window/step-builder-capture-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture/extended-menu-browser-capture.png b/docs/img/features/custom-steps/capture/extended-menu-browser-capture.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture/fig3.png b/docs/img/features/custom-steps/capture/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture/step-builder-browser-capture.png b/docs/img/features/custom-steps/capture/step-builder-browser-capture.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/capture/step-properties.png b/docs/img/features/custom-steps/capture/step-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/change-window-state/extended-menu-change-window.png b/docs/img/features/custom-steps/change-window-state/extended-menu-change-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/change-window-state/step-builder-change-window.png b/docs/img/features/custom-steps/change-window-state/step-builder-change-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros-2.png b/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros-2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros-3.png b/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros-3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros.png b/docs/img/features/custom-steps/check-js-errors/extended-menu-js-errros.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/fig2.png b/docs/img/features/custom-steps/check-js-errors/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/fig3.png b/docs/img/features/custom-steps/check-js-errors/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/fig5.png b/docs/img/features/custom-steps/check-js-errors/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/fig7.png b/docs/img/features/custom-steps/check-js-errors/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/fig9.png b/docs/img/features/custom-steps/check-js-errors/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/check-js-errors/step-builder-js-errors.png b/docs/img/features/custom-steps/check-js-errors/step-builder-js-errors.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/clear-browser-cache/extended-menu-clear-cache.png b/docs/img/features/custom-steps/clear-browser-cache/extended-menu-clear-cache.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/clear-browser-cache/step-builder-clear-cache.png b/docs/img/features/custom-steps/clear-browser-cache/step-builder-clear-cache.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/comment/comment-log.png b/docs/img/features/custom-steps/comment/comment-log.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/comment/step-builder-comment.png b/docs/img/features/custom-steps/comment/step-builder-comment.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/connect-to-app/extended-menu-connect-app.png b/docs/img/features/custom-steps/connect-to-app/extended-menu-connect-app.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/connect-to-app/step-builder-connec-app.png b/docs/img/features/custom-steps/connect-to-app/step-builder-connec-app.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/connect-to-app/step-builder-connect-app-wpf.png b/docs/img/features/custom-steps/connect-to-app/step-builder-connect-app-wpf.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/custom-annotation/props-custom-anotations.png b/docs/img/features/custom-steps/custom-annotation/props-custom-anotations.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/custom-annotation/step-builder-custom-anotation.png b/docs/img/features/custom-steps/custom-annotation/step-builder-custom-anotation.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/execution-delay/change-time-box.png b/docs/img/features/custom-steps/execution-delay/change-time-box.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/execution-delay/step-builder-execution-delay.png b/docs/img/features/custom-steps/execution-delay/step-builder-execution-delay.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/inspection-point/inspect-dom.png b/docs/img/features/custom-steps/inspection-point/inspect-dom.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/inspection-point/step-builder-inspc-point.png b/docs/img/features/custom-steps/inspection-point/step-builder-inspc-point.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/launch-app/launch-app-step.png b/docs/img/features/custom-steps/launch-app/launch-app-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/launch-app/launch-wpf-app-step.png b/docs/img/features/custom-steps/launch-app/launch-wpf-app-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/launch-app/step-launch-app-properties.png b/docs/img/features/custom-steps/launch-app/step-launch-app-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/launch-app/step-launch-wpf-app-properties.png b/docs/img/features/custom-steps/launch-app/step-launch-wpf-app-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/manual-step/fig2.png b/docs/img/features/custom-steps/manual-step/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/manual-step/manual-step-props.png b/docs/img/features/custom-steps/manual-step/manual-step-props.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/manual-step/step-builder-manual-steps.png b/docs/img/features/custom-steps/manual-step/step-builder-manual-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/maximize-browser/step-builder-max-browser.png b/docs/img/features/custom-steps/maximize-browser/step-builder-max-browser.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/navigate-to/fig2.png b/docs/img/features/custom-steps/navigate-to/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/navigate-to/step-builder-navigate-to.png b/docs/img/features/custom-steps/navigate-to/step-builder-navigate-to.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/open-pdf/pdf-dropdown.png b/docs/img/features/custom-steps/open-pdf/pdf-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/open-pdf/step-builder-open-pdf.png b/docs/img/features/custom-steps/open-pdf/step-builder-open-pdf.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/add-step.png b/docs/img/features/custom-steps/overview/add-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/fig4.png b/docs/img/features/custom-steps/overview/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/fig6.png b/docs/img/features/custom-steps/overview/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/use-the-step-builder-panel.png b/docs/img/features/custom-steps/overview/use-the-step-builder-panel.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/web-gen-step.png b/docs/img/features/custom-steps/overview/web-gen-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/overview/wpf-gen-step.png b/docs/img/features/custom-steps/overview/wpf-gen-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/press-key/extended-menu-press-key.png b/docs/img/features/custom-steps/press-key/extended-menu-press-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/press-key/step-builder-press-key.png b/docs/img/features/custom-steps/press-key/step-builder-press-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/refresh-browser/step-builder-refresh-browser.png b/docs/img/features/custom-steps/refresh-browser/step-builder-refresh-browser.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/script-step/fig1.png b/docs/img/features/custom-steps/script-step/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/script-step/fig2.png b/docs/img/features/custom-steps/script-step/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/script-step/fig3.png b/docs/img/features/custom-steps/script-step/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/script-step/fig4.png b/docs/img/features/custom-steps/script-step/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/add-test-step.png b/docs/img/features/custom-steps/test-as-step/add-test-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/example-test-as-step.png b/docs/img/features/custom-steps/test-as-step/example-test-as-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/fig10.png b/docs/img/features/custom-steps/test-as-step/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/fig8.png b/docs/img/features/custom-steps/test-as-step/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/gr-recorded-steps-as-test-direct-insert.png b/docs/img/features/custom-steps/test-as-step/gr-recorded-steps-as-test-direct-insert.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/gr-recorded-steps-as-test.png b/docs/img/features/custom-steps/test-as-step/gr-recorded-steps-as-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/login-test-sample-2.png b/docs/img/features/custom-steps/test-as-step/login-test-sample-2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/test-as-step/login-test-sample.png b/docs/img/features/custom-steps/test-as-step/login-test-sample.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/type-text/properties-type-text-step.png b/docs/img/features/custom-steps/type-text/properties-type-text-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/type-text/type-text-step.png b/docs/img/features/custom-steps/type-text/type-text-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/custom-steps/wait-for-url/step-builder-wait-url.png b/docs/img/features/custom-steps/wait-for-url/step-builder-wait-url.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig1.png b/docs/img/features/data-driven-testing/add-data-source/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig10.png b/docs/img/features/data-driven-testing/add-data-source/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig2.png b/docs/img/features/data-driven-testing/add-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig3.png b/docs/img/features/data-driven-testing/add-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig4.png b/docs/img/features/data-driven-testing/add-data-source/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig5.png b/docs/img/features/data-driven-testing/add-data-source/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig6.png b/docs/img/features/data-driven-testing/add-data-source/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig7.png b/docs/img/features/data-driven-testing/add-data-source/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig8.png b/docs/img/features/data-driven-testing/add-data-source/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig9.png b/docs/img/features/data-driven-testing/add-data-source/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/add-data-source/fig9a.png b/docs/img/features/data-driven-testing/add-data-source/fig9a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/bind-extracted-variable.png b/docs/img/features/data-driven-testing/attach-columns-input-values/bind-extracted-variable.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/bindings-dropdown.png b/docs/img/features/data-driven-testing/attach-columns-input-values/bindings-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/data-columns-dropdown.png b/docs/img/features/data-driven-testing/attach-columns-input-values/data-columns-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/external-variable-set-button.png b/docs/img/features/data-driven-testing/attach-columns-input-values/external-variable-set-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/external-variable.png b/docs/img/features/data-driven-testing/attach-columns-input-values/external-variable.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/fig1.png b/docs/img/features/data-driven-testing/attach-columns-input-values/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/fig2.png b/docs/img/features/data-driven-testing/attach-columns-input-values/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/fig3.png b/docs/img/features/data-driven-testing/attach-columns-input-values/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/fig4.png b/docs/img/features/data-driven-testing/attach-columns-input-values/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/open-step-properties.png b/docs/img/features/data-driven-testing/attach-columns-input-values/open-step-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-input-values/set-button.png b/docs/img/features/data-driven-testing/attach-columns-input-values/set-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-verifications/fig1.png b/docs/img/features/data-driven-testing/attach-columns-verifications/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-verifications/fig2.png b/docs/img/features/data-driven-testing/attach-columns-verifications/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-verifications/fig3.png b/docs/img/features/data-driven-testing/attach-columns-verifications/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/attach-columns-verifications/fig4.png b/docs/img/features/data-driven-testing/attach-columns-verifications/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig1.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig2.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig3.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig4.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig5.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig6.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig7.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/bind-test-data-source/fig8.png b/docs/img/features/data-driven-testing/bind-test-data-source/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig2.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig20.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig21.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig21.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig22.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig22.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig23.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig23.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/local-data-driven-test/fig4.png b/docs/img/features/data-driven-testing/local-data-driven-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/manage-external-data-source/fig1.png b/docs/img/features/data-driven-testing/manage-external-data-source/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/manage-external-data-source/fig2.png b/docs/img/features/data-driven-testing/manage-external-data-source/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/manage-external-data-source/fig3.png b/docs/img/features/data-driven-testing/manage-external-data-source/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/manage-external-data-source/fig4.png b/docs/img/features/data-driven-testing/manage-external-data-source/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/oracle-db-example/fig1.png b/docs/img/features/data-driven-testing/oracle-db-example/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/oracle-db-example/fig2.png b/docs/img/features/data-driven-testing/oracle-db-example/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/oracle-db-example/fig3.png b/docs/img/features/data-driven-testing/oracle-db-example/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/oracle-db-example/fig4.png b/docs/img/features/data-driven-testing/oracle-db-example/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/sql-database-example/fig1.png b/docs/img/features/data-driven-testing/sql-database-example/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/data-driven-testing/sql-database-example/fig2.png b/docs/img/features/data-driven-testing/sql-database-example/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig1.png b/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig1.png
old mode 100644
new mode 100755
index e69772e3..662b2936
Binary files a/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig1.png and b/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig1.png differ
diff --git a/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig2.png b/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig2.png
old mode 100644
new mode 100755
index 709eff06..794e4fcb
Binary files a/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig2.png and b/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig2.png differ
diff --git a/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig3.png b/docs/img/features/dialogs-and-popups/dialog-handler-updater/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/button-warning.png b/docs/img/features/dialogs-and-popups/dialogs/button-warning.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/dialog-step-builder.png b/docs/img/features/dialogs-and-popups/dialogs/dialog-step-builder.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/download-path.png b/docs/img/features/dialogs-and-popups/dialogs/download-path.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/file-upload-extended-menu.png b/docs/img/features/dialogs-and-popups/dialogs/file-upload-extended-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/filepath-in-savefile-dialog.png b/docs/img/features/dialogs-and-popups/dialogs/filepath-in-savefile-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/handle-button.png b/docs/img/features/dialogs-and-popups/dialogs/handle-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/open-file-dialog-multiple-file.png b/docs/img/features/dialogs-and-popups/dialogs/open-file-dialog-multiple-file.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/dialogs/timeouts-extended-menu.png b/docs/img/features/dialogs-and-popups/dialogs/timeouts-extended-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/Timeouts.png b/docs/img/features/dialogs-and-popups/html-popups/Timeouts.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/add-connect-close-step-builder.png b/docs/img/features/dialogs-and-popups/html-popups/add-connect-close-step-builder.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/fig1.png b/docs/img/features/dialogs-and-popups/html-popups/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/modal-popup.png b/docs/img/features/dialogs-and-popups/html-popups/modal-popup.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/popup-dynamic-url.png b/docs/img/features/dialogs-and-popups/html-popups/popup-dynamic-url.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/dialogs-and-popups/html-popups/popup-url.png b/docs/img/features/dialogs-and-popups/html-popups/popup-url.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-find-expression/fig1.png b/docs/img/features/elements-explorer/element-find-expression/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-find-expression/fig2.png b/docs/img/features/elements-explorer/element-find-expression/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-find-expression/fig3.png b/docs/img/features/elements-explorer/element-find-expression/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig1.png b/docs/img/features/elements-explorer/element-mapping/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig10.png b/docs/img/features/elements-explorer/element-mapping/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig11.png b/docs/img/features/elements-explorer/element-mapping/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig12.png b/docs/img/features/elements-explorer/element-mapping/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig13.png b/docs/img/features/elements-explorer/element-mapping/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig14.png b/docs/img/features/elements-explorer/element-mapping/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig15.png b/docs/img/features/elements-explorer/element-mapping/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig16.png b/docs/img/features/elements-explorer/element-mapping/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig17.png b/docs/img/features/elements-explorer/element-mapping/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig18.png b/docs/img/features/elements-explorer/element-mapping/fig18.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig19.png b/docs/img/features/elements-explorer/element-mapping/fig19.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig2.png b/docs/img/features/elements-explorer/element-mapping/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig20.png b/docs/img/features/elements-explorer/element-mapping/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig3.png b/docs/img/features/elements-explorer/element-mapping/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig4.png b/docs/img/features/elements-explorer/element-mapping/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig5.png b/docs/img/features/elements-explorer/element-mapping/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig6.png b/docs/img/features/elements-explorer/element-mapping/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig7.png b/docs/img/features/elements-explorer/element-mapping/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig8.png b/docs/img/features/elements-explorer/element-mapping/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/element-mapping/fig9.png b/docs/img/features/elements-explorer/element-mapping/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig0.png b/docs/img/features/elements-explorer/find-element-by-image/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig0a.png b/docs/img/features/elements-explorer/find-element-by-image/fig0a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig1.png b/docs/img/features/elements-explorer/find-element-by-image/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig10.png b/docs/img/features/elements-explorer/find-element-by-image/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig11.png b/docs/img/features/elements-explorer/find-element-by-image/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig12.png b/docs/img/features/elements-explorer/find-element-by-image/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig13.png b/docs/img/features/elements-explorer/find-element-by-image/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig14.gif b/docs/img/features/elements-explorer/find-element-by-image/fig14.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig15.gif b/docs/img/features/elements-explorer/find-element-by-image/fig15.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig16.png b/docs/img/features/elements-explorer/find-element-by-image/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig17.png b/docs/img/features/elements-explorer/find-element-by-image/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig17a.gif b/docs/img/features/elements-explorer/find-element-by-image/fig17a.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig18.png b/docs/img/features/elements-explorer/find-element-by-image/fig18.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig2.png b/docs/img/features/elements-explorer/find-element-by-image/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig3.png b/docs/img/features/elements-explorer/find-element-by-image/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig3a.png b/docs/img/features/elements-explorer/find-element-by-image/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig4.png b/docs/img/features/elements-explorer/find-element-by-image/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig5.png b/docs/img/features/elements-explorer/find-element-by-image/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig6.png b/docs/img/features/elements-explorer/find-element-by-image/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig7.png b/docs/img/features/elements-explorer/find-element-by-image/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig8.png b/docs/img/features/elements-explorer/find-element-by-image/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element-by-image/fig9.png b/docs/img/features/elements-explorer/find-element-by-image/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig1.png b/docs/img/features/elements-explorer/find-element/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig10.png b/docs/img/features/elements-explorer/find-element/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig101.png b/docs/img/features/elements-explorer/find-element/fig101.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig102.png b/docs/img/features/elements-explorer/find-element/fig102.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig103.png b/docs/img/features/elements-explorer/find-element/fig103.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig105.png b/docs/img/features/elements-explorer/find-element/fig105.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig106.png b/docs/img/features/elements-explorer/find-element/fig106.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig107.png b/docs/img/features/elements-explorer/find-element/fig107.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig108.png b/docs/img/features/elements-explorer/find-element/fig108.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig109.png b/docs/img/features/elements-explorer/find-element/fig109.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig11.png b/docs/img/features/elements-explorer/find-element/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig110.png b/docs/img/features/elements-explorer/find-element/fig110.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig111.png b/docs/img/features/elements-explorer/find-element/fig111.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig112.png b/docs/img/features/elements-explorer/find-element/fig112.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig113.png b/docs/img/features/elements-explorer/find-element/fig113.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig114.png b/docs/img/features/elements-explorer/find-element/fig114.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig115.png b/docs/img/features/elements-explorer/find-element/fig115.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig116.png b/docs/img/features/elements-explorer/find-element/fig116.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig117.png b/docs/img/features/elements-explorer/find-element/fig117.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig118.png b/docs/img/features/elements-explorer/find-element/fig118.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig119.png b/docs/img/features/elements-explorer/find-element/fig119.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig12.png b/docs/img/features/elements-explorer/find-element/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig120.png b/docs/img/features/elements-explorer/find-element/fig120.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig13.png b/docs/img/features/elements-explorer/find-element/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig130.png b/docs/img/features/elements-explorer/find-element/fig130.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig14.png b/docs/img/features/elements-explorer/find-element/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig15.png b/docs/img/features/elements-explorer/find-element/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig16.png b/docs/img/features/elements-explorer/find-element/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig17.png b/docs/img/features/elements-explorer/find-element/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig18.png b/docs/img/features/elements-explorer/find-element/fig18.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig19.png b/docs/img/features/elements-explorer/find-element/fig19.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig2.png b/docs/img/features/elements-explorer/find-element/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig20.png b/docs/img/features/elements-explorer/find-element/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig21.png b/docs/img/features/elements-explorer/find-element/fig21.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig3.png b/docs/img/features/elements-explorer/find-element/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig4.png b/docs/img/features/elements-explorer/find-element/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig5.png b/docs/img/features/elements-explorer/find-element/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig6.png b/docs/img/features/elements-explorer/find-element/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig7.png b/docs/img/features/elements-explorer/find-element/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig8.png b/docs/img/features/elements-explorer/find-element/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/find-element/fig9.png b/docs/img/features/elements-explorer/find-element/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/frames/fig0.png b/docs/img/features/elements-explorer/frames/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/frames/fig1.png b/docs/img/features/elements-explorer/frames/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/frames/fig2.png b/docs/img/features/elements-explorer/frames/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/frames/fig3.png b/docs/img/features/elements-explorer/frames/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig1.png b/docs/img/features/elements-explorer/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig2.png b/docs/img/features/elements-explorer/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig3.png b/docs/img/features/elements-explorer/overview/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig4.png b/docs/img/features/elements-explorer/overview/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig5.png b/docs/img/features/elements-explorer/overview/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig6.png b/docs/img/features/elements-explorer/overview/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig7.png b/docs/img/features/elements-explorer/overview/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/elements-explorer/overview/fig8.png b/docs/img/features/elements-explorer/overview/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/add-step.png b/docs/img/features/execute-apitest/add-api-test-as-step/add-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/browse-apitest.png b/docs/img/features/execute-apitest/add-api-test-as-step/browse-apitest.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/create-edit.png b/docs/img/features/execute-apitest/add-api-test-as-step/create-edit.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/import-existing.png b/docs/img/features/execute-apitest/add-api-test-as-step/import-existing.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/select-apitest-window.png b/docs/img/features/execute-apitest/add-api-test-as-step/select-apitest-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/select-test.png b/docs/img/features/execute-apitest/add-api-test-as-step/select-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/add-api-test-as-step/warning.png b/docs/img/features/execute-apitest/add-api-test-as-step/warning.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/passing-variables/add-variable.png b/docs/img/features/execute-apitest/passing-variables/add-variable.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/passing-variables/use-variable-in-web-test.png b/docs/img/features/execute-apitest/passing-variables/use-variable-in-web-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/passing-variables/variable-pane.png b/docs/img/features/execute-apitest/passing-variables/variable-pane.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/execute-apitest/passing-variables/variables-property.png b/docs/img/features/execute-apitest/passing-variables/variables-property.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/advanced-settings.png b/docs/img/features/integration/bug-tracking/configuration/advanced-settings.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/bug-report-icon-navigate-JIRA.png b/docs/img/features/integration/bug-tracking/configuration/bug-report-icon-navigate-JIRA.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/bug-report-icon-navigate.png b/docs/img/features/integration/bug-tracking/configuration/bug-report-icon-navigate.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/bug-report-propt.png b/docs/img/features/integration/bug-tracking/configuration/bug-report-propt.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/choose-advanced-settings.png b/docs/img/features/integration/bug-tracking/configuration/choose-advanced-settings.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig10.png b/docs/img/features/integration/bug-tracking/configuration/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig12.png b/docs/img/features/integration/bug-tracking/configuration/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig13.jpg b/docs/img/features/integration/bug-tracking/configuration/fig13.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig14.jpg b/docs/img/features/integration/bug-tracking/configuration/fig14.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig15.jpg b/docs/img/features/integration/bug-tracking/configuration/fig15.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig15.png b/docs/img/features/integration/bug-tracking/configuration/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig16.jpg b/docs/img/features/integration/bug-tracking/configuration/fig16.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig2.png b/docs/img/features/integration/bug-tracking/configuration/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig3-jira.png b/docs/img/features/integration/bug-tracking/configuration/fig3-jira.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig4.png b/docs/img/features/integration/bug-tracking/configuration/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig5.png b/docs/img/features/integration/bug-tracking/configuration/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig6.png b/docs/img/features/integration/bug-tracking/configuration/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig7.png b/docs/img/features/integration/bug-tracking/configuration/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig8.png b/docs/img/features/integration/bug-tracking/configuration/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/fig9.png b/docs/img/features/integration/bug-tracking/configuration/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/import-from-exploratory.png b/docs/img/features/integration/bug-tracking/configuration/import-from-exploratory.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/old-connect.png b/docs/img/features/integration/bug-tracking/configuration/old-connect.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/old-default-collection.png b/docs/img/features/integration/bug-tracking/configuration/old-default-collection.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/configuration/teampulse.png b/docs/img/features/integration/bug-tracking/configuration/teampulse.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/jira-custom-fields/fig1.png b/docs/img/features/integration/bug-tracking/jira-custom-fields/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/jira-custom-fields/fig2.png b/docs/img/features/integration/bug-tracking/jira-custom-fields/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig1.png b/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig3.png b/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig5.png b/docs/img/features/integration/bug-tracking/launch-bug-dialog/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/launch-bug-dialog/step-righ-click-menu-bug.png b/docs/img/features/integration/bug-tracking/launch-bug-dialog/step-righ-click-menu-bug.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/launch-bug-dialog/test-list-icon.png b/docs/img/features/integration/bug-tracking/launch-bug-dialog/test-list-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig1.png b/docs/img/features/integration/bug-tracking/submit-bug/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig2.png b/docs/img/features/integration/bug-tracking/submit-bug/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig3.png b/docs/img/features/integration/bug-tracking/submit-bug/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig4.png b/docs/img/features/integration/bug-tracking/submit-bug/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig5.png b/docs/img/features/integration/bug-tracking/submit-bug/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/submit-bug/fig6.png b/docs/img/features/integration/bug-tracking/submit-bug/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig1.png b/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig2.png b/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig3.png b/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig4.png b/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig5.png b/docs/img/features/integration/bug-tracking/tfs-custom-fields/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/conectivity-instructions/fig1.png b/docs/img/features/integration/quality-center/conectivity-instructions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/conectivity-instructions/fig2.png b/docs/img/features/integration/quality-center/conectivity-instructions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/conectivity-instructions/fig3.png b/docs/img/features/integration/quality-center/conectivity-instructions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/QC-button.png b/docs/img/features/integration/quality-center/integration/QC-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/fig2.png b/docs/img/features/integration/quality-center/integration/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/fig3.png b/docs/img/features/integration/quality-center/integration/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/fig5.png b/docs/img/features/integration/quality-center/integration/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/fig6.png b/docs/img/features/integration/quality-center/integration/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/quality-center/integration/fig7.png b/docs/img/features/integration/quality-center/integration/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig1.png b/docs/img/features/integration/teampulse/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig2.png b/docs/img/features/integration/teampulse/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig3.png b/docs/img/features/integration/teampulse/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig4.png b/docs/img/features/integration/teampulse/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig5.png b/docs/img/features/integration/teampulse/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig6.png b/docs/img/features/integration/teampulse/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/integration/teampulse/fig7.png b/docs/img/features/integration/teampulse/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/drop-inside-else.png b/docs/img/features/logical-steps/if-else/drop-inside-else.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/drop-inside-if.png b/docs/img/features/logical-steps/if-else/drop-inside-if.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/elem-in-DOM-exist-1.png b/docs/img/features/logical-steps/if-else/elem-in-DOM-exist-1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/elem-in-DOM-exist-if.png b/docs/img/features/logical-steps/if-else/elem-in-DOM-exist-if.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/else-executed.png b/docs/img/features/logical-steps/if-else/else-executed.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/if-executed.png b/docs/img/features/logical-steps/if-else/if-executed.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/quick-step-drop-down.png b/docs/img/features/logical-steps/if-else/quick-step-drop-down.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/rnd-num-gen-page.png b/docs/img/features/logical-steps/if-else/rnd-num-gen-page.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/select-condition-in-if.png b/docs/img/features/logical-steps/if-else/select-condition-in-if.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/step-builder-if-else.png b/docs/img/features/logical-steps/if-else/step-builder-if-else.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/uncheck-verify-step.png b/docs/img/features/logical-steps/if-else/uncheck-verify-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/verify-step-choose.png b/docs/img/features/logical-steps/if-else/verify-step-choose.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/if-else/vs-step-builder.png b/docs/img/features/logical-steps/if-else/vs-step-builder.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/loop/drag-drop-loop.png b/docs/img/features/logical-steps/loop/drag-drop-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/loop/extended-menu-loop.png b/docs/img/features/logical-steps/loop/extended-menu-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/loop/fig1.png b/docs/img/features/logical-steps/loop/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/loop/step-builder-loop.png b/docs/img/features/logical-steps/loop/step-builder-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/loop/vs-step-builder.png b/docs/img/features/logical-steps/loop/vs-step-builder.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/advanced-rec-tool.png b/docs/img/features/logical-steps/while-loop/advanced-rec-tool.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/checkbox-unchecked.png b/docs/img/features/logical-steps/while-loop/checkbox-unchecked.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/drag-drop-step-in-loop.png b/docs/img/features/logical-steps/while-loop/drag-drop-step-in-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/extended-menu-while-loop.png b/docs/img/features/logical-steps/while-loop/extended-menu-while-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/fig10.png b/docs/img/features/logical-steps/while-loop/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/fig13.jpg b/docs/img/features/logical-steps/while-loop/fig13.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/fig14.jpg b/docs/img/features/logical-steps/while-loop/fig14.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/rnd-gen-element-drop-down.png b/docs/img/features/logical-steps/while-loop/rnd-gen-element-drop-down.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/rnd-gen-page.png b/docs/img/features/logical-steps/while-loop/rnd-gen-page.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/step-builder-content.png b/docs/img/features/logical-steps/while-loop/step-builder-content.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/step-builder-while-loop.png b/docs/img/features/logical-steps/while-loop/step-builder-while-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/logical-steps/while-loop/vs-step-builder-while-loop.png b/docs/img/features/logical-steps/while-loop/vs-step-builder-while-loop.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/overview/colapse-button.png b/docs/img/features/project-explorer/overview/colapse-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/overview/folder-right-click-menu.png b/docs/img/features/project-explorer/overview/folder-right-click-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/overview/project-explorer-navigate.png b/docs/img/features/project-explorer/overview/project-explorer-navigate.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/overview/projects-right-click-menu.png b/docs/img/features/project-explorer/overview/projects-right-click-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/overview/test-right-click-menu.png b/docs/img/features/project-explorer/overview/test-right-click-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/allsteps-filter-checkbox.png b/docs/img/features/project-explorer/search-and-filter-tests/allsteps-filter-checkbox.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/allsteps-filter.png b/docs/img/features/project-explorer/search-and-filter-tests/allsteps-filter.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/both-in-dev-search-filters.png b/docs/img/features/project-explorer/search-and-filter-tests/both-in-dev-search-filters.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/both-in-dev-usage-filters.png b/docs/img/features/project-explorer/search-and-filter-tests/both-in-dev-usage-filters.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/both-search-allsteps-filter.png b/docs/img/features/project-explorer/search-and-filter-tests/both-search-allsteps-filter.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/both-usage-search-filters.png b/docs/img/features/project-explorer/search-and-filter-tests/both-usage-search-filters.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/filter-by-usage-from-other-tests-button.png b/docs/img/features/project-explorer/search-and-filter-tests/filter-by-usage-from-other-tests-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/searchbar-projects.png b/docs/img/features/project-explorer/search-and-filter-tests/searchbar-projects.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/test-in-dev-filter-button.png b/docs/img/features/project-explorer/search-and-filter-tests/test-in-dev-filter-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/test-step-selector.jpg b/docs/img/features/project-explorer/search-and-filter-tests/test-step-selector.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/type-search-filter.png b/docs/img/features/project-explorer/search-and-filter-tests/type-search-filter.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-explorer/search-and-filter-tests/used-by-right-click-menu.png b/docs/img/features/project-explorer/search-and-filter-tests/used-by-right-click-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/analytics/fig1.png b/docs/img/features/project-settings/analytics/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig1.png b/docs/img/features/project-settings/browsers/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig2.png b/docs/img/features/project-settings/browsers/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig3.png b/docs/img/features/project-settings/browsers/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig4.png b/docs/img/features/project-settings/browsers/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig5.png b/docs/img/features/project-settings/browsers/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/browsers/fig5a.png b/docs/img/features/project-settings/browsers/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/element-images/fig1.png b/docs/img/features/project-settings/element-images/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/emulated-device/fig1.png b/docs/img/features/project-settings/emulated-device/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/emulated-device/fig2.png b/docs/img/features/project-settings/emulated-device/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/emulated-device/fig3.png b/docs/img/features/project-settings/emulated-device/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/emulated-device/fig4.png b/docs/img/features/project-settings/emulated-device/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/find-logic/fig1.png b/docs/img/features/project-settings/find-logic/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/find-logic/fig2.png b/docs/img/features/project-settings/find-logic/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/find-logic/fig3.png b/docs/img/features/project-settings/find-logic/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/general/fig1.png b/docs/img/features/project-settings/general/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/general/fig2.png b/docs/img/features/project-settings/general/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/general/fig3.png b/docs/img/features/project-settings/general/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/installation/fig1.png b/docs/img/features/project-settings/installation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/overview/proj-settings-icon.png b/docs/img/features/project-settings/overview/proj-settings-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/overview/vs-proj-setting-icons.png b/docs/img/features/project-settings/overview/vs-proj-setting-icons.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/recording-options/fig1.png b/docs/img/features/project-settings/recording-options/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/recording-options/fig2.png b/docs/img/features/project-settings/recording-options/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/recording-options/fig3.png b/docs/img/features/project-settings/recording-options/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/script-options/fig1.png b/docs/img/features/project-settings/script-options/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig1.png b/docs/img/features/project-settings/theme/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig10.png b/docs/img/features/project-settings/theme/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig11.png b/docs/img/features/project-settings/theme/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig12.png b/docs/img/features/project-settings/theme/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig2.png b/docs/img/features/project-settings/theme/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig3.png b/docs/img/features/project-settings/theme/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig4.png b/docs/img/features/project-settings/theme/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig5.png b/docs/img/features/project-settings/theme/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig6.png b/docs/img/features/project-settings/theme/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig7.png b/docs/img/features/project-settings/theme/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig8.png b/docs/img/features/project-settings/theme/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/theme/fig9.png b/docs/img/features/project-settings/theme/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/translators/fig1.png b/docs/img/features/project-settings/translators/fig1.png
old mode 100644
new mode 100755
index 460a7aab..42268b9c
Binary files a/docs/img/features/project-settings/translators/fig1.png and b/docs/img/features/project-settings/translators/fig1.png differ
diff --git a/docs/img/features/project-settings/translators/fig2.png b/docs/img/features/project-settings/translators/fig2.png
old mode 100644
new mode 100755
index 58ec93d6..79cbfa1e
Binary files a/docs/img/features/project-settings/translators/fig2.png and b/docs/img/features/project-settings/translators/fig2.png differ
diff --git a/docs/img/features/project-settings/translators/fig3.png b/docs/img/features/project-settings/translators/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/project-settings/updates/fig1.png b/docs/img/features/project-settings/updates/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/current-date/extended-menu-current-DnT.png b/docs/img/features/random-data/current-date/extended-menu-current-DnT.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/current-date/step-builder-current-DnT.png b/docs/img/features/random-data/current-date/step-builder-current-DnT.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-date/extended-menu-rnd-dnt.png b/docs/img/features/random-data/random-date/extended-menu-rnd-dnt.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-date/step-cuilder-DnT.png b/docs/img/features/random-data/random-date/step-cuilder-DnT.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-number/extended-menu-rnd-num.png b/docs/img/features/random-data/random-number/extended-menu-rnd-num.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-number/step-builder-rnd-num.png b/docs/img/features/random-data/random-number/step-builder-rnd-num.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-string/extended-menu-rnd-str.png b/docs/img/features/random-data/random-string/extended-menu-rnd-str.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/random-data/random-string/step-builder-rnd-string.png b/docs/img/features/random-data/random-string/step-builder-rnd-string.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/browser-control/fig1.png b/docs/img/features/recorder/advanced-recording-tools/browser-control/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/common-steps/fig1.png b/docs/img/features/recorder/advanced-recording-tools/common-steps/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig1.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig2.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig3.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig4.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig5.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig6.png b/docs/img/features/recorder/advanced-recording-tools/dom-explorer/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig10.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig6.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig7.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig8.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig9.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/javascript-events/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/javascript-events/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/javascript-events/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/javascript-events/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/relative-mouse-click/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/scroll-actions/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/actions/scroll-actions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig6.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig7.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/extracted-var-binding.gif b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/extracted-var-binding.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig4a.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig4a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig6.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig7.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig8.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig9.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/extraction/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig10.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig6.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig7.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig8.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig9.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/gif9.gif b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/image-verification/gif9.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/add-quick-verification.gif b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/add-quick-verification.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig0.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig1.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig10.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig2.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig5.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig6.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig7.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig8.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig9.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/add-wait-step.gif b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/add-wait-step.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/fig3.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/fig4.png b/docs/img/features/recorder/advanced-recording-tools/element-steps/verifications/wait/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/anim1.gif b/docs/img/features/recorder/compact-recording-toolbar/anim1.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig1.png b/docs/img/features/recorder/compact-recording-toolbar/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig10.png b/docs/img/features/recorder/compact-recording-toolbar/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig11.png b/docs/img/features/recorder/compact-recording-toolbar/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig12.png b/docs/img/features/recorder/compact-recording-toolbar/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig13.png b/docs/img/features/recorder/compact-recording-toolbar/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig2.png b/docs/img/features/recorder/compact-recording-toolbar/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig3.png b/docs/img/features/recorder/compact-recording-toolbar/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig4.png b/docs/img/features/recorder/compact-recording-toolbar/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig5.png b/docs/img/features/recorder/compact-recording-toolbar/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig6.png b/docs/img/features/recorder/compact-recording-toolbar/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig7.png b/docs/img/features/recorder/compact-recording-toolbar/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig8.png b/docs/img/features/recorder/compact-recording-toolbar/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/compact-recording-toolbar/fig9.png b/docs/img/features/recorder/compact-recording-toolbar/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/fig1.png b/docs/img/features/recorder/highlighting-menu/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/mouse-actions/fig1.png b/docs/img/features/recorder/highlighting-menu/mouse-actions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/mouse-actions/fig2.png b/docs/img/features/recorder/highlighting-menu/mouse-actions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/mouse-actions/fig3.png b/docs/img/features/recorder/highlighting-menu/mouse-actions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/mouse-actions/fig4.png b/docs/img/features/recorder/highlighting-menu/mouse-actions/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/mouse-actions/fig5.png b/docs/img/features/recorder/highlighting-menu/mouse-actions/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/scroll-actions/fig1.png b/docs/img/features/recorder/highlighting-menu/scroll-actions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/scroll-actions/fig2.png b/docs/img/features/recorder/highlighting-menu/scroll-actions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/highlighting-menu/scroll-actions/fig3.png b/docs/img/features/recorder/highlighting-menu/scroll-actions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/test-recorder/fig6.png b/docs/img/features/recorder/test-recorder/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/test-recorder/fig7.png b/docs/img/features/recorder/test-recorder/fig7.png
old mode 100644
new mode 100755
index b8773060..f8b4104e
Binary files a/docs/img/features/recorder/test-recorder/fig7.png and b/docs/img/features/recorder/test-recorder/fig7.png differ
diff --git a/docs/img/features/recorder/translators/fig1.png b/docs/img/features/recorder/translators/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/recorder/translators/fig2.png b/docs/img/features/recorder/translators/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/change-service-account/fig1.png b/docs/img/features/scheduling-test-runs/change-service-account/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/change-service-account/fig2.png b/docs/img/features/scheduling-test-runs/change-service-account/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig1.png b/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig2.png b/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig3.png b/docs/img/features/scheduling-test-runs/connect-to-scheduling-server/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig1.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig1a.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2a.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2b.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig2b.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig3.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/connect-via-proxy/fig3a.png b/docs/img/features/scheduling-test-runs/connect-via-proxy/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/change-button.png b/docs/img/features/scheduling-test-runs/create-execution-server/change-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig0.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig1.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig10.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig11.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig12.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig1a.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig2-configure-button.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig2-configure-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig2.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig3.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig4.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig5.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig6.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig6a.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig6a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig6b.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig6b.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig6c.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig6c.png
old mode 100644
new mode 100755
index 716b1507..4c8d63aa
Binary files a/docs/img/features/scheduling-test-runs/create-execution-server/fig6c.png and b/docs/img/features/scheduling-test-runs/create-execution-server/fig6c.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig7.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig8.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/fig9.png b/docs/img/features/scheduling-test-runs/create-execution-server/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/start-session-monitor-config.png b/docs/img/features/scheduling-test-runs/create-execution-server/start-session-monitor-config.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-execution-server/start-session-monitor-win-menu.png b/docs/img/features/scheduling-test-runs/create-execution-server/start-session-monitor-win-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-restart-after-update.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-restart-after-update.png
new file mode 100644
index 00000000..ffd93f2d
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-restart-after-update.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png
new file mode 100644
index 00000000..84ac3140
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-replace-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-replace-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/communication-tab.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-custom-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-custom-key.png
new file mode 100644
index 00000000..d7c26e14
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-custom-key.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-default-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-default-key.png
new file mode 100644
index 00000000..c06f48c2
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-default-key.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-generate-key.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-generate-key.png
new file mode 100644
index 00000000..994a171d
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-generate-key.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-tab.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-tab.png
new file mode 100644
index 00000000..46d1dd2a
Binary files /dev/null and b/docs/img/features/scheduling-test-runs/create-scheduling-server/encryption-tab.png differ
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/execution-client-tab.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/execution-client-tab.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig1.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig14.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig2new.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig2new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig3new.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig3new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig4new.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig4new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig5a.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig5new.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig5new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-scheduling-server/fig7.png b/docs/img/features/scheduling-test-runs/create-scheduling-server/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-storage-server/fig1.png b/docs/img/features/scheduling-test-runs/create-storage-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-storage-server/fig1new.png b/docs/img/features/scheduling-test-runs/create-storage-server/fig1new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/create-storage-server/fig2new.png b/docs/img/features/scheduling-test-runs/create-storage-server/fig2new.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig1.png b/docs/img/features/scheduling-test-runs/install-runtime/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig2.png b/docs/img/features/scheduling-test-runs/install-runtime/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig3.png b/docs/img/features/scheduling-test-runs/install-runtime/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig4.png b/docs/img/features/scheduling-test-runs/install-runtime/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig5.png b/docs/img/features/scheduling-test-runs/install-runtime/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig6.png b/docs/img/features/scheduling-test-runs/install-runtime/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig7.png b/docs/img/features/scheduling-test-runs/install-runtime/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/install-runtime/fig8.png b/docs/img/features/scheduling-test-runs/install-runtime/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig1.png b/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig2.png b/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig3.png b/docs/img/features/scheduling-test-runs/local-run-all-in-one/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/migrate-database/fig1.png b/docs/img/features/scheduling-test-runs/migrate-database/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/migrate-database/fig2.png b/docs/img/features/scheduling-test-runs/migrate-database/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/migrate-database/fig3.png b/docs/img/features/scheduling-test-runs/migrate-database/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/overview/fig1.png b/docs/img/features/scheduling-test-runs/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/configure-execution-server-button.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/configure-execution-server-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig1.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig2.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig2a.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig3.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig3a.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig4.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig5.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig5a.png b/docs/img/features/scheduling-test-runs/remote-run-all-in-one/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig1.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig2.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig3.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig4.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig5.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig6.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig7.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/run-list-remotely/fig8.png b/docs/img/features/scheduling-test-runs/run-list-remotely/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig1.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig10.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig11.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig12.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig13.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig2.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig3.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig4.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig5.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig6.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig7.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig8.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/schedule-execution/fig9.png b/docs/img/features/scheduling-test-runs/schedule-execution/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig1.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig2.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig3.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig4.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig5.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig6.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig7.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/scheduling-results/fig8.png b/docs/img/features/scheduling-test-runs/scheduling-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig1.png b/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig2.png b/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig3.png b/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig4.png b/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig5.png b/docs/img/features/scheduling-test-runs/stop-cancel-scheduled-job/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/tts-command-line-client/fig1.png b/docs/img/features/scheduling-test-runs/tts-command-line-client/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/tts-command-line-client/fig2.png b/docs/img/features/scheduling-test-runs/tts-command-line-client/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/tts-command-line-client/fig3.png b/docs/img/features/scheduling-test-runs/tts-command-line-client/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/tts-command-line-client/fig4.png b/docs/img/features/scheduling-test-runs/tts-command-line-client/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/tts-command-line-client/fig5.png b/docs/img/features/scheduling-test-runs/tts-command-line-client/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/1-22-2019 10-24-26 AM.png b/docs/img/features/scheduling-test-runs/view-execution-status/1-22-2019 10-24-26 AM.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig1.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2_MongoServiceDown.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2_MongoServiceDown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2_dialogHandlerUpdate.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2_dialogHandlerUpdate.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2_nonCalibrated.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2_nonCalibrated.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2_schedulingServiceDown.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2_schedulingServiceDown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2_storageServiceDown.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2_storageServiceDown.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2a.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig2b.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig2b.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig3.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig3_VeryLongNameTest.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig3_VeryLongNameTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig3_runningTest.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig3_runningTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig3_unreachableExecutionMachine.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig3_unreachableExecutionMachine.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/scheduling-test-runs/view-execution-status/fig4.png b/docs/img/features/scheduling-test-runs/view-execution-status/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/connect-to-tfs/fig1.png b/docs/img/features/source-control/connect-to-tfs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/connect-to-tfs/fig2.png b/docs/img/features/source-control/connect-to-tfs/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/connect-to-tfs/fig3.png b/docs/img/features/source-control/connect-to-tfs/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/connect-to-tfs/fig4.png b/docs/img/features/source-control/connect-to-tfs/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/disconnect-from-tfs/fig1.png b/docs/img/features/source-control/disconnect-from-tfs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/disconnect-from-tfs/fig2.png b/docs/img/features/source-control/disconnect-from-tfs/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig10-commited-locally.png b/docs/img/features/source-control/git/branch-management/fig10-commited-locally.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig11-commited-remotely.png b/docs/img/features/source-control/git/branch-management/fig11-commited-remotely.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig12-checkout.png b/docs/img/features/source-control/git/branch-management/fig12-checkout.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig12-pull.png b/docs/img/features/source-control/git/branch-management/fig12-pull.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig13-deletel.png b/docs/img/features/source-control/git/branch-management/fig13-deletel.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig1_localRepo.png b/docs/img/features/source-control/git/branch-management/fig1_localRepo.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig2_remote_availableOptions.png b/docs/img/features/source-control/git/branch-management/fig2_remote_availableOptions.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig3_ManageBranches.png b/docs/img/features/source-control/git/branch-management/fig3_ManageBranches.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig3_remote_ManageBranches.png b/docs/img/features/source-control/git/branch-management/fig3_remote_ManageBranches.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig4_defaultBranch.png b/docs/img/features/source-control/git/branch-management/fig4_defaultBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig4_remote_defaultBranch.png b/docs/img/features/source-control/git/branch-management/fig4_remote_defaultBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig5_createBranch.png b/docs/img/features/source-control/git/branch-management/fig5_createBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig5_remote_createBranch.png b/docs/img/features/source-control/git/branch-management/fig5_remote_createBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig6_newBranch.png b/docs/img/features/source-control/git/branch-management/fig6_newBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig6_remote_PushNewBranch.png b/docs/img/features/source-control/git/branch-management/fig6_remote_PushNewBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig6_remote_newBranch.png b/docs/img/features/source-control/git/branch-management/fig6_remote_newBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig7_currentBranch.png b/docs/img/features/source-control/git/branch-management/fig7_currentBranch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig8-refresh.png b/docs/img/features/source-control/git/branch-management/fig8-refresh.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/branch-management/fig9-checkout-remote-branch.png b/docs/img/features/source-control/git/branch-management/fig9-checkout-remote-branch.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/connect-to-git/fig1.png b/docs/img/features/source-control/git/connect-to-git/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/connect-to-git/fig2.png b/docs/img/features/source-control/git/connect-to-git/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/connect-to-git/fig3.png b/docs/img/features/source-control/git/connect-to-git/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/connect-to-git/fig4_removeSC.png b/docs/img/features/source-control/git/connect-to-git/fig4_removeSC.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/open-git-project/fig1.png b/docs/img/features/source-control/git/open-git-project/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/open-git-project/fig2.png b/docs/img/features/source-control/git/open-git-project/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/open-git-project/fig6.png b/docs/img/features/source-control/git/open-git-project/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/overview/fig1.png b/docs/img/features/source-control/git/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/supported-git-commands/fig1.png b/docs/img/features/source-control/git/supported-git-commands/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/git/supported-git-commands/fig2.png b/docs/img/features/source-control/git/supported-git-commands/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig1.png b/docs/img/features/source-control/open-tfs-project/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig10.png b/docs/img/features/source-control/open-tfs-project/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig2.png b/docs/img/features/source-control/open-tfs-project/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig3.png b/docs/img/features/source-control/open-tfs-project/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig4.png b/docs/img/features/source-control/open-tfs-project/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig5.png b/docs/img/features/source-control/open-tfs-project/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig6.png b/docs/img/features/source-control/open-tfs-project/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig7.png b/docs/img/features/source-control/open-tfs-project/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig8.png b/docs/img/features/source-control/open-tfs-project/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/open-tfs-project/fig9.png b/docs/img/features/source-control/open-tfs-project/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/overview/fig1.png b/docs/img/features/source-control/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/project-item-options/fig1.png b/docs/img/features/source-control/project-item-options/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/team-foundation-service/fig1.png b/docs/img/features/source-control/team-foundation-service/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/team-foundation-service/fig2.png b/docs/img/features/source-control/team-foundation-service/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/source-control/team-foundation-service/fig3.png b/docs/img/features/source-control/team-foundation-service/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig1.png b/docs/img/features/test-lists/create-test-list/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig2.png b/docs/img/features/test-lists/create-test-list/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig2_FilterTestsByType.png b/docs/img/features/test-lists/create-test-list/fig2_FilterTestsByType.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig2_collapse.png b/docs/img/features/test-lists/create-test-list/fig2_collapse.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig2_searchField.png b/docs/img/features/test-lists/create-test-list/fig2_searchField.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig2a.png b/docs/img/features/test-lists/create-test-list/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig3.png b/docs/img/features/test-lists/create-test-list/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig4.png b/docs/img/features/test-lists/create-test-list/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig5.png b/docs/img/features/test-lists/create-test-list/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig6.png b/docs/img/features/test-lists/create-test-list/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig7.png b/docs/img/features/test-lists/create-test-list/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/create-test-list/fig8.png b/docs/img/features/test-lists/create-test-list/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/modify-test-list/fig1.png b/docs/img/features/test-lists/modify-test-list/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/modify-test-list/fig2.png b/docs/img/features/test-lists/modify-test-list/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/test-list-settings/fig1.png b/docs/img/features/test-lists/test-list-settings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/test-list-settings/fig2.png b/docs/img/features/test-lists/test-list-settings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/test-list-settings/fig3.png b/docs/img/features/test-lists/test-list-settings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/test-list-settings/fig4.png b/docs/img/features/test-lists/test-list-settings/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-lists/test-list-settings/fig5.png b/docs/img/features/test-lists/test-list-settings/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/change-step-target-element/select-element.png b/docs/img/features/test-maintenance/change-step-target-element/select-element.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/change-step-target-element/step-properties.png b/docs/img/features/test-maintenance/change-step-target-element/step-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/export-visual-studio/export-VS.png b/docs/img/features/test-maintenance/export-visual-studio/export-VS.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/export-visual-studio/fig3.png b/docs/img/features/test-maintenance/export-visual-studio/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/export-visual-studio/fig4.png b/docs/img/features/test-maintenance/export-visual-studio/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/export-visual-studio/fig5.png b/docs/img/features/test-maintenance/export-visual-studio/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/export-visual-studio/select-VS-version-propt.png b/docs/img/features/test-maintenance/export-visual-studio/select-VS-version-propt.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/reorder-test-steps/arrows-steps.png b/docs/img/features/test-maintenance/reorder-test-steps/arrows-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/reorder-test-steps/clear-icon.png b/docs/img/features/test-maintenance/reorder-test-steps/clear-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/reorder-test-steps/drag-drop-step.png b/docs/img/features/test-maintenance/reorder-test-steps/drag-drop-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/reorder-test-steps/mark-step.png b/docs/img/features/test-maintenance/reorder-test-steps/mark-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/search-test-steps/both-filters-and-search.png b/docs/img/features/test-maintenance/search-test-steps/both-filters-and-search.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/search-test-steps/drop-down-filter.png b/docs/img/features/test-maintenance/search-test-steps/drop-down-filter.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/search-test-steps/filter-checked.png b/docs/img/features/test-maintenance/search-test-steps/filter-checked.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/search-test-steps/search-bar.png b/docs/img/features/test-maintenance/search-test-steps/search-bar.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/search-test-steps/type-search-bar-filter.png b/docs/img/features/test-maintenance/search-test-steps/type-search-bar-filter.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/action-icon.png b/docs/img/features/test-maintenance/steps-pane/action-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/breakpoint-dot.png b/docs/img/features/test-maintenance/steps-pane/breakpoint-dot.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/code-behind-icon.png b/docs/img/features/test-maintenance/steps-pane/code-behind-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/continue-on-failure.png b/docs/img/features/test-maintenance/steps-pane/continue-on-failure.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/delete-icon.png b/docs/img/features/test-maintenance/steps-pane/delete-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/description-example.png b/docs/img/features/test-maintenance/steps-pane/description-example.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/edit-icon.png b/docs/img/features/test-maintenance/steps-pane/edit-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/redo-icon.png b/docs/img/features/test-maintenance/steps-pane/redo-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/shown-inloine-editor.png b/docs/img/features/test-maintenance/steps-pane/shown-inloine-editor.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/step-checkbox.png b/docs/img/features/test-maintenance/steps-pane/step-checkbox.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/step-down.png b/docs/img/features/test-maintenance/steps-pane/step-down.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/step-marker.png b/docs/img/features/test-maintenance/steps-pane/step-marker.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/step-order.png b/docs/img/features/test-maintenance/steps-pane/step-order.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/step-up.png b/docs/img/features/test-maintenance/steps-pane/step-up.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/steps-filter-drob-down.png b/docs/img/features/test-maintenance/steps-pane/steps-filter-drob-down.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/steps-pane-overview.png b/docs/img/features/test-maintenance/steps-pane/steps-pane-overview.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/steps-pane/undo-icon.png b/docs/img/features/test-maintenance/steps-pane/undo-icon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/change-storyboard-orientaiton.png b/docs/img/features/test-maintenance/storyboard/change-storyboard-orientaiton.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/fig10.png b/docs/img/features/test-maintenance/storyboard/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/fig9.png b/docs/img/features/test-maintenance/storyboard/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/recapture-storyboard.png b/docs/img/features/test-maintenance/storyboard/recapture-storyboard.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/scale-window.png b/docs/img/features/test-maintenance/storyboard/scale-window.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/specific-img-storyboard.png b/docs/img/features/test-maintenance/storyboard/specific-img-storyboard.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/storyboard-panel.png b/docs/img/features/test-maintenance/storyboard/storyboard-panel.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/storyboard-tab-location.png b/docs/img/features/test-maintenance/storyboard/storyboard-tab-location.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/storyboard-to-HTML.png b/docs/img/features/test-maintenance/storyboard/storyboard-to-HTML.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/storyboard/switch-to-steps-in-test.png b/docs/img/features/test-maintenance/storyboard/switch-to-steps-in-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-properties-standalone/test-properties-navigate.png b/docs/img/features/test-maintenance/test-properties-standalone/test-properties-navigate.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-properties-vs/fig1.png b/docs/img/features/test-maintenance/test-properties-vs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-properties-vs/fig2.png b/docs/img/features/test-maintenance/test-properties-vs/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-step-context-menu/right-click-1.png b/docs/img/features/test-maintenance/test-step-context-menu/right-click-1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-step-context-menu/right-click-2.png b/docs/img/features/test-maintenance/test-step-context-menu/right-click-2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-step-properties/fig2.png b/docs/img/features/test-maintenance/test-step-properties/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/test-step-properties/step-properties.png b/docs/img/features/test-maintenance/test-step-properties/step-properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/tests-in-development/right-click-remove-dev.png b/docs/img/features/test-maintenance/tests-in-development/right-click-remove-dev.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/tests-in-development/right-click-test.png b/docs/img/features/test-maintenance/tests-in-development/right-click-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/tests-in-development/test-in-dev-list-settings.png b/docs/img/features/test-maintenance/tests-in-development/test-in-dev-list-settings.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/tests-in-development/test-in-dev-mark.png b/docs/img/features/test-maintenance/tests-in-development/test-in-dev-mark.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-maintenance/tests-in-development/test-in-dev-test-list.png b/docs/img/features/test-maintenance/tests-in-development/test-in-dev-test-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig1.png b/docs/img/features/test-runners/add-path-environment-variables/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig10.png b/docs/img/features/test-runners/add-path-environment-variables/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig11.png b/docs/img/features/test-runners/add-path-environment-variables/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig12.png b/docs/img/features/test-runners/add-path-environment-variables/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig2.png b/docs/img/features/test-runners/add-path-environment-variables/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig3.png b/docs/img/features/test-runners/add-path-environment-variables/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig4.png b/docs/img/features/test-runners/add-path-environment-variables/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig5.png b/docs/img/features/test-runners/add-path-environment-variables/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig6.png b/docs/img/features/test-runners/add-path-environment-variables/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig7.png b/docs/img/features/test-runners/add-path-environment-variables/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig8.png b/docs/img/features/test-runners/add-path-environment-variables/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/add-path-environment-variables/fig9.png b/docs/img/features/test-runners/add-path-environment-variables/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig1.png b/docs/img/features/test-runners/artoftest-runner/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig10.png b/docs/img/features/test-runners/artoftest-runner/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig11.png b/docs/img/features/test-runners/artoftest-runner/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig12.png b/docs/img/features/test-runners/artoftest-runner/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig2.png b/docs/img/features/test-runners/artoftest-runner/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig3.png b/docs/img/features/test-runners/artoftest-runner/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig4.png b/docs/img/features/test-runners/artoftest-runner/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig5.png b/docs/img/features/test-runners/artoftest-runner/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig6.png b/docs/img/features/test-runners/artoftest-runner/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig7.png b/docs/img/features/test-runners/artoftest-runner/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig8.png b/docs/img/features/test-runners/artoftest-runner/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/artoftest-runner/fig9.png b/docs/img/features/test-runners/artoftest-runner/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig1.png b/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig2.png b/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig3.png b/docs/img/features/test-runners/integrate-task-scheduler-with-artoftest/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/manual-runner/fig1.png b/docs/img/features/test-runners/manual-runner/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/manual-runner/fig2.png b/docs/img/features/test-runners/manual-runner/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/manual-runner/fig3.png b/docs/img/features/test-runners/manual-runner/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig1.png b/docs/img/features/test-runners/mstest/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig10.png b/docs/img/features/test-runners/mstest/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig2.png b/docs/img/features/test-runners/mstest/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig3.png b/docs/img/features/test-runners/mstest/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig4.png b/docs/img/features/test-runners/mstest/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig5.png b/docs/img/features/test-runners/mstest/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig6.png b/docs/img/features/test-runners/mstest/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig7.png b/docs/img/features/test-runners/mstest/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig8.png b/docs/img/features/test-runners/mstest/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/mstest/fig9.png b/docs/img/features/test-runners/mstest/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/telerik-test-runner/fig1.png b/docs/img/features/test-runners/telerik-test-runner/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/telerik-test-runner/fig2.png b/docs/img/features/test-runners/telerik-test-runner/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/test-runners/telerik-test-runner/fig3.png b/docs/img/features/test-runners/telerik-test-runner/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/launch-tool/fig1.png b/docs/img/features/testing-types/exploratory-testing/launch-tool/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/launch-tool/fig2.png b/docs/img/features/testing-types/exploratory-testing/launch-tool/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/launch-tool/fig3.png b/docs/img/features/testing-types/exploratory-testing/launch-tool/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/launch-tool/fig4.png b/docs/img/features/testing-types/exploratory-testing/launch-tool/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/overview/fig1.png b/docs/img/features/testing-types/exploratory-testing/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/provide-feedback/fig1.png b/docs/img/features/testing-types/exploratory-testing/provide-feedback/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/exploratory-testing/provide-feedback/fig2.png b/docs/img/features/testing-types/exploratory-testing/provide-feedback/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/add-custom-cookies/fig1.png b/docs/img/features/testing-types/load-testing/add-custom-cookies/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/add-custom-cookies/fig2.png b/docs/img/features/testing-types/load-testing/add-custom-cookies/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/add-custom-cookies/fig3.png b/docs/img/features/testing-types/load-testing/add-custom-cookies/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/add-custom-cookies/fig4.png b/docs/img/features/testing-types/load-testing/add-custom-cookies/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/add-custom-cookies/fig5.png b/docs/img/features/testing-types/load-testing/add-custom-cookies/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/adding-user-profiles/fig10.png b/docs/img/features/testing-types/load-testing/adding-user-profiles/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/adding-user-profiles/fig8.png b/docs/img/features/testing-types/load-testing/adding-user-profiles/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/adding-user-profiles/fig9.png b/docs/img/features/testing-types/load-testing/adding-user-profiles/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig1.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig10.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig11.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig12.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig13.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig14.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig15.gif b/docs/img/features/testing-types/load-testing/analyzing-results/fig15.gif
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig15.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig16.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig1a.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig2.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig3.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig4.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig5.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig6.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig7.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig8.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/analyzing-results/fig9.png b/docs/img/features/testing-types/load-testing/analyzing-results/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/capturing-traffic/fig1.png b/docs/img/features/testing-types/load-testing/capturing-traffic/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/capturing-traffic/fig2.png b/docs/img/features/testing-types/load-testing/capturing-traffic/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/capturing-traffic/fig3.png b/docs/img/features/testing-types/load-testing/capturing-traffic/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/capturing-traffic/fig4.png b/docs/img/features/testing-types/load-testing/capturing-traffic/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 19 52.png b/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 19 52.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 20 29.png b/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 20 29.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 21 51.png b/docs/img/features/testing-types/load-testing/configure-remote-device/Photo 24.11.14, 16 21 51.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig1.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig10.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig11.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig2.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig3.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig5.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig6.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig7.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig8.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/configure-remote-device/fig9.png b/docs/img/features/testing-types/load-testing/configure-remote-device/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/data-driving/fig1.png b/docs/img/features/testing-types/load-testing/data-driving/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/data-driving/fig2.png b/docs/img/features/testing-types/load-testing/data-driving/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig1.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig11.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig12.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig13.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig14.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig2.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig3.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig4.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig5.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig6.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig7.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig7a.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig7a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig7b.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig7b.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/dynamic-targets/fig8.png b/docs/img/features/testing-types/load-testing/dynamic-targets/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/export-results/fig1.png b/docs/img/features/testing-types/load-testing/export-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/export-results/fig2.png b/docs/img/features/testing-types/load-testing/export-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/export-results/fig3.png b/docs/img/features/testing-types/load-testing/export-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/export-results/fig4.png b/docs/img/features/testing-types/load-testing/export-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/export-results/fig5.png b/docs/img/features/testing-types/load-testing/export-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/filter-user-profile/fig1.png b/docs/img/features/testing-types/load-testing/filter-user-profile/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/filter-user-profile/fig2.png b/docs/img/features/testing-types/load-testing/filter-user-profile/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/filter-user-profile/fig3.png b/docs/img/features/testing-types/load-testing/filter-user-profile/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/filter-user-profile/fig4.png b/docs/img/features/testing-types/load-testing/filter-user-profile/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/getting-started/fig1.png b/docs/img/features/testing-types/load-testing/getting-started/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/importing-traffic/fig1.png b/docs/img/features/testing-types/load-testing/importing-traffic/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/importing-traffic/fig2.png b/docs/img/features/testing-types/load-testing/importing-traffic/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/importing-traffic/fig3.png b/docs/img/features/testing-types/load-testing/importing-traffic/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/importing-traffic/fig4.png b/docs/img/features/testing-types/load-testing/importing-traffic/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/importing-traffic/fig5.png b/docs/img/features/testing-types/load-testing/importing-traffic/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/manage-windows-auth/fig1.png b/docs/img/features/testing-types/load-testing/manage-windows-auth/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/manage-windows-auth/fig2.png b/docs/img/features/testing-types/load-testing/manage-windows-auth/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/manage-windows-auth/fig3.png b/docs/img/features/testing-types/load-testing/manage-windows-auth/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/manage-windows-auth/fig4.png b/docs/img/features/testing-types/load-testing/manage-windows-auth/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/manage-windows-auth/fig5.png b/docs/img/features/testing-types/load-testing/manage-windows-auth/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig1.png b/docs/img/features/testing-types/load-testing/managing-vu/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig2.png b/docs/img/features/testing-types/load-testing/managing-vu/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig2a.png b/docs/img/features/testing-types/load-testing/managing-vu/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig3.png b/docs/img/features/testing-types/load-testing/managing-vu/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig3a.png b/docs/img/features/testing-types/load-testing/managing-vu/fig3a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig3b.png b/docs/img/features/testing-types/load-testing/managing-vu/fig3b.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig4.png b/docs/img/features/testing-types/load-testing/managing-vu/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig5.png b/docs/img/features/testing-types/load-testing/managing-vu/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig6.png b/docs/img/features/testing-types/load-testing/managing-vu/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/managing-vu/fig7.png b/docs/img/features/testing-types/load-testing/managing-vu/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig10.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig11.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig2.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig3.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig4.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig5.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig6.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig7.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig8.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/modifying-tests/fig9.png b/docs/img/features/testing-types/load-testing/modifying-tests/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig1.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig2.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig3.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig4.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig5.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig6.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig8.png b/docs/img/features/testing-types/load-testing/monitor-perf-metrics/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/overview/fig1.png b/docs/img/features/testing-types/load-testing/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig1.png b/docs/img/features/testing-types/load-testing/running-tests/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig1a.png b/docs/img/features/testing-types/load-testing/running-tests/fig1a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig2.png b/docs/img/features/testing-types/load-testing/running-tests/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig3.png b/docs/img/features/testing-types/load-testing/running-tests/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig4.png b/docs/img/features/testing-types/load-testing/running-tests/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig5.png b/docs/img/features/testing-types/load-testing/running-tests/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig6.png b/docs/img/features/testing-types/load-testing/running-tests/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig7.png b/docs/img/features/testing-types/load-testing/running-tests/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/running-tests/fig8.png b/docs/img/features/testing-types/load-testing/running-tests/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig1.png b/docs/img/features/testing-types/load-testing/test-settings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig2.png b/docs/img/features/testing-types/load-testing/test-settings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig3.png b/docs/img/features/testing-types/load-testing/test-settings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig4.png b/docs/img/features/testing-types/load-testing/test-settings/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig4a.png b/docs/img/features/testing-types/load-testing/test-settings/fig4a.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig5.png b/docs/img/features/testing-types/load-testing/test-settings/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/test-settings/fig6.png b/docs/img/features/testing-types/load-testing/test-settings/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/think-times/fig1.png b/docs/img/features/testing-types/load-testing/think-times/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/think-times/fig2.png b/docs/img/features/testing-types/load-testing/think-times/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/think-times/fig3.png b/docs/img/features/testing-types/load-testing/think-times/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/think-times/fig4.png b/docs/img/features/testing-types/load-testing/think-times/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/think-times/fig5.png b/docs/img/features/testing-types/load-testing/think-times/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/load-testing/troubleshooting-results-errors/fig1.png b/docs/img/features/testing-types/load-testing/troubleshooting-results-errors/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/convert-automated/navigate-to-props.png b/docs/img/features/testing-types/manual-testing/convert-automated/navigate-to-props.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-fail-test.png b/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-fail-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-select-browser.png b/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-select-browser.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-selected.png b/docs/img/features/testing-types/manual-testing/fast-forward/execute-prompt-1-selected.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/fast-forward-button.png b/docs/img/features/testing-types/manual-testing/fast-forward/fast-forward-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/fast-forward-promt.png b/docs/img/features/testing-types/manual-testing/fast-forward/fast-forward-promt.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/fig10.png b/docs/img/features/testing-types/manual-testing/fast-forward/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/fig7.png b/docs/img/features/testing-types/manual-testing/fast-forward/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/manual-step-record.png b/docs/img/features/testing-types/manual-testing/fast-forward/manual-step-record.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/manual-test-in-web.png b/docs/img/features/testing-types/manual-testing/fast-forward/manual-test-in-web.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/tab-icons.png b/docs/img/features/testing-types/manual-testing/fast-forward/tab-icons.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/fast-forward/test-list-result.png b/docs/img/features/testing-types/manual-testing/fast-forward/test-list-result.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/import-export/export-tab-button.png b/docs/img/features/testing-types/manual-testing/import-export/export-tab-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/import-export/import-excel-propmt.png b/docs/img/features/testing-types/manual-testing/import-export/import-excel-propmt.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/import-export/inport-tab-button.png b/docs/img/features/testing-types/manual-testing/import-export/inport-tab-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/overview/fig1.png b/docs/img/features/testing-types/manual-testing/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-1.png b/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-capture-img.png b/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-capture-img.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-comment.png b/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-comment.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-pass-fail.png b/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2-pass-fail.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2.png b/docs/img/features/testing-types/manual-testing/start-test/manual-test-prompt-2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/manual-testing/start-test/start-manual-test-button.png b/docs/img/features/testing-types/manual-testing/start-test/start-manual-test-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/compare-view/fig1.png b/docs/img/features/testing-types/performance-testing/compare-view/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/compare-view/fig2.png b/docs/img/features/testing-types/performance-testing/compare-view/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/compare-view/fig3.png b/docs/img/features/testing-types/performance-testing/compare-view/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/compare-view/fig4.png b/docs/img/features/testing-types/performance-testing/compare-view/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/details-view/fig1.png b/docs/img/features/testing-types/performance-testing/details-view/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/details-view/fig2.png b/docs/img/features/testing-types/performance-testing/details-view/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/details-view/fig3.png b/docs/img/features/testing-types/performance-testing/details-view/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/export-results/fig1.png b/docs/img/features/testing-types/performance-testing/export-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/export-results/fig2.png b/docs/img/features/testing-types/performance-testing/export-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/export-results/fig3.png b/docs/img/features/testing-types/performance-testing/export-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/export-results/fig4.png b/docs/img/features/testing-types/performance-testing/export-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/choose-browser.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/choose-browser.png
new file mode 100644
index 00000000..9524717b
Binary files /dev/null and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/choose-browser.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/continue-to-step-2.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/continue-to-step-2.png
new file mode 100644
index 00000000..23e81c80
Binary files /dev/null and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/continue-to-step-2.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png
old mode 100644
new mode 100755
index 62c1332c..9ae0427a
Binary files a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig1.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig10.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig11.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig12.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig13.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png
old mode 100644
new mode 100755
index 9d05f4ea..d67c6606
Binary files a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig14.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig15.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig16.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png
old mode 100644
new mode 100755
index 5dcc25e4..8daa38d6
Binary files a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig2.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3-saveButton.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3-saveButton.png
new file mode 100644
index 00000000..a702df1d
Binary files /dev/null and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3-saveButton.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png
old mode 100644
new mode 100755
index c2462c77..87fdad38
Binary files a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig3.png differ
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig4.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig5.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig6.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig7.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig8.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/gather-perfomance-data/monitor-multiple-machines.png b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/monitor-multiple-machines.png
new file mode 100644
index 00000000..43373b1d
Binary files /dev/null and b/docs/img/features/testing-types/performance-testing/gather-perfomance-data/monitor-multiple-machines.png differ
diff --git a/docs/img/features/testing-types/performance-testing/history-view/fig1.png b/docs/img/features/testing-types/performance-testing/history-view/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/history-view/fig2.png b/docs/img/features/testing-types/performance-testing/history-view/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/history-view/fig3.png b/docs/img/features/testing-types/performance-testing/history-view/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/history-view/fig4.png b/docs/img/features/testing-types/performance-testing/history-view/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/open-port-on-server/fig1.png b/docs/img/features/testing-types/performance-testing/open-port-on-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/open-port-on-server/fig2.png b/docs/img/features/testing-types/performance-testing/open-port-on-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/open-port-on-server/fig3.png b/docs/img/features/testing-types/performance-testing/open-port-on-server/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/performance-testing/overview-button/fig1.png b/docs/img/features/testing-types/performance-testing/overview-button/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/add-responsive-test-proj-explorer.png b/docs/img/features/testing-types/responsive-web/add-responsive-test-proj-explorer.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/add-responsive-test-ribbon.png b/docs/img/features/testing-types/responsive-web/add-responsive-test-ribbon.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/device-settings-button.png b/docs/img/features/testing-types/responsive-web/device-settings-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/device-settings-default-manual.png b/docs/img/features/testing-types/responsive-web/device-settings-default-manual.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/device-settings-dropdown-list.png b/docs/img/features/testing-types/responsive-web/device-settings-dropdown-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/recorded-steps.png b/docs/img/features/testing-types/responsive-web/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/responsive-recording-session.png b/docs/img/features/testing-types/responsive-web/responsive-recording-session.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/select-exec-browser.png b/docs/img/features/testing-types/responsive-web/select-exec-browser.png
old mode 100644
new mode 100755
diff --git a/docs/img/features/testing-types/responsive-web/trigger-recording-session.png b/docs/img/features/testing-types/responsive-web/trigger-recording-session.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig1.png b/docs/img/general-information/configure-your-browser/chrome/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig10.png b/docs/img/general-information/configure-your-browser/chrome/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig11.png b/docs/img/general-information/configure-your-browser/chrome/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig12.png b/docs/img/general-information/configure-your-browser/chrome/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig13.png b/docs/img/general-information/configure-your-browser/chrome/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig14.png b/docs/img/general-information/configure-your-browser/chrome/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig2.png b/docs/img/general-information/configure-your-browser/chrome/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig20.png b/docs/img/general-information/configure-your-browser/chrome/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig3.png b/docs/img/general-information/configure-your-browser/chrome/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig4.png b/docs/img/general-information/configure-your-browser/chrome/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig5.png b/docs/img/general-information/configure-your-browser/chrome/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig6.png b/docs/img/general-information/configure-your-browser/chrome/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig7.png b/docs/img/general-information/configure-your-browser/chrome/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig8.png b/docs/img/general-information/configure-your-browser/chrome/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/chrome/fig9.png b/docs/img/general-information/configure-your-browser/chrome/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig10.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig11.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig12.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig13.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig14.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig15.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig2.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig3.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig4.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig6.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig7.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig8.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge-chromium/fig9.png b/docs/img/general-information/configure-your-browser/edge-chromium/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig1.png b/docs/img/general-information/configure-your-browser/edge/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig10.png b/docs/img/general-information/configure-your-browser/edge/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig11.png b/docs/img/general-information/configure-your-browser/edge/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig2.png b/docs/img/general-information/configure-your-browser/edge/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig3.png b/docs/img/general-information/configure-your-browser/edge/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig4.png b/docs/img/general-information/configure-your-browser/edge/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig5.png b/docs/img/general-information/configure-your-browser/edge/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig6.png b/docs/img/general-information/configure-your-browser/edge/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig7.png b/docs/img/general-information/configure-your-browser/edge/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig8.png b/docs/img/general-information/configure-your-browser/edge/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/edge/fig9.png b/docs/img/general-information/configure-your-browser/edge/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig1.png b/docs/img/general-information/configure-your-browser/firefox/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig10.png b/docs/img/general-information/configure-your-browser/firefox/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig11.png b/docs/img/general-information/configure-your-browser/firefox/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig12.png b/docs/img/general-information/configure-your-browser/firefox/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig13.png b/docs/img/general-information/configure-your-browser/firefox/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig14.png b/docs/img/general-information/configure-your-browser/firefox/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig15.png b/docs/img/general-information/configure-your-browser/firefox/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig16.png b/docs/img/general-information/configure-your-browser/firefox/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig17.png b/docs/img/general-information/configure-your-browser/firefox/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig18.png b/docs/img/general-information/configure-your-browser/firefox/fig18.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig2.png b/docs/img/general-information/configure-your-browser/firefox/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig20.png b/docs/img/general-information/configure-your-browser/firefox/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig3.png b/docs/img/general-information/configure-your-browser/firefox/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig4.png b/docs/img/general-information/configure-your-browser/firefox/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig5.png b/docs/img/general-information/configure-your-browser/firefox/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig6.png b/docs/img/general-information/configure-your-browser/firefox/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig7.png b/docs/img/general-information/configure-your-browser/firefox/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig8.png b/docs/img/general-information/configure-your-browser/firefox/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/firefox/fig9.png b/docs/img/general-information/configure-your-browser/firefox/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig1.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig10.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig11.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig12.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig13.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig14.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig2.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig3.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig4.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig5.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig6.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig7.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig8.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/internet-explorer/fig9.png b/docs/img/general-information/configure-your-browser/internet-explorer/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig1.png b/docs/img/general-information/configure-your-browser/safari/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig2.png b/docs/img/general-information/configure-your-browser/safari/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig3.png b/docs/img/general-information/configure-your-browser/safari/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig4.png b/docs/img/general-information/configure-your-browser/safari/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig5.png b/docs/img/general-information/configure-your-browser/safari/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/configure-your-browser/safari/fig6.png b/docs/img/general-information/configure-your-browser/safari/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/load-test/fig1.png b/docs/img/general-information/create-test-standalone/load-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/load-test/fig2.png b/docs/img/general-information/create-test-standalone/load-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/load-test/fig3.png b/docs/img/general-information/create-test-standalone/load-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/manual-test/fig1.png b/docs/img/general-information/create-test-standalone/manual-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/manual-test/fig2.png b/docs/img/general-information/create-test-standalone/manual-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/manual-test/maual-test-screen.png b/docs/img/general-information/create-test-standalone/manual-test/maual-test-screen.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/manual-test/step-panel.png b/docs/img/general-information/create-test-standalone/manual-test/step-panel.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/add-load-wpf-manual-test-button.png b/docs/img/general-information/create-test-standalone/overview/add-load-wpf-manual-test-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/add-load-wpf-manual-test-from-project-explorer.png b/docs/img/general-information/create-test-standalone/overview/add-load-wpf-manual-test-from-project-explorer.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/add-new-web-test-button.png b/docs/img/general-information/create-test-standalone/overview/add-new-web-test-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/fig1.png b/docs/img/general-information/create-test-standalone/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/fig2.png b/docs/img/general-information/create-test-standalone/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/overview/project-ribbon-buttons.png b/docs/img/general-information/create-test-standalone/overview/project-ribbon-buttons.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig4.png b/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig5.png b/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig6.png b/docs/img/general-information/create-test-standalone/silverlight-out-of-browser/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/web-test/fig1.png b/docs/img/general-information/create-test-standalone/web-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/web-test/fig2.png b/docs/img/general-information/create-test-standalone/web-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/web-test/fig3.png b/docs/img/general-information/create-test-standalone/web-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/web-test/fig4.png b/docs/img/general-information/create-test-standalone/web-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig1.png b/docs/img/general-information/create-test-standalone/wpf-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig2.png b/docs/img/general-information/create-test-standalone/wpf-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig3.png b/docs/img/general-information/create-test-standalone/wpf-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig4.png b/docs/img/general-information/create-test-standalone/wpf-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig5.png b/docs/img/general-information/create-test-standalone/wpf-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig5a.png b/docs/img/general-information/create-test-standalone/wpf-test/fig5a.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig6.png b/docs/img/general-information/create-test-standalone/wpf-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-standalone/wpf-test/fig7.png b/docs/img/general-information/create-test-standalone/wpf-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig1.png b/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig2.png b/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig3.png b/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig4.png b/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig5.png b/docs/img/general-information/create-test-vsplugin/silverlight-out-of-browser/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/add-new-test.png b/docs/img/general-information/create-test-vsplugin/web-test/add-new-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/enter-url.png b/docs/img/general-information/create-test-vsplugin/web-test/enter-url.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/execute-test.png b/docs/img/general-information/create-test-vsplugin/web-test/execute-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig1.png b/docs/img/general-information/create-test-vsplugin/web-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig2.png b/docs/img/general-information/create-test-vsplugin/web-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig3.png b/docs/img/general-information/create-test-vsplugin/web-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig4.png b/docs/img/general-information/create-test-vsplugin/web-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig5.png b/docs/img/general-information/create-test-vsplugin/web-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig6.png b/docs/img/general-information/create-test-vsplugin/web-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/fig7.png b/docs/img/general-information/create-test-vsplugin/web-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/open-new-test.png b/docs/img/general-information/create-test-vsplugin/web-test/open-new-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/open-test.png b/docs/img/general-information/create-test-vsplugin/web-test/open-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/record-button.png b/docs/img/general-information/create-test-vsplugin/web-test/record-button.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/recorded-steps.png b/docs/img/general-information/create-test-vsplugin/web-test/recorded-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/web-test/web-test-by-default.png b/docs/img/general-information/create-test-vsplugin/web-test/web-test-by-default.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig1.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig11.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig12.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig2.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig3.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig4.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig5.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig6.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/create-test-vsplugin/wpf-test/fig7.png b/docs/img/general-information/create-test-vsplugin/wpf-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/add-services/fig1.png b/docs/img/general-information/installation/add-services/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/add-services/fig2.png b/docs/img/general-information/installation/add-services/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/add-services/fig3.png b/docs/img/general-information/installation/add-services/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/change-storage-service-account/fig1.png b/docs/img/general-information/installation/change-storage-service-account/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/CheckForUpdatesFull.gif b/docs/img/general-information/installation/check-for-updates/CheckForUpdatesFull.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/CheckForUpdatesSoftwareUpdateFull.gif b/docs/img/general-information/installation/check-for-updates/CheckForUpdatesSoftwareUpdateFull.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/CheckForUpdatesVisualStudio.gif b/docs/img/general-information/installation/check-for-updates/CheckForUpdatesVisualStudio.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig1.png b/docs/img/general-information/installation/check-for-updates/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig2.png b/docs/img/general-information/installation/check-for-updates/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig3.png b/docs/img/general-information/installation/check-for-updates/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig4.png b/docs/img/general-information/installation/check-for-updates/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig5.png b/docs/img/general-information/installation/check-for-updates/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig6.png b/docs/img/general-information/installation/check-for-updates/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig7.png b/docs/img/general-information/installation/check-for-updates/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/check-for-updates/fig8.png b/docs/img/general-information/installation/check-for-updates/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/configure-windows-server/fig2.png b/docs/img/general-information/installation/configure-windows-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/configure-windows-server/fig3.png b/docs/img/general-information/installation/configure-windows-server/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/configure-windows-server/fig4.png b/docs/img/general-information/installation/configure-windows-server/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/configure-windows-server/fig5.png b/docs/img/general-information/installation/configure-windows-server/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/configure-windows-server/fig6.png b/docs/img/general-information/installation/configure-windows-server/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig1.png b/docs/img/general-information/installation/install-procedure/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig2.png b/docs/img/general-information/installation/install-procedure/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig3-listOfComponents.png b/docs/img/general-information/installation/install-procedure/fig3-listOfComponents.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig3.png b/docs/img/general-information/installation/install-procedure/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig4.png b/docs/img/general-information/installation/install-procedure/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig5.png b/docs/img/general-information/installation/install-procedure/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig6.png b/docs/img/general-information/installation/install-procedure/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig7.png b/docs/img/general-information/installation/install-procedure/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig8.png b/docs/img/general-information/installation/install-procedure/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/install-procedure/fig9.png b/docs/img/general-information/installation/install-procedure/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig1.png b/docs/img/general-information/installation/manual-download/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig2.png b/docs/img/general-information/installation/manual-download/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig3.png b/docs/img/general-information/installation/manual-download/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig4.png b/docs/img/general-information/installation/manual-download/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig5.png b/docs/img/general-information/installation/manual-download/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/manual-download/fig6.png b/docs/img/general-information/installation/manual-download/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/re-activating-your-license/fig1.png b/docs/img/general-information/installation/re-activating-your-license/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/vs2017/vs2017installation.png b/docs/img/general-information/installation/vs2017/vs2017installation.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/installation/vs2022/fig1.png b/docs/img/general-information/installation/vs2022/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig1.png b/docs/img/general-information/test-execution/quick-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig11.png b/docs/img/general-information/test-execution/quick-execution/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig14.png b/docs/img/general-information/test-execution/quick-execution/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig2.png b/docs/img/general-information/test-execution/quick-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig3.png b/docs/img/general-information/test-execution/quick-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig4.png b/docs/img/general-information/test-execution/quick-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig5.png b/docs/img/general-information/test-execution/quick-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig6.png b/docs/img/general-information/test-execution/quick-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig8.png b/docs/img/general-information/test-execution/quick-execution/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/quick-execution/fig9.png b/docs/img/general-information/test-execution/quick-execution/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-list-execution/fig1.png b/docs/img/general-information/test-execution/test-list-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-list-execution/fig2.png b/docs/img/general-information/test-execution/test-list-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-list-execution/fig3.png b/docs/img/general-information/test-execution/test-list-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-list-execution/fig4.png b/docs/img/general-information/test-execution/test-list-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig1.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig10.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig11.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig2.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig3.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig4.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig5.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig6.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig7.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig8.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig9.png b/docs/img/general-information/test-execution/test-lists-in-vs-2017-2019/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig1.png b/docs/img/general-information/test-execution/test-lists-standalone/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig2.png b/docs/img/general-information/test-execution/test-lists-standalone/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig2_FilterTestsByType.png b/docs/img/general-information/test-execution/test-lists-standalone/fig2_FilterTestsByType.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig2_collapse.png b/docs/img/general-information/test-execution/test-lists-standalone/fig2_collapse.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig2_searchField.png b/docs/img/general-information/test-execution/test-lists-standalone/fig2_searchField.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig3.png b/docs/img/general-information/test-execution/test-lists-standalone/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig4.png b/docs/img/general-information/test-execution/test-lists-standalone/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig5.png b/docs/img/general-information/test-execution/test-lists-standalone/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig6.png b/docs/img/general-information/test-execution/test-lists-standalone/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig7.png b/docs/img/general-information/test-execution/test-lists-standalone/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/test-lists-standalone/fig8.png b/docs/img/general-information/test-execution/test-lists-standalone/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-debugger/fig1.png b/docs/img/general-information/test-execution/visual-debugger/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-debugger/fig2.png b/docs/img/general-information/test-execution/visual-debugger/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig1.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig2.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig3.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig4.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig5.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig6.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig7.png b/docs/img/general-information/test-execution/visual-studio-2012-and-later-test-list/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/vs-test-explorer/fig1.png b/docs/img/general-information/test-execution/vs-test-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/vs-test-explorer/fig2.png b/docs/img/general-information/test-execution/vs-test-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/vs-test-explorer/fig3.png b/docs/img/general-information/test-execution/vs-test-explorer/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-execution/vs-test-explorer/fig4.png b/docs/img/general-information/test-execution/vs-test-explorer/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig1.png b/docs/img/general-information/test-recording/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig2.png b/docs/img/general-information/test-recording/overview/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig3.png b/docs/img/general-information/test-recording/overview/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig4.png b/docs/img/general-information/test-recording/overview/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig5.png b/docs/img/general-information/test-recording/overview/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-recording/overview/fig6.png b/docs/img/general-information/test-recording/overview/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig1.png b/docs/img/general-information/test-results/analyze-test-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig10.png b/docs/img/general-information/test-results/analyze-test-results/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig11.png b/docs/img/general-information/test-results/analyze-test-results/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig12.gif b/docs/img/general-information/test-results/analyze-test-results/fig12.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig12.png b/docs/img/general-information/test-results/analyze-test-results/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig13.png b/docs/img/general-information/test-results/analyze-test-results/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig2.png b/docs/img/general-information/test-results/analyze-test-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig3.png b/docs/img/general-information/test-results/analyze-test-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig4.png b/docs/img/general-information/test-results/analyze-test-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig5.png b/docs/img/general-information/test-results/analyze-test-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig6.png b/docs/img/general-information/test-results/analyze-test-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig7.png b/docs/img/general-information/test-results/analyze-test-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/analyze-test-results/fig8.png b/docs/img/general-information/test-results/analyze-test-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/calendar/fig1.png b/docs/img/general-information/test-results/calendar/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/calendar/fig2.png b/docs/img/general-information/test-results/calendar/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/calendar/fig3.png b/docs/img/general-information/test-results/calendar/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/calendar/fig4.png b/docs/img/general-information/test-results/calendar/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/about-page/fig1.png b/docs/img/general-information/test-results/dashboard/about-page/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig1.png b/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig2.png b/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig3.png b/docs/img/general-information/test-results/dashboard/installation-and-configuration/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/overview/fig1.png b/docs/img/general-information/test-results/dashboard/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/fig1.png b/docs/img/general-information/test-results/dashboard/reports/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/fig2.png b/docs/img/general-information/test-results/dashboard/reports/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/fig3.png b/docs/img/general-information/test-results/dashboard/reports/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/fig4.png b/docs/img/general-information/test-results/dashboard/reports/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/gif1.gif b/docs/img/general-information/test-results/dashboard/reports/gif1.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/gif2.gif b/docs/img/general-information/test-results/dashboard/reports/gif2.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/reports/gif22.gif b/docs/img/general-information/test-results/dashboard/reports/gif22.gif
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/results/fig1.png b/docs/img/general-information/test-results/dashboard/results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/results/fig2.png b/docs/img/general-information/test-results/dashboard/results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/results/fig3.png b/docs/img/general-information/test-results/dashboard/results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/dashboard/results/fig4.png b/docs/img/general-information/test-results/dashboard/results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig1.png b/docs/img/general-information/test-results/export-test-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig2.png b/docs/img/general-information/test-results/export-test-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig3.png b/docs/img/general-information/test-results/export-test-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig4.png b/docs/img/general-information/test-results/export-test-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig5.png b/docs/img/general-information/test-results/export-test-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig6.png b/docs/img/general-information/test-results/export-test-results/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig7.png b/docs/img/general-information/test-results/export-test-results/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig8.png b/docs/img/general-information/test-results/export-test-results/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/export-test-results/fig9.png b/docs/img/general-information/test-results/export-test-results/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/quick-execute-test-step/fig1.png b/docs/img/general-information/test-results/quick-execute-test-step/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/quick-execute-test-step/fig2.png b/docs/img/general-information/test-results/quick-execute-test-step/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig1-new.png b/docs/img/general-information/test-results/reports/fig1-new.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig1.png b/docs/img/general-information/test-results/reports/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig2-new.png b/docs/img/general-information/test-results/reports/fig2-new.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig2.png b/docs/img/general-information/test-results/reports/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig3.png b/docs/img/general-information/test-results/reports/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig4.png b/docs/img/general-information/test-results/reports/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig5.png b/docs/img/general-information/test-results/reports/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig6.png b/docs/img/general-information/test-results/reports/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/reports/fig7.png b/docs/img/general-information/test-results/reports/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig1.png b/docs/img/general-information/test-results/step-failure-details/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig2.png b/docs/img/general-information/test-results/step-failure-details/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig3.png b/docs/img/general-information/test-results/step-failure-details/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig4.png b/docs/img/general-information/test-results/step-failure-details/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig5.png b/docs/img/general-information/test-results/step-failure-details/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig6.png b/docs/img/general-information/test-results/step-failure-details/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig7.png b/docs/img/general-information/test-results/step-failure-details/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/step-failure-details/fig8.png b/docs/img/general-information/test-results/step-failure-details/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/test-results-vs/fig3.png b/docs/img/general-information/test-results/test-results-vs/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/test-results-vs/fig4.png b/docs/img/general-information/test-results/test-results-vs/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/test-results-vs/fig5.png b/docs/img/general-information/test-results/test-results-vs/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/general-information/test-results/test-results-vs/fig6.png b/docs/img/general-information/test-results/test-results-vs/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/analyze-the-results/fig01.png b/docs/img/getting-started/analyze-the-results/fig01.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/analyze-the-results/fig02.png b/docs/img/getting-started/analyze-the-results/fig02.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/analyze-the-results/fig03.png b/docs/img/getting-started/analyze-the-results/fig03.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/analyze-the-results/fig04.png b/docs/img/getting-started/analyze-the-results/fig04.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/add-new-test1.png b/docs/img/getting-started/first-project/add-new-test1.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/add-new-test2.png b/docs/img/getting-started/first-project/add-new-test2.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/add-test-list.png b/docs/img/getting-started/first-project/add-test-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/add-web-test.gif b/docs/img/getting-started/first-project/add-web-test.gif
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/add-web-test.png b/docs/img/getting-started/first-project/add-web-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/compact-recording-toolbar.png b/docs/img/getting-started/first-project/compact-recording-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/create-test-list.png b/docs/img/getting-started/first-project/create-test-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/elements-and-page-nodes.png b/docs/img/getting-started/first-project/elements-and-page-nodes.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig0.png b/docs/img/getting-started/first-project/fig0.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig00.png b/docs/img/getting-started/first-project/fig00.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig01.png b/docs/img/getting-started/first-project/fig01.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig02.png b/docs/img/getting-started/first-project/fig02.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig02a.png b/docs/img/getting-started/first-project/fig02a.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig03.png b/docs/img/getting-started/first-project/fig03.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig04.png b/docs/img/getting-started/first-project/fig04.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig05.png b/docs/img/getting-started/first-project/fig05.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig05a.png b/docs/img/getting-started/first-project/fig05a.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig05b.png b/docs/img/getting-started/first-project/fig05b.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig06.png b/docs/img/getting-started/first-project/fig06.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig06a.png b/docs/img/getting-started/first-project/fig06a.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig06b.png b/docs/img/getting-started/first-project/fig06b.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig07.png b/docs/img/getting-started/first-project/fig07.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig08.png b/docs/img/getting-started/first-project/fig08.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig09.png b/docs/img/getting-started/first-project/fig09.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig0a.png b/docs/img/getting-started/first-project/fig0a.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig0b.png b/docs/img/getting-started/first-project/fig0b.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig10.png b/docs/img/getting-started/first-project/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig11.png b/docs/img/getting-started/first-project/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig12.png b/docs/img/getting-started/first-project/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig13.png b/docs/img/getting-started/first-project/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig14.png b/docs/img/getting-started/first-project/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/fig15.png b/docs/img/getting-started/first-project/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/file-types-in-file-explorer.png b/docs/img/getting-started/first-project/file-types-in-file-explorer.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/file-types.png b/docs/img/getting-started/first-project/file-types.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/project-components.png b/docs/img/getting-started/first-project/project-components.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/recording-toolbar.png b/docs/img/getting-started/first-project/recording-toolbar.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/run-test-list.png b/docs/img/getting-started/first-project/run-test-list.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/first-project/test-list-results.png b/docs/img/getting-started/first-project/test-list-results.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig00.png b/docs/img/getting-started/installation-and-activation/fig00.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig01.png b/docs/img/getting-started/installation-and-activation/fig01.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig02.png b/docs/img/getting-started/installation-and-activation/fig02.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig03.png b/docs/img/getting-started/installation-and-activation/fig03.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig04.png b/docs/img/getting-started/installation-and-activation/fig04.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig05.png b/docs/img/getting-started/installation-and-activation/fig05.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig06.png b/docs/img/getting-started/installation-and-activation/fig06.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig07.png b/docs/img/getting-started/installation-and-activation/fig07.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig08.png b/docs/img/getting-started/installation-and-activation/fig08.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig09.png b/docs/img/getting-started/installation-and-activation/fig09.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig10.png b/docs/img/getting-started/installation-and-activation/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig11.gif b/docs/img/getting-started/installation-and-activation/fig11.gif
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig12.png b/docs/img/getting-started/installation-and-activation/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig13.png b/docs/img/getting-started/installation-and-activation/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig14.png b/docs/img/getting-started/installation-and-activation/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig15.png b/docs/img/getting-started/installation-and-activation/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig16.png b/docs/img/getting-started/installation-and-activation/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/getting-started/installation-and-activation/fig17.png b/docs/img/getting-started/installation-and-activation/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/introduction/test-studio-framework/fig1.png b/docs/img/introduction/test-studio-framework/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/change-license-deactivate.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/change-license-deactivate.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/change-purchased-license.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/change-purchased-license.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig1.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig2.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig3.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/manage-license-info.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/manage-license-info.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/change-trial-purchase/welcome-screen-deactivate-license.png b/docs/img/knowledge-base/activation-kb/change-trial-purchase/welcome-screen-deactivate-license.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/swap-license/fig1.png b/docs/img/knowledge-base/activation-kb/swap-license/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/swap-license/fig2.png b/docs/img/knowledge-base/activation-kb/swap-license/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/swap-license/fig3.png b/docs/img/knowledge-base/activation-kb/swap-license/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/activation-kb/swap-license/fig4.png b/docs/img/knowledge-base/activation-kb/swap-license/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/add-existing-test/fig1.png b/docs/img/knowledge-base/best-practices-kb/add-existing-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig2.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig2a.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig2a.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig3.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig4.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig5.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig6.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig7.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig7a.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig7a.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig8.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig8a.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig8a.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig9.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/generate-application-log/vs-logging.png b/docs/img/knowledge-base/best-practices-kb/generate-application-log/vs-logging.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/regular-vs-coded-step/fig1.png b/docs/img/knowledge-base/best-practices-kb/regular-vs-coded-step/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/best-practices-kb/submit-support-ticket/fig1.png b/docs/img/knowledge-base/best-practices-kb/submit-support-ticket/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/calibration-error-preferences-file/fig1.png b/docs/img/knowledge-base/browsers-kb/calibration-error-preferences-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/custom-chrome-path/fig1.png b/docs/img/knowledge-base/browsers-kb/custom-chrome-path/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/custom-chrome-path/fig2.png b/docs/img/knowledge-base/browsers-kb/custom-chrome-path/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/custom-chrome-profile/fig1.png b/docs/img/knowledge-base/browsers-kb/custom-chrome-profile/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/custom-edge-profile/fig1.png b/docs/img/knowledge-base/browsers-kb/custom-edge-profile/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/browsers-kb/extension-not-available-in-store/fig1.png b/docs/img/knowledge-base/browsers-kb/extension-not-available-in-store/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig1.png b/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig2.png b/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig3.jpg b/docs/img/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest/fig3.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig1.png b/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig2.png b/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig3.png b/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig4.png b/docs/img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig1.png b/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig2.png b/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig3.png b/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig4.png b/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig5.png b/docs/img/knowledge-base/data-driven-testing-kb/sql-random-row/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/closesbrowser-property/fig1.png b/docs/img/knowledge-base/dialogs-and-popups-kb/closesbrowser-property/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action/fig1.png b/docs/img/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action/fig2.png b/docs/img/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig1.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig2.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig3.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig4.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig5.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig6.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig7.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig8.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig9.png b/docs/img/knowledge-base/dialogs-and-popups-kb/variable-query-strings/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/analyze-results/fig1.png b/docs/img/knowledge-base/load-testing-kb/analyze-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/analyze-results/fig2.png b/docs/img/knowledge-base/load-testing-kb/analyze-results/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/analyze-results/fig3.png b/docs/img/knowledge-base/load-testing-kb/analyze-results/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/analyze-results/fig4.png b/docs/img/knowledge-base/load-testing-kb/analyze-results/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/analyze-results/fig5.png b/docs/img/knowledge-base/load-testing-kb/analyze-results/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/load-strategies/fig1.png b/docs/img/knowledge-base/load-testing-kb/load-strategies/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/load-strategies/fig2.png b/docs/img/knowledge-base/load-testing-kb/load-strategies/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/load-strategies/fig3.png b/docs/img/knowledge-base/load-testing-kb/load-strategies/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/load-strategies/fig4.png b/docs/img/knowledge-base/load-testing-kb/load-strategies/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/virtual-users/fig1.png b/docs/img/knowledge-base/load-testing-kb/virtual-users/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/load-testing-kb/virtual-users/fig2.png b/docs/img/knowledge-base/load-testing-kb/virtual-users/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/disconnect-from-fource-control/fig1.png b/docs/img/knowledge-base/project-configuration-kb/disconnect-from-fource-control/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/encryption-key/copy-encryption-key.png b/docs/img/knowledge-base/project-configuration-kb/encryption-key/copy-encryption-key.png
new file mode 100644
index 00000000..d3d887af
Binary files /dev/null and b/docs/img/knowledge-base/project-configuration-kb/encryption-key/copy-encryption-key.png differ
diff --git a/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-generate-key.png b/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-generate-key.png
new file mode 100644
index 00000000..4ad8edb7
Binary files /dev/null and b/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-generate-key.png differ
diff --git a/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-import-key.png b/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-import-key.png
new file mode 100644
index 00000000..f1871563
Binary files /dev/null and b/docs/img/knowledge-base/project-configuration-kb/encryption-key/encryption-import-key.png differ
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig1.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig10.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig11.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig2.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig3.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig4.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig5.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig6.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig7.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig8.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig9.png b/docs/img/knowledge-base/project-configuration-kb/merge-page-nodes/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig1.png b/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig2.png b/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig3.png b/docs/img/knowledge-base/project-configuration-kb/register-certificate/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig1.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig10.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig103.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig103.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig104.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig104.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig105.gif b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig105.gif
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig106.gif b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig106.gif
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig107.gif b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig107.gif
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig108.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig108.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig11.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig2.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig3.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig4.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig5.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig6.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig7.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig8.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig9.png b/docs/img/knowledge-base/project-configuration-kb/using-chained-find-expressions/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/communication-key/copy-current-key.png b/docs/img/knowledge-base/scheduling-kb/communication-key/copy-current-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/communication-key/generate-key.png b/docs/img/knowledge-base/scheduling-kb/communication-key/generate-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/communication-key/replace-key.png b/docs/img/knowledge-base/scheduling-kb/communication-key/replace-key.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png b/docs/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig1.png b/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig2.png b/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig3.png b/docs/img/knowledge-base/scheduling-kb/drop-storage-database/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/extract-results-from-mongodb/fig1.png b/docs/img/knowledge-base/scheduling-kb/extract-results-from-mongodb/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/gmail-results/fig1.png b/docs/img/knowledge-base/scheduling-kb/gmail-results/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/increase-storage-service-timeout/fig1.png b/docs/img/knowledge-base/scheduling-kb/increase-storage-service-timeout/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/keep-active-session/fig1.png b/docs/img/knowledge-base/scheduling-kb/keep-active-session/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/keep-active-session/fig2.png b/docs/img/knowledge-base/scheduling-kb/keep-active-session/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/ConfigFile_fig2.png b/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/ConfigFile_fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/Services_fig1.jpg b/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/Services_fig1.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/fig3.png b/docs/img/knowledge-base/scheduling-kb/maintain-scheduling-services/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig1.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig2.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig3.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig4.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig5.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig6.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig7.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig8.png b/docs/img/knowledge-base/scheduling-kb/non-domain-environment/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig1.png b/docs/img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig2.png b/docs/img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig1.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig10.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig11.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig12.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig13.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig14.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig2.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig3.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig4.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig5.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig6.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig7.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig8.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig9.png b/docs/img/knowledge-base/silverlight-kb/automate-in-tfs-builds/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig1.png b/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig2.png b/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig3.png b/docs/img/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust/fig1.png b/docs/img/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust/fig2.png b/docs/img/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/silverlight-kb/testing-framework-with-silverlight-oob-and-elevated-trust/fig1.png b/docs/img/knowledge-base/silverlight-kb/testing-framework-with-silverlight-oob-and-elevated-trust/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/telerik-login-kb/fig1.png b/docs/img/knowledge-base/telerik-login-kb/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/ample-timetouts/fig1.png b/docs/img/knowledge-base/test-automation-kb/ample-timetouts/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/ample-timetouts/fig2.png b/docs/img/knowledge-base/test-automation-kb/ample-timetouts/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig1.png b/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig2.png b/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig3.png b/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig4.png b/docs/img/knowledge-base/test-automation-kb/dynamic-ids/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/invoke-mouse-hover/fig1.png b/docs/img/knowledge-base/test-automation-kb/invoke-mouse-hover/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/security-certificates/fig1.png b/docs/img/knowledge-base/test-automation-kb/security-certificates/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/security-certificates/fig2.png b/docs/img/knowledge-base/test-automation-kb/security-certificates/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/security-certificates/fig3.png b/docs/img/knowledge-base/test-automation-kb/security-certificates/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-automation-kb/security-certificates/fig4.png b/docs/img/knowledge-base/test-automation-kb/security-certificates/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig1.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig2.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig3.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig4.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig5.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig6.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/base-url/fig7.png b/docs/img/knowledge-base/test-execution-kb/base-url/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/excel-event/fig1.png b/docs/img/knowledge-base/test-execution-kb/excel-event/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/excel-event/fig2.png b/docs/img/knowledge-base/test-execution-kb/excel-event/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/execute-selenium-test/fig1.png b/docs/img/knowledge-base/test-execution-kb/execute-selenium-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/execute-selenium-test/fig2.png b/docs/img/knowledge-base/test-execution-kb/execute-selenium-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/multi-browsers/fig1.png b/docs/img/knowledge-base/test-execution-kb/multi-browsers/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/multi-browsers/fig2.png b/docs/img/knowledge-base/test-execution-kb/multi-browsers/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-execution-kb/slow-execution-rdc/fig1.png b/docs/img/knowledge-base/test-execution-kb/slow-execution-rdc/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig1.png b/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig2.png b/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig3.png b/docs/img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/disabled-attribute-html/fig1.png b/docs/img/knowledge-base/verification-kb/disabled-attribute-html/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/disabled-attribute-html/fig2.png b/docs/img/knowledge-base/verification-kb/disabled-attribute-html/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig1.png b/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig2.png b/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig3.png b/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig4.png b/docs/img/knowledge-base/verification-kb/verify-deleted-data/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-html-tool-tips/fig1.png b/docs/img/knowledge-base/verification-kb/verify-html-tool-tips/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-html-tool-tips/fig2.png b/docs/img/knowledge-base/verification-kb/verify-html-tool-tips/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig1.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig2.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig3.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig4.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig5.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-combobox-items/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-tool-tips/fig1.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-tool-tips/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/verification-kb/verify-silverlight-tool-tips/fig2.png b/docs/img/knowledge-base/verification-kb/verify-silverlight-tool-tips/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/convert-trx-to-html/fig1.png b/docs/img/knowledge-base/visual-studio-kb/convert-trx-to-html/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/resharper-compatibility/fig1.png b/docs/img/knowledge-base/visual-studio-kb/resharper-compatibility/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/add-existing-item.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/add-existing-item.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig1.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig2.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig3.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig4.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/run-settings-vs22.png b/docs/img/knowledge-base/visual-studio-kb/test-explorer-settings/run-settings-vs22.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig1.png b/docs/img/license-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig10.png b/docs/img/license-server/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig11.png b/docs/img/license-server/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig12.png b/docs/img/license-server/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig13.png b/docs/img/license-server/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig14.png b/docs/img/license-server/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig15.png b/docs/img/license-server/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig15a.png b/docs/img/license-server/fig15a.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig16.png b/docs/img/license-server/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig2.png b/docs/img/license-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig3.png b/docs/img/license-server/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig4.png b/docs/img/license-server/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig5.png b/docs/img/license-server/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig6.png b/docs/img/license-server/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig7.png b/docs/img/license-server/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig8.png b/docs/img/license-server/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig9.png b/docs/img/license-server/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/license-server/fig9a.png b/docs/img/license-server/fig9a.png
old mode 100644
new mode 100755
diff --git a/docs/img/overview/fig1.jpg b/docs/img/overview/fig1.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/overview/fig1.png b/docs/img/overview/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/browser-config/accept-permissions.jpg b/docs/img/prerequisites/browser-config/accept-permissions.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/browser-config/accept-popup.jpg b/docs/img/prerequisites/browser-config/accept-popup.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/browser-config/disable-extension.png b/docs/img/prerequisites/browser-config/disable-extension.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/browser-config/edge-notification.jpg b/docs/img/prerequisites/browser-config/edge-notification.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/installation/check-for-update-now.png b/docs/img/prerequisites/installation/check-for-update-now.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/installation/check-for-updates-settings.png b/docs/img/prerequisites/installation/check-for-updates-settings.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig1.png b/docs/img/prerequisites/license-activation/activating/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig2.png b/docs/img/prerequisites/license-activation/activating/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig3.png b/docs/img/prerequisites/license-activation/activating/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig4.png b/docs/img/prerequisites/license-activation/activating/fig4.png
old mode 100644
new mode 100755
index 4270e5fa..014f26f5
Binary files a/docs/img/prerequisites/license-activation/activating/fig4.png and b/docs/img/prerequisites/license-activation/activating/fig4.png differ
diff --git a/docs/img/prerequisites/license-activation/activating/fig5.png b/docs/img/prerequisites/license-activation/activating/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig6.png b/docs/img/prerequisites/license-activation/activating/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/activating/fig7.png b/docs/img/prerequisites/license-activation/activating/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig1.png b/docs/img/prerequisites/license-activation/manual-activation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig2.png b/docs/img/prerequisites/license-activation/manual-activation/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig3.png b/docs/img/prerequisites/license-activation/manual-activation/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig4.png b/docs/img/prerequisites/license-activation/manual-activation/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig5.png b/docs/img/prerequisites/license-activation/manual-activation/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/manual-activation/fig6.png b/docs/img/prerequisites/license-activation/manual-activation/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/prerequisites/license-activation/welcome-screen-deactivate-license.png b/docs/img/prerequisites/license-activation/welcome-screen-deactivate-license.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig1.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig10.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig11.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig12.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig13.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig14.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig15.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig16.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig17.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig17.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig18.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig18.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig19.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig19.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig2.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig20.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig20.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig3.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig4.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig5.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig6.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig7.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig8.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-android/fig9.png b/docs/img/test-studio-mobile/configure-your-app/configure-android/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/AddMobileTestingProjectAndTest.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/AddMobileTestingProjectAndTest.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/AirlinesCreated.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/AirlinesCreated.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildAndroid.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildAndroid.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildIos.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildIos.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ConnectedDevices.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ConnectedDevices.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ConnectedDevicesResults.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ConnectedDevicesResults.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateAirlines.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateAirlines.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateApp.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateApp.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateAppName.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateAppName.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateProject.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateProject.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateRun.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateRun.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadAndroid.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadAndroid.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadIos.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadIos.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ExecuteRun.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/ExecuteRun.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/GoToPortal.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/GoToPortal.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/PendingResults.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/PendingResults.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/RunResults.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/RunResults.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/RunSuccessfull.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/RunSuccessfull.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetAndroidIdentifier.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetAndroidIdentifier.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetIosIdentifier.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetIosIdentifier.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/TestPortal.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/TestPortal.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/TestResults.png b/docs/img/test-studio-mobile/configure-your-app/configure-appbuilder/TestResults.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-hybrid/mobile-testing-extension.png b/docs/img/test-studio-mobile/configure-your-app/configure-hybrid/mobile-testing-extension.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-hybrid/pluginxml-ios.png b/docs/img/test-studio-mobile/configure-your-app/configure-hybrid/pluginxml-ios.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-Android.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-Android.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-iOS.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-iOS.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-Android.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-Android.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-iOS.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-iOS.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-Android.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-Android.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-iOS.png b/docs/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-iOS.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/AndroidManifest.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/AndroidManifest.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/activity.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/activity.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/add-jars.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/add-jars.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/codegen-target.PNG b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/codegen-target.PNG
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/configure-jar.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/configure-jar.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/instrumentation.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/instrumentation.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-bindings-library.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-bindings-library.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-install.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-install.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/properties.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/properties.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/references.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-android/references.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig1.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig2.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig3.png b/docs/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig1.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig2.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig3.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig4.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig5.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig6.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig7.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig8.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig9.png b/docs/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig1.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig2.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig3.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig4.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig6.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/connect-agent-app/usb/fig7.png b/docs/img/test-studio-mobile/connect-agent-app/usb/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig4.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig5.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig6.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig7.png b/docs/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/code.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/code.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/log.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/log.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig4.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig5.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig4.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig5.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig6.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig7.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/adding-plugin-options.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/adding-plugin-options.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/adding-the-url-type-3.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/adding-the-url-type-3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/appID.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/appID.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/bundle-identifier.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/bundle-identifier.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog1.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog2.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/drag-static-lib-new.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/drag-static-lib-new.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/linked-lib-new.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/linked-lib-new.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/other-linker-flags-2.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/other-linker-flags-2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-copy.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-copy.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-qa.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-qa.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile.png b/docs/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/dom-explorer/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/dom-explorer/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/dom-explorer/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/dom-explorer/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-drag.png b/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-drag.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-explorer.png b/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-explorer.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-query-builder.png b/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-query-builder.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-toggle-highlight.png b/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-toggle-highlight.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-view-menu.png b/docs/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-view-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/demo-app-qa-ios.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/demo-app-qa-ios.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-disconnected.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-disconnected.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-wifi-connected.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-wifi-connected.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-wifi-settings.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/ios-wifi-settings.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-add-test.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-add-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-app-id.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-app-id.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-connect-device.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-connect-device.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-create-project.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-create-project.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-host-port.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-host-port.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-playback.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-playback.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-record-test.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-record-test.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-step-recording.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-step-recording.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-stop-recorder.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/mobile-studio-stop-recorder.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/getting-started/open-ios-demo.png b/docs/img/test-studio-mobile/getting-started-mb/getting-started/open-ios-demo.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_linux.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_linux.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_mac.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_mac.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_windows.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/menu_windows.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_linux_custom.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_linux_custom.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_linux_default.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_linux_default.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_mac_custom.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_mac_custom.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_mac_default.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_mac_default.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_windows_custom.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_windows_custom.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/message-server/start_windows_default.png b/docs/img/test-studio-mobile/getting-started-mb/message-server/start_windows_default.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig4.png b/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig5.png b/docs/img/test-studio-mobile/getting-started-mb/output-pane/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/fig6.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-context-menu.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-context-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-drag-drop.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-drag-drop.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-project-drag.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-project-drag.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-search-field.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-search-field.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-view-menu.png b/docs/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-view-menu.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/settings/fig1.png b/docs/img/test-studio-mobile/getting-started-mb/settings/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/settings/fig2.png b/docs/img/test-studio-mobile/getting-started-mb/settings/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/settings/fig3.png b/docs/img/test-studio-mobile/getting-started-mb/settings/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-active-step.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-active-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-continue-failure.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-continue-failure.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-enabled-steps.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-enabled-steps.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-error.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-error.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-expand-step.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-expand-step.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-displayname.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-displayname.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-dragdrop.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-dragdrop.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-filtering.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-filtering.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-type.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-type.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-test-contextmenu.png b/docs/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-test-contextmenu.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/install/run-demos/fig1.png b/docs/img/test-studio-mobile/install/run-demos/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/install/run-demos/fig2.png b/docs/img/test-studio-mobile/install/run-demos/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/install/run-demos/fig3.png b/docs/img/test-studio-mobile/install/run-demos/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/install/run-demos/fig4.png b/docs/img/test-studio-mobile/install/run-demos/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/install/run-demos/fig5.png b/docs/img/test-studio-mobile/install/run-demos/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig1.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/framework-installation/fig1.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/framework-installation/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/framework-installation/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/framework-installation/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig1.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig3.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig4.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig5.png b/docs/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig1.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig10.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig11.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig3.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig4.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig5.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig6.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig7.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig8.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig9.png b/docs/img/test-studio-mobile/knowledge-base-tm/device-cloud/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig1.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig2.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig3.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig4.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig5.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig6.png b/docs/img/test-studio-mobile/knowledge-base-tm/known-issues/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig1.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig2.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig3.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig4.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig5.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/quick-execution/fig6.png b/docs/img/test-studio-mobile/test-execution/quick-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig1.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig10.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig2.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig3.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig4.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig5.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig6.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig7.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig8.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-execution/test-list-execution/fig9.png b/docs/img/test-studio-mobile/test-execution/test-list-execution/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/create-test/fig1.png b/docs/img/test-studio-mobile/test-recording/create-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/create-test/fig2.png b/docs/img/test-studio-mobile/test-recording/create-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/create-test/fig3.png b/docs/img/test-studio-mobile/test-recording/create-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/create-test/fig4.png b/docs/img/test-studio-mobile/test-recording/create-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig1.png b/docs/img/test-studio-mobile/test-recording/record-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig10.png b/docs/img/test-studio-mobile/test-recording/record-test/fig10.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig11.png b/docs/img/test-studio-mobile/test-recording/record-test/fig11.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig12.png b/docs/img/test-studio-mobile/test-recording/record-test/fig12.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig13.png b/docs/img/test-studio-mobile/test-recording/record-test/fig13.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig14.png b/docs/img/test-studio-mobile/test-recording/record-test/fig14.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig15.png b/docs/img/test-studio-mobile/test-recording/record-test/fig15.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig16.png b/docs/img/test-studio-mobile/test-recording/record-test/fig16.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig2.png b/docs/img/test-studio-mobile/test-recording/record-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig3.png b/docs/img/test-studio-mobile/test-recording/record-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig4.png b/docs/img/test-studio-mobile/test-recording/record-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig5.png b/docs/img/test-studio-mobile/test-recording/record-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig6.png b/docs/img/test-studio-mobile/test-recording/record-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig7.png b/docs/img/test-studio-mobile/test-recording/record-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig8.png b/docs/img/test-studio-mobile/test-recording/record-test/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/fig9.png b/docs/img/test-studio-mobile/test-recording/record-test/fig9.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig1.png b/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig2.png b/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig3.png b/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig4.png b/docs/img/test-studio-mobile/test-recording/record-test/record-web-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig1.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig2.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig3.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig4.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig5.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/test-recording/step-builder/fig6.png b/docs/img/test-studio-mobile/test-recording/step-builder/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig1.png b/docs/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig2.png b/docs/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig1.png b/docs/img/test-studio-mobile/web-applications/certificate/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig2.png b/docs/img/test-studio-mobile/web-applications/certificate/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig3.png b/docs/img/test-studio-mobile/web-applications/certificate/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig6.PNG b/docs/img/test-studio-mobile/web-applications/certificate/fig6.PNG
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig7.PNG b/docs/img/test-studio-mobile/web-applications/certificate/fig7.PNG
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/certificate/fig8.PNG b/docs/img/test-studio-mobile/web-applications/certificate/fig8.PNG
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig1.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig2.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig3.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig6.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig7.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig8.png b/docs/img/test-studio-mobile/web-applications/connect-web-agent/fig8.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/proxy/fig1.png b/docs/img/test-studio-mobile/web-applications/proxy/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/proxy/fig2.png b/docs/img/test-studio-mobile/web-applications/proxy/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/proxy/fig3.png b/docs/img/test-studio-mobile/web-applications/proxy/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/proxy/fig4.png b/docs/img/test-studio-mobile/web-applications/proxy/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/run-web-demos/fig1.png b/docs/img/test-studio-mobile/web-applications/run-web-demos/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/test-studio-mobile/web-applications/run-web-demos/fig2.png b/docs/img/test-studio-mobile/web-applications/run-web-demos/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/api-reference/api-reference/fig1.png b/docs/img/testing-framework/api-reference/api-reference/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/automate-browser-actions/fig1.jpg b/docs/img/testing-framework/automate-browser-actions/fig1.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-mbunit/fig1.png b/docs/img/testing-framework/using-mbunit/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-nunit/fig1.png b/docs/img/testing-framework/using-nunit/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-nunit/fig2.png b/docs/img/testing-framework/using-nunit/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-nunit/fig3.png b/docs/img/testing-framework/using-nunit/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-vs-team-test/fig1.png b/docs/img/testing-framework/using-vs-team-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-vs-team-test/fig2.png b/docs/img/testing-framework/using-vs-team-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-vs-team-test/fig3.png b/docs/img/testing-framework/using-vs-team-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-vs-team-test/fig4.png b/docs/img/testing-framework/using-vs-team-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/using-xunit/fig1.png b/docs/img/testing-framework/using-xunit/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/annotator/fig1.png b/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/annotator/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing/fig1.png b/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing/fig2.png b/docs/img/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation/fig1.png b/docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation/fig1.png
deleted file mode 100644
index 1ecc9717..00000000
Binary files a/docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation/fig1.png and /dev/null differ
diff --git a/docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object/fig1.png b/docs/img/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object/fig1.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object/fig1.png
rename to docs/img/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object/fig1.png
diff --git a/docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation/fig1.png b/docs/img/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation/fig1.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation/fig1.png
rename to docs/img/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation/fig1.png
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/disabled-attribute/fig1.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/disabled-attribute/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/disabled-attribute/fig2.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/disabled-attribute/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig1.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig2.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig3.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig4.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff/fig1.jpg b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff/fig1.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/browser-inconsistencies-tg/special-characters/fig1.png b/docs/img/troubleshooting-guide/browser-inconsistencies-tg/special-characters/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure/fig1.png b/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig1.png b/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig2.png b/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig3.png b/docs/img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/another-installation/fig1.jpg b/docs/img/troubleshooting-guide/installation-problems-tg/another-installation/fig1.jpg
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig1.png b/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig2.png b/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig3.png b/docs/img/troubleshooting-guide/installation-problems-tg/create-installer-log-file/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/error-starting-services/fig1.png b/docs/img/troubleshooting-guide/installation-problems-tg/error-starting-services/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/proper-net-version/fig1.png b/docs/img/troubleshooting-guide/installation-problems-tg/proper-net-version/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/unable-to-load-sc-plugin/fig1.png b/docs/img/troubleshooting-guide/installation-problems-tg/unable-to-load-sc-plugin/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/installation-problems-tg/vs-plugin-installation/vs2019-ts-extension2.png b/docs/img/troubleshooting-guide/installation-problems-tg/vs-plugin-installation/vs2019-ts-extension2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service/fig1.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/no-results-data/fig1.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/no-results-data/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/add-dynamic-target.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/add-dynamic-target.png
new file mode 100644
index 00000000..a02276dd
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/add-dynamic-target.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/edit-profile.gif b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/edit-profile.gif
new file mode 100644
index 00000000..c1da4fad
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/edit-profile.gif differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-request.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-request.png
new file mode 100644
index 00000000..6a1fbcc0
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-request.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-response.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-response.png
new file mode 100644
index 00000000..2231401a
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-response.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/remove-queries-to-3rd-party-services.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/remove-queries-to-3rd-party-services.png
new file mode 100644
index 00000000..10ca590f
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/remove-queries-to-3rd-party-services.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/requests-loading-visual-resources.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/requests-loading-visual-resources.png
new file mode 100644
index 00000000..08735a72
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/requests-loading-visual-resources.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/see-added-dynamic-target-in-target-step.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/see-added-dynamic-target-in-target-step.png
new file mode 100644
index 00000000..de332fdb
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/see-added-dynamic-target-in-target-step.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/think-times.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/think-times.png
new file mode 100644
index 00000000..66db617c
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/think-times.png differ
diff --git a/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/user-profile-in-edit-mode.png b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/user-profile-in-edit-mode.png
new file mode 100644
index 00000000..c70c76ec
Binary files /dev/null and b/docs/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/user-profile-in-edit-mode.png differ
diff --git a/docs/img/troubleshooting-guide/network-related-problems-tg/fig1.png b/docs/img/troubleshooting-guide/network-related-problems-tg/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/network-related-problems-tg/fig2.png b/docs/img/troubleshooting-guide/network-related-problems-tg/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig1.png b/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig2.png b/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig3.png b/docs/img/troubleshooting-guide/recording-problems-tg/desktop-application/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig1.png b/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig2.png b/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig3.png b/docs/img/troubleshooting-guide/recording-problems-tg/highlighting-misaligned/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig1.png b/docs/img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig2.png b/docs/img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/recorder-attached/fig1.png b/docs/img/troubleshooting-guide/recording-problems-tg/recorder-attached/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig1.png b/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig2.png b/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig3.png b/docs/img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig1.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig2.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig3.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/no-local-test-list-run/fig1.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/no-local-test-list-run/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig1.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig2.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig3.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig4.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/scheduling-service-shuts-down/fig1.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/scheduling-service-shuts-down/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/scheduling-issues-tg/storage-service-connection-failed/fig1.png b/docs/img/troubleshooting-guide/scheduling-issues-tg/storage-service-connection-failed/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/source-control-problems-tg/change-git-credentials/project-settings-guid-value.png b/docs/img/troubleshooting-guide/source-control-problems-tg/change-git-credentials/project-settings-guid-value.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/source-control-problems-tg/change-git-credentials/webui-json-git-credentials.png b/docs/img/troubleshooting-guide/source-control-problems-tg/change-git-credentials/webui-json-git-credentials.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs/fig1.png b/docs/img/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/click-action-fails/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/click-action-fails/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/compilation-error-other-test/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/compilation-error-other-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied/failure-message.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied/failure-message.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig4.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig5.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/missing-page-elements/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/missing-page-elements/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/missing-page-elements/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/missing-page-elements/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/network-dll-access-net4-0/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/network-dll-access-net4-0/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/network-dll-access-net4-0/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/network-dll-access-net4-0/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig4.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/system-out-of-memory/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/system-out-of-memory/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig4.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog/win-sec-dialog.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog/win-sec-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig1.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig1.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig1.png
rename to docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig1.png
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig2.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig2.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig2.png
rename to docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig2.png
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig3.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig3.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig3.png
rename to docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig3.png
diff --git a/docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig4.png b/docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig4.png
old mode 100644
new mode 100755
similarity index 100%
rename from docs/img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig4.png
rename to docs/img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig4.png
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log/fig1.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure/fig1.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig1.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig2.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig3.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig4.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig1.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig2.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig3.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig4.png b/docs/img/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/verification-problems-tg/work-ie-not-ff/fig1.png b/docs/img/troubleshooting-guide/verification-problems-tg/work-ie-not-ff/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/blank-step-builder/optimiseRenderingVS2019.png b/docs/img/troubleshooting-guide/visual-studio-tg/blank-step-builder/optimiseRenderingVS2019.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig1.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig2.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig3.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig4.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig5.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig5.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig6.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig6.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig7.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-add-open-test/fig7.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig1.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig2.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig3.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig4.png b/docs/img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig1.png b/docs/img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig2.png b/docs/img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/fail-search-verify-step-dpi/testhost-dialog.png b/docs/img/troubleshooting-guide/visual-studio-tg/fail-search-verify-step-dpi/testhost-dialog.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/fail-search-verify-step-dpi/vs-test-dropdown.png b/docs/img/troubleshooting-guide/visual-studio-tg/fail-search-verify-step-dpi/vs-test-dropdown.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig1.png b/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig1.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig2.png b/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig2.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig3.png b/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig3.png
old mode 100644
new mode 100755
diff --git a/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig4.png b/docs/img/troubleshooting-guide/visual-studio-tg/missing-assembly-references/fig4.png
old mode 100644
new mode 100755
diff --git a/docs/index.md b/docs/index.md
deleted file mode 100644
index fe18287f..00000000
--- a/docs/index.md
+++ /dev/null
@@ -1,80 +0,0 @@
----
-title: Welcome to Test Studio
-page_title: Welcome to Test Studio
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and desktop testing solution. Test Studio tests support a proprietary Testing framework, functional UI testing, web responsive testing, etc. Find out more on our Welcome page."
-position: 0
----
-
-# Welcome to Test Studio
-
-<a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, PHP and MVC.
-
-
-<a href="/getting-started/test-recording/overview" target="_blank">Test Studio functional testing</a> is a comprehensive yet cost-effective automated testing suite. Users can complete tasks quickly and easily with the product’s point-and-click interface, which is augmented by Telerik-exclusive features like a visual storyboard and 3D element selection. Test Studio also offers script-less test automation for Silverlight applications.
-
- 
-
-<a href="/features/testing-types/load-testing/overview" target="_blank">Test Studio load tests</a> allow users to capture quickly capture, multiply and replay complex web traffic. Record HTTP traffic from desktop browsers, mobile devices and web services, and replay traffic with hundreds or thousands of virtual users spread across multiple machines. Fine-tune your load scenario with data binding, user authentication, and dynamic targets. 
-
-<a href="/test-studio-mobile/overview" target="_blank">Test Studio Mobile</a> is an intuitive and easy to use test automation solution for Mobile application testing. Create tests once and test across multiple devices and OS’s. The point and click functionality allows users to capture quickly and replay complex mobile testing functionality. There is no need to write a single line of code. Test against any number of real devices as you wish or through an emulator by connecting through Wifi.
-
-<a href="/test-studio-for-apis/overview" target="_blank">Test Studio for APIs</a> helps customers verify the integrity and reliability of their APIs in an easy way and incorporate their API testing effort in their continuous testing and delivery process. Test Studio for APIs is used to determine whether APIs return the correct response for a broad range of commonly accepted requests, react properly to edge cases such as failures and unexpected inputs, as well as deliver the responses in an acceptable amount of time.
-
-**Test Studio** offers two product versions:
-
--  Test Studio Web & Desktop version performs **Web and WPF testing** and includes the **Visual Studio plugin**.
--  The Ultimate version adds on top of **Web** and **WPF**, **Mobile**, **Load testing** and **Test Studio for APIs**.
-
-> Test Studio includes runtime files which support the execution of tests on the machine in which it’s licensed. Our <a href="/general-information/test-studio-run-time" target="_blank">**Runtime Edition**</a> is available and suggested for build servers and remote machines where test execution is required.
-
-All versions use identical repositories and file formats, facilitating seamless collaboration between even geographically diverse teams.
-
-<table id=no-table>
-<tr>
-<td valign=top>
-
-## Getting Started
-
-1. [Installation and Activation](/getting-started/installation-and-activation)
-2. [Your First Project](/getting-started/first-project)
-3. [Analyze the Results](/getting-started/analyze-the-results)
-4. [Next Steps](/getting-started/next-steps)
-
-## Getting Help
-
-* <a href="https://www.telerik.com/videos/teststudio">Videos</a>
-* <a href="/getting-started/start-a-project/in-product-tips-tricks">Tips and tricks</a>
-* <a href="https://www.telerik.com/forums/teststudio">Forums</a>
-* <a href="https://www.telerik.com/account/support-tickets">Contact support</a>
-* <a href="https://www.telerik.com/account/support-tickets/customer-service">Submit a general feedback</a>
-* <a href="https://www.telerik.com/account/support-tickets/presales-inquiry">Send a presale inquiry</a>
-* <a href="https://www.telerik.com/support/whats-new/teststudio">What's new</a>
-* <a href="https://www.telerik.com/support/whats-new/teststudio/release-history">Release notes</a>
-</td>
-<td valign=top>
-
-## Features
-
-* [Recorder](/features/recorder/overview)
-* [Elements Explorer](/features/elements-explorer/overview) 
-* [Testing Types](/features/testing-types)
-* [Data Driven Testing](/features/data-driven-testing/overview)
-* [Dialog Handling](/features/dialogs-and-popups/dialogs)
-* [Test Lists](/general-information//test-execution/test-list-execution)
-* [Scheduling Test Runs](/features/scheduling-test-runs/overview)
-* [Results Tab](/general-information/test-results/analyze-test-list-results)
-* [Custom Step from Step Builder](/features/custom-steps/overview)
-* [Project Settings](/features/project-settings/overview)
-* [Logical Steps](/features/logical-steps/if-else)
-* [Source Control](/features/source-control/checkin-guidelines)
-* [Coded Step](/features/coded-steps/coded-step)
-* [API Test as Step](/features/execute-apitest/add-api-test-as-step)
-* [Mobile Testing](/test-studio-mobile/overview)
-
-### Advanced Features
-
-* [Continious Integration and Deployment (CI/CD)](/advanced-topics/build-server/continious-integration-overview)
-* [Coded Samples for Different Scenarios](/advanced-topics/coded-samples/general/send-keystrokes)
-</td>
-</tr>
-<table>
diff --git a/docs/knowledge-base/best-practices-kb/add-existing-test.md b/docs/knowledge-base/best-practices-kb/add-existing-test.md
index a6b73115..b03b1984 100644
--- a/docs/knowledge-base/best-practices-kb/add-existing-test.md
+++ b/docs/knowledge-base/best-practices-kb/add-existing-test.md
@@ -4,7 +4,7 @@ page_title: Add Existing Test Script
 description: How to add an existing test in a new project. A test designed in one project can be reused in another. 
 position: 1
 ---
-# Add Existing Test Script #
+## Add Existing Test Script 
 
 If you would need to reuse a test from another project the easiest and safest way would be to use the built-in option to import existing test files as shown on the screenshot below:
 
diff --git a/docs/knowledge-base/best-practices-kb/automating-captcha-in-telerik-test-studio.md b/docs/knowledge-base/best-practices-kb/automating-captcha-in-telerik-test-studio.md
new file mode 100644
index 00000000..5828df81
--- /dev/null
+++ b/docs/knowledge-base/best-practices-kb/automating-captcha-in-telerik-test-studio.md
@@ -0,0 +1,44 @@
+---
+title: Automating Captcha in Telerik Test Studio
+description: Learn possible solutions for handling Captcha during automation testing in Telerik Test Studio.
+type: how-to
+page_title: Handling Captcha Challenges in Automation Using Telerik Test Studio
+meta_title: Handling Captcha Challenges in Automation Using Telerik Test Studio
+slug: automating-captcha-in-telerik-test-studio
+tags: telerik test studio, captcha, automation, find logic, search by image
+res_type: kb
+ticketid: 1675222
+---
+
+
+## Description
+
+I need to automate a process that involves solving a Captcha as part of the steps. Is there any solution or workaround to achieve this during automation testing?
+
+This knowledge base article also answers the following questions:
+- How to bypass Captcha during automation testing?
+- What are the options for handling Captcha in Telerik Test Studio?
+- Can Captcha be automated in test environments?
+
+## Solution
+
+Captchas are specifically designed to prevent automation for security purposes, including tools like Telerik Test Studio. However, there are alternative approaches you can consider during testing:
+
+1. **Whitelist Company Test IP:** Add your company's or test machine’s IP to the trusted list to bypass Captcha verification during testing.
+
+2. **Disable Captcha in Test Environment:** Turn off Captcha in testing environments such as staging or development while keeping it enabled in production.
+
+3. **Use Image-Based Element Identification:** For certain weak Captchas, you might use image-based element identification. This should only be a last resort if other options are unavailable.
+
+   - To identify an element by image for a single test step, enable `SearchByImageFirst` in the [step properties](/features/test-maintenance/test-step-properties).  
+   - To set image-based identification for the entire project, enable the checkbox `Search by image first` in the [Find Logic project settings](/features/project-settings/find-logic).  
+
+   Learn more about [element identification by image](/automated-tests/elements/elements-find-expression#elements-image).
+
+Discuss the most suitable approach with your development team to align with your requirements.
+
+## See Also
+
+- [Step Properties in Telerik Test Studio](/features/test-maintenance/test-step-properties)
+- [Find Logic Project Settings](h/features/project-settings/find-logic)
+- [Element Identification by Image in Telerik Test Studio](/automated-tests/elements/elements-find-expression#elements-image)
diff --git a/docs/knowledge-base/best-practices-kb/generate-application-log.md b/docs/knowledge-base/best-practices-kb/generate-application-log.md
index b26e3a2f..7f4be090 100644
--- a/docs/knowledge-base/best-practices-kb/generate-application-log.md
+++ b/docs/knowledge-base/best-practices-kb/generate-application-log.md
@@ -4,7 +4,7 @@ page_title: Generate Application Log
 description: How to generate the Test Studio application log? The application log records all events happening in the UI and can be used when troubleshooting various errors, which appear while recording, executing tests or while maintaining the test project. Any unexpected errors can be also explored in the application log. 
 position: 1
 ---
-# How to Generate the Test Studio Application Log
+## How to Generate the Test Studio Application Log
 
 Test Studio application logging records all events triggered from the tool while recording tests, executing these or maintaining elements and tests in the project. It is a powerful source of information, which helps to investigate any sort of issues.
 
@@ -112,15 +112,14 @@ Start <a href="http://support2.microsoft.com/kb/136393" target="_blank">Regedit<
 
 Find (or create) the __TraceLogEnabled__ key in this folder. Double click it and change the Value data to 1. The __TraceLogPath__ value is where the log gets stored. Ensure to isnert the file full path with name and file extension like this **C:\Temp\TraceLog\log.txt**.
 
-[1]: /img/knowledge-base/best-practices-kb/generate-application-log/fig1.png
+
 [2]: /img/knowledge-base/best-practices-kb/generate-application-log/fig2.png
 [2a]: /img/knowledge-base/best-practices-kb/generate-application-log/fig2a.png
 [3]: /img/knowledge-base/best-practices-kb/generate-application-log/fig3.png
 [4]: /img/knowledge-base/best-practices-kb/generate-application-log/fig4.png
-[5]: /img/knowledge-base/best-practices-kb/generate-application-log/fig5.png
+
 [6]: /img/knowledge-base/best-practices-kb/generate-application-log/fig6.png
 [7]: /img/knowledge-base/best-practices-kb/generate-application-log/fig7.png
 [7a]: /img/knowledge-base/best-practices-kb/generate-application-log/fig7a.png
 [8]: /img/knowledge-base/best-practices-kb/generate-application-log/fig8.png
 [8a]: /img/knowledge-base/best-practices-kb/generate-application-log/fig8a.png
-[9]: /img/knowledge-base/best-practices-kb/generate-application-log/fig9.png
diff --git a/docs/knowledge-base/best-practices-kb/id-automation-id.md b/docs/knowledge-base/best-practices-kb/id-automation-id.md
index 9e0678c8..e75fe722 100644
--- a/docs/knowledge-base/best-practices-kb/id-automation-id.md
+++ b/docs/knowledge-base/best-practices-kb/id-automation-id.md
@@ -4,7 +4,7 @@ page_title: ID & Automation ID
 description: Static and unique id attribute for the elements in a dynamic application. It is recommended to assign such during the application development process to ease the automation process. 
 position: 1
 ---
-# Element Identification with ID and Automation ID #
+## Element Identification with ID and Automation ID 
 
 As a QA professional, it's **important** to get **involved** with the **development team** early on in the process. This article will discuss just one of the many benefits in doing so – coding standards and the use of IDs for enhanced team productivity. Require this up front and you can significantly cut back test case maintenance.
  
@@ -14,10 +14,8 @@ I'll use Tag Indexes as my example – if my find logic says locate the tenth \<
  
 Stop the madness.
  
-Ask your development team to implement IDs for your dynamic HTML applications or Automation IDs for your Silverlight applications. As long as the IDs are unique, your element repository will not require maintenance when changes are made to your application.
+Ask your development team to implement IDs for your dynamic HTML applications or Automation IDs for your WPF applications. As long as the IDs are unique, your element repository will not require maintenance when changes are made to your application.
  
 Our Automated Testing Tools do an amazing job at automatically identifying elements for you – this saves countless hours and allows you to continue the expansion of your regression suite while keeping your project on schedule. Why not take this to the next level by implementing IDs as a coding standard and substantially reducing your test case maintenance time.
 
-* Silverlight Users – <a href="http://msdn.microsoft.com/en-us/library/system.windows.automation.automationproperties.automationid.aspx" target="_blank">read more on the AutomationProperties.AutomationID Attached Property</a>.
-
 * Dynamic HTML Testers – <a href="http://msdn.microsoft.com/en-us/library/ms533880(v=vs.85).aspx" target="_blank">read more on the Element ID Attribute</a>.
\ No newline at end of file
diff --git a/docs/knowledge-base/best-practices-kb/regular-vs-coded-step.md b/docs/knowledge-base/best-practices-kb/regular-vs-coded-step.md
index 9e3684d6..bd3e276b 100644
--- a/docs/knowledge-base/best-practices-kb/regular-vs-coded-step.md
+++ b/docs/knowledge-base/best-practices-kb/regular-vs-coded-step.md
@@ -4,15 +4,15 @@ page_title: Regular vs. Coded Step
 description: The benefits of recorded steps against coded and vice versa. 
 position: 1
 ---
-# Regular vs. Coded Step #
+## Regular vs. Coded Step 
 
 *We've noticed that a considerable number our customers' projects rely heavily on code in order to implement their test cases.*
 
 Test Studio is designed to keep coding to a minimum. Test Studio will automatically generate for you steps that correspond to lengthy code blocks. Let's look at a simple example. Let's say you need to verify that the *alt* property of the logo on the Wikipedia main page matches the text WikipediA. This is added quickly and easily in Test Studio and a single regular step is generated. If you convert this step to code, however, it will look like this:
 
-```C#
+````C#
 Pages.Wikipedia.WikipediAImage.AssertAttribute().Value("alt", ArtOfTest.Common.StringCompareType.Contains, "WikipediA");
-```
+````
 
 Regular and coded steps visible here:
 
@@ -20,19 +20,19 @@ Regular and coded steps visible here:
 
 The single line of code might seem easy to write. However the following element:
 
-```C#
+````C#
 Pages.Wikipedia.WikipediAImage
-```
+````
 
 is actually a variable that represents Find Logic generated by Test Studio. So in this case here's the code that would replace the step without using anything generated by Test Studio:
 
-```C#
+````C#
 HtmlImage logo = Find.ByExpression<HtmlImage>(@"src=//upload.wikimedia.org/wikipedia/commons/thumb/b/bb/Wikipedia_wordmark.svg/174px-Wikipedia_wordmark.svg.png");
 
 logo.AssertAttribute().Value("alt", ArtOfTest.Common.StringCompareType.Contains, "WikipediA");
-```
+````
 
-The first part of this code is Find Logic. This is one of the challenging aspects of of UI automation and a lot of the times you'll be unable to find a good way to identify an element. Particularly when no ID (HTML) or <a href="http://blogs.telerik.com/automated-testing-tools/posts/11-03-01/best-practices-element-identification-with-id-and-automationid" target="_blank">Automation ID</a> (Silverlight) has been implemented. Test Studio will do that for you, saving you a lot of work and improving the reliability of your test. Additionally, Test Studio allows you to control and change the Find Logic as seen <a href="/features/elements-explorer/find-element" target="_blank">here</a> and <a href="/features/project-settings/identification-logic" target="_blank">here</a>.
+The first part of this code is Find Logic. This is one of the challenging aspects of of UI automation and a lot of the times you'll be unable to find a good way to identify an element. Particularly when no ID (HTML) or <a href="http://blogs.telerik.com/automated-testing-tools/posts/11-03-01/best-practices-element-identification-with-id-and-automationid" target="_blank">Automation ID</a> has been implemented. Test Studio will do that for you, saving you a lot of work and improving the reliability of your test. Additionally, Test Studio allows you to control and change the Find Logic as seen <a href="/features/elements-explorer/find-element" target="_blank">here</a> and <a href="/features/project-settings/identification-logic" target="_blank">here</a>.
  
 Additionally using coded step increases the chances of hitting compilation errors and other errors related to building a test project.
 
diff --git a/docs/knowledge-base/best-practices-kb/submit-support-ticket.md b/docs/knowledge-base/best-practices-kb/submit-support-ticket.md
index 24cf1da5..ffb2c6e2 100644
--- a/docs/knowledge-base/best-practices-kb/submit-support-ticket.md
+++ b/docs/knowledge-base/best-practices-kb/submit-support-ticket.md
@@ -4,13 +4,13 @@ page_title: Submit Support Ticket
 description: How to submit a support ticket to contact the Test Studio Support Team. What details to provide to get help for a Test Studio query as soon as possible. 
 position: 1
 ---
-# Submit Support Ticket #
+## Submit Support Ticket 
 
 You can submit your support query in your your Telerik account <a href="https://www.telerik.com/account/support-tickets" target="_blank">here</a>.
 
 For timely issue resolution, provide as much information as possible in your initial message. The below guidelines will help you determine what details may be required.
 
-## Steps to Reproduce Any Misbehavior in the Tool ##
+## Steps to Reproduce Any Misbehavior in the Tool 
 
 Provide precise steps to reproduce the issue. Please include:
 
@@ -20,7 +20,7 @@ Provide precise steps to reproduce the issue. Please include:
 
 * A short screen recording of the issue.
 
-## Error Message ##
+## Error Message 
 
 Copy and paste the entire message and/or provide a screen shot of it.
 
@@ -44,7 +44,7 @@ Copy and paste the entire message and/or provide a screen shot of it.
 
 * For issues with licensing, product activation, or accessing virtual users, email <mailto:teststudiosales@telerik.com>.
 
-## Application Under Test Details ##
+## Application Under Test Details 
 
 Is your application publicly accessible?
 
@@ -56,7 +56,7 @@ Is your application publicly accessible?
 
 * If the issue is specific to your WPF application, send the entire app. If this is not possible, create a small sample app that demonstrates the issue.
 
-## New Tickets ##
+## New Tickets 
 
 * To ask multiple, unrelated questions, please submit a separate ticket for each question. This allows us to more efficiently address your issues.
 
diff --git a/docs/knowledge-base/best-practices-kb/test-modularization.md b/docs/knowledge-base/best-practices-kb/test-modularization.md
index 8d09b6b2..4905cc61 100644
--- a/docs/knowledge-base/best-practices-kb/test-modularization.md
+++ b/docs/knowledge-base/best-practices-kb/test-modularization.md
@@ -4,21 +4,21 @@ page_title: Test Modularization
 description: Best practices how to organize a Test Studio project to ease its maintenance in the future. Reusing tests across the project, using coded steps and custom code, data driven testing, data binding verification and input steps, dynamic data binding using extracted values in runtime. logical steps - if else, loop.
 position: 1
 ---
-#Test Modularization#
+## Test Modularization
 
 *How can I create common global functions for all my tests? Does Test Studio support global project variables or a built-in data store that can be used for all tests? Is there an ability to collaborate between tests, pass arguments to them, and run a set of tests without using test lists?*
 
-##Solution##
+## Solution
 
 The term "*Test Modularization*" is often used to describe common approaches how to configure your project to ease its maintenance and perception. Test Studio offers lots of features to obtain great project visibility and implementing their usage is  very much encouraged. There are two main approaches to accomplish good modularization: **Test as Step** and **Using Code**.
 
-###Test as Step###
+### Test as Step
 
 <a href="/features/custom-steps/test-as-step" target="_blank">Test as Step</a> is the method most commonly used.  The idea is to divide your script into sub-tests that could be called by a parent test. A good example for such sub-tests are "Login" and "Logout". Basically you could insert any repeating actions into a sub-test and call it whenever required. We do not limit how deep you can go with sub-tests, although it becomes unmanageable and we do not recommend to go too deep. 
  
 In the <a href="/features/project-explorer/overview" target="_blank">project explorer</a> you could create sub-folders within the test project folder to better organize and group the main tests and sub-tests together. Right click the project node and select **Create Folder** to add a new one. 
 
-###Using Code###
+### Using Code
 
 In this approach you use the <a href="/features/custom-steps/script-step" target="_blank">Script Step</a> feature to call your own coded functions. These coded functions can exist in any of the below places:
 
@@ -30,7 +30,7 @@ In this approach you use the <a href="/features/custom-steps/script-step" target
 
 4. Within a <a href="/features/coded-steps/standalone-code-file" target="_blank">standalone code file</a> which will be globally accessible in the terms of the current project. 
 
-###Other useful features###
+### Other useful features
 
 The closest built-in feature we have for globally accessible data is <a href="/features/data-driven-testing/Overview" target="_blank">Data Driven Testing</a>. Setting the sub-test to <a href="/features/data-driven-testing/multi-level-tests" target="_blank">Inherit the Data</a> from the parent test will allow you to have global project data. This parameterizes the sub-test by binding the parent test to a different set of data. In general you could data bind each test with separate data sources - it depends on your particular scenario. For your convenience there are different <a href="/features/data-driven-testing/add-data-source" target="_blank">internal and external sources</a> supported. 
  
diff --git a/docs/knowledge-base/browsers-kb/calibration-error-preferences-file.md b/docs/knowledge-base/browsers-kb/calibration-error-preferences-file.md
index b961a21d..0ef0b68d 100644
--- a/docs/knowledge-base/browsers-kb/calibration-error-preferences-file.md
+++ b/docs/knowledge-base/browsers-kb/calibration-error-preferences-file.md
@@ -2,9 +2,9 @@
 title: Edge Calibration Error
 page_title: Edge Calibration Error
 description: "Edge Calibration Error in Test Studio - Could not read Edge Preferences file Error during serialization or deserialization. The length of the string exceeds the value set on the maxJsonLength value." 
-position: 1
+position: 3
 ---
-# Error on Trying to Calibrate Edge Browser 
+## Error on Trying to Calibrate Edge Browser 
 
 Test Studio <a href="/prerequisites/configure-your-browser/browser-configuration" target="_blank">browsers calibration</a> is a mandatory step to set the supported browsers in compatible state for recording and execution of automated tests.
 
diff --git a/docs/knowledge-base/browsers-kb/chrome-clean-reinstall.md b/docs/knowledge-base/browsers-kb/chrome-clean-reinstall.md
index 07d3735f..7245f392 100644
--- a/docs/knowledge-base/browsers-kb/chrome-clean-reinstall.md
+++ b/docs/knowledge-base/browsers-kb/chrome-clean-reinstall.md
@@ -2,26 +2,30 @@
 title: Chrome Clean Reinstall
 page_title: Chrome Clean Reinstall
 description: A clean reinstall of Chrome browser may help to fix Test Studio Chrome Extension not loading or steps not executing issues. A clean reinstall of Chrome ensures the browser's user data is removed.
-position: 3
+position: 6
 ---
-# How to Perform Clean Reinstall of Chrome Browser
+## How to Perform Clean Reinstall of Chrome Browser
 
 ## Problem
 
-Test Studio extension in Chrome browser does not load during recording, or the test steps are not executing.
+Chrome browser does not start when selected as recording browser, or the test steps are not executed.
 
 ## Solution
 
-Complete a clean reinstall of Chrome browser to ensure left over user data interferes with the Test Studio extension and prevents the browser to act as expected. The below steps guides you through the process:
+Clean reinstall of Chrome browser refreshes the standard browser profile and the one used from Test Studio. That way any left over user data which might be interfering and might be preventing the browser to act as expected is cleared. 
+
+The below steps guides you through the process:
 
 1. Start Windows Control Panel > Add/Remove Programs and choose to uninstall Chrome from your machine.
 
-2. In a File Explorer browse to Chrome user data folder - default is *C:\Users\\\<YourUsername>\AppData\Local\Google\Chrome*. Delete any leftover data in this folder or remove the complete folder.
+2. In a File Explorer browse to Chrome user data folder - default `C:\Users\\YourUsername\AppData\Local\Google\Chrome`. Delete any leftover data in this folder or remove the complete folder.
 
-3. In a File Explorer browse to Test Studio user data folder for Chrome - *C:\Users\\\<YourUsername>\AppData\Local\ArtOfTest\TSChromeUserData* and delete its content. 
+3. In a File Explorer browse to Test Studio user data folder for the browsers - `C:\Users\\YourUsername\AppData\Local\ArtOfTest\` and delete the folders for Chrome and Chrome headless profiles: 
+    - TSChromeUserData
+    - TSChromeHeadlessUserData
 
-3. Perform a fresh install of the latest official version of the Chrome browser.
+4. Perform a fresh install of the latest official version of the Chrome browser.
 
-4. To use the Chrome browser for Test Studio automation again, you need to [calibrate it](https://docs.telerik.com/teststudio/getting-started/configure-your-browser/chrome#2-browser-calibration) and add the [Telerik Test Studio extension](https://chrome.google.com/webstore/detail/progress-telerik-test-stu/gegcllkonmciadpdldechnepmjildoan).
+5. Initiate a test recording session or execution using the Chrome browser.
 
-5. If you continue experience troubles with Chrome test execution, you can contact the Test Studio support team by [submitting a support ticket](/knowledge-base/best-practices-kb/submit-support-ticket).
+6. If you continue experience troubles with Chrome test execution, you can contact the Test Studio support team by [submitting a support ticket](/knowledge-base/best-practices-kb/submit-support-ticket) and providing the [Test Studio application log](/knowledge-base/best-practices-kb/generate-application-log#operate-with-logging-in-standalone-version) generated during the attempt to execute or record a test in Test Studio.
diff --git a/docs/knowledge-base/browsers-kb/custom-chrome-path.md b/docs/knowledge-base/browsers-kb/custom-chrome-path.md
index 53f18482..35f61780 100644
--- a/docs/knowledge-base/browsers-kb/custom-chrome-path.md
+++ b/docs/knowledge-base/browsers-kb/custom-chrome-path.md
@@ -2,9 +2,9 @@
 title: Custom Chrome Path
 page_title: Custom Chrome Path
 description: How to set Custom Chrome path if the Chrome installation is a custom one. 
-position: 1
+position: 2
 ---
-#How to Set a Custom Chrome Path#
+## How to Set a Custom Chrome Path
 
 Test Studio looks by default at *C:\Program Files (x86)\Google\Chrome\Application\* for the chrome.exe and *C:\Users\\[UserName]\AppData\Local\Google\Chrome\User Data\Default\* for preferences file.
 
diff --git a/docs/knowledge-base/browsers-kb/custom-chrome-profile.md b/docs/knowledge-base/browsers-kb/custom-chrome-profile.md
index c77fad6b..17adc069 100644
--- a/docs/knowledge-base/browsers-kb/custom-chrome-profile.md
+++ b/docs/knowledge-base/browsers-kb/custom-chrome-profile.md
@@ -2,9 +2,9 @@
 title: Custom Chrome Profile
 page_title: Custom Chrome Profile
 description: Calibrate the default Chrome Profile
-position: 2
+position: 4
 ---
-# How to Set a Custom Chrome Profile
+## How to Set a Custom Chrome Profile
 
 Test Studio allows you to create a custom profile in Chrome browser, which remains in use only when running tests from Test Studio.
 
diff --git a/docs/knowledge-base/browsers-kb/custom-edge-chromium-profile.md b/docs/knowledge-base/browsers-kb/custom-edge-chromium-profile.md
index ee7488db..e6dba8e1 100644
--- a/docs/knowledge-base/browsers-kb/custom-edge-chromium-profile.md
+++ b/docs/knowledge-base/browsers-kb/custom-edge-chromium-profile.md
@@ -2,9 +2,9 @@
 title: Custom Edge Chromium Profile
 page_title: Custom Edge Chromium Profile
 description: Use Custom Edge Chromium Profile for testing in Test Studio. 
-position: 2
+position: 5
 ---
-# How to Set a Custom Edge Chromium Profile 
+## How to Set a Custom Edge Chromium Profile 
 
 Test Studio allows you to create a custom profile in Edge Chromium browser, which remains in use only when running tests from Test Studio.
 
diff --git a/docs/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store.md b/docs/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store.md
index 744fbcaf..22050b18 100644
--- a/docs/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store.md
+++ b/docs/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store.md
@@ -6,7 +6,7 @@ page_title:  Progress® Telerik® Test Studio® Extension is Not Available in Ch
 tags: progress, telerik, test studio, chrome, extension, edge chromium
 res_type: kb
 ticketid: 1678431
-position: 0
+position: 1
 ---
 
 
diff --git a/docs/knowledge-base/data-driven-testing-kb/dynamic-data-binding.md b/docs/knowledge-base/data-driven-testing-kb/dynamic-data-binding.md
index a9eab0b0..94eac64f 100644
--- a/docs/knowledge-base/data-driven-testing-kb/dynamic-data-binding.md
+++ b/docs/knowledge-base/data-driven-testing-kb/dynamic-data-binding.md
@@ -5,11 +5,11 @@ description: I want my test to dynamically bind to a different data set at run-t
 previous_url: /user-guide/knowledge-base/data-driven-testing/dynamic-data-binding.aspx, user-guide/knowledge-base/data-driven-testing/dynamic-data-binding
 position: 1
 ---
-#Dynamic Data Binding#
+## Dynamic Data Binding
 
 *I want my test to dynamically bind to a different data set at run-time. The data I want the test to use will depend on certain conditions of my application, but the test steps will always be the same.*
 
-##Solution 1##
+## Solution 1
 
 First, be aware that dynamically binding data is not currently a built-in feature in Test Studio. You can only bind a test to a single data source. However, there is a trick you can implement in code to achieve the same result. The trick relies on swapping the data file to which a test is bound at run time. 
 
@@ -29,15 +29,15 @@ For example:
 
 3. Keep in mind that when Test Studio binds a test to an Excel file, it actually makes a copy of the file in the **Project\Data** folder. Ensure you swap the file located in the **Project\Data** folder, and not the file in its original location.
 
-##Solution 2##
+## Solution 2
 
 Put your data into a SQL data base and <a href="/features/data-driven-testing/bind-test-data-source" target="_blank">Use T-SQL to Pull the Data</a> you want from the database. Optionally, you can <a href="/knowledge-base/data-driven-testing-kb/sql-random-row" target="_blank">Generate a Random Number</a> in your T-SQL to point to the row of data to pull.
 
-##Solution 3##
+## Solution 3
 
 You can <a href="/advanced-topics/coded-samples/general/execution-extensions" target="_blank">Create Your Own Test Extension DLL</a> and implement the OnInitializeDataSource in which you can do pretty much anything in code. Place the DLL into the following directory:
 
-* **C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\**
+*C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins\**
 
  
 
diff --git a/docs/knowledge-base/data-driven-testing-kb/multiple-users-with-login.md b/docs/knowledge-base/data-driven-testing-kb/multiple-users-with-login.md
index 5df04c0b..d6da37a7 100644
--- a/docs/knowledge-base/data-driven-testing-kb/multiple-users-with-login.md
+++ b/docs/knowledge-base/data-driven-testing-kb/multiple-users-with-login.md
@@ -4,7 +4,7 @@ page_title: Multiple Users with Login
 description: How to configure a test to use the same data source row multiple times. 
 position: 1
 ---
-#Repeating Actions for Multiple Users with Login#
+## Repeating Actions for Multiple Users with Login
 
 After loading the input data using data binding (an Excel file), I want to get the specific row item in the data multiple times. Here is the business scenario:
 
diff --git a/docs/knowledge-base/data-driven-testing-kb/numeric-values-trimmed.md b/docs/knowledge-base/data-driven-testing-kb/numeric-values-trimmed.md
index 73681564..81ee632c 100644
--- a/docs/knowledge-base/data-driven-testing-kb/numeric-values-trimmed.md
+++ b/docs/knowledge-base/data-driven-testing-kb/numeric-values-trimmed.md
@@ -4,15 +4,15 @@ page_title: Fix Trimmed Numeric Values
 description: External data source from CSV file is trimmed after the numeric separator. Data is not the same when you bind it to a test. IP values are not full in data driven test.
 position: 6
 ---
-#Numeric Values from External Data Source are Trimmed#
+## Numeric Values from External Data Source are Trimmed
 
-##Problem##
+## Problem
 
 When you have a data driven test with CSV external source and for example try typing in an IP address like this "192.168.0.0", the value can get trimmed to just "192.168". The reason why the IP address is trimmed is because of the Ole DB driver, which TestStudio is using under the hood. In details the Ole DB driver is asked to create an in-memory DataTable. The first row defines the column's name and the other rows are the actual data. As each cell value, including the column names, are scanned a data type is extrapolated.
 
 All rows that have IPs like this "192.168.0.0" could get trimmed based on the Windows' Culture settings, where the **"."** is a numeric separator. The DB driver matches this to a "numeric" value and trims it to "192.168".
 
-##Solution##
+## Solution
 
 There are two possible solution for the above issue.
 
diff --git a/docs/knowledge-base/data-driven-testing-kb/pass-a-variable.md b/docs/knowledge-base/data-driven-testing-kb/pass-a-variable.md
index a02e55d1..b450ede5 100644
--- a/docs/knowledge-base/data-driven-testing-kb/pass-a-variable.md
+++ b/docs/knowledge-base/data-driven-testing-kb/pass-a-variable.md
@@ -4,11 +4,11 @@ page_title: Pass a Variable
 description: An example how to reuse a dynamically extracted variable (during runtime) in different tests.
 position: 1
 ---
-#Pass a Variable Between Tests#
+## Pass a Variable Between Tests
 
 I would like to capture data in one test and pass it to another. Is it possible to set a variable in one test and have it accessible by another test in the project?
 
-##Solution##
+## Solution
 
 This is possible using the <a href="/features/recorder/verifications/Extraction" target="_blank">Extraction</a> and <a href="/features/custom-steps/test-as-step" target="_blank">Test as Step</a> features.
 
@@ -51,4 +51,3 @@ This is possible using the <a href="/features/recorder/verifications/Extraction"
 [2]: /img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig2.png
 [3]: /img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig3.png
 [4]: /img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig4.png
-[5]: /img/knowledge-base/data-driven-testing-kb/pass-a-variable/fig5.png
diff --git a/docs/knowledge-base/data-driven-testing-kb/sql-random-row.md b/docs/knowledge-base/data-driven-testing-kb/sql-random-row.md
index 71713d1f..4f46dd84 100644
--- a/docs/knowledge-base/data-driven-testing-kb/sql-random-row.md
+++ b/docs/knowledge-base/data-driven-testing-kb/sql-random-row.md
@@ -4,11 +4,11 @@ page_title: SQL Random Row
 description: I would like to use a single, random row of data for each execution of a test that is data bound to a SQL Database.
 position: 1
 ---
-#Use T-SQL to Pull a Random Row from a SQL Database#
+## Use T-SQL to Pull a Random Row from a SQL Database
 
 *I would like to use a single, random row of data for each execution of a test that is data bound to a SQL Database.*
 
-##Solution##
+## Solution
 
 This is possible with T-SQL. Here's how to do it:
 
@@ -23,19 +23,20 @@ This is possible with T-SQL. Here's how to do it:
 
 3. Check **Use T-SQL**. Enter the following code into the **T-SQL Editor** section and click **Update**:
 
-	```SQL
-	SELECT TOP 1 [Name], [City], [Email], [Message]
-	FROM [myDataBase].[dbo].[table]
-	Where Email Like '%domain%'
-	ORDER By NEWID()
-	```
-	* Line 1 indicates how many rows and which columns to use.
+````SQL
+SELECT TOP 1 [Name], [City], [Email], [Message]
+FROM [myDataBase].[dbo].[table]
+Where Email Like '%domain%'
+ORDER By NEWID()
+````
+
+- Line 1 indicates how many rows and which columns to use.
 	
-	* Line 2 indicates the database and table name.
+- Line 2 indicates the database and table name.
 	
-	* Line 3 indicates whether to filter based on text matching criteria. In this case, since all entries in the Email column contain domain, all rows are returned.
+- Line 3 indicates whether to filter based on text matching criteria. In this case, since all entries in the Email column contain domain, all rows are returned.
 	
-	* Line 4 sorts the rows by a unique identifier, which essentially randomizes them in the database.
+-  Line 4 sorts the rows by a unique identifier, which essentially randomizes them in the database.
 
 
 4.&nbsp; Click **Update again** to see the randomization in action. 
diff --git a/docs/knowledge-base/dialogs-and-popups-kb/closesbrowser-property.md b/docs/knowledge-base/dialogs-and-popups-kb/closesbrowser-property.md
index 555a07bb..8276e1dd 100644
--- a/docs/knowledge-base/dialogs-and-popups-kb/closesbrowser-property.md
+++ b/docs/knowledge-base/dialogs-and-popups-kb/closesbrowser-property.md
@@ -4,7 +4,7 @@ page_title: ClosesBrowser Property
 description: When to use the ClosesBrowser Property for popups which invokes an event that closes the pop-up.
 position: 1
 ---
-# Using the ClosesBrowser Property for Pop-ups
+## Using the ClosesBrowser Property for Pop-ups
 
 Pop-ups can have a control (usually a button) which invokes an event that closes the pop-up. This can cause problems when performing UI Automation with Test Studio.
 
diff --git a/docs/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action.md b/docs/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action.md
index 603f67a9..e5d1bfbd 100644
--- a/docs/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action.md
+++ b/docs/knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action.md
@@ -4,12 +4,12 @@ page_title: UnexpectedDialogAction
 description: Handle any unexpected dialogs if such appear during test list execution. 
 position: 1
 ---
-#Avoiding Dialog Handling Problems with the UnexpectedDialogAction Feature#
+## Avoiding Dialog Handling Problems with the UnexpectedDialogAction Feature
 
 I am running tests as part of a test list. I am having trouble with dialog handler steps that timeout.
 
 
-##Solution##
+## Solution
 
 The problem is likely related to your test list settings. There's a setting called UnexpectedDialogAction which allows the tests (in a test list) to automatically handle dialogs that are deemed "unexpected." Since it's hard to distinguish between expected and unexpected dialogs, this feature handle dialogs that it shouldn't. Here's how to determine whether this is the problem you're experiencing:
 
@@ -24,13 +24,13 @@ Execute the problematic test as part of a test list, and then by Quick Execution
 
 If you determine that the UnexpectedDialogAction is causing unpredictable behavior in your test lists, set it *DoNotHandle* and the problem should disappear.
 
-###Standalone version###
+### Standalone version
 
 In Test Studio Standalone version, set the *UnexpectedDialogAction* from the *Edit Test List Settings menu*:
 
 ![UnexpectedDialogAction][1]
 
-###Visual Studio plugin###
+### Visual Studio plugin
 
 In the Visual Studio plugin, edit the <a href="/features/test-runners/MSTest" target="_blank">.testsettings</a> file that corresponds to the test list run:
 
diff --git a/docs/knowledge-base/dialogs-and-popups-kb/variable-query-strings.md b/docs/knowledge-base/dialogs-and-popups-kb/variable-query-strings.md
index 3b27e757..d0651ff7 100644
--- a/docs/knowledge-base/dialogs-and-popups-kb/variable-query-strings.md
+++ b/docs/knowledge-base/dialogs-and-popups-kb/variable-query-strings.md
@@ -4,7 +4,7 @@ page_title: Variable Query Strings
 description: Often web applications are designed such that they use a variable or random query string in the URL address. The order status page at Newegg.com is a good example of this. Every time you go to their order status page, a random ID is added to the URL. Here is how Test Studio can handle these dynamic URLs.
 position: 1
 ---
-#How to Deal with Variable Query Strings in URLs#
+## How to Deal with Variable Query Strings in URLs
 
 Often web applications are designed such that they use a variable or random query string in the URL address. The order status page at Newegg.com is a good example of this. Every time you go to their order status page, a random ID is added to the URL as shown in this screen shot:
 
@@ -16,7 +16,7 @@ In this screen shot I recorded entering and leaving the Newegg order status page
 
 ![Duplicate elements][2]
 
-##Solution##
+## Solution
 
 You can easily recover from what appears to be a mess. Before I explain how to clean up this mess, I'd like to reassure you that what looks like a mess in Elements Explorer is not really a problem during test execution. The framework actually doesn't use the page nodes during test execution. It only uses the Find Expressions for the elements that the test steps interact with. So even though you have multiple page nodes, each with their own element, executing the recorded test will work correctly since it is actually ignoring the variable URL.
 
@@ -34,12 +34,16 @@ In order to avoid this duplication in the feature recording of your tests change
 
 1. Open Project Settings.
 
-	<table id="no-table">
+	<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+	<td>
+	
+	![Standalone][5]<br>**Standalone version**</td>
+	<td>
+	
+	![VS Plugin][6]<br>**VS Plugin**</td>
 	<tr>
-	<td>![Standalone][5]<br>**Standalone version**</td>
-	<td>![VS Plugin][6]<br>**VS Plugin**</td>
-	<tr>
-	<table>
+	</table>
 
 2. Click **Recording Options**.
 
@@ -49,7 +53,7 @@ In order to avoid this duplication in the feature recording of your tests change
 
 After making this change, recording your test scripts will automatically merge duplicate pages and elements into just one page node with the unique elements showing under it.
 
-##Connecting to HTML Popup Windows##
+## Connecting to HTML Popup Windows
 
 The other place you may have to deal with variable query strings is in the URL of pop-up windows. Unfortunately these have to be cleaned up manually after each recording. Test Studio currently does not have a feature to automatically strip or ignore the query strings when recording and/or executing a "Connect to pop-up window" test step. If you try to execute a test that connects to a pop-up window with a variable query string in the URL, the test will probably fail because you are almost guaranteed to get a different query string at run time then you had when you recorded your test script. Here's a screen shot of an example:
 
diff --git a/docs/knowledge-base/getting-out-of-memory-exception-errors.md b/docs/knowledge-base/getting-out-of-memory-exception-errors.md
index e248dad8..83fd2212 100644
--- a/docs/knowledge-base/getting-out-of-memory-exception-errors.md
+++ b/docs/knowledge-base/getting-out-of-memory-exception-errors.md
@@ -3,9 +3,8 @@ title: Getting Out of Memory Exception Errors
 page_title: System Out of Memory Exception Errors
 description: Getting Out of Memory Exception (OutOfMemory or System.OutOfMemoryException) Errors when scheduling tests to run on remote machine. Remote test list execution is failing because of OutOfMemory exceptions. Fix OutOfMemory Exception OOM exception. Open results crashes with System.OutOfMemory.
 previous_url: /user-guide/knowledge-base/oom.aspx
-position: 20
+position: 2
 ---
-# Dealing with `OutOfMemoryException` Errors
 
 ## Problem
 
diff --git a/docs/knowledge-base/load-testing-kb/analyze-results.md b/docs/knowledge-base/load-testing-kb/analyze-results.md
index db0aaa03..0a3ae1d3 100644
--- a/docs/knowledge-base/load-testing-kb/analyze-results.md
+++ b/docs/knowledge-base/load-testing-kb/analyze-results.md
@@ -4,29 +4,29 @@ page_title: Analyze Results
 description: Analyze Load Result. Identify Key Areas of Load Data. User Experience Metrics. Load Generation Metrics. Resource Use Metrics. Correlate Key Load Data. Identify Issues based on the load test runs results. View Page Specific Metrics. 
 position: 1
 ---
-#Analyze Load Results#
+## Analyze Load Results
 
 Test Studio load tests can generate a large amount of data. This document contains suggestions to help you interpret this data. Keep in mind that the behavior of your application may be complex, and that each application is different. Work with the developers of your application, server administrators, and other stakeholders to gain insights specific to your environment.
 
-##Identify Key Areas of Load Data##
+## Identify Key Areas of Load Data
 
 Three sets of results data that your load test produces are usually important for the purposes of results analysis.
 
-###User Experience Metrics###
+### User Experience Metrics
 
 These data directly measure the behavior of the application from the perspective of the end user. This category includes metrics like Average Response Time, HTTP Errors/second, and Responses Received/second. These metrics are gathered by Test Studio Load Tests by default, and do not require you to profile Performance Counters.
 
-###Load Generation Metrics###
+### Load Generation Metrics
 
 These data measure the amount of traffic that your test sends to the application under test. This category includes metrics like Created Virtual Users, Current Virtual Users, and Requests Sent/second. These metrics are gathered by Test Studio Load Tests by default, and do not require you to profile Performance Counters.
 
-###Resource Use Metrics###
+### Resource Use Metrics
 
 These data measure the amount of hardware resources the application under test uses during your load test. This category includes metrics like % Processor Time, Memory Cache Faults/sec, and Avg. Disk Queue Length. These metrics are not gathered by Test Studio Load Tests by default, and require you to profile Performance Counters.
 
 Your test may measure additional metrics, but these are a good place to start your analysis.
 
-##Correlate Key Load Data##
+## Correlate Key Load Data
 
 Once you have gathered and identified the key areas of load test data, you can ask questions about how these data relate to one another. For example:
 
@@ -44,7 +44,7 @@ Once you have gathered and identified the key areas of load test data, you can a
 
 You can help identify whether your application meets its requirements or goals using the <a href="/features/testing-types/load-testing/running-tests" target="_blank">Goals</a> feature.
 
-##Identify Issues##
+## Identify Issues
 
 You can identify numerous problems by asking these questions. Most of these issues fall into one or more of the following categories.
 
@@ -56,7 +56,7 @@ You can identify numerous problems by asking these questions. Most of these issu
 
 * **Bugs**. These are issues that are not responsive to load.
 
-##Compare Key Load Data Graphically##
+## Compare Key Load Data Graphically
 
 Comparing any of the three key areas of load data to one another can help answer your questions about how these data relate to one another. Here are some common graphs to view:
 
@@ -78,7 +78,7 @@ Spikes in processor usage may be associated with increased response times for us
 
 ![Average Time to First Byte (ms) vs. Total % Processor Time][3]
 
-##View Page Specific Metrics##
+## View Page Specific Metrics
 
 To identify slow resources and the cause of HTTP errors, view the <a href="/features/testing-types/load-testing/analyzing-results" target="_blank">Page Specific Metrics</a> screen for your load results. This view helps identify which pages generated the most HTTP errors and which pages had the highest average response time.
 
@@ -92,7 +92,7 @@ To find out what kind of errors a page generated, click on the row for that URL
 
 ![Error code][5]
 
-##See Also##
+## See Also
 
 * <a href="/features/testing-types/load-testing/analyzing-results" target="_blank">Analyze Results Screen</a>
 
diff --git a/docs/knowledge-base/load-testing-kb/exported-results.md b/docs/knowledge-base/load-testing-kb/exported-results.md
index 252ae95d..8a8ffd19 100644
--- a/docs/knowledge-base/load-testing-kb/exported-results.md
+++ b/docs/knowledge-base/load-testing-kb/exported-results.md
@@ -4,7 +4,7 @@ page_title: Exported Results
 description: What exported Load results show. Overall Test Statistics. HTTP Statistics by URI. Status Codes by URI.
 position: 1
 ---
-# Understand Exported Load Results
+## Understand Exported Load Results
 
 The Test Studio Load Test <a href="/features/testing-types/load-testing/analyzing-results" target="_blank">Analysis Screen</a> displays graphical results. If you export your load test results in HTML or .XLSX format, the results appear as a table. This document contains tips on interpreting this data.
 
diff --git a/docs/knowledge-base/load-testing-kb/load-strategies.md b/docs/knowledge-base/load-testing-kb/load-strategies.md
index 8afc31ce..c7beb075 100644
--- a/docs/knowledge-base/load-testing-kb/load-strategies.md
+++ b/docs/knowledge-base/load-testing-kb/load-strategies.md
@@ -4,11 +4,11 @@ page_title: Load Strategies
 description: Choose which load strategy will suit the current requirements and adjust the Test Strudio load test accordingly. Stress Testing. Baseline Tests and High Load Tests. Soak Testing. Scalability Testing. Geographic Diversity Testing. 
 position: 1
 ---
-#Types of Load Tests#
+## Types of Load Tests
 
 There are many types of load tests, each designed to answer specific questions. Here are four common types of load test, and how to start building them in Test Studio.
 
-##Stress Testing##
+## Stress Testing
 
 A typical stress test begins with a small amount of load and slowly increase this amount throughout the test. This test type answers these questions:
 
@@ -32,11 +32,11 @@ Once the test is completed, you can identify the time in the <a href="/features/
 
 ![Performance counters][2]
 
-###Baseline Tests and High Load Tests###
+### Baseline Tests and High Load Tests
 
 Two related load test types are **baseline tests** and **high load** tests. Unlike a stress test, these tests use a continuous number of VUs. A baseline test uses a number of VUs equal to the number of users the application is required to support; a high load test uses a number of VUs greater than the requirements. These tests can answer the questions, "Does my application support the required number of users?" and "Does my application support the target number of users?" You can also answer these questions by stress testing.
 
-##Soak Testing##
+## Soak Testing
 
 Soak tests (also known as **endurance tests**) apply a constant load to the target application for an extended period of time. This test type answers these questions:
 
@@ -52,7 +52,7 @@ Users Over Time for a soak test is a flat line:
 
 The amount of load is often the expected number of users, but you may also wish to soak test your application at multiple load levels. The purpose of the soak test is to identify problems in application performance that do not occur over shorter test durations, such as memory leaks. When analyzing the soak test results, make sure to analyze the performance counters on the application server to find patterns in resource usage.
 
-##Scalability Testing##
+## Scalability Testing
 
 Scalability tests perform multiple load tests against different resource configurations. This test type tries to answer these questions:
 
@@ -68,7 +68,7 @@ Scalability tests correspond to different application and server configurations:
 
 Keep in mind that some cloud services may not expose their performance counters to our Profiler, which is included in Test Studio Runtime and Standalone installations.
 
-##Geographic Diversity Testing##
+## Geographic Diversity Testing
 
 Geographic diversity tests generate load from different locations. This test type tries to answer these questions:
 
@@ -78,7 +78,7 @@ Geographic diversity tests generate load from different locations. This test typ
 
 You can use Test Studio Load Testing to perform geographic diversity testing by installing and selecting <a href="/features/scheduling-test-runs/create-execution-server" target="_blank">Execution Servers</a> in different locations. These locations can simulate the locations of different users or user populations. You can compare the results from load tests run on a machine in one location with those run in another. Keep in mind that Test Studio Test Lists will be distributed automatically to different Execution Machines, so select one Execution Machine for each Test List in this type of test. Once you have performed this type of test, you may want to repeat the test with a different application server location to see if this improves results.
 
-##See Also##
+## See Also
 
 * <a href="/knowledge-base/load-testing-kb/selecting-traffic" target="_blank">Selecting Load Traffic</a>
 
diff --git a/docs/knowledge-base/load-testing-kb/profiling-your-app.md b/docs/knowledge-base/load-testing-kb/profiling-your-app.md
index 66363b0b..4ec15b38 100644
--- a/docs/knowledge-base/load-testing-kb/profiling-your-app.md
+++ b/docs/knowledge-base/load-testing-kb/profiling-your-app.md
@@ -4,27 +4,26 @@ page_title: Profiling Your App
 description: Profiling Your App in Test Studio load test. Identifying performance metrics to gather and analyze. Role-specific Metrics - Application Server (performance counters to measure the resource usage of different components of the application server). Database Server (performance counters to measure the behavior and resource usage of your SQL database server). Execution Server (performance counters to determine if the machine executing the load test is a bottleneck).
 position: 1
 ---
-#Profiling Your App#
 
 When you load test your application with Test Studio, the Load Testing tool automatically <a href="/features/testing-types/load-testing/analyzing-results" target="_blank">calculates metrics</a> about the HTTP traffic it receives from your application server. But some of the most important data about your application's performance comes from directly observing performance counters on the application and database servers. Test Studio's Execution Server and Standalone versions provide a Profiler for the machine where they are installed. By adding a machine to a Test Studio Load Test under <a href="/features/testing-types/load-testing/monitor-perf-metrics" target="_blank">Monitor Performance</a>, you can gather robust information about the performance of any machine in your application topology.
 
-##Identifying Metrics##
+## Identifying Metrics
 
 You may select which performance metrics to gather and analyze in a number of ways.
 
-###Requirements###
+### Requirements
 
 Project stakeholders may provide you with requirements that directly correspond to specific performance metrics. For example, the application may have a requirement that it must support over 1000 simultaneous users. This corresponds to a stress test in which the total number of virtual users surpasses 1000.
 
-###Derived metrics###
+### Derived metrics
 
 You can also derive specific metrics from your application requirements. For example, the application may have a requirement that users begin to see responses to their actions within one second on average. From this requirement, you can derive a <a href="/features/testing-types/load-testing/running-tests" target="_blank">goal</a>: "Average Time to First Byte is Less Than 1000 ms."
 
-#Role-specific Metrics#
+## Role-specific Metrics
 
 Depending on the specific role of a machine in your application topology, you can select a different set of performance counters to monitor during your load test. Because every application has its own distinct architecture, each load test may have its own set of appropriate performance counters. Talk to your developers about which performance counters are most relevant for your application. Consider these as a starting point.
 
-###Application Server###
+### Application Server
 
 Consider monitoring these performance counters to measure the resource usage of different components of the application server.
 
@@ -50,7 +49,7 @@ For .NET applications, consider monitoring these .NET performance counters:
 
 * .NET CLR Memory\ % Time in GC
 
-###Database Server###
+### Database Server
 
 Consider monitoring these performance counters to measure the behavior and resource usage of your SQL database server.
 
@@ -68,7 +67,7 @@ Consider monitoring these performance counters to measure the behavior and resou
 
 * Databases\ Active Transactions
 
-###Execution Server###
+### Execution Server
 
 Consider monitoring these performance counters to determine if your <a href="/features/scheduling-test-runs/create-scheduling-server" target="_blank">Execution Server</a> is a bottleneck in your load test.
 
@@ -80,7 +79,7 @@ Consider monitoring these performance counters to determine if your <a href="/fe
 
 * .NET CLR LocksAndThreads\ Telerik.TestStudio.RemoteExecutor \ ContentionRate /sec
 
-##See Also##
+## See Also
 
 * <a href="http://msdn.microsoft.com/en-us/library/windows/desktop/aa373083(v=vs.85).aspx" target="_blank">Performance Counters at MSDN</a>
 
diff --git a/docs/knowledge-base/load-testing-kb/selecting-traffic.md b/docs/knowledge-base/load-testing-kb/selecting-traffic.md
index 7db50517..bad4fa8b 100644
--- a/docs/knowledge-base/load-testing-kb/selecting-traffic.md
+++ b/docs/knowledge-base/load-testing-kb/selecting-traffic.md
@@ -4,30 +4,28 @@ page_title: Selecting Traffic
 description: Select the traffic in a load user profile for useful and robust load test results. 
 position: 1
 ---
-#Selecting Load Traffic##
+## Selecting Load Traffic
 
 There are many types of load tests, each with its own goals. But for most load tests, following a few general principles should provide more useful and robust load test results.
 
-##Simulate Realistic User Behavior##
+## Simulate Realistic User Behavior
 
 Once you have identified the expected ways in which users will interact with your application, you can use this information to simulate the load your application will encounter. Using <a href="/getting-started/create-test-standalone/web-test" target="_blank">Test Studio Web Tests</a>, you can record typical workflows in the browser then, you can <a href="/features/testing-types/load-testing/capturing-traffic" target="_blank">import these as Profiles</a> inside a Test Studio Load Test. Finally, you can <a href="/features/testing-types/load-testing/test-settings" target="_blank">allocate different percentages of the Workload</a> to each User Profile according to the percentage of users that you expect to perform this workflow. This way, your load test will generate traffic that accurately simulates your expected users
 
-
-##Record Cross-Browser Traffic##
+## Record Cross-Browser Traffic
 
 Different browsers generate different kinds of traffic. To simulate this variety, <a href="/features/testing-types/load-testing/capturing-traffic" target="_blank">record your load traffic in a variety of browsers</a> that reflects your specific users or the broader Internet usage. You can <a href="/features/testing-types/load-testing/capturing-traffic" target="_blank">capture your load traffic from functional tests in a variety of browsers</a>. Or, you can capture traffic in your load test directly and select the proper browsers. Once you have recorded the User Profile, you can allocate Workload based on the popularity of the browser.
 
 
-##Test Components Separately##
+## Test Components Separately
 
 In addition to testing the overall mix of user workflows, you can also create separate load tests that only focus on a specific part of your application (for example, the login workflow). This will provide information about which components suffer the greatest performance decrease under stress. This is especially useful once you have determined that your application is not meeting expectations and wish to identify the performance bottleneck. It also helps to fine-tune the performance of an application that already meets requirements.
 
-
-##Functional, Performance, and Load##
+## Functional, Performance, and Load
 
 To save time and increase accuracy, begin with functional tests (like Web Tests) to ensure your application behaves correctly; then, use these to create <a href="/features/testing-types/performance-testing/overview" target="_blank">Performance tests</a> to see the experience of a single user and find performance issues that occur without load. Finally, import your functional tests into Load tests to see the behavior of the application with large numbers of users. Repeat these tests throughout the development process to prevent regressions and identify opportunities for performance improvements.
 
-##See Also##
+## See Also
 
 * <a href="/knowledge-base/load-testing-kb/load-strategies" target="_blank">Load Testing Strategies</a>
 
diff --git a/docs/knowledge-base/load-testing-kb/think-times.md b/docs/knowledge-base/load-testing-kb/think-times.md
index 71438a0d..9f2dc161 100644
--- a/docs/knowledge-base/load-testing-kb/think-times.md
+++ b/docs/knowledge-base/load-testing-kb/think-times.md
@@ -4,11 +4,11 @@ page_title: Think Times
 description: Think times in Test Studioo Load test represents the time it takes a user to process the information received from the application and decide what to do next. It also represents other delays, like the amount of time spent filling in a form before submitting the content. Advantages if choosing the right Think Times in Test Studio load test. 
 position: 1
 ---
-#Think Times#
+## Think Times
 
 In Test Studio Load Tests, <a href="/features/testing-types/load-testing/think-times" target="_blank">Think Time</a> represents the time it takes a user to process the information received from the application and decide what to do next. It also represents other delays, like the amount of time spent filling in a form before submitting the content.
 
-## Advantages ##
+## Advantages 
 
 There are several advantages to choosing the right Think Times.
 
@@ -18,20 +18,20 @@ There are several advantages to choosing the right Think Times.
 
 **Think Times Enable the Use of Dynamic Targets**. Some Load Tests need <a href="/features/testing-types/load-testing/dynamic-targets" target="_blank">Dynamic Targets</a> to properly simulate user scenarios. Because Dynamic Targets are contained in the responses from the server, Test Studio needs to wait for the server to respond before it can extract the Dynamic Target values. Including Think Times in your Load Test helps ensure there is sufficient time after responses for Dynamic Targets to function properly.
 
-## Using Think Times ##
+## Using Think Times 
 
 Think Times are flexible, so consider how best to use them.
 
-### Vary Think Times ###
+### Vary Think Times 
 
 Because every user is different, accurate load tests need a range of Think Time values. For example, some users take longer to read or enter data into a form than others. Test Studio can automatically vary the Think Time based on a deviation time specified with the Think Time. This will more accurately replicate the length of time from when a person receives a response from your server to the time that person requests a new page.
 
-### Choose a Realistic Think Time Range ###
+### Choose a Realistic Think Time Range 
 
 A usual deviation will be anywhere from 10 to 120 seconds, depending on the specific user scenario. A good approach to determine what this range should be for any specific webpage is to study the logs of your website and determine what is the median amount of time users spend on the page and the ranges of variations from this median.
 
 
-##See Also##
+## See Also
 
 * <a href="/features/testing-types/load-testing/think-times" target="_blank">Think Times How-To article</a>
 
diff --git a/docs/knowledge-base/load-testing-kb/virtual-users.md b/docs/knowledge-base/load-testing-kb/virtual-users.md
index 1248fca8..4d89f93e 100644
--- a/docs/knowledge-base/load-testing-kb/virtual-users.md
+++ b/docs/knowledge-base/load-testing-kb/virtual-users.md
@@ -4,17 +4,17 @@ page_title: Virtual Users
 description: clarify some of the concepts behind Virtual Users in Test Studio Load Tests. Workload in Test Studio load test. How to adjust the workload of user profiles to cover the load test requirements.
 position: 1
 ---
-#Virtual Users#
+## Virtual Users
 
 This document attempts to clarify some of the concepts behind Virtual Users in Test Studio Load Tests.
 
-## Workload ##
+## Workload 
 
-### Balancing Profiles ###
+### Balancing Profiles 
 
 The Workload is the proportion that each User Profile will be used compared to all the User Profiles contained in the test. For example, if User Profile A is set to 80% while User Profile B is set to 20%, 80% of the load traffic will come from User Profile A, while 20% of the load traffic will come from User Profile B. If both user profiles are set to 20% (or any value that is the same), 50% of the load traffic will come from User Profile A and 50% of the load traffic will come from User Profile B.
 
-### Parallel versus Distributed Execution ###
+### Parallel versus Distributed Execution 
 
 As of 2013 R1, Test Lists can run in <a href="/features/scheduling-test-runs/schedule-execution" target="_blank">Parallel Execution</a> mode. If load tests are executed in this mode, each Execution Server will utilize all VUs. If a Test List is run in Distributed mode instead, a Test Studio Load Test will evenly distribute the users across all of the available Execution Server. For example, if you specify 500 users and have 5 Execution Servers, each load agent will simulate 100 users.
 
@@ -24,7 +24,7 @@ Workloads determine the percentage of the Execution Server's VUs to apply to a U
 
 ![user profile][1]
 
-### Available Users ###
+### Available Users 
 
 Here you specify how many users to simulate while running the load test. Test Studio Load Tests will always increase or decrease concurrent users at a constant rate, resulting in a straight line between the number of starting and ending concurrent users.
 
@@ -36,7 +36,7 @@ The minimum number of users for either entry is the total number of reporting te
 
 (1 * 100) / 33 = 3.03, which is then rounded up to 4. Thus the minimum number of virtual users for starting or ending is 4.
 
-## See Also ##
+## See Also 
 
 * <a href="/features/testing-types/load-testing/managing-vu" target="_blank">Managing Virtual Users</a>
 
diff --git a/docs/knowledge-base/login-issues-telerik-website.md b/docs/knowledge-base/login-issues-telerik-website.md
index 652917a7..dd910efc 100644
--- a/docs/knowledge-base/login-issues-telerik-website.md
+++ b/docs/knowledge-base/login-issues-telerik-website.md
@@ -7,16 +7,16 @@ slug: login-issues-telerik-website
 tags: progress, telerik, test studio, login, troubleshooting
 res_type: kb
 ticketid: 1661389
-position: 19
+position: 1
 ---
 
 ## Description
 
 When attempting to sign into the Telerik website errors may appear in the browser console due to the CloudFlare verification. The error in the browser is as follows: 
 
-```HTML
+````HTML
 Oops! We couldn't verify you're human. Please try a different browser or contact us for assistance. 
-```
+````
 
 ![Login error](/img/knowledge-base/telerik-login-kb/fig1.png)
 
diff --git a/docs/knowledge-base/project-configuration-kb/disconnect-from-fource-control.md b/docs/knowledge-base/project-configuration-kb/disconnect-from-fource-control.md
index 03118451..c9ef3605 100644
--- a/docs/knowledge-base/project-configuration-kb/disconnect-from-fource-control.md
+++ b/docs/knowledge-base/project-configuration-kb/disconnect-from-fource-control.md
@@ -4,11 +4,11 @@ page_title: Disconnect From Source Control
 description: How to disconnect a local project from TFS, so it is no longer source controlled.
 position: 1
 ---
-#Disconnect From Source Control#
+## Disconnect From Source Control
 
 I'd like to disconnect a local project from TFS, so it is no longer source controlled.
 
-##Solution##
+## Solution
 
 This can be done from the Project Explorer UI.
 
diff --git a/docs/knowledge-base/project-configuration-kb/generate-encryption-key.md b/docs/knowledge-base/project-configuration-kb/generate-encryption-key.md
new file mode 100644
index 00000000..cb50e279
--- /dev/null
+++ b/docs/knowledge-base/project-configuration-kb/generate-encryption-key.md
@@ -0,0 +1,162 @@
+---
+title: Generate Encryption Key
+page_title: Generate and Update Encryption Key
+description: Generate Encryption Key for Test Studio projects. Import the new key for all Test Studio installations across all involved machines. 
+position: 0
+---
+
+The **Encryption Key** is used to secure sensitive data across the Test Studio projects. You can get the current key or generate a new one in the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server" target="_blank">Scheduling Config wizard</a>. 
+
+<!-- no toc -->
+- [Manage the Encryption Key](#manage-the-encryption-key)
+  - [Default Encryption Key](#default-encryption-key)
+  - [Generate New Key](#generate-new-encryption-key)
+  - [Copy Current Key](#copy-current-key)
+- [Generate and Import Custom Encryption Key in Single Machine Setup](#generate-and-import-custom-encryption-key-in-single-machine-setup)
+- [Generate and Import Custom Encryption Key in Multiple Machines Setup](#generate-and-import-custom-encryption-key-in-multiple-machines-setup)
+- [Re-Generate the Custom Key](#re-generate-the-custom-key)
+
+## Manage the Encryption Key
+
+Find useful details on the available options to manage the Encryption key.
+
+### Default Encryption Key 
+
+The Encryption tab lets you manage the **Encryption Key** which is used to secure sensitive data across the Test Studio projects including: 
+
+- Passwords for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests; SMTP credentials if used in the Scheduling configuration;
+- Password steps recorded in automated tests when the _'Encrypt'_ step property is enabled. 
+
+![Encryption key tab](/img/features/scheduling-test-runs/create-scheduling-server/encryption-tab.png)
+
+The **Current Key** section indicates which is the key in use. Test Studio installation uses a default encryption key and you see the current key is the __Default Key Loaded__. In this configuration you can't copy or see the key. 
+
+![Default Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-default-key.png)
+
+
+### Generate New Key
+
+The **Replace Key** section lets you **Generate** a new key. Once generated, the new value is populated in the text field and is ready to be imported. Hit the **Import** button to replace the current key with the new one. 
+
+![Replace Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-generate-key.png)
+
+> **Note**
+> <br>
+> <br>
+> When __importing a custom encryption key for the first time__ some of the encrypted data becomes inaccessible. To __continue using your Test Studio projects in such case you must__: 
+> * __re-enter all passwords__ for connecting to source control repository or bug tracking systems, and SMTP settings if used in Scheduling configuration;
+> * all projects on the machine are __upgraded to use the new key__ for __password steps__ in automated tests when the _'Encrypt'_ step property is enabled and for __database connection strings used in data driven tests__ thus _no further interaction is needed_ for these.
+
+> If you decide to __regenerate the encryption key and import a new one__ all encrypted data becomes inaccessible. To __continue using your Test Studio projects in such case you must__: 
+> * __re-enter all passwords__ for connecting to source control repository or bug tracking systems, and database connection strings used in data driven tests, and SMTP settings if used in Scheduling configuration;
+> * __re-record all password steps__ in automated tests when the _'Encrypt'_ step property is enabled.
+
+
+### Copy Current Key
+
+Once a custom key is generated and imported, the **Current Key** section allows you to copy the value of the key using the __Copy to Clipboard__ button, or see it using the __Show__ button (for the cases when copying is not an option).
+
+> **Important!**
+> <br>
+> The copied key __must be imported on all machines__ where Test Studio is in use.
+
+![Custom Encryption key](/img/features/scheduling-test-runs/create-scheduling-server/encryption-custom-key.png)
+
+
+> **Note**
+> <br>
+> <br>
+> The __Encryption key is set per machine__. This means that importing a key on one machine lets all projects on the same machine to use it. If you see any troubles with the imported key on a machine, be sure to restart all Test Studio processes. 
+> <br>
+> <br>
+> The actual __Encryption key__ is kept in a file named `encryptKey.txt` which is saved in folder `C:\ProgramData\Telerik\Test Studio\Configs`. This location is accessible from all users on each local machine and we strongly recommend to ensure its security as per your company security policies. 
+
+## Generate and Import Custom Encryption Key in Single Machine Setup 
+
+Once you generate a new key, hit the **Import** button to replace the current key in use on the current machine. 
+
+In the case when you have only one machine with Test Studio, follow the below steps: 
+
+1. Open the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#start-the-test-studio-scheduling-config-wizard" target="_blank">Test Studio Services config wizard</a>. 
+2. Switch to the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#encryption-tab" target="_blank">Encryption tab</a> and generate new Encryption key. 
+3. Hit the **Import** button and wait for a while. 
+
+    ![Generate encryption Key](/img/knowledge-base/project-configuration-kb/encryption-key/encryption-generate-key.png)
+
+4. The <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Execution client application from the system tray</a> on this machine is restarted. 
+   
+    __Note!__ You may see a message that the Execution server app is closed and you need to start it manually. 
+
+    ![Restart Execution server](/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png)
+
+5. If running __restart Test Studio standalone application__ and current project in use. When restarted __the project will be upgraded__.
+6. If the __project is connected to Git source control__ <a href="/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio" target="_blank">reset the Git credentials</a>. 
+7. If the __project is connected to bug tracking system__ <a href="/features/integration/bug-tracking/configuration" target="_blank">re-enter the credentials in use</a>.
+8. If the __current machine is used as Scheduling server__ with <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#automatic-email-notification-for-scheduled-executions" target="_blank">configured SMTP settings, re-enter the credentials in use and apply the change</a>. 
+   
+    **Note!** SMTP settings are applied for the machine where the Scheduling service is in use, so you only need to change these once.
+
+9. __Password steps__ in automated tests when the _'Encrypt'_ step property is enabled are upgraded to use the new encryption key. 
+10.  __Database connection strings used in data driven tests__ are upgraded to use the new encryption key. 
+11. You can continue using the project as before.
+ 
+
+## Generate and Import Custom Encryption Key in Multiple Machines Setup 
+
+Once you generate a new key, hit the **Import** button to replace the current key in use for current machine.  
+
+In the setup where Test Studio project is used on multiple machines,  you need to __import the new key on each machine__. Follow the below steps: 
+
+1. Open the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#start-the-test-studio-scheduling-config-wizard" target="_blank">Test Studio Services config wizard</a> on the machine where the Scheduling service is. 
+2. In the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#encryption-tab" target="_blank">Encryption tab</a> generate new Encryption key. 
+3. Hit the **Import** button and wait for a while. 
+   
+    ![Generate encryption Key](/img/knowledge-base/project-configuration-kb/encryption-key/encryption-generate-key.png)
+
+4. The <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Execution client application from the system tray</a> on this machine is restarted. 
+   
+    __Note!__ You may see a message that the Execution server app is closed and you need to start it manually. 
+
+    ![Restart Execution server](/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png)
+
+5. If running __restart Test Studio standalone application__ and current project in use. When restarted __the project will be upgraded__.
+6. If the __project is connected to Git source control__ <a href="/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio" target="_blank">reset the Git credentials</a>. 
+7. If the __project is connected to bug tracking system__ <a href="/features/integration/bug-tracking/configuration" target="_blank">re-enter the credentials in use</a>.
+8. If the __current machine is used as Scheduling server__ with <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#automatic-email-notification-for-scheduled-executions" target="_blank">configured SMTP settings, re-enter the credentials in use and apply the change</a>. 
+   
+    **Note** SMTP settings are applied for the machine where the Scheduling service is in use, so you only need to change these once.
+
+9. __Password steps__ in automated tests when the _'Encrypt'_ step property is enabled are upgraded to use the new encryption key. 
+10. __Database connection strings used in data driven tests__ are upgraded to use the new encryption key. 
+11. If the current project is under source control __push the latest changes to the remote repository__. 
+12. On this same machine __copy the new key__ value from the __Current Key__ section in the Test Studio Services config wizard->Encryption tab. Be sure to __safely distribute the key as per your local security policies__.
+
+    ![Copy current Key](/img/knowledge-base/project-configuration-kb/encryption-key/copy-encryption-key.png)
+
+13. __Logon to each of the machines__ where Test Studio is in use.
+14. <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#start-the-test-studio-scheduling-config-wizard" target="_blank">Start the Test Studio Services configuration wizard</a>.
+15. Switch to the Encryption tab and use the copied key from your local machine (Step 10. in this list) to import it. Be sure to __safely distribute the key as per your local security policies__.
+    
+    ![Import new Key](/img/knowledge-base/project-configuration-kb/encryption-key/encryption-import-key.png)
+
+16. Hit the **Import** button and wait for a while.
+17. If running the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#start-the-execution-client" target="_blank">Execution client application from the system tray</a> is restarted. 
+   
+    __Note!__ You may see a message that the Execution server app is closed and you need to start it manually. 
+
+    ![Restart Execution server](/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png)
+
+18. Repeat steps 13. to 17. for all machines where Test Studio is in use. If __Test Studio application is running while importing the new key be sure to restart it__. 
+19. Continue with __getting the latest version of the project__ from the source control in use and recording/running tests. If the machine is used for test execution as part of the Test Studio Scheduling setup, you need to <a href="/automated-tests/scheduling/upload-latest-files" target="_blank">upload the latest state of project in the Storage database</a>. 
+
+## Re-Generate the Custom Key 
+
+If you decide to __re-generate the custom encryption key__ and replace it with a new one, be informed that __all encrypted data becomes inaccessible__. This means you need to also re-record all password steps across the automated tests and re-enter database connection strings used in data driven testing along with re-entering Git, bug tracking system and SMTP credentials. 
+
+You can follow the steps described for single machine setup or multiple machines configuration listed above with the only change in steps 9. and 10. as follows: 
+
+* __Password steps must be re-recorded__ in automated tests when the _'Encrypt'_ step property is used. 
+    
+    __Tip!__ You can use the option to <a href="/features/custom-steps/overview#add-step-for-a-recorded-element" target="_blank">add steps for an existing element</a> in the elements repository to re-create the step. Another possible approach is to use <a href="/automated-tests/test-execution/partial-test-execution" target="_blank">the partial test run options</a>. 
+
+* __Database connection strings used in data driven tests__ must be <a href="/features/data-driven-testing/add-data-source#add-a-database-source" target="_blank">re-entered</a>.
diff --git a/docs/knowledge-base/project-configuration-kb/multiple-projects.md b/docs/knowledge-base/project-configuration-kb/multiple-projects.md
index a94d6781..e659ff48 100644
--- a/docs/knowledge-base/project-configuration-kb/multiple-projects.md
+++ b/docs/knowledge-base/project-configuration-kb/multiple-projects.md
@@ -4,20 +4,20 @@ page_title: Multiple Projects
 description: Reusing tests and Helper methods across multiple projects. When multiple projects use the same or similar resources, you may wish to share or integrate these project resources. Here we address four scenarios - Sharing helper methods (standalone code file) between projects, sharing data sources between projects, and importing tests from other projects.
 position: 1
 ---
-#Multiple Projects#
+## Multiple Projects
 
 When multiple projects use the same or similar resources, you may wish to share or integrate these project resources. Here we address four scenarios: Sharing helper methods between projects, sharing data sources between projects, and importing tests from other projects.
 
-##Sharing Helper Methods Between Projects##
+## Sharing Helper Methods Between Projects
 
 If your projects use common methods, you may wish to place them in a custom DLL. You can then add references to this utility class in your different projects in <a href="/advanced-topics/coded-samples/general/utility-class-in-standalone" target="_blank">Standalone Test Studio</a> or the <a href="/advanced-topics/coded-samples/general/use-external-dll-in-vs" target="_blank">Visual Studio Plugin</a>.
 
-##Sharing Data Sources Between Projects##
+## Sharing Data Sources Between Projects
 
 Generally, <a href="/features/data-driven-testing/bind-test-data-source" target="_blank">data sources</a> must be in the same project folder as the tests bound to them. Test Studio creates a copy of the target data source for this purpose, so that after data binding, changes to the original data source do not automatically affect the data source for the test. 
 
 A <a href="/features/data-driven-testing/sql-database-example" target="_blank">SQL database</a>, however, behaves differently: any test configured to connect to a SQL database as a data source will retrieve up-to-date data from that database. So, any number of projects can data bind to the same SQL database and access the same data.
 
-##Importing Tests from Another Project##
+## Importing Tests from Another Project
 
 All Test Studio projects are file-based. To import tests from one project to another, you can copy the test files (.tstest) from those projects into the target project. Next, manually <a href="/troubleshooting-guide/test-execution-problems-tg/pages-not-defined" target="_blank">update the namespace</a> for any copied code-behind files. Test Studio will automatically detect this new test on restart or Project view refresh. 
\ No newline at end of file
diff --git a/docs/knowledge-base/project-configuration-kb/register-certificate.md b/docs/knowledge-base/project-configuration-kb/register-certificate.md
index 4fae85df..737b1e59 100644
--- a/docs/knowledge-base/project-configuration-kb/register-certificate.md
+++ b/docs/knowledge-base/project-configuration-kb/register-certificate.md
@@ -4,7 +4,7 @@ page_title: Register Certificate
 description: "Register Certificate for HTTPS Connection. I encounter certificate-related warnings when the Test Studio recorder or runner is attached to the browser. Load Test cannot navigate to the desired page due to security warning certificate error"
 position: 1
 ---
-# Register Certificate for HTTPS Connection
+## Register Certificate for HTTPS Connection
 
 When running performance and load tests, you might encounter warnings for the website's security certificate against https pages.
 
@@ -46,9 +46,9 @@ Without a full version of Test Studio installed, there is no GUI to register the
 
 Open a command prompt and change the working directory to the Test Studio installation folder `C:\Program Files (x86)\Progress\Test Studio\Bin`. Then enter the following command:
 
-```
+````
 ArtOfTest.WebAii.HttpProxy.exe InstallCertificate
-```
+````
 
  
 
diff --git a/docs/knowledge-base/scheduling-kb/configure-reverse-proxy.md b/docs/knowledge-base/scheduling-kb/configure-reverse-proxy.md
index 46dc0ec8..1a5821d4 100644
--- a/docs/knowledge-base/scheduling-kb/configure-reverse-proxy.md
+++ b/docs/knowledge-base/scheduling-kb/configure-reverse-proxy.md
@@ -4,7 +4,7 @@ page_title: Example Configuration for Reverse Proxy Server
 description: Example Configuration for Reverse Proxy Server to use for connecting to the Test Studio Scheduling setup. 
 position: 2
 ---
-# Reverse Proxy Server
+## Reverse Proxy Server
 
 Test Studio Standalone application allows connection to Scheduling setup configured behind a pre-configured reverse proxy using client and server certificates. The reverse proxy have to use TLS and to have client certificate authentication enabled.
 
@@ -26,12 +26,12 @@ An alternative is to use your own trusted certificates.
 Use the following commands to issue the Custom Authority certificate: 
 
 1. Enter the following command in the console: 
-```openssl genrsa -aes256 -out ts-CA-key.pem -passout pass:"1234" 2048```
+````openssl genrsa -aes256 -out ts-CA-key.pem -passout pass:"1234" 2048```
 
 where you need to replace _1234_ with a suitable password. 
 
 2. Enter the following command in the console: 
-```openssl req -passin pass:"1234" -x509 -sha256 -new -nodes -key ts-CA-key.pem -days 3650 -out ts-CA-cert.pem```
+````openssl req -passin pass:"1234" -x509 -sha256 -new -nodes -key ts-CA-key.pem -days 3650 -out ts-CA-cert.pem```
 
 where you need to add the information for which you get prompted. This includes `Common Name` and for the purpose of this example we use __Test Studio CA__ as Common Name
 
@@ -40,75 +40,75 @@ where you need to add the information for which you get prompted. This includes
 Follow the steps below:
 
 1. Enter the following command in the console: 
-```openssl genrsa -aes256 -out ts-server.key -passout pass:"1234" 2048```
+````openssl genrsa -aes256 -out ts-server.key -passout pass:"1234" 2048```
 
 where you need to replace _1234_ with a suitable password.
 
 2. Enter the following command in the console: 
-```openssl req -passin pass:"1234" -new -key ts-server.key -out ts-server.csr```
+````openssl req -passin pass:"1234" -new -key ts-server.key -out ts-server.csr```
 
 where you need add the information for which you get prompted. This includes `Common Name` and we recommend using the proxy machine domain name. For the purpose of this example we use __ProxyMachineName__ as Common Name.
 
 3. Create a _ts-server.ext_ file with the following content:
 
-	```
-	authorityKeyIdentifier=keyid,issuer
-	basicConstraints=CA:FALSE
-	keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
-	subjectAltName = @alt_names
+````
+authorityKeyIdentifier=keyid,issuer
+basicConstraints=CA:FALSE
+keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
+subjectAltName = @alt_names
 
-	[alt_names]
-	DNS.0 = ProxyMachineName
-	DNS.1 = ProxyMachineName.companyDomain.com
-	IP.0 = xxx.xxx.xx.x
-	```
+[alt_names]
+DNS.0 = ProxyMachineName
+DNS.1 = ProxyMachineName.companyDomain.com
+IP.0 = xxx.xxx.xx.x
+````
 
 	where DNS.0 and DNS.1 hold the machine host name and the full qualified domain name for the machine which hosts the proxy server. IP.0 is the IP address of the proxy server machine in the network from which it will be accessed remotely. 
 
 4. Enter the following command in the console:
-```openssl x509 -passin pass:"1234" -req -in ts-server.csr -CA ts-CA-cert.pem -CAkey ts-CA-key.pem -CAcreateserial -out ts-server.crt -days 1825 -sha256 -extfile ts-server.ext```
+````openssl x509 -passin pass:"1234" -req -in ts-server.csr -CA ts-CA-cert.pem -CAkey ts-CA-key.pem -CAcreateserial -out ts-server.crt -days 1825 -sha256 -extfile ts-server.ext````
 
 5. Create a _ts-server.pass_ file which contains the pass phrase for _ts-server.key_. This is _1234_ for this example. 
 
 ### Create Client Certificate
 
 1. Enter the following command in the console: 
-```openssl genrsa -aes256 -out ts-client.key -passout pass:"1234" 2048```
+````openssl genrsa -aes256 -out ts-client.key -passout pass:"1234" 2048````
 
 where you need to replace _1234_ with a suitable password.
 
 2. Enter the following command in the console: 
-```openssl req -passin pass:"1234" -new -key ts-client.key -out ts-client.csr```
+````openssl req -passin pass:"1234" -new -key ts-client.key -out ts-client.csr````
 
 where you need add the information for which you get prompted. This includes `Common Name` and we recommend using the machine domain name. For the purpose of this example we use __ProxyMachineName__ as Common Name.
 
 3. Create a _ts-client.ext_ file with the following content: 
 
-	```
-	authorityKeyIdentifier=keyid,issuer
-	subjectKeyIdentifier = hash
-	basicConstraints=CA:FALSE
-	nsCertType = client, email
-	nsComment = "Test Studio Client Certificate"
-	keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
-	extendedKeyUsage = clientAuth, emailProtection
-	subjectAltName = @alt_names
-
-	[alt_names]
-	DNS.0 = ProxyMachineName
-	DNS.1 = ProxyMachineName.companyDomain.com
-	IP.0 = xxx.xxx.xx.x
-	```
+````
+authorityKeyIdentifier=keyid,issuer
+subjectKeyIdentifier = hash
+basicConstraints=CA:FALSE
+nsCertType = client, email
+nsComment = "Test Studio Client Certificate"
+keyUsage = digitalSignature, nonRepudiation, keyEncipherment, dataEncipherment
+extendedKeyUsage = clientAuth, emailProtection
+subjectAltName = @alt_names
+
+[alt_names]
+DNS.0 = ProxyMachineName
+DNS.1 = ProxyMachineName.companyDomain.com
+IP.0 = xxx.xxx.xx.x
+````
 where DNS.0 and DNS.1 hold the machine host name and the full qualified domain name for the machine which hosts the proxy server. IP.0 is the IP address of the proxy server machine in the network from which it will be accessed remotely. 
 
 4. Enter the following command in the console: 
-```openssl x509 -passin pass:"1234" -req -in ts-client.csr -CA ts-CA-cert.pem -CAkey ts-CA-key.pem -CAcreateserial -out ts-client.crt -days 1825 -sha256 -extfile ts-client.ext```
+````openssl x509 -passin pass:"1234" -req -in ts-client.csr -CA ts-CA-cert.pem -CAkey ts-CA-key.pem -CAcreateserial -out ts-client.crt -days 1825 -sha256 -extfile ts-client.ext````
 
 5. Enter the following command in the console: 
-```cat ts-client.key ts-client.crt ts-CA-cert.pem > ts-client.pem```
+````cat ts-client.key ts-client.crt ts-CA-cert.pem > ts-client.pem```
 
-6. Enter the following command in the console: 
-```openssl pkcs12 -passin pass:"1234" -export -out ts-client.pfx -inkey ts-client.key -in ts-client.pem -certfile ts-CA-cert.pem -passout pass:"1234"```
+6. Enter the following command in the console: `
+````openssl pkcs12 -passin pass:"1234" -export -out ts-client.pfx -inkey ts-client.key -in ts-client.pem -certfile ts-CA-cert.pem -passout pass:"1234"````
 
 where you need to replace _1234_ with a suitable password.
 
@@ -128,96 +128,96 @@ For this example we use nginx for Windows. As an alternative you can use any typ
 
 2. Configure nginx by changing the contents of the nginx.conf file located in the conf folder. Be sure to __replace "c:/ts-certs/" with the folder where your CA and Server certificates are located__.
 
-	```
-	#user  nobody;
-	worker_processes  1;
+````
+#user  nobody;
+worker_processes  1;
 
-	pid        logs/nginx.pid;
+pid        logs/nginx.pid;
 
-	events {
-		worker_connections  1024;
-	}
+events {
+	worker_connections  1024;
+}
 
-	http {
-		include       mime.types;
-		default_type  application/octet-stream;
+http {
+	include       mime.types;
+	default_type  application/octet-stream;
 
-		# Enable large body size due to application specifics
-		client_max_body_size 0;
+	# Enable large body size due to application specifics
+	client_max_body_size 0;
 
-		keepalive_timeout  65;
+	keepalive_timeout  65;
 
-		# Add server certificate to enable TLS
-		# Replace the folder location with the one where you store the certificates
-		ssl_certificate      c:/ts-certs/Server/ts-server.crt;
-		ssl_certificate_key  c:/ts-certs/Server/ts-server.key;
-		ssl_password_file	c:/ts-certs/Server/ts-server.pass;
+	# Add server certificate to enable TLS
+	# Replace the folder location with the one where you store the certificates
+	ssl_certificate      c:/ts-certs/Server/ts-server.crt;
+	ssl_certificate_key  c:/ts-certs/Server/ts-server.key;
+	ssl_password_file	c:/ts-certs/Server/ts-server.pass;
 
-		# Enable client certificate verification and specify the CA certificate used to issue the client certificate 
-		# Replace the folder location with the one where you store the certificates
-		ssl_verify_client on;	
-		ssl_client_certificate c:/ts-certs/CA/ts-CA-cert.pem;
+	# Enable client certificate verification and specify the CA certificate used to issue the client certificate 
+	# Replace the folder location with the one where you store the certificates
+	ssl_verify_client on;	
+	ssl_client_certificate c:/ts-certs/CA/ts-CA-cert.pem;
 
-		# HTTPS server
-		# Ensure to keep the headers exactly as listed in the example below
-		server {
-			listen       9009 ssl default_server;
-			server_name  localhost;
+	# HTTPS server
+	# Ensure to keep the headers exactly as listed in the example below
+	server {
+		listen       9009 ssl default_server;
+		server_name  localhost;
 
-			#ssl_session_cache    shared:SSL:1m;
-			#ssl_session_timeout  5m;
+		#ssl_session_cache    shared:SSL:1m;
+		#ssl_session_timeout  5m;
 
-			ssl_ciphers  HIGH:!aNULL:!MD5;
-			ssl_prefer_server_ciphers  on;
-			
-			# Proxy calls to Test Studio Scheduling service
-			# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
-			# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
-
-			location / {
-				proxy_pass http://localhost:8009;
-				proxy_pass_request_headers      on;
-				proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;	
-			}
-			
-			# Proxy calls to Test Studio Storage service
-			# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
-			# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
-
-			location /v1 {
-				proxy_pass http://localhost:8492;
-				proxy_pass_request_headers      on;
-				proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;
-			}
-			
-			# Proxy calls to Test Studio Executive Dashboard service
-			# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
-			# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
-			# Executive Dashboard can be then accessed on address https://proxyMachineName:9009/ed
-
-			location /ed/ {
-				proxy_pass http://localhost:8085/;
-				proxy_pass_request_headers      on;
-				
-				sub_filter_types application/javascript;
-				sub_filter 'href="/'  'href="/ed/';
-				sub_filter 'src="/'  'src="/ed/';
-				sub_filter '/assets/'  '/ed/assets/';
-				sub_filter '+"/api"'  '+"/ed/api"';
-				sub_filter_once off;
-			}
+		ssl_ciphers  HIGH:!aNULL:!MD5;
+		ssl_prefer_server_ciphers  on;
+		
+		# Proxy calls to Test Studio Scheduling service
+		# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
+		# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
+
+		location / {
+			proxy_pass http://localhost:8009;
+			proxy_pass_request_headers      on;
+			proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;	
+		}
+		
+		# Proxy calls to Test Studio Storage service
+		# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
+		# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
+
+		location /v1 {
+			proxy_pass http://localhost:8492;
+			proxy_pass_request_headers      on;
+			proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;
+		}
+		
+		# Proxy calls to Test Studio Executive Dashboard service
+		# This configuration is meant for the setup when Scheduling service and Proxy server are on the same machine
+		# If the proxy server is separate machine, replace localhost with the Scheduling machine host name
+		# Executive Dashboard can be then accessed on address https://proxyMachineName:9009/ed
+
+		location /ed/ {
+			proxy_pass http://localhost:8085/;
+			proxy_pass_request_headers      on;
 			
-			# Proxy call to test studio runner. Important this endpoint should use this convention /runner/{machineName}
-			# Substitute {machineName} with the name of the machine where the runner is located
-			#  All Execution machines need to be listed as below with their host names
-
-			location /runner/{machineName}/ {
-				proxy_pass http://localhost:55555/;
-				proxy_pass_request_headers      on;
-				proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;
-			}
+			sub_filter_types application/javascript;
+			sub_filter 'href="/'  'href="/ed/';
+			sub_filter 'src="/'  'src="/ed/';
+			sub_filter '/assets/'  '/ed/assets/';
+			sub_filter '+"/api"'  '+"/ed/api"';
+			sub_filter_once off;
+		}
+		
+		# Proxy call to test studio runner. Important this endpoint should use this convention /runner/{machineName}
+		# Substitute {machineName} with the name of the machine where the runner is located
+		#  All Execution machines need to be listed as below with their host names
+
+		location /runner/{machineName}/ {
+			proxy_pass http://localhost:55555/;
+			proxy_pass_request_headers      on;
+			proxy_set_header TS-Original-Request-Uri $scheme://$host:$server_port$request_uri;
 		}
 	}
-	```
+}
+````
 
 3. Start nginx by navigating to its folder in cmd window and run __"start nginx"__. You can reload the server via __"nginx -s reload"__ or stop it with __"nginx -s quit"__.
\ No newline at end of file
diff --git a/docs/knowledge-base/scheduling-kb/drop-storage-database.md b/docs/knowledge-base/scheduling-kb/drop-storage-database.md
index bb35b5b6..cfbf813a 100644
--- a/docs/knowledge-base/scheduling-kb/drop-storage-database.md
+++ b/docs/knowledge-base/scheduling-kb/drop-storage-database.md
@@ -4,13 +4,15 @@ page_title: Drop The Storage Database
 description: Drop The Storage Database. The Telerik Storage Database cannot be accessed. Telerik Storage database gets corrupted. This can lead to execution of outdated test lists or even inability to execute a test list. Unable to find test file.  
 position: 9
 ---
-# Drop The Storage Database
+## Drop The Storage Database
 
 In certain situations the storage database can get corrupted and cannot be updated with the latest changes of your test lists. This can lead to execution of outdated test lists or even inability to execute a test list due to missing test files. 
 
 In such cases you need to drop the MongoDB database, which will force Test Studio to newly upload the project files to the storage for the next scheduled job.
 
-> Dropping the whole MongoDB database will delete the results of any previous scheduled test list executions. If the already existing results are still necessary, you can drop only single collections.
+> __Important!__
+> <br> 
+> Dropping the whole MongoDB database deletes the results of any previous scheduled test list executions. __If the already existing results are still necessary, you can drop only single collections__ as suggested below.
 
 ## Install the MongoDB Compass Tool
 
diff --git a/docs/knowledge-base/scheduling-kb/extract-results-from-mongodb.md b/docs/knowledge-base/scheduling-kb/extract-results-from-mongodb.md
index c8c10b3d..ebd126a6 100644
--- a/docs/knowledge-base/scheduling-kb/extract-results-from-mongodb.md
+++ b/docs/knowledge-base/scheduling-kb/extract-results-from-mongodb.md
@@ -4,7 +4,7 @@ page_title: Extract run results from MongoDB
 description: Extract run results from Storage database MongoDB
 position: 9
 ---
-# Extract run results from MongoDB
+## Extract run results from MongoDB
 
 ## Data Overview
 
diff --git a/docs/knowledge-base/scheduling-kb/generate-communication-key.md b/docs/knowledge-base/scheduling-kb/generate-communication-key.md
index cda1959d..608413cf 100644
--- a/docs/knowledge-base/scheduling-kb/generate-communication-key.md
+++ b/docs/knowledge-base/scheduling-kb/generate-communication-key.md
@@ -4,10 +4,18 @@ page_title: Generate and Update Communication Key
 description: Generate Communication Key for the Test Studio Scheduling configuration. Import the new key for all Test Studio components across all involved machines. 
 position: 1
 ---
-# Generate New Communication Key 
+## Generate New Communication Key 
 
 The **Communication Key** is required by all Test Studio Scheduling components - services and clients, to establish the connection and communicate between each other. You can get the current key or generate a new one in the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server" target="_blank">Scheduling Config wizard</a>. 
 
+<!-- no toc -->
+- [Manage the Communication Key](#manage-the-communication-key)
+  - [Default Communication Key](#default-communication-key)
+  - [Generate New Key](#generate-new-key)
+  - [Copy Current Key](#copy-current-key)
+- [Generate and Import Key in Single Machine Scheduling Setup](#generate-and-import-key-in-single-machine-scheduling-setup)
+- [Generate and Import Key in Multiple Machines Scheduling Setup](#generate-and-import-key-in-multiple-machines-scheduling-setup)
+
 ## Manage the Communication Key
 
 Find useful details on the available options to manage the Communication key value.
@@ -16,18 +24,18 @@ Find useful details on the available options to manage the Communication key val
 
 The **Communication** tab in the Scheduling Config wizard lets you manage the current key in use or generate and import a new one. 
 
-![Communication key tab](/img/features//scheduling-test-runs/create-scheduling-server/communication-tab.png)
+![Communication key tab](/img/features/scheduling-test-runs/create-scheduling-server/communication-tab.png)
 
 The **Current Key** section indicates which is the key in use. The Scheduling setup is configured to use a default communication key for each Test Studio installation. Thus, after initial install you see the current key is the __Default Key Loaded__. In this configuration you can't copy or see the key. 
 
-![Default Communication key](/img/features//scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png)
+![Default Communication key](/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-default-key.png)
 
 
 ### Generate New Key
 
 The **Replace Key** section lets you **Generate** a new key. Once generated, the new value is populated in the text field and is ready to be imported. Hit the **Import** button to replace the current key with the new one. 
 
-![Replace Communication key](/img/features//scheduling-test-runs/create-scheduling-server/communication-tab-replace-key.png)
+![Replace Communication key](/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-replace-key.png)
 
 > **Note**
 > <br>
@@ -43,14 +51,17 @@ The **Replace Key** section lets you **Generate** a new key. Once generated, the
 
 Once a custom key is generated and imported, the **Current Key** section allows you to copy the value of the key using the __Copy to Clipboard__ button, or see it using the __Show__ button (for the cases when copying is not an option). The key value can be reset to the default value using the __Reset to Default__ button.
 
-![Custom Communication key](/img/features//scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png)
+> **Important!**
+> <br>
+> The copied key __must be imported on all machines__ included in the Test Studio Scheduling setup.
+
+![Custom Communication key](/img/features/scheduling-test-runs/create-scheduling-server/communication-tab-custom-key.png)
 
-The copied key must be imported on all machines included in the Test Studio Scheduling setup.
 
 > **Note**
 > <br>
 > <br>
-> The communication key is set per machine. This means that importing a key on one machine lets all other components on the same machine to use it. If you see any troubles with the imported key on a machine, be sure to restart all Test Studio processes. 
+> The __communication key is set per machine__. This means that importing a key on one machine lets all other components on the same machine to use it. If you see any troubles with the imported key on a machine, be sure to restart all Test Studio processes. 
 
 ## Generate and Import Key in Single Machine Scheduling Setup 
 
@@ -93,13 +104,13 @@ In the setup where all components of the Scheduling configuration are on differe
 
     ![Restart Execution server](/img/knowledge-base/scheduling-kb/communication-key/restart-exec-server.png)
 
-6. On this same machine copy the new key value from the __Current Key__ section in the Scheduling config wizard->Communication tab. 
+6. On this same machine __copy the new key__ value from the __Current Key__ section in the Scheduling config wizard->Communication tab. Be sure to __safely distribute the key as per your local security policies__.
 
     ![Copy current Key](/img/knowledge-base/scheduling-kb/communication-key/copy-current-key.png)
 
 7. Logon to each of the machine utilized as Execution servers in the Scheduling setup.
 8. <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#start-the-test-studio-scheduling-config-wizard" target="_blank">Start the Test Studio Services configuration wizard</a>.
-9. Switch to the Communication tab and use the copied key from the Scheduling machine (Step 6. in this list) to import it. 
+9. Switch to the Communication tab and use the copied key from the Scheduling machine (Step 6. in this list) to import it. Be sure to __safely distribute the key as per your local security policies__.
     
     ![Import new Key](/img/knowledge-base/scheduling-kb/communication-key/replace-key.png)
 
diff --git a/docs/knowledge-base/scheduling-kb/gmail-results.md b/docs/knowledge-base/scheduling-kb/gmail-results.md
index 15c538dd..4b0b3229 100644
--- a/docs/knowledge-base/scheduling-kb/gmail-results.md
+++ b/docs/knowledge-base/scheduling-kb/gmail-results.md
@@ -4,7 +4,7 @@ page_title: Results Through Gmail
 description: Use Gmail SMTP Server to Send Result Email for Scheduled Test List Execution
 position: 9
 ---
-# Use Gmail SMTP Server to Send Result Email for Scheduled Test List Execution 
+## Use Gmail SMTP Server to Send Result Email for Scheduled Test List Execution 
 
 Test Studio's Scheduling service allows sending an email with the results from scheduled test list runs. To enable the feature you need an available SMTP server and the necessary settings to access it from within Test Studio. 
 
diff --git a/docs/knowledge-base/scheduling-kb/locked-machine.md b/docs/knowledge-base/scheduling-kb/locked-machine.md
index 76acb36a..28af28e9 100644
--- a/docs/knowledge-base/scheduling-kb/locked-machine.md
+++ b/docs/knowledge-base/scheduling-kb/locked-machine.md
@@ -5,23 +5,23 @@ description: "Test Script Execution on Locked Machine. Test Studio test run with
 previous_url: /user-guide/knowledge-base/test-execution/no-tests-execute-on-locked-machine.aspx, /user-guide/knowledge-base/test-execution/no-tests-execute-on-locked-machine
 position: 3
 ---
-# No Tests Execute on Locked Machine
+## No Tests Execute on Locked Machine
 
 ## Problem 
 
 When I disconnect from and/or lock the machine that acts as my <a href="/features/scheduling-test-runs/create-execution-server" target="_blank">Execution Server</a>, no scheduled tests are executed. This includes Remote Desktop Sessions that are minimized or closed. The following error may appear for tests with dialog handling steps or type and click steps, which are using `SimulateRealTyping` or `SimulateRealClick` properties enabled: 
 
-```
+````
 UnsupportedNonInteractiveOperationException(additional information about the exception)
-```
+````
 
 or 
 
-```
+````
 SendInput: Failed. Win32Error:
 InnerException:
 System.ComponentModel.Win32Exception (0x80004005): SendInput: Failed. Win32Error:
-```
+````
 
 Is it possible for tests to execute normally without requiring my account to always be logged in on that machine?
 
@@ -29,7 +29,7 @@ Is it possible for tests to execute normally without requiring my account to alw
 
 Any test that requires **moving the mouse** or sending **key strokes** requires access to the GUI session - e.g dialog handling uses both the mouse and keyboard typing. Telerik tests are not the only affected by this Windows limitation, you will find this is a general problem with any tool that performs UI testing.
 
-## Minimum Requirements for a Test Studio Execution Machine ###
+## Minimum Requirements for a Test Studio Execution Machine 
 
 Ensure all the following conditions are met for the server on which the tests will be executed:
 
diff --git a/docs/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0.md b/docs/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0.md
index 8dfae411..7613d63b 100644
--- a/docs/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0.md
+++ b/docs/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0.md
@@ -4,7 +4,7 @@ page_title: Upgrade Existing MongoDB to Version 4.0
 description: Upgrade an existing MongoDB version lower than 3.6 to MongoDB version 4.0 or higher. Problems with starting MongoDB service. Not able to use Test Studio Scheduling feature. MongoDB service unable to start. 
 position: 10
 ---
-# Upgrade Existing MongoDB to Version 4.0
+## Upgrade Existing MongoDB to Version 4.0
 
 MongoDB is a third party database used by Test Studio to store the project data required for scheduling tests on remote machines. We strive to keep this working out of the box, though there are upgrades of the Mongo, which affect the database used by Test Studio.
 
@@ -22,9 +22,9 @@ What we found working quite well for us is to back up your existing database and
 
 Start a Command Prompt as Administrator and change the directory to the bin/ folder in the 3.x  MongoDB installation directory. Run the following command:
 
-```
+````
 mongodump --db TSStorageData
-```
+````
 
 The result is a dump/ folder where the command is run, which contains the dump of the TSStorageData database.
 
@@ -38,9 +38,9 @@ Open the Windows services and manually stop the MongoDB service.
 
 Start a Command Prompt as Administrator and type the following command:
  
-```
+````
 sc delete MongoDB
-```
+````
 
 ![Delete Service][2]
 
@@ -64,9 +64,9 @@ The MongoDB service can now be started. The most convenient way to start it is t
 
 Once the installation of MongoDB 4.x is finished and the service is running, you can restore the - database. Copy the *dump* folder, created in point 1., from the MongoDB 3.x *bin* folder to the *bin* in installation folder of the 4.x MongoDB server. Start a Command Prompt as Administrator and change the directory to the *bin* folder under the 4.x MongoDB installation, run the following command:
 
-```
+````
 Mongorestore dump/
-```
+````
 
 [1]: /img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig1.png
 [2]: /img/knowledge-base/scheduling-kb/upgrade-to-mongo-4-0/fig2.png
diff --git a/docs/knowledge-base/scheduling-kb/virtual-machine-ui-tests-fail-without-active-session.md b/docs/knowledge-base/scheduling-kb/virtual-machine-ui-tests-fail-without-active-session.md
new file mode 100644
index 00000000..662028aa
--- /dev/null
+++ b/docs/knowledge-base/scheduling-kb/virtual-machine-ui-tests-fail-without-active-session.md
@@ -0,0 +1,36 @@
+---
+title: UI Testing on Virtual Machines Fails Without Active User Session
+description: Resolving issues with Telerik Test Studio UI testing in virtual machines when no active user session exists.
+type: troubleshooting
+page_title: Virtual Machine UI Tests Fail Without Active Session in Telerik Test Studio
+meta_title: Virtual Machine UI Tests Fail Without Active Session in Telerik Test Studio
+slug: virtual-machine-ui-tests-fail-without-active-session
+tags: telerik test studio, ui testing, virtual machine, vgpu, session monitor
+res_type: kb
+ticketid: 1698547
+---
+
+## Description
+
+I run UI test scripts in a virtual machine using vGPU with Telerik Test Studio. These scripts are triggered by a pipeline, and no user interacts with the virtual machine during execution. However, the __tests fail to detect or interact with elements__ like login fields, despite the application launching successfully. When I establish an RDP connection to the virtual machine, the tests execute correctly.
+
+## Cause
+
+__UI functional testing requires an active user session__ to interact with UI elements effectively. When the virtual machine lacks an active session, the tests fail to interact with the application as expected. Establishing an RDP session temporarily resolves the issue because it restores the active console session.
+
+## Solution
+
+To ensure UI test execution without requiring a continuous RDP session, use the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#user-session-configuration" target="_blank">Test Studio Session Monitor application</a>. This tool maintains an active user session by reconnecting the console session after the RDP connection closes.
+
+## Steps to Resolve the Misbehavior
+
+1. Ensure the Test Studio Session Monitor is installed and enabled on the virtual machine.
+2. Leave the Session Monitor application running on the virtual machine.
+3. Disconnect the RDP session safely, knowing that the console session will be restored by the Session Monitor.
+4. Trigger the test scripts from the pipeline. The tests should execute successfully as the active session is maintained.
+
+If the Session Monitor has been enabled but the issue persists, consider alternative remote desktop software that ensures the virtual machine maintains an active session during pipeline-triggered executions.
+
+## See Also
+- [User Session Configuration for Execution Server](https://docs.telerik.com/teststudio/automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server#user-session-configuration) 
+- [Test Studio Execution Servers Overview](https://docs.telerik.com/teststudio/automated-tests/scheduling/multiple-machines-scheduling-setup) 
diff --git a/docs/knowledge-base/test-automation-kb/ample-timetouts.md b/docs/knowledge-base/test-automation-kb/ample-timetouts.md
index 3ecb336d..0952a16e 100644
--- a/docs/knowledge-base/test-automation-kb/ample-timetouts.md
+++ b/docs/knowledge-base/test-automation-kb/ample-timetouts.md
@@ -4,7 +4,7 @@ page_title: Ample Timetouts
 description: Randomly failing tests. I have recorded few tests and each time I run these, they fail at different step. 
 position: 1
 ---
-# Setting Ample Timeouts in Test 
+## Setting Ample Timeouts in Test 
 
 Random failures in test or test list runs are often caused by the lack of synchronization between the speed of executing the action steps and the application responsiveness during the execution. 
 
diff --git a/docs/knowledge-base/test-automation-kb/dynamic-ids.md b/docs/knowledge-base/test-automation-kb/dynamic-ids.md
index 8c5a7e65..c7e18d26 100644
--- a/docs/knowledge-base/test-automation-kb/dynamic-ids.md
+++ b/docs/knowledge-base/test-automation-kb/dynamic-ids.md
@@ -5,7 +5,7 @@ description: Web site or application generates ID attributes for its elements dy
 previous_url: /user-guide/knowledge-base/test-automation/dynamically-generated-id-attributes.aspx
 position: 1
 ---
-# Working Around Dynamically Generated ID Attributes
+## Working Around Dynamically Generated ID Attributes
 
 *Your web site or application generates ID attributes for its elements dynamically. This causes your tests to fail because once the ID attribute for a given element changes, it can no longer be identified.*
 
@@ -15,12 +15,16 @@ We recommend that you consider changing your application in order to make it use
 
 1. Open the Project Settings menu:
 
-	<table id="no-table">
+	<table id="no-table" style="border:none;">
+	<tr style="text-align: center; background-color: transparent; border:none;">
+	<td>
+	
+    ![Standalone][1]<br>**Standalone version**</td>
+	<td>
+	
+	![VS Plugin][2]<br>**VS Plugin**</td>
 	<tr>
-	<td>![Standalone][1]<br>**Standalone version**</td>
-	<td>![VS Plugin][2]<br>**VS Plugin**</td>
-	<tr>
-	<table>
+	</table>
 
 2. Go to **Find Logic** from the navigation bar on the left:
 
diff --git a/docs/knowledge-base/test-automation-kb/fail-test-programmatically.md b/docs/knowledge-base/test-automation-kb/fail-test-programmatically.md
index 46da4bee..3e9b5ef2 100644
--- a/docs/knowledge-base/test-automation-kb/fail-test-programmatically.md
+++ b/docs/knowledge-base/test-automation-kb/fail-test-programmatically.md
@@ -4,7 +4,7 @@ page_title: Fail test step or mark the entire test result as failed
 description: Even if all test steps are successful, you might need to fail one step or the entire test at the end of the execution. You can do that programmatically in OnAfterTestCompleted method.
 position: 1
 ---
-# Fail Step or Test Programatically
+## Fail Step or Test Programatically
 
 ## PROBLEM
 
@@ -20,7 +20,7 @@ You can change the result from specific step or the entire test programmatically
 
 3.&nbsp; Find a specific condition, which will be used to evaluate the state of the application and whether the step or test should be marked as failed.
 
-```C#
+````C#
 namespace DemoProj
 {
 
@@ -49,4 +49,4 @@ namespace DemoProj
         }
     }   
 }
-```
+````
diff --git a/docs/knowledge-base/test-automation-kb/get-set-position-radslider-wpf.md b/docs/knowledge-base/test-automation-kb/get-set-position-radslider-wpf.md
index b5e12198..848773f8 100644
--- a/docs/knowledge-base/test-automation-kb/get-set-position-radslider-wpf.md
+++ b/docs/knowledge-base/test-automation-kb/get-set-position-radslider-wpf.md
@@ -16,38 +16,38 @@ In the case when there is no explicitly defined slider thumb, you can use the Va
 
 Let's say that in the application under test there is a slider defined like this:
 
-```XAML
+````xml
 <telerik:RadSlider Name="MySlider" Minimum="0" Maximum="100" Value="50"/>
-```
+````
 
 Use following Test Studio code to get/set the position of the slider in the application under test.
 
-```C#
+````C#
 // Read value
 var sliderValue = Applications.<YOUR_APPLICATION>.<YOUR_WINDOW>.MySlider.Find.ByType<SliderThumb>().Value;
 
 // Change value
 Applications.<YOUR_APPLICATION>.<YOUR_WINDOW>.MySlider.Find.ByType<SliderThumb>().Value = 20;
-```
+````
 
 In the case when there is an explicitly defined slider thumb, you will have to use that thumb's Value property to change the position of the slider.
 
 Let's say that in the application under test there is a slider defined like this:
 
-```XAML
+````xml
 <telerik:RadSlider Name="MySlider" Minimum="0" Maximum="100">
     <telerik:RadSlider.Thumbs>
         <telerik:SliderThumb Value="50" Visibility="Visible"/>
     </telerik:RadSlider.Thumbs>
 </telerik:RadSlider>
-```
+````
 
 Use following Test Studio code to get/set the possition of the slider in the application under test.
 
-```C#
+````C#
 // Read value
 var sliderValue = Applications.<YOUR_APPLICATION>.<YOUR_WINDOW>.MySlider.Find.ByType<SliderThumb>().Value;
 
 // Change value
 Applications.<YOUR_APPLICATION>.<YOUR_WINDOW>.MySlider.Find.ByType<SliderThumb>().Value = 20;
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/knowledge-base/test-automation-kb/invoke-mouse-hover.md b/docs/knowledge-base/test-automation-kb/invoke-mouse-hover.md
index 5e8b470e..25b55d30 100644
--- a/docs/knowledge-base/test-automation-kb/invoke-mouse-hover.md
+++ b/docs/knowledge-base/test-automation-kb/invoke-mouse-hover.md
@@ -4,7 +4,7 @@ page_title: Invoke Mouse Hover
 description: Insert Mouse Hoverover step. I recorded a click in a fly-out sub-menu, however it does not execute properly because the menu never properly expands to expose the element. Invoke mouse action.
 position: 1
 ---
-# Invoke a Mouse Hover event
+## Invoke a Mouse Hover event
 
 ## PROBLEM
 
diff --git a/docs/knowledge-base/test-automation-kb/read-wpf-automation-properties.md b/docs/knowledge-base/test-automation-kb/read-wpf-automation-properties.md
index dc4122f5..c1d189bf 100644
--- a/docs/knowledge-base/test-automation-kb/read-wpf-automation-properties.md
+++ b/docs/knowledge-base/test-automation-kb/read-wpf-automation-properties.md
@@ -15,9 +15,9 @@ How to read WPF `AutomationProperties` in Test Studio.
 Automation properties are defined as a set of  an attached properties of a WPF element, so you can read them using `GetAttachedProperty` method. 
 Here's an example of how to read the `ItemStatus` property:
 
-```C#
+````C#
 var itemStatus = <Your-Wpf-Element>.GetAttachedProperty<string>("System.Windows.Automation.AutomationProperties", "ItemStatus");
-```
+````
 
 > __Note__
 > The code above will work only when automation property values are set in the XAML of your WPF application.
diff --git a/docs/knowledge-base/test-automation-kb/security-certificates.md b/docs/knowledge-base/test-automation-kb/security-certificates.md
index c8c1ec4a..d3556be0 100644
--- a/docs/knowledge-base/test-automation-kb/security-certificates.md
+++ b/docs/knowledge-base/test-automation-kb/security-certificates.md
@@ -4,7 +4,7 @@ page_title: Security Certificates
 description: Security (SSL) Certificates. Browser prompt certificate warning. 
 position: 1
 ---
-# Security Certificates
+## Security Certificates
 
 Security (SSL) Certificates are tricky to automate because each browser prompts its warning differently. Because Test Studio only records in Internet Explorer, the "Continue to this website" link pictured below is recorded and expected to pass when executed in IE. That specific link does not exist in the other browsers, so we expect the test to fail at that step in Firefox, Safari, and Chrome.
 
@@ -37,19 +37,19 @@ There are a few workarounds to consider:
 
 4. Add a <a href="/features/custom-steps/script-step" target="_blank">Coded Step</a>. The code will perform different actions (such as mouse clicks and/or key presses) based on which browser is used. This will handle the different Certificate screens you encounter across browsers. Here's an example for Chrome:
 
-```C#
+````C#
 if (ActiveBrowser.BrowserType == BrowserType.Chrome)
 {
     Manager.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Tab);
     Manager.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Space);
 }
-```
-```VB
+````
+````VB
 If ActiveBrowser.BrowserType = BrowserType.Chrome Then
     Manager.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Tab)
     Manager.Desktop.KeyBoard.KeyPress(System.Windows.Forms.Keys.Space)
 End If
-```
+````
 
 [1]: /img/knowledge-base/test-automation-kb/security-certificates/fig1.png
 [2]: /img/knowledge-base/test-automation-kb/security-certificates/fig2.png
diff --git a/docs/knowledge-base/test-execution-kb/base-url.md b/docs/knowledge-base/test-execution-kb/base-url.md
index 435be20e..0a072ee0 100644
--- a/docs/knowledge-base/test-execution-kb/base-url.md
+++ b/docs/knowledge-base/test-execution-kb/base-url.md
@@ -4,11 +4,11 @@ page_title: Running a Test against Multiple Environments Using BaseURL
 description: Using BaseURL in a Test Studio project. Multiple test environments in which to execute test scripts. The server URL is different for each environment. How can I avoid rewriting all of my tests from scratch to make them work with a different server URL? Run the same tests against the different staging environments.
 position: 1
 ---
-# Running a Test Against Multiple Environments (Using BaseURL) #
+## Running a Test Against Multiple Environments (Using BaseURL) 
 
 I have multiple test environments against which to execute my test scripts. The server URL is different for each environment. How can I avoid rewriting all of my tests from scratch to make them work with a different server URL?
 
-## Solution ##
+## Solution 
 
 Test Studio allows you to create URL-relative tests with the concept of BaseURL. The BaseURL property is the static part of the URL that is set as a global setting for your entire project. A simple example is if your application **MyApplication** is deployed on both a production server **http://Server1** and a testing server **http://Server2**. If you <a href="#project-property">set the global project setting</a> and start recording, the navigation step will be recorded as follows:
 
@@ -19,14 +19,14 @@ Test Studio allows you to create URL-relative tests with the concept of BaseURL.
 
 In addition test lists have their own BaseURL property. This property is by default inherited by the project settings, but you can <a href="#test-lists-property">change it</a> to run the same set of tests against different servers. Bear in mind that if a test list has a BaseURL set it overrides the project property.
 
-## Project Property ##
+## Project Property 
 
 1. The global project setting can be set in the <a href="/features/project-settings/recording-options" target="_blank">Project Settings in the Recording tab</a>.
 1. The same setting can be quick accessed in the **Test** ribbon in the **Base URL** text field.
 
     ![BaseURL][1]
 
-## Test Lists Property ##
+## Test Lists Property 
 
 By default the test list, created in the project with already set BaseURL, inherits the same BaseURL. This can be changed in the <a href="/general-information/test-execution/test-list-settings" target="_blank">test list settings</a>. The BaseURL setting is listed under the Web tab.
 
@@ -34,7 +34,7 @@ By default the test list, created in the project with already set BaseURL, inher
 
 > __Note!__ The test list setting overrides the project setting, and thus you can create multiple test lists and set each to run against different BaseURL.
 
-## Test Step Property ##
+## Test Step Property 
 
 When the test uses any URL, which matches the BaseURL set for the project, the Navigate step will be recorded with the URL divided accordingly in the __BaseURL__ and __NavigateURL__ - this matches the relative part of the used URL.
 
@@ -52,11 +52,11 @@ If the navigated URL differs from the project BaseURL the navigation step is rec
 ><br>
 > If you need a single test to use different URL, other than the BaseURL, use the __Navigate To__ step property _BaseUrl_.
 
-## Project Property in the Visual Studio Plugin ##
+## Project Property in the Visual Studio Plugin 
 
 The default Test Studio settings are not applied in Visual Studio when executing tests through the <a href="/general-information/test-execution/vs-2012-test-explorers" target="_blank">Test Explorer</a>. To be able to set __BaseURL__ you will need to <a href="/knowledge-base/visual-studio-kb/test-explorer-settings" target="_blank">add a settings file and set it to be used from the Visual Studio Test Explorer</a>. Modify the newly created settings file to use the desired BaseURL in its Web tab.
 
-## Using the BaseURL with Frames ##
+## Using the BaseURL with Frames 
 
 When a recorded test step interacts with an element inside an iFrame, by default that iFrame is mapped with its full URL. There is an option, however, to specify that the URL of the iFrame is relative to the set BaseURL. Highlight the <a href="/general-information/test-recording/frames" target="_blank">Frame node</a> in the Elements Explorer and locate the **UsesBaseUrlHost** setting in the Frame's Properties Pane.
 
@@ -66,7 +66,7 @@ Let's say we want to run a test against the same application, but on different s
 
 When **UsesBaseUrlHost** is set to True, the frame uses the host portion of the project's or test list's BaseURL setting.
 
-### FrameInfo BaseURL ###
+### FrameInfo BaseURL 
 
 Let's say we want to run a test against the same application, but under different paths on the same server: **http://Server1/Dev1/Folder1/** and **http://Server1/Dev2/Folder1/**.
 
@@ -74,13 +74,13 @@ Modify the **BaseURL** property under **FrameInfo**. Start with '^/' to substitu
 
 ![FrameInfo BaseURL][6]
 
-## Connect to a Popup Window Using BaseURL ##
+## Connect to a Popup Window Using BaseURL 
 
 If **the base URL** of the dialog matches the one set as a **BaseUrl** property - Test Studio will automatically split the recorded URL, as well. For example - **PopupUrl** property of the "Connect to pop-up window" test step will contain the second part of the dialog's URL.
 
 ![Connect to Popup with BaseURL][7]
 
-## Maintain Previously Recorded Elements ##
+## Maintain Previously Recorded Elements 
 
 If you decide to apply the BaseURL setting for the project when there are already existing tests and elements, you may need to <a href="/knowledge-base/project-configuration-kb/merge-page-nodes" target="_blank">refactor the elements</a> in the Elements Repository to adjust the Page nodes properties to reflect the <a href="/features/project-settings/recording-options#elements-page-compare-mode" target="_blank">BaseURL recording options</a>.
 
diff --git a/docs/knowledge-base/test-execution-kb/excel-event.md b/docs/knowledge-base/test-execution-kb/excel-event.md
index 0b2ecb4f..acd6b76c 100644
--- a/docs/knowledge-base/test-execution-kb/excel-event.md
+++ b/docs/knowledge-base/test-execution-kb/excel-event.md
@@ -4,7 +4,7 @@ page_title: Executing a Test from an Excel Event
 description: Executing a Test from an Excel Event. Execute Test Studio tests or test lists by triggering events in an Excel spreadsheet
 position: 1
 ---
-#Executing a Test from an Excel Event#
+## Executing a Test from an Excel Event
 
 Some users may want to execute Test Studio tests or test lists by triggering events in an Excel spreadsheet. For example, your goal may be to create an Excel spreadsheet with a button whose click event is attached to a macro that runs your Test Studio tests.
 
diff --git a/docs/knowledge-base/test-execution-kb/execute-selenium-test.md b/docs/knowledge-base/test-execution-kb/execute-selenium-test.md
index f33bef7c..ec671357 100644
--- a/docs/knowledge-base/test-execution-kb/execute-selenium-test.md
+++ b/docs/knowledge-base/test-execution-kb/execute-selenium-test.md
@@ -4,15 +4,15 @@ page_title: Execute Selenium Test with Test Studio
 description: Execute Selenium Test with Test Studio. Execute Selenium Test as part of Test Studio web test.
 position: 1
 ---
-# Execute Selenium Test with Test Studio
+## Execute Selenium Test with Test Studio
 
-If you have written your selenium tests using C# then you can easily execute them using Test Studio. Steps to proceed:
+If you have written your selenium tests using C# then you can easily execute them using Test Studio. Steps to follow:
 
-1.&nbsp; In Test Studio <a href="http://docs.telerik.com/teststudio/getting-started/create-test-standalone/web-test" target="_blank">create a new test</a>.
+1.&nbsp; In Test Studio <a href="/getting-started/create-test-standalone/web-test" target="_blank">create a new test</a>.
 
-2.&nbsp; Add a <a href="http://docs.telerik.com/teststudio/advanced-topics/coded-steps/coded-step" target="_blank">coded step</a> in the test. 
+2.&nbsp; Add a <a href="/advanced-topics/coded-steps/coded-step" target="_blank">coded step</a> in the test. 
 
-3.&nbsp; Download selenium dlls from <a href="http://docs.seleniumhq.org/download/" target="_blank">here</a> and <a href="http://docs.telerik.com/teststudio/advanced-topics/coded-steps/add-assembly-reference" target="_blank">add the assembly references</a>.
+3.&nbsp; Download selenium dlls from <a href="http://docs.seleniumhq.org/download/" target="_blank">here</a> and <a href="/advanced-topics/coded-steps/add-assembly-reference" target="_blank">add the assembly references</a>.
 
 4.&nbsp; Make sure you add the using statements:
 
@@ -24,9 +24,15 @@ If you have written your selenium tests using C# then you can easily execute the
 
 The provided code sample above opens Firefox browser and navigates to Google.com. In the search field it types "webdriver" and hit the search button.
 
-6.&nbsp; Click the <a hreg="http://docs.telerik.com/teststudio/getting-started/test-execution/quick-execution" target="_blank">**Execute**</a> button in the **Quick Execution** ribbon in order to run the test. You can also execute the test as a part of a <a href="http://docs.telerik.com/teststudio/getting-started/test-execution/test-lists-standalone" target="_blank">test list</a>.
+6.&nbsp; Click the <a href="/getting-started/test-execution/quick-execution" target="_blank">**Execute**</a> button to run the test. 
 
-7.&nbsp; As soon as the test is executed you can review the test result using the <a href="http://docs.telerik.com/teststudio/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log" target="_blank">execution log</a> or using the <a href="http://docs.telerik.com/teststudio/getting-started/test-results/calendar" target="_blank">calendar</a> if executed as a part of a test list. The test can fail if an Assert statement fails.
+7.&nbsp; You can also execute the test as a part of a <a href="/getting-started/test-execution/test-lists-standalone" target="_blank">test list</a>.
+
+8.&nbsp; As soon as the test is executed you can review the test result using the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log" target="_blank">execution log</a> or using the <a href="/getting-started/test-results/calendar" target="_blank">calendar</a> if executed as a part of a test list. The test can fail if an Assert statement fails.
+
+> __Note!__ 
+> <br>
+> Test Studio web test always launches the selected browser upon execution. However, this shouldn't be the same browser in which the Selenium test runs as this might cause any inconsistency. 
 
 [1]: /img/knowledge-base/test-execution-kb/execute-selenium-test/fig1.png
 [2]: /img/knowledge-base/test-execution-kb/execute-selenium-test/fig2.png
diff --git a/docs/knowledge-base/test-execution-kb/ghost-tests-dynamic-test-list-resolution.md b/docs/knowledge-base/test-execution-kb/ghost-tests-dynamic-test-list-resolution.md
new file mode 100644
index 00000000..4bf09196
--- /dev/null
+++ b/docs/knowledge-base/test-execution-kb/ghost-tests-dynamic-test-list-resolution.md
@@ -0,0 +1,54 @@
+---
+title: Resolving Ghost Tests in Dynamic Test Lists
+description: Learn how to address the issue of ghost tests appearing in Dynamic Test Lists in Progress® Telerik® Test Studio® when using Scheduling.
+type: how-to
+page_title: Fixing Issues with Ghost Tests in Dynamic Test Lists in Test Studio
+slug: ghost-tests-dynamic-test-list-resolution
+tags: test-studio,scheduling,dynamic-test-list,mongodb,storage-database
+res_type: kb
+ticketid: 1686593
+---
+
+
+## Description
+
+When running a Dynamic Test List in Progress® Telerik® Test Studio® via <a href="/automated-tests/scheduling/overview" target="_blank">Scheduling</a>, you may encounter a situation where tests that no longer exist in the local project are executed. These ghost tests may appear because the MongoDB storage database retains files even after they have been deleted from the local project. This issue can cause test failures and discrepancies between the local project and the tests executed remotely.
+
+This knowledge base article also answers the following questions:
+- How to remove ghost tests from a Dynamic Test List in Test Studio?
+- Why are deleted tests still running in Test Studio Scheduling?
+- How to clean up the MongoDB storage database for Test Studio?
+
+## Solution
+
+To resolve this issue, follow one of the approaches below:
+
+### Approach 1: Using MongoDB Compass to Delete Specific Tests
+
+1. Download MongoDB Compass from their <a href="https://www.mongodb.com/try/download/compass" target="_blank">official download page</a>.
+2. Connect MongoDB Compass to your Test Studio storage database using the instructions <a href="https://www.mongodb.com/docs/compass/current/connect/" target="_blank">here</a>.
+3. Navigate to the `tests` collection in the MongoDB database.
+4. Search for and locate the document corresponding to the ghost test using the guidelines <a href="https://www.mongodb.com/docs/compass/current/documents/#manage-documents" target="_blank">here</a>.
+5. Delete the identified document to remove the ghost test.
+
+### Approach 2: Use Static Test Lists or Refine Filters
+
+- Replace the Dynamic Test List with a Static Test List if applicable. Static lists do not rely on filters and will contain only the tests explicitly added.
+- Modify the filters for the Dynamic Test List to ensure they are more precise and exclude unintended tests.
+
+### Approach 3: Drop the Entire Storage Database
+
+1. Follow the steps outlined <a href="/knowledge-base/scheduling-kb/drop-storage-database" target="_blank">to drop the entire MongoDB storage database</a>.
+2. After dropping the database, use <a href="/automated-tests/scheduling/upload-latest-files" target="_blank">the `Upload` button</a> in Test Studio to upload the current state of your project to the Storage database.
+
+
+> __Note!__ 
+> <br>
+> Dropping the entire database also __deletes all existing test results__. If you need __to keep the results from previous runs__, consider dropping specific collections only using the instructions <a href="/knowledge-base/scheduling-kb/drop-storage-database#drop-single-collections-from-database" target="_blank">here</a>.
+
+## See Also
+
+- [MongoDB Compass Documentation](https://www.mongodb.com/docs/compass/current/)
+- [Dropping the Storage Database](/knowledge-base/scheduling-kb/drop-storage-database)
+- [Dynamic Test Lists Overview](/automated-tests/test-lists/test-lists-standalone#dynamic-test-lists)
+- [Scheduling Setup in Test Studio](/automated-tests/scheduling/overview)
diff --git a/docs/knowledge-base/test-execution-kb/keep-active-session.md b/docs/knowledge-base/test-execution-kb/keep-active-session.md
index 8fb3c03d..e407bd90 100644
--- a/docs/knowledge-base/test-execution-kb/keep-active-session.md
+++ b/docs/knowledge-base/test-execution-kb/keep-active-session.md
@@ -4,11 +4,11 @@ page_title: Keep an Active Session
 description: No Functional tests can be executed on locked machine or inactive desktop session. This is a possible solution how to configure few machines to keep an active session on one of the machines. 
 position: 1
 ---
-# Keep an Active Session Running on the Execution Server
+## Keep an Active Session Running on the Execution Server
 
 Scheduling involves running Test Studio tests on an Execution Server. However, any test that requires moving the mouse or sending keystrokes requires an unlocked desktop. Test Studio tests are not the only ones affected by this Windows limitation. This is a general problem with any tool that performs UI testing.
 
-Test Studio tests running against HTML-based web applications (ASP .NET and others) frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject events (like a Click or Select) directly into the DOM structure of the page. Unfortunately, when performing Silverlight or WPF testing, these events cannot be injected in the same way. We have to simulate system-wide mouse moves and mouse clicks instead.
+Test Studio tests running against HTML-based web applications (ASP .NET and others) frequently can work on a locked machine because most test steps don't use the mouse or keyboard. Instead they are able to inject events (like a Click or Select) directly into the DOM structure of the page. Unfortunately, when performing WPF testing, these events cannot be injected in the same way. We have to simulate system-wide mouse moves and mouse clicks instead.
 
 ## Solution
 
diff --git a/docs/knowledge-base/test-execution-kb/minimized-rdc.md b/docs/knowledge-base/test-execution-kb/minimized-rdc.md
index c464f555..a8168dbf 100644
--- a/docs/knowledge-base/test-execution-kb/minimized-rdc.md
+++ b/docs/knowledge-base/test-execution-kb/minimized-rdc.md
@@ -4,11 +4,11 @@ page_title: Minimized RDC
 description: Scheduled tests cannot be run on minimized RDC. To run tests on a remote machine while the RDC window is minimized, add registry keys on the computer from which you connect to the remote machine
 position: 1
 ---
-#Minimized Remote Desktop Connection#
+## Minimized Remote Desktop Connection
 
 *I am executing tests on a remote machine using Remote Desktop Connection/Protocol. It works correctly as long as the RDC window is active and/or maximized. However the tests fail when the RDC window is minimized.*
 
-##Solution##
+## Solution
 
 This is a common issue with all UI automation tools. To run tests on a remote machine while the RDC window is minimized, add registry keys on the computer from which you connect to the remote machine:
 
diff --git a/docs/knowledge-base/test-execution-kb/multi-browsers.md b/docs/knowledge-base/test-execution-kb/multi-browsers.md
index f3c7fcba..6da2da44 100644
--- a/docs/knowledge-base/test-execution-kb/multi-browsers.md
+++ b/docs/knowledge-base/test-execution-kb/multi-browsers.md
@@ -4,7 +4,7 @@ page_title: How to Run Tests in Parallel / in Multi Browsers
 description: How can I run my tests in parallel? How do I run my tests in multiple browsers? Run scheduled Test Studio tests against different browsers.
 position: 1
 ---
-#How to Run Tests in Parallel / in Multi Browsers#
+## How to Run Tests in Parallel / in Multi Browsers
 
 Customers often wonder "How can I run my tests in parallel" and/or "How do I run my tests in multiple browsers, including multiple versions of the same browser". There are many ways to accomplish this. This article will focus on how to achieve this using the <a href="/features/scheduling-test-runs/Overview" target="_blank">Scheduling Server and Execution Server</a> that comes with both full Test Studio and our <a href="/general-information/test-studio-run-time" target="_blank">Runtime edition</a>.
 
@@ -20,7 +20,7 @@ You now may be wondering "With the above restrictions how is it possible to run
 
 For example, you want to run your tests in IE 9, 10, 11 as well as the latest version of Chrome and Firefox. This requires a minimum of three machines, one for IE 9, one for IE 10 and one for IE 11. You can also install Chrome and Firefox on any of the three machines, or all three if you like. Or if you prefer setup two additional machines, one for Chrome and one for Firefox.
 
-##How to Run Tests in Multiple Browsers##
+## How to Run Tests in Multiple Browsers
 
 Now let's get into the technical details of how to make your tests run in different browsers. First you must put your test or tests into a <a href="/getting-started/test-execution/test-lists-standalone" target="_blank">test list</a>. Next open the <a href="/getting-started/test-execution/test-list-settings" target="_blank">Test List Settings</a>, go to the Web tab and open the ExecutingBrowsers drop down.
 
@@ -30,7 +30,7 @@ Here is where you select which browser or browsers you want Test Studio to run t
 
 That's all it takes to make your tests run in different browsers on the same machine.
 
-##How to Run Tests in Parallel##
+## How to Run Tests in Parallel
 
 As previously stated in this article, to run tests in parallel you must setup multiple execution servers. Here's a high level block diagram of what this looks like:
 
diff --git a/docs/knowledge-base/test-execution-kb/run-api-test-in-web-test.md b/docs/knowledge-base/test-execution-kb/run-api-test-in-web-test.md
index 249e9164..19723052 100644
--- a/docs/knowledge-base/test-execution-kb/run-api-test-in-web-test.md
+++ b/docs/knowledge-base/test-execution-kb/run-api-test-in-web-test.md
@@ -4,7 +4,7 @@ page_title: Run an API Test within a Web Test
 description:  Run an API Test within a Web Test with Test Studio. Execute API test as step in a web test in Test Studio. Run API tests as part of a Test Studio web project. Integrate API testing with Test Studio web tests. 
 position: 1
 ---
-# How to Run an API Test within a Web Test
+## How to Run an API Test within a Web Test
 
 In some cases you may need to combine a Test Studio web test with an API test. For example, if your application under test interacts with a service (e.g. creates a user in a web interface that gets stored in a database) and you want to verify directly against that interface that your new user is correctly created.
 
@@ -27,7 +27,7 @@ The code will wait for the end of the API test execution. After the process ends
 Hint: in a default installation, the path to the executable Telerik.ApiTesting.Runner.exe is: 
 "C:\Program Files (x86)\Progress\Test Studio\Bin\ApiTesting\runnerconsole\Telerik.ApiTesting.Runner.exe"
 
-```C#
+````C#
 	
 	// Have to include the references:
 	using System.Diagnostics;
@@ -57,8 +57,8 @@ Hint: in a default installation, the path to the executable Telerik.ApiTesting.R
 	    Assert.AreEqual(exitCode, 0);
 	}
 	
-```
-```VB
+````
+````VB
 	
 	Imports System.Diagnostics
 	
@@ -81,7 +81,7 @@ Hint: in a default installation, the path to the executable Telerik.ApiTesting.R
 
 	End Sub
 	
-```
+````
 
 ## Advanced: Passing a Variable from an API Test to a Web Test
 
@@ -110,7 +110,7 @@ To achieve that you can:
 
  - Add another coded step after that, that will read the .variables file for your test and extract the desired variable:
 
-```C#
+````C#
 		
 		// Have to include the references:
 		using System.IO;
@@ -139,8 +139,8 @@ To achieve that you can:
 	        SetExtractedValue("extractedEmail", email);
 		}
 		
-```
-```VB
+````
+````VB
 
 		Imports System.IO
 		Imports Newtonsoft.Json.Linq
@@ -163,7 +163,7 @@ To achieve that you can:
            
         End Sub
 
-```
+````
 
 Note: .variables files contain text in json format. An easy way to extract a particular value from them is if you parse the file using [Json.NET](http://www.newtonsoft.com/json). Test Studio already uses Json.NET so its .dll file (Newtonsoft.Json.dll) is available in the Bin folder of the Test Studio installation folder. In order to add `using Newtonsoft.Json.Linq;` to your coded step, you need to add an assembly reference to Newtonsoft.Json.dll as described [here](http://docs.telerik.com/teststudio/features/coded-steps/add-assembly-reference)
 
diff --git a/docs/knowledge-base/test-execution-kb/run-mobile-test-in-web-test.md b/docs/knowledge-base/test-execution-kb/run-mobile-test-in-web-test.md
deleted file mode 100644
index 9b17c0dc..00000000
--- a/docs/knowledge-base/test-execution-kb/run-mobile-test-in-web-test.md
+++ /dev/null
@@ -1,79 +0,0 @@
----
-title: Run a Mobile Test within a Web Test
-page_title: Run a Mobile Test within a Web Test
-description: Run mobile Test within a Web Test with Test Studio. Execute mobile test as step in a web test in Test Studio. Run Mobiletests as part of a Test Studio web project. Integrate Mobile testing with Test Studio web tests. 
-position: 1
-publish: false
----
-#How to Run a Mobile Test within a Web Test#
-
-A common testing scenario is to have a web based application that could interact both with web and mobile users. There is a way to develop and execute a web test that at certain step runs a mobile test. To complete that the following initial conditions are needed:
-
- - web test,
- - mobile test,
- - Mobile Testing Desktop Application running - it will run the Message Server.
-
-Next step is to create a coded step in the web test that will start a system process. The following code will run the Telerik.MobileTesting.Runner.exe with arguments: 
-
- - Message Server's url and port
- - mobile project path
- - the relative path to and name of the mobile test
-
-The code will wait for the end of the mobile test execution. After the process ends - the exit code is placed in assert statement to check if this step passed or failed depending on the mobile test status.
-
-Detailed results of the mobile test execution will be present in the mobile project folder (*Results* sub-folder), where the mobile test is located. 
-
-```C#
-// Need to include the references:
-using System.IO;
-using System.Diagnostics;
-
-[CodedStep(@"Run Mobile Test")]
-public void Run_Mobile_Test_CodedStep()
-{
-    // initialize new system process
-    Process runMobileTest = new Process();
-
-    // define the process name to be started
-    runMobileTest.StartInfo.FileName = @"[PathToExecutable]\Telerik.MobileTesting.Runner.exe";
-
-    // set the arguments
-    runMobileTest.StartInfo.Arguments = @"/C " +  " /msgServer=\"ws://localhost:8084\" /project=\"[PathToTheProject]\\DemoMobileProject\" /test=\"Web Tests\"\\Login.mttest";
-
-    // run the process
-    runMobileTest.Start();
-
-    // wait until the test return an exit code
-    runMobileTest.WaitForExit();
-
-    // get the exit code from the executed process 
-    int exitCode = runMobileTest.ExitCode;
-
-    // check if this test step pass or fail. If return 0 - process complete normally, else - process fould.
-    Assert.AreEqual(exitCode, 0);
-}
-```
-```VB
-
-Imports System.IO
-Imports System.Diagnostics
-
-<CodedStep("Run Mobile Test")> _
-Public Sub Run_Mobile_Test_CodedStep()
-
-    Dim runMobileTest As New Process()
-
-    runMobileTest.StartInfo.FileName = "[PathToExecutable]\Telerik.MobileTesting.Runner.exe"
-
-    runMobileTest.StartInfo.Arguments = "/C " +  " /msgServer=\"ws://localhost:8084\" /project=\"[PathToTheProject]\\DemoMobileProject\" /test=\"Web Tests\"\\Login.mttest";
-
-    runMobileTest.Start()
-
-    runMobileTest.WaitForExit()
-
-    Dim exitCode As Integer = runMobileTest.ExitCode		
-
-    Assert.AreEqual(exitCode, 0)
-
-End Sub
-```
diff --git a/docs/knowledge-base/test-execution-kb/run-web-test-in-other-test.md b/docs/knowledge-base/test-execution-kb/run-web-test-in-other-test.md
index df91a8f7..0a1bf355 100644
--- a/docs/knowledge-base/test-execution-kb/run-web-test-in-other-test.md
+++ b/docs/knowledge-base/test-execution-kb/run-web-test-in-other-test.md
@@ -4,14 +4,14 @@ page_title: Run a Web Test within Other Test
 description: Execute a Test Studio web test as part of any other test in code. 
 position: 1
 ---
-#How to Run a Web Test within Other Test#
+## How to Run a Web Test within Other Test
 
 This scenario makes sense for example when there is a web test or test list located in another project that has to be executed in the current project. Such approach has to be implemented with caution though. The external test would be launched as separate to the main process and in case of its failure there could be not enough information on the reasons that happen. If the test is located in the same project then it could be executed <a href="/features/custom-steps/test-as-step" target="_blank">as a step</a> or in a <a href="/features/coded-steps/coded-step" target="_blank">coded step</a> using the expression: this.ExecuteTest("SampleTest.tstest").
 
 To run an external test it has to be in a coded step. There a separate system process has to be started. The following code will run the ArtOfTest.Runner.exe with argument - a test list containing single or multiple tests to be executed. All possible arguments are listed in this <a href="/features/test-runners/artoftest-runner" target="_blank">article</a>.
 
 
-```C#
+````C#
     
 // references to the project
 using System.IO;
@@ -42,8 +42,8 @@ public void Run_Web_Test_CodedStep()
     Assert.AreEqual(exitCode, 0);
 }
     
-```
-```VB
+````
+````VB
     
 Imports System.IO
 Imports System.Diagnostics
@@ -67,4 +67,4 @@ Imports System.Diagnostics
 	
 End Sub
     
-```
+````
diff --git a/docs/knowledge-base/test-execution-kb/set-test-execution-time-limit.md b/docs/knowledge-base/test-execution-kb/set-test-execution-time-limit.md
index 328a9c27..afe34109 100644
--- a/docs/knowledge-base/test-execution-kb/set-test-execution-time-limit.md
+++ b/docs/knowledge-base/test-execution-kb/set-test-execution-time-limit.md
@@ -5,12 +5,12 @@ description: In some automation scenarios it is necessary to limit a single test
 
 position: 1
 ---
-#Set Test Execution Time Limit#
+## Set Test Execution Time Limit
 
 In some automation scenarios it is necessary to limit a single test execution to a certain time frame. That is possible if the following approach is used. In an <a href="/advanced-topics/coded-samples/general/execution-extensions" target="_blank">execution extension</a> library is set timer that is re-set each time the new test starts. If the time expired before the timer is re-set - all processes related to test execution are killed. This will ensure if a test takes more than initially defined time interval to stop its execution and continue with the next test. Below is given sample execution extension library with time frame set to 5 minutes.
 
 
-```C#
+````C#
 	
 public class ExecutionTimeout : IExecutionExtension
 {
@@ -100,9 +100,8 @@ public class ExecutionTimeout : IExecutionExtension
         }
     }
 }
-```
-
-```VB
+````
+````VB
 
 Public Class ExecutionTimeout
 	Implements IExecutionExtension
@@ -179,4 +178,4 @@ Public Class ExecutionTimeout
 	End Sub
 End Class
 
-```
+````
diff --git a/docs/knowledge-base/test-execution-kb/slow-execution-rdc.md b/docs/knowledge-base/test-execution-kb/slow-execution-rdc.md
index 2909cab2..cd86ca90 100644
--- a/docs/knowledge-base/test-execution-kb/slow-execution-rdc.md
+++ b/docs/knowledge-base/test-execution-kb/slow-execution-rdc.md
@@ -4,11 +4,11 @@ page_title: Slow Execution via RDC
 description: Test Studio tests execution is too slow via RDC. Test Studio Tests fail via RDC
 position: 1
 ---
-#Slow Execution via Remote Desktop Connection#
+## Slow Execution via Remote Desktop Connection
 
 *I am using Test Studio via a Remote Desktop Connection. Execution is slow and tests often fail.*
 
-##Solution##
+## Solution
 
 Decrease the color depth of the remote session to increase performance. This option is on the **Display** tab of the RDC menu.
 
diff --git a/docs/knowledge-base/test-execution-kb/test-list-execution-stops-unexpectedly.md b/docs/knowledge-base/test-execution-kb/test-list-execution-stops-unexpectedly.md
index 1b9f1bd8..a3ab8325 100644
--- a/docs/knowledge-base/test-execution-kb/test-list-execution-stops-unexpectedly.md
+++ b/docs/knowledge-base/test-execution-kb/test-list-execution-stops-unexpectedly.md
@@ -30,11 +30,11 @@ To identify and resolve the issue with the Test List execution stopping unexpect
 
 3. Once the execution stops unexpectedly, review the generated application log. Look for entries similar to the following error message:
 
-    ```
-    [Error] LoadTest: Unable to find test at 'C:\Test Studio\ProjectFolder\SubFolder\Test1.tstest'!
-    ....
-    CommandLineTestListRunner.RunnerProcess_Exited() : Runner process exit code: 12 - NOT_RUN_TEST_NOT_FOUND.
-    ```
+````
+[Error] LoadTest: Unable to find test at 'C:\Test Studio\ProjectFolder\SubFolder\Test1.tstest'!
+....
+CommandLineTestListRunner.RunnerProcess_Exited() : Runner process exit code: 12 - NOT_RUN_TEST_NOT_FOUND.
+````
 
 4. This error indicates that a test referenced in the Test List (`Test1.tstest`) is missing from the specified location in the project.
 
diff --git a/docs/knowledge-base/test-execution-kb/troubleshoot-execute-command-failed-error-telerik-test-studio.md b/docs/knowledge-base/test-execution-kb/troubleshoot-execute-command-failed-error-telerik-test-studio.md
index f2de9e44..858abfcb 100644
--- a/docs/knowledge-base/test-execution-kb/troubleshoot-execute-command-failed-error-telerik-test-studio.md
+++ b/docs/knowledge-base/test-execution-kb/troubleshoot-execute-command-failed-error-telerik-test-studio.md
@@ -11,9 +11,9 @@ tags: troubleshooting, executecommand error, client error, protocol error, runti
 
 I get the following error when executing an automation script in Telerik Test Studio:
 
-```
+````
 'ExecuteCommand failed! InError set by the client. Client Error: Protocol error (Runtime.evaluate): Promise was collected BrowserCommand'
-```
+````
 
 The error occurs on a click step. Although the button is clicked and the action is performed as expected, the step fails.
 
diff --git a/docs/knowledge-base/test-execution-kb/troubleshooting-error-cs0246-telerik-test-studio.md b/docs/knowledge-base/test-execution-kb/troubleshooting-error-cs0246-telerik-test-studio.md
index 1a425881..3490d476 100644
--- a/docs/knowledge-base/test-execution-kb/troubleshooting-error-cs0246-telerik-test-studio.md
+++ b/docs/knowledge-base/test-execution-kb/troubleshooting-error-cs0246-telerik-test-studio.md
@@ -1,32 +1,51 @@
 ---
-title: Resolving Error CS0246 in Telerik Test Studio
-description: Learn how to resolve the CS0246 compialtion error in Telerik Test Studio when running a batch remotely or locally.
+title: Resolving "Error CS0246 'Pages' could not be found" in Telerik Test Studio
+description: "Learn how to resolve the CS0246: The type or namespace name 'Pages' could not be found compialtion error in Telerik Test Studio when running a batch remotely or locally. "
 type: troubleshooting
 page_title: Troubleshooting Compile Error CS0246 in Telerik Test Studio
 slug: troubleshooting-error-cs0246-telerik-test-studio
 tags: telerik-test-studio, error-cs0246, troubleshooting
 res_type: kb
 ---
+
 ## Description
-When trying to compile Test Studio project I get error CS0246. The error prevents me running a test list remotely or locally. The error persists even when I try to run a single test using the Execute button.
+When trying to compile Test Studio project I get error __CS0246: The type or namespace name 'Pages' could not be found__. The error prevents me running a test list remotely or locally. The error persists even when I try to run a single test using the `Execute` button.
 
-```
+````
 [ Compiler ]
 12:14:49 'ERROR' > C:\Test Studio Projects\TestProject27\getBaseUrl.tstest.cs(39,16) : error CS0246: The type or namespace name 'Pages' could not be found (are you missing a using directive or an assembly reference?)
 12:14:49 'ERROR' > C:\Test Studio Projects\TestProject27\getBaseUrl.tstest.cs(32,17) : error CS0246: The type or namespace name 'Pages' could not be found (are you missing a using directive or an assembly reference?)
 12:14:49 'INFO' > Build Failed
 
-```
+````
+
+## Cause 
+
+The code-behind files listed in the compilation errors have a namespace which doesn't match the project's namespace. 
 
 ## Solution
+
 To resolve this compilation CS0246 error, follow these steps:
 
 1. Open the project in Telerik Test Studio.
 2. <a href="/automated-tests/coded-tests/compile-project" target="_blank">Compile the project</a> by selecting the "Compile All" option. 
 3. Check the <a href="/automated-tests/coded-tests/output-panel" target="_blank">Output panel</a> for any compilation errors. The errors are listed there.
-4. Verify if any new tests with coded steps were added to the project. If so, ensure that they were <a href="/knowledge-base/best-practices-kb/add-existing-test" target="_blank">added using the import option</a> in Test Studio and not copied and pasted into the Windows File Explorer.
-5. Open the Project Settings and switch to the <a href="/features/project-settings/script-options" target="_blank">"Script" tab</a>. Note the project's namespace.
-6. Review the tests listed in the compilation error and their coded files.
-7. In the code-behind file of each test listed in the compilation error, check if the namespace matches the project's namespace from the settings - replace it with the current namespace.
-8. Alternatively, you can change the namespace for all tests at once by opening the Project Settings, switching to the "Script" tab, and modifying the namespace there. Confirm the changes by clicking "OK".
-9. Compile the project again using the "Compile All" option and ensure that the compilation is now successful.
+    
+    > __Important!__
+    ><br>
+    ><br>
+    > If the __local compilation is successful__ but you see the mendioned error when executing tests remotely via the Test Studio Scheduling setup, probably you uploaded the project to the Storage database in a corrupted state. 
+    ><br>
+    > - __If the test and code-behind file exists__ in the project, ensure <a href="/automated-tests/scheduling/upload-latest-files" target="_blank">to upload the latest fixed state of the project to the Storage database</a>. 
+    ><br>
+    > - __If the test and code-behind file doesn't exists__ in the project anymore, you will need to <a href="/knowledge-base/scheduling-kb/drop-storage-database" target="_blank">drop the database</a>.  
+
+4. Open the Project Settings and switch to the <a href="/features/project-settings/script-options" target="_blank">"Script" tab</a>. Note the project's namespace.
+5. Review the tests listed in the compilation error and their coded files.
+6. In the code-behind file of each test listed in the compilation error, __check if the namespace matches the project's namespace from the settings - replace it with the current namespace__.
+7. Alternatively, you can change the namespace for all tests at once by opening the Project Settings, switching to the "Script" tab, and modifying the namespace there. Confirm the changes by clicking "OK".
+8. Compile the project again using the "Compile All" option and ensure that the compilation is now successful.
+
+> __Tip__
+> <br> 
+> To avoid such errors ensure that you __use the option to <a href="/knowledge-base/best-practices-kb/add-existing-test" target="_blank">import existing tests</a> in a Test Studio project__ instead of copying the files in  Windows File Explorer.
diff --git a/docs/knowledge-base/test-execution-kb/troubleshooting-test-failure-downloading-excel-file-test-studio.md b/docs/knowledge-base/test-execution-kb/troubleshooting-test-failure-downloading-excel-file-test-studio.md
index a679a19b..218f500f 100644
--- a/docs/knowledge-base/test-execution-kb/troubleshooting-test-failure-downloading-excel-file-test-studio.md
+++ b/docs/knowledge-base/test-execution-kb/troubleshooting-test-failure-downloading-excel-file-test-studio.md
@@ -12,7 +12,7 @@ res_type: kb
 
 Executing a test in Test Studio that includes a step to download a file, the test fails with the following error:
 
-```
+````
 Failure detected during execution. Details:
 ------------------------------------------------------------
 System.ArgumentException: Open or Run downloaded file is not supported for ChromeHeadless.
@@ -24,7 +24,7 @@ System.ArgumentException: Open or Run downloaded file is not supported for Chrom
    at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTestIteration(Object codeBehindInstance, Boolean isDataDriven)
    at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InternalExecuteTest(Test test, TestResult initializationResult)
    at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
-```
+````
 
 The error occurs when running the test with the regular Chrome browser, not just the headless version. Running the test in Edge and Firefox behaves the same way and fails with the same error. 
 
diff --git a/docs/knowledge-base/test-recording-kb/element-image-known-scenarios.md b/docs/knowledge-base/test-recording-kb/element-image-known-scenarios.md
index dfa8b378..22b130dd 100644
--- a/docs/knowledge-base/test-recording-kb/element-image-known-scenarios.md
+++ b/docs/knowledge-base/test-recording-kb/element-image-known-scenarios.md
@@ -4,7 +4,7 @@ page_title: Element Images Known Scenarios
 description: "Element Images Known Scenarios Requiring Manual Adjustment. Combobox element image is incorrect. textBox element image is incorrect. Element Image Capturing on Scaled Monitors. Recording WaitForExist Step element image is missing. Recording Different Images in different browsers for the Same Element. Using different images for a single element depending on the step where the same element is used. "
 position: 1
 ---
-# Scenarios in Which Element Images Require Additional Adjustment
+## Scenarios in Which Element Images Require Additional Adjustment
 
 There are certain scenarios in which Test Studio will not record the correct image for an element, or not record an image at all. The known workflows are described in details below.
 
@@ -35,7 +35,3 @@ Test Studio allows you to capture manually a new image for an element and then a
 3. Once the desired image is correctly recorded, in the [Image Usage Details section](/features/elements-explorer/find-element-by-image#image-usage-details) choose the step to apply it to from the **"Used By"** dropdown and then click on the **Apply** button.
 
 4. Save the changes. Switching the steps, which uses the element, from the same **"Used By"** dropdown, will display the different images accordingly.
-
-[1]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig1.png
-[2]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig2.png
-[3]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig3.png
diff --git a/docs/knowledge-base/test-recording-kb/fix-ocr-64bit-wpf.md b/docs/knowledge-base/test-recording-kb/fix-ocr-64bit-wpf.md
index 862fcfcf..e62e81ec 100644
--- a/docs/knowledge-base/test-recording-kb/fix-ocr-64bit-wpf.md
+++ b/docs/knowledge-base/test-recording-kb/fix-ocr-64bit-wpf.md
@@ -4,7 +4,7 @@ page_title: Fix OCR for 64bit WPF Applications
 description: Fix OCR recording and execution for 64bit WPF applications. Optical Character Recognition OCR for WPF applications 64 bit. Test Studio release 2020 R2 fix for OCR for WPF application.
 position: 3
 ---
-# Fix Optical Character Recognition (OCR) Recording and Execution for 64bit WPF Applications
+## Fix Optical Character Recognition (OCR) Recording and Execution for 64bit WPF Applications
 
 The <a href="/features/recorder/verifications/text-from-image" target="_blank">OCR feature</a> for WPF tests was introduced with Test Studio 2020 R2 SP1 (v.2020.2.910). You can extract the text from image and use it in verification, wait of extract steps.
 
diff --git a/docs/knowledge-base/test-recording-kb/kendoui-duplicate-elements.md b/docs/knowledge-base/test-recording-kb/kendoui-duplicate-elements.md
deleted file mode 100644
index 991cd0b7..00000000
--- a/docs/knowledge-base/test-recording-kb/kendoui-duplicate-elements.md
+++ /dev/null
@@ -1,34 +0,0 @@
----
-title: KendoUI Duplicate Elements
-page_title: KendoUI duplicate elements
-description: KendoUI duplicate elements due to new find logic
-position: 1
----
-#KendoUI duplicate elements due to new find logic#
-
-We have changed the element's find logic generated by the recorder (IE only, translators dependent) when recording over KendoUI widgets. This is to ensure reliable find logic for solid playback experience.
-
-This will result in separate elements appearing in the Elements Explorer as shown below. 
-
-![Elemets][1]
-
-Please note that you can leave the elements as they are, without taking extra actions. If you find having multiple elements in your project you can always merge elements, having the old elements to point to the newly recorded one using the find expression builder.
-
-The new logic includes a list of find clauses over the unique class attribute of Kendo widgets. It may also automatically build chained find expressions (for sub elements of widgets).
-A new GroupIndex clause is added so that the playback can find the exact instance in the HTML in case of multiple of the same type.
-
-Please find examples below of the same element recorded with the old find logic and the new one (see the highlighted parts).
-
-Old find logic:
-
-![Old find logic][2]
-
-New Find Logic:
-
-![New find logic][3]
-
-Please note that you will get inconsistent experience recording in IE vs. non-IE. This is due to missing KendoUI translators in Chrome/Firefox/Safari recorder.
-
-[1]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig1.png
-[2]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig2.png
-[3]: /img/knowledge-base/test-recording-kb/kendoui-duplicate-elements/fig3.png
diff --git a/docs/knowledge-base/test-recording-kb/resetting-ssl-certificates-test-studio.md b/docs/knowledge-base/test-recording-kb/resetting-ssl-certificates-test-studio.md
new file mode 100644
index 00000000..575e9bb4
--- /dev/null
+++ b/docs/knowledge-base/test-recording-kb/resetting-ssl-certificates-test-studio.md
@@ -0,0 +1,48 @@
+---
+title: Resetting SSL Certificates to Resolve Performance Run Errors in Telerik Test Studio
+description: Learn how to reset SSL certificates to resolve performance run errors in Telerik Test Studio caused by FiddlerCore certificate issues.
+type: how-to
+page_title: Resolving SSL Certificate Errors in Telerik Test Studio Performance Runs
+meta_title: Resolving SSL Certificate Errors in Telerik Test Studio Performance Runs
+slug: resetting-ssl-certificates-test-studio
+tags: telerik test studio, ssl, fiddler, performance, certificate
+res_type: kb
+ticketid: 1576623
+---
+
+
+## Description
+
+I encountered a SSL certificate error while running performance tests in Telerik Test Studio. The issue seems related to the FiddlerCore engine used in the background by Test Studio. Fiddler certificates might be improperly configured or corrupted, causing the connection to not be trusted.
+
+This knowledge base article also answers the following questions:
+- How to reset Fiddler SSL certificates for Telerik Test Studio?
+- How to resolve SSL errors in Test Studio performance mode?
+- How to fix SSL certificate issues affecting Test Studio tests?
+
+## Solution
+
+To fix this issue, reset the Fiddler certificates using the following steps:
+
+1. If Fiddler Classic is installed, open it and navigate to the [Options menu](https://docs.telerik.com/fiddler/configure-fiddler/tasks/decrypthttps) (Tools > Options > HTTPS).
+2. From the Actions dropdown, select "Reset All Certificates."
+3. Confirm all prompts about removing existing certificates and adding new ones.
+4. Ensure the prompt configuring Windows to always trust the Fiddler root certificate is confirmed.
+
+If Fiddler is not actively used but was installed previously, remove leftover certificates manually:
+
+1. Open the Windows Certificate Manager by typing `certmgr` in the Start menu.
+2. Under "Trusted Root Certification Authorities," locate certificates named `DO_NOT_TRUST_FiddlerRoot`.
+3. Remove all Fiddler-related certificates.
+4. Close the Certificate Manager.
+
+After resetting or removing certificates:
+1. Open Telerik Test Studio.
+2. Register the HTTPS certificate again.
+3. Run tests in performance mode to confirm the issue is resolved.
+
+## See Also
+
+- [Decrypting HTTPS Traffic in Fiddler](https://docs.telerik.com/fiddler/configure-fiddler/tasks/decrypthttps)
+- [Trusting the Fiddler Root Certificate](https://docs.telerik.com/fiddler/configure-fiddler/tasks/trustfiddlerrootcert) 
+
diff --git a/docs/knowledge-base/verification-kb/disabled-attribute-html.md b/docs/knowledge-base/verification-kb/disabled-attribute-html.md
index d386f5ee..d93e539c 100644
--- a/docs/knowledge-base/verification-kb/disabled-attribute-html.md
+++ b/docs/knowledge-base/verification-kb/disabled-attribute-html.md
@@ -4,7 +4,7 @@ page_title: Disabled Attribute (HTML)
 description: How to verify an HTML element attribute is disabled. Many website developers will setup buttons or other elements within the site to be "disabled" until a certain action occurs. When using Test Studio to test this, it is sometimes necessary to create a special verification that confirms that the button (in this example) is visible but disabled (not clickable/usable)
 position: 1
 ---
-#How to Verify the Disabled Attribute (HTML)#
+## How to Verify the Disabled Attribute (HTML)
 
 Many website developers will setup buttons or other elements within the site to be "disabled" until a certain action occurs. When using Test Studio to test this, it is sometimes necessary to create a special verification that confirms that the button (in this example) is visible but disabled (not clickable/usable). You can similarly verify that the disabled attribute no longer exists, indicating the button is clickable/usable.
 
@@ -13,11 +13,11 @@ For example, when you have a disabled or not disabled element on a page that nee
 
 ![Element Mapping][1]
 
-##SOLUTION 1 (No Code)##
+## SOLUTION 1 (No Code)
 
 1.&nbsp; Start recording.
 
-2.&nbsp; 2.Navigate to the page/step with the disabled element you'd like to verify.
+2.&nbsp; Navigate to the page/step with the disabled element you'd like to verify.
 
 *	Enable hover over highlighting.
 *	Hover the mouse over the applicable element
@@ -31,29 +31,29 @@ For example, when you have a disabled or not disabled element on a page that nee
 
 4.&nbsp; A new Verify rule will be created within the Test at the location you specified. You can right click this step to **Change Role** and **Set as Wait**, if desired. 
 
-##SOLUTION 2 (Using Code, also apples to Telerik Testing Framework)##
+## SOLUTION 2 (Using Code, also apples to Telerik Testing Framework)
 
 There are several ways to indicate a disabled element in HTML. This solution will work for each type of <a href="/troubleshooting-guide/browser-inconsistencies-tg/disabled-attribute" target="_blank">disabled</a>. First, access the element from a <a href="/features/custom-steps/script-step" target="_blank">Coded Step</a>.
 
 There are two ways to do that:
 
-1.&nbsp; 1.Write the Find Logic yourself in code. Use this approach if you are using Telerik Testing Framework only. You can insert this logic in the same coded step that does the disabled verification.
+1.&nbsp; Write the Find Logic yourself in code. Use this approach if you are using Telerik Testing Framework only. You can insert this logic in the same coded step that does the disabled verification.
 
-```C#
+````C#
 Element e = Find.ByExpression("id=myInput");
-```
+````
 
 2.&nbsp; Add the element to your Project Elements, then reference it from that source. Use this approach if you are using Test Studio Standalone version or the Visual Studio plugin.
 
-```C#
+````C#
 HtmlInputText e = Pages.TryitEditorV14.FrameView.LnameText;
-```
+````
 
 3.&nbsp; Once you have your Element e, here is the verification in code:
 
-```C#
+````C#
 Assert.IsTrue(e.ToString().Contains("disabled"));
-```
+````
 
 [1]: /img/knowledge-base/verification-kb/disabled-attribute-html/fig1.png
 [2]: /img/knowledge-base/verification-kb/disabled-attribute-html/fig2.png
diff --git a/docs/knowledge-base/verification-kb/verify-deleted-data.md b/docs/knowledge-base/verification-kb/verify-deleted-data.md
index 7fa5e608..02b35628 100644
--- a/docs/knowledge-base/verification-kb/verify-deleted-data.md
+++ b/docs/knowledge-base/verification-kb/verify-deleted-data.md
@@ -4,11 +4,11 @@ page_title: Verify Deleted Data
 description: verify that an element does not exist within a Test Studio test
 position: 1
 ---
-#Verify Deleted Data#
+## Verify Deleted Data
 
 I would like to verify that an element does not exist, like after deleting a row from a data grid.
 
-##Solution
+## Solution
 
 This is possible with a Wait for ExistsNot verification. Here's an example against <a href="http://demos.telerik.com/aspnet-ajax/grid/examples/columns-rows/rows/drag-and-drop/defaultcs.aspx" target="_blank">this Telerik demo site</a>:
 
diff --git a/docs/knowledge-base/verification-kb/verify-html-tool-tips.md b/docs/knowledge-base/verification-kb/verify-html-tool-tips.md
index f8cce860..a376f5f2 100644
--- a/docs/knowledge-base/verification-kb/verify-html-tool-tips.md
+++ b/docs/knowledge-base/verification-kb/verify-html-tool-tips.md
@@ -4,17 +4,17 @@ page_title: Verify HTML Tooltips
 description: Verify HTML Tooltips in Test Studio web test. Check the tooltip text in a Test Studio test. 
 position: 1
 ---
-#Verify HTML Tool-Tips#
+## Verify HTML Tool-Tips
 
 There's more than one way to implement Tool-tips in HTML. They are usually implemented using the Title attribute that gets applied to elements. Consider this HTML code snippet:
 
-```HTML
+````HTML
 <p>Test Studio, made by <span name="myHtmlSpan" title="Telerik is a leading vendor of development, team productivity, and automated testing tools.">Telerik</span>, is a quantum leap forward in Web test automation.</p>
-```
+````
 
 When you hover your mouse over the word Telerik, the tooltip will be displayed as shown in this screenshot:
 
-##SOLUTION 1 (No Code)##
+## SOLUTION 1 (No Code)
 
 ![Tool tip][1]
 
@@ -30,15 +30,15 @@ When you hover your mouse over the word Telerik, the tooltip will be displayed a
 
 5.&nbsp; Click **Add Step**. 
 
-##SOLUTION 2 (Using Code, also apples to Telerik Testing Framework)##
+## SOLUTION 2 (Using Code, also apples to Telerik Testing Framework)
 
 1.&nbsp; Create a <a href="/features/custom-steps/script-step" target="_blank">coded step</a>.
 
 2.&nbsp; Write the code as follows:
 
-```C#
+````C#
 Find.ByName<HtmlSpan>("myHtmlSpan").AssertAttribute().Value("title", ArtOfTest.Common.StringCompareType.Same, "Telerik is a leading vendor of development, team productivity, and automated testing tools.");
-```
+````
 
 Now when you execute your test it will verify that the Title attribute, i.e. the tool-tip, of your HTML element contains the correct text.
 
diff --git a/docs/knowledge-base/visual-studio-kb/resharper-compatibility.md b/docs/knowledge-base/visual-studio-kb/resharper-compatibility.md
index 568c124d..0182ab1b 100644
--- a/docs/knowledge-base/visual-studio-kb/resharper-compatibility.md
+++ b/docs/knowledge-base/visual-studio-kb/resharper-compatibility.md
@@ -4,11 +4,11 @@ page_title: ReSharper Compatibility
 description: ReSharper Compatibility in Test Studio. Cannot resolve symbol error messages in Test Studio.
 position: 1
 ---
-#ReSharper Compatibility#
+## ReSharper Compatibility
 
 *With ReSharper installed, you receive Cannot resolve symbol error messages in Test Studio code-behind files.*
 
-##Solution##
+## Solution
 
 ReSharper is warning you that it cannot locate the definition of the element in the project. The problem is that element definitions are kept in our Pages.g.cs(vb) file. This file is not included in the Visual Studio test project, but is included during project builds using an internal custom build task that is defined by Progress Test Studio. 
  
@@ -18,7 +18,8 @@ The error message is benign and can be safely ignored.
 
 Pages.MainPage.FrameContentIFrame*
 
-##Solution##
+
+## Solution
 
 Disable ReSharper's IntelliSense and enable Visual Studio's.
 
diff --git a/docs/prerequisites/configure-your-browser/browser-configuration.md b/docs/prerequisites/configure-your-browser/browser-configuration.md
index 96185552..24f842b7 100644
--- a/docs/prerequisites/configure-your-browser/browser-configuration.md
+++ b/docs/prerequisites/configure-your-browser/browser-configuration.md
@@ -10,7 +10,7 @@ position: 0
 A specific set of settings is required to enable each of the supported browsers for test recording and execution with Test Studio and this is called __Browser Calibration__. Some of the browsers also require the installation of an extension.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 <br>
@@ -26,7 +26,3 @@ To ease you in applying these settings, Test Studio provides a built-in mechanis
 > **Note** 
 ><br>
 > Test Studio deprecates Internet Explorer support in Q1 2025.
-
-[1]: /img/prerequisites/browser-config/edge-notification.jpg
-[2]: /img/prerequisites/browser-config/accept-popup.jpg
-[3]: /img/prerequisites/browser-config/accept-permissions.jpg
diff --git a/docs/prerequisites/configure-your-browser/browser-support-updater.md b/docs/prerequisites/configure-your-browser/browser-support-updater.md
index 6f6973f2..f47e3db9 100644
--- a/docs/prerequisites/configure-your-browser/browser-support-updater.md
+++ b/docs/prerequisites/configure-your-browser/browser-support-updater.md
@@ -16,7 +16,15 @@ When available, the __Browser support update__ notification appears next to the
 
 1. Click the __Update__ button next to the __New update available__ notification.
 
-![Browser support Update Button][2]
+    ![Browser support Update Button][2]
+
+2. Hitting the __Update__ button triggers the <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server" target="_blank">Test Studio Services Cofigurator application</a> where you need to switch to its <a href="/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server#browsers-tab" target="_blank">__Browsers__ tab</a>. 
+
+    > __Note!__ 
+    ><br> 
+    > Running the Browser support update through the Test Studio Services Config Wizard requires admin rights. 
+
+    ![Browser Update available](/img/features/scheduling-test-runs/create-scheduling-server/browsers-tab-update-aval.png)
 
 After the update, restart Test Studio for the changes to take effect.
 
diff --git a/docs/prerequisites/configure-your-browser/chrome-for-testing.md b/docs/prerequisites/configure-your-browser/chrome-for-testing.md
index 8d5fa583..6020d59a 100644
--- a/docs/prerequisites/configure-your-browser/chrome-for-testing.md
+++ b/docs/prerequisites/configure-your-browser/chrome-for-testing.md
@@ -17,29 +17,21 @@ Use the below steps to switch using the Chrome for Testing browser for test reco
 
 1. Go to the official Chrome channel to download Chrome for Testing setup - https://googlechromelabs.github.io/chrome-for-testing/#stable
 2. Look for the URL of the current `win64` or `win32` stable version and select the one which corresponds to the OS in use.
-    For example: https://storage.googleapis.com/chrome-for-testing-public/132.0.6834.159/win64/chrome-win64.zip
+
+    > __Tip!__ 
+    > <br>
+    > You can use the following __direct download link for Chrome v.138 for Windows 64-bit__: https://storage.googleapis.com/chrome-for-testing-public/138.0.7153.0/win64/chrome-win64.zip
+
 3. Download the zip file by pasting the URL in the browser and note the download folder.
 4. Open a File Explorer and browse to `Program Files` or `Program Files x86` depending on the OS in use.
-5. Create the following folder: Google\Chrome for Testing\Application
-6. Copy the downloaded zip file to this folder and extract it.
-7. Run the `setup.exe` in the same folder.
-
-## Setup Test Studio to use Chrome for Testing
-
-Once the Chrome for Testing setup is complete Test Studio starts using it automatically and no further adjustment is needed. 
-
-
-<script>
-window.addEventListener('DOMContentLoaded', function () {
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(e){
-        e.preventDefault();
-        $(this).toggleClass("active").next().slideToggle("normal");
-		$(this).find('#d').text(function (i, oldText) {
-        return $.trim(oldText) == '+' ? '-' : '+';
-		});
-		
-    });
-    });
-</script>
+5. Create the following folder under the selected `Program Files` one: `\Google\Chrome for Testing\Application`.
+6. Copy the downloaded zip file with the installation and extract it in the newly created folder.
+7. Run the `setup.exe` in that same folder `\Google\Chrome for Testing\Application`.
+
+>__Note__ 
+> <br>
+> Chrome for Testing doesn't update automatically. When you need a new version of the browser, use the same procedure to upgrade the Chrome for Testing. 
+
+## Setup Test Studio to Use Chrome for Testing
+
+Once the Chrome for Testing setup is complete Test Studio starts using it automatically and no further adjustment is needed.
diff --git a/docs/prerequisites/configure-your-browser/chrome.md b/docs/prerequisites/configure-your-browser/chrome.md
index b1f1cde6..8622c197 100644
--- a/docs/prerequisites/configure-your-browser/chrome.md
+++ b/docs/prerequisites/configure-your-browser/chrome.md
@@ -24,19 +24,3 @@ By default Test Studio projects are __configured to automate the Chrome browser
 > __Important__
 > <br>
 > The __Progress Telerik Test Studio Extension__ <a href="/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store" target="_blank">is missing in the Chrome Web Store</a> and is completely deprecated.
-
-
-<script>
-window.addEventListener('DOMContentLoaded', function () {
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(e){
-        e.preventDefault();
-        $(this).toggleClass("active").next().slideToggle("normal");
-		$(this).find('#d').text(function (i, oldText) {
-        return $.trim(oldText) == '+' ? '-' : '+';
-		});
-		
-    });
-    });
-</script>
diff --git a/docs/prerequisites/configure-your-browser/edge-chromium.md b/docs/prerequisites/configure-your-browser/edge-chromium.md
index b5689380..a3b9973e 100644
--- a/docs/prerequisites/configure-your-browser/edge-chromium.md
+++ b/docs/prerequisites/configure-your-browser/edge-chromium.md
@@ -24,23 +24,4 @@ By default Test Studio projects are __configured to automate the Edge Chromium b
 
 > __Important__
 > <br>
-> The __Progress Telerik Test Studio Extension__ <a href="/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store" target="_blank">is missing in the Chrome Web Store</a> and is completely deprecated.
-
-
-
-<script>
-window.addEventListener('DOMContentLoaded', function () {
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(e){
-        e.preventDefault();
-        $(this).toggleClass("active").next().slideToggle("normal");
-		$(this).find('#d').text(function (i, oldText) {
-        return $.trim(oldText) == '+' ? '-' : '+';
-		});
-		
-    });
-    });
-</script>
-
-
+> The __Progress Telerik Test Studio Extension__ <a href="/knowledge-base/browsers-kb/telerik-test-studio-extension-not-available-in-web-store" target="_blank">is missing in the Chrome Web Store</a> and is completely deprecated.
\ No newline at end of file
diff --git a/docs/prerequisites/configure-your-browser/firefox.md b/docs/prerequisites/configure-your-browser/firefox.md
index 25b93085..8baef0b4 100644
--- a/docs/prerequisites/configure-your-browser/firefox.md
+++ b/docs/prerequisites/configure-your-browser/firefox.md
@@ -15,7 +15,7 @@ position: 3
 }
 </style>
 
-# Configuring Firefox for Test Studio Automation#
+# Configuring Firefox for Test Studio Automation
 
 This document describes the steps to enable Firefox browser for test recording and execution.
 
@@ -30,183 +30,137 @@ Install the latest <a href="https://addons.mozilla.org/en-US/firefox/addon/progr
 
 ## 2. Browser Calibration
 
-To ensure a flawless and consistent automation process, there are a few browser settings that we need to apply. We call this **browser calibration** and have implemented a feature to <a href="/features/project-settings/browsers" target="_blank">**automatically calibrate the browser**</a> out of the box. No manual interaction is required.<br><br>
+To ensure a flawless and consistent automation process, there are a few browser settings that we need to apply. We call this **browser calibration** and have implemented a feature to <a href="/features/project-settings/browsers" target="_blank">**automatically calibrate the browser**</a> out of the box. No manual interaction is required.
 
 > __Tip__
 > <br>
 > <br>
-> You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).<br><br>
+> You can check all settings applied from the calibration in the <a href="#Manual_Configuration">Manual Configuration</a> section below (click the + sign to expand it).
 
 
-<p></p>
-<p></p>
+## Extension Install Procedure
 
-<p><hr></p>
-<p></p>
-<p></p>
+1.&nbsp; When you start recording against Firefox, but the Progress extension is not installed, the browser will load the recording start page and will try to load the extension. The recorder will search for the extension for the period that is defined in the *ClientReady* Timeout (the default is 60 seconds).
 
-<p class="trigger"><a name="Extension_Install" style="color:black; text-decoration: none;";> Extension Install Procedure <span id="d" style="color:#28a1e2";> + </span></a></p>
+<img src="/img/general-information/configure-your-browser/firefox/fig14.png" alt="Wait For Extension">
 
-<div class="toggle_container">
-<div class="block">
+2.&nbsp;  If the Progress extension doesn't load within the timeout period, a link to the Mozzila Extension Page will be displayed to install the extension.
 
-<hr/>
-<br>
+<img src="/img/general-information/configure-your-browser/firefox/fig10.png" alt="Get Extension">
 
-1.&nbsp; When you start recording against Firefox, but the Progress extension is not installed, the browser will load the recording start page and will try to load the extension. The recorder will search for the extension for the period that is defined in the *ClientReady* Timeout (the default is 60 seconds).<br><br>
+3.&nbsp; By clicking on <strong>Get It Free From Mozilla Extensions Page</strong> you will be directly navigated to the Progress extension on the Extension Page.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig14.png" alt="Wait For Extension"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig11.png" alt="Extension In Page">
 
-2.&nbsp;  If the Progress extension doesn't load within the timeout period, a link to the Mozzila Extension Page will be displayed to install the extension.<br><br>
+4.&nbsp; By clicking the <strong>Add to Firefox</strong> button the extension will be added after confirmation. 
 
-<img src="/img/general-information/configure-your-browser/firefox/fig10.png" alt="Get Extension"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig12.png" alt="Add Extension Confirmation">
 
-3.&nbsp; By clicking on <strong>Get It Free From Mozilla Extensions Page</strong> you will be directly navigated to the Progress extension on the Extension Page.<br><br>
+5.&nbsp; Click on the icon located to the right of the address bar to find the extension's version.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig11.png" alt="Extension In Page"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig13.png" alt="Extension Version">
 
-4.&nbsp; By clicking the <strong>Add to Firefox</strong> button the extension will be added after confirmation. <br><br>
+## Manual Configuration
 
-<img src="/img/general-information/configure-your-browser/firefox/fig12.png" alt="Add Extension Confirmation"><br><br>
-
-5.&nbsp; Click on the icon located to the right of the address bar to find the extension's version.<br><br>
-
-<img src="/img/general-information/configure-your-browser/firefox/fig13.png" alt="Extension Version"><br><br>
-
-<hr/>
-
-</div>
-</div>
-
-<p></p>
-<p></p>
-<p></p>
-
-<p class="trigger"><a name="Manual_Configuration" style="color:black; text-decoration: none;";> Manual Configuration <span id="d" style="color:#28a1e2";> + </span></a></p>
-
-<div class="toggle_container">
-<div class="block">
-	
-<h3>Enable Progress Test Studio Extension</h3>
+### Enable Progress Test Studio Extension
 
 Follow the steps below to manually configure Firefox for web automation with Test Studio.
 
-1. Click on the browser settings button in the upper right corner and select <strong>Add-ons</strong>.<br><br>
+1. Click on the browser settings button in the upper right corner and select <strong>Add-ons</strong>.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig1.png" alt="Extension"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig1.png" alt="Extension">
 
-2. Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.<br><br>
+2. Ensure that the <strong>Progress Test Studio Extension</strong> is enabled.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig2.png" alt="Extension"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig2.png" alt="Extension">
 
-<h3>Zoom Level Set to 100%</h3>
+### Zoom Level Set to 100%
 
 1. Click on the browser settings button.<br>
 
-2. Use the plus (+) and minus (-) buttons to set it to 100%.<br><br>
+2. Use the plus (+) and minus (-) buttons to set it to 100%.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig3.png" alt="Zoom"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig3.png" alt="Zoom">
 
-<h3>Turn Off Pop-up Blocker & Enable JavaScript</h3>
+### Turn Off Pop-up Blocker & Enable JavaScript
 
-1. Click on the browser settings button and select <strong>Options</strong>.<br><br>
+1. Click on the browser settings button and select <strong>Options</strong>.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig4.png" alt="Zoom"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig4.png" alt="Zoom">
 
-2. Click on the <strong>Privacy and Security</strong> tab (on the left side) and scroll down to <strong>Permissions</strong> section.<br><br>
+2. Click on the <strong>Privacy and Security</strong> tab (on the left side) and scroll down to <strong>Permissions</strong> section.
 
-3. Uncheck the <strong>Block pop-up windows</strong> checkbox.<br><br>
+3. Uncheck the <strong>Block pop-up windows</strong> checkbox.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig5.png" alt="Pop up blocker"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig5.png" alt="Pop up blocker">
 
-<h3>Pop-ups Open in a New Tab</h3>
+### Pop-ups Open in a New Tab
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 
-2. Scroll down to the <strong>Tabs</strong> section and check <strong>Open new windows in a new tab instead</strong>. <br><br>
+2. Scroll down to the <strong>Tabs</strong> section and check <strong>Open new windows in a new tab instead</strong>. 
 
-<img src="/img/general-information/configure-your-browser/firefox/fig6.png" alt="Pop up open in new window"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig6.png" alt="Pop up open in new window">
 
-<h3>Enable File Downloads</h3>
+### Enable File Downloads
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 
-2. Scroll down to the <strong>Downloads</strong> section and check and select <strong>Always ask you where to save files</strong>.<br><br>
+2. Scroll down to the <strong>Downloads</strong> section and check and select <strong>Always ask you where to save files</strong>.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig7.png" alt="Downloads"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig7.png" alt="Downloads">
 
-<h3>Enable Cookies</h3>
+### Enable Cookies
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 2. Click on <strong>Privacy and Security</strong>.<br>
-3. Scroll down to the <strong>History</strong> section to set the option to <strong>Remember history</strong>.<br><br>
+3. Scroll down to the <strong>History</strong> section to set the option to <strong>Remember history</strong>.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig8.png" alt="Cookies"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig8.png" alt="Cookies">
 
-<h3>Disable 'Remember passwords for sites'</h3>
+### Disable 'Remember passwords for sites'
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 2. Click on <strong>Privacy and Security</strong>.<br>
-3. Make sure the <strong>Remember logins and passwords for websites</strong> option is disabled.<br><br>
+3. Make sure the <strong>Remember logins and passwords for websites</strong> option is disabled.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig9.png" alt="Passwords"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig9.png" alt="Passwords">
 
-<h3>Set PDF Files to Be Always Saved</h3>
+### Set PDF Files to Be Always Saved
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 2. Locate the <strong>Applications</strong> section on the <strong>General Settings tab</strong>.<br>
-3. Set the PDF format file action to <strong>Save File</strong>.<br><br>
-
-<img src="/img/general-information/configure-your-browser/firefox/fig20.png" alt="Save PDF file"><br><br>
+3. Set the PDF format file action to <strong>Save File</strong>.
 
+<img src="/img/general-information/configure-your-browser/firefox/fig20.png" alt="Save PDF file">
 
-<h3>Use System Proxy Settings</h3>
+### Use System Proxy Settings
 
-As of the 2012 R1 version released in April 2012, set the Connection Settings to Use system proxy settings.<br><br>
+As of the 2012 R1 version released in April 2012, set the Connection Settings to Use system proxy settings.
 
 1. Click on the browser settings button and select <strong>Options</strong>.<br>
 2. Click on <strong>General</strong>.<br>
 3. Scroll down to the <strong>Network Proxy</strong> section and press on <strong>Settings... </strong> button.<br>
-4. In the <strong>Connection Settings</strong> window select <strong>Use system proxy settings</strong>.<br><br>
+4. In the <strong>Connection Settings</strong> window select <strong>Use system proxy settings</strong>.
 
-<img src="/img/general-information/configure-your-browser/firefox/fig15.png" alt="Proxy"><br><br>
+<img src="/img/general-information/configure-your-browser/firefox/fig15.png" alt="Proxy">
 
-<h3>Setting Configuration Flags</h3>
+### Setting Configuration Flags
 
 There are three more settings to be modified in the configuration editor -  type <strong>about:config</strong> in the url bar and press Enter to access it. Double click the following settings to set these to <strong>false</strong>:
 
-<ul>
-	<li> <strong>browser.sessionstore.resume_from_crash</strong> <br> <br> <img src="/img/general-information/configure-your-browser/firefox/fig16.png" alt="browser_sessionstore_resume_from_crash"> <br> </li>
-	<li> <strong>browser.tabs.warnOnClose</strong> <br> <br><img src="/img/general-information/configure-your-browser/firefox/fig17.png" alt="browser_tabs_warnOnClose"> <br></li>
-	<li> <strong>browser.tabs.warnOnCloseOtherTabs</strong> <br> <br> <img src="/img/general-information/configure-your-browser/firefox/fig18.png" alt="browser_tabs_warnOnCloseOtherTabs"> <br></li>
+- **browser.sessionstore.resume_from_crash**
+<img src="/img/general-information/configure-your-browser/firefox/fig16.png" alt="browser_sessionstore_resume_from_crash">
 
-</ul>
+- **browser.tabs.warnOnClose**
+<img src="/img/general-information/configure-your-browser/firefox/fig17.png" alt="browser_tabs_warnOnClose">
 
-<br>
+- **browser.tabs.warnOnCloseOtherTabs**
+<img src="/img/general-information/configure-your-browser/firefox/fig18.png" alt="browser_tabs_warnOnCloseOtherTabs">
 
-<h3>Disable Conflicting Extensions</h3>
+### Disable Conflicting Extensions
 
 The following Add-ons are known to conflict with the Progress Test Studio Extension: <br>
 
-<ul>
-	<li>AOL Messaging Toolbar</li>
-	<li>FoxyProxyStandard</li>
-</ul>
-
-</div>
-</div>
-
-<script>
-window.addEventListener('DOMContentLoaded', function () {
-$(".toggle_container").hide();
-    
-    $("p.trigger").click(function(e){
-        e.preventDefault();
-        $(this).toggleClass("active").next().slideToggle("normal");
-		$(this).find('#d').text(function (i, oldText) {
-        return $.trim(oldText) == '+' ? '-' : '+';
-		});
-		
-    });
-    });
-</script>
+- AOL Messaging Toolbar
+- FoxyProxyStandard
\ No newline at end of file
diff --git a/docs/prerequisites/installation/configure-windows-server.md b/docs/prerequisites/installation/configure-windows-server.md
deleted file mode 100644
index 3a283b1b..00000000
--- a/docs/prerequisites/installation/configure-windows-server.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Configure Windows Server
-page_title: Configuring Windows Server 2008/2012 for Test Automation
-description: "Test Studio Configuring Windows Server 2008/2012 for Test Automation"
-position: 9
-publish: false
----
-# Configuring Windows Server 2008/2012 for Test Automation #
-
-
-If you plan on running Telerik test automation on either Windows Server 2008 or 2012 and use IE, you will need to turn off the Windows component __Internet Explorer Enhanced Security Configuration__. This component is a great feature and highly recommended for machines actually being used as production servers. However, it interferes with test automation running against the IE browser.
-
-## Turn off Internet Explorer Enhanced Security Configuration on Windows Server 2012 ##
-
-1.	Open __Server Manager__.
-
-	![Server Manager](/img/general-information/installation/configure-windows-server/fig4.png)
-
-2. In the left pane, select the __Local Server__.
-
-	![Local Server](/img/general-information/installation/configure-windows-server/fig5.png)
-
-3. In the right pane under __Properties__, disable IE Enhanced Security Configuration.
-
-	![Properties](/img/general-information/installation/configure-windows-server/fig6.png)
-
-
-## Turn off Internet Explorer Enhanced Security Configuration on Windows Server 2008 ##
-
-1. Click __Start > Administrative Tools > Server Manager__.
-2. In the __Security Information__ section find and click on __Configure IE ESC__ (in the box on the right)
-
-	![Configure IE ESC](/img/general-information/installation/configure-windows-server/fig2.png)
-
-3. Turn off __IE ESC__ for both __Administrators__ and __Users__.
-
-	![Turn off IE ES](/img/general-information/installation/configure-windows-server/fig3.png)
-
-4. Click __OK__.
-5. Close __Server Manager__.
-
diff --git a/docs/prerequisites/installation/installation-consideration.md b/docs/prerequisites/installation/installation-consideration.md
index 4e51b13f..3e74b3ea 100644
--- a/docs/prerequisites/installation/installation-consideration.md
+++ b/docs/prerequisites/installation/installation-consideration.md
@@ -15,7 +15,7 @@ Before you install Test Studio, make sure that the following requirements are me
 - If you plan on running Test Studio test automation on Windows Server OS and use IE, <a href="#configuring-windows-server-for-test-studio-test-automation" target="_blank">turn off the __Windows component Internet Explorer Enhanced Security Configuration__</a>.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Visual Studio 2022 Installation Specifics
diff --git a/docs/prerequisites/installation/vs2017-compatibility.md b/docs/prerequisites/installation/vs2017-compatibility.md
deleted file mode 100644
index dc17f1f9..00000000
--- a/docs/prerequisites/installation/vs2017-compatibility.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: VS 2017 Compatibility
-page_title: VS 2017 Compatibility
-description: "Test Studio Compatibility with Visual Studio 2017. Prerequisites to install Test Studio plugin with Visual Studio 2017. Test Studio installed on Visual Studio 2017 but cannot start a test project. "
-position: 8
-publish: false
----
-# How to Install Visual Studio 2017 to Integrate Test Studio
-
-Visual Studio 2017 requires additional feature in its installation to be compatible with the Test Studio plugin for Visual Studio.
-
-Before installing Test Studio, you need to modify the Visual Studio 2017 installation and add the **Testing Tools Core Features** component under Debugging and Testing section. Once you enable this component complete the Visual Studio 2017 standard installation process and then perform the <a href="/prerequisites/installation/install-procedure" target="_blank">standard Test Studio installation</a>.
-
-![Visual Studio 2017 Installation][1]
-
-[1]: /img/general-information/installation/vs2017/vs2017installation.png
\ No newline at end of file
diff --git a/docs/prerequisites/license-activation/activating-your-license.md b/docs/prerequisites/license-activation/activating-your-license.md
index 12b1a16f..98888384 100644
--- a/docs/prerequisites/license-activation/activating-your-license.md
+++ b/docs/prerequisites/license-activation/activating-your-license.md
@@ -10,13 +10,18 @@ position: 1
 
 You can find the following topics in the article: 
 
-- [Launch Test Studio and Login](#launch-test-studio-and-login)
-- [Choose Test Studio Edition](#choose-test-studio-edition)
-- [Choose Test Studio License](#choose-test-studio-license)
-- [Possible troubles when activating the license](#possible-troubles)
+- [Activate Your Test Studio License](#activate-your-test-studio-license)
+  - [Launch Test Studio and Login](#launch-test-studio-and-login)
+    - [Direct Login](#direct-login)
+    - [SSO Login](#sso-login)
+  - [Choose Test Studio Edition](#choose-test-studio-edition)
+  - [Choose Test Studio License](#choose-test-studio-license)
+  - [Possible Troubles](#possible-troubles)
+    - [0 Seats Available](#0-seats-available)
+    - [Connection Error](#connection-error)
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-overview.html %}
+{% include cta-panel-overview.html %}
 {% endif %}
 
 ## Launch Test Studio and Login
diff --git a/docs/prerequisites/license-activation/manage-license.md b/docs/prerequisites/license-activation/manage-license.md
index 8e33099c..8d77b78c 100644
--- a/docs/prerequisites/license-activation/manage-license.md
+++ b/docs/prerequisites/license-activation/manage-license.md
@@ -40,10 +40,9 @@ Another option to deactivate the license is in the __Change License...__ screen
 ![Deactivate License from Manage window][14]
 
 [1]: /img/knowledge-base/activation-kb/change-trial-purchase/fig1.png
-[2]: /img/knowledge-base/activation-kb/change-trial-purchase/fig2.png
-[3]: /img/knowledge-base/activation-kb/change-trial-purchase/fig3.png
+
 
 [11]: /img/knowledge-base/activation-kb/change-trial-purchase/manage-license-info.png
 [12]: /img/knowledge-base/activation-kb/change-trial-purchase/change-purchased-license.png
-[13]: /img/knowledge-base/activation-kb/change-trial-purchase/welcome-screen-deactivate-license.png
+
 [14]: /img/knowledge-base/activation-kb/change-trial-purchase/change-license-deactivate.png
diff --git a/docs/redirect-tests-teststudio.csv b/docs/redirect-tests-teststudio.csv
new file mode 100644
index 00000000..19ebf97a
--- /dev/null
+++ b/docs/redirect-tests-teststudio.csv
@@ -0,0 +1,594 @@
+, /welcome
+/WELCOME, /welcome
+/advanced-topics/build-server/build-servers-test-execution, /automated-tests/continuous-integration/continious-integration-overview
+/advanced-topics/build-server/continious-integration-overview, /automated-tests/continuous-integration/continious-integration-overview
+/advanced-topics/build-server/mtm, /advanced-topics/build-server/azure-devops
+/advanced-topics/build-server/tfs-2017-builds, /advanced-topics/build-server/azure-devops
+/advanced-topics/build-server/tfs-builds, /automated-tests/continuous-integration/continious-integration-overview
+/advanced-topics/build-server/vs-team-services-builds, /advanced-topics/build-server/azure-devops
+/advanced-topics/coded-steps/add-assembly-reference, /automated-tests/coded-tests/add-assembly-reference
+/advanced-topics/coded-steps/code-behind-file, /automated-tests/coded-tests/coded-step#which-is-the-code-behind-file
+/advanced-topics/coded-steps/coded-step, /automated-tests/coded-tests/coded-step
+/archived-docs/recorder/overview, /welcome
+/archived-docs/recorder/recording-toolbar, /welcome
+/archived-docs/recorder/step-suggestions, /welcome
+/archived-docs/test, /welcome
+/automated-tests/coded-tests/standalone-code-file, /automated-tests/coded-tests/coded-step#which-is-the-standalone-code-file
+/automated-tests/customize-project/built-in-help-tools/guided-tutorials, /automated-tests/customize-project/built-in-help-tools/in-product-guides
+/automated-tests/load/advanced-topics/manage-windows-auth, /automated-tests/load/configuring-load-tests-quick-guide
+/automated-tests/scheduling/advanced-topics/change-service-account, /automated-tests/scheduling/overview
+/automated-tests/scheduling/advanced-topics/using-service-api, /automated-tests/scheduling/overview
+/automated-tests/scheduling/multiple-machines-scheduling-setup/create-storage-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/automated-tests/troubleshooting/troubleshooting-tools-tg/test, /welcome
+/automated-tests/vs-plugin/preview-code, /automated-tests/vs-plugin/convert-steps-code
+/features/coded-steps/add-assembly-reference, /automated-tests/coded-tests/add-assembly-reference
+/features/coded-steps/code-behind-file, /automated-tests/coded-tests/coded-step#which-is-the-code-behind-file
+/features/coded-steps/coded-step, /automated-tests/coded-tests/coded-step
+/features/coded-steps/compile-project, /automated-tests/coded-tests/compile-project
+/features/coded-steps/convert-steps-code, /automated-tests/vs-plugin/convert-steps-code#convert-all-steps-to-code
+/features/coded-steps/output-panel, /automated-tests/coded-tests/output-panel
+/features/coded-steps/preview-code, /automated-tests/vs-plugin/convert-steps-code
+/features/coded-steps/standalone-code-file, /automated-tests/coded-tests/coded-step#which-is-the-standalone-code-file
+/features/custom-layout/custom-layout, /automated-tests/customize-project/custom-layout
+/features/custom-steps/browser-refresh, /features/custom-steps/web-test-common/browser-refresh
+/features/custom-steps/capture-browser, /features/custom-steps/web-test-common/capture-browser
+/features/custom-steps/change-window-state, /features/custom-steps/wpf-common/change-window-state
+/features/custom-steps/check-js-errors, /features/custom-steps/web-test-common/check-js-errors
+/features/custom-steps/clear-browser-cache, /features/custom-steps/web-test-common/clear-browser-cache
+/features/custom-steps/comment, /features/custom-steps/all-tests-common/comment
+/features/custom-steps/custom-annotation, /features/custom-steps/all-tests-common/custom-annotation
+/features/custom-steps/execution-delay, /features/custom-steps/all-tests-common/execution-delay
+/features/custom-steps/inspection-point, /features/custom-steps/all-tests-common/inspection-point
+/features/custom-steps/manual-step, /features/custom-steps/all-tests-common/manual-step
+/features/custom-steps/maximize-browser, /features/custom-steps/web-test-common/maximize-browser
+/features/custom-steps/navigate-to, /features/custom-steps/web-test-common/navigate-to
+/features/custom-steps/open-pdf, /features/custom-steps/web-test-common/open-pdf
+/features/custom-steps/script-step, /features/custom-steps/all-tests-common/script-step
+/features/custom-steps/test-as-step, /features/custom-steps/all-tests-common/test-as-step
+/features/custom-steps/wait-for-url, /features/custom-steps/web-test-common/wait-for-url
+/features/data-driven-testing/attach-columns-verifications, /features/data-driven-testing/attach-columns-input-values
+/features/data-driven-testing/local-data-driven-tes, /automated-tests/data-drive-test/local-data-driven-test
+/features/data-driven-testing/local-data-driven-test, /automated-tests/data-drive-test/local-data-driven-test
+/features/data-driven-testing/multi-level-tests, /automated-tests/data-drive-test/multi-level-tests
+/features/data-driven-testing/overview, /automated-tests/data-drive-test/what-is-ddt
+/features/data-driven-testing/quick-execute-resultS, /automated-tests/data-drive-test/ddt-results#quick-execution-results
+/features/data-driven-testing/test-list-results, /automated-tests/data-drive-test/ddt-results#test-list-results
+/features/dialogs-and-popups/dialog-handler-updater, /prerequisites/configure-your-browser/browser-support-updater
+/features/dialogs-and-popups/modal-popups, /features/dialogs-and-popups/html-popups#modal-popups
+/features/elements-explorer/elements-find-expression, /automated-tests/elements/elements-find-expression
+/features/elements-explorer/find-element, /automated-tests/elements/find-element
+/features/elements-explorer/find-element-by-image, /automated-tests/elements/find-element-by-image
+/features/elements-explorer/frames, /automated-tests/elements/frames
+/features/elements-explorer/overview, /automated-tests/elements/overview
+/features/elements-menu/dom-explorer, /features/recorder/advanced-recording-tools/dom-explorer
+/features/elements-menu/overview, /automated-tests/recording/hover-over-highlighting
+/features/execute-apitest/add-api-test-as-step, /automated-tests/execute-apitest/add-api-test-as-step
+/features/execute-apitest/edit-integrated-api-project, /automated-tests/execute-apitest/edit-integrated-api-project
+/features/execute-apitest/passing-variables, /automated-tests/execute-apitest/passing-variables
+/features/project-settings/identification-logic, /features/project-settings/find-logic
+/features/project-settings/others, /features/project-settings/general
+/features/recorder/advanced-recording-tools/element-steps/actions/mouse-actions, /features/recorder/advanced-recording-tools/element-steps/actions/adv-mouse-actions
+/features/recorder/advanced-recording-tools/element-steps/actions/scroll-actions, /features/recorder/highlighting-menu/scroll-actions
+/features/recorder/advanced-recording-tools/element-steps/verifications/extraction, /features/recorder/highlighting-menu/quick-steps/extraction
+/features/recorder/advanced-recording-tools/element-steps/verifications/quick-verification, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/features/recorder/advanced-recording-tools/element-steps/verifications/wait, /features/recorder/highlighting-menu/quick-steps/wait
+/features/recorder/dom-explorer, /features/recorder/advanced-recording-tools/dom-explorer
+/features/recorder/mouse-actions/drag-and-drop, /features/recorder/advanced-recording-tools/element-steps/actions/drag-and-drop
+/features/recorder/mouse-actions/relative-mouse-actions, /features/recorder/highlighting-menu/mouse-actions
+/features/recorder/overview, /automated-tests/recording/overview
+/features/recorder/test-recorder, /automated-tests/recording/overview
+/features/recorder/verifications/advanced-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification
+/features/recorder/verifications/extraction, /features/recorder/highlighting-menu/quick-steps/extraction
+/features/recorder/verifications/image-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/image-verification
+/features/recorder/verifications/overview, /features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications
+/features/recorder/verifications/quick-verification, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/features/recorder/verifications/text-from-image, /features/recorder/advanced-recording-tools/element-steps/verifications/text-from-image
+/features/recorder/verifications/wait, /features/recorder/highlighting-menu/quick-steps/wait
+/features/scheduling-test-runs/advanced-topics/change-service-account, /automated-tests/scheduling/overview
+/features/scheduling-test-runs/advanced-topics/migrate-database, /welcome
+/features/scheduling-test-runs/advanced-topics/tts-command-line-client, /automated-tests/scheduling/advanced-topics/tts-command-line-client
+/features/scheduling-test-runs/advanced-topics/using-service-api, /automated-tests/scheduling/overview
+/features/scheduling-test-runs/change-service-account, /automated-tests/scheduling/overview
+/features/scheduling-test-runs/connect-to-scheduling-server, /automated-tests/scheduling/connect-to-scheduling-server
+/features/scheduling-test-runs/create-execution-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server
+/features/scheduling-test-runs/create-scheduling-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/features/scheduling-test-runs/create-storage-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/features/scheduling-test-runs/local-run-all-in-one, /automated-tests/scheduling/remote-scheduled-run
+/features/scheduling-test-runs/local-scheduled-run, /automated-tests/scheduling/remote-scheduled-run
+/features/scheduling-test-runs/migrate-database, /welcome
+/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-execution-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server
+/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-scheduling-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/features/scheduling-test-runs/multiple-machines-scheduling-setup/create-storage-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/features/scheduling-test-runs/multiple-machines-scheduling-setup/install-runtime, /automated-tests/scheduling/multiple-machines-scheduling-setup/install-runtime
+/features/scheduling-test-runs/overview, /automated-tests/scheduling/overview
+/features/scheduling-test-runs/remote-run-all-in-one, /automated-tests/scheduling/remote-scheduled-run
+/features/scheduling-test-runs/remote-scheduled-run, /automated-tests/scheduling/remote-scheduled-run
+/features/scheduling-test-runs/run-list-remotely, /automated-tests/scheduling/run-list-remotely
+/features/scheduling-test-runs/scheduling-results, /automated-tests/scheduling-results/scheduling-results
+/features/scheduling-test-runs/stop-cancel-scheduled-job, /automated-tests/scheduling/stop-cancel-scheduled-job
+/features/scheduling-test-runs/tts-command-line-client, /automated-tests/scheduling/advanced-topics/tts-command-line-client
+/features/scheduling-test-runs/using-service-api, /automated-tests/scheduling/overview
+/features/scheduling-test-runs/view-execution-status, /automated-tests/scheduling/view-execution-status
+/features/source-control/checkin-guidelines, /automated-tests/source-control/checkin-guidelines
+/features/source-control/git/branch-management, /automated-tests/source-control/git/branch-management
+/features/source-control/git/connect-to-git, /automated-tests/source-control/git/connect-to-git
+/features/source-control/git/open-git-project, /automated-tests/source-control/git/open-git-project
+/features/source-control/git/overview-git, /automated-tests/source-control/git/overview-git
+/features/source-control/git/supported-git-commands, /automated-tests/source-control/git/supported-git-commands
+/features/source-control/sc-alternatives, /automated-tests/source-control/sc-alternatives
+/features/source-control/tfs/connect-to-tfs, /automated-tests/source-control/tfs/connect-to-tfs
+/features/source-control/tfs/disconnect-from-tfs, /automated-tests/source-control/tfs/disconnect-from-tfs
+/features/source-control/tfs/open-tfs-project, /automated-tests/source-control/tfs/open-tfs-project
+/features/source-control/tfs/overview-tfs, /automated-tests/source-control/tfs/overview-tfs
+/features/source-control/tfs/project-item-options-tfs, /automated-tests/source-control/tfs/project-item-options-tfs
+/features/source-control/tfs/team-foundation-service, /automated-tests/source-control/tfs/team-foundation-service
+/features/test-maintenance/change-test-step-properties, /features/test-maintenance/test-step-properties
+/features/test-maintenance/convert-steps-code, /automated-tests/coded-tests/coded-step
+/features/test-maintenance/project-files-context-menu, /features/project-explorer/overview
+/features/test-maintenance/steps-pane-overview, /features/test-maintenance/steps-pane
+/features/test-maintenance/test-properties, /features/test-maintenance/test-properties-standalone
+/features/test-maintenance/test-properties-vs-plugin, /features/test-maintenance/test-properties-vs
+/features/testing-types, /features/testing-types/manual-testing/overview
+/features/testing-types/load-testing/add-custom-cookies, /automated-tests/load/designing-load-tests/modifying-tests#insert-a-custom-cookie-into-a-user-profile
+/features/testing-types/load-testing/adding-user-profiles, /automated-tests/load/designing-load-tests/adding-user-profiles
+/features/testing-types/load-testing/advanced-topics/configure-remote-device, /automated-tests/load/advanced-topics/configure-remote-device
+/features/testing-types/load-testing/advanced-topics/data-driving, /automated-tests/load/advanced-topics/data-driving
+/features/testing-types/load-testing/advanced-topics/manage-windows-auth, /automated-tests/load/configuring-load-tests-quick-guide
+/features/testing-types/load-testing/advanced-topics/monitor-perf-metrics, /automated-tests/load/advanced-topics/monitor-perf-metrics
+/features/testing-types/load-testing/analyzing-results, /automated-tests/load/load-testing-results/analyzing-results
+/features/testing-types/load-testing/best-practices, /automated-tests/load/running-load-test/best-practices
+/features/testing-types/load-testing/capturing-traffic, /automated-tests/load/designing-load-tests/adding-user-profiles#capturing-traffic
+/features/testing-types/load-testing/configure-remote-device, /automated-tests/load/advanced-topics/configure-remote-device
+/features/testing-types/load-testing/data-driving, /automated-tests/load/advanced-topics/data-driving
+/features/testing-types/load-testing/designing-load-tests/adding-user-profiles, /automated-tests/load/designing-load-tests/adding-user-profiles
+/features/testing-types/load-testing/designing-load-tests/dynamic-targets, /automated-tests/load/designing-load-tests/dynamic-targets
+/features/testing-types/load-testing/designing-load-tests/getting-started, /automated-tests/load/designing-load-tests/getting-started
+/features/testing-types/load-testing/designing-load-tests/managing-vu, /automated-tests/load/designing-load-tests/managing-vu
+/features/testing-types/load-testing/designing-load-tests/modifying-tests, /automated-tests/load/designing-load-tests/modifying-tests
+/features/testing-types/load-testing/designing-load-tests/test-settings, /automated-tests/load/designing-load-tests/test-settings
+/features/testing-types/load-testing/designing-tests, /automated-tests/load/designing-load-tests/getting-started
+/features/testing-types/load-testing/dynamic-targets, /automated-tests/load/designing-load-tests/dynamic-targets
+/features/testing-types/load-testing/export-results, /automated-tests/load/load-testing-results/export-results
+/features/testing-types/load-testing/filter-user-profile, /automated-tests/load/designing-load-tests/modifying-tests#filter-user-profile
+/features/testing-types/load-testing/importing-traffic, /automated-tests/load/designing-load-tests/adding-user-profiles#importing-traffic
+/features/testing-types/load-testing/load-testing-results/analyzing-results, /automated-tests/load/load-testing-results/analyzing-results
+/features/testing-types/load-testing/load-testing-results/export-results, /automated-tests/load/load-testing-results/export-results
+/features/testing-types/load-testing/load-testing-results/troubleshooting-results-errors, /automated-tests/load/load-testing-results/troubleshooting-results-errors
+/features/testing-types/load-testing/manage-windows-auth, /automated-tests/load/configuring-load-tests-quick-guide
+/features/testing-types/load-testing/managing-vu, /automated-tests/load/designing-load-tests/managing-vu
+/features/testing-types/load-testing/modifying-tests, /automated-tests/load/designing-load-tests/modifying-tests
+/features/testing-types/load-testing/monitor-perf-metrics, /automated-tests/load/advanced-topics/monitor-perf-metrics
+/features/testing-types/load-testing/overview, /automated-tests/load/overview
+/features/testing-types/load-testing/remote-load-test-execution, /automated-tests/load/running-load-test/remote-load-test-execution
+/features/testing-types/load-testing/running-load-test/best-practices, /automated-tests/load/running-load-test/best-practices
+/features/testing-types/load-testing/running-load-test/remote-load-test-execution, /automated-tests/load/running-load-test/remote-load-test-execution
+/features/testing-types/load-testing/running-load-test/running-tests, /automated-tests/load/running-load-test/running-tests
+/features/testing-types/load-testing/running-tests, /automated-tests/load/running-load-test/running-tests
+/features/testing-types/load-testing/test-settings, /automated-tests/load/designing-load-tests/test-settings
+/features/testing-types/load-testing/think-times, /automated-tests/load/designing-load-tests/modifying-tests#addremovechange-the-think-times
+/features/testing-types/load-testing/troubleshooting-results-errors, /automated-tests/load/load-testing-results/troubleshooting-results-errors
+/features/testing-types/performance-testing/compare-view, /automated-tests/performance/compare-view
+/features/testing-types/performance-testing/details-view, /automated-tests/performance/details-view
+/features/testing-types/performance-testing/export-results, /automated-tests/performance/export-results
+/features/testing-types/performance-testing/gather-perfomance-data, /automated-tests/performance/gather-perfomance-data
+/features/testing-types/performance-testing/history-view, /automated-tests/performance/history-view
+/features/testing-types/performance-testing/open-port-on-server, /automated-tests/performance/open-port-on-server
+/features/testing-types/performance-testing/overview, /automated-tests/performance/overview
+/features/testing-types/performance-testing/overview-button, /automated-tests/performance/overview-button
+/features/testing-types/responsive-test, /automated-tests/responsive/responsive-test
+/features/testing-types/wpf-test, /automated-tests/wpf/wpf-test
+/features/testing-types/wpf-testing/wpf-test, /automated-tests/wpf/wpf-test
+/features/verifications/Extraction, /features/recorder/highlighting-menu/quick-steps/extraction
+/features/verifications/Extraction.html, /features/recorder/highlighting-menu/quick-steps/extraction
+/features/verifications/advanced-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification
+/features/verifications/image-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/image-verification
+/features/verifications/overview, /features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications
+/features/verifications/quick-verification, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/features/verifications/wait, /features/recorder/highlighting-menu/quick-steps/wait
+/general-information/configure-your-browser/chrome, /prerequisites/configure-your-browser/chrome
+/general-information/configure-your-browser/edge, /prerequisites/configure-your-browser/edge-chromium
+/general-information/configure-your-browser/edge-chromium, /prerequisites/configure-your-browser/edge-chromium
+/general-information/configure-your-browser/firefox, /prerequisites/configure-your-browser/firefox
+/general-information/configure-your-browser/internet-explorer, /system-requirements
+/general-information/configure-your-browser/safari, /prerequisites/configure-your-browser/browser-configuration
+/general-information/create-test-standalone/add-test, /getting-started/first-test#add-a-test-to-the-project
+/general-information/create-test-standalone/silverlight-out-of-browser, /welcome
+/general-information/create-test-vsplugin/silverlight-out-of-browser, /welcome
+/general-information/create-test-vsplugin/web-test, /automated-tests/vs-plugin/web-test
+/general-information/create-test-vsplugin/wpf-test, /automated-tests/vs-plugin/wpf-test
+/general-information/for-developers, /welcome
+/general-information/for-qa-tester, /welcome
+/general-information/for-team-leads, /welcome
+/general-information/installation/activating-your-license, /prerequisites/license-activation/activating-your-license
+/general-information/installation/add-services, /prerequisites/installation/add-services
+/general-information/installation/check-for-updates, /prerequisites/installation/check-for-updates
+/general-information/installation/configure-windows-server, /prerequisites/installation/installation-consideration
+/general-information/installation/install-procedure, /prerequisites/installation/install-procedure
+/general-information/installation/manual-activation, /prerequisites/license-activation/manual-activation
+/general-information/installation/manual-download, /prerequisites/installation/manual-download
+/general-information/installation/re-activating-your-license, /prerequisites/license-activation/re-activating-your-license
+/general-information/installation/vs2017-compatibility, /prerequisites/installation/installation-consideration
+/general-information/start-a-project/guided-tutorials, /automated-tests/customize-project/built-in-help-tools/in-product-guides
+/general-information/start-a-project/in-product-guides, /automated-tests/customize-project/built-in-help-tools/in-product-guides
+/general-information/start-a-project/in-product-tips-tricks, /automated-tests/customize-project/built-in-help-tools/in-product-tips-tricks
+/general-information/start-a-project/welcome-screen, /automated-tests/customize-project/welcome-screen
+/general-information/test-execution/quick-execution, /automated-tests/test-execution/quick-execution
+/general-information/test-execution/test-list-execution, /automated-tests/test-lists/test-list-execution
+/general-information/test-execution/test-list-settings, /features/test-lists/test-list-settings
+/general-information/test-execution/test-lists-in-vs-2017-2019, /automated-tests/vs-plugin/test-lists-in-vs-2017-2019
+/general-information/test-execution/test-lists-standalone, /automated-tests/test-lists/test-lists-standalone
+/general-information/test-execution/test-lists-type-standalone, /automated-tests/test-lists/test-lists-standalone
+/general-information/test-execution/visual-debugger, /automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run
+/general-information/test-execution/visual-studio-2012-and-later-test-list, /welcome
+/general-information/test-execution/vs-2012-test-explorer, /automated-tests/vs-plugin/vs-test-explorer
+/general-information/test-execution/vs-test-explorer, /automated-tests/vs-plugin/vs-test-explorer
+/general-information/test-recording/frames, /automated-tests/elements/frames
+/general-information/test-recording/overview, /automated-tests/recording/overview
+/general-information/test-recording/recording-toolbar, /features/recorder/compact-recording-toolbar
+/general-information/test-recording/step-suggestions, /features/recorder/advanced-recording-tools/element-steps/steps-overview
+/general-information/test-recording/translators, /features/recorder/translators
+/general-information/test-results/analyze-quick-run-results, /automated-tests/test-results/analyze-quick-run-results
+/general-information/test-results/analyze-test-list-results, /automated-tests/test-list-results/analyze-test-list-results
+/general-information/test-results/calendar, /automated-tests/test-list-results/calendar
+/general-information/test-results/dashboard/about-page, /automated-tests/scheduling-results/dashboard/about-page
+/general-information/test-results/dashboard/installation-and-configuration, /automated-tests/scheduling-results/dashboard/installation-and-configuration
+/general-information/test-results/dashboard/overview, /automated-tests/scheduling-results/dashboard/overview
+/general-information/test-results/dashboard/reports, /automated-tests/scheduling-results/dashboard/reports
+/general-information/test-results/dashboard/results, /automated-tests/scheduling-results/dashboard/results
+/general-information/test-results/executive-dashboard, /automated-tests/scheduling-results/dashboard/overview
+/general-information/test-results/export-test-results, /automated-tests/test-list-results/export-test-results
+/general-information/test-results/quick-execute-test-step, /automated-tests/test-results/quick-execute-test-step
+/general-information/test-results/reports, /automated-tests/test-list-results/reports
+/general-information/test-results/step-failure-details, /automated-tests/test-results/step-failure-details
+/general-information/test-results/test-results-vs, /automated-tests/vs-plugin/test-results-vs
+/general-information/test-studio-framework, /test-studio-editions
+/general-information/test-studio-run-time, /test-studio-editions
+/getting-started/configure-your-browser/chrome, /prerequisites/configure-your-browser/chrome
+/getting-started/configure-your-browser/edge, /prerequisites/configure-your-browser/edge-chromium
+/getting-started/configure-your-browser/edgechromium, /prerequisites/configure-your-browser/edge-chromium
+/getting-started/configure-your-browser/firefox, /prerequisites/configure-your-browser/firefox
+/getting-started/configure-your-browser/internet-explorer, /system-requirements
+/getting-started/configure-your-browser/safari, /prerequisites/configure-your-browser/browser-configuration
+/getting-started/create-test-standalone/add-test, /getting-started/first-test#add-a-test-to-the-project
+/getting-started/create-test-standalone/load-test, /getting-started/first-test#add-a-test-to-the-project
+/getting-started/create-test-standalone/manual-test, /getting-started/first-test#add-a-test-to-the-project
+/getting-started/create-test-standalone/silverlight-out-of-browser, /welcome
+/getting-started/create-test-standalone/web-test, /getting-started/first-test#add-a-test-to-the-project
+/getting-started/create-test-standalone/wpf-test, /automated-tests/wpf/wpf-test
+/getting-started/create-test-vsplugin/silverlight-out-of-browser, /welcome
+/getting-started/create-test-vsplugin/web-test, /automated-tests/vs-plugin/web-test
+/getting-started/create-test-vsplugin/wpf-test, /automated-tests/vs-plugin/wpf-test
+/getting-started/installation-and-activation, /prerequisites/installation/install-procedure
+/getting-started/installation/activating-your-license, /prerequisites/license-activation/activating-your-license
+/getting-started/installation/add-services, /prerequisites/installation/add-services
+/getting-started/installation/check-for-updates, /prerequisites/installation/check-for-updates
+/getting-started/installation/configure-windows-server, /prerequisites/installation/installation-consideration
+/getting-started/installation/install-procedure, /prerequisites/installation/install-procedure
+/getting-started/installation/manual-activation, /prerequisites/license-activation/manual-activation
+/getting-started/installation/manual-download, /prerequisites/installation/manual-download
+/getting-started/installation/personal-data, /prerequisites/installation/installation-consideration
+/getting-started/installation/re-activating-your-license, /prerequisites/license-activation/re-activating-your-license
+/getting-started/installation/vs2017-compatability, /prerequisites/installation/installation-consideration
+/getting-started/start-a-project/in-product-tips-tricks, /automated-tests/customize-project/built-in-help-tools/in-product-tips-tricks
+/getting-started/start-a-project/welcome-screen, /automated-tests/customize-project/welcome-screen
+/getting-started/test-execution/quick-execution, /automated-tests/test-execution/quick-execution
+/getting-started/test-execution/test-list-execution, /automated-tests/test-lists/test-list-execution
+/getting-started/test-execution/test-list-settings, /features/test-lists/test-list-settings
+/getting-started/test-execution/test-lists-standalone, /automated-tests/test-lists/test-lists-standalone
+/getting-started/test-execution/test-lists-type-standalone, /automated-tests/test-lists/test-lists-standalone
+/getting-started/test-execution/visual-debugger, /automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run
+/getting-started/test-execution/visual-studio-2012-and-later-test-list, /welcome
+/getting-started/test-execution/visual-studio-test-list, /automated-tests/vs-plugin/test-lists-in-vs-2017-2019
+/getting-started/test-execution/vs-2012-test-explorer, /automated-tests/vs-plugin/vs-test-explorer
+/getting-started/test-recording/frames, /automated-tests/elements/frames
+/getting-started/test-recording/overview, /automated-tests/recording/overview
+/getting-started/test-recording/recording-toolbar, /features/recorder/compact-recording-toolbar
+/getting-started/test-recording/step-suggestions, /features/recorder/advanced-recording-tools/element-steps/steps-overview
+/getting-started/test-recording/translators, /features/recorder/translators
+/getting-started/test-results/analyze-test-results, /automated-tests/test-list-results/analyze-test-list-results
+/getting-started/test-results/quick-execute-test-step, /automated-tests/test-results/quick-execute-test-step
+/getting-started/test-results/quick-execution-test-step, /automated-tests/test-results/quick-execute-test-step
+/getting-started/test-results/step-failure-details, /automated-tests/test-results/step-failure-details
+/getting-started/test-results/test-results-vs, /automated-tests/vs-plugin/test-results-vs
+/index, /welcome
+/introduction/for-developers, /welcome
+/introduction/for-qa-tester, /welcome
+/introduction/for-team-leads, /welcome
+/introduction/test-studio-framework, /test-studio-editions
+/introduction/test-studio-run-time, /test-studio-editions
+/knowledge-base/data-driven-testing-kb/data-driven-test-with-mstest, /automated-tests/data-drive-test/what-is-ddt
+/knowledge-base/project-configuration-kb/anonymous-access-error-when-connecting-to-team-foundation-service, /automated-tests/source-control/checkin-guidelines
+/knowledge-base/project-configuration-kb/element-repository, /automated-tests/elements/element-repository
+/knowledge-base/project-configuration-kb/merge-page-nodes, /automated-tests/elements/merge-page-nodes
+/knowledge-base/project-configuration-kb/using-chained-find-expressions, /automated-tests/elements/using-chained-find-expressions
+/knowledge-base/scheduling-kb/keep-active-session, /knowledge-base/test-execution-kb/keep-active-session
+/knowledge-base/scheduling-kb/maintain-scheduling-services, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/knowledge-base/scheduling-kb/non-domain-environment, /automated-tests/scheduling/overview
+/knowledge-base/scheduling-kb/upload-latest-files, /automated-tests/scheduling/upload-latest-files
+/knowledge-base/silverlight-kb/automate-in-tfs-builds, /welcome
+/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel, /welcome
+/knowledge-base/silverlight-kb/silverlight-oob-and-elevated-trust, /welcome
+/knowledge-base/silverlight-kb/test, /welcome
+/knowledge-base/silverlight-kb/testing-framework-with-silverlight-oob-and-elevated-trust, /welcome
+/knowledge-base/test-execution-kb/locked-machine, /knowledge-base/scheduling-kb/locked-machine
+/knowledge-base/test-execution-kb/run-mobile-test-in-web-test, /welcome
+/knowledge-base/verification-kb/verify-silverlight-combobox-items, /welcome
+/knowledge-base/verification-kb/verify-silverlight-tool-tips, /welcome
+/knowledge-base/visual-studio-kb/convert-trx-to-html, /welcome
+/knowledge-base/visual-studio-kb/test-explorer-settings, /automated-tests/vs-plugin/test-explorer-settings
+/online-api-reference-1-1/test, /api
+/online-api-reference-2-0/test, /api
+/online-api-reference/test, /api
+/personal-data, https://www.progress.com/legal/privacy-policy
+/prerequisites/configure-your-browser/edge, /prerequisites/configure-your-browser/edge-chromium
+/prerequisites/configure-your-browser/internet-explorer, /prerequisites/configure-your-browser/edge-chromium
+/prerequisites/configure-your-browser/safari, /prerequisites/configure-your-browser/browser-configuration
+/test-studio-mobile/test, /welcome
+/testing-framework/api-reference, /api
+/testing-framework/api-reference/api-reference, /api
+/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files, /testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers
+/teststudioapi/test, /api
+/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value, /automated-tests/recording/overview#how-to-add-steps-in-the-test
+/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome, /prerequisites/configure-your-browser/chrome
+/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-edgechromium, /prerequisites/configure-your-browser/edge-chromium
+/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff, /prerequisites/configure-your-browser/firefox
+/troubleshooting-guide/browser-inconsistencies-tg/html-button, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/troubleshooting-guide/scheduling-issues-tg/no-change-button, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/troubleshooting-guide/scheduling-issues-tg/scheduling-service-shuts-down, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log, /automated-tests/troubleshooting/failing-test#test-studio-application-log
+/troubleshooting-guide/troubleshooting-tools-tg/using-the-dom-on-failure, /automated-tests/troubleshooting/failing-test#step-failure-details
+/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log, /automated-tests/troubleshooting/failing-test#execution-log-on-failure
+/troubleshooting-guide/troubleshooting-tools-tg/using-the-visual-debugger, /automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run
+/troubleshooting-guide/visual-studio-tg/enable-deployment, /automated-tests/vs-plugin/test-explorer-settings
+/user-guide.aspx, /welcome
+/user-guide/add-custom-step/change-window-state, /features/custom-steps/wpf-common/change-window-state
+/user-guide/add-custom-step/change-window-state.aspx, /features/custom-steps/wpf-common/change-window-state
+/user-guide/add-custom-step/comment, /features/custom-steps/all-tests-common/comment
+/user-guide/add-custom-step/comment.aspx, /features/custom-steps/all-tests-common/comment
+/user-guide/add-custom-step/custom-annotation, /features/custom-steps/all-tests-common/custom-annotation
+/user-guide/add-custom-step/custom-annotation.aspx, /features/custom-steps/all-tests-common/custom-annotation
+/user-guide/add-custom-step/script-step.aspx, /features/custom-steps/all-tests-common/script-step
+/user-guide/add-custom-step/test-as-step.aspx, /features/custom-steps/all-tests-common/test-as-step
+/user-guide/code-samples/general/extracted-variables-in-code, /advanced-topics/coded-samples/general/extracted-variables-in-code
+/user-guide/code-samples/general/extracted-variables-in-code.aspx, /advanced-topics/coded-samples/general/extracted-variables-in-code
+/user-guide/code-samples/general/relative-dialog-path, /advanced-topics/coded-samples/general/relative-dialog-path
+/user-guide/code-samples/html/ajax-postback, /testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support
+/user-guide/code-samples/html/dynamic-grid, /advanced-topics/coded-samples/html/dynamic-grid
+/user-guide/code-samples/html/dynamic-grid.aspx, /advanced-topics/coded-samples/html/dynamic-grid
+/user-guide/coded_steps, /automated-tests/coded-tests/coded-step
+/user-guide/coded_steps.aspx, /automated-tests/coded-tests/coded-step
+/user-guide/coded_steps/add-an-assembly-reference, /automated-tests/coded-tests/add-assembly-reference
+/user-guide/coded_steps/add-an-assembly-reference.aspx, /automated-tests/coded-tests/add-assembly-reference
+/user-guide/coded_steps/code-behind-file, /automated-tests/coded-tests/coded-step#which-is-the-code-behind-file
+/user-guide/coded_steps/code-behind-file.aspx, /automated-tests/coded-tests/coded-step#which-is-the-code-behind-file
+/user-guide/command-line-test-execution, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution.aspx, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution/artoftestrunner, /features/test-runners/artoftest-runner
+/user-guide/command-line-test-execution/artoftestrunner.aspx, /features/test-runners/artoftest-runner
+/user-guide/command-line-test-execution/continuous-integration/continuous-integration-environments, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution/continuous-integration/continuous-integration-environments.aspx, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution/continuous-integration/cruisecontrol-net, /advanced-topics/build-server/cruise-control.net-builds
+/user-guide/command-line-test-execution/continuous-integration/cruisecontrol-net.aspx, /advanced-topics/build-server/cruise-control.net-builds
+/user-guide/command-line-test-execution/continuous-integration/team-foundation-server-builds, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution/continuous-integration/team-foundation-server-builds.aspx, /automated-tests/continuous-integration/continious-integration-overview
+/user-guide/command-line-test-execution/continuous-integration/teamcity, /advanced-topics/build-server/team-city-builds
+/user-guide/command-line-test-execution/continuous-integration/teamcity.aspx, /advanced-topics/build-server/team-city-builds
+/user-guide/configure-your-browser/chrome, /prerequisites/configure-your-browser/chrome
+/user-guide/configure-your-browser/chrome.aspx, /prerequisites/configure-your-browser/chrome
+/user-guide/configure-your-browser/firefox, /prerequisites/configure-your-browser/firefox
+/user-guide/configure-your-browser/firefox.aspx, /prerequisites/configure-your-browser/firefox
+/user-guide/configure-your-browser/internet-explorer, /system-requirements
+/user-guide/configure-your-browser/internet-explorer.aspx, /system-requirements
+/user-guide/configure-your-browser/safari.aspx, /prerequisites/configure-your-browser/browser-configuration
+/user-guide/create-a-test-vs-plugin/web-test, /automated-tests/vs-plugin/web-test
+/user-guide/create-a-test-vs-plugin/web-test.aspx, /automated-tests/vs-plugin/web-test
+/user-guide/create-a-test-vs-plugin/wpf-test, /automated-tests/vs-plugin/wpf-test
+/user-guide/create-a-test-vs-plugin/wpf-test.aspx, /automated-tests/vs-plugin/wpf-test
+/user-guide/data-driven-testing, /automated-tests/data-drive-test/what-is-ddt
+/user-guide/data-driven-testing.aspx, /automated-tests/data-drive-test/what-is-ddt
+/user-guide/data-driven-testing/add-a-data-source, /features/data-driven-testing/add-data-source
+/user-guide/data-driven-testing/add-a-data-source.aspx, /features/data-driven-testing/add-data-source
+/user-guide/data-driven-testing/attach-columns-to-input-values, /features/data-driven-testing/attach-columns-input-values
+/user-guide/data-driven-testing/attach-columns-to-input-values.aspx, /features/data-driven-testing/attach-columns-input-values
+/user-guide/data-driven-testing/attach-columns-to-verifications, /features/data-driven-testing/attach-columns-input-values
+/user-guide/data-driven-testing/attach-columns-to-verifications.aspx, /features/data-driven-testing/attach-columns-input-values
+/user-guide/data-driven-testing/local-data-driven-test, /automated-tests/data-drive-test/local-data-driven-test
+/user-guide/data-driven-testing/local-data-driven-test.aspx, /automated-tests/data-drive-test/local-data-driven-test
+/user-guide/data-driven-testing/manage-data-source, /features/data-driven-testing/manage-external-data-source
+/user-guide/data-driven-testing/manage-data-source.aspx, /features/data-driven-testing/manage-external-data-source
+/user-guide/dialogs-and-popups/dialogs, /features/dialogs-and-popups/dialogs
+/user-guide/dialogs-and-popups/dialogs.aspx, /features/dialogs-and-popups/dialogs
+/user-guide/dialogs-and-popups/html-popups, /features/dialogs-and-popups/html-popups
+/user-guide/dialogs-and-popups/html-popups.aspx, /features/dialogs-and-popups/html-popups
+/user-guide/dialogs-and-popups/modal-popups, /features/dialogs-and-popups/html-popups#modal-popups
+/user-guide/dialogs-and-popups/modal-popups.aspx, /features/dialogs-and-popups/html-popups#modal-popups
+/user-guide/elements-menu/dom-explorer, /features/recorder/advanced-recording-tools/dom-explorer
+/user-guide/elements-menu/dom-explorer.aspx, /features/recorder/advanced-recording-tools/dom-explorer
+/user-guide/getting-started/using-telerik-testing-framework, /testing-framework/getting-started
+/user-guide/getting-started/using-telerik-testing-framework.aspx, /testing-framework/getting-started
+/user-guide/installation/activating-your-license, /prerequisites/license-activation/activating-your-license
+/user-guide/installation/activating-your-license.aspx, /prerequisites/license-activation/activating-your-license
+/user-guide/installation/change_storage_service_account.aspx, /automated-tests/scheduling/overview
+/user-guide/installation/check_for_updates, /prerequisites/installation/check-for-updates
+/user-guide/installation/check_for_updates.aspx, /prerequisites/installation/check-for-updates
+/user-guide/installation/configure-windows-server, /prerequisites/installation/installation-consideration
+/user-guide/installation/configure-windows-server.aspx, /prerequisites/installation/installation-consideration
+/user-guide/installation/install-procedure, /prerequisites/installation/install-procedure
+/user-guide/installation/install-procedure.aspx, /prerequisites/installation/install-procedure
+/user-guide/installation/manual-activation, /prerequisites/license-activation/manual-activation
+/user-guide/installation/manual-activation.aspx, /prerequisites/license-activation/manual-activation
+/user-guide/installation/manual_download, /prerequisites/installation/manual-download
+/user-guide/installation/manual_download.aspx, /prerequisites/installation/manual-download
+/user-guide/installation/re-activate-your-license, /prerequisites/license-activation/re-activating-your-license
+/user-guide/installation/re-activate-your-license.aspx, /prerequisites/license-activation/re-activating-your-license
+/user-guide/installation/trial-services, /prerequisites/installation/add-services
+/user-guide/installation/trial-services.aspx, /prerequisites/installation/add-services
+/user-guide/knowledge-base/best-practices/generate-application-log, /knowledge-base/best-practices-kb/generate-application-log
+/user-guide/knowledge-base/best-practices/generate-application-log.aspx, /knowledge-base/best-practices-kb/generate-application-log
+/user-guide/knowledge-base/data-driven-testing/dynamic-data-binding, /knowledge-base/data-driven-testing-kb/dynamic-data-binding
+/user-guide/knowledge-base/data-driven-testing/extracted-variables-in-code.aspx, /advanced-topics/coded-samples/general/extracted-variables-in-code
+/user-guide/knowledge-base/data-driven-testing/repeating-actions-for-multiple-users, /knowledge-base/data-driven-testing-kb/multiple-users-with-login
+/user-guide/knowledge-base/dialogs-popups/unexpected-dialog-action, /knowledge-base/dialogs-and-popups-kb/unexpected-dialog-action
+/user-guide/knowledge-base/project-configuration/element-repository, /automated-tests/elements/element-repository
+/user-guide/knowledge-base/project-configuration/register-certificate-for-https-connection, /knowledge-base/project-configuration-kb/register-certificate
+/user-guide/knowledge-base/project-configuration/register-certificate-for-https-connection.aspx, /knowledge-base/project-configuration-kb/register-certificate
+/user-guide/knowledge-base/scheduling/resolve-common-scheduling-issues, /troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely
+/user-guide/knowledge-base/silverlight/automate-silverlight-tests-in-tfs-builds, /welcome
+/user-guide/knowledge-base/silverlight/out-of-browser-and-elevated-trust, /welcome
+/user-guide/knowledge-base/test-automation/ample-timeouts, /knowledge-base/test-automation-kb/ample-timetouts
+/user-guide/knowledge-base/test-automation/dynamically-generated-id-attributes, /knowledge-base/test-automation-kb/dynamic-ids
+/user-guide/knowledge-base/test-automation/invoke-mouse-hover, /knowledge-base/test-automation-kb/invoke-mouse-hover
+/user-guide/knowledge-base/test-execution/execute-custom-scripts-before-after-test, /advanced-topics/coded-samples/general/custom-scripts-before-after
+/user-guide/knowledge-base/test-execution/using-baseurl, /knowledge-base/test-execution-kb/base-url
+/user-guide/knowledge-base/test-execution/using-baseurl.aspx, /knowledge-base/test-execution-kb/base-url
+/user-guide/knowledge-base/verification/verify-the-disabled-attribute-html, /knowledge-base/verification-kb/disabled-attribute-html
+/user-guide/knowledge-base/verification/verify-tool-tips, /knowledge-base/verification-kb/verify-html-tool-tips
+/user-guide/load-testing, /automated-tests/load/overview
+/user-guide/load-testing.aspx, /automated-tests/load/overview
+/user-guide/load-testing/designing-load-tests/adding-user-profiles/capture-remote-traffic.aspx, /automated-tests/load/advanced-topics/configure-remote-device
+/user-guide/load-testing/load-analyzing-results.aspx, /automated-tests/load/load-testing-results/analyzing-results
+/user-guide/load-testing/load-managing-users.aspx, /automated-tests/load/designing-load-tests/managing-vu
+/user-guide/load-testing/load-running-tests.aspx, /automated-tests/load/running-load-test/running-tests
+/user-guide/modifying-tests/change-step-target-element, /features/test-maintenance/change-step-target-element
+/user-guide/modifying-tests/change-step-target-element.aspx, /features/test-maintenance/change-step-target-element
+/user-guide/modifying-tests/change-test-step-properties, /features/test-maintenance/test-step-properties
+/user-guide/modifying-tests/change-test-step-properties.aspx, /features/test-maintenance/test-step-properties
+/user-guide/modifying-tests/convert-all-steps-to-code, /automated-tests/coded-tests/coded-step
+/user-guide/modifying-tests/convert-all-steps-to-codes.aspx, /automated-tests/coded-tests/coded-step
+/user-guide/modifying-tests/properties-pane.aspx, /features/test-maintenance/test-properties-standalone
+/user-guide/modifying-tests/reorder-test-steps, /features/test-maintenance/reorder-test-steps
+/user-guide/modifying-tests/reorder-test-steps.aspx, /features/test-maintenance/reorder-test-steps
+/user-guide/modifying-tests/search_test_steps, /features/test-maintenance/search-test-steps
+/user-guide/modifying-tests/search_test_steps.aspx, /features/test-maintenance/search-test-steps
+/user-guide/modifying-tests/steps-pane-overview, /features/test-maintenance/steps-pane
+/user-guide/modifying-tests/steps-pane-overview.aspx, /features/test-maintenance/steps-pane
+/user-guide/modifying-tests/storyboard, /features/test-maintenance/storyboard
+/user-guide/modifying-tests/storyboard.aspx, /features/test-maintenance/storyboard
+/user-guide/modifying-tests/test-properties, /features/test-maintenance/test-properties-standalone
+/user-guide/modifying-tests/test-properties-vs-plugin, /features/test-maintenance/test-properties-vs
+/user-guide/modifying-tests/test-properties-vs-plugin.aspx, /features/test-maintenance/test-properties-vs
+/user-guide/modifying-tests/test-properties.aspx, /features/test-maintenance/test-properties-standalone
+/user-guide/modifying-tests/test-test-step-context-menu, /features/test-maintenance/test-step-context-menu
+/user-guide/modifying-tests/test-test-step-context-menu.aspx, /features/test-maintenance/test-step-context-menu
+/user-guide/overview, /welcome
+/user-guide/overview.aspx, /welcome
+/user-guide/overview/for-developers, /welcome
+/user-guide/overview/for-developers.aspx, /welcome
+/user-guide/overview/for-team-leads, /welcome
+/user-guide/overview/for-team-leads.aspx, /welcome
+/user-guide/overview/test-studio-vs-framework, /test-studio-editions
+/user-guide/overview/test-studio-vs-framework.aspx, /test-studio-editions
+/user-guide/overview/test-studio-vs-run-time, /test-studio-editions
+/user-guide/overview/test-studio-vs-run-time.aspx, /test-studio-editions
+/user-guide/overview/webui_for_qa_testers, /welcome
+/user-guide/overview/webui_for_qa_testers.aspx, /welcome
+/user-guide/performance, /automated-tests/performance/overview
+/user-guide/performance.aspx, /automated-tests/performance/overview
+/user-guide/performance/compare-view, /automated-tests/performance/compare-view
+/user-guide/performance/compare-view.aspx, /automated-tests/performance/compare-view
+/user-guide/performance/details-view, /automated-tests/performance/details-view
+/user-guide/performance/details-view.aspx, /automated-tests/performance/details-view
+/user-guide/performance/export_results, /automated-tests/performance/export-results
+/user-guide/performance/export_results.aspx, /automated-tests/performance/export-results
+/user-guide/performance/gather-performance-data, /automated-tests/performance/gather-perfomance-data
+/user-guide/performance/gather-performance-data.aspx, /automated-tests/performance/gather-perfomance-data
+/user-guide/performance/history-view, /automated-tests/performance/history-view
+/user-guide/performance/history-view.aspx, /automated-tests/performance/history-view
+/user-guide/performance/open-port-on-server, /automated-tests/performance/open-port-on-server
+/user-guide/performance/open-port-on-server.aspx, /automated-tests/performance/open-port-on-server
+/user-guide/performance/overview, /automated-tests/performance/overview-button
+/user-guide/performance/overview.aspx, /automated-tests/performance/overview-button
+/user-guide/project-settings, /features/project-settings/overview
+/user-guide/project-settings.aspx, /features/project-settings/overview
+/user-guide/project-settings/browsers, /features/project-settings/browsers
+/user-guide/project-settings/browsers.aspx, /features/project-settings/browsers
+/user-guide/project-settings/recording-options, /features/project-settings/recording-options
+/user-guide/project-settings/recording-options.aspx, /features/project-settings/recording-options
+/user-guide/project-settings/script-options, /features/project-settings/script-options
+/user-guide/project-settings/script-options.aspx, /features/project-settings/script-options
+/user-guide/project-settings/translators, /features/project-settings/translators
+/user-guide/project-settings/translators.aspx, /features/project-settings/translators
+/user-guide/recording-tests, /automated-tests/recording/overview
+/user-guide/recording-tests.aspx, /automated-tests/recording/overview
+/user-guide/recording-tests/frames, /automated-tests/elements/frames
+/user-guide/recording-tests/frames.aspx, /automated-tests/elements/frames
+/user-guide/recording-tests/recording-toolbar, /features/recorder/compact-recording-toolbar
+/user-guide/recording-tests/recording-toolbar.aspx, /features/recorder/compact-recording-toolbar
+/user-guide/recording-tests/step-suggestions, /features/recorder/advanced-recording-tools/element-steps/steps-overview
+/user-guide/recording-tests/step-suggestions.aspx, /features/recorder/advanced-recording-tools/element-steps/steps-overview
+/user-guide/recording-tests/translators, /features/recorder/translators
+/user-guide/recording-tests/translators.aspx, /features/recorder/translators
+/user-guide/scheduling-test-runs, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs.aspx, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs/cancel-scheduled-job, /automated-tests/scheduling/stop-cancel-scheduled-job
+/user-guide/scheduling-test-runs/cancel-scheduled-job.aspx, /automated-tests/scheduling/stop-cancel-scheduled-job
+/user-guide/scheduling-test-runs/change-service-account, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs/change-service-account.aspx, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs/connect-a-project-to-a-scheduling-server, /automated-tests/scheduling/view-execution-status
+/user-guide/scheduling-test-runs/connect-a-project-to-a-scheduling-server.aspx, /automated-tests/scheduling/view-execution-status
+/user-guide/scheduling-test-runs/create-a-scheduling-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/user-guide/scheduling-test-runs/create-a-scheduling-server.aspx, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/user-guide/scheduling-test-runs/create-an-execution-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server
+/user-guide/scheduling-test-runs/create-an-execution-server.aspx, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-execution-server
+/user-guide/scheduling-test-runs/create-storage-server, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/user-guide/scheduling-test-runs/create-storage-server.aspx, /automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server
+/user-guide/scheduling-test-runs/machine-status, /automated-tests/scheduling/connect-to-scheduling-server
+/user-guide/scheduling-test-runs/machine-status.aspx, /automated-tests/scheduling/connect-to-scheduling-server
+/user-guide/scheduling-test-runs/run-list-remotely, /automated-tests/scheduling/run-list-remotely
+/user-guide/scheduling-test-runs/run-list-remotely.aspx, /automated-tests/scheduling/run-list-remotely
+/user-guide/scheduling-test-runs/schedule-test-execution, /automated-tests/scheduling/schedule-execution
+/user-guide/scheduling-test-runs/schedule-test-execution.aspx, /automated-tests/scheduling/schedule-execution
+/user-guide/scheduling-test-runs/scheduling-results, /automated-tests/scheduling-results/scheduling-results
+/user-guide/scheduling-test-runs/scheduling-results.aspx, /automated-tests/scheduling-results/scheduling-results
+/user-guide/scheduling-test-runs/service-apis, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs/service-apis.aspx, /automated-tests/scheduling/overview
+/user-guide/scheduling-test-runs/telerik-teststudio-commandline-client, /automated-tests/scheduling/advanced-topics/tts-command-line-client
+/user-guide/scheduling-test-runs/telerik-teststudio-commandline-client.aspx, /automated-tests/scheduling/advanced-topics/tts-command-line-client
+/user-guide/test-execution/quick-execution, /automated-tests/test-execution/quick-execution
+/user-guide/test-execution/quick-execution.aspx, /automated-tests/test-execution/quick-execution
+/user-guide/test-execution/standalone-test-list-type, /automated-tests/test-lists/test-lists-standalone
+/user-guide/test-execution/standalone-test-list-type.aspx, /automated-tests/test-lists/test-lists-standalone
+/user-guide/test-execution/standalone-test-lists, /automated-tests/test-lists/test-lists-standalone
+/user-guide/test-execution/standalone-test-lists.aspx, /automated-tests/test-lists/test-lists-standalone
+/user-guide/test-execution/test-list-settings, /features/test-lists/test-list-settings
+/user-guide/test-execution/test-list-settings.aspx, /features/test-lists/test-list-settings
+/user-guide/test-execution/visual-debugger, /automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run
+/user-guide/test-execution/visual-debugger.aspx, /automated-tests/troubleshooting/visual-debugger#make-use-of-the-visual-debugger-tool-options-during-test-run
+/user-guide/test-execution/visual-studio-2012-test-explorer, /automated-tests/vs-plugin/vs-test-explorer
+/user-guide/test-execution/visual-studio-2012-test-explorer.aspx, /automated-tests/vs-plugin/vs-test-explorer
+/user-guide/test-results/step-failure-details, /automated-tests/test-results/step-failure-details
+/user-guide/test-results/step-failure-details.aspx, /automated-tests/test-results/step-failure-details
+/user-guide/test-results/test-as-step-results, /automated-tests/test-results/quick-execute-test-step
+/user-guide/test-results/test-as-step-results.aspx, /automated-tests/test-results/quick-execute-test-step
+/user-guide/test-results/test-results-vs-plugin, /automated-tests/vs-plugin/test-results-vs
+/user-guide/test-results/test-results-vs-plugin.aspx, /automated-tests/vs-plugin/test-results-vs
+/user-guide/test-runners/artoftestrunner, /features/test-runners/artoftest-runner
+/user-guide/test-runners/artoftestrunner.aspx, /features/test-runners/artoftest-runner
+/user-guide/troubleshooting_guide/installation-problems/create-installer-log-file, /troubleshooting-guide/installation-problems-tg/create-installer-log-file
+/user-guide/troubleshooting_guide/recording-problems/hover-over-highlighting-is-misaligned, /troubleshooting-guide/recording-problems-tg/highlighting-misaligned
+/user-guide/troubleshooting_guide/recording-problems/hover-over-highlighting-is-misaligned.aspx, /troubleshooting-guide/recording-problems-tg/highlighting-misaligned
+/user-guide/troubleshooting_guide/recording-problems/namespace-reservation, /welcome
+/user-guide/troubleshooting_guide/test-execution-problems/cannot-execute-in-chrome, /prerequisites/configure-your-browser/browser-configuration
+/user-guide/troubleshooting_guide/test-execution-problems/if-else-logical-step-fails, /troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails
+/user-guide/troubleshooting_guide/test-execution-problems/if-else-logical-step-fails.aspx, /troubleshooting-guide/test-execution-problems-tg/if-else-logical-step-fails
+/user-guide/troubleshooting_guide/test-execution-problems/invoke-blind-mouse-click, /troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click
+/user-guide/troubleshooting_guide/test-execution-problems/localhost-dynamic-ports, /automated-tests/test-execution/quick-execution
+/user-guide/troubleshooting_guide/test-execution-problems/missing-page-elements.aspx, /troubleshooting-guide/test-execution-problems-tg/missing-page-elements
+/user-guide/troubleshooting_guide/test-execution-problems/pages-not-defined.aspx, /troubleshooting-guide/test-execution-problems-tg/pages-not-defined
+/user-guide/troubleshooting_guide/test-execution-problems/unable-to-locate-element, /troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element
+/user-guide/troubleshooting_guide/test-execution-problems/unable-to-locate-element.aspx, /troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element
+/user-guide/troubleshooting_guide/visual-studio/enable-deployment, /automated-tests/vs-plugin/test-explorer-settings
+/user-guide/troubleshooting_guide/visual-studio/missing-assembly-references, /troubleshooting-guide/visual-studio-tg/missing-assembly-references
+/user-guide/troubleshooting_guide/visual-studio/missing-assembly-references.aspx, /troubleshooting-guide/visual-studio-tg/missing-assembly-references
+/user-guide/verifications, /features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications
+/user-guide/verifications.aspx, /features/recorder/advanced-recording-tools/element-steps/steps-overview#verifications
+/user-guide/verifications/advanced-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification
+/user-guide/verifications/advanced-verification.aspx, /features/recorder/advanced-recording-tools/element-steps/verifications/advanced-verification
+/user-guide/verifications/data-bind-an-extraction-step, /features/recorder/highlighting-menu/quick-steps/extraction
+/user-guide/verifications/data-bind-an-extraction-step.aspx, /features/recorder/highlighting-menu/quick-steps/extraction
+/user-guide/verifications/image-verification, /features/recorder/advanced-recording-tools/element-steps/verifications/image-verification
+/user-guide/verifications/image-verification.aspx, /features/recorder/advanced-recording-tools/element-steps/verifications/image-verification
+/user-guide/verifications/quick-verification, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/user-guide/verifications/quick-verification.aspx, /features/recorder/highlighting-menu/quick-steps/quick-verification
+/user-guide/verifications/wait, /features/recorder/highlighting-menu/quick-steps/wait
+/user-guide/verifications/wait.aspx, /features/recorder/highlighting-menu/quick-steps/wait
\ No newline at end of file
diff --git a/docs/samples/DemoMobileProject.zip b/docs/samples/DemoMobileProject.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/HandleAndroidSystemDialog.zip b/docs/samples/HandleAndroidSystemDialog.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileRuntime-Linux.zip b/docs/samples/MobileRuntime-Linux.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileRuntime-MacOs.zip b/docs/samples/MobileRuntime-MacOs.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileRuntime-Windows.zip b/docs/samples/MobileRuntime-Windows.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileTestingAgentForSimulator.zip b/docs/samples/MobileTestingAgentForSimulator.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileTestingExtension_Android.zip b/docs/samples/MobileTestingExtension_Android.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileTestingExtension_Hybrid.zip b/docs/samples/MobileTestingExtension_Hybrid.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/MobileTestingExtension_iOS.zip b/docs/samples/MobileTestingExtension_iOS.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/androidDemoApplication.zip b/docs/samples/androidDemoApplication.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/cordovaDemoApplication.zip b/docs/samples/cordovaDemoApplication.zip
old mode 100644
new mode 100755
diff --git a/docs/samples/xCodeDemoApplication.zip b/docs/samples/xCodeDemoApplication.zip
old mode 100644
new mode 100755
diff --git a/docs/system-requirements.md b/docs/system-requirements.md
index 4830e8b6..bfdf47b2 100644
--- a/docs/system-requirements.md
+++ b/docs/system-requirements.md
@@ -152,7 +152,7 @@ table{width: 100%; border-spacing: 0; border-collapse: collapse; background-colo
 
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 
@@ -170,7 +170,10 @@ Admin permissions are required for:
 
 	* Visual Studio projects target a version between .NET Framework 4.7.2 to 4.8.1.
     * Visual Studio 2022 requires <a href="/prerequisites/installation/installation-consideration#visual-studio-2022-installation-specifics" target="_blank">minimum selection of components</a> to add in its installation.
-	
+
+> **Important** 
+><br>
+> Test Studio ends support for Visual Studio 2019 at the beginning of 2026. 
 
 ## .NET Framework
 
diff --git a/docs/test-studio-editions.md b/docs/test-studio-editions.md
index f78793b3..b7792b5d 100644
--- a/docs/test-studio-editions.md
+++ b/docs/test-studio-editions.md
@@ -14,7 +14,7 @@ The **Test Studio** tool consists of a few different modules, which are packed i
 > Licensing is managed on a per machine basis. Each VM is considered a machine and must be licensed.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Test Studio Standalone Application
diff --git a/docs/test-studio-mobile/api-reference/andorid.md b/docs/test-studio-mobile/api-reference/andorid.md
deleted file mode 100644
index 415c2318..00000000
--- a/docs/test-studio-mobile/api-reference/andorid.md
+++ /dev/null
@@ -1,883 +0,0 @@
----
-title: Android
-page_title: Android
-description: "Telerik Mobile Testing - API Reference - Android"
-position: 0
-publish: true
-slug: ms-android-api
----
-
-# Android
-
-Methods
-<select id="methodsSelect" onchange="window.location.hash='#'+event.currentTarget.selectedOptions[0].value;">
- <option value="dragtodisplacement">DragToDisplacement</option>  <option value="dragtopoint">DragToPoint</option>  <option value="elementexists">ElementExists</option>  <option value="elementvisible">ElementVisible</option>  <option value="getpropertyvalue">GetPropertyValue</option>   <option value="pinchin">PinchIn</option>  <option value="pinchout">PinchOut</option>  <option value="pressbackbutton">PressBackButton</option>  <option value="pressmenubutton">PressMenuButton</option>  <option value="pressreturn">PressReturn</option>  <option value="presssearchbutton">PressSearchButton</option>  <option value="screenshot">Screenshot</option>  <option value="selectrow">SelectRow</option>  <option value="setdate">SetDate</option><option value="settext">SetText</option>  <option value="setvalue">SetValue</option>  <option value="swipe">Swipe</option>  <option value="tap">Tap</option>  <option value="tapandhold">TapAndHold</option>  <option value="tapatlocation">TapAtLocation</option>  <option value="tapatpoint">TapAtPoint</option>  <option value="tapcenterleft">TapCenterLeft</option>  <option value="tapcenterright">TapCenterRight</option>  <option value="toggle">Toggle</option>  <option value="twofingerrotate">TwoFingerRotate</option>  <option value="typetext">TypeText</option>  <option value="wait">Wait</option>  <option value="waitfor">WaitFor</option> <option value="waitforelementexists">WaitForElementExists</option>  <option value="waitforelementvisible">WaitForElementVisible</option>  <option value="waitforpropertyvalue">WaitForPropertyValue</option><option value="zoomin">ZoomIn</option> <option value="zoomout">ZoomOut</option> 
-</select>
-
-Methods for automating native Android applications.
-
-##Methods
-
-<a id="dragtodisplacement"></a>
-## DragToDisplacement (AndroidQuery[] query, TapPoint fromPoint, TapPoint displacement, int steps)
-
-Performs a drag gesture from a point to a displacement from that point within the view specified by the query. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*fromPoint (TapPoint)* - The X, Y position in the view to start the drag from. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*displacement (TapPoint)* - The X, Y distance from the fromPoint to end the drag. If null, defaults to center point in view.
-
-*steps (int)* - The amount of touches to generate to complete the drag. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.DragToDisplacement(elementQry, new TapPoint() { X = 10, Y = 10 }, new TapPoint() { X = -10, Y = -10 }, 20);
-```
-
-```VB
-Me.ActiveDevice.Android.DragToDisplacement(elementQry, New TapPoint() With {.X = 10, .Y = 10 }, New TapPoint() With {.X = -10, .Y = -10 }, 20)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtopoint"></a>
-##  DragToPoint(AndroidQuery[] query, TapPoint fromPoint, TapPoint toPoint, int steps)
-
-
-Performs a drag gesture from a point to a point within the view specified by the query. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*fromPoint (TapPoint)* - The X, Y position in the view to start the drag from. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*toPoint (TapPoint)* - The X, Y position in the view to end the drag. If null, equals the fromPoint. If X, or Y is negative, that value defaults to the X, or Y value of fromPoint. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*steps (int)* - The amount of touches to generate to complete the drag. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.DragToPoint(elementQry, new TapPoint() { X = 10, Y = 10 }, new TapPoint() { X = 10, Y = 10 }, 20);
-```
-```VB
-Me.ActiveDevice.Android.DragToPoint(elementQry, New TapPoint() With {.X = 10, .Y = 10 }, New TapPoint() With { .X = 10, .Y = 10 }, 20)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="elementexists"></a>
-## ElementExists (AndroidQuery[] query)
-
-Checks if the view specified by the query exists, and returns the result. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.ElementExists(elementQry);
-```
-
-```VB
-Me.ActiveDevice.Android.ElementExists(elementQry)
-```
-
-### Return Value
-
-Gets a value indicating whether the element exists.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="elementvisible"></a>
-## ElementVisible (AndroidQuery[] query)
-
-Checks if the view specified by the query is visible, and returns the result. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery*) - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.ElementVisible(elementQry);
-```
-
-```VB
-Me.ActiveDevice.Android.ElementVisible(elementQry)
-```
-
-
-### Return Value
-
-Gets a value indicating whether the element is visible.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getpropertyvalue"></a>
-## GetPropertyValue (AndroidQuery[] query, string propertyName)
-
-Retrieves the value of a property from a specified view. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*propertyName (string)* - The string name of the property.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.GetPropertyValue(elementQry, "text");
-```
-
-```VB
-Me.ActiveDevice.Android.GetPropertyValue(elementQry, "text")
-```
-
-
-### Return Value
-
-The String value of the property.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
-<a id="pinchin"></a>
-##PinchIn (AndroidQuery[] query, TapPoint point, int distance, int steps)
-
-Performs a pinch in gesture at the specified location within the view specified by the query. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The X, Y center point to pinch into in the view. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*distance (int)* - The distance away from the point to start. Minimum value is 1.
-
-*steps (int)* - The amount of touches to generate to complete the pinch in. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PinchIn(elementQry, new TapPoint() { X = 10, Y = 10 }, 100, 50);
-```
-
-```VB
-Me.ActiveDevice.Android.PinchIn(elementQry, New TapPoint() With {.X = 10, .Y = 10 }, 100, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pinchout"></a>
-##PinchOut(AndroidQuery[] query, TapPoint point, int distance, int steps)
-
-Performs a pinch out gesture at the specified location within the view specified by the query. Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The X, Y center point to pinch out from the view. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*distance (int)* - The distance away from the point to end. Minimum value is 1.
-
-*steps (int)* - The amount of touches to generate to complete the pinch out. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PinchOut(elementQry, new TapPoint() { X = 10, Y = 10 }, 100, 50);
-```
-
-```VB
-Me.ActiveDevice.Android.PinchOut(elementQry, New TapPoint() With { .X = 10, .Y = 10 }, 100, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pressbackbutton"></a>
-##PressBackButton ()
-
-Presses the hardware back button.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PressBackButton();
-```
-
-```VB
-Me.ActiveDevice.Android.PressBackButton()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pressmenubutton"></a>
-##PressMenuButton ()
-
-Presses the hardware menu button.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PressMenuButton();
-```
-
-```VB
-Me.ActiveDevice.Android.PressMenuButton()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pressreturn"></a>
-##PressReturn (AndroidQuery[] query)
-
-Presses the software keyboard return key. <para>If the target is a SearchView, the keypress will target its internal text editing view. Supports subclasses and views of **android.widget.EditText** and **android.widget.SearchView**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PressReturn(elementQry);
-```
-
-```VB
-Me.ActiveDevice.Android.PressReturn(elementQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="presssearchbutton"></a>
-##PressSearchButton ()
-
-Presses the hardware search button.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.PressSearchButton();
-```
-
-```VB
-Me.ActiveDevice.Android.PressSearchButton()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="screenshot"></a>
-## Screenshot ()
-
-Takes a screenshot of the tested UI.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Screenshot();
-```
-
-```VB
-Me.ActiveDevice.Android.Screenshot()
-```
-### Return Value
-
-The taken screenshot as array of bytes.
-
-## Screenshot (string fileName)
-
-Takes a screenshot of the tested UI.
-
-### Parameters
-
-*fileName (string)* - The name and location to save the image at.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Screenshot("MyScreenshot.png");
-```
-
-```VB
-Me.ActiveDevice.Android.Screenshot("MyScreenshot.png")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="selectrow"></a>
-##SelectRow (AndroidQuery[] query, int row, int? group = null)
-
-Selects a row in a view specified by the query. If the target is an ExpandableListView, you must also specify a group or the row number will be applied to the group. The group will be expanded before the row is selected within the group. Supports subclasses of: **android.widget.AdapterView**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*row (int)* - Тhe row to select. <para>Positive numbers only.
-
-*group (int)* - Тhe group containing the row to select, for ExpandableListViews. Optional. Positive numbers only.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.SelectRow(elementQry, 1);
-```
-
-```VB
-Me.ActiveDevice.Android.SelectRow(elementQry, 1)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setdate"></a>
-##SetDate (AndroidQuery[] query,  DateTime date)
-
-Sets the date on a view specified by the query. Supports views and subclasses of: **android.widget.CalendarView**, **android.widget.DatePicker**, **android.widget.TimePicker**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*date (DateTime)* - The date to set.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.SetDate(elementQry,new DateTime(2014,4,12));
-```
-
-```VB
-Me.ActiveDevice.Android.SetDate(elementQry, New DateTime(2014, 4, 12))
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="settext"></a>
-##SetText (AndroidQuery[] query, string text)
-
-Sets the text on a view specified by the query. If the target is a SearchView, this command will target its internal text editing view, and the SearchView will be expanded before text is entered into it.
-
-Supports subclasses and views of **android.widget.EditText** and **android.widget.SearchView**. 
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*text (string)* - Тhe text value to set on the view.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.SetText(elementQry, "Test");
-```
-
-```VB
-Me.ActiveDevice.Android.SetText(elementQry, "Test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setvalue"></a>
-##SetValue (AndroidQuery[] query, double value)
-
-Sets the value of a view specified by the query. 
-
-Supports subclasses of **android.widget.AbsSeekBar** and views and subclasses of **android.widget.NumberPicker**. 
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*value (double)* - The value the view should be set to.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.SetValue(elementQry, 60);
-```
-
-```VB
-Me.ActiveDevice.Android.SetValue(elementQry, 60)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="swipe"></a>
-##Swipe (AndroidQuery[] query, SwipeDirection direction)
-
-Performs a swipe gesture across the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**. 
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*direction (SwipeDirection)* - The direction to swipe.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Swipe(elementQry, SwipeDirection.Down);
-```
-
-```VB
-Me.ActiveDevice.Android.Swipe(elementQry, SwipeDirection.Down)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tap"></a>
-##Tap (AndroidQuery[] query, int tapCount = 1, int tapDownDelay = 10, int tapUpDelay = 100)
-
-Performs a tap gesture at the center of the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*tapCount (int)* - How many times to tap. Optional. Default value is 1.
-
-*tapDownDelay (int)* - The amount of time in milliseconds tap down should last. Optional. Default value is 10.
-
-*tapUpDelay (int)* - The amount of time in milliseconds tap up should last, if multiple taps are used. Optional. Default value is 100.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Tap(buttonQry);
-
-this.ActiveDevice.Android.Tap(buttonQry, 2, 1000, 500);
-```
-
-```VB
-Me.ActiveDevice.Android.Tap(buttonQry)
-
-Me.ActiveDevice.Android.Tap(buttonQry, 2, 1000, 500)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapandhold"></a>
-##TapAndHold (AndroidQuery[] query)
-
-Performs a tap-and-hold gesture at the center of the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TapAndHold(buttonQry);
-```
-
-```VB
-Me.ActiveDevice.Android.TapAndHold(buttonQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatlocation"></a>
-##TapAtLocation (AndroidQuery[] query, int x, int y, int tapCount = 1)
-
-Performs a tap gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*x (int)* - The X coordinate of the location to tap. <para>If negative value is submitted, the value defaults to the center X of the view. If greater than the X of the view, it is still applied as is.
-
-*y (int)* - The Y coordinate of the location to tap. <para>If negative value is submitted, the value defaults to the center Y of the view. If greater than the Y of the view, it is still applied as is.
-
-*tapCount (int)* - How many times to tap. Optional. Default value is 1.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TapAtLocation(buttonQry, 10, 10);
-
-this.ActiveDevice.Android.TapAtLocation(buttonQry, 10, 10, 2);
-```
-
-```VB
-Me.ActiveDevice.Android.TapAtLocation(buttonQry, 10, 10)
-
-Me.ActiveDevice.Android.TapAtLocation(buttonQry, 10, 10, 2)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatpoint"></a>
-##TapAtPoint (AndroidQuery[] query, TapPoint point = null, int tapCount = 1, int tapDownDelay = 10, int tapUpDelay = 100)
-
-Performs a tap gesture at the specified point within the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The X, Y position to tap in the view. <para>Optional. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-*tapCount (int)* - How many times to tap. <para>Optional. Default value is 1.
-
-*tapDownDelay (int)* - The amount of time in milliseconds tap down should last. Optional. Default value is 10.
-
-*tapUpDelay (int)* - The amount of time in milliseconds tap up should last, if multiple taps are used. Optional. Default value is 100.
-### Example
-
-```C#
-this.ActiveDevice.Android.TapAtPoint(buttonQry);
-
-this.ActiveDevice.Android.TapAtPoint(buttonQry, new TapPoint() { X=10, Y=10 }, 2, 1000, 500);
-```
-
-```VB
-Me.ActiveDevice.Android.TapAtPoint(buttonQry)
-
-Me.ActiveDevice.Android.TapAtPoint(buttonQry, New TapPoint() With { .X = 10, .Y = 10 }, 2, 1000, 500)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterleft"></a>
-##TapCenterLeft (AndroidQuery[] query)
-
-Performs a tap gesture at the center-left of the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TapCenterLeft(buttonQry);
-```
-
-```VB
-Me.ActiveDevice.Android.TapCenterLeft(buttonQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterright"></a>
-##TapCenterRight (AndroidQuery[] query)
-
-Performs a tap gesture at the center-right of the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TapCenterRight(buttonQry);
-```
-
-```VB
-Me.ActiveDevice.Android.TapCenterRight(buttonQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="toggle"></a>
-##Toggle (AndroidQuery[] query, bool toggle)
-
-Sets the toggle state of a view specified by the query.
-
-Supports views and subclasses of: **android.widget.CompoundButton**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*toggle (bool)* - Тhe on/off true/false state to apply to the togglable view.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Toggle(elementQry, true);
-```
-
-```VB
-Me.ActiveDevice.Android.Toggle(elementQry, true)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="twofingerrotate"></a>
-##TwoFingerRotate (AndroidQuery[] query, TapPoint point, int angleInDegrees)
-
-Performs a rotate gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The X, Y position of origin to rotate around in the view. If null, defaults to center point in view. If X, or Y is negative, that value defaults to the center X, or Y of the view. If X or Y is greater than the X or Y of the view, it is still applied as is.
-
-angleInDegrees (int) - The angle in degrees to rotate.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TwoFingerRotate(elementQry, new TapPoint() {X=20,Y=20 }, 180);
-```
-
-```VB
-Me.ActiveDevice.Android.TwoFingerRotate(elementQry, New TapPoint() With { .X = 20, .Y = 20 }, 180)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="typetext"></a>
-##TypeText (AndroidQuery[] query, string text)
-
-Types the text into a view specified by the query. If the target is a SearchView, the typing will target its internal text editing view, and the SearchView will be expanded before text is entered into it.
-
-Supports subclasses and views of **android.widget.EditText** and **android.widget.SearchView**.
-
-### Parameters
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*text (string)* -The text value to type into the view.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.TypeText(elementQry, "Test");
-```
-
-```VB
-Me.ActiveDevice.Android.TypeText(elementQry, "Test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="wait"></a>
-##Wait (int miliseconds)
-
-Waits an arbitrary amount of time before continuing execution.
-
-### Parameters
-*miliseconds (int)* - The amount of time to wait in milliseconds.<para>Positive numbers only.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.Wait(1000);
-```
-
-```VB
-Me.ActiveDevice.Android.Wait(1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitfor"></a>
-##WaitFor (Func \<bool> func, int checkInterval, int timeout)
-
-Executes periodic verifications against a custom condition and times out if the condition is not met.
-
-### Parameters
-*func (\<bool> func)* - The custom condition to verify.
-
-*checkInterval (int)* - The interval between verification calls. Positive numbers only.
-
-*timeout (int)* - The overall number of milliseconds to wait. Positive numbers only. Cannot be less than 'checkInterval'.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.WaitFor(new Func<bool>(() => { Random r = new Random(); return (r.Next(2) % 2 == 0); }), 100, 200); 
-```
-
-```VB
-Me.ActiveDevice.Android.WaitFor(New Func(Of Boolean)(Function() 
-Dim r As New Random()
-Return (r.[Next](2) Mod 2 = 0)
-
-End Function), 100, 200)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforelementexists"></a>
-##WaitForElementExists (AndroidQuery[] query, bool exists, int checkInterval, int timeout)
-
-Executes periodic verifications against an element query to ensure element existence or times out.
-
-Supports views and subclasses of: android.view.View.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*exists (bool)* - The expected command value.
-
-*checkInterval (int)* - The interval between verification calls. Positive numbers only.
-
-*timeout (int)* - The overall number of milliseconds to wait. Positive numbers only. Cannot be less than 'checkInterval'.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.WaitForElementExists(elementQry, true, 100, 1000);
-```
-
-```VB
-Me.ActiveDevice.Android.WaitForElementExists(elementQry, true, 100, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforelementvisible"></a>
-##WaitForElementVisible (AndroidQuery[] query, bool visible, int checkInterval, int timeout)
-
-Executes periodic verifications against an element query to ensure element visibility or times out.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*visible (bool)* - The expected command value.
-
-*checkInterval (int)* - The interval between verification calls. Positive numbers only.
-
-*timeout (int)* - The overall number of milliseconds to wait. Positive numbers only. Cannot be less than 'checkInterval'.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.WaitForElementVisible(elementQry, true, 100, 1000);
-```
-
-```VB
-Me.ActiveDevice.Android.WaitForElementVisible(elementQry, true, 100, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforpropertyvalue"></a>
-##WaitForPropertyValue (AndroidQuery[] query, string propertyName, string propertyValue, int checkInterval, int timeout)  
-
-Executes periodic verifications against an element property to ensure its value or times out.
-
-Supports views and subclasses of: **android.view.View**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-*propertyName (string)* - The string name of the property.
-
-*propertyValue (string)* - The expected property value.
-
-*checkInterval (int)* - The interval between verification calls. Positive numbers only.
-
-*timeout (int)* - The overall number of milliseconds to wait. Positive numbers only. Cannot be less than 'checkInterval'.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.WaitForPropertyValue(elementQry, "text", "t", 100, 1000);
-```
-
-```VB
-Me.ActiveDevice.Android.WaitForPropertyValue(elementQry, "text", "t", 100, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-<a id="zoomin"></a>
-##ZoomIn(AndroidQuery[] query)
-
-Taps on the zoom in button of a ZoomControls.
-
-Supports views and subclasses of **android.widget.ZoomControls**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.ZoomIn(elementQry);
-```
-
-```VB
-Me.ActiveDevice.Android.ZoomIn(elementQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-<a id="zoomout"></a>
-##ZoomOut(AndroidQuery[] query)
-
-Taps on the zoom out button of a ZoomControls.
-
-Supports views and subclasses of **android.widget.ZoomControls**.
-
-### Parameters
-
-*query (AndroidQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-this.ActiveDevice.Android.ZoomOut(elementQry);
-```
-
-```VB
-Me.ActiveDevice.Android.ZoomOut(elementQry)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
\ No newline at end of file
diff --git a/docs/test-studio-mobile/api-reference/creating-queries.md b/docs/test-studio-mobile/api-reference/creating-queries.md
deleted file mode 100644
index 41a78af9..00000000
--- a/docs/test-studio-mobile/api-reference/creating-queries.md
+++ /dev/null
@@ -1,261 +0,0 @@
----
-title: Creating Queries
-page_title: Creating Queries
-description: "Telerik Mobile Testing - Creating Queries"
-position: -1
-publish: true
-slug: ms-create-query
----
-
-# Creating queries
-
-<select id="methodsSelect" onchange="window.location.hash='#'+event.currentTarget.selectedOptions[0].value;">
- <option value="android">Android</option>  <option value="ios">iOS</option> <option value="web">Web</option> <option value="hybrid">Hybrid</option>
-</select>
-
-Queries are used to select a view (Native or Web).
-
-When a query is executed, all elements matching the query are stored in an internal array. By default the element at index 0 is used for any operations to be performed. This index can be manually specified in the query by setting index.
-
-*Note: The properties are case sensitive, you should use them in the queries as they are defined in your application.*
-
-> A *Dictionary* data structure is used in the sample code lines below. It is necessary to add a reference to the project of the *System.Collections.Generic* namespace.
-
-```C#
-{ Class = "TYPE", Index=2 }
-```
-
-```VB
-{.Class = "TYPE", .Index=2 }
-```
-
-
-
-<a id="android"></a>
-## Android
-
-Android queries are objects that define one or more properties to match in a **android.view.View**. If a view is found where all properties match, the requested operation is performed on that view. If multiple views with matching properties are found, the operation is performed on the first view found to be a match.
-
-```C#
-AndroidQuery query = new AndroidQuery(){Properties = new Dictionary<string, string>(){ {  "propertyName1" , "expectedValue"}, {"propertyName2" , "expectedValue2"} } };
-```
-
-```VB
-Dim query As New AndroidQuery()
-query.Properties.Add("propertyName1", "expectedValue")
-query.Properties.Add("propertyName2", "expectedValu2")
-```
-
-Sometimes it is necessary to locate a view using supplemental information, such as a class type (android.view.View, android.widget.Button, etc). This can be done as follows:
-
-```C#
-// TYPE can be android.view.View, android.widget.Button, etc.
-AndroidQuery query = new AndroidQuery(){Class="TYPE"};
-```
-```VB
-
-Dim query As New AndroidQuery()
-query.Class="TYPE"
-```
-
-Queries for a class type will find views of that type, and views that derive from that type in their inheritance chain. It is possible to define a query that only locates views with an exact class type, excluding parent class types.
-
-```C#
-// TYPE can be android.view.View, android.widget.Button, etc.
-AndroidQuery query = new AndroidQuery(){Class="TYPE", ExactClass = true};
-```
-```VB
-Dim query As New AndroidQuery() With {.Class = "TYPE", .ExactClass  = True}
-```
-
-Queries for class type can be combined with queries for property values.
-
-```C#
-{% raw %}
-AndroidQuery query = new AndroidQuery(){Class="android.widget.Button", Properties = new Dictionary<string, string>(){{"text", "Button1"}}};
-{% endraw %}
-```
-```VB
-Dim query As New AndroidQuery() With {.Class = "android.widget.Button"}
-query.Properties.Add("text", "Button 1")
-```
-
-
-You can query for a control using the id specified in a layout XML file. As an example, to query for the control specified as:
-
-```XML
-<View android:id="@+id/myControl"/>
-```
-
-format your query like:
-
-```C#
-{% raw %}
-AndroidQuery query = new AndroidQuery(){Class="TYPE", Properties = new Dictionary<string, string>(){{"ID", "myControl"}}};
-{% endraw %}
-```
-```VB
-Dim query As New AndroidQuery()
-query.Properties.Add("ID", "myControl")
-```
-
-**Chained queries** can be used to perform complex queries that require many query types. A chained query is an array of single queries. Each query of the array represents a child of the previous query in the array. The first query represents a child of the top-most view.
-
-```C#
-//Finds the first android.widget.ExpandableListView, then search inside of it for android.widget.Button with index 10 
-AndroidQuery[] chainedQuery = new AndroidQuery[] { new AndroidQuery(){Class = "TYPE"}, new AndroidQuery() {Class = "TYPE", Index = 10} } ;
-```
-```VB
-Dim chainedQuery As AndroidQuery() = New AndroidQuery() {New AndroidQuery() With {.Class = "TYPE"}, New AndroidQuery() With {.Class = "TYPE", .Index=10}}
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br>
-
-<a id="ios"></a>
-## iOS
-
-iOS queries are objects that define one or more properties to match in a UIView. If a view is found where all properties match, the requested operation is performed on that view. If multiple views with matching properties are found, the operation is performed on the first view found to be a match.
-
-```C#
-IOSQuery query = new IOSQuery(){Properties = new Dictionary<string, string>(){ {  "propertyName1" , "expectedValue"}, {"propertyName2" , "expectedValue2"} } };
-```
-```VB
-Dim query As New IOSQuery()
-query.Properties.Add("propertyName1", "expectedValue")
-query.Properties.Add("propertyName2", "expectedValu2")
-```
-Sometimes it is necessary to locate a view using supplemental information, such as a class type (UIView, UIButton, etc). This can be done as follows:
-
-```C#
-// TYPE can be UIView, UIButton, etc.
-IOSQuery query = new IOSQuery(){Class="TYPE"};
-```
-```VB
-Dim query As New IOSQuery() With {.Class="Type"}
-```
-
-Queries for a class type will find views of that type, and views that derive from that type in their inheritance chain. It is possible to define a query that only locates views with an exact class type, excluding parent class types.
-
-```C#
-//TYPE can be UIView, UIButton, etc
-IOSQuery query = new IOSQuery(){Class="TYPE", ExactClass = true};
-```
-```VB
-Dim query As New IOSQuery() With { .Class="Type", .ExactClass = True}
-```
-
-Queries for class type can be combined with queries for property values.
-
-```C#
-{% raw %}
-IOSQuery query = new IOSQuery(){Class="UIButton", Properties = new Dictionary<string, string>(){{"currentTitle", "Button 1"}}};
-{% endraw %}
-```
-```VB
-Dim query As New AndroidQuery()
-query.Class="android.widget.Button"
-query.Properties.Add("text", "Button 1")
-```
-
-**Chained queries** can be used to perform complex queries that require many query types. A chained query is an array of single queries. Each query of the array represents a child of the previous query in the array. The first query represents a child of the window.
-
-```C#
-//Finds the first UITableView, then search inside of it for UITableViewCell with index 10 
-IOSQuery[] chainedQuery = new IOSQuery[] { new IOSQuery(){Class = "UITableView"}, new IOSQuery() {Class = "UITableViewCell", Index = 10} } ;
-```
-```VB
-Dim chainedQuery As IOSQuery() = New IOSQuery() {New IOSQuery() With {.Class = "UITableView"}, New IOSQuery() With {.Class = "UITableViewCell", .Index=10}}
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br>
-
-## Web
-
-Web queries are objects that define one or more properties to match in a **Html element**. If an element is found where all properties match, the requested operation is performed on that element. If multiple elements with matching properties are found, the operation is performed on the first element found to be a match.
-
-Sometimes it is necessary to locate an element using supplemental information, such as a ClassName (ui-autocomplete). This can be done as follows:
-
-```C#
-//Search for html element with ClassName ui-autocomplete
-WebQuery query = new WebQuery() {ClassName = "ui-autocomplete"};
-```
-```VB
-Dim query As New WebQuery() With { .ClassName = "ui-autocomplete" }
-```
-
-or by ID
-
-```C#
-//Search for html element with ID ui-autocomplete
-WebQuery queryById = new WebQuery() {Id = "ui-autocomplete"};
-```
-```VB
-Dim queryById As New WebQuery() With { .Id = "ui-autocomplete" }
-```
-
-or by XPath
-
-
-```C#
-//Search for html element with XPath @"//*[@id=""c1""]/div[1]/div[1]/a"
-WebQuery queryByXpath = new WebQuery() { XPath = @"//*[@id=""c1""]/div[1]/div[1]/a" };
-```
-```VB
-Dim queryByXpath As New WebQuery() With { .XPath = "//*[@id=""c1""]/div[1]/div[1]/a"  }
-```
-
-or by TagName and Index
-
-```C#
-//Search for html element with TagName a
-WebQuery queryByTagNameAndIndex = new WebQuery() { TagName = "a", Index = 1 };
-```
-```VB
-Dim queryByTagNameAndIndex As New WebQuery() With { .TagName = "a", .Index = 1 }
-```
-
-You can also combine them into one query
-
-```C#
-//Search for html element with ClassName ui-autocomplete, ID ui-autocomplete, TagName a and Index 1
-WebQuery query = new WebQuery() {ClassName = "CLASSNAME", Id = "ID", TagName = "TAGNAME", Index = 1 };
-```
-```VB
-Dim query As New WebQuery() With { .ClassName = "CLASSNAME", .Id = "ID", .TagName = "a", .Index = 1 }
-```
-
-**Chained queries** can be used to perform complex queries that require many query types. A chained query is an array of single queries. Each query of the array represents a child of the previous query in the array. The first query represents a child of the window.
-
-
-```C#
-//Finds the first element with ClassName col1, then search inside of it for an element with TagName a and index 1
-WebQuery[] chainedQuery = new WebQuery[] {new WebQuery(){ClassName = "col1"}, new WebQuery() { TagName = "a", Index = 1 } };
-```
-```VB
-Dim chainedQuery As WebQuery() = New WebQuery() {New WebQuery() With { .ClassName = "col1" }, New WebQuery() With { .TagName = "a", .Index=1 }}
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br>
-
-## Hybrid
-
-Hybrid queries are a combination of native and web queries. A native query (iOS, Android) is needed to identify the native web view that hosts the app and a web query to identify a specific web element. If the hybrid app is hosted inside only one web view, then the native view query can be skipped:
-
-```C#
-// This will perform a web tap action on the provided element located inside the first found WebView object in the app.
-this.ActiveDevice.Web.Tap(this.Elements.MyScreen.webview.BUTTON);
-
-// This will perform a web tap action on the provided element located inside a specific WebView object in the app.
-this.ActiveDevice.Web.Tap(this.Elements.MyScreen.webview.View, this.Elements.MyScreen.webview.BUTTON);
-```
-```VB
-' Me.ActiveDevice.Web.Tap(Elements.MyScreen.webview.BUTTON)
-
-' Me.ActiveDevice.Web.Tap(Elements.MyScreen.webview.View, Elements.MyScreen.webview.BUTTON)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br>
diff --git a/docs/test-studio-mobile/api-reference/hybrid.md b/docs/test-studio-mobile/api-reference/hybrid.md
deleted file mode 100644
index b4bef1e8..00000000
--- a/docs/test-studio-mobile/api-reference/hybrid.md
+++ /dev/null
@@ -1,1480 +0,0 @@
----
-title: Hybrid
-page_title: Hybrid
-description: "Telerik Mobile Testing - API Reference - Hybrid"
-position: 5
-publish: true
-slug: ms-hybrid-api
----
-
-# Hybrid
-
-Methods
-<select id="methodsSelect" onchange="window.location.hash='#'+event.currentTarget.selectedOptions[0].value;">
-<option value="click">Click</option>
-<option value="doubleclick">DoubleClick</option>
-<option value="drag">Drag</option>
-<option value="dragtodisplacement">DragToDisplacement</option>
-<option value="dragtoelement">DragToElement</option>
-<option value="dragtopoint">DragToPoint</option>
-<option value="executescript">ExecuteScript</option>
-<option value="getattribute">GetAttribute</option>
-<option value="getchecked">GetChecked</option>
-<option value="getcolumncount">GetColumnCount</option>
-<option value="gethtml">GetHtml</option>
-<option value="getinerror">GetInError</option>
-<option value="getpaused">GetPaused</option>
-<option value="getrowcount">GetRowCount</option>
-<option value="getscriptresult">GetScriptResult</option>
-<option value="getselectedindex">GetSelectedIndex</option>
-<option value="getselectedtext">GetSelectedText</option>
-<option value="getselectedvalue">GetSelectedValue</option>
-<option value="getstyle">GetStyle</option>
-<option value="gettextcontent">GetTextContent</option>
-<option value="getvalue">GetValue</option>
-<option value="hoverover">HoverOver</option>
-<option value="pinchin">PinchIn</option>
-<option value="pinchout">PinchOut</option>
-<option value="presskey">PressKey</option>
-<option value="rightclick">RightClick</option>
-<option value="scroll">Scroll</option>
-<option value="scrolltoelement">ScrollToElement</option>
-<option value="setattribute">SetAttribute</option>
-<option value="setchecked">SetChecked</option>
-<option value="sethtml">SetHtml</option>
-<option value="setpaused">SetPaused</option>
-<option value="setselectedindex">SetSelectedIndex</option>
-<option value="setselectedtext">SetSelectedText</option>
-<option value="setselectedvalue">SetSelectedValue</option>
-<option value="setstyle">SetStyle</option>
-<option value="settextcontent">SetTextContent</option>
-<option value="setvalue">SetValue</option>
-<option value="swipe">Swipe</option>
-<option value="tap">Tap</option>
-<option value="tapandhold">TapAndHold</option>
-<option value="tapatlocation">TapAtLocation</option>
-<option value="tapatpoint">TapAtPoint</option>
-<option value="tapcenterleft">TapCenterLeft</option>
-<option value="tapcenterright">TapCenterRight</option>
-<option value="twofingerrotate">TwoFingerRotate</option>
-<option value="wait">Wait</option>
-<option value="waitfor">WaitFor</option>
-<option value="waitforscriptresult">WaitForScriptResult</option>
-</select>
-
-Methods for automating hybrid applications.
-
-Since hybrid app is a web app running inside a native container (WebView), hybrid API methods that target specific element accept a web query to identify the element. If the app contains only one native container (WebView), using a API overload method that accepts a WebQuery object to identify that element suffices. However, if the app implements more than one native containers (WebView), finding an element inside the different native containers requires using and API overload method that identifies the native container first in which the web element is located. Below you can find an example of 2 overloads of the Tap hybrid API method:
-
-```C#
-// This will perform a web tap action on the provided element located inside the first found WebView object in the app.
-this.ActiveDevice.Web.Tap(this.Elements.MyScreen.webview.BUTTON);
-
-// This will perform a web tap action on the provided element located inside a specific WebView object in the app.
-this.ActiveDevice.Web.Tap(this.Elements.MyScreen.webview.View, this.Elements.MyScreen.webview.BUTTON);
-```
-
-```VB
-' Me.ActiveDevice.Web.Tap(Elements.MyScreen.webview.BUTTON)
-
-' Me.ActiveDevice.Web.Tap(Elements.MyScreen.webview.View, Elements.MyScreen.webview.BUTTON)
-```
-
- > For brevity, API methods in this topic are listed with their WebView/Element overloads. However, based on the actual scenario to be tested any of the other available overloads can be used instead.
-
-##Methods
-
-<a id="click"></a>
-## Click(Query[] viewQuery, Query[] elementQuery)
-
-Perform a click on an element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will perform a click action on the provided web element
-this.ActiveDevice.Web.Click(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.Click(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="doubleclick"></a>
-## DoubleClick(Query[] viewQuery, Query[] elementQuery)
-
-Perform a double click on an element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will perform a double-click on the provided web element
-this.ActiveDevice.Web.DoubleClick(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.DoubleClick(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="drag"></a>
-## Drag(Query[] viewQuery, Query[] elementQuery, int offsetX, int offsetY)
-
-Drag an element to a specific point.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*offsetX (int)* - Destination point horizontal offset from element center.
-
-*offsetY (int)* - Destination point vertical offset from element center.
-
-### Example
-
-```C#
-// This will drag a draggable web element to 100x,300y point realtive to the center of the provided element
-this.ActiveDevice.Web.Drag(Elements.MyScreen.WebView.Drag, 100,300);
-```
-
-```VB
-Me.ActiveDevice.Web.Drag(Elements.MyScreen.WebView.Drag, 100, 300)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtodisplacement"></a>
-## DragToDisplacement(Query[] viewQuery, Query[] elementQuery, TapPoint fromPoint, TapPoint displacement, int steps)
-
-Performs drag gesture on element specified by the query to a displacement point from that element
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*fromPoint (TapPiont)* - Starting point of drag gesture. If null, defaults to center point of element.
-
-*displacement (TapPiont)* - Displacement, represented as point object. If null, defaults to center point of element.
-
-*steps (int)* - The amount of touches to generate to complete the drag gesture.  Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// This will drag an element in web view from 0x, 0y point (relative to the element) to 100x, 300y point relative to the first TapPoint(0,0) in 150 simulated touches
-this.ActiveDevice.Web.DragToDisplacement(Elements.MyScreen.WebView.DragElement, new TapPoint(0,0), new TapPoint(100,300), 150);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToDisplacement(Elements.MyScreen.WebView.DragElement, New TapPoint(0, 0), New TapPoint(100, 300), 150)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtoelement"></a>
-## DragToElement(Query[] viewQuery, Query[] dragElementQuery, Query[] toElementQuery)
-
-Drag an element over another element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*dragElementQuery (WebQuery)* - WebQuery object that identifies element to be dragged. The element to be dragged must be draggable.
-
-*toElementQuery (WebQuery)* - WebQuery object that identifies element the dragged element will be dragged over.
-
-### Example
-
-```C#
-// Drag element `DragElement` on top of element `TestField`
-this.ActiveDevice.Web.DragToElement(Elements.MyScreen.WebView.DragElement, Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToElement(Elements.MyScreen.WebView.DragElement, Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtopoint"></a>
-## DragToPoint(Query[] viewQuery, Query[] elementQuery, TapPoint fromPoint, TapPoint toPoint, int steps )
-
-Drag an element to a specified point.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*fromPoint (TapPiont)* - Starting point of drag gesture. If null, defaults to center point of element.
-
-*displacement (TapPiont)* - Finishing point of drag gesture. If null, defaults to center point of element.
-
-*steps (int)* - The amount of touches to generate to complete the drag gesture.  Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// This will drag an element in web view from 0x, 0y point inside the specified element to 100x, 300y point relative to the element in 150 simulated touches
-this.ActiveDevice.Web.DragToPoint(Elements.MyScreen.WebView.DragElement, new TapPoint(0,0), new TapPoint(100,300), 150);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToPoint(Elements.MyScreen.WebView.DragElement, New TapPoint(0, 0), New TapPoint(100, 300), 150)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="executescript"></a>
-## ExecuteScript(Query[] viewQuery, string script, Query[] elementQuery)
-
-Execute a script into a web view.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*script (string)* - String that is transferred to application under test and evaled into current web view.
-
-*elementQuery (WebQuery)* - WebQuery for target element. Element defined by this parameter can be accessed using `targetElement` variable inside the script parameter string.
-
-### Example
-
-```C#
-// Executes the script of the string parameter on the web view under test. Deprecated: Use getScriptResult instead.
-this.ActiveDevice.Web.ExecuteScript("document.getElementsByTagName(\"div\")");
-```
-
-```VB
-Me.ActiveDevice.Web.ExecuteScript("document.getElementsByTagName(""div"")")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getattribute"></a>
-## GetAttribute(Query[] viewQuery, Query[] elementQuery, string attrName)
-
-Get attribute value of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*attrName (string)* - Name of the attribute.
-
-### Return Value
-
-A string containing the value of the specified attribute.
-
-### Example
-
-```C#
-// Get the `id` attribute value of `DragElement` as string
-string idAttribute = this.ActiveDevice.Web.GetAttribute(Elements.MyScreen.WebView.DragElement, "id");
-```
-
-```VB
-Dim idAttribute As String = Me.ActiveDevice.Web.GetAttribute(Elements.MyScreen.WebView.DragElement, "id")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getchecked"></a>
-## GetChecked(Query[] viewQuery, Query[] elementQuery)
-
-Gets checked state of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-A bool containing the checked state of specific element.
-
-### Example
-
-```C#
-// Returns the checked state of the checkBox as boolean
-bool state = this.ActiveDevice.Web.GetChecked(Elements.MyScreen.WebView.CheckBox);
-```
-
-```VB
-Dim state As Boolean = Me.ActiveDevice.Web.GetChecked(Elements.MyScreen.WebView.CheckBox)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
-<a id="getcolumncount"></a>
-## GetColumnCount(Query[] viewQuery, Query[] elementQuery, uint rowIndex)
-
-Get the number of cells of a specific row in a table.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*rowIndex (unit)* - Index of row which cells count is needed.
-
-### Return Value
-
-The number of cells in a particular row in a table element.
-
-### Example
-
-```C#
-// Returns the number of columns in the specified table row.
-uint count = this.ActiveDevice.Web.GetColumnCount(Elements.MyScreen.WebView.TableView, 1);
-```
-
-```VB
-Dim count As UInteger = Me.ActiveDevice.Web.GetColumnCount(Elements.MyScreen.WebView.TableView, 1)
-```
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="gethtml"></a>
-## GetHtml(Query[] viewQuery, Query[] elementQuery)
-
-Get inner html of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-A string containing the inner html of the specified element.
-
-### Example
-
-```C#
-// Gets the inner HTML of CheckBox
-string html = this.ActiveDevice.Web.GetHtml(Elements.MyScreen.WebView.CheckBox);
-```
-
-```VB
-Dim html As String = Me.ActiveDevice.Web.GetHtml(Elements.MyScreen.WebView.CheckBox)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getinerror"></a>
-## GetInError(Query[] viewQuery, Query[] elementQuery)
-
-Gets error state of audio/video element. This function returns inconsistent results for mobile browsers.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-True if control is in error state, otherwise false.
-
-### Example
-
-```C#
-bool statePlayer = this.ActiveDevice.Web.GetInError(Elements.MyScreen.WebView.Player);
-```
-
-```VB
-Dim statePlayer As Boolean = Me.ActiveDevice.Web.GetInError(Elements.MyScreen.WebView.Player)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getpaused"></a>
-## GetPaused(Query[] viewQuery, Query[] elementQuery)
-
-Get paused state of audio/video element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-True if audio/video element is paused, otherwise false.
-
-### Example
-
-```C#
-// Get the paused state of a `video` element.
-bool statePaused = this.ActiveDevice.Web.GetPaused(Elements.MyScreen.WebView.Player);
-```
-
-```VB
-Dim statePaused As Boolean = Me.ActiveDevice.Web.GetPaused(Elements.MyScreen.WebView.Player)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getrowcount"></a>
-## GetRowCount(Query[] viewQuery, Query[] elementQuery)
-
-Get number of rows of a table element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-The number of rows of a table element.
-
-### Example
-
-```C#
-// Returns the number of rows in the TableView
-uint rowCount = this.ActiveDevice.Web.GetRowCount(Elements.MyScreen.WebView.TableView);
-```
-
-```VB
-Dim rowCount As UInteger = Me.ActiveDevice.Web.GetRowCount(Elements.MyScreen.WebView.TableView)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getscriptresult"></a>
-## GetScriptResult(Query[] viewQuery, string script, Query[] elementQuery)
-
-Executes a script into a web view and returns the result.
-
-**Note:** In order to use this method you should add a reference assembly to **Microsoft.CSharp.dll** and **System.Core.dll** from the [project settings]({% slug ms-project-settings%}#References).
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*script (string)* - String that is transferred and evaled into current web view.
-
-*elementQuery (WebQuery)* - WebQuery for target element. Element defined by this parameter can be accessed using `targetElement` variable inside the script parameter string.
-
-### Example
-
-```C#
-// This will execute the script of the string parameter and save value of the element id property as object.
-object result = this.ActiveDevice.Web.GetScriptResult("document.getElementsByTagName(\"div\").id");
-```
-
-```VB
-Dim result As Object = Me.ActiveDevice.Web.GetScriptResult("document.getElementsByTagName(""div"").id")
-```
-
-### Return Value
-
-Result of script execution.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedindex"></a>
-## GetSelectedIndex(Query[] viewQuery, Query[] elementQuery)
-
-Get selected index of a select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-Array of numbers containing the selected indexes.
-
-### Example
-
-```C#
-// Get the selected index of the `Select` element (multiple items can be selected)
-uint[] index = this.ActiveDevice.Web.GetSelectedIndex(Elements.MyScreen.WebView.Select);
-```
-
-```VB
-Dim index As UInteger() = Me.ActiveDevice.Web.GetSelectedIndex(Elements.MyScreen.WebView.Select)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedtext"></a>
-## GetSelectedText(Query[] viewQuery, Query[] elementQuery)
-
-Get selected text values of select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-Array of strings containing the selected text(s).
-
-### Example
-
-```C#
-// Get the selected text of the `Select` element (multiple items can be selected)
-string[] selectedText = this.ActiveDevice.Web.GetSelectedText(Elements.MyScreen.WebView.Select);
-```
-
-```VB
-Dim selectedText() As String = Me.ActiveDevice.Web.GetSelectedText(Elements.MyScreen.WebView.Select)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedvalue"></a>
-## GetSelectedValue(Query[] viewQuery, Query[] elementQuery)
-
-Get selected value strings of select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-Array of strings containing the selected value(s).
-
-### Example
-
-```C#
-// Get the selected value of the `Select` element (multiple items can be selected)
-string[] selectedValue = this.ActiveDevice.Web.GetSelectedValue(Elements.MyScreen.WebView.Select);
-```
-
-```VB
-Dim selectedValue As String() = Me.ActiveDevice.Web.GetSelectedValue(Elements.MyScreen.WebView.Select)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getstyle"></a>
-## GetStyle(Query[] viewQuery, Query[] elementQuery, string styleProp)
-
-Get the value of a specific style property.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*styleProp (string)* - Name of the style attribute.
-
-### Return Value
-
-The value of requested style property.
-
-### Example
-
-```C#
-// Get the width value.
-string style = this.ActiveDevice.Web.GetStyle(Elements.MyScreen.WebView.TestField, "width");
-```
-
-```VB
-Dim style As String = Me.ActiveDevice.Web.GetStyle(Elements.MyScreen.WebView.TestField, "width")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="gettextcontent"></a>
-## GetTextContent(Query[] viewQuery, Query[] elementQuery)
-
-Get text content of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-A string containing the text content value.
-
-### Example
-
-```C#
-// This will return the text content of the test element
-string textContent = this.ActiveDevice.Web.GetTextContent(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Dim textContent As String = Me.ActiveDevice.Web.GetTextContent(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getvalue"></a>
-## GetValue(Query[] viewQuery, Query[] elementQuery)
-
-Get value of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Return Value
-
-A string containing the value of the specified element.
-
-### Example
-
-```C#
-// This will return the value of the test element
-string valueOfElement = this.ActiveDevice.Web.GetValue(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Dim valueOfElement As String = Me.ActiveDevice.Web.GetValue(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="hoverover"></a>
-## HoverOver(Query[] viewQuery, Query[] elementQuery)
-
-Perform a mouse hover over a web element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Perform a mouse hover action
-this.ActiveDevice.Web.HoverOver(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.HoverOver(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
-<a id="pinchin"></a>
-## PinchIn(Query[] viewQuery, Query[] elementQuery, TapPoint point, int distance, int steps)
-
-Perform pinch in gesture at the specified location within the element specified by the query. 
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordintes of pinch center point. If null, defaults to center point of element.
-
-*distance (int)* - Distance away from the center to start. Minimum value is 20.
-
-*steps (int)* - The amount of touches to generate to complete the pinch. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// Perform a pinch in over the test element where the pinch will start at 100x, 100y point within the element and will pinchIn 20px in 50 simulated touches
-this.ActiveDevice.Web.PinchIn(Elements.MyScreen.WebView.TestField, new TapPoint(100,100), 20, 50);
-```
-
-```VB
-Me.ActiveDevice.Web.PinchIn(Elements.MyScreen.WebView.TestField, New TapPoint(100, 100), 20, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pinchout"></a>
-## PinchOut(Query[] viewQuery, Query[] elementQuery, TapPoint point, int distance, int steps)
-
-Perform pinch out gesture at the specified location within the element specified by the query.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordintes of pinch center point. If null, defaults to center point of element.
-
-*distance (int)* - Distance away from the center to start. Minimum value is 20.
-
-*steps (int)* - The amount of touches to generate to complete the pinch. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// Perform a pinch out over the test element where the pinch out will start at 100x,100y point within the element and will pinchOut 20px in 50 simulated touches
-this.ActiveDevice.Web.PinchOut(Elements.MyScreen.WebView.TestField, new TapPoint(100,100), 20, 50);
-```
-
-```VB
-Me.ActiveDevice.Web.PinchOut(Elements.MyScreen.WebView.TestField, New TapPoint(100, 100), 20, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="presskey"></a>
-## PressKey(Query[] viewQuery, Query[] elementQuery, int keyCode, bool alt, bool ctrl, bool shift)
-
-Invoke press key event on specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*keyCode (int)* - Code of the key.
-
-*alt (boolean)* - Boolean value indicating whether ALT is pressed. The default is false.
-
-*ctrl (boolean)* - Boolean value indicating whether CTRL is pressed. The default is false.
-
-*shift (boolean)* - Boolean value indicating whether SHIFT is pressed. The default is false.
-
-### Example
-
-```C#
-// This will invoke the press CAPS LOCK key event (with code 20) over the test element 
-this.ActiveDevice.Web.PressKey(Elements.MyScreen.WebView.TestField, 20);
-```
-
-```VB
-Me.ActiveDevice.Web.PressKey(Elements.MyScreen.WebView.TestField, 20)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="rightclick"></a>
-## RightClick(Query[] viewQuery, Query[] elementQuery)
-
-Perform a right click on an element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Perform a right click on the test element
-this.ActiveDevice.Web.RightClick(Elements.MyScreen.WebQuery.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.RightClick(Elements.MyScreen.WebQuery.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="scroll"></a>
-## Scroll(Query[] viewQuery, Query[] elementQuery, int x = 0, int y = 0)
-
-Scroll the web view to any element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*x (int)* - The X confidantes of the specific element.
-
-*y (int)* - The Y confidantes of the specific element.
-
-### Example
-
-```C#
-// Scroll to a 300x, 300y point relative to the element
-this.ActiveDevice.Web.Scroll(Elements.MyScreen.WebView.TestField, 300, 300);
-```
-
-```VB
-Me.ActiveDevice.Web.Scroll(Elements.MyScreen.WebView.TestField, 300, 300)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="scrolltoelement"></a>
-## ScrollToElement(Query[] viewQuery, Query[] elementQuery)
-
-Scroll the web page to any element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Scroll to the test element to make it visible on the screen
-this.ActiveDevice.Web.ScrollToElement(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.ScrollToElement(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setattribute"></a>
-## SetAttribute(Query[] viewQuery, Query[] elementQuery, string attrName, string attrValue)
-
-Set attribute of specific element to a specific value.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*attrName (string)* - Name of the attribute.
-
-*attrValue (string)* - Value to be set.
-
-### Example
-
-```C#
-// Set the id attribute of the test element to test
-this.ActiveDevice.Web.SetAttribute(Elements.MyScreen.WebView.TestField, "id", "test");
-```
-
-```VB
-Me.ActiveDevice.Web.SetAttribute(Elements.MyScreen.WebView.TestField, "id", "test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setchecked"></a>
-## SetChecked(Query[] viewQuery, Query[] elementQuery, bool checkedValue)
-
-Sets checked state of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - Query object that identifies an element uniquely.
-
-*checkedValue (boolean)* - Checked state value to be set.
-
-### Example
-
-```C#
-// Set the state of the checklbox to false
-this.ActiveDevice.Web.SetChecked(Elements.MyScreen.WebView.CheckBox, false);
-```
-
-```VB
-Me.ActiveDevice.Web.SetChecked(Elements.MyScreen.WebView.CheckBox, False)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="sethtml"></a>
-## SetHtml(Query[] viewQuery, Query[] elementQuery, string html)
-
-Set inner html of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*html (sting)* - The Html that will be inserted in the specific element.
-
-### Example
-
-```C#
-// Set the '<label>text<label>' html to the test element
-this.ActiveDevice.Web.SetHtml(Elements.MyScreen.WebView.TestField, "<label>text<label>");
-```
-
-```VB
-Me.ActiveDevice.Web.SetHtml(Elements.MyScreen.WebView.TestField, "<label>text<label>")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setpaused"></a>
-## SetPaused(Query[] viewQuery, Query[] elementQuery, bool pausedState)
-
-Set paused state of audio/video element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*pausedState (boolean)* - Paused state to be set.
-
-### Example
-
-```C#
-// This method will pause the video player
-this.ActiveDevice.Web.SetPaused(Elements.MyScreen.WebView.Player, true);
-```
-
-```VB
-Me.ActiveDevice.Web.SetPaused(Elements.MyScreen.WebView.Player, True)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedindex"></a>
-## SetSelectedIndex(Query[] viewQuery, Query[] elementQuery, params uint[] indexes)
-
-Set selected index of a select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*indexes (uint array)* - Array of indexes to be selected.
-
-### Example
-
-```C#
-// Selects index 3 from the `select` element
-this.ActiveDevice.Web.SetSelectedIndex(Elements.MyScreen.WebView.Select, 3);
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedIndex(Elements.MyScreen.WebView.Select, 3)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedtext"></a>
-## SetSelectedText(Query[] viewQuery, Query[] elementQuery, params string[] text)
-
-Set selected text of a select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - Query object that identifies an element uniquely.
-
-*text (string array)* - Array of strings to be selected.
-
-### Example
-
-```C#
-// Selects a specific item by its text in a `select` element
-this.ActiveDevice.Web.SetSelectedText(Elements.MyScreen.WebView.Select, "text1");
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedText(Elements.MyScreen.WebView.Select, "text1")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedvalue"></a>
-## SetSelectedValue(Query[] viewQuery, Query[] elementQuery, params string[] values)
-
-Set selected value of a select element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*values (string array)* - Array of strings to be selected.
-
-### Example
-
-```C#
-// Selects a specific item by its value in a `select` element
-this.ActiveDevice.Web.SetSelectedValue(Elements.MyScreen.WebView.Select, "value2");
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedValue(Elements.MyScreen.WebView.Select, "value2")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setstyle"></a>
-## SetStyle(Query[] viewQuery, Query[] elementQuery, string styleProp, string styleValue)
-
-Set specific style property value.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*styleProp (string)* - Name of the style attribute.
-
-*styleValue (string)* - Value to be set.
-
-### Example
-
-```C#
-// This will set the width of the testElement to 50 px
-this.ActiveDevice.Web.SetStyle(Elements.MyScreen.WebView.TestField, "width", "50px");
-```
-
-```VB
-Me.ActiveDevice.Web.SetStyle(Elements.MyScreen.WebView.TestField, "width", "50px")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="settextcontent"></a>
-## SetTextContent(Query[] viewQuery, Query[] elementQuery, string textContent)
-
-Set text content of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*textContent (string)* - Text content to be set.
-
-### Example
-
-```C#
-// This will set the text content of the test element
-this.ActiveDevice.Web.SetTextContent(Elements.MyScreen.WebView.TestField, "textToSet");
-```
-
-```VB
-Me.ActiveDevice.Web.SetTextContent(Elements.MyScreen.WebView.TestField, "textToSet")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setvalue"></a>
-## SetValue(Query[] viewQuery, Query[] elementQuery, string value)
-
-Set value of specific element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - Query object that identifies an element uniquely.
-
-*value (string)* - Value to be set.
-
-### Example
-
-```C#
-// Set "test" value to the test element
-this.ActiveDevice.Web.SetValue(Elements.MyScreen.WebView.TestField, "test");
-```
-
-```VB
-Me.ActiveDevice.Web.SetValue(Elements.MyScreen.WebView.TestField, "test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="swipe"></a>
-## Swipe(Query[] viewQuery, Query[] elementQuery, SwipeDirection direction, int swipeDistance)
-
-Perform a swipe gesture across the element specified by the query. 
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*direction (SwipeDirection)* - Direction to swipe.
-
-*swipeDistance (int)* - Swipe distance, default is '200'.
-
-### Example
-
-```C#
-// Swipe right on the test element
-this.ActiveDevice.Web.Swipe(Elements.MyScreen.WebView.TestField, SwipeDirection.Right);
-```
-
-```VB
-Me.ActiveDevice.Web.Swipe(Elements.MyScreen.WebView.TestField, SwipeDirection.Right)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tap"></a>
-## Tap(Query[] viewQuery, Query[] elementQuery, int tapCount, int tapDownDelay, int tapUpDelay)
-
-Tap a web element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-*tapDownDelay (int)* - Tap down delay in miliseconds. Min value 50.
-
-*tapUpDelay (int)* - Tap up delay in miliseconds. Min value 50.
-
-### Example
-
-```C#
-// Tap action on the test element
-this.ActiveDevice.Web.Tap(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.Tap(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapandhold"></a>
-## TapAndHold(Query[] viewQuery, Query[] elementQuery)
-
-Perform tap-and-hold gesture at the center of the element.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap and hold action on the center of the test element
-this.ActiveDevice.Web.TapAndHold(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapAndHold(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatlocation"></a>
-## TapAtLocation(Query[] viewQuery, Query[] elementQuery, int X, int Y, int tapCount)
-
-Tap an element on particular location. 
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*X (int)* - X coordinate of point to be tapped.
-
-*Y (int)* - Y coordinate of point to be tapped.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-### Example
-
-```C#
-// Tap at 50x, 50y point within the test element
-this.ActiveDevice.Web.TapAtLocation(Elements.MyScreen.WebView.TestField, 50, 50, 1);
-```
-
-```VB
-Me.ActiveDevice.Web.TapAtLocation(Elements.MyScreen.WebView.TestField, 50, 50, 1)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatpoint"></a>
-## TapAtPoint(Query[] viewQuery, Query[] elementQuery, TapPoint point, int tapCount, int tapDownDelay, int tapUpDelay)
-
-Tap an element on particular point. 
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*point (TapPoint)* - Point inside element to be tapped.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-*tapDownDelay (int)* - Tap down delay in miliseconds. Min value 50.
-
-*tapUpDelay (int)* - Tap up delay in miliseconds. Min value 50.
-
-### Example
-
-```C#
-// Tap at 50x, 50y point within the test element
-this.ActiveDevice.Web.TapAtPoint(Elements.MyScreen.WebView.TestField, new TapPoint(50,50));
-```
-
-```VB
-Me.ActiveDevice.Web.TapAtPoint(Elements.MyScreen.WebView.TestField, New TapPoint(50, 50))
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterleft"></a>
-## TapCenterLeftQuery[] viewQuery, Query[] elementQuery)
-
-Tap an element on center left point.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap an element on center left point.
-this.ActiveDevice.Web.TapCenterLeft(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapCenterLeft(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterright"></a>
-## TapCenterRight(Query[] viewQuery, Query[] elementQuery)
-
-Tap an element on center right point.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap an element on center right point.
-this.ActiveDevice.Web.TapCenterRight(Elements.MyScreen.WebView.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapCenterRight(Elements.MyScreen.WebView.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="twofingerrotate"></a>
-## TwoFingerRotate(Query[] viewQuery, Query[] elementQuery, TapPoint point, int angle)
-
-Perform rotate gesture at the specified location within the element specified by the query. 
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*elementQuery (WebQuery)* - WebQuery object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordinates of rotation center point.
-
-*angle (int)* - The angle in degrees to rotate. The default value is 0.
-
-### Example
-
-```C#
-// Rotate the test element starting from 100x, 100y within the element and rotating for 45 degrees
-this.ActiveDevice.Web.TwoFingerRotate(Elements.MyScreen.WebView.TestField, new TapPoint(100, 100), 45);
-```
-
-```VB
-Me.ActiveDevice.Web.TwoFingerRotate(Elements.MyScreen.WebView.TestField, New TapPoint(100, 100), 45)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="wait"></a>
-## Wait(int timeout)
-
-Wait specific amount of time before continuing execution.
-
-### Parameters
-
-*timeout (int)* - The amount of time to wait in milliseconds.
-
-### Example
-
-```C#
-// Wait for 2 seconds
-this.ActiveDevice.Web.Wait(2000);
-```
-
-```VB
-Me.ActiveDevice.Web.Wait(2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitfor"></a>
-## WaitFor(Func&lt;bool&gt; func, int checkInterval, int timeout)
-
-Wait for func to return true or timeouts.
-
-### Parameters
-
-*func (Func&lt;bool&gt;)* - A delegate to a function that is called on every interval.
-
-*checkInterval (int)* - Check interval in milliseconds. Can't be less than or equal to 0.
-
-*timeout (int)* - Timeout interval in milliseconds. Can't be less than or equal to 0. Can't be less than `checkInterval`.
-
-### Example
-
-```C#
-// Execute TestMethod1 for 2 sec every 100ms until it returns true or timeouts.
-this.ActiveDevice.Web.WaitFor(TestMethod1, 100, 2000);
-```
-
-```VB
-Me.ActiveDevice.Web.WaitFor(TestMethod1, 100, 2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforscriptresult"></a>
-## WaitForScriptResult(Query[] viewQuery, string script, Query[] elementQuery, dynamic result, int checkInterval, int timeout)
-
-Wait until script execution matches specified value or timeout occurs.
-
-### Parameters
-
-*viewQuery (AndroidQuery or IOSQuery)* - native query for target WebView container object.
-
-*script (string)* - String that is transferred and evaled into current web view on every interval.
-
-*elementQuery (WebQuery)* - WebQuery for target element. Element defined by this parameter can be accessed using `targetElement` variable inside the script parameter string.
-
-*result (dynamic)* - Script result to be matched.
-
-*checkInterval (int)* - Check interval in milliseconds. Can't be less than or equal to 0.
-
-*timeout (int)* - Timeout interval in milliseconds. Can't be less than or equal to 0. Can't be less than `checkInterval`.
-
-### Example
-
-```C#
-// Wait for a specific result from script - wait for the readyState to return `complete` by checking every 10ms for 2 sec timeout.
-this.ActiveDevice.Web.WaitForScriptResult("document.readyState", null, "complete", 10, 2000);
-```
-
-```VB
-Me.ActiveDevice.Web.WaitForScriptResult("document.readyState", Nothing, "complete", 10, 2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
\ No newline at end of file
diff --git a/docs/test-studio-mobile/api-reference/ios.md b/docs/test-studio-mobile/api-reference/ios.md
deleted file mode 100644
index 04197a30..00000000
--- a/docs/test-studio-mobile/api-reference/ios.md
+++ /dev/null
@@ -1,996 +0,0 @@
----
-title: iOS
-page_title: iOS
-description: "Telerik Mobile Testing - API Reference - iOS"
-position: 0
-publish: true
-slug: ms-ios-api
----
-
-# iOS
-
-Methods
-<select id="methodsSelect" onchange="window.location.hash='#'+event.currentTarget.selectedOptions[0].value;">
- <option value="DragCellToIndexPath">DragCellToIndexPath</option>  <option value="DragToDisplacement">DragToDisplacement</option> <option value="DragToPoint">DragToPoint</option>  <option value="ElementExists">ElementExists</option>  <option value="elementvisible">ElementVisible</option>  <option value="getpropertyvalue">GetPropertyValue</option>   <option value="PressDismiss">PressDismiss</option>  <option value="PressReturn">
-PressReturn</option>  <option value="PinchIn">PinchIn</option>  <option value="PinchOut">PinchOut</option><option value="ScrollToItem">ScrollToItem</option>  <option value="ScrollToRow">ScrollToRow</option> <option value="SelectRowInComponent">SelectRowInComponent</option>  <option value="SelectRow">SelectRow</option>  <option value="SelectItem">SelectItem</option>  <option value="SetDate">SetDate</option>    <option value="SetText">SetText</option>  <option value="SetValue">SetValue</option>  <option value="Screenshot">Screenshot</option>  <option value="Swipe">Swipe</option>  <option value="Tap">Tap</option><option value="TapAtLocation">TapAtLocation</option>  <option value="TapAtPoint">TapAtPoint</option>  <option value="TapCenterLeft">TapCenterLeft</option>  <option value="TapCenterRight">TapCenterRight</option>  <option value="TapAndHold">TapAndHold</option>  <option value="TypeText">TypeText</option>  <option value="TapSubviewAtIndex">TapSubviewAtIndex</option> 
-<option value="Toggle">Toggle</option> <option value="TwoFingerRotate">TwoFingerRotate</option> <option value="Wait">Wait</option>
-<option value="WaitForElementExists">WaitForElementExists</option>  <option value="WaitForElementVisible">WaitForElementVisible</option> <option value="WaitForPropertyValue">WaitForPropertyValue</option> 
-
-</select>
-
-Methods for automating native iOS applications.
-
-##Methods
-
-
-<a id="DragCellToIndexPath"></a>
-## DragCellToIndexPath(IOSQuery[] query, int fromRow, int fromSection, int toRow, int toSection)
-
-Drags the cell from the specified row and section to a different row and section.
-
-Supports views and subclasses of: **UITableView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*fromRow (int)* - The row to drag from.
-
-*fromSection (int)* - The section that contains the fromRow.
-
-*toRow (int)* - The row to drag to.
-
-*toSection (int)* - The section that contains the toRow.
-
-### Example
-
-```C#
-// This will drag table cell from row 1 to row 4 in the TableView
-this.ActiveDevice.IOS.DragCellToIndexPath(Elements.MyScreen.UITableView, 1,0,4,0);	
-```
-
-```VB
-Me.ActiveDevice.IOS.DragCellToIndexPath(Elements.MyScreen.UITableView, 1,0,4,0)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="DragToDisplacement"></a>
-## DragToDisplacement(IOSQuery[] query, TapPoint fromPoint, TapPoint displacement, int steps)
-
-Performs a drag gesture from a location to a displacement from that location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*fromPoint (TapPoint)* - The x, y position in the view to start the drag from.
-
-*displacement (TapPoint)* - The x, y distance from the fromPoint to end the drag.
-
-*steps (int)* - The amount of touches to generate to complete the drag. 3 minimum and not more than 1000.
-
-### Example
-
-```C#
-// This will drag an item in UIView from 100x,100y point to 100x,300y point relative to that UIView using 200 touches
-this.ActiveDevice.IOS.DragToDisplacement(Elements.MyScreen9.UIView, new TapPoint(100,100),new TapPoint(100,300),200);
-```
-
-```VB
-Me.ActiveDevice.IOS.DragToDisplacement(Elements.MyScreen9.UIView, New TapPoint(100, 100), New TapPoint(100, 300), 200)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="DragToPoint"></a>
-## DragToPoint(IOSQuery[] query, TapPoint fromPoint, TapPoint toPoint, int steps)
-
-Performs a drag gesture from a location to a location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*fromPoint (TapPoint)* - The x, y position in the view to start the drag from.
-
-*toPoint (TapPoint)* - The x, y position in the view to end the drag.
-
-*steps (int)* - The amount of touches to generate to complete the drag. 3 minimum and not more than 1000.
-
-### Example
-
-```C#
-// This will drag an item in UIView from 100x,100y point to 100x,300y point in the same UIView using 200 touches
-this.ActiveDevice.IOS.DragToPoint(Elements.MyScreen9.UIView, new TapPoint(100,100),new TapPoint(100,300),200);
-```
-
-```VB
-Me.ActiveDevice.IOS.DragToPoint(Elements.MyScreen9.UIView, New TapPoint(100, 100), New TapPoint(100, 300), 200)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="ElementExists"></a>
-## ElementExists(IOSQuery[] query)
-
-Checks if the view specified by the query exists, and returns the result as boolean.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-### Return Value
-
-Exists boolean
-
-### Example
-
-```C#
-// This will verify that the UISwitch exists and return the result as booelan 
-bool exists = this.ActiveDevice.IOS.ElementExists(Elements.MyScreen9.UISwitch);
-```
-
-```VB
-Me.ActiveDevice.IOS.ElementExists(Elements.MyScreen9.UISwitch)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="elementvisible"></a>
-## ElementVisible(IOSQuery[] query)
-
-Checks if the view specified by the query is visible, and returns the result as boolean.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-### Return Value
-
-isVisible boolean
-
-### Example
-
-```C#
-// This will verify that the UISwitch is visible on the screen and return the result as booelan 
-bool visible = this.ActiveDevice.IOS.ElementVisible(Elements.MyScreen9.UISwitch);
-```
-
-```VB
-Dim visible As Boolean = Me.ActiveDevice.IOS.ElementVisible(Elements.MyScreen9.UISwitch)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getpropertyvalue"></a>
-## GetPropertyValue(IOSQuery[] query, string propertyName)
-
-Retrieves the value of a property from a specified view.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*propertyName (string)* - The string name of the property.
-
-### Return Value
-
-The String value of the property.
-
-### Example
-
-```C#
-// This will get the value of "text" property of a label and save it in the LabelText string
-string LabelText = this.ActiveDevice.IOS.GetPropertyValue(Elements.MyScreen1.UILabel, "text");
-```
-
-```VB
-Dim LabelText As String = Me.ActiveDevice.IOS.GetPropertyValue(Elements.MyScreen1.UILabel, "text")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="PressDismiss"></a>
-## PressDismiss()
-
-Presses dismiss on the keyboard.
-
-### Example
-
-```C#
-// This will press the dismiss key on the keyboard
-this.ActiveDevice.IOS.PressDismiss();
-```
-
-```VB
-Me.ActiveDevice.IOS.PressDismiss()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="PressReturn"></a>
-## PressReturn()
-
-Presses return on the keyboard.
-
-### Example
-
-```C#
-// This will press the return key on the keyboard
-this.ActiveDevice.IOS.PressReturn();
-```
-
-```VB
-Me.ActiveDevice.IOS.PressReturn()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="PinchIn"></a>
-## PinchIn(IOSQuery[] query, TapPoint point, int distance, int steps)
-
-Performs a pinch in gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The x, y center point to pinch into the view. If null, defaults to center point in view.
-
-*distance (int)* - The distance away from the center point to start the pinch. Cannot be less than 1.
-
-*steps (int)* - The amount of touches to generate to complete the pinch in. Cannot be less than 3 and more than 1000.
-
-### Example
-
-```C#
-// This will Pinch In over the center of the UIView and with each finger at 20 pixels from the center of the UIView. The Pinch in action will performed in 100 "touches".
-this.ActiveDevice.IOS.PinchIn(Elements.MyScreen9.UIView,null,20,100);
-```
-
-```VB
-Me.ActiveDevice.IOS.PinchIn(Elements.MyScreen9.UIView,null,20,100)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="PinchOut"></a>
-## PinchOut(IOSQuery[] query, TapPoint point, int distance, int steps)
-
-Performs a pinch out gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The x, y position to pinch out from in the view. If null, defaults to center point in view.
-
-*distance (int)* - The distance away from the center point to end the pinch. Cannot be less than 1.
-
-*steps (int)* - The amount of touches to generate to complete the pinch out. Cannot be less than 3 and more than 1000.
-
-### Example
-
-```C#
-// This will Pinch Out over the center of the UIView and with each finger at 20 pixels from the center of the UIView. The Pinch out action will performed in 100 "touches".
-this.ActiveDevice.IOS.PinchOut(Elements.MyScreen9.UIView,null,20,100);
-```
-
-```VB
-Me.ActiveDevice.IOS.PinchOut(Elements.MyScreen9.UIView,null,20,100)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="ScrollToItem"></a>
-## ScrollToItem(IOSQuery[] query, int item, int section, IOSCollectionViewScrollPosition cvScrollPosition)
-
-Scrolls to an item in a section on a view specified by the query.
-
-Supports views and subclasses of: **UICollectionView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*item (int)* - Тhe index of the item to scroll to.
-
-*section (int)* - Тhe section that contains the item to scroll to.
-
-*cvScrollPosition (IOSCollectionViewScrollPosition)* - (enum) the position in the UI the item should scroll to.
-
-### Example
-
-```C#
-// This will select an item with index 4 that is part of UICollection
-this.ActiveDevice.IOS.SelectItem(Elements.MyScreen2.UICollectionView, 4, 0);
-```
-
-```VB
-Me.ActiveDevice.IOS.SelectItem(Elements.MyScreen2.UICollectionView, 4, 0)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="ScrollToRow"></a>
-## ScrollToRow(IOSQuery[] query, int row, int section, IOSTableViewScrollPosition tvScrollPosition)
-
-Scrolls to a row in a section on a view specified by the query.
-
-Supports views and subclasses of: **UITableView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*row (int)* - Тhe row to scroll to.
-
-*section (int)* - Тhe section that contains the row to scroll to.
-
-*tvScrollPosition (IOSTableViewScrollPosition)* - (enum) The position in the UI the row should scroll to.
-
-### Example
-
-```C#
-// This will scroll to row 5, section 0 of UITableView and will make sure that the row will appear as close as possible to the top of the screen
-this.ActiveDevice.IOS.ScrollToRow(Elements.MyScreen.UITableView, 5, 0, IOSTableViewScrollPosition.Top);
-```
-
-```VB
-Me.ActiveDevice.IOS.ScrollToRow(Elements.MyScreen.UITableView, 5, 0, IOSTableViewScrollPosition.Top)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SelectRowInComponent"></a>
-## SelectRowInComponent(IOSQuery[] query, int row, int component)
-
-Selects a row in a component of a view specified by the query.
-
-Supports views and subclasses of: **UIPickerView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*row (int)* - The row to select.
-
-*component (int)* - The index of the component that contains the row to select.
-
-### Example
-
-```C#
-// Select row 5 from component 0 in the UIPicker 
-this.ActiveDevice.IOS.SelectRowInComponent(Elements.MyScreen5.UIPickerView, 5, 0);
-```
-
-```VB
-Me.ActiveDevice.IOS.SelectRowInComponent(Elements.MyScreen5.UIPickerView, 5, 0)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SelectRow"></a>
-## SelectRow(IOSQuery[] query, int row, int section)
-
-Selects a row in a section on a view specified by the query.
-
-Supports views and subclasses of: **UITableView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*row (int)* - The row to select.
-
-*section (int)* - The table view section that contains the row to select.
-
-### Example
-
-```C#
-//This will select row 5, section 0 from the UITableView element
-this.ActiveDevice.IOS.SelectRow(Elements.MyScreen.UITableView, 5,0);
-```
-
-```VB
-Me.ActiveDevice.IOS.SelectRow(Elements.MyScreen.UITableView, 5,0)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SelectItem"></a>
-## SelectItem(IOSQuery[] query, int item, int section)
-
-Selects an item in a section on a view specified by the query.
-
-Supports views and subclasses of: **UICollectionView**. The item must currently be visible on the screen.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*item (int)* - The index of the item to select.
-
-*section (int)* - The section that contains the item to select.
-
-### Example
-
-```C#
-//This will select row 5, section 0 from the UITableView element
-this.ActiveDevice.IOS.SelectRow(Elements.MyScreen.UITableView, 5,0);
-```
-
-```VB
-Me.ActiveDevice.IOS.SelectRow(Elements.MyScreen.UITableView, 5,0)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SetDate"></a>
-## SetDate(IOSQuery[] query, DateTime date)
-
-Sets the date on a view specified by the query.
-
-Supports views and subclasses of: **UIDatePicker**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*date (DateTime)* - .NET DateTime object.
-
-### Example
-
-```C#
-// This will set the value of a date picker to 2015-12-12 12:00 AM
-this.ActiveDevice.IOS.SetDate(Elements.MyScreen3.UIDatePicker, new DateTime(2015, 12, 12));
-```
-
-```VB
-Me.ActiveDevice.IOS.SetDate(Elements.MyScreen3.UIDatePicker, new DateTime(2015, 12, 12))
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SetText"></a>
-## SetText(IOSQuery[] query, string text)
-
-Sets the text on a view specified by the query.
-
-Supports views and subclasses of: **UITextField**, **UITextView**, **UISearchBar**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*text (string)* - The text value to set on the view.
-
-### Example
-
-```C#
-// This will set "Set Text" string in the text field
-this.ActiveDevice.IOS.SetText(Elements.MyScreen4.UITextField, "Set Text");
-```
-
-```VB
-Me.ActiveDevice.IOS.SetText(Elements.MyScreen4.UITextField, "Set Text")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="SetValue"></a>
-## SetValue(IOSQuery[] query, double value, int newTimeout = 0)
-
-Sets the value of a view specified by the query.
-
-Supports views and subclasses of **UIStepper**, and **UISlider**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*value (double)* - The value the view should be set to.
-
-*newTimeout (int)* - (optional) An amount of time in milliseconds to wait for the operation to complete.
-
-### Example
-
-```C#
-// This will set Value of 0.5 of the UIStepper and fail the operation if it takes more than 100ms
-this.ActiveDevice.IOS.SetValue(Elements.MyScreen8.UIStepper, 0.5, 100);
-```
-
-```VB
-Me.ActiveDevice.IOS.SetValue(Elements.MyScreen8.UIStepper, 0.5, 100)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="Screenshot"></a>
-## Screenshot()
-
-Takes a screenshot of the tested UI.
-
-Supports views and subclasses of **UIStepper**, and **UISlider**.
-
-### Return Value
-
-The taken screen shot as array of bytes.
-
-### Example
-
-```C#
-// This will make a screenshot of the app under test and return it as an array of bytes
-byte[] screenshotInBytes = this.ActiveDevice.IOS.Screenshot();
-```
-
-```VB
-Dim screenshotInBytes As Byte() = Me.ActiveDevice.IOS.Screenshot()
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="Swipe"></a>
-## Swipe(IOSQuery[] query, SwipeDirection direction)
-
-Performs a swipe gesture across the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*direction (SwipeDirection)* - (enum) The direction to swipe.
-
-### Example
-
-```C#
-// This will perform a swipe gesture over the UIView to the right
-this.ActiveDevice.IOS.Swipe(Elements.MyScreen9.UIView, SwipeDirection.Right);
-```
-
-```VB
-Me.ActiveDevice.IOS.Swipe(Elements.MyScreen9.UIView, SwipeDirection.Right)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="Tap"></a>
-## Tap(IOSQuery[] query, int tapCount = 1, int tapDownDelay = 10, int tapUpDelay = 10)
-
-Performs a tap gesture at the center of the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*tapCount (int)* - (optional) How many times to tap. If null, defaults to 1.
-
-*tapDownDelay (int)* - (optional) The amount of time tap down should last. Defaults to 10 milliseconds and cannot be less.
-
-*tapUpDelay (int)* - (optional) The amount of time tap up should last, if multiple taps are used. Defaults to 10 milliseconds and cannot be less.
-
-### Example
-
-```C#
-// This will tap twice UIRoundedRectButton and will use the default value for tapDownDealy and TapUpDelay
-this.ActiveDevice.IOS.Tap(Elements.MyScreen1.UIRoundedRectButton, 2);
-```
-
-```VB
-Me.ActiveDevice.IOS.Tap(Elements.MyScreen1.UIRoundedRectButton, 2)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapAtLocation"></a>
-## TapAtLocation(IOSQuery[] query, int x, int y, int tapCount = 1)
-
-Performs a tap gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*x (int)* - The x position to tap in the view.
-
-*y (int)* - The y position to tap in the view.
-
-*tapCount (int)* - (optional) - how many times to tap. If null, defaults to 1.
-
-### Example
-
-```C#
-// This will tap twice UIRoundedRectButton at location x=5 and y =10
-this.ActiveDevice.IOS.TapAtLocation(Elements.MyScreen1.UIRoundedRectButton, 5, 10, 2);
-```
-
-```VB
-Me.ActiveDevice.IOS.TapAtLocation(Elements.MyScreen1.UIRoundedRectButton, 5, 10, 2)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapAtPoint"></a>
-## TapAtPoint(IOSQuery[] query, TapPoint point = null, int tapCount = 1, int tapDownDelay = 10, int tapUpDelay = 10)
-
-Performs a tap gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - (optional) The x, y position to tap in the view. If null, defaults to center point in view. If x, or y is negative, that value defaults to the center x, or y of the view.
-
-*tapCount (int)* - (optional) How many times to tap. If null, defaults to 1.
-
-*tapDownDelay (int)* - (optional) The amount of time tap down should last. Defaults to 10 milliseconds and cannot be less.
-
-*tapUpDelay (int)* - (optional) The amount of time tap up should last, if multiple taps are used. Defaults to 10 milliseconds and cannot be less.
-
-### Example
-
-```C#
-// This will perform tap on UIbutton on a specific point relative to the button. In this case the point to tap is with x=10 and y=10 offset.
-TapPoint point = new TapPoint(10,10);
-this.ActiveDevice.IOS.TapAtPoint(Elements.MyScreen1.UIRoundedRectButton, point);
-```
-
-```VB
-Dim point As New TapPoint(10, 10)
-Me.ActiveDevice.IOS.TapAtPoint(Elements.MyScresen1.UIRoundedRectButton, point)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapCenterLeft"></a>
-## TapCenterLeft(IOSQuery[] query)
-
-Performs a tap gesture at the center-left of the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-//This will will tap exactly at the point between the left end and the exact center of the button
-this.ActiveDevice.IOS.TapCenterLeft(Elements.MyScreen1.UIRoundedRectButton);
-```
-
-```VB
-Me.ActiveDevice.IOS.TapCenterLeft(Elements.MyScreen1.UIRoundedRectButton)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapCenterRight"></a>
-## TapCenterRight(IOSQuery[] query)
-
-Performs a tap gesture at the center-right of the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-// This will will tap exactly at the point between the right end and the exact center of the button
-this.ActiveDevice.IOS.TapCenterRight(Elements.MyScreen1.UIRoundedRectButton);
-```
-
-```VB
-Me.ActiveDevice.IOS.TapCenterRight(Elements.MyScreen1.UIRoundedRectButton)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapAndHold"></a>
-## TapAndHold(IOSQuery[] query)
-
-Performs a tap-and-hold gesture at the center of the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-### Example
-
-```C#
-// This will tap the button and hold it tapped for 3 seconds
-this.ActiveDevice.IOS.TapAndHold(Elements.MyScreen1.UIRoundedRectButton);
-```
-
-```VB
-Me.ActiveDevice.IOS.TapAndHold(Elements.MyScreen1.UIRoundedRectButton)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TypeText"></a>
-## TypeText(IOSQuery[] query, string text, int keyDelay)
-
-Taps the view specified by the query, then types the specified text using the keyboard.
-
-Supports views and subclasses of **UITextField**, **UITextView**, and **UISearchBar**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*text (string)* - The text value to set on the view.
-
-*keyDelay (int)* - The delay in milliseconds between each key stroke.
-
-### Example
-
-```C#
-// This will type "Type Text" string in the text field with 20ms delay between key strokes
-this.ActiveDevice.IOS.TypeText(Elements.MyScreen4.UITextField, "Type Text", 20);
-```
-
-```VB
-Me.ActiveDevice.IOS.TypeText(Elements.MyScreen4.UITextField, "Type Text", 20)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TapSubviewAtIndex"></a>
-## TapSubviewAtIndex(IOSQuery[] query, int index)
-
-Taps a subview at an index in the children of a view specified by the query.
-
-Supports views and subclasses of **UISegmentedControl**, **UITabBar**, **UIToolbar**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*index (int)* - The index of the view to tap.
-
-### Example
-
-```C#
-// This will tap a subview of index 3 that is child of UIToolbar control
-this.ActiveDevice.IOS.TapSubviewAtIndex(Elements.MyScreen6.UIToolbar, 3);
-```
-
-```VB
-Me.ActiveDevice.IOS.TapSubviewAtIndex(Elements.MyScreen6.UIToolbar, 3)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="Toggle"></a>
-## Toggle(IOSQuery[] query, bool toggleValue)
-
-Sets the toggle state of a view specified by the query.
-
-Supports views and subclasses of: **UISwitch**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*toggleValue (bool)* - The on/off true/false state to apply to the togglable view.
-
-### Example
-
-```C#
-// Toggles the UISwitch button to true state
-this.ActiveDevice.IOS.Toggle(Elements.MyScreen9.UISwitch, true);
-```
-
-```VB
-Me.ActiveDevice.IOS.Toggle(Elements.MyScreen9.UISwitch, true)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="TwoFingerRotate"></a>
-## TwoFingerRotate(IOSQuery[] query, TapPoint point, int angleInDegrees)
-
-Performs a rotate gesture at the specified location within the view specified by the query.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*point (TapPoint)* - The x, y position of origin to rotate around in the view.
-
-*angleInDegrees (int)* - The angle in degrees to rotate.
-
-### Example
-
-```C#
-// This will rotate 90 degrees the UIView with two fingers starting from 100 x, 100 y position realtive to the UIView
-this.ActiveDevice.IOS.TwoFingerRotate(Elements.MyScreen9.UIView, new TapPoint(100,100), 90);
-```
-
-```VB
-Me.ActiveDevice.IOS.TwoFingerRotate(Elements.MyScreen9.UIView, new TapPoint(100,100), 90)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="Wait"></a>
-## Wait(int miliseconds)
-
-Waits an arbitrary amount of time before continuing execution.
-
-### Parameters
-
-*miliseconds (int)* - The amount of time to wait in milliseconds.
-
-### Example
-
-```C#
-// This will pause the execution and will wait for 10ms
-this.ActiveDevice.IOS.Wait(10);
-```
-
-```VB
-Me.ActiveDevice.IOS.Wait(10)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="WaitForElementExists"></a>
-## WaitForElementExists(IOSQuery[] query, bool exists, int checkInterval, int timeout)
-
-Executes elementExists command until the result matches the specified value or the timeout occurs.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*exists (bool)* - The expected command value.
-
-*checkInterval (int)* - The interval between elementExists command calls.
-
-*timeout (int)* - The overall number of milliseconds to wait for the element to exist.
-
-### Example
-
-```C#
-// This will wait 1000 ms for UISwitch to exists and will check each 10 ms
-this.ActiveDevice.IOS.WaitForElementExists(Elements.MyScreen9.UISwitch, true, 10, 1000);
-```
-
-```VB
-Me.ActiveDevice.IOS.WaitForElementExists(Elements.MyScreen9.UISwitch, true, 10, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="WaitForElementVisible"></a>
-## WaitForElementVisible(IOSQuery[] query, bool isVisible, int checkInterval, int timeout)
-
-Executes elementVisible command until the result matches the specified value or the timeout occurs.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*isVisible (bool)* - The expected command value.
-
-*checkInterval (int)* - The interval between elementVisible command calls.
-
-*timeout (int)* - The overall number of milliseconds to wait for the element to get visible.
-
-### Example
-
-```C#
-// This will wait 1000 ms for UISwitch to be visible and will check each 10 ms
-this.ActiveDevice.IOS.WaitForElementVisible(Elements.MyScreen9.UISwitch, true, 10, 1000);
-```
-
-```VB
-Me.ActiveDevice.IOS.WaitForElementVisible(Elements.MyScreen9.UISwitch, true, 10, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="WaitForPropertyValue"></a>
-## WaitForPropertyValue(IOSQuery[] query, string propertyName, string propertyValue, int checkInterval, int timeout)
-
-Executes getPropertyValue command until the result matches the specified value or the timeout occurs.
-
-Supports views and subclasses of: **UIView**.
-
-### Parameters
-
-*query (IOSQuery)* - Identifies an element uniquely.
-
-*propertyName (string)* - The string name of the property.
-
-*propertyValue (string)* - The expected property value as string.
-
-*checkInterval (int)* - The interval between getPropertyValue command calls.
-
-*timeout (int)* - The overall number of milliseconds to wait for the property value to match.
-
-### Example
-
-```C#
-// This will wait 1000 ms for UILabel property text to become "test" and will check each 10 ms
-this.ActiveDevice.IOS.WaitForPropertyValue(Elements.MyScreen1.UILabel, "text", "test", 10, 1000);
-```
-
-```VB
-Me.ActiveDevice.IOS.WaitForPropertyValue(Elements.MyScreen1.UILabel, "text", "test", 10, 1000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
diff --git a/docs/test-studio-mobile/api-reference/overview.md b/docs/test-studio-mobile/api-reference/overview.md
deleted file mode 100644
index 73045ff1..00000000
--- a/docs/test-studio-mobile/api-reference/overview.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: Overview
-page_title: Overview
-description: "Telerik Mobile Testing - API Reference - Web"
-position: -2
-publish: true
-slug: ms-overview-api
----
-
-#Test Studio Mobile API Reference Guide
-
-Test Studio Mobile API reference describes the different API calls you can use in [coded steps]({% slug ms-coded-steps%}) to fine tune your mobile test automation. Pick the API set based on the platform you are targeting 
-
-*	[Methods for automating native Android applications]({% slug ms-android-api%})
-
-*	[Methods for automating native iOS applications]({% slug ms-ios-api%})
-
-*	[Methods for automating Web applications]({% slug ms-web-api%})
-
-*	[Methods for automating Hybrid applications]({% slug ms-hybrid-api%})
-
-Most API calls require a valid element query, so take some time to learn how to [create queries]({% slug ms-create-query%}) in Test Studio Mobile.
-
-See Also
---------
-
-* [Coded Steps]({% slug ms-coded-steps%})
-* [Code Item]({% slug ms-code-item%})
-* [Code Behind File]({% slug ms-code-behind%})
-* [Output Pane]({% slug ms-output-pane%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/api-reference/web.md b/docs/test-studio-mobile/api-reference/web.md
deleted file mode 100644
index 42d8c413..00000000
--- a/docs/test-studio-mobile/api-reference/web.md
+++ /dev/null
@@ -1,1421 +0,0 @@
----
-title: Web
-page_title: Web
-description: "Telerik Mobile Testing - API Reference - Web"
-position: 0
-publish: true
-slug: ms-web-api
----
-
-# Web
-
-Methods
-<select id="methodsSelect" onchange="window.location.hash='#'+event.currentTarget.selectedOptions[0].value;">
-<option value="click">Click</option>
-<option value="doubleclick">DoubleClick</option>
-<option value="drag">Drag</option>
-<option value="dragtodisplacement">DragToDisplacement</option>
-<option value="dragtoelement">DragToElement</option>
-<option value="dragtopoint">DragToPoint</option>
-<option value="executescript">ExecuteScript</option>
-<option value="getattribute">GetAttribute</option>
-<option value="getchecked">GetChecked</option>
-<option value="getcolumncount">GetColumnCount</option>
-<option value="gethtml">GetHtml</option>
-<option value="getinerror">GetInError</option>
-<option value="getpaused">GetPaused</option>
-<option value="getrowcount">GetRowCount</option>
-<option value="getscriptresult">GetScriptResult</option>
-<option value="getselectedindex">GetSelectedIndex</option>
-<option value="getselectedtext">GetSelectedText</option>
-<option value="getselectedvalue">GetSelectedValue</option>
-<option value="getstyle">GetStyle</option>
-<option value="gettextcontent">GetTextContent</option>
-<option value="getvalue">GetValue</option>
-<option value="hoverover">HoverOver</option>
-<option value="navigatetourl">NavigateToUrl</option>
-<option value="pinchin">PinchIn</option>
-<option value="pinchout">PinchOut</option>
-<option value="presskey">PressKey</option>
-<option value="rightclick">RightClick</option>
-<option value="scroll">Scroll</option>
-<option value="scrolltoelement">ScrollToElement</option>
-<option value="setattribute">SetAttribute</option>
-<option value="setchecked">SetChecked</option>
-<option value="sethtml">SetHtml</option>
-<option value="setpaused">SetPaused</option>
-<option value="setselectedindex">SetSelectedIndex</option>
-<option value="setselectedtext">SetSelectedText</option>
-<option value="setselectedvalue">SetSelectedValue</option>
-<option value="setstyle">SetStyle</option>
-<option value="settextcontent">SetTextContent</option>
-<option value="setvalue">SetValue</option>
-<option value="swipe">Swipe</option>
-<option value="tap">Tap</option>
-<option value="tapandhold">TapAndHold</option>
-<option value="tapatlocation">TapAtLocation</option>
-<option value="tapatpoint">TapAtPoint</option>
-<option value="tapcenterleft">TapCenterLeft</option>
-<option value="tapcenterright">TapCenterRight</option>
-<option value="twofingerrotate">TwoFingerRotate</option>
-<option value="wait">Wait</option>
-<option value="waitfor">WaitFor</option>
-<option value="waitforscriptresult">WaitForScriptResult</option>
-<option value="waitforurl">WaitForUrl</option>
-</select>
-
-Methods for automating web applications.
-
-##Methods
-
-<a id="click"></a>
-## Click(Query[] query)
-
-Perform a click on an element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will perform a web click action on the provided element
-this.ActiveDevice.Web.Click(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.DoubleClick(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="doubleclick"></a>
-## DoubleClick(Query[] query)
-
-Perform a double click on an element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will perform a web double click on the provided element
-this.ActiveDevice.Web.DoubleClick(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.DoubleClick(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="drag"></a>
-## Drag(Query[] query, int offsetX, int offsetY)
-
-Drag an element to specific point.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*offsetX (int)* - Destination point horizontal offset from element center.
-
-*offsetY (int)* - Destination point vertical offset from element center.
-
-### Example
-
-```C#
-// This will drag a draggable web element to 100x,300y point realtive to the center of the provided element
-this.ActiveDevice.Web.Drag(Elements.MyScreen.DragElement, 100,300);
-```
-
-```VB
-Me.ActiveDevice.Web.Drag(Elements.MyScreen.DragElement, 100, 300)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtodisplacement"></a>
-## DragToDisplacement(Query[] query, TapPoint fromPoint, TapPoint displacement, int steps)
-
-Performs drag gesture from a point to a displacement within the element specified by the query.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*fromPoint (TapPiont)* - Starting point of drag gesture. If null, defaults to center point in view.
-
-*displacement (TapPiont)* - Displacement, represented as point object. If null, defaults to center point of element.
-
-*steps (int)* - The amount of touches to generate to complete the drag gesture.  Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// This will drag an item in web view from 0x,0y point (relative to the element) to 100x,300y point relative to the first TapPoint(0,0) in 150 simulated touches
-this.ActiveDevice.Web.DragToDisplacement(Elements.MyScreen.DragElement, new TapPoint(0,0), new TapPoint(100,300), 150);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToDisplacement(Elements.MyScreen.DragElement, New TapPoint(0, 0), New TapPoint(100, 300), 150)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtoelement"></a>
-## DragToElement(Query[] dragElementQuery, Query[] toElementQuery)
-
-Drag an element over another element.
-
-### Parameters
-
-*dragElementQuery (WebQuery)* - Query object that identifies element to be dragged. The element to be dragged must be draggable.
-
-*toElementQuery (WebQuery)* - Query object that identifies element the dragged element will be dragged over.
-
-### Example
-
-```C#
-// Drag element dragElement on top of element TestField
-this.ActiveDevice.Web.DragToElement(Elements.MyScreen.DragElement, Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToElement(Elements.MyScreen.DragElement, Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="dragtopoint"></a>
-## DragToPoint(Query[] query, TapPoint fromPoint, TapPoint toPoint, int steps )
-
-Drag an element over another element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*fromPoint (TapPiont)* - Starting point of drag gesture. If null, defaults to center point of element.
-
-*displacement (TapPiont)* - Finishing point of drag gesture. If null, defaults to center point of element.
-
-*steps (int)* - The amount of touches to generate to complete the drag gesture.  Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// This will drag an item in web view from 0x,0y point inside the specified element to 100x,300y point relative to the element in 150 simulated touches
-this.ActiveDevice.Web.DragToPoint(Elements.MyScreen.DragElement, new TapPoint(0,0), new TapPoint(100,300), 150);
-```
-
-```VB
-Me.ActiveDevice.Web.DragToPoint(Elements.MyScreen.DragElement, New TapPoint(0, 0), New TapPoint(100, 300), 150)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="executescript"></a>
-## ExecuteScript(string script, Query[] query)
-
-Execute a script into web browser.
-
-### Parameters
-
-*script (string)* - String that is transferred to application under test and evaled into current web page.
-
-*query (WebQuery)* - Query for target element. Element defined by this parameter can be accessed using targetElement variable inside the script parameter string.
-
-### Example
-
-```C#
-// Executes the script inside the string parameter on the web app under test. Deprecated: Use getScriptResult instead.
-this.ActiveDevice.Web.ExecuteScript("document.getElementsByTagName(\"div\")");
-```
-
-```VB
-Me.ActiveDevice.Web.ExecuteScript("document.getElementsByTagName(""div"")")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getattribute"></a>
-## GetAttribute(Query[] query, string attrName)
-
-Get attribute value of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*attrName (string)* - Name of the attribute.
-
-### Example
-
-```C#
-// Get attribute will return the id attribute of DragElement as string
-string idAttribute = this.ActiveDevice.Web.GetAttribute(Elements.MyScreen.DragElement, "id");
-```
-
-```VB
-Dim idAttribute As String = Me.ActiveDevice.Web.GetAttribute(Elements.MyScreen.DragElement, "id")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getchecked"></a>
-## GetChecked(Query[] query)
-
-Gets checked state of specific checkbox element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-
-### Example
-
-```C#
-// Returns the checked state of the checkBox as boolean
-bool state = this.ActiveDevice.Web.GetChecked(Elements.MyScreen.CheckBox);
-```
-
-```VB
-Dim state As Boolean = Me.ActiveDevice.Web.GetChecked(Elements.MyScreen.CheckBox)
-```
-
-### Return Value
-
-The checked state of specific checkbox element.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
-<a id="getcolumncount"></a>
-## GetColumnCount(Query[] query, uint rowIndex)
-
-Gets checked state of specific checkbox element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*rowIndex (unit)* - Index of row which column count is needed.
-
-### Example
-
-```C#
-// Returns the number of columns in the desired table row
-uint count = this.ActiveDevice.Web.GetColumnCount(Elements.MyScreen.TableView, 1);
-```
-
-```VB
-Dim count As UInteger = Me.ActiveDevice.Web.GetColumnCount(Elements.MyScreen.TableView, 1)
-```
-
-### Return Value
-
-The number of columns in a particular row in table element.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="gethtml"></a>
-## GetHtml(Query[] query)
-
-Get inner html of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Gets the inner HTML of CheckBox
-string html = this.ActiveDevice.Web.GetHtml(Elements.MyScreen.CheckBox);
-```
-
-```VB
-Dim html As String = Me.ActiveDevice.Web.GetHtml(Elements.MyScreen.CheckBox)
-```
-
-### Return Value
-
-The inner html of specific element as string.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getinerror"></a>
-## GetInError(Query[] query)
-
-Gets error state of audio/video element. This function returns inconsistent results for mobile browsers. Use only with desktop browsers.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-bool statePlayer = this.ActiveDevice.Web.GetInError(Elements.MyScreen.Player);
-```
-
-```VB
-Dim statePlayer As Boolean = Me.ActiveDevice.Web.GetInError(Elements.MyScreen.Player)
-```
-
-### Return Value
-
-True if control is in error state, otherwise false.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getpaused"></a>
-## GetPaused(Query[] query)
-
-Get paused state of audio/video element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-bool statePaused = this.ActiveDevice.Web.GetPaused(Elements.MyScreen.Player);
-```
-
-```VB
-Dim statePaused As Boolean = Me.ActiveDevice.Web.GetPaused(Elements.MyScreen.Player)
-```
-
-### Return Value
-
-True if audio/video element is paused, otherwise false.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getrowcount"></a>
-## GetRowCount(Query[] query)
-
-Get number of rows of a table element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Returns the number of rows in the TableView
-uint rowCount = this.ActiveDevice.Web.GetRowCount(Elements.MyScreen.TableView);
-```
-
-```VB
-Dim rowCount As UInteger = Me.ActiveDevice.Web.GetRowCount(Elements.MyScreen.TableView)
-```
-
-### Return Value
-
-The number of rows of a table element.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getscriptresult"></a>
-## GetScriptResult(string script, Query[] query)
-
-Get number of rows of a table element.
-
-**Note:** In order you se this method you should add reference assembly to **Microsoft.CSharp.dll** and **System.Core.dll** from the <a href="/test-studio-mobile/getting-started-mb/project-settings" target="_blank">project settings</a>.
-
-### Parameters
-
-*script (string)* - String that is transferred to application under test and evaled into current web page.
-
-*query (WebQuery)* - Query for target element. Element defined by this parameter can be accessed using targetElement variable inside the script parameter string.
-
-### Example
-
-```C#
-// This will execute the script in the string and save the result as object
-object result = this.ActiveDevice.Web.GetScriptResult("document.getElementsByTagName(\"div\")");
-```
-
-```VB
-Dim result As Object = Me.ActiveDevice.Web.GetScriptResult("document.getElementsByTagName(""div"")")
-```
-
-### Return Value
-
-Result of script execution.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedindex"></a>
-## GetSelectedIndex(Query[] query)
-
-Get selected index of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Get the selected index of the Select element (select type element), more than one items can be selected
-uint[] index = this.ActiveDevice.Web.GetSelectedIndex(Elements.MyScreen.Select);
-```
-
-```VB
-Dim index As UInteger() = Me.ActiveDevice.Web.GetSelectedIndex(Elements.MyScreen.Select)
-```
-
-### Return Value
-
-Array of selected indexes.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedtext"></a>
-## GetSelectedText(Query[] query)
-
-Get selected text values of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Gets the selected text/s from selected items in the select element
-string[] selectedText = this.ActiveDevice.Web.GetSelectedText(Elements.MyScreen.Select);
-```
-
-```VB
-Dim selectedText() As String = Me.ActiveDevice.Web.GetSelectedText(Elements.MyScreen.Select)
-```
-
-### Return Value
-
-Array of selected text values.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getselectedvalue"></a>
-## GetSelectedValue(Query[] query)
-
-Get selected value strings of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Gets the selected value/s from selected items in the select element
-string[] selectedValue = this.ActiveDevice.Web.GetSelectedValue(Elements.MyScreen.Select);
-```
-
-```VB
-Dim selectedValue As String() = Me.ActiveDevice.Web.GetSelectedValue(Elements.MyScreen.Select)
-```
-
-### Return Value
-
-Array of selected value strings.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getstyle"></a>
-## GetStyle(Query[] query, string styleProp)
-
-Get specific style property value.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*styleProp (string)* - Name of the style attribute.
-
-### Example
-
-```C#
-// Get style will return the width style in the example
-string style = this.ActiveDevice.Web.GetStyle(Elements.MyScreen.TestField, "width");
-```
-
-```VB
-Dim style As String = Me.ActiveDevice.Web.GetStyle(Elements.MyScreen.TestField, "width")
-```
-
-### Return Value
-
-The value of requested style attribute.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="gettextcontent"></a>
-## GetTextContent(Query[] query)
-
-Get text content of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will return the text content of the test element
-string textContent = this.ActiveDevice.Web.GetTextContent(Elements.MyScreen.TestField);
-```
-
-```VB
-Dim textContent As String = Me.ActiveDevice.Web.GetTextContent(Elements.MyScreen.TestField)
-```
-
-### Return Value
-
-Text content of specified element.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="getvalue"></a>
-## GetValue(Query[] query)
-
-Get value of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// This will return the value of the test element
-string valueOfElement = this.ActiveDevice.Web.GetValue(Elements.MyScreen.TestField);
-```
-
-```VB
-Dim valueOfElement As String = Me.ActiveDevice.Web.GetValue(Elements.MyScreen.TestField)
-```
-
-### Return Value
-
-Value of specified element.
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="hoverover"></a>
-## HoverOver(Query[] query)
-
-Perform a mouse hover over an element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Perform a mouse hover action
-this.ActiveDevice.Web.HoverOver(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.HoverOver(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-
-<a id="navigatetourl"></a>
-## NavigateToUrl(string url)
-
-Make the browser under test navigate to specific URL.
-
-### Parameters
-
-*url (string)* - The URL to navigate to.
-
-### Example
-
-```C#
-// Make the browser under test navigate to http://telerik.com
-this.ActiveDevice.Web.NavigateToUrl("http://telerik.com");
-```
-
-```VB
-Me.ActiveDevice.Web.NavigateToUrl("http://telerik.com")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pinchin"></a>
-## PinchIn(Query[] query, TapPoint point, int distance, int steps)
-
-Perform pinch in gesture at the specified location within the view specified by the query. 
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordintes of pinch center point. If null, defaults to center point of element.
-
-*distance (int)* - Distance away from the center to start. Minimum value is 20.
-
-*steps (int)* - The amount of touches to generate to complete the pinch. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// Perform a pinch in over the test element where the pinch will start at 100x,100y point within the element and will pinchIn 20px in 50 simulated touches
-this.ActiveDevice.Web.PinchIn(Elements.MyScreen.TestField, new TapPoint(100,100), 20, 50);
-```
-
-```VB
-Me.ActiveDevice.Web.PinchIn(Elements.MyScreen.TestField, New TapPoint(100, 100), 20, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="pinchout"></a>
-## PinchOut(Query query, TapPoint point, int distance, int steps)
-
-Perform pinch out gesture at the specified location within the view specified by the query.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordintes of pinch center point. If null, defaults to center point of element.
-
-*distance (int)* - Distance away from the center to start. Minimum value is 20.
-
-*steps (int)* - The amount of touches to generate to complete the pinch. Valid values are in the range: 3 - 1000.
-
-### Example
-
-```C#
-// Perform a pinch in over the test element where the pinch out will start at 100x,100y point within the element and will pinchOut 20px in 50 simulated touches
-this.ActiveDevice.Web.PinchOut(Elements.MyScreen.TestField, new TapPoint(100,100), 20, 50);
-```
-
-```VB
-Me.ActiveDevice.Web.PinchOut(Elements.MyScreen.TestField, New TapPoint(100, 100), 20, 50)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="presskey"></a>
-## PressKey(Query[] query, int keyCode, bool alt, bool ctrl, bool shift)
-
-Invoke press key event on specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*keyCode (int)* - Code of the key.
-
-*alt (boolean)* - Boolean value indicating whether ALT is pressed. The default is false.
-
-*ctrl (boolean)* - Boolean value indicating whether CTRL is pressed. The default is false.
-
-*shift (boolean)* - Boolean value indicating whether SHIFT is pressed. The default is false.
-
-### Example
-
-```C#
-// This will invoke the press CAPS LOCK key event (with code 20) over the test element 
-this.ActiveDevice.Web.PressKey(Elements.MyScreen.TestField, 20);
-```
-
-```VB
-Me.ActiveDevice.Web.PressKey(Elements.MyScreen.TestField, 20)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="rightclick"></a>
-## RightClick(Query[] query)
-
-Perform a right click on an element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Perform a right click on the test element
-this.ActiveDevice.Web.RightClick(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.RightClick(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="scroll"></a>
-## Scroll(Query[] query, int x = 0, int y = 0)
-
-Scroll the web page to any element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*x (int)* - The X confidantes of the specific element.
-
-*y (int)* - The Y confidantes of the specific element.
-
-
-
-### Example
-
-```C#
-// Scroll to a 300x, 300y point relative to the element
-this.ActiveDevice.Web.Scroll(Elements.MyScreen.TestField, 300, 300);
-```
-
-```VB
-Me.ActiveDevice.Web.Scroll(Elements.MyScreen.TestField, 300, 300)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="scrolltoelement"></a>
-## ScrollToElement(Query[] query)
-
-Scroll the web page to any element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Scroll to the test element to make it visible on the screen
-this.ActiveDevice.Web.ScrollToElement(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.ScrollToElement(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setattribute"></a>
-## SetAttribute(Query[] query, string attrName, string attrValue)
-
-Set attribute of specific element to a specific value.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*attrName (string)* - Name of the attribute.
-
-*attrValue (string)* - Value to be set.
-
-### Example
-
-```C#
-// Set the id attribute of the test element to test
-this.ActiveDevice.Web.SetAttribute(Elements.MyScreen.TestField, "id", "test");
-```
-
-```VB
-Me.ActiveDevice.Web.SetAttribute(Elements.MyScreen.TestField, "id", "test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setchecked"></a>
-## SetChecked(Query[] query, bool checkedValue)
-
-Sets checked state of specific checkbox element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*attrName (boolean)* - Checked state value to be set.
-
-### Example
-
-```C#
-// Set the state of the checklbox to false
-this.ActiveDevice.Web.SetChecked(Elements.MyScreen.CheckBox, false);
-```
-
-```VB
-Me.ActiveDevice.Web.SetChecked(Elements.MyScreen.CheckBox, False)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="sethtml"></a>
-## SetHtml(Query[] query, string html)
-
-Set inner html of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*html (sting)* - The Html that will be inserted in the specific element.
-
-### Example
-
-```C#
-// this will set the '<label>text<label>' html to the test element
-this.ActiveDevice.Web.SetHtml(Elements.MyScreen.TestField, "<label>text<label>");
-```
-
-```VB
-Me.ActiveDevice.Web.SetHtml(Elements.MyScreen.TestField, "<label>text<label>")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setpaused"></a>
-## SetPaused(Query[] query, bool pausedState)
-
-Set paused state of audio/video element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*pausedState (boolean)* - Paused state to be set.
-
-### Example
-
-```C#
-// This method will pause the video player
-this.ActiveDevice.Web.SetPaused(Elements.MyScreen.Player, true);
-```
-
-```VB
-Me.ActiveDevice.Web.SetPaused(Elements.MyScreen.Player, True)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedindex"></a>
-## SetSelectedIndex(Query[] query, params uint[] indexes)
-
-Set selected index of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*indexes (uint array)* - Array of selected indexes.
-
-### Example
-
-```C#
-// Selects element with index 3 from the select element
-this.ActiveDevice.Web.SetSelectedIndex(Elements.MyScreen.Select, 3);
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedIndex(Elements.MyScreen.Select, 3)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedtext"></a>
-## SetSelectedText(Query[] query, params string[] text)
-
-Set selected text values of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*text (string array)* - Array of selected text values.
-
-### Example
-
-```C#
-// Selects a specific item by its text in select element
-this.ActiveDevice.Web.SetSelectedText(Elements.MyScreen.Select, "text");
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedText(Elements.MyScreen.Select, "text")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setselectedvalue"></a>
-## SetSelectedValue(Query[] query, params string[] values)
-
-Set selected value strings of select element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*values (string array)* - Array of values.
-
-### Example
-
-```C#
-// Set selected value of select element
-this.ActiveDevice.Web.SetSelectedValue(Elements.MyScreen.Select, "value");
-```
-
-```VB
-Me.ActiveDevice.Web.SetSelectedValue(Elements.MyScreen.Select, "value")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setstyle"></a>
-## SetStyle(Query[] query, string styleProp, string styleValue)
-
-Set specific style property value.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*styleProp (string)* - Name of the style attribute.
-
-*styleValue (string)* - Value to be set.
-
-### Example
-
-```C#
-// This will set the width of the testElement to 5-px
-this.ActiveDevice.Web.SetStyle(Elements.MyScreen.TestField, "width", "50px");
-```
-
-```VB
-Me.ActiveDevice.Web.SetStyle(Elements.MyScreen.TestField, "width", "50px")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="settextcontent"></a>
-## SetTextContent(Query[] query, string textContent)
-
-Set text content of specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*textContent (string)* - Text content to be set.
-
-### Example
-
-```C#
-// This will set the text content of the test element
-this.ActiveDevice.Web.SetTextContent(Elements.MyScreen.TestField, "textToSet");
-```
-
-```VB
-Me.ActiveDevice.Web.SetTextContent(Elements.MyScreen.TestField, "textToSet")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="setvalue"></a>
-## SetValue(Query[] query, string value)
-
-Set value to specific element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*value (string)* - Value to be set.
-
-### Example
-
-```C#
-// Set "test" value to the test element
-this.ActiveDevice.Web.SetValue(Elements.MyScreen.TestField, "test");
-```
-
-```VB
-Me.ActiveDevice.Web.SetValue(Elements.MyScreen.TestField, "test")
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="swipe"></a>
-## Swipe(Query[] query, SwipeDirection direction)
-## Swipe(Query[] query, SwipeDirection direction, int swipeDistance = 200)
-
-Perform a swipe gesture across the view specified by the query. 
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*direction (SwipeDirection)* - Direction to swipe.
-
-*swipeDistance (int)* - Swipe distance, default is '200'.
-
-### Example
-
-```C#
-// Swipe right on the test element
-this.ActiveDevice.Web.Swipe(Elements.MyScreen.TestField, SwipeDirection.Right);
-```
-
-```VB
-Me.ActiveDevice.Web.Swipe(Elements.MyScreen.TestField, SwipeDirection.Right)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tap"></a>
-## Tap(Query[] query, int tapCount, int tapDownDelay, int tapUpDelay)
-
-Tap an element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-*tapDownDelay (int)* - Tap down delay in miliseconds. Min value 50.
-
-*tapUpDelay (int)* - Tap up delay in miliseconds. Min value 50.
-
-### Example
-
-```C#
-// Tap action on the test element
-this.ActiveDevice.Web.Tap(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.Tap(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapandhold"></a>
-## TapAndHold(Query[] query)
-
-Perform tap-and-hold gesture at the center of the element.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap and hold action on the test element
-this.ActiveDevice.Web.TapAndHold(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapAndHold(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatlocation"></a>
-## TapAtLocation(Query[] query, int X, int Y, int tapCount)
-
-Tap an element on particular location. 
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*X (int)* - X coordinate of point to be tapped.
-
-*Y (int)* - Y coordinate of point to be tapped.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-### Example
-
-```C#
-// Tap at 50x,50y point within the test element
-this.ActiveDevice.Web.TapAtLocation(Elements.MyScreen.TestField, 50, 50, 1);
-```
-
-```VB
-Me.ActiveDevice.Web.TapAtLocation(Elements.MyScreen.TestField, 50, 50, 1)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapatpoint"></a>
-## TapAtPoint(Query[] query, TapPoint point, int tapCount, int tapDownDelay, int tapUpDelay)
-
-Tap an element on particular point. 
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*point (TapPoint)* - Point inside element to be tapped.
-
-*tapCount (int)* - Numbers of taps to be performed. Min value 1.
-
-*tapDownDelay (int)* - Tap down delay in miliseconds. Min value 50.
-
-*tapUpDelay (int)* - Tap up delay in miliseconds. Min value 50.
-
-### Example
-
-```C#
-// Tap at 50x,50y point within the test element
-this.ActiveDevice.Web.TapAtPoint(Elements.MyScreen.TestField, new TapPoint(50,50));
-```
-
-```VB
-Me.ActiveDevice.Web.TapAtPoint(Elements.MyScreen.TestField, New TapPoint(50, 50))
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterleft"></a>
-## TapCenterLeft(Query[] query)
-
-Tap an element on center left point.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap an element on center left point.
-this.ActiveDevice.Web.TapCenterLeft(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapCenterLeft(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="tapcenterright"></a>
-## TapCenterRight(Query[] query)
-
-Tap an element on center right point.
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-### Example
-
-```C#
-// Tap an element on center right point.
-this.ActiveDevice.Web.TapCenterRight(Elements.MyScreen.TestField);
-```
-
-```VB
-Me.ActiveDevice.Web.TapCenterRight(Elements.MyScreen.TestField)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="twofingerrotate"></a>
-## TwoFingerRotate(Query[] query, TapPoint point, int angle)
-
-Perform rotate gesture at the specified location within the view specified by the query. 
-
-### Parameters
-
-*query (WebQuery)* - Query object that identifies an element uniquely.
-
-*point (TapPoint)* - Coordinates of rotation center point.
-
-*angle (int)* - The angle in degrees to rotate. The default value is 0.
-
-### Example
-
-```C#
-// Rotate the test element starting from 100x,100y within the element and rotating for 45 degrees
-this.ActiveDevice.Web.TwoFingerRotate(Elements.MyScreen.TestField, new TapPoint(100,100), 45);
-```
-
-```VB
-Me.ActiveDevice.Web.TwoFingerRotate(Elements.MyScreen.TestField, New TapPoint(100, 100), 45)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="wait"></a>
-## Wait(int timeout)
-
-Wait specific amount of time before continuing execution.
-
-### Parameters
-
-*timeout (int)* - The amount of time to wait in milliseconds.
-
-### Example
-
-```C#
-// Wait for 2 seconds
-this.ActiveDevice.Web.Wait(2000);
-```
-
-```VB
-Me.ActiveDevice.Web.Wait(2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitfor"></a>
-## WaitFor(Func<bool> func, int checkInterval, int timeout)
-
-Wait for func to return true or timeout.
-
-### Parameters
-
-*func (Func<bool>)* - Function that is called on every interval.
-
-*checkInterval (int)* - Check interval in milliseconds.
-
-*timeout (int)* - Timeout interval in milliseconds.
-
-### Example
-
-```C#
-// Execute TestMethod1 for 2 sec every 100ms until it returns true of false
-this.ActiveDevice.Web.WaitFor(TestMethod1, 100, 2000);
-```
-
-```VB
-Me.ActiveDevice.Web.WaitFor(TestMethod1, 100, 2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforscriptresult"></a>
-## WaitForScriptResult(string script, Query[] query, dynamic result, int checkInterval, int timeout)
-
-Wait for func to return true or timeout.
-
-### Parameters
-
-*script (string)* - Function that is called on every interval.
-
-*query (WebQuery)* - Query for target element. Element defined by this parameter can be accessed using targetElement variable inside the script parameter string.
-
-*result (dynamic)* - Script result to be matched.
-
-*checkInterval (int)* - Delay in milliseconds between checks.
-
-*timeout (int)* - Number of milliseconds to wait for script result to match.
-
-### Example
-
-```C#
-// Wait for a specific result from script - waith for the readyState to return complete by checking every 10ms for 2 sec timeout
-this.ActiveDevice.Web.WaitForScriptResult("document.readyState", null, "complete", 10, 2000);
-```
-
-```VB
-Me.ActiveDevice.Web.WaitForScriptResult("document.readyState", Nothing, "complete", 10, 2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
-<a id="waitforurl"></a>
-## WaitForUrl(string url, int checkInterval, int timeout)
-
-Wait until current url matches specified value or timeout occurs.
-
-### Parameters
-
-*url (string)* - Url to match.
-
-*checkInterval (int)* - Delay in milliseconds between checks.
-
-*timeout (int)* - Number of milliseconds to wait for script result to match.
-
-### Example
-
-```C#
-// This will wait for the telerik.com page to load and will check every 10ms for 2 seconds
-this.ActiveDevice.Web.WaitForUrl("http://telerik.com", 10, 2000);
-```
-
-```VB
-Me.ActiveDevice.Web.WaitForUrl("http://telerik.com", 10, 2000)
-```
-
-<a href="#methodsSelect">Back to Top</a>
-<br><br>
-
diff --git a/docs/test-studio-mobile/features/code-features/base-test-methods.md b/docs/test-studio-mobile/features/code-features/base-test-methods.md
deleted file mode 100644
index ebd47fc6..00000000
--- a/docs/test-studio-mobile/features/code-features/base-test-methods.md
+++ /dev/null
@@ -1,57 +0,0 @@
----
-title: Base test methods
-page_title: Base test methods
-description: Base test methods
-publish: true
-position: 5
-slug: ms-basetest-methods
-previous_url: /test-studio-mobile/getting-started-mb/code-features/coded-stepsd
----
-
-#Base test methods
-
-Every Native/Hybrid/Web mobile test inherits a base mobile test class that provides some additional functionality. For example, some code can be executed before the test is started or after the test is completed. In these cases you can override the `OnBeforeTestStarted` and `OnAfterTestCompleted` methods the base test class provides. The code below shows how to utilize this scenario and add sample test execution duration calculation to the test execution log.
-
-```C#
-protected override void OnAfterTestCompleted()
-{
-	Log.WriteLine("Test completed at: " + DateTime.Now.ToLongTimeString());
-}
-	
-protected override void OnBeforeTestStarted()
-{
-	Log.WriteLine("Test started at: " + DateTime.Now.ToLongTimeString());
-}
-```
-	
-```VB
-Protected Overrides Sub OnAfterTestCompleted()
-	Log.WriteLine("Test completed at: " + DateTime.Now.ToLongTimeString())
-End Sub
-
-Protected Overrides Sub OnBeforeTestStarted()
-	Log.WriteLine("Test started at: " + DateTime.Now.ToLongTimeString())
-End Sub
-```
-
-Here is a completed view of the test code-behind file:
-
-![Test Base Methods Code](/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/code.png)
-
-Executing the test provides a log file that contains the logged data:
-
-![Test Base Methods Log](/img/test-studio-mobile/getting-started-mb/coded-features/base-test-methods/log.png)
-
-
-See Also
---------
-
-* [Coded Steps]({%slug ms-coded-steps%})
-* [Code Item]({%slug ms-code-item%})
-* [Code Behind File]({%slug ms-code-behind%})
-* [Output Pane]({%slug ms-output-pane%})
-* [Compile Project]({%slug ms-compile-project%})
-* [Android API]({%slug ms-android-api%})
-* [iOS API]({%slug ms-ios-api%})
-* [Hybrid API]({%slug ms-hybrid-api%})
-* [Web API]({%slug ms-web-api%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/code-features/code-behind-file.md b/docs/test-studio-mobile/features/code-features/code-behind-file.md
deleted file mode 100644
index 88dd0fed..00000000
--- a/docs/test-studio-mobile/features/code-features/code-behind-file.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Code-Behind File
-page_title: Code-Behind File
-description: Code-Behind File
-publish: true
-position: 2
-slug: ms-code-behind
-previous_url: /test-studio-mobile/getting-started-mb/code-features/code-behind-file
----
-#Code-Behind File
-
-You can create a code behind file for each test where you can implement [coded steps]({% slug ms-coded-steps%}) and custom test classes.
-
-There are two methods of creating a coded behind file for your test:
-
-1. Add a Coded Step from the [Step Builder]({% slug ms-step-builder%}).
-
-	![Add Coded step](/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig1.png)
-
-2. Right click the test and select **Add Code-Behind**.
-
-	![Add Coded Behind](/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig2.png)
-
-	Select coding language.
-
-	![Select coding language](/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig5.png)
-
-Both actions create a code-behind file with an empty test method where you can implement your custom code. Each code behind file can contain multiple test methods. 
-
-See [Coded Steps]({% slug ms-coded-steps%}) article which describes how to execute the code in the test method.
-
-You can also implement multiple test classes in a single code behind file. If methods of the test class will be bound to coded steps the class must  inherit *IOSTestBase*, *AndroidTestBase* or *WebTestBase* class depending on the type test you are using as shown below. 
-
-![Class code](/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig3.png)
-
-
-In order to use the methods from a particular class you should bind the test to that class. You can do this from the test's properties, select the test from the [Project Explorer]({% slug ms-project-explorer%}) so its properties are shown in the Properties pane.
-
-![Class map](/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig4.png)
-
-
-See Also
---------
-
-* [Compile Project]({% slug ms-compile-project%})
-* [Code Item]({% slug ms-code-item%})
-* [Coded Steps]({% slug ms-coded-steps%})
-* [Android API]({% slug ms-android-api%})
-* [iOS API]({% slug ms-ios-api%})
-* [Hybrid API]({% slug ms-hybrid-api%})
-* [Web API]({% slug ms-web-api%})
-* [Base Test Methods]({% slug ms-basetest-methods%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/code-features/code-item.md b/docs/test-studio-mobile/features/code-features/code-item.md
deleted file mode 100644
index cffe3595..00000000
--- a/docs/test-studio-mobile/features/code-features/code-item.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Code Item
-page_title: Code Item
-description: Code Item
-publish: true
-position: 3
-slug: ms-code-item
-previous_url: /test-studio-mobile/getting-started-mb/code-features/code-item,/test-studio-mobile/getting-started-mb/code-features
----
-#Code Item
-
-Add a code item to create a utility class that defines a set of methods which perform common, often re-used functions. The code item can be used also as a helper class which can assist in providing some extended functionality for your test project.
-
-##How To Create Code Item
-
-1. Right click on the project in the [Project Explorer]({% slug ms-project-explorer%}) or on a folder in the project and click **Add Code Item**.
-
-	![Add Code Item](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig1.png)
-
-2. Choose the coding language.
-
-	![Choose coding language](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig7.png)
-
-3. Choose a name and and click **OK** (HelperClass in our example). 
-
-	![Name of the coded item](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig2.png)
-
-4. The Code Item with HelperClass name is created under the selected location.
-
-	![Created code item](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig3.png)
-
-##How To Use Code Item
-
-This is an example how to use the code item.
-
-1. Open the already created coded item (*HelperClass*).
-
-2. Create a simple [Query]({% slug ms-create-query%}) which locates an element with class *UIStepper* and *Index* 1.
-
-	```C#
-	public static IOSQuery UIStepperControl = new IOSQuery() { Class = "UIStepper", Index = 1};
-	```
-
-	```VB
-	Public Shared UIStepperControl As New IOSQuery() With {.Class = "UIStepper", .Index  = True}
-	``` 
-
-	![Create a query](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig4.png)
-
-3. In order to access the functions and methods from the Code Item in the test code-behind file you should add an using statement which matches the **namespace** of the **HelperClass**.
-
-	![Using statement](/img/test-studio-mobile/getting-started-mb/coded-features/code-item/fig5.png)
-
-
-See Also
---------
-
-* [Compile Project]({% slug ms-compile-project%})
-* [Code-Behind File]({% slug ms-code-behind%})
-* [Coded Steps]({% slug ms-coded-steps%})
-* [Android API]({% slug ms-android-api%})
-* [iOS API]({% slug ms-ios-api%})
-* [Hybrid API]({% slug ms-hybrid-api%})
-* [Web API]({% slug ms-web-api%})
-* [Base Test Methods]({% slug ms-basetest-methods%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/code-features/coded-steps.md b/docs/test-studio-mobile/features/code-features/coded-steps.md
deleted file mode 100644
index e5d3ef4d..00000000
--- a/docs/test-studio-mobile/features/code-features/coded-steps.md
+++ /dev/null
@@ -1,52 +0,0 @@
----
-title: Coded Steps
-page_title: Coded Steps
-description: Coded Steps
-publish: true
-position: 1
-slug: ms-coded-steps
-previous_url: /test-studio-mobile/getting-started-mb/code-features/coded-steps
----
-
-#Coded Steps
-
-Test Studio Mobile supports coded steps. This allows you to write code and have it executed as a test step. Use a coded step for a scenario that requires more complexity than what can be composed with the [Step Builder]({% slug ms-step-builder%}).
-
-1. Add a Coded Step from the [Step Builder]({% slug ms-step-builder%}).
-
-	![Add Coded step](/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig1.png)
-
-2. Select coding language.
-
-	![Select coding language](/img/test-studio-mobile/getting-started-mb/coded-features/code-behind-file/fig5.png)
-
-	This creates a [code-behind file]({% slug ms-code-behind%}) with an empty test method where you can implement your custom code.
-
-3. In order to execute the code in the test method you should bind it to an existing coded step in the test to which this test class belongs.Double click the coded step in your test in order to access the drop down menu with all valid methods. Select one and save the test.
-
-	> valid methods are methods of a Public Partial Class that inherits *IOSTestBase*, *AndroidTestBase*  or *WebTestBase* depending on the test type you are using.
-
-	![Bind a coded step](/img/test-studio-mobile/getting-started-mb/coded-features/coded-steps/fig3.png)
-
-4. Here is an example how to use a simple "Tap" command and how to access the recorded elements that belong to the particular test.
-
-	> All recorded elements are stored in *Elements* collection.
-
-	```C#
-	this.ActiveDevice.IOS.Tap(this.Elements.MyScreen1.UIRoundedRectButton);
-	```
-
-	```VB
-	Me.ActiveDevice.IOS.Tap(Me.Elements.MyScreen1.UIRoundedRectButton)
-	```
-
-See Also
---------
-
-* [Compile Project]({% slug ms-compile-project%})
-* [Code Item]({% slug ms-code-item%})
-* [Code Behind File]({% slug ms-code-behind%})
-* [Android API]({% slug ms-android-api%})
-* [iOS API]({% slug ms-ios-api%})
-* [Hybrid API]({% slug ms-hybrid-api%})
-* [Web API]({% slug ms-web-api%})
diff --git a/docs/test-studio-mobile/features/code-features/compile-project.md b/docs/test-studio-mobile/features/code-features/compile-project.md
deleted file mode 100644
index a3dafe8b..00000000
--- a/docs/test-studio-mobile/features/code-features/compile-project.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Compile Project
-page_title: Compile Project
-description: Compile Project
-publish: true
-position: 4
-slug: ms-compile-project
-previous_url: /test-studio-mobile/getting-started-mb/code-features/compile-project
----
-#Compile Project
-
-You can compile the entire test project by pressing the **Compile** button in the ribbon of Test Studio Mobile.
-
-![Compile button](/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig1.png)
-
-By compiling the test project you can identify compile-time errors, such as incorrect syntax, misspelled keywords, type mismatches, and incorrect method binding. 
-
-When you compile the test project Test Studio Mobile builds the project dll in the **bin** folder of the project.
-
-The output of the compilation process is displayed in the [Output Pane]({% slug ms-output-pane%}) under **Compiler**. 
-
-![Output Pane](/img/test-studio-mobile/getting-started-mb/coded-features/compile-project/fig2.png)
-
-
-See Also
---------
-
-* [Coded Steps]({% slug ms-coded-steps%})
-* [Code Item]({% slug ms-code-item%})
-* [Code Behind File]({% slug ms-code-behind%})
-* [Output Pane]({% slug ms-output-pane%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/dom-explorer.md b/docs/test-studio-mobile/features/dom-explorer.md
deleted file mode 100644
index bfada9dc..00000000
--- a/docs/test-studio-mobile/features/dom-explorer.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: DOM Explorer
-page_title: DOM Explorer
-description: DOM Explorer
-publish: true
-position: 4
-slug: ms-dom-explorer
-previous_url: /test-studio-mobile/getting-started-mb/dom-explorer,/test-studio-mobile/getting-started-mb
----
-#DOM Explorer
-
- > The DOM explorer is populated only when a test is in record mode.
-
-The DOM Explorer allows you to inspect all elements of the tested application at once, shown in a tree-like or in a grouped-by-tag view. The DOM Explorer is helpful with a complex applications where simply taping may not be enough to find the element you're looking for. It is used also for building steps through the [Step Builder]({% slug ms-step-builder%})
-
-In order to access it click **DOM Explorer** tab in the middle bottom pane.
-
-![DOM Explorer](/img/test-studio-mobile/getting-started-mb/dom-explorer/fig1.png)
-
-##DOM Explorer Toolbar
-
-The DOM Explorer Toolbar provides some additional features that may come handy.
-
-![Toolbar](/img/test-studio-mobile/getting-started-mb/dom-explorer/fig2.png)
-
-*	**Highlight the element** - toggle this button whether to highlight the element in the tested application or not. When it is enabled the selected element from the DOM tree will be surrounded by a red rectangle on the recording device. This feature works only for Native apps.
-
-*	**Search for element** - to search an element in the DOM. The found element will be selected automatically.
-
-*	**Elements Tree View** - displays elements in their original tree-like hierarchy order.
-
-*	**Elements Tag View** - displays elements grouped by their tagname.
-
-*	**View Selector** - displayed only when Hybrid test is in record mode. Use it to select the Native/Web view which DOM tree you need loaded.
-
-
-## See also
-
-* [Record an Android test]({% slug ms-record-test-android%})
-* [Record an iOS test]({% slug ms-record-test-ios%})
-* [Record a Web test]({% slug ms-record-test-web%})
-* [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-* [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/elements-explorer.md b/docs/test-studio-mobile/features/elements-explorer.md
deleted file mode 100644
index a6581721..00000000
--- a/docs/test-studio-mobile/features/elements-explorer.md
+++ /dev/null
@@ -1,51 +0,0 @@
----
-title: Elements Explorer
-page_title: Elements Explorer
-description: Elements explorer functionality
-slug: ms-elements-explorer
-tags: elements, explorer, mobile
-publish: true
-position: 3
-previous_url: /test-studio-mobile/getting-started-mb/elements-explorer
----
-#Elements Explorer
-
-This section is dedicated to the Elements Explorer view and functionality.
-
-The Elements Explorer pane shows a tree-like view of your elements in the project. Elements are grouped first by test and then by a test view in the test forming hierarchical representation. Elements are added to the tree when test steps are recorded based on the views the user interacts with. 
-
-![Mobile Studio Elements Explorer](/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-explorer.png)
-
-Right click an element or a view to show context menu options:
-
-* **Renaming** an element or a view to give it a descriptive name for better recognition in the tree.
-
-* **Edit** an element. Using this option the element find logic can be changed in the query builder dialog. At the time elements are added to the repository, they are assigned a query that is used to identify the same element when the test is played back. Change that query if the element identification is not recorded as expected or wrong element is identified. The query builder dialog initially shows the current query properties. Those properties are editable and can be deleted or new properties can be added to extend the query.
-
-* Click **Used By** to see the list of steps of the current test where the selected element is used by. Double clicking a step from the list opens the test and highlights the step.
-
-![Mobile Studio Query Builder](/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-query-builder.png)
-
-In the top left corner of the elements explorer pane, two buttons are located:
-
-* **Refresh** elements button. In addition to refreshing the elements tree, this button will also collapse all expanded tests and views in the Elements explorer pane.
-
-* Toggle highlighting button. When enabled this option automatically navigates the Elements explorer pane to the element used by the selected step. For example if the fourth step in the test uses element named `First slider`, then clicking on that step will automatically expand the elements tree to the `First slider` element and highlight it.
-
-![Mobile Studio Toggle Highlight](/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-toggle-highlight.png)
-
-The Top right corner of the Elements explorer pane is reserved for visibility controlling buttons. The pane can be docked, pinned or closed. In addition it can be moved by drag-drop of its header or resized by drag-drop of its borders.
-
-![Mobile Studio Elements Drag](/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-elements-drag.png)
-
-If the Elements explorer pane is accidently closed or in case a layout reset is needed, the View menu can be used
-
-![Mobile Studio View Menu](/img/test-studio-mobile/getting-started-mb/elements-explorer/mobile-studio-view-menu.png)
-
-See Also
---------
-
-* [Getting Started Native Apps]({% slug ms-getting-started-native%})
-* [Getting Started Web Apps]({% slug ms-getting-started-web%})
-* [Test Explorer]({% slug ms-test-explorer%})
-* [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/message-server.md b/docs/test-studio-mobile/features/message-server.md
deleted file mode 100644
index 7fd27385..00000000
--- a/docs/test-studio-mobile/features/message-server.md
+++ /dev/null
@@ -1,89 +0,0 @@
----
-title: Message Server
-page_title: Message Server
-description: Message Server
-slug: ms-message-server
-tags: message server
-publish: true
-position: 8
-previous_url: /test-studio-mobile/getting-started-mb/message-server
----
-
-#Message Server
-
-Test Studio Mobile allows the user to write tests on a desktop machine and then execute them on a mobile device. The communication between the desktop runner and the device's agent is based on exchanged JSON messages. A piece of sofware called **Message Server** is responsible for handling these messages. 
-
-## Default Execution
-
-The Message Server is a node.js application that starts automatically behind the scenes when Test Studio **mobile** project is opened in the Test Studio GUI. It runs on the same machine where Test Studio is run and can be accessed on the machine's host/IP address and port [selected by the user]({% slug ms-project-settings%}) - **the default is 8084**. Because message server is responsible for the entire communication between test runner and agents, Test Studio also connects to it right after a mobile project is opened. 
-
-In the Test Studio GUI, the message server current status can be verified at the bottom left corner. If, for some reason, Test Stuido can't connect to the message server, a red dot indicattor is presented. Click **Edit Settings** to show the Message Server Settings dialog where its host and port can be edited:
-
-![message server disconnected](/img/test-studio-mobile/getting-started-mb/message-server/fig1.png)
-
-Enter valid and available host and port values and click the **Restart** button to restart and connection to the message server. 
-
-![message server connected](/img/test-studio-mobile/getting-started-mb/message-server/fig2.png)
-
- > Message server settings can also be edited from the [project settings dialog]({% slug ms-project-settings%})
-
-Once Test Studio is connected to a running instance of the message server, you can connect your native ([USB]({% slug ms-connect-agent-usb%}) and [Wi-Fi]({% slug ms-connect-agent-wifi%})) or [web]({% slug ms-configure-tsm%}) agents.
-
-## Standalone Execution
-
-The Message Server can be started even if Test Studio GUI doesn't run at all. The stand-alone version is include in the Mobile Runtime package and can be run on Windows, Mac and Linux machines:
-
-1. [Download]({% slug ms-download%}#4-Mobile-Runtime) the Mobile Runtime package for the intended platform and unpack it.
-2. Open a command window and navigate to the unpacked folder location. Navigate to the `MessageServer` folder.
-3. For Windows execute the `msgsrv-ctl.bat` file. For Mac/Linux execute the `msgsrv-ctl.sh` file. This will show you the available options for message server CLI. 
-
-	Windows
-
-	![message server menu](/img/test-studio-mobile/getting-started-mb/message-server/menu_windows.png)
-
-	Mac
-
-	![message server menu](/img/test-studio-mobile/getting-started-mb/message-server/menu_mac.png)
-
-	Linux
-
-	![message server menu](/img/test-studio-mobile/getting-started-mb/message-server/menu_linux.png)
-
-4. Calling the `start` command will launch a stand-alone message server on the default port 8084.
-
-	Windows
-
-	![message server start default](/img/test-studio-mobile/getting-started-mb/message-server/start_windows_default.png)
-
-	Mac
-
-	![message server start default](/img/test-studio-mobile/getting-started-mb/message-server/start_mac_default.png)
-
-	Linux
-
-	![message server start default](/img/test-studio-mobile/getting-started-mb/message-server/start_Linux_default.png)
-
-5. The stand-alone Message Server CLI allows usage of any available port in the range bewteen 1025 and 65535. Just specify it as an option to the `start` command:
-
-	Windows
-
-	![message server start custom](/img/test-studio-mobile/getting-started-mb/message-server/start_windows_custom.png)
-
-	Mac
-
-	![message server start custom](/img/test-studio-mobile/getting-started-mb/message-server/start_Mac_custom.png)
-
-	Linux
-
-	![message server start custom](/img/test-studio-mobile/getting-started-mb/message-server/start_Linux_custom.png)
-
-
-Once the message server is started, you can start connecting native Android and iOS agents to it using [Wi-Fi]({% slug ms-connect-agent-wifi%}) or [USB]({% slug ms-connect-agent-usb%}) connections.
-
- > The stand-alone version of the Message Server doesn't stop automatically. You will need to call the `stop` command of the Message Server CLI after you finish your work with it. To check the current status of the server, call the CLI's `status` command.
-
-See Also
---------
-
-+ [System Requirements]({% slug ms-requirements%})
-+ [Downloads]({% slug ms-download%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/mobile-testing-runner-cli.md b/docs/test-studio-mobile/features/mobile-testing-runner-cli.md
deleted file mode 100644
index d90f3df1..00000000
--- a/docs/test-studio-mobile/features/mobile-testing-runner-cli.md
+++ /dev/null
@@ -1,133 +0,0 @@
----
-title: Mobile Testing Test Runner CLI
-page_title: Mobile Testing Test Runner CLI
-description: Mobile Testing Test Runner CLI
-slug: ms-test-runner
-tags: test, explorer, mobile
-publish: true
-position: 9
-previous_url: /test-studio-mobile/getting-started-mb/mobile-testing-runner-cli,/test-studio-mobile/knowledge-base/continuous-integration/cli
----
-#Mobile Testing Test Runner CLI
-
-The Mobile Testing Test Runner Command Line Interface provides granular control over executing your tests. It runs on Windows, Linux and Mac machines and can be used for test execution only.
-* On Windows 7+ machines, Mobile Testing Runner CLI installs as part of Test Studio Mobile and its default location is in *%TestStudioInstallationFodler%\Bin\MobileStudio*. It can also be downloaded and run separately as part of the [Mobile Runtime]({% slug ms-download%}#4-Mobile-Runtime).
-* On Mac and Linux machines, Mobile Testing Runner CLI can be downloaded and run separately as part of the [Mobile Runtime]({% slug ms-download%}#4-Mobile-Runtime). ([Mono][1] is required to be installed on the machine).
-
-Mobile testing runner CLI is an executable file that uses the following format:
-
-Windows:
-
-**Telerik.MobileTesting.Runner.exe** [/msgServer=message_server] [/project=project_root]
-\[(/test=test.mttest) | (/list=list.mtlist)] (/deviceId=device_id) (/runName=run_name)
-(/output=output.mtresult)
-
-Mac/Linux:
-
-**mono Telerik.MobileTesting.Runner.exe** [/msgServer=message_server] [/project=project_root]
-\[(/test=test.mttest) | (/list=list.mtlist)] (/deviceId=device_id) (/runName=run_name)
-(/output=output.mtresult)
-
-Where:
-* Square brackets mean the command-line argument is mandatory. 
-* Parenthesis mean the argument is optional. 
-* The “|” means “OR” meaning /test OR /list can be used. 
-
-The tool accepts the following the command-line arguments:
-
-* `/msgServer=message_server`
-
-	The address of a running [message server]({% slug ms-message-server%}) to which the test device(s) are connected to. 
-
-	> A message server is running every time you open a Test Studio Mobile project and its host and port can be found in the [project settings dialog]({% slug ms-project-settings%}). A [stand-alone version]({% slug ms-message-server%}#Standalone-Execution) of the message server can also be run without using the Test Studio GUI.
-
-* `/project=project_root`
-
-	Project_root is the full path to the root folder of a project which tests or lists will be executed.
-
-	> The test project root is the folder that contains the `settings.mt` file.
-
-* `/listDevices=fullInfo or /listDevices=onlyId`
-
-	List all connected devices' info - full info or only id.
-
-
-* `/test=test.mttest`
-
-	Full or relative path to the test.mtest that the runner will execute, the relative path is relative to the project root provided in the /project argument. 
-
-	> The `/test` argument cannot be used in the same command with `/list` argument.
-
-* `/list=list.mtlist`
-
-	Full or relative path to the list.mtlist that the runner will execute, the relative path is relative to the TestLists folder of the project root (provided in the /project argument) . Test list is a collection of single tests that resides in the \TestLists folder of a mobile testing project. 
-
-	> The `/list` argument cannot be used in the same command with `/test` argument. By default if the `/output` argument is not set, a result file containing the test list execution results is created in the `\Results` folder of the test project.
-
-* `/deviceId=device_id`
-
-	This is an optional argument which will make the runner execute the test or list only on devices specified by their device_id.  
-
-	By default a test or list will automatically execute on the first valid device connected to the message server. The device id of a connected device can be found in the **Connected Devices** pane in the Test Studio Mobile or by using the `getagents` command of the `tmtest` tool. This tool is located in the `MessageServer` folder and can be used as follows:
-
-	1. Open a command window and navigate to the `MessageServer` folder. If you have TestStudio installed, this folder is located in *%TestStudioInstallationFodler%\Bin\MobileStudio*. If you use the [Mobile Runtime]({% slug ms-download%}#4-Mobile-Runtime), the folder is located in the root of the runtime folder.
-
-	2. Type **node tmtest getagents -h** or **node tmtest getagents --help** to see options.
-
-	3. Type **node tmtest getagents** to see a list of agents connected to the default message server URL at ws://localhost:8081 or specify `--message-server-url` argument if your message server runs on port different than 8081.
-
-	**iOS**
-
-	![ios](/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig1.png)
-
-	**Windows**
-
-	![Windows](/img/test-studio-mobile/getting-started-mb/mobile-testing-runner-cli/fig2.png)
-
-* `/runName=run_name`
-
-	Set a custom test run name for the result.
-
-* `/output=output.mtresult`
-
-	Provide a full path to a specific output location.
-
-* `/resultType=result_type`
-
-	Results format:<br>
-	0 - Mobile Studio Json results file (default)<br>
-	1 - JUnit XML (test to JUnit test)<br>
-	2 - JUnit XML (test step to JUnit test)<br>
-
-	> The default result is in JSON format saved in a file having `.mtresult` extension. It can be loaded in [Test Studio Mobile results view]({% slug ms-testlist-execution%}#results) if the result is saved in the `{pathToYourProject}\Results` folder of a test project. 
-	>If the `/output` argument is not set, the result is saved in the `{pathToYourProject}\Results folder` despite of its type.
-	
-
-**Examples:**
-
-Below are several examples of running Telerik.MobileTesting.Runner.exe via the command line.
-
-> The sample command lines below may split into two or more lines. This is a visual effect that depends on the width of the help viewer’s window. When specifying a command line for mobile testing runner, type all command-line arguments into the same line.
-
-The following command will connect to a running message server and execute a single test on the first valid device connected to the message server.
-
-	"C:\Program Files (x86)\Progress\Test Studio\Bin\MobileStudio\Telerik.MobileTesting.Runner.exe" /msgServer=ws://localhost:8084 /project="c:\testproject\MobileDemoProject" /test=androidTest.tmtest
-
-The following command will run a test list against a specific device (its device id provided as argument) and output the result at a specified location.
-
-	"C:\Program Files (x86)\Progress\Test Studio\Bin\MobileStudio\Telerik.MobileTesting.Runner.exe" /msgServer=ws://localhost:8084 /project="c:\testproject\MobileDemoProject" /deviceId= 6968cda2-83e6-4e39-9fcf-30b614656229 /list=AllAndroidTests.mtlist /output="c:\mobileTestingResults\androidRun.mtresult"
-
-The following command will run a test list on the first valid device connected to the message server, create a result file from the run and put a custom test run name in the result file.
-
-	"C:\Program Files (x86)\Progress\Test Studio\Bin\MobileStudio\Telerik.MobileTesting.Runner.exe" /msgServer=ws://localhost:8084 /project="c:\testproject\MobileDemoProject" /list=AllAndroidTests.mtlist  /runName=AndroidListIteration1   /ouput="c:\mobileTestingResults\androidSingleTestRun.mtresult"
-
-
- 
-
-[1]: http://www.mono-project.com/download/
-
-See Also
---------
-
-* [Downloads]({% slug ms-download%})
-* [System Requirements]({% slug ms-requirements%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/output-pane.md b/docs/test-studio-mobile/features/output-pane.md
deleted file mode 100644
index a50fd988..00000000
--- a/docs/test-studio-mobile/features/output-pane.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Output Pane
-page_title: Output Pane
-description: Output Pane functionality
-slug: ms-output-pane
-tags: test, explorer, mobile
-publish: true
-position: 6
-previous_url: /test-studio-mobile/getting-started-mb/output-pane
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-
-# Output Pane in Test Studio Mobile
-
-The **Output** window displays a record of log messages recorded by Test Studio Mobile throughout runtime. These include build errors that occur when a project is compiled.
-
-You can find it in the Output tab on the middle bottom pane by default. If it is hidden you can display it from **View -> Output**.
-
-![OutPut Pane](/img/test-studio-mobile/getting-started-mb/output-pane/fig1.png)
-
-You can chose between **General** and **Compiler** option to filter the type of information in the pane.
-
-![OutPut Pane option](/img/test-studio-mobile/getting-started-mb/output-pane/fig2.png)
-
-The **General** option displays a record of log messages recorded by Test Studio Mobile throughout runtime. These errors are designed to indicate important events and help pinpoint where problems may occur.
-
-![OutPut Pane](/img/test-studio-mobile/getting-started-mb/output-pane/fig4.png)
-
-The **Compiler** option (only if you have [code-behind file]({% slug ms-code-behind%}), [code item]({% slug ms-code-item%}), or [coded steps]({% slug ms-coded-steps%})) displays information about a specific error message during the compilation of the project.
-
-*	Display the errors, warnings, and messages produced while you write code.
-
-*	Find syntax errors noted by IntelliSense.
-
-
-![Compiler](/img/test-studio-mobile/getting-started-mb/output-pane/fig3.png)
-
-
-Click the Clear button ![Clear](/img/test-studio-mobile/getting-started-mb/output-pane/fig5.png) in order to clear the output results.
-
-
-See Also
---------
-
-+ [Compile Project]({% slug ms-compile-project%})
-+ [Code Item]({% slug ms-code-item%})
-+ [Code-Behind File]({% slug ms-code-behind%})
-+ [Coded Steps]({% slug ms-coded-steps%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/project-explorer.md b/docs/test-studio-mobile/features/project-explorer.md
deleted file mode 100644
index 55f29593..00000000
--- a/docs/test-studio-mobile/features/project-explorer.md
+++ /dev/null
@@ -1,68 +0,0 @@
----
-title: Project Explorer
-page_title: Project Explorer
-description: Project explorer functioanlity
-slug: ms-project-explorer
-tags: project, explorer, mobile
-publish: true
-position: 1
-previous_url: /test-studio-mobile/getting-started-mb/project-explorer
----
-
-#Project Explorer
-
-This section is dedicated to the Project Exlorer UI and functionality.
-
-The Project Explorer pane shows a tree-like structure of your tests in the project. Tests can be added directly to the project, or logically grouped in folders. Folders in turn, can be nested forming hierarchical representation of your testing solution. Tests and folders can be added either through the dedicated buttons located right above the project icon, or by a context menu shown on right click of a test, folder or project:
-
-<table id="no-table">
-	<tr>
-		<td>![Mobile Studio Context Menu](/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-context-menu.png)</td>
-		<td>![Context Menu](/img/test-studio-mobile/getting-started-mb/project-explorer/fig6.png)</td>
-	</tr>
-<table>
-
-
-The context menu options (based on the target) also feature:
-
-* Rename a project, folder, test or test list.
-* Delete, Cut, Copy and Paste operations of a folder or test.
-* Open a project, folder, test or test list in Windows explorer.
-* Open a test or test list in Test Explorer.
-* Open References in [Project Settings]({% slug ms-project-settings%}) where you can see a list of existing project references, add a new reference, or delete an existing one. 
-* Add [Code Item]({% slug ms-code-item%})
-* Add [Code-Behind File]({% slug ms-code-behind%})
-
-Tests and folders support drag-drop to change the logical structure of the project:
-
-![Mobile Studio Drag Drop](/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-drag-drop.png)
- 
-Project explorer also features keyboard support that includes:
-
-* Selection navigation amongst tests and folders with the **arrow keys** (up and down).
-* Expanding and collapsing parent folders with the **arrow keys** (left and right).
-* Cut (Ctrl+X), Copy (Ctrl+C) and Paste (Ctrl+V) of folders and tests.
-* Opening a selected test with **Enter** key.
-* Deleting a test or folder with the **Delete** key.
-* Renaming project, folder or test with **F2** key.
-* Multi item selection using the Ctrl or Shift keys.
-
-Searching through tests is supported by a search field at the top right corner of the pane. The search text is dynamic and once typing starts, items will be filtered with every key stroke.
-
-![Mobile Studio Search Field](/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-search-field.png)
-
-The Top right corner of the Project explorer pane is reserved for visibility controlling buttons. The pane can be docked, pinned or closed. In addition it can be moved by drag-drop of its header or resized by drag-drop of its borders.
-
-![Mobile Studio Project Drag](/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-project-drag.png)
-
-If the Project explorer pane is accidently closed or in case a layout reset is needed, the View menu can be used
-
-![Mobile Studio View Menu](/img/test-studio-mobile/getting-started-mb/project-explorer/mobile-studio-view-menu.png)
-
-See Also
---------
-
-* [Getting Started Native Apps]({% slug ms-getting-started-native%})
-* [Getting Started Web Apps]({% slug ms-getting-started-web%})
-* [Test Explorer]({% slug ms-test-explorer%})
-* [Elements Explorer]({% slug ms-elements-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/project-settings.md b/docs/test-studio-mobile/features/project-settings.md
deleted file mode 100644
index f270b91e..00000000
--- a/docs/test-studio-mobile/features/project-settings.md
+++ /dev/null
@@ -1,46 +0,0 @@
----
-title: Project Settings
-page_title: Project Settings
-description: Project Settings
-publish: true
-position: 7
-slug: ms-project-settings
-previous_url: /test-studio-mobile/getting-started-mb/project-settings
----
-#Project Settings
-
-In the Test Studio Mobile ribbon click the gear icon to display the settings dialog.
-
-Use this dialog to adjust the project settings.
-
-![Open settings dialog](/img/test-studio-mobile/getting-started-mb/settings/fig1.png)
-
-##General
-
-In this section you can adjust basic settings of the project.
-
-![General](/img/test-studio-mobile/getting-started-mb/settings/fig2.png)
-
-* **USB Connectivity**
-	* iOS USB Connect time out - adjust the time out for iOS USB connection.
-
-* **Message Server**
-	* Message server IP - the IP address that the local [message server]({% slug ms-message-server%}) will use for communication. Use "localhost" to auto-bind the first IP address in the DNS list (default).
-
-	* Message server port - The TCP/IP port that the local [message server]({% slug ms-message-server%}) will use for communication. 
-
-* **Web Proxy**
-	* Web proxy port - The TCP/IP port that the Web proxy will use for communication with your mobile device.
-
-##References
-
-Here you can see a list of existing project references, add a new reference, or delete an existing one. 
-
-![References](/img/test-studio-mobile/getting-started-mb/settings/fig3.png)
-
-
-See Also
---------
-
-+ [Message Server]({% slug ms-message-server%})
-+ [Output Pane]({% slug ms-output-pane%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/step-builder.md b/docs/test-studio-mobile/features/step-builder.md
deleted file mode 100644
index 5bd408a4..00000000
--- a/docs/test-studio-mobile/features/step-builder.md
+++ /dev/null
@@ -1,44 +0,0 @@
----
-title: Step Builder
-page_title:  Step Builder
-description: "Description of Step Builder"
-publish: true
-position: 5
-slug: ms-step-builder
-previous_url: /test-studio-mobile/test-recording/step-builder
----
-
-#Step Builder
-
-The Step Builder is a feature that allows you to add steps to your test manually. In order to access it click the **Step Builder** tab in the lower right corner. The Step Builder appears. 
-
-> You should select an element from the [DOM Explorer]({% slug ms-dom-explorer%}) in order to add a step for that element.
-
-> Some of the Step Builder steps are available only when a test is in record mode.
-
-![Select Element](/img/test-studio-mobile/test-recording/step-builder/fig6.png)
-
-If no element is selected from the DOM only the common step suggestions appear.
-
-![step builder](/img/test-studio-mobile/test-recording/step-builder/fig1.png)
-
-The Step Builder is a context aware feature and the steps that are only related to the selected element appear. The main categories are Actions, Verifications and Wait.
-
-<table id="no-table">
-	<tr>
-		<td>![Actions](/img/test-studio-mobile/test-recording/step-builder/fig2.png) <br><br>**Actions**</td>
-		<td>![Verifications](/img/test-studio-mobile/test-recording/step-builder/fig3.png) <br><br>**Verifications**</td>
-		<td>![Wait](/img/test-studio-mobile/test-recording/step-builder/fig4.png) <br><br> **Wait**</td>
-	</tr>
-<table>
-
-You can add a step by double clicking on the step or by clicking the **Add Step** button.
-
-![add step](/img/test-studio-mobile/test-recording/step-builder/fig5.png)
-
-
-See Also
---------
-
-+ [DOM Explorer]({% slug ms-dom-explorer%})
-+ [Project Explorer Pane]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/features/test-explorer.md b/docs/test-studio-mobile/features/test-explorer.md
deleted file mode 100644
index 93f2e365..00000000
--- a/docs/test-studio-mobile/features/test-explorer.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Test Explorer
-page_title: Test Explorer
-description: Test explorer functioanlity
-slug: ms-test-explorer
-tags: test, explorer, mobile
-publish: true
-position: 2
-previous_url: /test-studio-mobile/getting-started-mb/test-explorer
----
-#Test Explorer
-
-This section is dedicated to the Test Exlorer UI and functionality.
-
-The Test Explorer pane shows open tests and the steps of the currently selected open test. The explorer features the following:
-
-1. Active step column - a marker in this column shows the currently active test step. In recording mode this marker shows the position where the next recorded step will be added in the list. Only one step can be active step at a time.
-
-	![Mobile Studio Active Step](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-active-step.png)
-
-2. Enabled steps column - check box in front of each step indicates whether it is enabled. Disabled steps are not executed during playback no matter whether the step passes or fails. Multiple steps can be disabled at a time.
-
-	![Mobile Studio Active Step](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-enabled-steps.png)
-
-3. Continue on failure steps column - an icon in front of each step indicates whether test execution will continue even if the step fails. Normally, execution stops once a step fails. Multiple steps can be marked as `continue on failure` at a time.
-
-	![Mobile Studio Continue Failure](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-continue-failure.png)
-
-4. Expand/Collapse step column - based on the step type different parameters can be tweaked. Expand a step to see the options that can be changed. Only one step can be expanded at a time.
-
-	![Mobile Studio Expand Step](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-expand-step.png)
-
-5. Step description column - here the step index as well as a step display name is provided. The step display name is configurable through the properties pane.
-
-	![Mobile Studio Step Display Name](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-displayname.png)
-
-6. Step type column - indicates the step type - verification, action etc.
-
-	![Mobile Studio Step Type](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-type.png)
-
-7. Execution log and Error details - those buttons get active after a test is played back. The execution log provides details on a step by step basis. If a failure is detected, the log and the Error details are populated with descriptive error messages
-
-	![Mobile Studio Error](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-error.png)
-
-8. Context menu options showed upon right click on a step:
-
-	* Delete, Cut, Copy and Paste operations.
-	* Run test to specific step, run just selected steps or run from specific step. These options are available only when recording is currently active.
-
-	![Mobile Studio Step ContextMenu](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-test-contextmenu.png)
-
-9. Project explorer also features keyboard support that includes:
-
-	* Selection navigation between steps with the **arrow keys** (up and down).
-	* Deleting a step with the **Delete** key.
-	* Cut (Ctrl+X), Copy (Ctrl+C) and Paste (Ctrl+V) steps.
-	* Multi step selection using the Ctrl or Shift keys.
-
-10. Steps support drag-drop to change their order in the list:
-
-	![Mobile Studio Step Drag Drop](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-dragdrop.png)
-
-11. Steps can be filtered by step type or step display name - use the filter field and search field at the top right corner of the pane. The search text is dynamic and once typing starts, steps will be filtered with every key stroke.
-
-	![Mobile Studio Step Filtering](/img/test-studio-mobile/getting-started-mb/test-explorer/mobile-studio-step-filtering.png)
-
-
-See Also
---------
-
-* [Getting Started Native Apps]({% slug ms-getting-started-native%})
-* [Getting Started Web Apps]({% slug ms-getting-started-web%})
-* [Project Explorer]({% slug ms-project-explorer%})
-* [Elements Explorer]({% slug ms-elements-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/getting-started/native-applications.md b/docs/test-studio-mobile/getting-started/native-applications.md
deleted file mode 100644
index 7af067ed..00000000
--- a/docs/test-studio-mobile/getting-started/native-applications.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Native/Hybrid Applications
-page_title: Native/Hybrid Applications
-description: Getting Started article describing how to record and playback a mobile Test Studio test.
-slug: ms-getting-started-native
-tags: ios, testing, native, android, hybrid
-publish: true
-previous_url: /test-studio-mobile/overview-mb/native-applications,/test-studio-mobile/overview-mb
-position: 1
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-# Getting Started with Native/Hybrid iOS and Android Applications in Test Studio Mobile
-
-This section walks you through the process of recording your first Test Studio Mobile native Android/iOS test and execute it on a physical device. Before you start, please ensure the following:
-
-* You have access to a Windows machine where Test Studio Ultimate will be installed. The Test Studio Mobile solution currently works only on Windows machines and installs as part of the Test Studio product.
-* iOS or Android running physical device. Testable app will be installed on this device. Mobile tests will be executed against this app.
-* A Mac machine running Xcode is required to build and deploy the Demo App for iOS to a device.
-* A machine running Eclipse or Android Studio to build and deploy the Demo App for Android to a device.
-* Cordova CLI is required to be installed to build and deploy the Hybrid Demo App to a device.
-
-## Agent App Installation
-
-The Mobile Testing Agent app must be installed on a physical or virtual device that will execute tests against native/hybrid apps. The Agent app connects the testable app on the device with the machine where Test Studio Ultimate is installed.
-
-* [Agent App Installation]({% slug ms-install-agent-app%})
-
-## Connect Agent
-
-After installing the Mobile Testing Agent app you should connect it to the Test Studio Mobile either by USB or Wi-Fi:
-
-* [USB Connection]({% slug ms-connect-agent-usb%})
-
-* [Wi-Fi Connection]({% slug ms-connect-agent-wifi%})
-
-##Install a testable app to a device
-
-You can either configure your app to be testable or use one of the pre-configured native Demo apps.
-
-###Configure your app to be testable
-
-* [Configure Android Native App]({% slug ms-configure-android%})
-
-* [Configure iOS Native App]({% slug ms-configure-ios%})
-
-* [Configure NativeScript App]({% slug ms-configure-nativescript%})
-
-* [Configure Hybrid (AppBuilder) App]({% slug ms-configure-hybrid-appbuilder%})
-
-* [Configure Hybrid (Cordova) App]({% slug ms-configure-hybrid%})
-
-* [Configure Xamarin iOS App]({% slug ms-configure-xamarin-ios%})
-
- > Cordova, Xamarin and NativeScript apps eventually build native iOS/Android apps. As a result the configuration can be made either at the Xamarin/NativeScript level or at the final iOS/Android level.
-
-###Build a pre-configured Demo app.
-
-* [Run Demos]({% slug ms-run-demos%})
-
-##Record and Playback Test
-
-Once the above setup is complete you can start recording
-
-* [Android Native]({% slug ms-record-test-android%}), [iOS Native]({% slug ms-record-test-ios%}), [Android Hybrid]({% slug ms-record-test-android-hybrid%}) or [iOS Hybrid]({% slug ms-record-test-ios-hybrid%}) test.
-
-or 
-
-* [Playback your test]({% slug ms-quick-execution%})
-
-
-See Also
---------
-
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/getting-started/web-applications.md b/docs/test-studio-mobile/getting-started/web-applications.md
deleted file mode 100644
index e82de195..00000000
--- a/docs/test-studio-mobile/getting-started/web-applications.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Web Applications
-page_title: Web Applications
-description: Getting Started article describing how to record and playback a mobile Test Studio test.
-slug: ms-getting-started-web
-tags: ios, testing, started
-previous_url: /test-studio-mobile/overview-mb/web-applications
-publish: true
-position: 1
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-# Getting Started with Web Applications in Test Studio Mobile
-
-This section walks you through the process of recording your first Test Studio Mobile web test and execute it in a browser (Mobile or Desktop). Before you start, please ensure the following:
-
-* You have access to a Windows machine where Test Studio Ultimate will be installed. The Test Studio Mobile solution currently works only on Windows machines and installs as part of the Test Studio product.
-
-## Connect Agent(Browser)
-
-Connecting a web browser to Test Studio Mobile is a multi-step process that uses a built-in WebProxy. The proxy is responsible for injecting a Web Extension in every page that a web test navigates to.
-
-* [Web Connection]({% slug ms-configure-tsm%})
-
-##Record and Playback Test
-
-Once the above setup is complete you can start
-
-* [Recording your test]({% slug ms-record-test-web%})
-
-or
-
-* [Playback your test]({% slug ms-quick-execution%})
-
-
-See Also
---------
-
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/knowledge-base/android-system-dialog.md b/docs/test-studio-mobile/knowledge-base/android-system-dialog.md
deleted file mode 100644
index bbd10223..00000000
--- a/docs/test-studio-mobile/knowledge-base/android-system-dialog.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Android System Dialog
-page_title: Android System Dialog 
-description: "Handle Android System Dialog"
-publish: true
-position: 0
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-
-# How To Handle Android System Dialog
-
-## PROBLEM
-
-While automating an Android application a system Android dialog pops up. It is not available in the DOM tree and no actions against it are recorded in the test. How such a dialog could be handled? 
-
-## SOLUTION
-
-The system dialog generated by the OS is not part of the application under test and thus is not present in the DOM tree. This is why there are no actions recorded against it.
-
-Please find a coded approach how to handle such a dialog. The solution uses two bat files to execute the necessary commands through adb (<a href="https://developer.android.com/studio/command-line/adb.html" target="_blank">Android Debug Bridge</a>), a working directory (which is set to "C:\Work\" for this example but any other could be used after adjusting it in the code) and an xml file generated during the test run which contains all elements on the execution device screen. Once the file is copied to the working directory it is parsed and the required button on screen is located by its name. Its center could be located on screen using its coordinates and a tap is sent through adb.
-
-Create a bat file named getdump.cmd and add the following adb commands in it:
-
-```
-adb shell uiautomator dump /data/local/tmp/test.xml
-
-adb pull /data/local/tmp/test.xml
-```
-
-The first one will get all elements on screen and will save them into "test.xml" file which initially will be stored on the device. The second command pulls the generated xml on the desktop working direcotiry.
-
-Create a second bat file named dismiss.cmd and add the following adb command:
-
-```
-adb shell input tap %1 %2
-```
-
-This is the tap on screen on specific coordinates sent through adb.
-
-The sample project which uses the above two files and performs the parcing of the xml file, locates the required button on device screen and tap on it could be downloaded <a href="/samples/HandleAndroidSystemDialog.zip" target="_blank">here</a>.
-
->Note: The above solution is a sample which demonstrates the approach how to handle system Android dialogs and will require adjustment for the specific dialog you need to automate.
\ No newline at end of file
diff --git a/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-android.md b/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-android.md
deleted file mode 100644
index d3757b4c..00000000
--- a/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-android.md
+++ /dev/null
@@ -1,142 +0,0 @@
----
-title: Android
-page_title: Android CI
-description: "Setup CI build for Android apps using Mobile Testing Runner CLI"
-publish: true
-position: 0
-slug: ms-ci-android
-previous_url: /test-studio-mobile/knowledge-base-mb/continuous-integration-mb/ci-android,/test-studio-mobile/knowledge-base-mb/continuous-integration-mb
----
-
-#Setup CI build for Android apps using Mobile Testing Runner CLI
-
-This topic is dedicated to the steps that can be followed to create a Jenkins CI build based on the Mobile Testing Runner CLI. Requirements:
-
-*	[Jenkins Server](http://jenkins-ci.org/)
-*	Android SDK
-*	Download and unzip on your local machine [Mobile Runtime package]({% slug ms-download%}#4-Mobile-Runtime) for the OS you are running. This demo uses the Windows package.
-*	Download and install [Mono](http://www.mono-project.com/download/) (only if you want to run on Mac/Linux) 
-*	Powershell (optional - used in this demo)
-*	GitHub/TFS/Git Jenkins plugin
-*	Post-build Actions Jenkins plugin (recommended)
-
-##Setup Jenkins build:
-
-1.&nbsp; Download and install Jenkins on the Windows machine. Install the Jenkins plugins afterwards.
-
-2.&nbsp; Open the Jenkins Web UI and create a new Jenkins job.
-
-> As of release **R1 2018 (v2018.1.130)** you could install and use the <a href="/test-studio-mobile/knowledge-base/continuous-integration/jenkins-ci-plugin-mobile" target="_blank">Jenkins Mobile Studio Plugin</a>.
-
-3.&nbsp; In the **Source Code Management** section, connect to the repository where your tests reside. We will use a Github repository for this demo.
-
-  ![jenkins setup](/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig1.png)
-
-4.&nbsp; Setup the Windows batch command that will execute the tests. Here, a powershell script module function is used.
-
-  ![batch command](/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/android/fig2.png)
-
-The actual script code follows. For brevity, it implements 4 functions that are responsible for different tasks. Note the describing comments in the code.
-
-```
-$ErrorActionPreference = "Stop"
-	# Starts the Emulator.
-      function start-emulator {
-        # Start an android Emulator.
-        emulator -avd Emulator51
-
-        # Wait 2 minutes for the Emulator to load up. Adjust this time depending on the emulator version.
-        start-sleep -s 120
-
-        # Call the function that installs the app to test and connects the agent to the message server.
-        install-connect-apps
-      }
-
-      # Installs the app and connects the agent to the message server which must be started first.
-      function install-connect-apps {
-        # Install the app to test. Change the path to a local store (where you have build the project) or online repository.
-        adb -s emulator-5554 install -r "Android\Apps\DemoApplicationTesting.apk"
-        start-sleep -s 10
-
-        # Start the Mobile Testing agent app.
-        adb -s emulator-5554 shell monkey -p com.telerik.testing.executionagent -c android.intent.category.LAUNCHER 1
-        start-sleep -s 10
-
-        # Set the location to the Message Server folder (where you have downloaded and unziped it) and start the message server on port 8081.
-        Set-Location -Path (".\MobileRuntime-Windows\MessageServer")
-        start-process msgsrv-ctl.bat "stop"
-        start-sleep -s 5
-        start-process msgsrv-ctl.bat "start 8081"
-        start-sleep -s 5
-
-        # Connect the Mobile Testing agent to the message server.
-        adb -s emulator-5554 forward tcp:8082 tcp:8082
-        start-sleep -s 10
-        node.exe tmtest.js connect --message-server-url ws://localhost:8081 --address localhost:8082
-        start-sleep -s 10
-
-        # Call the function that runs the tests.
-        run-tests
-
-        # Stop the Message Server
-        start-process msgsrv-ctl.bat "stop"
-      }
-
-      # Runs the tests.
-      function run-tests{
-        # Set the location of the MobileRuntime folder (where you have downloaded and unziped it) and execute a run.
-        Set-Location -Path (".\MobileRuntime-Windows")
-
-        # Run the tests and output results to a json file.
-        .\Telerik.MobileTesting.Runner.exe /msgServer=ws://localhost:8081 /project=C:\[userName]\MyTestProjectName 
-		/list=C:\[userName]\MyTestProjectName\TestLists\ListName.mtlist 
-		/output=C:\OutputResultsFolder\Results.mtresult /resultType=1
-        start-sleep -s 10 
-
-        # If a test fails, stop the Emulator and exit the build with error code.
-        If($LASTEXITCODE -ne 0)
-        {
-          stop-emulator
-          exit 1
-        }
-        start-sleep -s 10
-        # Call the function that stops the emulator.
-        stop-emulator
-      }
-
-      # Stops the emulator.
-      function stop-emulator{
-        $processes = @(Get-Process emulator-arm -ErrorAction SilentlyContinue)
-        foreach ($process in $processes)
-        {
-          $process | Stop-Process -force
-        }
-      }
-
-      export-modulemember -function start-emulator
-
-```
-
-The **start-emulator** function just launches the Android emulator named *Emulator51*. The emulator must be created prior to running the script. [Android AVD](http://developer.android.com/tools/devices/managing-avds.html) can be used for this task.
-
-After the emulator is started, the next function in the chain is called. The **install-connect-apps** function does 3 tasks:
-
->Before **install-connect-apps** function is called the Mobile Testing Agent app must be [installed]({% slug ms-install-agent-app%}) and the testable аpp must be [configured for testing]({% slug ms-configure-android%}) and available for deployment as built .apk file.
-
-*	Installs the testable App on the launched emulator. This app must be instrumented with the Test Studio Mobile extension and built as described [here]({% slug ms-configure-android%}).
-
-*	Starts the Mobile Testing agent app on the emulator.
-
-*	Connects the Mobile Testing Аgent app to the message server. Since message server is started on port 8081, we use 8082 for the connection. Note that this is the default port for Mobile Testing Agent app USB connection and if you want to use another port, you will have to change it both in the script and in the Mobile Testing Agent app [USB settings]({% slug ms-connect-agent-usb%}).
-
-The **run-tests** function navigates to a location where test project is stored and then calls a command that executes its tests on the emulator against the testable app. If a test fails the emulator is closed and the build is marked as failed.
-
-The last function **stop-emulator** just closes the emulator no matter whether the build passes or fails.
-
-Jenkins also supports emailing build results and build artifacts. Setting up these post-build actions, ensures that the build status (pass or fail) and the actual test results are delivered to the responsible people.
-
-Add a post build action - to publish JUnit test results report. This will provide results to be visible from Jenkins UI.
-
-**See Also**
-
-*	[Continuous Integration iOS]({% slug ms-ci-ios%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-ios.md b/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-ios.md
deleted file mode 100644
index f5192419..00000000
--- a/docs/test-studio-mobile/knowledge-base/continuous-integration/ci-ios.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: iOS
-page_title: iOS CI
-description: "Setup CI build for iOS apps using Mobile Testing Runner CLI"
-publish: true
-position: 0
-slug: ms-ci-ios
-previous_url: /test-studio-mobile/knowledge-base-mb/continuous-integration-mb/ci-ios
----
-
-#Setup CI build for iOS apps using Mobile Testing Runner CLI
-
-This topic is dedicated to the steps that can be followed to create a Jenkins CI build based on the Mobile Testing Runner CLI. Requirements:
-
-* [Jenkins Server](http://jenkins-ci.org/)
-* Mac OS x 9+
-* Xcode 6+
-* iOS SDK
-* Download and unzip on your local machine [Mobile Runtime package]({% slug ms-download%}#4-Mobile-Runtime) for Mac.
-* Download and install [Mono](http://www.mono-project.com/download/)
-* GitHub/TFS/Git Jenkins plugin
-* Post-build Actions Jenkins plugin (recommended)
-
-##Setup Jenkins build:
-
-1.&nbsp; Download and install Jenkins on the Mac machine. Install the Jenkins plugins afterwards.
-
-2.&nbsp; Open the Jenkins Web UI and create a new Jenkins job.
-
-> As of release **R1 2018 (v2018.1.130)** you could install and use the <a href="/test-studio-mobile/knowledge-base/continuous-integration/jenkins-ci-plugin-mobile" target="_blank">Jenkins Mobile Studio Plugin</a>.
-
-3.&nbsp; In the **Source Code Management** section, connect to the repository where your tests reside. We will use a Github repository for this demo.
-
-  ![jenkins setup](/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig1.png)
-
-4.&nbsp; Add an Execute Shell build step.
-
-  ![build](/img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/ios/fig2.png)
-
-  In this step add a short script that will start a simulator, install apps in it and execute tests. Note the describing comments in the code.
-
-  > Before the script below is called the Mobile Testing Agent app must be [installed]({% slug ms-install-agent-app%}) and the testable аpp must be [configured for testing]({% slug ms-configure-ios%}) and available for deployment as built .app file.
-
-
-  ```
-    export PATH=$PATH:/usr/local/bin
-
-    # sudo `-H -u {ROOT_USER}` this command is used to ensure that every command is executed on the same user. Start the desired simulator by its ID. 
-    # You can find a list of available simulators and their IDs by executing `xcrun simctl list`.
-    # The `|| return 0` pipe is used in order to escape the common error `timeout waiting for  device to boot` which will always appear on slower machines.
-    sudo -H -u {ROOT_USER} open -a Simulator --args -CurrentDeviceUDID {DEVICE_ID} || return 0 
-  
-    # In order to ensure the simulator is ready, you can add the a sleep step depending on the machine speed.
-    sleep 60
-
-    # Install the app to test. Change the path to a local store (where you have build the project) or online repository.
-    sudo -H -u {ROOT_USER} xcrun simctl install booted $WORKSPACE/DemoApplicationTesting.app
-    sleep 1
-
-    # Launch the Mobile Testing agent on the device
-    sudo -H -u {ROOT_USER} xcrun simctl launch booted com.telerik.MobileTesting
-
-    # Set the location to the Message Server folder (where you have downloaded and unziped it) and start the message server on port 8081.
-    cd "/MobileRuntime-Mac/MessageServer/"
-    sudo -u {ROOT_USER} ./msgsrv-ctl.sh stop
-    sleep 10
-    sudo -u {ROOT_USER} ./msgsrv-ctl.sh start 8081
-    sleep 10
-
-    # Connect the Mobile Testing agent to the message server.
-    sudo -u {ROOT_USER} ./node tmtest.js connect --message-server-url "ws://127.0.0.1:8081" --address "localhost:8082"
-
-    # Navigate to the MobileRuntime folder (where you have downloaded and unziped it) and execute a run.
-    cd "/MobileRuntime-Mac/"
-    sudo -u {ROOT_USER} mono Telerik.MobileTesting.Runner.exe /msgServer="ws://127.0.0.1:8081" /project="/Users/MyTestProjectName" /list="/Users/MyTestProjectName/TestLists/MyListName.mtlist" /resultType=1
-
-    #Stop message server
-    cd /Users/testing/Desktop/jenkins/workspace/CI\ -\ iOSRunner\ -\ Develop/MessageServer
-    sudo -u testing ./msgsrv-ctl.sh stop
-  ```
-
-5.&nbsp; Add Post-Build action step. Those are steps which will be run after the test execution.
-
-In this step, make sure that the simulator will reset to its original state:
-
-```
-    # Shut down the desired simulator by its ID
-    sudo -H -u {ROOT_USER} xcrun simctl shutdown {DEVICE_ID}
-    sleep 10
-
-    # The next command is optional, it will reset the simulator and everything on it which means that next time in addition to the app under test, the Mobile Testing agent should be installed again.
-    sudo -H -u {ROOT_USER}  xcrun simctl erase {DEVICE_ID}
-    sleep 10
-
-    # Kill simulator process
-    sudo -u {ROOT_USER} killall "Simulator" {DEVICE_ID}
-
-```
-
-Jenkins also supports emailing build results and build artifacts. Setting up these post-build actions, ensures that the build status (pass or fail) and the actual test results are delivered to the responsible people.
-
-**See Also**
-
-* [Continuous Integration Android]({% slug ms-ci-android%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/knowledge-base/continuous-integration/jenkins-ci-plugin-mobile.md b/docs/test-studio-mobile/knowledge-base/continuous-integration/jenkins-ci-plugin-mobile.md
deleted file mode 100644
index 9ea1f87b..00000000
--- a/docs/test-studio-mobile/knowledge-base/continuous-integration/jenkins-ci-plugin-mobile.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Jenkins Plugin Mobile Runner
-page_title: Jenkins Plugin Mobile Runner
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 2
----
-# Mobile Test Studio Plugin for Jenkins CI #
-
-The Test Studio Plugin allows you to build and execute Mobile Test Studio tests and test lists in Jenkins CI environment and easily explore the generated JUnit xml results in the built-in Jenkins functionality.
-
-1.&nbsp; **Install the Mobile Studio Plugin** - download it <a href="/downloads/Jenkins_Plugin_Mobilestudio.zip" target="_blank">here</a> and add it to the Plugin folder of the Jenkins server installation.
-
-2.&nbsp; **Create a freestyle project**. Create an item and select 'Build a freestyle project'.
-
-![Freestyle project][2]
-
-3.&nbsp; **Add a Mobile Studio Runner configuration build step**. Under the 'Add build step menu' section select 'Mobile Studio runner configuration'.
-
-![TS Plugin build step][3]
-
-4.&nbsp; **Input the full path to Telerik.MobileTesting.Runner.exe**. The default path to find the Test Runner executable is C:\Program Files (x86)\Progress\Test Studio\Bin\MobileStudio.
-
-5.&nbsp; **Input Message Server address** - running <a href="/test-studio-mobile/features/message-server" target="_blank">message server</a> to which the devices are connected to.
-
-6.&nbsp; **Input device ID** to execute the tests on. 
-
-7.&nbsp; **Specify the test or test list to execute** using full or relative path to the file and the project root folder full path.
-
-![Build step arguments][4]
-
-8.&nbsp; **Choose whether to represent test or test steps as a JUnit test**. By enabling the checkbox a *test list* will be represented as a test suite and each including test will be represented as a JUnit test. 
-
-![Convert to JUnit][5]
-
-9.&nbsp; **Add post build action** - to publish JUnit test results report. This will provide results to be visible from Jenkins UI.
-
-![Publish in JUnit][6]
-
-Your test execution step is now ready to save and run.
-
-[1]: /img/advanced-topics/build-server/jenkins-ci-plugin/fig1.png
-[2]: /img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig2.png
-[3]: /img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig3.png
-[4]: /img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig4.png
-[5]: /img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig5.png
-[6]: /img/test-studio-mobile/knowledge-base-tm/continuous-integration-tm/jenkins-plugin/fig6.png
-
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-android.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-android.md
deleted file mode 100644
index f3d6256d..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-android.md
+++ /dev/null
@@ -1,262 +0,0 @@
----
-title: Android
-page_title: Configure Android App
-description: Apply our testing extension to your native Android application.
-slug: ms-configure-android
-tags: android testing, native
-publish: true
-previous_url: /test-studio-mobile/configure-your-app/configure-android
-position: 1
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-# Configure your Android app to be testable
-
-> The application configured following the steps below, should be used for testing purposes only and will not be accepted in Google Play Store. 
-
-Android apps must be configured in order to be testable by Test Studio Mobile. This can be achieved through the built-in configuration or manually:
-
-*   [Built-In Configuration](#built-in-configuration)
-*   [Manual Configuration](#manual-configuration)
-
-## Built-In Configuration
-
- > The built-in configuration requires that you have Java SDK v.1.8 or later, Android SDK v.14 or later Android Build Tools v.20 or later installed (Android Build Tools are a component of the Android Studio installation).</br>
-
- > It doesn't change already instrumented app and you have to ensure that the `libs` folder of your project doesn't contain `MobileTestingExtension.jar` or `MobileTestingExtension.aar` files. In addition built-in configuration is not supported for the below cases:
- > * Apps downloaded from Google play or built in production mode.
- > * The app to be instrumented has more than 65536 methods and is installed on device running API level 20 and below. See [that article]({% slug ms-known-issues%}#instumentation-exception) for more information.
-
- The automatic configuration is incorporated into Test Studio Mobile project and can be launched by clicking the Android gear box icon at the right corner of the toolbar:
-
-![AndroidGear](/img/test-studio-mobile/configure-your-app/configure-android/fig11.png)
-
-The Android application configuration dialog shows up. The first-time setup requires that paths to **Android SDK** and **Java JDK** foolders are set:
-
-![SDK_JAVA_errors](/img/test-studio-mobile/configure-your-app/configure-android/fig12.png)
-
- > For more informational about Android application configuration settings, please see [this article]({% slug ms-configure-android-settings%}).
-
-After valid paths are set, the **Next** button is enabled and the **Input location** step can be selected. It allows configuring an app either already installed on a device, or taken from the local machine file system. Configuring an app installed on a device, requires that the device is **USB connected** to the local machine running Test Studio Mobile:
-
-![InputLocation](/img/test-studio-mobile/configure-your-app/configure-android/fig13.png)
-
-Selecting a connected device automatically loads a subset of all apps installed on it. Apps that have identifiers starting with `com.android` and `com.google` are not shown initially. In order to show all available apps on the device, check the **Show All** checkbox. In addition instead of scrolling through the list, a search box allows you to look for a specific app identifier:
-
-![InputLocationApps](/img/test-studio-mobile/configure-your-app/configure-android/fig14.png)
-
- > Configuring system apps is not supported. If system app is selected the configuration will either fail or the app may become unstable. Test Studio is not responsible for any damage that a configured system app may cause.
-
-After app to be configured is selected, the Output location step is enabled and can be navigated by clicking the **Next** button:
-
-![OutputLocation](/img/test-studio-mobile/configure-your-app/configure-android/fig15.png)
-
-Output location can be either the local machine file system or any of the USB connected devices:
-
-![OuptuLocationSelection](/img/test-studio-mobile/configure-your-app/configure-android/fig16.png)
-
-Clicking the **Run** button will start the configuration process. After the app is successfully configured it will be deployed to the selected device or saved at the specified file location.
-
-![ProvisionedSuccessfully](/img/test-studio-mobile/configure-your-app/configure-android/fig17.png)
-
-Testing the configured app can start immediatelly by opening an Android test and selecting a device for recording. The app identifier is automatically added and can be chosen from the list of app identifiers that is shown when recording starts. [This article]({% slug ms-record-test-android%}) describes test recording in detail.
-
-## Manual Configuration
-
-> The manual configuration requires the source code (Android Studio/Eclipse project).
-
-Configure your Android app to be testable.
-
-* [Android Studio and AAR extension](#android-studio-and-aar-extension)
-* [Android Studio and JAR extension](#android-studio-and-jar-extension)
-* [Eclipse](#eclipse)
-
-# Android Studio and AAR extension.
-
-## Copy Extension
-
-1. [Download](/samples/MobileTestingExtension_Android.zip) the Test Studio Mobile extension for Android and unpack it.
-2. Open `/MobileTestingExtension_Android/`.
-3. Copy `MobileTestingExtension.aar`.
-4. In your project open `/projectFolder/mymodulename/libs`.
-5. Paste `MobileTestingExtension.aar`.
-
-## Configure Module gradle settings
-
-1. Open `/projectFolder/mymodulename/build.gradle`.
-2. Add the following `productFlavors` in the `android` object:
-
-        productFlavors {
-            myFlavor {
-                targetSdkVersion 0
-            }
-        }
-
-3. Add the following line to the `dependencies` section:
-
-        myFlavorCompile (name: 'MobileTestingExtension', ext: 'aar')
-        
-    ![Manual Aar Module](/img/test-studio-mobile/configure-your-app/configure-android/fig18.png)
-
-## Configure Project gradle settings
-
-1. Open `/projectFolder/build.gradle`.
-2. Add the following `flatDir` element in the `repositories` object:
-        
-        flatDir {
-            dirs 'libs'
-        }
-        
-    ![Manual Aar Project](/img/test-studio-mobile/configure-your-app/configure-android/fig19.png)
-
-3. Sync the project and select **View > Tool Windows > Build Variants**.
-4. Select the **myFlavorDebug** build variant and deploy it.
-
-    ![Build Flavour](/img/test-studio-mobile/configure-your-app/configure-android/fig20.png)
-
-
-<a href="#Configure-your-Android-app-to-be-testable">Back to Top</a>
-<br><br>
-
-# Android Studio and JAR extension.
-
-## Copy Extension
-
-1. [Download](/samples/MobileTestingExtension_Android.zip) the Test Studio Mobile extension for Android and unpack it.
-2. Open `/MobileTestingExtension_Android/`.
-3. Copy `MobileTestingExtension.jar`.
-4. In your project open `/projectFolder/mymodulename/libs`.
-5. Paste `MobileTestingExtension.jar`.
-
-## Add Flavors
-
-1. Open your project in Android Studio.
-2. Right Click on the project and select **Open Module Settings**.
-3. Click **app** under **Project Settings**.
-4. Click the **Flavors** tab.
-5. Click **+** to add two new entries: `production` and `mobileTesting`.
-
-    ![Product Flavors](/img/test-studio-mobile/configure-your-app/configure-android/fig1.png)
-
-6. Click **OK**.
-
-## Configure Testing Flavor
-
-1. Open `/projectFolder/mymodulename/build.gradle`.
-2. Add the following after `productFlavors` in the `android` object:
-
-        android.applicationVariants.all { variant ->
-        if (variant.flavorName == 'mobileTesting') {
-            variant.outputs[0].processResources.manifestFile = file("src/${variant.flavorName}/AndroidManifest.xml")
-            variant.outputs[0].processManifest.enabled=false
-            }
-        }
-
-![Build Variants](/img/test-studio-mobile/configure-your-app/configure-android/fig3.png)
-
-## Include Extension
-
-1. Open `/projectFolder/mymodulename/build.gradle`.
-2. Add the following lines to the `dependencies` section:
-
-        mobileTestingCompile files('libs/MobileTestingExtension.jar')
-        
-    ![Apply Testing Extension in Android Studio](/img/test-studio-mobile/configure-your-app/configure-android/fig4.png)
-
-## Create Subfolders
-
-Create the following subfolders in the project:
-
-* `/projectFolder/mymodulename/src/mobileTesting`
-
-## Copy Android Manifest
-
-1. Open `/projectFolder/mymodulename/src/main`.
-2. Copy `AndroidManifest.xml`.
-3. Open `/projectFolder/mymodulename/src/mobileTesting`.
-4. Paste `AndroidManifest.xml`.
-
-## Edit Android Manifest
-
-1. Open `/projectFolder/mymodulename/src/mobileTesting/AndroidManifest.xml`.
-2. Verify that the permisiion element **android.permission.SYSTEM_ALERT_WINDOW** is added to the manifest file. 
-3. Add the following top-level `instrumentation` element which will be used as App-Identifier in Test Studio Mobile (don't forget to change `your.app.package` with your actuall app package name):
-
-        <instrumentation
-            android:targetPackage="your.app.package"
-            android:name="com.telerik.testingextension.MobileTestingInstrumentation" />
-
-    ![Instrumentation](/img/test-studio-mobile/configure-your-app/configure-android/fig5.png)
-
-4. Add the following `activity` element as a child of the `application` element:
-
-        <activity
-            android:name="com.telerik.testingextension.EntryPoint"
-            android:theme="@android:style/Theme.NoDisplay">
-        <intent-filter>
-            <action android:name="com.telerik.testing.ACTION_AUTOMATE"/>
-            <category android:name="android.intent.category.DEFAULT"/>
-        </intent-filter>
-        </activity>
-
-    ![Activity](/img/test-studio-mobile/configure-your-app/configure-android/fig6.png)
-
-5. Select **View > Tool Windows > Build Variants**.
-6. Select the **mobileTestingDebug** build variant and deploy it.
-
-    ![Testing Build Variant](/img/test-studio-mobile/configure-your-app/configure-android/fig7.png)
-
-<a href="#Configure-your-Android-app-to-be-testable">Back to Top</a>
-<br><br>
-
-# Eclipse
-## Copy Extension
-
-1. Open `/Telerik Mobile Testing/extensions/Android`.
-2. Copy `MobileTestingExtension.jar`.
-3. Open `/projectFolder/libs`.
-4. Paste `MobileTestingExtension.jar`.
-
-![Add Extension](/img/test-studio-mobile/configure-your-app/configure-android/fig8.png)
-## Edit Android Manifest
-
-1. Open `/projectFolder/AndroidManifest.xml`.
-2. Verify that the permisiion element **android.permission.SYSTEM_ALERT_WINDOW** is added to the manifest file. 
-3. Add the following top-level `instrumentation` element which will be used as App-Identifier in Test Studio Mobile:
-
-        <instrumentation
-            android:targetPackage="your.app.package"
-            android:name="com.telerik.testingextension.MobileTestingInstrumentation" />
-
-    ![Instrumentation Eclipse](/img/test-studio-mobile/configure-your-app/configure-android/fig9.png)
-
-4. Add the following `activity` element as a child of the `application` element:
-
-        <activity
-            android:name="com.telerik.testingextension.EntryPoint"
-            android:theme="@android:style/Theme.NoDisplay">
-        <intent-filter>
-            <action android:name="com.telerik.testing.ACTION_AUTOMATE"/>
-            <category android:name="android.intent.category.DEFAULT"/>
-        </intent-filter>
-        </activity>
-
-    ![Activity Eclipse](/img/test-studio-mobile/configure-your-app/configure-android/fig10.png)
-
-5. Build the project and deploy it.
-
-<a href="#Configure-your-Android-app-to-be-testable">Back to Top</a>
-<br><br>
-
-See Also
---------
-
-+ [Record Android Test]({% slug ms-record-test-android%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-appbuilder.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-appbuilder.md
deleted file mode 100644
index 304907e8..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-appbuilder.md
+++ /dev/null
@@ -1,86 +0,0 @@
----
-title: Hybrid (AppBuilder)
-page_title: Hybrid (AppBuilder) app Testing
-description: Apply our testing extension to your AppBuilder application.
-slug: ms-configure-hybrid-appbuilder
-tags: appbuilder testing, hybrid
-publish: true
-position: 4
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-#Configure your AppBuilder app to be testable.
-
-> Setting up your app for testing with Telerik Mobile Testing plugin requires that you disable the Analytics plugin which is enabled by default in some of the AppBuilder app templates.
-
-Follow the step-by-step instructions below to create a new sample AppBuilder hybrid app, add the Telerik Mobile Testing plugin to it, and execute sample tests against it.
-
-* [Create AppBuilder hybrid sample app](#CreateApp)
-* [Build and deploy the app](#PhysicalDevices)
-
-## Create AppBuilder sample hybrid app <a id="CreateApp" name="CreateApp"></a>
-
-1. To create an AppBuilder sample hybrid app, an [account in the Telerik Platform][1] is needed. Once logged in, create a new app by clicking on the **Create App** button.
-
-  ![Create App](/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateApp.png)
-
-2. Select **Advanced** tile. For the purpose of this tutorial we will use the Airlines demo application from the **Samples and templates** option. Let's name the app `MySampleApp` and click the **CreateApp** button.
-
-  ![Create App Name](/img/test-studio-mobile/configure-your-app/configure-appbuilder/CreateAppName.png)
-
-3. The next step is to enable the Telerik Mobile Testing plugin and set the app's configuration variable to match the app identifier. To do this, double-click **Properties** in the solution explorer and then go to **Plugins**. Scroll to the bottom and enable the Telerik Mobile Testing plugin. If Telerik Mobile Testing is not in the list, add it from the plugin marketplace by clicking on the **Install from Plugins Marketplace** button. Finally expand the plugin and click on the **Configuration variables** button. Enter the iOS app identifier that you will use in your iOS hybrid tests. 
-
-  ![Set Ios Identifier](/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetIosIdentifier.png)
-
-  <a name="appid"></a>
- > In your iOS hybrid tests the app identifier for an iOS app must match the IOS_APP_URL entered in the **Configuration variables** dialog, and suffixed with **://** . For example **airlinessampleapp://**.
-
- > The **Configuration variables** window sets only the iOS variable. The Android variable is set by default in the `General` settings and can be changed from there (see below).
-
- <!--- > When automation against `WKWebView` views is targeted, additional set of plugins is required. Click on **Install from Plugins Marketplace** button, and search for **Mobile Testing Extension - WebKit** and **WKWebView Polyfill** plugins. 
-
- > When automation against `Crosswalk WebView` views is targeted, additional set of plugins is required. Click on **Install from Plugins Marketplace** button, and search for **Mobile Testing Extension - XWalkView** and **Crosswalk WebView Engine** plugins. --->
-
-4. Go to **General** settings and verify the Application Identifier matches the Android app identifier that you will use in your tests.
-
-  ![Set Android Identifier.png](/img/test-studio-mobile/configure-your-app/configure-appbuilder/SetAndroidIdentifier.png)
-
-## Build and deploy the app.<a id="PhysicalDevices" name="PhysicalDevices"></a>
-
-1. To build the app click **Run**, then **Build** and choose the Android or iOS app package. For iOS builds you need to have your private identity and provisioning profile correctly setup.
-
-  Android
-
-  ![Build Android](/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildAndroid.png)
-
-  iOS
-
-  ![Build iOS](/img/test-studio-mobile/configure-your-app/configure-appbuilder/BuildIos.png)
-
-2. After a successful build, the app can be downloaded (iOS & Android) or QR scanned (Android) and installed.
-
-  Android
-
-  ![Download Android](/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadAndroid.png)
-
-  iOS
-
-  ![Download Ios](/img/test-studio-mobile/configure-your-app/configure-appbuilder/DownloadIos.png)
-
-3. Now that you have the app configured for testing, the next step is to [create]({% slug ms-create-test%}) and then record an [Android]({% slug ms-record-test-android-hybrid%}) or [iOS]({% slug ms-record-test-ios-hybrid%}) hybrid test.
-
-## See Also
-
-* [Agent App instalation]({% slug ms-install-agent-app%})
-* [Connect Agent App WiFi]({% slug ms-connect-agent-wifi%})
-* [Connect Agent App USB]({% slug ms-connect-agent-usb%})
-* [Create Test]({% slug ms-create-test%})
-* [Record Android Hybrid test]({% slug ms-record-test-android-hybrid%})
-* [Record iOS hybrid test]({% slug ms-record-test-ios-hybrid%})
-
-
-[1]:http://docs.telerik.com/platform/help/accounts/accounts
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-hybrid.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-hybrid.md
deleted file mode 100644
index 0f019db4..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-hybrid.md
+++ /dev/null
@@ -1,74 +0,0 @@
----
-title: Hybrid (Cordova)
-page_title: Hybrid (Cordova) app Testing
-description: Apply testing extension to a Hybrid (Cordova) application.
-slug: ms-configure-hybrid
-tags: cordova testing, hybrid
-publish: true
-position: 5
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-#Configure your Hybrid app (Cordova) to be testable
-
-  > The application configured following the steps below, should be used for testing purposes only and will not be accepted in Apple App Store and Google Play Store. 
-
-Since building Hybrid mobile applications produce native iOS and Android apps, they can be easily tested with Test Studio Mobile. [This getting-started article]({% slug ms-getting-started-native%}) provides more details about testing native iOS and Android apps.
-
-
-## Create a hybrid Cordova app
-
-Follow the standard flow for creating hybrid Cordova app described [here][1].
-
-## Add Extension
-
-1. [Download](/samples/MobileTestingExtension_Hybrid.zip) the Test Studio Mobile extension for Hybrid apps and unpack it.
-2. After a hybrid app is created navigate to app's containing folder and add the extension:
-
-		cordova plugin add "Path to `com.telerik.mobiletesting` folder"
-
-	![Mobile Testing Extension](/img/test-studio-mobile/configure-your-app/configure-hybrid/mobile-testing-extension.png)
-
- > Type `cordova plugin` to list all added plugins and verify the `Mobile Testing Extension` plugin is added.
-
-## App Identifier
-
-To successfully test a Condova hybrid app, Test Studio Mobile needs to know the app identifier. It is set like this:
-
-* Android - the App Identifier for Android is set during app creation in the Cordova CLI (see **Create a hybrid Cordova app** above) and looks something like **com.mycompany.myapp**.
-* iOS - the App Identifier for iOS comes from the Test Studio Mobile extension for iOS (see **Add Extension** above). By default this extension sets **telerikmt1** to be the App Identifier for iOS. To change it in the extension before it is added to the app, navigate to the folder of the downloaded extension (`com.telerik.mobiletesting`) and open the **plugin.xml** file in your preferred text editor. Locate the App Identifier as shown below and cahnge it:
-
-![Mobile Testing AppId iOS](/img/test-studio-mobile/configure-your-app/configure-hybrid/pluginxml-ios.png)
-
- > If you deploy the app to an **iOS 9** device then you must use one of the names listed below:
-* telerikmt1
-* telerikmt2
-* telerikmt3
-* telerikmt4
-* telerikmt5
-* telerikmt6
-* telerikmt7
-* telerikmt8
-* telerikmt9
-* telerikmt10
-* tsdemoapplication
-
-## Build and deploy the app
-
-To complete the app, follow the [Cordova Command-line Interface][1] guide to add required platforms and deploy to devices or emulators.
-
-See Also
---------
-
-+ [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-+ [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
-
-[1]: https://cordova.apache.org/docs/en/latest/guide/cli/index.html
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-ios.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-ios.md
deleted file mode 100644
index 6729aea2..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-ios.md
+++ /dev/null
@@ -1,160 +0,0 @@
----
-title: iOS
-page_title: Configure iOS App
-description: Apply our testing extension to the QA target of your native iOS application.
-slug: ms-configure-ios
-tags: ios testing, native
-publish: true
-previous_url: /test-studio-mobile/configure-your-app/configure-ios
-position: 2
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-#Configure your iOS app to be testable
-
-> The application configured following the steps below, should be used for testing purposes only and will not be accepted in Apple App Store. 
-
-## Duplicate Target
-
-1. Open your project in Xcode. This guide uses the open source application Wikipedia as an example.
-2. Select the project file in Xcode in order to view the list of Targets.
-
-    ![List of Targets](/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile.png)
-
-3. Right click the target for testing and click **Duplicate**.
-
-    ![Creating the Duplicate Target](/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-copy.png)
-
-4. Rename the new target to `ApplicationNameQA`.
-
-  > This signifies that the target is a QA-only build, and should not be used as a release.
-
-5.  Since Xcode does not do it automatically, update the new target’s associated files, settings, and schemes to reflect the new target name.
-
-  > Update the build settings to properly reference any property list files you rename.
-
-  ![The Renamed Target](/img/test-studio-mobile/getting-started-mb/configure-ios/wikipedia-mobile-qa.png)
-    
-  This table contains the items to update when a target is duplicated:
-
-   <table>
-    <tbody>
-      <tr>
-        <td><strong>Target</strong></td>
-        <td>ApplicationName copy &gt; ApplicationNameQA</td>
-      </tr>
-      <tr>
-        <td><strong>Target .plist file</strong></td>
-        <td>ApplicationName copy-Info.plist &gt; ApplicationNameQA.plist</td>
-      </tr>
-      <tr>
-        <td><strong>Target &gt; Build Settings &gt; Packaging &gt; Info.plist File</strong></td>
-        <td>ApplicationName copy-Info.plist &gt; ApplicationNameQA.plist</td>
-      </tr>
-      <tr>
-        <td><strong>Target &gt; Build Settings &gt; Packaging &gt; Product Name</strong></td>
-        <td>ApplicationName copy &gt; ApplicationNameQA</td>
-      </tr>
-      <tr>
-        <td><strong>Scheme &gt; Manage Schemes</strong></td>
-        <td>ApplicationName copy &gt; ApplicationNameQA</td>
-      </tr>
-    </tbody>
-  </table>
-
-  > If you're using the Wikipedia app as an example and intend to deploy it to your device, modify the following setting to build it with your own credentials: **Target &gt; Summary &gt; iOS Application Target &gt; Bundle Identifier**.
-
-  ![The Modified Bundle Indentifier](/img/test-studio-mobile/getting-started-mb/configure-ios/bundle-identifier.png)
-
-## Add Extension
-
-1. Select the new target in the **Scheme** drop-down.
-2. [Download](/samples/MobileTestingExtension_iOS.zip) the Test Studio Mobile extension for iOS and unpack it.
-3. Open `/MobileTestingExtension_iOS/` and drag **libMobileTestingExtension.a** into your Project's file listing.
-
-    ![Dragging the Static Library](/img/test-studio-mobile/getting-started-mb/configure-ios/drag-static-lib-new.png)
-	
-	>If you target to automate [WKWebView's](https://developer.apple.com/library/ios/documentation/WebKit/Reference/WKWebView_Ref/)  in your project, drag **libMobileTestingWebKit.a** into your Project's file listing as well.
-
-4. Select **Create folder references for any added folders**.
-5. Uncheck the original target and check the new QA target.
-6. Click **Finish**.
-
-    ![Linking the Static Libraries](/img/test-studio-mobile/getting-started-mb/configure-ios/adding-plugin-options.png)
-
-7. Go to **Build Phases &gt; Link Binary With Libraries**. A reference to the testing extension is automatically added. Add **libicucore.tbd**, **Security.framework**,  **QuartzCore.framework** and **CFNetwork.framework** if they are not already linked. In older versions of Xcode you may need to add **libicucore.dylib** instead of **libicucore.tbd**. This grants WebSocket compatibiltiy.
-    
-    > If you target to automate WKWebView's in your project, **WebKit.framework** must also be added.
-
-    ![The Successfully Linked Static Library](/img/test-studio-mobile/getting-started-mb/configure-ios/linked-lib-new.png)
-
-8. Go to **Build Settings &gt; Linking** and add `-add_load` to **Other Linker Flags**.
-
-    ![Other Linker Flags](/img/test-studio-mobile/getting-started-mb/configure-ios/other-linker-flags-2.png)
-
-    > This ensures all symbols from the static libraries compile correctly into the target application.
-
-## Add URL Type
-
-1. Go to the **Info** tab of the `QA` target's settings and click **+** to add a new URL Type.
-
-  *  **Identifier:** com.telerik.automation
-  *  **URL Schemes:** APPLICATIONNAME
-  *  **Role:** Editor
-
-  ![Adding the URL Type](/img/test-studio-mobile/getting-started-mb/configure-ios/adding-the-url-type-3.png)
-
-  > The **URL Schemes** should not contain any spaces. The APPLICATIONNAME portion need not match your duplicate Target name exactly, however we recommend consistency. The only requirement is that APPLICATIONNAME is unique so it does not conflict with another testable application.
-
-  > If you deploy the app to an **iOS 9+** device  then you must use one of the names listed below:
-  *	telerikmt1
-  *	telerikmt2
-  *	telerikmt3
-  *	telerikmt4
-  *	telerikmt5
-  *	telerikmt6
-  *	telerikmt7
-  *	telerikmt8
-  *	telerikmt9
-  *	telerikmt10
-  *	tsdemoapplication
-
-2. Select the newly configured target and click **Run**.
-
-  > After the `Build Succeeded` message, you may have to wait up to 10 seconds for the application to deploy. The device's screen will be black in the meantime.
-
-  > You may need to close your application (and the {{site.mt}} app) on the device before deploying.
-
-
-## Application ID
-
-The Application Identifier is setup during the instrumentation process of the testable app. The Application Identifier is combination of URL Schemes suffixed with **://**.
-
-> When used in Test Studio Mobile, the `Application Identifier` must be suffixed with **://**. For example, the app identifier that is setup in previous section is **WikipediamobileQA** (no trailing colon and slashes), but suffixed with **://** when entered in the Test Studio Mobile **Set Application ID** dialog.
-
-![APPID](/img/test-studio-mobile/getting-started-mb/configure-ios/appID.png)
-
-##iOS 9 Confirmation Dialogs
-
-iOS 9 introduces a feature that requires user confirmation when Mobile Testing Agent app starts an app under test. As a result a confirmation dialog is shown the first time tests are run and after the first test is executed. Once Open is chosen for both dialogs they won't be presented any more. However the first execution may still fail because of the interruption caused by the dialogs.
-
-<table id="no-table">
-	<tr>
-		<td>![Conformation dialog 1](/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog1.png)</td>
-		<td>![Conformation dialog 2](/img/test-studio-mobile/getting-started-mb/configure-ios/confdialog2.png)</td>
-	</tr>
-<table>
-
-
-See Also
---------
-
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-nativescript.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-nativescript.md
deleted file mode 100644
index dcb17770..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-nativescript.md
+++ /dev/null
@@ -1,106 +0,0 @@
----
-title: NativeScript
-page_title: Configure NativeScript App
-description: Apply our testing extension to your NativeScript application.
-slug: ms-configure-nativescript
-tags: NativeScript, native, script
-publish: true
-previous_url: /test-studio-mobile/configure-your-app/configure-nativescript
-position: 3
----
-
-#Configure your NativeScript app to be testable.
-
-> The application configured following the steps below, should be used for testing purposes only and will not be accepted in Apple App Store and Google Play Store. 
-
-Since building NativeScript mobile applications produce native iOS and Android apps, they can be easily tested with Test Studio Mobile. [This getting-started article]({% slug ms-getting-started-native%}) provides more details about testing native iOS and Android apps.
-
-1. The first step is to prepare the NativeScript application.
-
- > If you don't have NativeScript installed you can follow [this intallation guide](https://docs.nativescript.org/start/quick-setup)
-
-	If you don't have a NativeScript application to configure, you can create a new one by executing the following command:
-
-		tns create myApplicationName
-
-
-	Android
-
-	![Create Android](/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-Android.png)
-
-	iOS
-
-	![Create iOS](/img/test-studio-mobile/configure-your-app/configure-nativescript/CreateProject-iOS.png)
-
-2. Next you need change the current folder to the newly created app folder and add the Test Studio Mobile plugin for NativeScript with the following command:
-
-		tns plugin add nativescript-teststudio
-
-
-	Android
-
-	![AddPlugin Android](/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-Android.png)
-
-	iOS
-
-	![AddPlugin iOS](/img/test-studio-mobile/configure-your-app/configure-nativescript/AddPlugin-iOS.png)
-
-	During execution of the command the specific app id is set that Test Studio Mobile will use to start the app:
-
-	* For the Android version of the application, the **"id"** key that is set when the project is created is used. This key can be found in application's *package.json* file. :
-
-			...
-		 	"nativescript": {
-	    		"id": "org.nativescript.justTest",
-		    	...
-		    	}, 
-			...
-
-	* For the iOS version of the application, **"telerikmt1"** is set by default and used as URL Scheme required to access the tested application. For more information please read the note for URL Schemes in this [article]({% slug ms-configure-ios%}#Add-URL-Type)
-
-	If you want to add the plugin and set the iOS parameter value with a single command, you can use the extended version of *tns* command as follows:
-
-		tns plugin add nativescript-teststudio --var.IOS_APP_URL iosAppUrl
-
-	Here you need to replace *iosAppUrl* with the value you want your app to use.
-
-	> The Android parameter can't be changed with the CLI command. However both Android and iOS parameters can be changed manually in the *package.json* file.
-	
-	To confirm that you've correctly changed the app iOS url, you can check the *package.json* of the NativeScript application. The new value is added to the *"nativescript-teststudio-variables"* key. You can change this value in order to access the application from Test Studio with different url.
-
-		"nativescript-teststudio-variables": {
-		      "IOS_APP_URL": "telerikmt1"
-	    	}
-
-3. The next step is to prepare, build and deploy the application to a device or an emulator (you may need to have the device/emulator started):
-	
-	Android
-
-		tns run android
-
-	![RunProject Android](/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-Android.png)
-
-	iOS
-
-		tns run ios
-
-	![RunProject iOS](/img/test-studio-mobile/configure-your-app/configure-nativescript/RunProject-iOS.png)
-
-
-4. Now you can begin to test the UI with Test Studio as described in this [article]({% slug ms-create-test%}).
-
-
-> If you don't want to use the NativeScript plugin as described above, you can setup the generated native project manually. Open the project for each platform (from *platforms/ios* or *platforms/android*) and follow the steps required for configuring native [iOS]({% slug ms-configure-ios%}) and [Android]({% slug ms-configure-android%}#Manual) applications. 
-
-> You can configure native Android applications automatically right from within the Mobile Test Studio. Read more [here]({% slug ms-configure-android%}#Built-In-Configuration).
-
-
-See Also
---------
-
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Record Android Test]({% slug ms-record-test-android%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-android.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-android.md
deleted file mode 100644
index c755ed99..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-android.md
+++ /dev/null
@@ -1,111 +0,0 @@
----
-title: Xamarin Android
-page_title: Xamarin Android Testing
-description: Apply our testing extension to your Xamarin application.
-slug: ms-configure-xamarin-android
-tags: testing, xamarin
-publish: true
-position: 6
----
-
-#Configure your Xamarin Android app to be testable
-
-## Prerequsites:
-
-* Visual Studio 2015 or 2017 with installed "Modile development with .NET" workload
-
-![New install][1]
-
-* Test Studio Mobile Android extension:
-    1. [Download](http://docs.telerik.com/teststudio/samples/MobileTestingExtension_Android.zip) the Test Studio Mobile extension for Android and unpack it
-    2. Extract MobileTestingExtension.jar somewhere on your PC
-
-## Building the Xamarin bindings library:
-
-1.&nbsp; Start new Visual Studio project and select Templates->Android->Bindings Library (Android)
-
-![New Binding Library][2]
-
-2.&nbsp; Add **MobileTestingExtension.jar** to project:
-
-```
-    Solution Explorer->Right click on 'Jars' folder->Add->Existing Item...    
-    Navigate to MobileTestingExtension.jar and add it to the project.
-```
-
-![Adding JAR to project][3]
-
-3.&nbsp; Edit **MobileTestingExtension.jar** properties:
-
-```
-    In Solution Explorer select MobileTestingExtension.jar and change 'Build Action' to 'EmbeddedJar'
-```
-
-![Configuring JAR][4]
-
-4.&nbsp; Open project Properties and set **Target Framework** to be same as **Target Framework** of the application that will be tested.
-
-![Properties][5]
-
-5.&nbsp; Ensure to set explicitly the **Android Codegen Target** in project Properties to *jar2xml*.
-
-![Codegen Target][6]
-
-
-6.&nbsp; Build Bindings library. You probably will get some warning messages in output console, but the library should be build sucefully and ouputed DLL will be located at:
-
-```
-Visual Studio Projects\ClassLibrary\ClassLibrary\bin\Debug\ClassLibrary.dll
-```
-
-For more information about building Xamarin bindings library see: [Creating Bindings Library](https://developer.xamarin.com/guides/android/advanced_topics/binding-a-java-library/binding-a-jar/#Creating_the_Bindings_Library)
-
-
-## Configuring Xamarin application:
-
-1.&nbsp; Add Bindings Library to the project under test:
-
-![References][7]
-
-2.&nbsp; Open **AndroidManifest.xml** for editing
-
-![AndroidManifest][8]
-
-3.&nbsp; Add the following top-level instrumentation element which will be used as App-Identifier in Test Studio Mobile and change target package name to match your application package:
-
-```
- <instrumentation
-        android:name="com.telerik.testingextension.MobileTestingInstrumentation"
-        android:targetPackage="Todo.Android"/>
-```
-
-![Instrumentation][9]
-
-4.&nbsp; Add the following activity element as a child of the application element:
-
-```
-<activity android:name="com.telerik.testingextension.EntryPoint"
-        android:theme="@android:style/Theme.NoDisplay" >
-    <intent-filter>
-    <action android:name="com.telerik.testing.ACTION_AUTOMATE"/>
-    <category android:name="android.intent.category.DEFAULT" />
-    </intent-filter>
-</activity>
-```
-
-![Activity][10]
-
-5.&nbsp; Your application is ready for testing.
-
-For more information about recording and executing tests with Test Studio Mobile see: [Test Studio Mobile Help](http://docs.telerik.com/teststudio/test-studio-mobile/overview)
-
-[1]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-install.png
-[2]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/new-bindings-library.png
-[3]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/add-jars.png
-[4]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/configure-jar.png
-[5]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/properties.png
-[6]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/codegen-target.png
-[7]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/references.png
-[8]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/AndroidManifest.png
-[9]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/instrumentation.png
-[10]: /img/test-studio-mobile/configure-your-app/configure-xamarin-android/activity.png
diff --git a/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-ios.md b/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-ios.md
deleted file mode 100644
index fd71fd87..00000000
--- a/docs/test-studio-mobile/native-applications/configure-your-app/configure-xamarin-ios.md
+++ /dev/null
@@ -1,78 +0,0 @@
----
-title: Xamarin iOS
-page_title: Xamarin iOS Testing
-description: Apply our testing extension to your Xamarin application.
-slug: ms-configure-xamarin-ios
-tags: testing, xamarin
-publish: true
-position: 6
----
-
-#Configure your Xamarin iOS app to be testable
-
-> The application configured following the steps below, should be used for testing purposes only and will not be accepted in Apple App Store. 
-
-Since building Xamarin iOS mobile applications produce native iOS apps, they can be easily tested with Test Studio Mobile. [This getting-started article]({% slug ms-getting-started-native%}) provides more details about testing native iOS apps.
-
-## Add Extension
-
-1. [Download](/samples/MobileTestingExtension_iOS.zip) the Test Studio Mobile extension for iOS and unpack it.
-2. To bring the extension into your project, select the project from the solution explorer and press **Command + Option + A** to open the `Add files` dialog. Add **libMobileTestingExtension.a** to the project. When prompted, tell Xamarin Studio to copy it into the project.
-
-    ![Add extension xamarin ios](/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig1.png)
-
-## Add URL Type
-
-1. Open the **Info.plist** file, navigate to the **Advanced** tab and add a new `URL Type`.
-    *  **Identifier:** com.telerik.automation
-    *  **URL Schemes:** APPLICATIONNAME
-    *  **Role:** Editor
-
-    ![Add URL](/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig2.png)
-
-    > The **URL Schemes** should not contain any spaces. The APPLICATIONNAME portion need not match your app name exactly. The only requirement is that APPLICATIONNAME is unique so it does not conflict with another testable application.<br/>
-    If you deploy the app to an **iOS 9 device** then you must use one of the names listed below:
-    * telerikmt1
-    * telerikmt2
-    * telerikmt3
-    * telerikmt4
-    * telerikmt5
-    * telerikmt6
-    * telerikmt7
-    * telerikmt8
-    * telerikmt9
-    * telerikmt10
-    * tsdemoapplication
-
-
-## Configure Xamarin.iOS to Link the Library
-
-1. Right-click the Xamarin iOS project and choose **Options**
-2. Expand **Build** and select **iOS Build**
-3. At the bottom of the dialog set the following to the **Additional mtouch arguments** text field:
-
-  `-gcc_flags "-L${ProjectDir} -force_load ${ProjectDir}/libMobileTestingExtension.a -lMobileTestingExtension -licucore -framework CFNetwork -framework Security -framework QuartzCore"`
-
-    ![Xamarin link](/img/test-studio-mobile/configure-your-app/configure-xamarin-ios/fig3.png)
-
-    > When targetting iOS7 you may need to add the **-all_load** flag to the **Additional mtouch arguments**:<br/><br/>
-    `-gcc_flags "-L${ProjectDir} -all_load -force_load ${ProjectDir}/libMobileTestingExtension.a -lMobileTestingExtension -licucore -framework CFNetwork -framework Security -framework QuartzCore"`
-
-
-    > More information about linking iOS libraries in Xamarin project is available [here](http://developer.xamarin.com/guides/ios/advanced_topics/native_interop/).
-
-4. Close the Project Options dialog and click **Run**.
-
-    > After the `Build Succeeded` message, you may have to wait up to 10 seconds for the application to deploy. The device's screen will be black in the meantime.
-
-    > You may need to close your application (and the Mobile Testing Agent app) on the device before deploying.
-
-
-See Also
---------
-
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Elements Explorer]({% slug ms-elements-explorer%})
-+ [Test Explorer]({% slug ms-test-explorer%})
-+ [Project Explorer]({% slug ms-project-explorer%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-usb.md b/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-usb.md
deleted file mode 100644
index a15acd47..00000000
--- a/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-usb.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: USB Connection
-page_title: USB Connection
-description: "USB Connection"
-publish: true
-previous_url: /test-studio-mobile/connect-agent-app/connect-agent-usb
-position: 0
-slug: ms-connect-agent-usb
----
-
-# USB Connection
-
-Once you have [installed]({% slug ms-install-agent-app%}) the Mobile Testing agent app, tap on it to launch it.
-
-1. Tap on the **USB** button.
-
-	![click USB](/img/test-studio-mobile/connect-agent-app/usb/fig1.png)
-
-2. Specify the port and click **Done**.
-
-	![specify port](/img/test-studio-mobile/connect-agent-app/usb/fig2.png)
-
-3. [Create]({% slug ms-create-test%}) a **Mobile** test project in Test Studio and go to Connected Devices pane. Click **Connect Device** button.
-
-	![connect device](/img/test-studio-mobile/connect-agent-app/usb/fig3.png)
-
-	> Note that when one or more devices are connected, the button in the center of the screen is not shown and only the button in the upper left corner can be used to connect additional devices.
-
-4. On the Connect a Device dialog that appears click on **Device** tab and then choose **USB Connection** option. The device should be recognized automatically. Simply verify the information, make sure the port which you selected in step 2 matches and click on the **+** icon to connect your device.
-
-	![connect device](/img/test-studio-mobile/connect-agent-app/usb/fig4.png)
-
-	> You can edit the port by double clicking on it.
-
-5. Once successfully connected the device appear under the Connected Devices pane and the mobile testing agent displays the status that the device is connected and **Disconnect** button appears:
-
-<table id="no-table">
-	<tr>
-	<td> ![device listed](/img/test-studio-mobile/connect-agent-app/usb/fig6.png) </td>
-	<td> ![agent status](/img/test-studio-mobile/connect-agent-app/usb/fig7.png) </td>
-	</tr>
-<table>
-
-
-> Please note in order to connect an iOS device you **MUST** have [iTunes](http://www.apple.com/itunes/) installed on the machine.
-
-
-> For Samsung Android devices please make sure you have the Samsung USB drivers installed properly. You can download the drivers from [here](http://developer.samsung.com/technical-doc/view.do?v=T000000117).
-
-
-> The Android devices should be in **development mode**.
-
-
-See Also
---------
-
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Record Android Test]({% slug ms-record-test-android%})
-+ [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-+ [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
-+ [Playback Tests]({% slug ms-quick-execution%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-wifi.md b/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-wifi.md
deleted file mode 100644
index f526f29a..00000000
--- a/docs/test-studio-mobile/native-applications/connect-agent-app/connect-agent-wifi.md
+++ /dev/null
@@ -1,63 +0,0 @@
----
-title: Wi-Fi Connection
-page_title: Wi-Fi Connection
-description: "Wi-Fi Connection"
-publish: true
-previous_url: /test-studio-mobile/connect-agent-app/connect-agent-wifi
-position: 0
-slug: ms-connect-agent-wifi
----
-
-# Wi-Fi Connection
-
-1. [Create]({% slug ms-create-test%}) a **Mobile** test project
-
-2. After the project is created and loaded, go to the **Connected Devices** pane and click the **Connect Device** button
-
-	![Connect a device](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig2.png)
-
-3. From the opened pop-up window select the **Device** tab and then choose the **WiFi Connection** option. Copy the **Host** address and **Port** number that should be entered in the Test Studio Mobile Agent app
-
-	![Configure host and port](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig3.png)
-
-4. Once you have [installed]({% slug ms-install-agent-app%}) the Mobile Testing Agent app, tap on it to launch it:
- 
- 	Android
-
- 	![Andorid mobile agent](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig4.png)
-
-	iOS
-
-	![iOS mobile agent](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig7.png)
-
-5. Tap the Wi-Fi button and enter the **Host** and **Port** your message server is running on (copied in step 3 above). The message server is started automatically upon Test Studio Ultimate installation and runs by default on port 8084:
-
-	Android
-
-	![Adjust port](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig5.png)
-
-	iOS
-
-	![Adjust port](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig8.png)
-
-6. Tap the **Connect** button, the agent connects to the server and its state changes to connected:
-
-	Android
-
-	![Connect](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig6.png)
-
-	iOS
-
-	![Connect](/img/test-studio-mobile/connect-agent-app/connect-agent-wifi/fig9.png)
-
-7. You can now start recording or executing your tests.
-
-
-See Also
---------
-
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
-+ [Record Android Test]({% slug ms-record-test-android%})
-+ [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-+ [Playback Tests]({% slug ms-quick-execution%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/installation/agent-app-installation.md b/docs/test-studio-mobile/native-applications/installation/agent-app-installation.md
deleted file mode 100644
index 5e53b6cc..00000000
--- a/docs/test-studio-mobile/native-applications/installation/agent-app-installation.md
+++ /dev/null
@@ -1,87 +0,0 @@
----
-title: Agent App Installation
-page_title: Agent App Installation
-description: How to install agent to an iOS simulator
-previous_url: /test-studio-mobile/installation/agent-app-installation
-position: 2
-slug: ms-install-agent-app
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-# Agent App Installation
-
-## Overview
-
-The Mobile Testing Agent app must be installed on physical or virtual devices that will execute tests against native or hybrid apps. This app connects the machine where Test Studio Mobile is installed and the actual testable app.
-
-## Install to a real device
-
-Mobile Testing Agent app can be installed for free from [AppStore](https://itunes.apple.com/us/app/mobile-testing/id787441509?ls=1&amp;mt=8) or [Google Play](https://play.google.com/store/apps/details?id=com.telerik.testing.executionagent). Search for `Mobile Testing` and install the app to any supported device aimed for testing.
-
-## Install to an Android emulator
-
-1. Create an Android emulator with the [AVD Manager](http://developer.android.com/tools/devices/managing-avds.html).
-
-2. [Download](/samples/MobileTestingExtension_Android.zip) the Test Studio Mobile extension for Andorid and unpack it. Find the `MobileTesting.apk` file.
-
-3. Open a new command window.
-
-4. Open the Android SDK subfolder: /sdk/platform-tools.
-
-* ### OS X
-
-	1. Type ./adb devices to see a list of connected devices.
-
-	2. Type ./adb -s DEVICE_ID install "\path\to\MobileTesting.apk"
-
-		where DEVICE_ID is the target device or emulator.
-
-		![Device ID](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig1.png)
-
-* ### Windows
-
-	1. Type adb devices to see a list of connected devices.
-
-	2. Type adb -s DEVICE_ID install "\path\to\MobileTesting.apk"
-
-		where DEVICE_ID is the target device or emulator.
-
-		![Device ID Windows](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig2.png)
-
-
-## Install on iOS simulator
-
-1. Open a new command window.
-
-2. [Download](/samples/MobileTestingAgentForSimulator.zip) the Test Studio Agent App package for iOS and unpack it. Find the `MobileTestingSimulator.app` folder.
-
-* ###Using Xcode 6
-
-	1. To get a list of all available simulators type: *xcrun simctl list*
-
-		![Install app agent](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig4.png)
-
-	2. Choose a device and boot it if it is not already.
-
-		![Boot simulator](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig5.png)
-
-* ###Using Xcode 7
-
-	1. Open the Spotlight search and type *Simulator* to find the Simulator app and start it.
-
-		![Open Spotlight](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig6.png)
-
-Once a simulator is booted, install the `MobileTesting.app` to it by the following terminal command.
-
-![Install agent](/img/test-studio-mobile/getting-started-mb/agent-app-installation/fig7.png)
-
-
-See Also
---------
-
-+ [Downloads]({%slug ms-download%})
-+ [Run Demos]({%slug ms-run-demos%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/installation/download.md b/docs/test-studio-mobile/native-applications/installation/download.md
deleted file mode 100644
index 05b3cc5b..00000000
--- a/docs/test-studio-mobile/native-applications/installation/download.md
+++ /dev/null
@@ -1,71 +0,0 @@
----
-title: Downloads
-page_title: Downloads
-description: Mobile Testing Downloads
-slug: ms-download
-tags: ios, android, wp, testing, download
-publish: true
-previous_url: /test-studio-mobile/installation/download
-position: 2
----
-
-# Pick your download
-
-## 1. Mobile Testing Agent App
-
-The Mobile Testing Agent app must be installed on physical or virtual devices that will execute tests against native or hybrid apps. This app connects Test Studio Mobile and the actual testable app. Read [this article]({% slug ms-install-agent-app%}) for more information.
-
-  * [Mobile Testing Agent app for iOS](https://itunes.apple.com/us/app/mobile-testing/id787441509?ls=1&amp;mt=8) - required to execute native tests on an iOS device (link to the AppStore).
-
-  * [Mobile Testing Agent app for iOS](/samples/MobileTestingAgentForSimulator.zip) - required to execute native tests on an iOS simualtor (direct download of the application package).
-
-  * [Mobile Testing Agent app for Android](https://play.google.com/store/apps/details?id=com.telerik.testing.executionagent) - required to execute native tests on an Android device.
-
-## 2. Extensions
-
-Native/Hybrid apps must be configured in order to be testable by Test Studio Mobile. Configuring requires adding a platform specific Test Studio Mobile extension to the app. Read the dedicated [Android]({% slug ms-configure-android%}), [iOS]({% slug ms-configure-ios%}) and [Hybrid (Cordova)]({% slug ms-configure-hybrid%}) articles for more information.
-
-* [Android extension](/samples/MobileTestingExtension_Android.zip)
-
-* [iOS extension](/samples/MobileTestingExtension_iOS.zip)
-
-* [Hybrid extension](/samples/MobileTestingExtension_Hybrid.zip)
-
-## 3. Demo Apps
-
-Demo apps are preconfigured native/hyrbid apps for testing with Test Studio Mobile. Read [this article]({% slug ms-run-demos%}) for more information.
-
-* [Android demo app](/samples/androidDemoApplication.zip)
-
-* [iOS demo app](/samples/xCodeDemoApplication.zip)
-
-* [Hybrid (Cordova) demo app](/samples/cordovaDemoApplication.zip)
-
-## 4. Mobile Runtime
-
-The Mobile Runtime package is dedicated to test execution only. It consists of stand-alone versions of the tools that are required for test execution - Message Server and Mobile Testing Runner CLI.
-
-### Message Server
-
-Read [this article]({% slug ms-message-server%}) for more information about what Message Server is and how it works. By default, this server installs as part of Test Studio Mobile installation and starts automatically behind the scenes when Test Studio mobile project is opened in the GUI. However, a stand-alone version of the Message Server can be started even if Test Studio Mobile GUI doesn't run at all. The stand-alone version is part of the Mobile Runtime package that is available for Windows, Mac and Linux.
-
-### Mobile Testing Runner CLI
-
-Read [this article]({% slug ms-test-runner%}) for more information about what Mobile Testing Runner CLI is and how it works. By default, this CLI runner installs as part of Test Studio Mobile installation and starts automatically behind the scenes when Test Studio mobile project is opened in the GUI. However, a stand-alone version of the Mobile Testing Runner CLI can be started even if Test Studio Mobile GUI doesn't run at all. The stand-alone version is part of the Mobile Runtime package that is available for Windows, Mac and Linux.  
-
-* [Mobile Runtime for Windows](/samples/MobileRuntime-Windows.zip)
-* [Mobile Runtime for Mac](/samples/MobileRuntime-MacOs.zip)
-* [Mobile Runtime for Linux](/samples/MobileRuntime-Linux.zip)
-
-## 5. Demo Test Project
-
-A sample Test Studio Mobile project containing tests running against the Demo Apps. Read [this article]({% slug ms-quick-execution%}) for more information about how to execute the tests.
-
-* [Demo project](/samples/DemoMobileProject.zip)
-
-
-See Also
---------
-
-+ [Agent App Installation]({% slug ms-install-agent-app%})
-+ [Run Demos]({% slug ms-run-demos%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/native-applications/run-demos.md b/docs/test-studio-mobile/native-applications/run-demos.md
deleted file mode 100644
index 55c6f4dc..00000000
--- a/docs/test-studio-mobile/native-applications/run-demos.md
+++ /dev/null
@@ -1,84 +0,0 @@
----
-title: Run Demos
-page_title: Run Demos
-description: How to build, deploy and run the demo applications
-previous_url: /test-studio-mobile/installation/run-demos,/test-studio-mobile/native-applications/installation/run-demos
-position: 3
-slug: ms-run-demos
----
-#Run Demo Applications
-
-* <a href="#Android-Demo-App">Android Demo App</a>
-* <a href="#iOS-Demo-App">iOS Demo App</a>
-* <a href="#Hybrid-Demo-App">Hybrid Demo App</a>
-
-##Android Demo App
-
-1. [Install]({% slug ms-install-agent-app%}) the Mobile Testing Agent app to a physical or virtual device.
-
-2. [Download](/samples/androidDemoApplication.zip) Android demo application and unzip it.
-
-3. Open **Android Studio**
-
-4. Select **Open an existing Android Studio Project**
-
-5. Open /DemoApplication and click **OK**
-
-	![Open demo application](/img/test-studio-mobile/install/run-demos/fig1.png)
-
-6. Select **View > Tool Windows > Build Variants**
-
-7. Select the **mobileTestingDebug** build variant
-
-	![Select testing debug](/img/test-studio-mobile/install/run-demos/fig2.png)
-
-8. Click **Run** to deploy the demo app to a device or an emulator.
-
-	![Run the demo app](/img/test-studio-mobile/install/run-demos/fig3.png)
-
-9. After the demo app is deployed, you can [record Android test]({% slug ms-record-test-android%}) and [execute it]({% slug ms-quick-execution%}). Alternatively download the [mobile demo tests project](/samples/DemoMobileProject.zip), open it in Test Studio Mobile and excute tests in `Android_Native_Tests` folder.
-
-##iOS Demo App
-
-1. [Install]({% slug ms-install-agent-app%}) the Mobile Testing Agent app to a physical or virtual device.
-
-2. [Download](/samples/xCodeDemoApplication.zip) iOS demo application and unzip it. 
-
-3. Open **Xcode**
-
-4. Select **File > Open**
-
-5. Open /DemoApplication/DemoApplication.xcodeproj and click **Open**.
-
-	![Open demo application](/img/test-studio-mobile/install/run-demos/fig4.png)
-
-6. Select the **DemoApplicationQA** target and select a device or simulator
-
-7. Click **Run**
-
-	![Run the demo app](/img/test-studio-mobile/install/run-demos/fig5.png)
-
-8. After the demo app is deployed, you can [record iOS test]({% slug ms-record-test-ios%}) and [execute it]({% slug ms-quick-execution%}). Alternatively download the [mobile demo tests project](/samples/DemoMobileProject.zip), open it in Test Studio Mobile and excute tests in `iOS_Native_Tests` folder.
-
-## Hybrid Demo App
-
-1. [Install]({% slug ms-install-agent-app%}) the Mobile Testing Agent app to a physical or virtual device.
-
-2. [Download](/samples/cordovaDemoApplication.zip) Hybrid (Cordova) demo application and unzip it. 
-
-3. Open a command window in the `DemoApplication` folder and follow the [Cordova Command-line Interface][1] guide to add required platforms and deploy to devices or emulators.
-
-4. After the demo app is deployed, you can record [Android Hybrid test]({% slug ms-record-test-android-hybrid%}) or [iOS Hybrid test]({% slug ms-record-test-ios-hybrid%}) and [execute it]({% slug ms-quick-execution%}). Alternatively download the [mobile demo tests project](/samples/DemoMobileProject.zip), open it in Test Studio Mobile and excute the Android Hybrid tests in the `Android_Hybrid_Tests` folder or the iOS Hybrid tests in the `iOS_Hybrid_Tests` folder.
-
-See Also
---------
-
-+ [Agent App Installation]({% slug ms-install-agent-app%})
-+ [Downloads]({% slug ms-download%})
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Record iOS Test]({% slug ms-record-test-ios%})
-+ [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
-+ [Record Android Test]({% slug ms-record-test-android%})
-+ [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-
-[1]: https://cordova.apache.org/docs/en/latest/guide/cli/index.html
\ No newline at end of file
diff --git a/docs/test-studio-mobile/overview.md b/docs/test-studio-mobile/overview.md
deleted file mode 100644
index c5ad9ca2..00000000
--- a/docs/test-studio-mobile/overview.md
+++ /dev/null
@@ -1,107 +0,0 @@
----
-title: Overview
-page_title: Test Studio Mobile Overview
-description: "Overview of Test Studio Mobile"
-previous_url: /mobile-testing/overview
-position: 0
-slug: ms-overview
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-# Overview
-
-Test Studio Mobile is an intuitive and easy to use test automation solution for Mobile application testing. Create tests once and test across multiple devices and OS.
-
-The point and click functionality allows users to capture quickly and replay complex mobile testing functionality.  There is no need to write a single line of code.  In addition, if you like to enrich the tests with a custom logic in code, you can make use of the .NET and our mobile testing frameworks in coded test steps or standalone code files. Test against any number of real devices as you wish or through an emulator by connecting through Wifi or USB.
-
-## Features - Test Studio Mobile desktop application.
-
-Test Studio Mobile is a desktop application that connects your tests with targetted apps installed on remote devices. It introduces tons of fancy features that makes testing mobile apps a real pleasure: 
-
-*	Team Collaboration: Intuitive UI with built-in IDE allow testers to craft automation and easily collaborate with SDETs and developers for long-term maintainability.
-
-*	[Project Explorer]({% slug ms-project-explorer%}) - visualizes your tests in tree-like project structure that allows for easier navigation and management. 
-
-*	[Test Explorer]({% slug ms-test-explorer%}) - shows open tests and the steps of the currently selected open test.
-
-*	[Elements Explorer]({% slug ms-elements-explorer%}) - shows a tree-like view of the elements in the project. Every recorded step targets a specific element and those are elements are summarized in this view.
-
-*	[DOM Explorer]({% slug ms-dom-explorer%}) - allows you to inspect all elements of the tested application at once, shown in a tree-like structure or in a grouped-by-tag view. Properties can be verified and steps can be added against any element in the DOM explorer.
-
-*	[Step Builder]({% slug ms-step-builder%}) - this feature allows you to add context-based steps to your test manually. Works in a tight relation with DOM explorer.
-
-*	[Output]({% slug ms-output-pane%}) - this pane displays a record of log messages recorded by Test Studio Mobile throughout runtime. 
-
-*	Connected devices - view a list of all currently connected devices that are ready for test recording/execution. 
-
-*	Results (Test Lists) - this pane displays test list results in a list-like format. 
-
-*	Properties - this context-based pane shows properties of the currently selected item - this can be the project, test, step, element, folder, code file, connected device or a test list.
-
-*	<a href="/features/testing-types/load-testing/configure-remote-device" target="_blank">Load testing with mobile device traffic:</a> Connect your device(s) to Test Studio’s built-in remote proxy to quickly capture scenarios for load testing.
-
-## Features - Supported testing scenarios.
-
-Test Studio Mobile covers a wide range of testing scenarios, including native, hybrid, web, NativeScript (Android and iOS) and Xamarin (iOS) apps testing. Tests can be recoreded or manually written and executed solely or inside test lists. 
-
-### Platforms support
-
-Nowadays mobile apps can be created using different platforms. Test Studio Mobile supports the most recognized and utilized of them including Android and iOS:
-
-*	Testing Native apps - both Android and iOS native apps are supported. Just configure your [Android App]({% slug ms-configure-android%}) or [iOS app]({% slug ms-configure-ios%}) to be testable and start recording your tests.
-
-*	Testing Hybrid apps - both Android and iOS hybrid apps are supported. Just configure your [Cordova]({% slug ms-configure-hybrid%}) or [AppBuilder (Telerik Platform)]({% slug ms-configure-hybrid-appbuilder%}) app to be testable and start recording your tests.
-
-*	Testing Web apps - the most used mobile browsers are supported - Safari for iOS and Chrome and Firefox for Android are supported. Test Studio uses a proxy to [configure your mobile web app]({% slug ms-configure-tsm%}) for testing.
-
-*	Testing NativeScript apps - making a NativeScript app testable is achieved by adding a separate plugin with a [single line of code]({% slug ms-configure-nativescript%}).
-
-*	Testing Xamarin apps (iOS only) - just [configure your Xamarin Studio app]({% slug ms-configure-xamarin-ios%}) to be testable and start recording your tests.
-
-### Connecting Agents (Devices)
-
-Test recording and execution is performed on connected devices. Test Studio Mobile supports both physical and virtual Android and iOS devices and provides the following options for connecting them:
-
-*	[Wi-Fi connection]({% slug ms-connect-agent-wifi%}) - connect your Android or iOS device to Test Studio Mobile over Wi-Fi. This connection type is tailored for Native or Hybrid app testing and requires installation of the Mobile Testing Agent app. 
-
-*	[USB connection]({% slug ms-connect-agent-usb%}) - connect your Android or iOS device to Test Studio Mobile over USB cable. This connection type is tailored for Native or Hybrid app testing and requires installation of the Mobile Testing Agent app. 
-
-*	[Web connection]({% slug ms-configure-tsm%}) - connect a browser in your Android or iOS device to Test Studio Mobile over Wi-Fi. This connection type is tailored only for Web app testing and requires redirecting web traffic through a Test Studio Mobile proxy.
-
-### Recording and Execution
-
-As a complete mobile app testing solution, Test Studio Mobile supports the following approaches for test recording and execution:
-
-*	Test Studio Mobile recorder - this built in feature allows you to create your tests without writing a single line of code and supports multiple gestures such as scroll, zoom, swipe, pinch etc. In record mode any action preformed over the tested app is automatically recorded as a step in the test. Those steps can be then refined if they are not recorded correctly and can be used with [Android native]({% slug ms-record-test-android%}), [Android hybrid]({% slug ms-record-test-android-hybrid%}), [iOS native]({% slug ms-record-test-ios%}), [iOS hybrid]({% slug ms-record-test-ios-hybrid%}) and [Web]({% slug ms-record-test-web%}) tests.
-
-*	Coded tests support - scenarios that go beyond the Test Studio Mobile Recorder capabilities can be automated with code. Coded support includes [coded steps]({% slug ms-coded-steps%}) inside any type of test and [code item]({% slug ms-code-item%}) files that are compiled separately from tests. Adding assembly references and code compilation in both C# and VB languages are supported. 
-
-*	[Quick execution]({% slug ms-quick-execution%}) - a single test execution that provides results for the test itself and for every step in the test. Can be run on a single connected device only.
-
-*	[Test List execution]({% slug ms-testlist-execution%}) - a single test list execution against one or more connected devices. Results are provided for the test list, every test in the test list and every step in every test.
-
-*	[Mobile Runtime]({% slug ms-download%}#4-Mobile-Runtime) - despite Test Studio Mobile can be installed on Windows machines only, already recorded tests can be executed on Windows, Mac and Linux machines. 
-
-## Next Steps
-
-+ [Getting started with Native and Hybrid apps testing]({% slug ms-getting-started-native%})
-+ [Getting started with Web testing]({% slug ms-getting-started-web%})
-
-## Resources
-
-<ul>
-	<li>
-		<a href="http://www.telerik.com/support/teststudio" target="_blank">Test Studio Learning and Support Resources</a>
-	</li>
-	<li>
-		<a href="http://www.telerik.com/webinars/teststudio" target="_blank">Test Studio Webinars</a>
-	</li>
-</ul>
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-execution-requirements.md b/docs/test-studio-mobile/test-execution-requirements.md
deleted file mode 100644
index 1d64be97..00000000
--- a/docs/test-studio-mobile/test-execution-requirements.md
+++ /dev/null
@@ -1,75 +0,0 @@
----
-title: System Requirements
-page_title: System Requirements
-description: "Test Studio Mobile System Requirements"
-position: 0
-slug: ms-requirements
-previous_url: /test-studio-mobile/test-execution-requirements-mb
----
-#System Requirements
-
-##Test Recording
-
-To utilize the codeless point and click test recording, a Windows 7+ machine running Test Studio Mobile is needed. Currently, Test Studio Mobile comes as part of the Test Studio Ultimate bundle and can't be installed on Mac machines. Test recording requires at least 1 connected Native or Web test agent (see below).
-
-##Test Execution
-
-Test execution requires at least 1 connected Native or Web test agent (see below).
-
-* Windows 7+ machines - tests can be executed either by the Test Studio Mobile GUI or Mobile Testing Test Runner CLI for Windows.
-* Mac OS X 10.8+ machines - tests can be executed only by the Mobile Testing Test Runner CLI for Mac and Linux. 
-* Linux Ubuntu 14+ machines - tests can be executed only by the Mobile Testing Test Runner CLI for Mac and Linux.
-
-##Test Agent for Native/Hybrid Applications
-
-When a native or hybrid app is to be tested, test agent is the Mobile Testing Agent app for Android or iOS:
-
-###Android Native/Hybrid
-
-*	Install the Mobile Testing Agent app for Android on a device/emulator running Android 4+ 
-
-###iOS Native/Hybrid
-
-*	Install the Mobile Testing Agent app for iOS on a Device/simulator running iOS 8+
-
-##Test Agent for Web Applications
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-When a web app is to be tested, test agent is the browser itself (mobile or desktop). The browser must support WebSockets. Below is a short list of browsers that support WebSockets:
-
-*	iOS Safari 6.0+
-
-*	Android Browser 4.4+
-
-*	Chrome for Android 32.0+
-
-*	Firefox for Android 26.0+
-
-*	[See more](http://caniuse.com/#search=websocket)
-
-##Native Demo apps
-
-Preconfigured Native demo apps for Android and iOS are available for download. Building and deploying those apps require:
-
-*	Windows 7+ and Android Studio 0.4.0+ to deploy provided Android Demo Application
-*	Mac OS X 10.8+ and Xcode 6+ to deploy provided iOS Demo Application
-
-##Hybrid Demo app
-
-Preconfigured Hybrid demo app (Cordova) is available for download. Building and deploying that app require:
-
-*   Cordova CLI
-
-##Mobile Testing Test Runner CLI
-
-*	Windows 7+ machines - Mobile Testing Test Runner CLI installs as part of Test Studio Mobile. 
-*	Mac OS X 10.8+ machines - Mobile Testing Test Runner CLI can be downloaded and run separately and requires Mono to be installed on the Mac.
-*	Linux machines running Ubuntu 14+ - Mobile Testing Test Runner CLI can be downloaded and run separately and requires Mono to be installed on the machine.
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-execution/quick-execution.md b/docs/test-studio-mobile/test-execution/quick-execution.md
deleted file mode 100644
index 9bbe8fd2..00000000
--- a/docs/test-studio-mobile/test-execution/quick-execution.md
+++ /dev/null
@@ -1,48 +0,0 @@
----
-title: Quick Execution
-page_title: Quick Execution
-description: "Quick Execution"
-publish: true
-slug: ms-quick-execution
-position: 0
-slug: ms-quick-execution
----
-
-#Playback a Test
-
-1. Open your project in Test Studio Mobile.
-
-2. To playback a test, it must be open in the Test Studio test explorer (double-click a test to open it in the test explorer). Clicking on the **Playback** button starts the test execution.
-
-	![Playback Button](/img/test-studio-mobile/test-execution/quick-execution/fig1.png)
-
-##Test Results
-
-When the test is executed the passed steps are marked with green color
-
-![Passed steps](/img/test-studio-mobile/test-execution/quick-execution/fig2.png)
-
-and the failed steps are marked with red color
-
-![Failed steps](/img/test-studio-mobile/test-execution/quick-execution/fig3.png)
-
-### Error details
-
-The Error Details view collects all the information related to a single failed test step. Select the failed step and click **Error Details** button.
-
-![Error details](/img/test-studio-mobile/test-execution/quick-execution/fig4.png)
-
-###Execution log
-
-The execution log or test log is a log available after test execution in the test view. You can pull it out by clicking **View Log** button.
-
-![View Log button](/img/test-studio-mobile/test-execution/quick-execution/fig5.png)
-
-The execution log is a record of the steps executed in the test, whether they passed or failed. It records what actions a step takes and what elements it acts upon. It lists all steps in one sequence and provides details for failed steps if any.
-
-![Execution log](/img/test-studio-mobile/test-execution/quick-execution/fig6.png)
-
-###See Also
-
-*	[Run Demo Web Tests]({% slug ms-run-demos-web%})
-*	[Run Native/Hybrid Demo Tests]({% slug ms-run-demos%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-execution/test-list-execution.md b/docs/test-studio-mobile/test-execution/test-list-execution.md
deleted file mode 100644
index 7fa99537..00000000
--- a/docs/test-studio-mobile/test-execution/test-list-execution.md
+++ /dev/null
@@ -1,61 +0,0 @@
----
-title: Test List Execution
-page_title: Test List Execution
-description: "Test List Execution in Test Studio Mobile"
-publish: true
-position: 0
-slug: ms-testlist-execution
----
-
-# Mobile Test Lists
-
-1. In Test Studio Mobile you can execute one or more tests through a Test List. You can create a test list using the Create a List button:
-
-	![add test list](/img/test-studio-mobile/test-execution/test-list-execution/fig1.png)
-
-	or by right clicking on the TestList node in the project:
-
-	![add test list](/img/test-studio-mobile/test-execution/test-list-execution/fig2.png)
-
-2. A new dialog appears where you need to specify the test list type. Provide a name and click **OK**.
-
-	![list type](/img/test-studio-mobile/test-execution/test-list-execution/fig3.png)
-
- > Android Hybrid tests can be added to Android test lists and iOS Hybrid tests can be added to iOS test lists.
-
-3. In order to add a test in the test list, double click the list to open it in the middle pane of Test Studio and click on the Edit button:
-
-	![edit](/img/test-studio-mobile/test-execution/test-list-execution/fig4.png)
-
-4. Select one or multiple tests and add them in the test list by clicking the arrow and click **Done**. You can also add tests by double clicking them.
-
-	![add test](/img/test-studio-mobile/test-execution/test-list-execution/fig5.png)
-
-	The test now appears in the test list.
-
-	![test list added](/img/test-studio-mobile/test-execution/test-list-execution/fig6.png)
-
-	> You can also add tests using drag&drop directly from the project explorer into the test list.
-
-5. In order to execute the test list ensure it is open and click on the **Run** button or press **F5**.
-
-	![run test list](/img/test-studio-mobile/test-execution/test-list-execution/fig7.png)
-
-	You can also run a single list on multiple devices from the same type. Open the test list, and click the small arrow right next to the play button and choose the **Run on multiple** option:
-
-	![run on multiple](/img/test-studio-mobile/test-execution/test-list-execution/fig9.png)
-
-<a id="results"></a>
-The results of the test list run appear in the **Results** pane.
-
-![results](/img/test-studio-mobile/test-execution/test-list-execution/fig8.png)
-
-Double-click a test list in the Results view to see the result of each test. Double-clicking a test in this list drills down to show the steps of that test. The bread crumb trail at the top of the panel now shows the test list followed by the test name.
-
-![Drill down the results](/img/test-studio-mobile/test-execution/test-list-execution/fig10.png)
-
-Click the top level in the bread crumb trail to jump directly back to the test list result.
-
-###See Also
-
-*	[Playback a Test]({% slug ms-quick-execution%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-recording/create-test.md b/docs/test-studio-mobile/test-recording/create-test.md
deleted file mode 100644
index 067e7b27..00000000
--- a/docs/test-studio-mobile/test-recording/create-test.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Create a Test
-page_title:  Create a Test
-description: "Create a Test Studio Mobile test"
-slug: ms-create-test
-publish: true
-position: 0
-slug: ms-create-test
----
-
-#Create a Test Studio Mobile Test
-
-1. Launch Test Studio
-
-2. Click **Create project**, select **Mobile** and a Project Name and Location
-
-	![Create a test](/img/test-studio-mobile/test-recording/create-test/fig1.png)
-
-3. Click **Create a Test** button 
-
-	![Create a test button](/img/test-studio-mobile/test-recording/create-test/fig2.png)
-
-	or right click on the project and select **Add New Test**
-	
-	![Create a test button via right click](/img/test-studio-mobile/test-recording/create-test/fig3.png)
-
-4. Select the test type you want to create
-
-	![Select a test type](/img/test-studio-mobile/test-recording/create-test/fig4.png)
-
-## See also
-
-* [Record an Android test]({% slug ms-record-test-android%})
-* [Record an iOS test]({% slug ms-record-test-ios%})
-* [Record a Web test]({% slug ms-record-test-web%})
-* [Record Android Hybrid Test]({% slug ms-record-test-android-hybrid%})
-* [Record iOS Hybrid Test]({% slug ms-record-test-ios-hybrid%})
diff --git a/docs/test-studio-mobile/test-recording/record-a-test/record-test-android-hybrid.md b/docs/test-studio-mobile/test-recording/record-a-test/record-test-android-hybrid.md
deleted file mode 100644
index c1591826..00000000
--- a/docs/test-studio-mobile/test-recording/record-a-test/record-test-android-hybrid.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Record Android Hybrid Test
-page_title:  Record Android Hybrid Test
-description: "Record a Test Studio Mobile test"
-publish: true
-position: 3
-slug: ms-record-test-android-hybrid
----
-
-#Record an Android Hybrid Test
-
-Once the native Mobile Testing Agent app is [connected]({% slug ms-getting-started-native%}#Connect-Agent) to Test Studio Mobile the devices are listed in the **Conencted Devices** pane.
-
-1. Open an Android Hybrid test to enable the recording buttons. 
-
-	![Record Android Hybrid](/img/test-studio-mobile/test-recording/record-test/fig9.png)
-
-2. Clicking on any of the **Record** buttons, shows a dialog where `Application Identifier` must be entered. The app identifier is:
-	* For AppBuilder app, it is set during AppBuidler app [configuration process]({% slug ms-configure-hybrid-appbuilder%}#appid).
-	* For Cordova app, it is set in the Cordova CLI during the [Cordova App creation process]({% slug ms-configure-hybrid%}#App-Identifier) and is something like `com.mycompany.myapp`.
-	* For the [Demo Hyrbid App]({% slug ms-run-demos%}#Android-Hybrid-Demo-App), it is already setup with the **io.cordova.hellocordova** identifier for Android.
-
-	![Android Hybrid APP identifier](/img/test-studio-mobile/test-recording/record-test/fig10.png)
-
-3. Clicking the **Start** button disconnects the Agent app and launches the testable app. The test recorder is attached and any gestures or actions you perform over the launched testable app are recorded as steps in the Test Studio test
-
-	![Android App](/img/test-studio-mobile/test-recording/record-test/fig11.png)
-
-	> Additional steps (e.g. verifications) can be added through the [Step Builder]({% slug ms-step-builder%}).
-
-4. Once the test is complete, stop recording by clicking on the **Stop Record** button. The recorder is detached, the testable app is closed and the Agent app is returned in connected state.
-
-	![Stop recording Android App](/img/test-studio-mobile/test-recording/record-test/fig12.png)
-
-## See also
-
-* [Create a test]({% slug ms-create-test%})
-* [Connect agent USB]({% slug ms-connect-agent-usb%})
-* [Connect agent Wi-Fi]({% slug ms-connect-agent-wifi%})
-
-[1]: https://cordova.apache.org/docs/en/latest/guide/cli/index.html
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-recording/record-a-test/record-test-android.md b/docs/test-studio-mobile/test-recording/record-a-test/record-test-android.md
deleted file mode 100644
index 22db3358..00000000
--- a/docs/test-studio-mobile/test-recording/record-a-test/record-test-android.md
+++ /dev/null
@@ -1,43 +0,0 @@
----
-title: Record Android Test
-page_title:  Record Android Test
-description: "Record a Test Studio Mobile test"
-publish: true
-slug: ms-record-test-android
-previous_url: /test-studio-mobile/test-recording/record-test
-position: 0
-slug: ms-record-test-android
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-#Record an Android Test
-
-Once the native Mobile Testing Agent app is [connected]({% slug ms-getting-started-native%}#Connect-Agent) to Test Studio Mobile the devices are listed in the **Conencted Devices** pane.
-
-1. Open an Android test to enable the recording buttons. 
-
-	![Record Android](/img/test-studio-mobile/test-recording/record-test/fig8.png)
-
-2. Clicking on any of the **Record** buttons, shows a dialog where `Application Identifier` must be selected. The app identifier is setup during the [Android instrumentation process]({% slug ms-configure-android%}) of the testable app. The [Demo App]({% slug ms-run-demos%}#Android-Demo-App) is already setup with the **com.telerik.demoapplication** identifier.
-
-	![Android APP identifier](/img/test-studio-mobile/test-recording/record-test/fig5.png)
-
-3. Clicking the **Start** button disconnects the Agent app and launches the Demo App. The test recorder is attached and any gestures or actions you perform over the launched Demo App is recorded as steps in the Test Studio test
-
-	![Android App](/img/test-studio-mobile/test-recording/record-test/fig6.png)
-
-	**Note:** Additional steps (e.g. verifications) can be added through the [Step Builder]({% slug ms-step-builder%}).
-
-4. Once the test is complete, stop recording by clicking on the **Stop Record** button. The recorder is detached, the Demo App is closed and the Agent app is returned in connected state.
-
-	![Stop recording Android App](/img/test-studio-mobile/test-recording/record-test/fig7.png)
-
-## See also
-
-* [Create a test]({% slug ms-create-test%})
-* [Connect agent USB]({% slug ms-connect-agent-usb%})
-* [Connect agent Wi-Fi]({% slug ms-connect-agent-wifi%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios-hybrid.md b/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios-hybrid.md
deleted file mode 100644
index 8cc7d679..00000000
--- a/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios-hybrid.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Record iOS Hybrid Test
-page_title:  Record iOS Hybrid Test
-description: "Record a Test Studio Mobile test"
-publish: true
-position: 4
-slug: ms-record-test-ios-hybrid
----
-
-#Record an iOS Hybrid Test
-
-Once the native Mobile Testing Agent app is [connected]({% slug ms-getting-started-native%}#Connect-Agent) to Test Studio Mobile the devices are listed in the **Conencted Devices** pane.
-
-1. Open an iOS Hybrid test to enable the recording buttons. 
-
-	![Record iOS Hybrid](/img/test-studio-mobile/test-recording/record-test/fig13.png)
-
-2. Clicking on any of the **Record** buttons, shows a dialog where `Application Identifier` must be entered. The app identifier is:
-	* For AppBuilder app, it is set during AppBuidler app [configuration process]({% slug ms-configure-hybrid-appbuilder%}#appid).
-	* For Cordova app, it is set in the Cordova CLI during the [Cordova App creation process]({% slug ms-configure-hybrid%}#App-Identifier) and is something like **telerikmt1**.
-	* For the [Demo Hyrbid App]({% slug ms-run-demos%}#Android-Hybrid-Demo-App), it is already setup with the **telerikmt1** identifier for iOS.
-
-	![iOS Hybrid APP identifier](/img/test-studio-mobile/test-recording/record-test/fig14.png)
-
-3. Clicking the **Start** button disconnects the Agent app and launches the testable app. The test recorder is attached and any gestures or actions you perform over the launched testable app are recorded as steps in the Test Studio test
-
-	![iOS App](/img/test-studio-mobile/test-recording/record-test/fig15.png)
-
-	> Additional steps (e.g. verifications) can be added through the [Step Builder]({% slug ms-step-builder%}).
-
-4. Once the test is complete, stop recording by clicking on the **Stop Record** button. The recorder is detached, the testable app is closed and the Agent app is returned in connected state.
-
-	![Stop recording iOS App](/img/test-studio-mobile/test-recording/record-test/fig16.png)
-
-## See also
-
-* [Create a test]({% slug ms-create-test%})
-* [Connect agent USB]({% slug ms-connect-agent-usb%})
-* [Connect agent Wi-Fi]({% slug ms-connect-agent-wifi%})
-
-[1]: https://cordova.apache.org/docs/en/latest/guide/cli/index.html
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios.md b/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios.md
deleted file mode 100644
index 2508c6d3..00000000
--- a/docs/test-studio-mobile/test-recording/record-a-test/record-test-ios.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Record iOS Test
-page_title:  Record iOS Test
-description: "Record a Test Studio Mobile test"
-publish: true
-position: 1
-slug: ms-record-test-ios
----
-
-#Record an iOS Test
-
-Once the native Mobile Testing Agent app is [connected]({% slug ms-getting-started-native%}#Connect-Agent) to Test Studio Mobile the devices are listed in the **Conencted Devices** pane.
-
-1. Open an iOS test to enable the recording buttons. 
-
-	![Record iOS](/img/test-studio-mobile/test-recording/record-test/fig1.png)
-
-2. Clicking on any of the **Record** buttons, shows a dialog where `Application Identifier` must be selected. The app identifier is setup during the [iOS instrumentation process]({% slug ms-configure-ios%}) of the testable app. The [Demo App]({% slug ms-run-demos%}#iOS-Demo-App) is already setup with the **tsdemoapplication://** identifier.
-
- 	> When used in Test Studio, the `Application Identifier` setup in Xcode must be suffixed with **://**. For example, the app identifier that is setup for the Demo app in Xcode is **tsdemoapplication** (no trailing colon and slashes), but suffixed with **://** when entered in the Test Studio **Set Application ID** dialog.
-
-	![iOS App](/img/test-studio-mobile/test-recording/record-test/fig2.png)
-
-3. Clicking the **Start** button disconnects the Agent app and launches the Demo App. The test recorder is attached and any gestures or actions you perform over the launched Demo App is recorded as steps in the Test Studio test:
-
-	![iOS App](/img/test-studio-mobile/test-recording/record-test/fig3.png)
-
-	**Note:** Additional steps (e.g. verifications) can be added through the [Step Builder]({% slug ms-step-builder%}).
-
-4. Once the test is complete, stop recording by clicking on the **Stop Record** button. The recorder is detached, the Demo App is closed and the Agent app is returned in connected state.
-
-	![iOS App](/img/test-studio-mobile/test-recording/record-test/fig4.png)
- 
-## See also
-
-* [Create a test]({% slug ms-create-test%})
-* [Connect agent USB]({% slug ms-connect-agent-usb%})
-* [Connect agent Wi-Fi]({% slug ms-connect-agent-wifi%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/test-recording/record-a-test/record-test-web.md b/docs/test-studio-mobile/test-recording/record-a-test/record-test-web.md
deleted file mode 100644
index 76b7b545..00000000
--- a/docs/test-studio-mobile/test-recording/record-a-test/record-test-web.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Record Web Test
-page_title:  Record Web Test
-description: "Record a Test Studio Mobile test"
-publish: true
-position: 2
-slug: ms-record-test-web
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-#Record a Web Test
-
-Once the web agent (browser) is [connected]({% slug ms-connect-webagent%}) to Test Studio Mobile the agents (browsers) are listed in the **Conencted Devices** pane.
-
-1. [Create]({% slug ms-create-test%}) and open a Web test. Once you open it the recording buttons are getting enabled.
-
-	![Record buttons](/img/test-studio-mobile/test-recording/record-test/record-web-test/fig1.png)
-
-2. Clicking on any of the **Record** buttons shows a dialog where *Application Url* must be typed (e.g. http://www.telerik.com).
-
-	![Set URL](/img/test-studio-mobile/test-recording/record-test/record-web-test/fig2.png)
-
-3. Clicking the **Start** button navigates to the set URL in your mobile browser. The test recorder is attached and any gestures or actions you perform over the launched web application is recorded as steps in the Test Studio test. 
-
-	![Record the test](/img/test-studio-mobile/test-recording/record-test/record-web-test/fig3.png)
-
-	**Note:** Additional steps (e.g. verifications) can be added through the [Step Builder]({% slug ms-step-builder%}).
-
-4. Once the test is complete, stop recording by clicking on the **Stop Record** button. The recorder is detached and you can run the test.
-
-	![Stop the recording](/img/test-studio-mobile/test-recording/record-test/record-web-test/fig4.png)
-
-## See also
-
-* [Connect a Web Agent]({% slug ms-connect-webagent%})
-* [Step Builder]({% slug ms-step-builder%})
-* [Quick Execution]({% slug ms-quick-execution%})
diff --git a/docs/test-studio-mobile/troubleshooting/configure-android-settings.md b/docs/test-studio-mobile/troubleshooting/configure-android-settings.md
deleted file mode 100644
index aa3b9bc4..00000000
--- a/docs/test-studio-mobile/troubleshooting/configure-android-settings.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Android Configuration Settings
-page_title: Android Configuration Settings
-description: Apply our testing extension to your native Android application.
-slug: ms-configure-android-settings
-tags: android testing, native
-publish: true
-position: 0
-previous_url: /test-studio-mobile/troubleshooting-mb/configure-android-settings
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">automated responsive testing</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> As of March 1, 2020, native mobile testing is __no longer supported__.
-
-#Android Configuration Settings
-
-Configuring an Android app to be testable is a complicated process that unzips the app (.apk) file, changes it and then rebuilds it. Several **Android** and **Java** tools are taking part into the process and that is why it is important to have all configurations correctly set. The configuration mechanism saves and loads these settings from a file that is created the first time Android application configuration is initiated. The file contents is in pure text format and can be edited manually using any text editor. However, it is not recommended to manually edit it except in the cases listed in this topic.
-
-The first time **Android** application configuration is started, a path to the **Android SDK** and **Java JDK** folders must be set. Those values are then saved in the configuration settings file and can be changed either through the Android application configuration dialog or manually. If either of the values is not valid or does not exist, error messages are shown and configuration can't be continued. 
-
-![SDK_JAVA_errors](/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig1.png)
-
-In some cases Android application configuration can't be continued even when **Android SDK** and **Java JDK** paths are set correctly. In addition to these 2 parameters, it also depends on Android build tools version and Android platforms installed. They are automatically set based on the Android SDK value. If for some reason the saved Android Build Tools and Platform values become invalid (e.g. uninstall them from the Android SDK Manager), Android application configuration won't work and errors will be shown. To fix this you can either:
-	
-1. Open the Android application configuration dialog and delete the **Android SDK** value and enter it again. This will initiate a new automatic detection of the Android build tools and Android platform versions.
-	
-2. Close the Android application configuration dialog. Edit the values manually in the configuration file that is by default located in `%USERPROFILE%\AppData\Roaming\ArtOfTest\MtAPKProvisioningSettings.json`. 
-
-![BuildTool_Platform](/img/test-studio-mobile/troubleshooting-guide/android-configuration/fig2.png)
-
-After the configuration file is edited, save it and reopen Android application configuration dialog to pick the new values.
\ No newline at end of file
diff --git a/docs/test-studio-mobile/troubleshooting/known-issues.md b/docs/test-studio-mobile/troubleshooting/known-issues.md
deleted file mode 100644
index 365069e0..00000000
--- a/docs/test-studio-mobile/troubleshooting/known-issues.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Known Issues
-page_title: Known Issues 
-description: "Known Issues"
-publish: true
-position: 0
-slug: ms-known-issues
-previous_url: /test-studio-mobile/troubleshooting-mb/known-issues,/test-studio-mobile/troubleshooting-mb
----
-
-#Known Issues
-
-##PROBLEM
-
-After a Test Studio is upgraded, running coded tests created with previous Test Studio versions may fail with:
-
-*Could not load file or assembly error*
-
-![Could not load assembly](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig5.png)
-
-##SOLUTION
-
-This is expected behavior for projects that have coded steps. All you have to do to resolve it is:
-
-1. Open you test project root folder.
-
-2. Open the Bin folder inside it and delete the file named *MyProjectName.dll*.
-
-3. Run the test.
-
-
-##PROBLEM
-
-I am getting *TestProject.TestName does not contain a definition for "Context" and no extension method "Context" accepting a first argument of type TestProject.TestName could be found (are you missing a using directive or an assembly reference?)* compilation error in my C# project
-
-![C# error](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig1.png)
-
-and 
-
-*"Context is not a member of TestProject.TestName error in file C:\Users\\[userName]\AppData\Local\Temp\tempFileName.tmp"* compilation error in my VB project.
-
-![VB error](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig2.png)
-
-This compile error appears in case you have changed the class name in your code file.
-
-![VB error](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig3.png)
-
-##SOLUTION
-
-When you change the class name you should bind the test to the new class name. You can do this from the test properties.
-
-![Bind the new class](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig4.png)
-
-<div id="instumentation-exception">
-##PROBLEM
-
-*While instrumenting a native Android application through the [built in method]({% slug ms-configure-android%}#Built-In-Configuration) I get the following exception:*
-
-![Error while instrumenting Android app](/img/test-studio-mobile/knowledge-base-tm/known-issues/fig6.png)
-
-This happens when the app to be instrumented has more than 65536 methods and is is installed on device running API level 20 and below. 
-
-##SOLUTION
-
-You should use device which is running API level 21 or higher or use the [manual]({% slug ms-configure-android%}#Manual) instrumentation.
\ No newline at end of file
diff --git a/docs/test-studio-mobile/web-applications/configuration/certificate.md b/docs/test-studio-mobile/web-applications/configuration/certificate.md
deleted file mode 100644
index 250a86cb..00000000
--- a/docs/test-studio-mobile/web-applications/configuration/certificate.md
+++ /dev/null
@@ -1,15 +0,0 @@
----
-title: Install Certificate
-page_title: Install Certificate
-description: "Install Certificate"
-position: 1
-slug: ms-certificate
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-
-# Install Certificate #
-
-> Before proceeding with the certificate installation you should have  successfully set up. [Connect the Web Agent]({% slug ms-connect-webagent %}).
-
-To accept the routed proxy traffic, the web client must trust the web proxy server. This requires installing a certificate on the device.
diff --git a/docs/test-studio-mobile/web-applications/configuration/configure-teststudio-mobile.md b/docs/test-studio-mobile/web-applications/configuration/configure-teststudio-mobile.md
deleted file mode 100644
index b5ebdae7..00000000
--- a/docs/test-studio-mobile/web-applications/configuration/configure-teststudio-mobile.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Configure Test Studio Mobile
-page_title: Configure Test Studio Mobile
-description: "Configure Test Studio Mobile"
-position: 0
-slug: ms-configure-tsm
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-# Configure Test Studio Mobile for Web testing
-
-> The web testing configuration is a 4 step process. The first step is to configure the Test Studio Mobile project on the desktop machine.
-
-1. Create a **Mobile** test project and [add a web test]({% slug ms-create-test%}).
-
-2. Go to [project settings]({% slug ms-project-settings%}) and set the **Web proxy port** (the default is set to 8083). 
-
-3. Click **Connect Device** under **Connected Device** pane. 
-
-	![Connect Device](/img/test-studio-mobile/web-applications/connect-web-agent/fig2.png)
-
-4. Choose the **Web Browser** tab.
-
-	4.1 Click **Install** button to set the local HTTPS certificate.
-
-	4.2 Using the mobile browser you want to test in go to the shown URL or scan the QR code. This will navigate you to the TestStudio Mobile agent configuration page on your device.
-
-	![Navigate to URL](/img/test-studio-mobile/web-applications/connect-web-agent/fig3.png)
-
-5. Continue with [Proxy Configuration]({% slug ms-webproxy%})
\ No newline at end of file
diff --git a/docs/test-studio-mobile/web-applications/configuration/connect-agent.md b/docs/test-studio-mobile/web-applications/configuration/connect-agent.md
deleted file mode 100644
index 7c2ddefe..00000000
--- a/docs/test-studio-mobile/web-applications/configuration/connect-agent.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Connect Web Agent
-page_title: Connect Web Agent
-description: "Connect Web Agent"
-position: 5
-slug: ms-connect-webagent
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-
-# Connect Web Agent
-
-1. After successful [proxy configuration]({% slug ms-webproxy%}) and [certificate installation]({% slug ms-certificate%}) tap the **Connect** button to connect to Test Studio execution agent configuration page.
-
-	![Connect to the execution agent](/img/test-studio-mobile/web-applications/connect-web-agent/fig7.png)
-
-	> In some cases you may have to **restart Chrome** mobile browser in order to access the connect screen in TestStudio Mobile agent configuration page (step 3. Connect).
-
-2. After successful connection you can start [recording a web test]({% slug ms-record-test-web%}). Alternatively, [run the Demo web tests]({% slug ms-run-demos-web%})
-
-
-	![Successful connection](/img/test-studio-mobile/web-applications/connect-web-agent/fig8.png)
-
-**See Also**
-
-* [Record a web test]({% slug ms-record-test-web%})
-+ [Playback Tests]({% slug ms-quick-execution%})
diff --git a/docs/test-studio-mobile/web-applications/configuration/proxy.md b/docs/test-studio-mobile/web-applications/configuration/proxy.md
deleted file mode 100644
index 96dbe0ec..00000000
--- a/docs/test-studio-mobile/web-applications/configuration/proxy.md
+++ /dev/null
@@ -1,93 +0,0 @@
----
-title: Configure Proxy
-page_title: Configure Proxy
-description: "Configure Proxy"
-position: 1
-slug: ms-webproxy
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-# Configure Proxy
-
-> Before proceeding with the proxy configuration you must have [Test Studio Mobile Configuration]({% slug ms-configure-tsm%}) successfully set up.
-
-## Configure Web Proxy On Mobile Devices
-
-Test Studio Mobile uses a web proxy for injecting a web extension in every page that a web test navigates to. Before tests are recorded or executed, the web browser must be configured to route its traffic through Test Studio Mobile web proxy.
-
-*	**Android Browsers**
-	*	<a href="#android">Chrome (other)</a>
-	*	<a href="#android-firefox">FireFox</a>
-
-*	**iOS browsers**
-	*	<a href="#ios">All browsers</a>
-
-
-##Android
-
-<a id="android"></a>
-###Chrome (other)
-
-1. On your mobile device tap **Settings -> WiFi**.
-
-2. Long tap on connected network's name.
-
-3. Modify Network Config -> Show Advanced Options.
-
-4. Type the **Host** into the **Proxy host name** field and the **Port** into to the **Proxy port** field. Take the **Host** and **Port** values from the TestStudio Mobile agent configuration page on your device.
-
-	![Configure proxy Android](/img/test-studio-mobile/web-applications/proxy/fig1.png)
-
-5. Click **Save** in the settings dialog. Click the **Next** button in the browser.
-
-6. Continue with [Install Certificate]({% slug ms-certificate%}) procedure.
-
-<a id="android-firefox"></a>
-###FireFox
-
-
-1. Type **about:config** in your FifeFox mobile browser.
-
-2. Search for Proxy and enter the **Host** and **Port** in the corresponding fields. Take the **Host** and **Port** values from the TestStudio Mobile agent configuration page on your device.
-
-	*	**network.proxy.http** - Host
-	*	**network.proxy.http_port** - Port
-
-	![FF](/img/test-studio-mobile/web-applications/proxy/fig3.png)
-
-3. Do the same for SSL connection and don't forget to set **Network Proxy Type** to 1.
-
-	*	**network.proxy.ssl** - Host
-	*	**network.proxy.ssl_port** - Port
-	*	**network.proxy.type** - **set to 1**.
-
-	![FF](/img/test-studio-mobile/web-applications/proxy/fig4.png)
-
-4. After configuring the WiFI proxy settings click the **Next** button.
-
-5. Continue with [Install Certificate]({% slug ms-certificate%}) procedure.
-
-<a id="ios"></a>
-##iOS
-
-###All Browsers
-
-1. Tap **Settings -> Wifi -> Tap the connected WiFi network**.
-
-2. Tap the **Manual** option in the HTTP Proxy section.
-
-3. Type **Host** into the **Server** field and the **Proxy** into to the **Port** field. Take the **Host** and **Port** values from the TestStudio Mobile agent configuration page on your device.
-
-	![Configure proxy iOS](/img/test-studio-mobile/web-applications/proxy/fig2.png)
-
-4. After configuring the WiFI proxy settings click the **Next** button.
-
-5. Continue with [Install Certificate]({% slug ms-certificate%}) procedure.
\ No newline at end of file
diff --git a/docs/test-studio-mobile/web-applications/run-demos.md b/docs/test-studio-mobile/web-applications/run-demos.md
deleted file mode 100644
index 070cea1c..00000000
--- a/docs/test-studio-mobile/web-applications/run-demos.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Run Demo Web Tests
-page_title: Run Demo Web Tests
-description: "Run Demo Web Tests"
-position: 1
-slug: ms-run-demos-web
----
-
-> To help you meet the demands of mobile users, Test Studio offers <a href="https://www.telerik.com/teststudio/automated-website-responsive-testing" target="_blank">responsive testing of web applications</a> enabling you to test your web application's layout, functionality and behavior on mobile and desktop browsers.
-><br>
-><br>
-> Check out the <a href="/automated-tests/responsive/responsive-test" target="_blank">technical documentation for responsive application testing</a> in Test Studio.
-
-{% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
-{% endif %}
-
-# Run Demo Web Tests
-
-1. [Configure]({% slug ms-configure-tsm%}) the web agent.
-
-2. Download the [mobile demo tests project](/samples/DemoMobileProject.zip).
-
-3. Start Test Studio Mobile, click on **Open Project**, navigate to the demo mobile project folder and click **Select Folder**.
-
-	![Open demo project](/img/test-studio-mobile/web-applications/run-web-demos/fig1.png)
-
-4. Open and run any web test or web test list through the quick execution button.
-
-	![run web test](/img/test-studio-mobile/web-applications/run-web-demos/fig2.png)
-
-
-See Also
---------
-
-+ [Playback Tests]({% slug ms-quick-execution%})
-+ [Record Web Test]({% slug ms-record-test-web%})
\ No newline at end of file
diff --git a/docs/testing-framework/api-reference.md b/docs/testing-framework/api-reference.md
index 1f5835a3..8d35e2da 100644
--- a/docs/testing-framework/api-reference.md
+++ b/docs/testing-framework/api-reference.md
@@ -5,6 +5,6 @@ description: "Test Studio Testing Framework API reference."
 position: 8
 ---
 
-#API Reference#
+# API Reference
 
 You can access Test Studio API <a href="http://docs.telerik.com/teststudio/api" target="_blank">here</a>.
diff --git a/docs/testing-framework/automate-browser-actions.md b/docs/testing-framework/automate-browser-actions.md
index 1ccd7105..26c6a3dc 100644
--- a/docs/testing-framework/automate-browser-actions.md
+++ b/docs/testing-framework/automate-browser-actions.md
@@ -5,7 +5,8 @@ description: "Test Studio Testing Framework support in coded test for automating
 previous_url: /user-guide/getting-started/automating-browser-actions.aspx, /user-guide/getting-started/automating-browser-actions
 position: 1
 ---
-#Automate Browser Actions (DOM & UI)#
+
+# Automate Browser Actions (DOM & UI)
 
 Telerik Testing Framework supports three types of automation actions:
 
@@ -17,7 +18,7 @@ Telerik Testing Framework supports three types of automation actions:
  
 The code sample below demonstrates browser control and direct DOM actions.
 
-```C#
+````C#
 // *** Browser control below
   
 // Some test cases may require that all cookies be cleared ahead of time.  
@@ -98,8 +99,8 @@ ActiveBrowser.Actions.SelectDropDown(selection, "test", true);
 // the currently selected text should be the dropdown selection
 string textSelected = ActiveBrowser.GetSelectedText();   
 Assert.AreEqual("test", textSelected, "Actual test is \"{0}\"", textSelected);
-```
-```VB
+````
+````VB
  
 ActiveBrowser.NavigateTo("http://www.google.com")
   
@@ -172,7 +173,7 @@ Actions.SelectDropDown(selection, 2)
 
 Dim textSelected As String = ActiveBrowser.GetSelectedText()
 Assert.AreEqual("test", textSelected, "Actual test is ""{0}""", textSelected)
-```
+````
 
 Let's look at some pure UI automation to simulate some of the DOM actions above. Before we look at the sample code, there are few things to note regarding pure UI automation using Telerik Testing Framework:
 
@@ -184,7 +185,7 @@ Let's look at some pure UI automation to simulate some of the DOM actions above.
  
 The code below shows how to set the text for the 'input1' text box using pure UI automation:
 
-```C#
+````C#
 ActiveBrowser.Actions.ScrollToVisible(input1);
 
 //The ScrollToVisible method could set an element to the top  or the bottom of the page 
@@ -194,14 +195,14 @@ input1.ScrollToVisible(ArtOfTest.WebAii.Core.ScrollToVisibleType.ElementTopAtWin
 
 Manager.Desktop.Mouse.Click(MouseClickType.LeftClick, input1.GetRectangle());
 Manager.Desktop.KeyBoard.TypeText("Hello there", 100);
-```
-```VB
+````
+````VB
 ActiveBrowser.Actions.ScrollToVisible(input1)
 Manager.Desktop.Mouse.Click(MouseClickType.LeftClick, input1.GetRectangle())
 Manager.Desktop.KeyBoard.TypeText("Hello there", 100)
-```
+````
 
-##Advanced Scenarios##
+## Advanced Scenarios
 
 The 'Mouse' object offers a rich set of APIs to perform some complex UI automation including operations like DragAndDrop that is extremely difficult to perform using direct DOM automation. Such types of operations are becoming more popular with the rich content applications that are emerging on the internet. For example, you can use this DragAndDrop support to automate portals that include web part regions that can be dragged and repositioned like Microsoft's SharePoint server or Google's customized homepage.
  
@@ -213,7 +214,7 @@ For example, if you are attempting to click the red (x) on this window to drag i
 
 You would write something like this:
 
-```C#
+````C#
 // get the window element we are trying to drag.
 Element mywindow = ActiveBrowser.Find.ByName("mydraggablewindow");
   
@@ -224,8 +225,8 @@ Element mydestination = ActiveBrowser.Find.ById("mydestinationlocation");
 // from the top center edge) and dragging it to the center of the destination location.
 Manager.Desktop.Mouse.DragDrop(mywindow.GetRectangle(), new System.Drawing.Point(0, 2), OffsetReference.TopCenter,
     mydestination.GetRectangle(), new System.Drawing.Point(0, 0), OffsetReference.AbsoluteCenter);
-```
-```VB
+````
+````VB
 ' get the window element we are trying to drag.
 Dim mywindow As Element = ActiveBrowser.Find.ByName("mydraggablewindow")
   
@@ -236,6 +237,6 @@ Dim mydestination As Element = ActiveBrowser.Find.ById("mydestinationlocation")
 ' from the top center edge) and dragging it to the center of the destination location.
 Manager.Desktop.Mouse.DragDrop(mywindow.GetRectangle(), New Drawing.Point(0, 2), OffsetReference.TopCenter, _
     mydestination.GetRectangle(), New Drawing.Point(0, 0), OffsetReference.AbsoluteCenter)
-```
+````
 
 [1]: /img/testing-framework/automate-browser-actions/fig1.jpg
\ No newline at end of file
diff --git a/docs/testing-framework/frequently-asked-questions.md b/docs/testing-framework/frequently-asked-questions.md
index c374ce1d..150824fd 100644
--- a/docs/testing-framework/frequently-asked-questions.md
+++ b/docs/testing-framework/frequently-asked-questions.md
@@ -4,7 +4,7 @@ page_title: Frequently Asked Questions
 description: "Test Studio Testing Framework FAQ."
 position: 1
 ---
-#Frequently Asked Questions#
+# Frequently Asked Questions
 
 * **How much does Telerik Testing Framework cost?**
 	
@@ -68,13 +68,13 @@ System.Configuration.ConfigurationErrorsException: System.Configuration.Configur
 
 *There is a significant difference between TextContent and InnerText. TextContent is only the text at the same level as the node. InnerText is the combined text from the current node and everything below it. The text you are seeing in the browser window is probably contained within another element, such as a <span> element. Studying an HTML example will help make this clear:*
 	
-```HTML
+````HTML
 <td id="gridEvents_rc_0_0">
    Same Level Text
    <nobr>Foremen
        <div>Lower Level Text</div>
    </nobr>
 </td>
-```   
+````   
 
 *In this example TextContent is the string "Same Level Text". InnerText is the string "Same Level TextForemenLower Level Text". You can probably use InnerText in your code in place of TextContent and be just fine.*	
\ No newline at end of file
diff --git a/docs/testing-framework/getting-started.md b/docs/testing-framework/getting-started.md
index e025df99..a6b8b8ea 100644
--- a/docs/testing-framework/getting-started.md
+++ b/docs/testing-framework/getting-started.md
@@ -31,27 +31,17 @@ padding: 8px;
 
 </style>
 
-#Getting Started with Telerik Testing Framework#
+# Getting Started with Telerik Testing Framework
 
 Thanks for using Telerik Testing Automation infrastructure. To get started using this framework, please follow the instructions below. If you have further questions, feel free to <a href="http://www.telerik.com/account/support-tickets/available-support-list.aspx" target="_blank">contact us</a>.
 
 
-##Installing and Setting Up the Infrastructure##
+## Installing and Setting Up the Infrastructure
 
 To get started, first download the <a href="https://www.telerik.com/teststudio/testing-framework" target="_blank">Telerik Testing Framework</a> installer package and run the installation. Once it is complete, you will have all of the following placed in the Telerik Testing Framework %InstallDir% folder:
 
 * The Telerik Automation Infrastructure library. **ArtOfTest.WebAii.dll** (for version 2010 and older, **ArtOfTest.Common.dll** is also included).
 
-* Telerik's Internet Explorer client. **ArtOfTest.InternetExplorer.dll**.
-
-* Telerik's Firefox client: Automatically installed in your install directory.
-
-* Chrome: You should download and install manually Telerik <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> Chrome Playback extension from the <a href="https://chrome.google.com/webstore/category/extensions" target="_blank">Chrome Web Store</a>. See <a href="/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome" target="_blank">this article</a> for direct extension links.
-
-* Safari client: Automatically installed in your install directory.
-
-* Silverlight plug-in: **ArtOfTest.WebAii.Mime.dll**.
-
 * Our HTTP Proxy: **ArtOfTest.WebAii.HttpProxy.exe**.
 
 * ASP.NET TestRegion Custom Control: **ArtOfTest.WebAii.AspNet.dll**.
@@ -72,7 +62,7 @@ To get started, first download the <a href="https://www.telerik.com/teststudio/t
 
 > Both the Telerik Testing Framework library and the Internet Explorer client are installed and ready to use once the installation is complete. The templates are also installed into your local templates for the current user. You also have a copy of these templates under %InstallDir%\Visual Studio Templates\.
 
-##Starting Automation Using Telerik Testing Framework##
+## Starting Automation Using Telerik Testing Framework
 
 * If you are using Visual Studio Team Test, please reference the <a href="/testing-framework/using-vs-team-test" target="_blank">Studio Team Test</a> Using Visual  topic.
 
@@ -94,11 +84,11 @@ Once <a href="https://www.telerik.com/teststudio/testing-framework" target="_bla
 
 5. Click OK to finish adding the needed references.
 
-##Quick Start Sample Code##
+## Quick Start Sample Code
 
 Before calling into any of the Telerik library methods, you need to make sure that you have properly initialized an instance of the **Manager** object passing in the settings you want used for this instance. To initialize the project:
 
-```C#
+````C#
 // Initialize the settings
 Settings mySettings = new Settings();
  
@@ -123,8 +113,8 @@ myManager.ActiveBrowser.Actions.Click(mybtn);
  
 // Shut-down the manager and do all clean-up
 myManager.Dispose();
-```
-```VB
+````
+````VB
 
 
 Dim mySettings As New Settings()
@@ -150,7 +140,7 @@ myManager.ActiveBrowser.Actions.Click(mybtn)
  
 
 myManager.Dispose()
-```
+````
 
 The Manager object exposes all methods/properties needed to perform browser automation, element identification, logging and DOM traversal including TestRegion identification. Below is a brief description of the key objects exposed off the Manager and their corresponding key object properties/methods:
 
diff --git a/docs/testing-framework/using-mbunit.md b/docs/testing-framework/using-mbunit.md
index a20678cd..1cefb85d 100644
--- a/docs/testing-framework/using-mbunit.md
+++ b/docs/testing-framework/using-mbunit.md
@@ -1,11 +1,11 @@
 ---
 title: Using MbUnit
 page_title: Using MbUnit
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Test Studio Testing Framework with MbUnit test"
 position: 1
 ---
 
-#Using MbUnit#
+# Using MbUnit
 
 <a href="https://www.telerik.com/teststudio/testing-framework" target="_blank">Telerik Testing Framework</a> comes with built-in support for MbUnit 3.2.3 and higher. The latest release of MbUnit can be downloaded <a href="https://code.google.com/p/mb-unit/" target="_blank">here</a>.
 
@@ -17,7 +17,7 @@ Telerik Automation Infrastructure comes with the following features to facilitat
 
 * When installing Telerik Testing Framework, a new fully commented MbUnit.net item template will be added to your list of available templates. This will enable you to start using Telerik by simply selecting it from the Add->New Item tool menu (or context menu) available to your VS project. You are provided with both a C# and a VB.NET template.
 
-##Getting Started Using MbUnit##
+## Getting Started Using MbUnit
 
 In this section we will walk you through the steps to get you started using <a href="https://www.telerik.com/teststudio/testing-framework" target="_blank">Testing Framework</a> with MbUnit.net.
 
@@ -41,7 +41,7 @@ In this section we will walk you through the steps to get you started using <a h
 
 * Start writing your automated <a href="https://www.telerik.com/teststudio/testing-framework" target="_blank">Testing Framework</a> unit tests.
 
-##Telerik's MbUnit Template##
+## Telerik's MbUnit Template
 
 Telerik MbUnit.net tests inherit from a base test class called **BaseTest** that lives in the **ArtOfTest.WebAii.TestTemplate** namespace. The base class, in addition to providing the integration benefits described above, provides:
 
@@ -83,16 +83,16 @@ Telerik MbUnit.net tests inherit from a base test class called **BaseTest** that
 
 * The base class also offers different options that you might want to choose from depending on the scenarios and your testing environment. The Telerik template installed on your machines, by default uses the following initialization:
 
-```C#
+````C#
 Initialize(false);
-```
-```VB
+````
+````VB
 Initialize(False)
-```
+````
 
 The above initializes the Telerik Testing Framework but does not enable the RecycleBrowser feature. Because MbUnit.net does not have the concept of a test fixture setup/teardown the RecycleBrowser feature cannot be used. If that initialization does not work for you, you can choose to pass in different parameters or choose to do your own custom setup of the framework. For example, if you want to override some of the settings from the .config file in one or two of your test cases, you can simply do the following:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -104,8 +104,8 @@ settings.DefaultBrowser = BrowserType.FireFox;
   
 // Now call Initialize with your updated settings object
 Initialize(settings);
-```
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -117,14 +117,14 @@ mySettings.DefaultBrowser = BrowserType.FireFox
   
 ' Now call Initialize with your updated settings object
 Initialize(mySettings)
-```
+````
 
 For more information on Telerik Testing Framework's settings & configuration please refer to the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class" target="_blank">Settings and Configuration</a> topic.
 
-##Starting Automation##
+## Starting Automation
 
 
-```C#
+````C#
 [Test]
 [Description("My simple demo")]
 public void SimpleTest()
@@ -138,8 +138,8 @@ public void SimpleTest()
      // verify the title is actually Google.
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText);
 }
-```
-```VB
+````
+````VB
 <Test(), _
 Description("My simple demo")> _
 Public Sub SimpleTest()
@@ -154,6 +154,6 @@ Public Sub SimpleTest()
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText)
   
 End Sub
-```
+````
 
 [1]: /img/testing-framework/using-mbunit/fig1.png
diff --git a/docs/testing-framework/using-nunit.md b/docs/testing-framework/using-nunit.md
index de45d0e2..9cfb4798 100644
--- a/docs/testing-framework/using-nunit.md
+++ b/docs/testing-framework/using-nunit.md
@@ -1,12 +1,12 @@
 ---
 title: Using NUnit
 page_title: Using NUnit
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Test Studio Testing Framework with NUnit test"
 previous_url: /user-guide/getting-started/using-nunit.aspx, /user-guide/getting-started/using-nunit
 position: 1
 ---
 
-#Using NUnit#
+# Using NUnit
 
 Telerik Testing Framework comes with built-in support for NUnit 2.5 and higher. The latest release of NUnit can be downloaded <a href="https://launchpad.net/nunitv2" target="_blank">here</a>.
 
@@ -18,21 +18,21 @@ Telerik Automation Infrastructure comes with the following features to facilitat
 
 * Unifies the log content. Any logging from Telerik automation using its Log object will also be logged to NUnit's output including logging from JavaScript. For example:
 
-```C#
+````C#
 [Test]
 public void NUnitLog()
 {
      Log.WriteLine("Hi from WebAii");
 }
-```
-```VB
+````
+````VB
 <Test()> _
 Public Sub NUnitLog()
   
      Log.WriteLine("Hi from WebAii")
   
 End Sub
-```
+````
 
 NUnit log:
 
@@ -42,7 +42,7 @@ NUnit log:
 
 * When installing Telerik Testing Framework, a new fully commented NUnit item template will be added to your list of available templates. This will enable you to start using Telerik Testing Framework by simply selecting it from the Add->New Item tool menu (or context menu) available to your VS project. You are provided with both a C# and a VB.NET template.
 
-##Getting Started Using NUnit##
+## Getting Started Using NUnit
 
 In this section we will walk you through the steps to get you started using Telerik Testing Framework with NUnit.
 
@@ -76,7 +76,7 @@ In this section we will walk you through the steps to get you started using Tele
 
 * Start writing your automated Telerik unit tests.
 
-##Telerik's NUnit Template##
+## Telerik's NUnit Template
 
 Telerik NUnit tests inherit from a base test class called **BaseTest** that lives in the **ArtOfTest.WebAii.TestTemplate** namespace. The base class, in addition to providing the integration benefits described above, provides:
 
@@ -120,17 +120,17 @@ Telerik NUnit tests inherit from a base test class called **BaseTest** that live
 
 * The base class also offers different options that you might want to choose from depending on the scenarios and your testing environment. The Telerik template installed on your machines, by default uses the following initialization:
 
-```C#
+````C#
 Initialize(new TestContextWriteLine(Console.Out.WriteLine));
-```
-```VB
+````
+````VB
 Initialize(New TestContextWriteLine(AddressOf Console.Out.WriteLine))
-```
+````
 
 The above initialization passes in a delegate to the WriteLine method of NUnit so that you can unify the logging across both frameworks. If that initialization does not work for you, you can choose to pass in different parameters or choose to do your own custom setup of the framework. For example, if you want to override some of the settings from the .config file in one or two of your test cases, you can simply do the following:
 
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -142,8 +142,8 @@ settings.DefaultBrowser = BrowserType.FireFox;
   
 // Now call Initialize again with your updated settings object
 Initialize(settings, new TestContextWriteLine(Console.Out.WriteLine));
-```
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -155,25 +155,25 @@ mySettings.DefaultBrowser = BrowserType.FireFox
   
 ' Now call Initialize again with your updated settings object
 Initialize(mySettings, New TestContextWriteLine(AddressOf Console.Out.WriteLine))
-```
+````
 
 Also if you don't really want to unify the logging and would prefer the framework to perform its own logging in a custom folder, you can simply use the following overload:
 
 
-```C#
+````C#
 Initialize(myCustomLocation);
-```
-```VB
+````
+````VB
 Initialize(myCustomLocation)
-```
+````
 
 For more information on Telerik Testing Framework's settings & configuration please refer to the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class" target="_blank">Settings and Configuration</a> topic.
 
-##Starting Automation##
+## Starting Automation
 
 Now that we have an understanding of the template, we can start automating right away. Pick your test method and start writing your automation test code for your unit test. For example:
 
-```C#
+````C#
 [Test]
 [Description("My simple demo")]
 public void SimpleTest()
@@ -187,8 +187,8 @@ public void SimpleTest()
      // verify the title is actually Google.
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText);
 }
-```
-```VB
+````
+````VB
 <Test(), _
 Description("My simple demo")> _
 Public Sub SimpleTest()
@@ -203,7 +203,7 @@ Public Sub SimpleTest()
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText)
   
 End Sub
-```
+````
 
 [1]: /img/testing-framework/using-nunit/fig1.png
 [2]: /img/testing-framework/using-nunit/fig2.png
diff --git a/docs/testing-framework/using-vs-team-test.md b/docs/testing-framework/using-vs-team-test.md
index aa958520..ffea0974 100644
--- a/docs/testing-framework/using-vs-team-test.md
+++ b/docs/testing-framework/using-vs-team-test.md
@@ -1,11 +1,11 @@
 ---
 title: Using VS Team Test
 page_title: Using VS Team Test
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Test Studio Testing Framework with VS Team test"
 position: 1
 ---
 
-#Using Visual Studio Team Test#
+# Using Visual Studio Team Test
 
 Telerik Testing Framework comes with built-in support for Visual Studio Team Test and its unit testing framework. Telerik Testing Framework can be used with or without Visual Studio, but if you are already using Visual Studio Team Test in your development environment, you can easily and quickly integrate Telerik Testing Framework as part of that environment.
  
@@ -15,7 +15,7 @@ Telerik Automation Infrastructure comes with the following features to facilitat
 
 * Unifies both the logging location and the log content. Any logging from Telerik automation using its Log object will also be logged to the Visual Studio log location and to the actual Visual Studio log content of that particular test. This includes logging from JavaScipt.
 
-```C#
+````C#
 [TestMethod]
 public void DLog()
 {
@@ -25,8 +25,8 @@ public void DLog()
      Log.WriteLine("Hello from Telerik");
   
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub DLog()
   
@@ -36,15 +36,15 @@ Public Sub DLog()
      Log.WriteLine("Hello from Telerik")
   
 End Sub
-```
+````
 
-##Visual Studio log##
+## Visual Studio log
 
-###VS 2012 / 2013###
+### VS 2012 / 2013
 
 ![VS 2012/2013][1]
 
-###VS 2010###
+### VS 2010
 
 ![VS 2010][2]
 
@@ -52,7 +52,7 @@ End Sub
 
 * When installing Telerik Testing Framework, a new fully commented Visual Studio item template will be added to your list of available templates. This will enable you to start using Telerik Testing Framework by simply selecting it from the 'Add->New Item' tool menu (or context menu) available to your VS project. You are provided with both a C# and a VB.NET template.
 
-##Getting Started Using Visual Studio Team Test##
+## Getting Started Using Visual Studio Team Test
 
 In this section we will walk you through the steps to get you started using Telerik Framework inside a Visual Studio Team Test environment.
 
@@ -76,7 +76,7 @@ In this section we will walk you through the steps to get you started using Tele
 
 * Start writing your automated Telerik unit test just like any other Visual Studio unit test. You can view, manage, and execute your Telerik unit tests just like any other Visual Studio unit tests.
 
-##Telerik's Visual Studio Team Test Template##
+## Telerik's Visual Studio Team Test Template
 
 The Telerik Framework template is very similar to Visual Studio's unit test template with the addition of Telerik's integration points to initialize and clean up Telerik's infrastructure. Telerik Visual Studio tests also inherit from a base test class called **BaseTest** that lives in the **ArtOfTest.WebAii.TestTemplate** namespace. The base class, in addition to providing the integration benefits described above, provides:
 
diff --git a/docs/testing-framework/using-xunit.md b/docs/testing-framework/using-xunit.md
index 4854beb0..3a0e9378 100644
--- a/docs/testing-framework/using-xunit.md
+++ b/docs/testing-framework/using-xunit.md
@@ -1,11 +1,11 @@
 ---
 title: Using xUnit
 page_title: Using xUnit
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Test Studio Testing Framework with xUnit test"
 position: 1
 ---
 
-#Using xUnit#
+# Using xUnit
 
 Telerik Testing Framework comes with built-in support for xUnit.net 1.8 and higher. The latest release of xUnit can be downloaded <a href="http://xunit.codeplex.com/releases/view/62840" target="_blank">here</a>.
  
@@ -17,7 +17,7 @@ Telerik Automation Infrastructure comes with the following features to facilitat
 
 * When installing Telerik Testing Framework, a new fully commented xUnit.net item template will be added to your list of available templates. This will enable you to start using Telerik by simply selecting it from the Add->New Item tool menu (or context menu) available to your VS project. You are provided with both a C# and a VB.NET template.
 
-##Getting Started Using xUnit.net##
+## Getting Started Using xUnit.net
 
 In this section we will walk you through the steps to get you started using Telerik Testing Framework with xUnit.net.
 
@@ -41,7 +41,7 @@ In this section we will walk you through the steps to get you started using Tele
 
 * Start writing your automated Telerik Testing Framework unit tests.
 
-##Telerik's xUnit Template##
+## Telerik's xUnit Template
 
 Telerik xUnit.net tests inherit from a base test class called **BaseTest** that lives in the **ArtOfTest.WebAii.TestTemplate** namespace. The base class, in addition to providing the integration benefits described above, provides:
 
@@ -83,16 +83,16 @@ Telerik xUnit.net tests inherit from a base test class called **BaseTest** that
 
 * The base class also offers different options that you might want to choose from depending on the scenarios and your testing environment. The Telerik template installed on your machines, by default uses the following initialization:
 
-```C#
+````C#
 Initialize(false);
-```
-```VB
+````
+````VB
 Initialize(False)
-```
+````
 
 The above initialization initializes the Telerik Testing Framework but does not enable the RecycleBrowser feature. Because xUnit.net does not have the concept of a test fixture setup/teardown the RecycleBrowser feature cannot be used. If that initialization does not work for you, you can choose to pass in different parameters or choose to do your own custom setup of the framework. For example, if you want to override some of the settings from the .config file in one or two of your test cases, you can simply do the following:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -104,8 +104,8 @@ settings.DefaultBrowser = BrowserType.FireFox;
   
 // Now call Initialize with your updated settings object
 Initialize(settings);
-```
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -117,14 +117,14 @@ mySettings.DefaultBrowser = BrowserType.FireFox
   
 ' Now call Initialize with your updated settings object
 Initialize(mySettings)
-```
+````
 
 For more information on Telerik Testing Framework's settings & configuration please refer to the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class" target="_blank">Settings and Configuration</a> topic.
 
-##Starting Automation##
+## Starting Automation
 
 
-```C#
+````C#
 [Test]
 [Description("My simple demo")]
 public void SimpleTest()
@@ -138,8 +138,8 @@ public void SimpleTest()
      // verify the title is actually Google.
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText);
 }
-```
-```VB
+````
+````VB
 <Test(), _
 Description("My simple demo")> _
 Public Sub SimpleTest()
@@ -154,6 +154,6 @@ Public Sub SimpleTest()
      Assert.AreEqual("Google", ActiveBrowser.Find.ByTagIndex("title", 0).InnerText)
   
 End Sub
-```
+````
 
 [1]: /img/testing-framework/using-xunit/fig1.png
\ No newline at end of file
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
index aea43276..c7409ee6 100644
--- 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
@@ -4,7 +4,7 @@ page_title: Asp.NET Host Server
 description: "Test Studio Testing Framework support for Asp.NET Host Server"
 position: 1
 ---
-#Using Asp.Net In-Process Host Server#
+# Using Asp.Net In-Process Host Server
 
 Many of our customers have asked for a way to execute tests without the need for a browser. They wanted a light-weight, fast and agile execution that fits within their Continuous Integration Builds and works easily with 'CruiseControl.Net' or 'Visual Studio Team Foundation Server.' We enabled these scenarios with two areas of support:
 
@@ -18,11 +18,11 @@ 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:
 
-```ASP
+````ASP
 <%@ Page Language="C#" %>
  
 <!DOCTYPE htmlPUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
@@ -90,30 +90,30 @@ With all these in mind, let's look at an example that illustrates how we can ena
     </form>
 </body>
 </html>
-```
+````
 
 
 You can run this page using the Asp.Net InProc server by first setting the default browser to 'AspNetHost' and setting the physical location of the web application. For example, you can override these settings in your test initialization or set them in your .config file:
 
-```C#
+````C#
 // Set the default browser to be AspNetHost
 settings.DefaultBrowser = BrowserType.AspNetHost;
  
 // Set the location of the Asp.Net App
 settings.WebAppPhysicalPath = @"C:\MyAspNetApp\";
-```
-```VB
+````
+````VB
 ' Set the default browser to be AspNetHost
 mysettings.DefaultBrowser = BrowserType.AspNetHost
  
 ' Set the location of the Asp.Net App
 mysettings.WebAppPhysicalPath = System.IO.Path.Combine(Globals.PATH_TO_PAGES, "AspNetApp")
-```
+````
 
 Next you can perform your automation in the same manner as you would for any other browser. For example:
 
 
-```C#
+````C#
 // Will initialize a new AspNetApplication object.
 Manager.LaunchNewBrowser();
  
@@ -175,8 +175,8 @@ Assert.IsTrue(label.InnerText.Contains(DateTime.Today.ToShortDateString()));
 Actions.Click(Find.ById("treeView1t1"));
 label.Refresh();
 Assert.IsTrue(label.InnerText.Contains("Node2"));
-```
-```VB
+````
+````VB
 
 ' Will initialize a new AspNetApplication object.
 Manager.LaunchNewBrowser()
@@ -234,9 +234,9 @@ Assert.IsTrue(label.InnerText.Contains(DateTime.Today.ToShortDateString))
 Actions.Click(Find.ById("treeView1t1"))
 label.Refresh()
 Assert.IsTrue(label.InnerText.Contains("Node2"))
-```
+````
 
 
-##Debugging Page Requests##
+## Debugging Page Requests
 
 Given that these page requests are running in-process without any UI showing, it is sometimes difficult to see what exactly is being rendered. To make debugging scenarios easier, Telerik Testing Framework enables the option of rendering the responses from the Asp.Net In-Process server into an IE browser instance. To enable this debug mode, simply set the **Settings.EnableUILessRequestViewing** to True and an IE instance will launch and redirect a copy of all responses from the Asp.Net host to that instance so you can visually inspect the UI of the pages.
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/attribute-extensions.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/attribute-extensions.md
index d235430e..9014a34a 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/attribute-extensions.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/attribute-extensions.md
@@ -4,11 +4,11 @@ page_title: Attribute Extensions
 description: "Test Studio Testing Framework Attribute Extensions."
 position: 1
 ---
-#Unit Testing Attribute Extensions#
+# Unit Testing Attribute Extensions
 
 > <span class="redcolor">IMPORTANT:</span> If you want to use the Attribute Extensions with NUnit, please make sure to setup NUnit extensions as described in the <a href="/testing-framework/using-nunit" target="_blank">Using NUnit</a> topic. Visual Studio Team Test does not require any additional steps.
 
-##What Are These Extensions?##
+## What Are These Extensions?
 
 Unit testing attribute extensions is one of the coolest features of the framework. They came about as we were reviewing automated unit test code for some of our customers and our own unit testing code for the framework. The things that became apparent after reviewing these automated tests were:
 
@@ -30,14 +30,14 @@ Attribute Extensions are test fixture attributes that can be used to decorate un
 
 * **DialogAttribute**: You use this attribute on test methods to define the Win32 pop-up dialogs you want monitored and define how you want them handled. If you have common dialogs that pop-up across your test methods, you can simply set this attribute on the test class and the dialog will be monitored and handled for all test methods contained in that test class.
 
-##Examples##
+## Examples
 
-###FindParamAttribute###
+### FindParamAttribute
 
 Let's start by taking few examples for FindParamAttribute. Assume we have an input textbox that we commonly access through out all the test methods in our Foo test class. Well, we can share this methods across all the test methods in 'foo' by setting that FindParam using FindParamAttribute on the test class like this:
 
 
-```C#
+````C#
 [TestClass]
 [FindParam("InputTxtbx", FindType.TagIndex, "input:0")]
 class Foo : BaseTest
@@ -62,8 +62,8 @@ class Foo : BaseTest
          Actions.SetText(Find.Elements["InputTxtbx"], "test2");
      }
 }
-```
-```VB
+````
+````VB
 <TestClass(), _
 FindParam("InputTxtbx", FindType.TagIndex, "input:0")> _
 Public Class Foo
@@ -94,11 +94,11 @@ Public Class Foo
     End Sub
  
 End Class
-```
+````
 
 You can use 1-N FindParam attributes on your test class or test method. If you have elements that are shared across more than one test method, set these FindParam's on the test class, else simply set them on the test method. For example:
 
-```C#
+````C#
 [TestClass]
 [FindParam("InputTxtbx", FindType.TagIndex, "input:0")]
 class Foo : BaseTest
@@ -134,8 +134,8 @@ class Foo : BaseTest
          // here. Calling Find.Elements["CheckBx"], will throw an exception.
      }
 }
-```
-```VB
+````
+````VB
 <TestClass(), _
 FindParam("InputTxtbx", FindType.TagIndex, "input:0")> _
 Public Class Foo
@@ -174,15 +174,15 @@ Public Class Foo
     End Sub
  
 End Class
-```
+````
 
-###FindParamAttributes and TestRegions###
+### FindParamAttributes and TestRegions
 
 FindParamAttributes can also be used with TestRegions when they are defined within an application. In this scenario, the FindParam needs to reflect an element search within a specific TestRegion. To tie a FindParamAttribute with a TestRegion, simply set the TestRegionId property of that FindParam on your test method or test class. Here is an example:
 
 FindParamAttributes can also be used with TestRegions when they are defined within an application. In this scenario, the FindParam needs to reflect an element search within a specific TestRegion. To tie a FindParamAttribute with a TestRegion, simply set the TestRegionId property of that FindParam on your test method or test class. Here is an example:
 
-```C#
+````C#
 
 [TestMethod]
 [Description("Illustrate how to use FindParamAttributes with TestRegion's")]
@@ -209,8 +209,8 @@ public void UsingFindParamAttributeWithTestRegion's()
      // Note: You can also use the FindParamAttribute(fileName) and scope all
      // the elements contained in file to a specific testregion.
 }
-```
-```VB
+````
+````VB
 <TestMethod(), _
 Description("Illustrate how to use FindParamAttributes with TestRegion's"), _
 FindParam("progtbl", FindType.TagIndex, "table:1"), _
@@ -234,13 +234,13 @@ Public Sub UsingFindParamAttributeWithTestRegions()
      ' the elements contained in the file to a specific testregion.
  
 End Sub
-```
+````
 
-###DialogAttribute###
+### DialogAttribute
 
 Dialog attribute is used similar to the FindParamAttribute but instead of defining how an element should be found, it defines how a dialog should be handled in addition to the dialog types to handle. Again these attributes can be shared across test methods by setting them on a test class or can be directly set on the test method that will cause the dialog to pop up. Here are few examples of some of the common dialogs:
 
-```C#
+````C#
 // ALERTS
 [TestMethod]
 [Dialog(DialogButton.OK)] // handle any alert dialogs in this test method
@@ -284,8 +284,8 @@ public void LogonDialogWithAttributes()
      // Navigate to a page that needs a logon
      ActiveBrowser.NavigateTo(http://www.test.com/pageneedinglogon.aspx);
 }
-```
-```VB
+````
+````VB
 
 ' Alerts
 <TestMethod(), _
@@ -319,7 +319,7 @@ Dialog("<username>", "<password>", DialogButton.OK)> _
 Public Sub LogonDialogWithAttributes()
      ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>")
 End Sub
-```
+````
 
 
 **Note:** All examples shown above should work with NUnit 2.4 and higher and Visual Studio Team Test. In the samples above we simply used Visual Studio Team Test.
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/frames-support.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/frames-support.md
index 5cd5cc7d..57907cdf 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/frames-support.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/frames-support.md
@@ -4,7 +4,7 @@ page_title: Frames Support
 description: "Test Studio Testing Framework support for iFrames. Access elements in iFrames from a coded step. Coded test to interact with elements in iFrames. "
 position: 1
 ---
-#Frames Support#
+# Frames Support
 
 Telerik Testing Framework understands what Frames and IFrames are and includes built-in support to work with them. It automatically scans the webpage and locates all of the frames it contains and then adds them to the FramesCollection property of the Browser object.
  
@@ -15,37 +15,47 @@ Frames are treated just like another browser instance. In order to work with the
 	<th>Method</th><th>Parameter</th><th>Description</th>
 </tr>
 <tr>
-	<td>**Browser.Frames[string frameName]**</td>
+	<td>
+
+**Browser.Frames[string frameName]**</td>
 	<td>Takes a string that specifies the name of the frame. e.g. <frame src="t1.html" name="t1_frame"></td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames[int frameIndex]**</td>
+	<td>
+
+**Browser.Frames[int frameIndex]**</td>
 	<td>Takes an integer specifying which frame to get from the frame collection. Useful if you know ahead of time you want the second frame. e.g. ActiveBrowser.Frames[1]</td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Throws an error if the index value is out of range.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames[FrameInfo frameInfo]**</td>
+	<td>
+
+**Browser.Frames[FrameInfo frameInfo]**</td>
 	<td>Takes a FrameInfo object that specifies the properties of the frame you want. Perhaps you want to locate a frame by its src property.</td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found.</td>
 </tr>
 <tr>
-	<td>**Browser.Frames.ById(string frameId)**</td>
+	<td>
+
+**Browser.Frames.ById(string frameId)**</td>
 	<td>Takes a string that specifies the ID of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
 </tr>
 <tr>
-	<td>**Browser.Frames.BySrc(string src)**</td>
+	<td>
+
+**Browser.Frames.BySrc(string src)**</td>
 	<td>Takes a string that specifies the source of the frame. Prefix with a tilde (~) to indicate a partial match.</td>
 	<td>This method searches for a frame that matches the specified string and then returns a Browser object representing that frame that you can use to interact with the frame. Returns null if no matching frame can be found. </td>
 </tr>
-<table>
+</table>
 
 Telerik Testing Framework allows users to access frames and perform automation against these frames just like any other page. A frame is simply a mini browser window inside your web page that can host its own HTML document. That is why frames are represented as Browser objects and are accessible using the **Frames[]** collection of the browser object that contains the 'iframe' or 'frameset' elements.
  
 Let's take an example that demonstrates this support. Assuming we have the following simple web page:
 
-```HTML
+````HTML
 <HTML>
 <HEAD><TITLE>THE I HATE FRAMES PAGE</TITLE></HEAD>
 <FRAMESET COLS="33%,33%">
@@ -53,11 +63,11 @@ Let's take an example that demonstrates this support. Assuming we have the follo
     <FRAMESRC="..\BrowserActions.htm" id="T2_Frame">
 </FRAMESET>
 </HTML>
-```
+````
 
 To access the 't1.html' frame elements and perform actions against it, first I need to navigate to the page, then I need to access the frame that contains that page from the 'Frames[]' collection as follows:
 
-```C#
+````C#
 // Launch an instance of the browser
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, true);
    
@@ -80,8 +90,8 @@ t1_frame.Actions.Click(toggleOn);
    
 // Click the toggleoff button
 t2_frame.Actions.Click(toggleOff);
-```
-```VB
+````
+````VB
 ' Launch an instance of the browser
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, True)
  
@@ -104,10 +114,11 @@ t1_frame.Actions.Click(toggleOn)
  
 ' Click the toggleoff button
 t2_frame.Actions.Click(toggleOff)
-```
+````
 
 At this point, the 't1_frame' object is just like any other Browser object. You can use the Find.Byxxx/Actions objects to find elements/execute actions in the document or execute any of the browser actions like 'NavigateTo' or 'Refresh()', 'GoBack()', etc.
  
-###Notes about Frames support:###
+
+### Notes about Frames support:
 
 The Frames collection supports two methods that can be used to easily wait on all frames to be ready or to refresh all the DOM trees within these frames. The methods are : 'ActiveBrowser.Frames.RefreshAllDomTrees()' & 'ActiveBrowser.Frames.WaitAllUntilReady()'. You can use these methods if you are doing actions that affect all frames in the page and you want to wait for these actions across all frames all at once
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
index 7ff8142e..8783237b 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/JavaScript-dialogs.md
@@ -14,7 +14,7 @@ __Telerik Testing Framework__ includes native support for dialog handling (under
 ><br>
 > _using ArtOfTest.WebAii.Win32.Dialogs;_
 
-```C#
+````C#
 
 // Define the Alert dialog and how it needs to be handled - choose between Ok and Cancel
 var alertDlg = new ArtOfTest.WebAii.Win32.Dialogs.AlertDialog(Manager.ActiveBrowser, DialogButton.CANCEL);
@@ -50,8 +50,8 @@ Manager.DialogMonitor.Stop();
 // especially if the elements to use are related to the action confirmed with the dialog handling
 //Manager.ActiveBrowser.RefreshDomTree();
 
-```
-```VB
+````
+````VB
 ' Define the Alert dialog
 IDialog alertDlg = New ArtOfTest.WebAii.Win32.Dialogs.AlertDialog(Manager.ActiveBrowser, DialogButton.OK)
 
@@ -77,7 +77,7 @@ Actions.InvokeScript("InvokeAlert()")
 Manager.DialogMonitor.RemoveDialog(alertDlg)
 Manager.DialogMonitor.Stop()
 
-```
+````
 
 
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/confirm-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/confirm-dialogs.md
index f13415b7..887ba6c6 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/confirm-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/confirm-dialogs.md
@@ -14,7 +14,7 @@ __Telerik Testing Framework__ includes native support for dialog handling (under
 ><br>
 > _using ArtOfTest.WebAii.Win32.Dialogs;_
 
-```C#
+````C#
 // Define the Confirm dialog and how it needs to be handled - choose between Ok and Cancel
 var confirmDlg = new ArtOfTest.WebAii.Win32.Dialogs.ConfirmDialog(Manager.ActiveBrowser, DialogButton.OK);
 
@@ -49,8 +49,8 @@ Manager.DialogMonitor.Stop();
 // especially if the elements to use are related to the action confirmed with the dialog handling
 //Manager.ActiveBrowser.RefreshDomTree();
 
-```
-```VB
+````
+````VB
 ' Define the Confirm dialog
 IDialog confirmDlg = New ArtOfTest.WebAii.Win32.Dialogs.ConfirmDialog(Manager.ActiveBrowser, DialogButton.OK)
 
@@ -76,4 +76,4 @@ Actions.InvokeScript("InvokeConfirm()")
 Manager.DialogMonitor.RemoveDialog(confirmDlg)
 Manager.DialogMonitor.Stop()
 
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
index 77c6eace..3233e1ce 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-dialogs.md
@@ -4,11 +4,12 @@ page_title: Handle Custom Dialogs
 description: "Test Studio Testing Framework Custom Dialog handling. Handle a dialog in custom manner in a coded step in Test Studio. Coded test to handle dialogs in Test Studio using custom logic."
 position: 10
 ---
-#Custom Dialog Handler#
+
+# Custom Dialog Handler
 
 If for whatever reason you decide that you don't like the way the dialog is being handled or want to perform extra tasks before handling the dialog, you can simply craft your own dialog handling code and then ask the dialog to call your code instead of its dialog handling code. Here is an example:
 
-```C#
+````C#
 public void DoCustomDialogHandlingForBuiltInDialogs()
  {
     AlertDialog myAlertDialog = new AlertDialog(ActiveBrowser, DialogButton.OK);
@@ -46,8 +47,8 @@ public bool MyCustomAlertHandler(IDialog dialog)
          return false;
     }
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub DoCustomDialogHandlingForBuiltInDialogs()
   
@@ -80,7 +81,7 @@ Public Sub MyCustomAlertHandler(ByVal dialog As ArtOfTest.WebAii.Win32.Dialogs.I
     End Try
   
 End Sub
-```
+````
 
 
 > **To compile the above code include the following using:**
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
index 795504d5..9bd86d61 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/custom-handlers.md
@@ -4,31 +4,31 @@ page_title: Custom Handlers
 description: "Test Studio Testing Framework Custom Dialog handling. Handle a custom dialog in a coded step in Test Studio. Coded test to handle custom (non-common) dialogs in Test Studio."
 position: 11
 ---
-#Creating Custom Dialog Handlers#
+# Creating Custom Dialog Handlers
 
 So far we've addressed the common dialogs that browsers popup and how the built-in support can be used to handle them. So what do we do if we have a different dialog that we need to handle? Telerik Testing Framework provides a **GenericDialog class** (which does all the work for you of implementing a custom dialog handler), a **BaseDialog class** (which does most of the work of implementing a custom dialog handler), and the IDialog interface for when you need to roll your own custom dialog handler from scratch. Once implemented you can add your custom dialog handler to the **DialogMonitor** and have all your other dialogs handled just like the rest of the built-in dialogs.
 
-##Using the GenericDialog Class##
+## Using the GenericDialog Class
 
 Using the GenericDialog class you can create your own custom dialog handler that can handle most any simple standard Win32 dialog. Here's an example of how to implement a handler for Internet Explorers Security Warning dialog:
 
-```C#
+````C#
 GenericDialog SecurityWarningDialog = new GenericDialog(ActiveBrowser, "Security Warning", false, 1);  // Click on the Yes button
 Manager.DialogMonitor.AddDialog(SecurityWarningDialog);
-```
-```VB
+````
+````VB
 Dim SecurityWarningDialog As GenericDialog = New GenericDialog(Me.ActiveBrowser, "Security Warning", False, 1)  ' Click on the Yes button
 SecurityWarningDialog GenericDialog = GenericDialog(.ActiveBrowser, , , 1) 
 Manager.DialogMonitor.AddDialog(SecurityWarningDialog)
-```
+````
 
-##Using the BaseDialog Class##
+## Using the BaseDialog Class
 
 By using the BaseDialog class as your base class to derive your custom dialog handler you only need to override the IsDialogActive() and Handle() functions. You may also provide your own constructor to validate the button type that will dismiss the dialog and/or accept a Desktop object (which you will need if you need to call Mouse.Click or Keyboard.SendString). Reference to System.Drawing.dll have to be added to the project as well.
 
 The below example is a complete custom dialog handler that handles the "Security Alert" dialog displayed by Internet Explorer:
 
-```C#
+````C#
 using System;
 using ArtOfTest.WebAii.Core;
 using ArtOfTest.Common.Win32;
@@ -141,8 +141,8 @@ namespace WebTesting
         #endregion
     }
 }
-```
-```VB
+````
+````VB
 Imports ArtOfTest.WebAii.Core
 Imports ArtOfTest.Common.Win32
 Imports ArtOfTest.WebAii.Win32.Dialogs
@@ -239,22 +239,22 @@ Namespace WebTesting
 		#End Region
 	End Class
 End Namespace
-```
+````
 
 Once you have implemented your new custom dialog handler it requires just one line of code to add it to the DialogMonitor:
 
-```C#
+````C#
 Manager.DialogMonitor.AddDialog(new SecurityAlertDialog(ActiveBrowser, DialogButton.YES, Manager.Desktop));
-```
-```VB
+````
+````VB
 Manager.DialogMonitor.AddDialog(New SecurityAlertDialog(Me.ActiveBrowser, DialogButton.YES, Me.Manager.Desktop))
-```
+````
 
-##Implementing a Custom Dialog Handler with IDialog##
+## Implementing a Custom Dialog Handler with IDialog
 
 When the GenericDialog and the BaseDialog classes don't provide the functionality you need, you can roll your own complete custom dialog handling by implementing the <a href="http://docs.telerik.com/teststudioapi/html/T_ArtOfTest_WebAii_Win32_Dialogs_IDialog.htm" target="_blank">IDialog</a> interface. An example of when this is necessary is when creating handlers for most FireFox dialogs. See How to handle FireFox dialogs for an example of a FireFox dialog handler implemented using the IDialog interface. A reference to UIAutomationClient.dll has to be added to the project and a using to System.Windows.Automation namespace would be required in the code. The IDialog interface has the following methods and properties that you must implement:
 
-```C#
+````C#
 /// <summary>
 /// Interface to implement for dialogs to be monitored and handled by the DialogMonitor object.
 /// </summary>
@@ -318,8 +318,8 @@ public interface IDialog
      /// </summary>
 	 bool MatchesUIAutomationElement(AutomationElement element);
 }
-```
-```VB
+````
+````VB
 ''' <summary>
 ''' The dialogs current state. This property is Managed by the dialog
 ''' monitor. Implementors should simply provide a private field to
@@ -428,7 +428,7 @@ End Sub
 ''' </summary>
 Private Function MatchesUIAutomationElement(element As AutomationElement) As Boolean
 End Function
-```
+````
 
 After implementing this interface and creating an instance of your class in your test code, you can add the instance to the DialogMonitor to begin handling of your special dialog. See Handling FireFox dialogs for an example of implementing the IDialog interface. The interface is pretty straight forward but here is how the DialogMonitor uses it:
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
index 9f3ec5c6..9f644220 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-download-dialog.md
@@ -5,11 +5,12 @@ description: "Handle a download dialog in a coded step in Test Studio. Coded tes
 previous_url: /user-guide/write-tests-in-code/advanced-topics/handling-html-popups-and-dialogs/built-in-dialog-handlers/handling-filedownload-dialog.aspx, /user-guide/write-tests-in-code/advanced-topics/handling-html-popups-and-dialogs/built-in-dialog-handlers/handling-filedownload-dialog
 position: 7
 ---
-#Handling FileDownload Dialogs#
+
+# Handling FileDownload Dialogs
 
 With FileDownload, you need to pass in the full path to the download location and how the dialog should be handled. 
 
-```C#
+````C#
 DownloadDialogsHandler dialog = new DownloadDialogsHandler (Manager.ActiveBrowser, DialogButton.SAVE, @"D:\text.txt", Manager.Desktop); 
  
 Manager.DialogMonitor.Start();
@@ -19,8 +20,8 @@ Manager.DialogMonitor.Start();
 Element.Click(false); 
  
 dialog.WaitUntilHandled(30000);
-```
-```VB
+````
+````VB
 Dim dialog As New DownloadDialogsHandler(Manager.ActiveBrowser, DialogButton.SAVE, "D:\text.txt", Manager.Desktop)
 
 Manager.DialogMonitor.Start()
@@ -30,7 +31,7 @@ Manager.DialogMonitor.Start()
 Element.Click(False)
 
 dialog.WaitUntilHandled(30000)
-```
+````
 
 
 > **To compile the above code include the following using:**
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
index 0892c468..f0d89030 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/file-upload-dialog.md
@@ -8,7 +8,7 @@ position: 6
 
 With FileUpload, you need to pass in the full path to the file to upload and how the dialog should be handled. The options for FileUpload are: DialogButton.OPEN, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add a FileUpload dialog to be monitored.
 Manager.DialogMonitor.AddDialog(new FileUploadDialog(ActiveBrowser, @"C:\EmptyTextFile.txt", DialogButton.OPEN));
   
@@ -23,8 +23,8 @@ Manager.DialogMonitor.Start();
 Pages.YourSite.YourButton.Click();
   
 // Dialog should be automatically handled
-```
-```VB
+````
+````VB
 ' Add a FileUpload dialog to be monitored.
 Manager.DialogMonitor.AddDialog(New FileUploadDialog(ActiveBrowser, Path.Combine(Globals.PATH_TO_PAGES, "..\SupportFiles\EmptyTextFile.txt"), DialogButton.OPEN))
   
@@ -34,13 +34,13 @@ Manager.DialogMonitor.Start()
   
 ' Cause the upload Dialog to pop-up
 Pages.YourSite.YourButton.Click()
-```
+````
 
 ## Multiple Files Upload
 
 There are scenarios where multiple files needs to be uploaded. Below you could find a sample code how to obtain that with the Testing Framework. The code will loop through a set of files and will upload each after the previous. The sample is built against a <a href="https://www.w3schools.com/jsref/tryit.asp?filename=tryjsref_fileupload_multiple" target="_blank">public accessible webpage</a> and to give a try to that example you have to first navigate to that page. 
 
-```C#
+````C#
 // place small pictures with names file1.png and file2.png in c:\temp folder to have the sample working without modification
 string path = @"C:\temp\" ;
 string[] fileNames = new string[] { "file1.png", "file2.png" } ;
@@ -84,7 +84,7 @@ for (int i = 0; i < fileNames.Length; i++ )
     ActiveBrowser.Refresh();
 }
 
-```
+````
 
 > **Note** To compile the above code include the following using:
 >
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md
deleted file mode 100644
index fb79783c..00000000
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs.md
+++ /dev/null
@@ -1,420 +0,0 @@
----
-title: Firefox Dialogs
-page_title: Firefox Dialogs
-description: "Test Studio Testing Framework FF dialogs - obsolete"
-position: 1
-publish: false
----
-#How to Handle Firefox Dialogs#
-
-Firefox dialogs require special attention because some of them are not standard Win32 dialogs, for example Firefox's download manager dialog. As a result the usual method for handing dialogs does not work with Firefox dialogs. Here is what the download manager dialog looks like:
-
-<table id="no-table">
-	<tr>
-		<td>![Firefox download manager dialog window][1] <br><br>**Firefox download manager dialog window**</td>
-		<td>![Firefox download manager dialog window after download completes][2] <br><br>**Firefox download manager dialog window after download completes**</td>
-	</tr>
-<table>
-
-Using Microsoft's Spy++ tool the first thing we discover about this dialog is that the class name is **MozillaUIWindowClass** instead of the standard dialog class name of #**32770**. As a result this dialog will not be included in the WindowCollection list that is passed in to the IsDialogActive function. This is because DialogMonitor filters the desktop windows on the class name #**32770**. This fact alone necessitates rolling our own custom dialog handler using the IDialog interface to overcome this problem.
- 
-The other thing we discover about this dialog is that the Clear List button and the links are not Win32 accessible. We'll have to come up with different methods of accessing them if needed. Fortunately in this case all we want to do is close the dialog when the download is finished.
- 
-Let's start implementing our dialog handler. First we'll need some local class variables and property accessors:
-
-```C#
-using System;
-using System.Threading;
- 
-using ArtOfTest.WebAii.Win32;
-using ArtOfTest.WebAii.Win32.Dialogs;
- 
-namespace WebTesting
-{
-     public class FFDownloadsDialog : IDialog
-     {
-        #region Members
-        /// <summary>
-        /// Private storage for the number of times this dialog has been successfully handled.
-        /// </summary>
-        private int _handleCount;
-        /// <summary>
-        /// The number of times in a row the dialog has been found. This overcomes the problem
-        /// where the dialog is first put up and momentarily displays "Downloads" and is
-        /// quickly changed to "16% complete 1 file � Downloads".
-        /// </summary>
-        private int _foundCount = 0;
-        /// <summary>
-        /// The download window found.
-        /// </summary>
-        private Window _window;
-        /// <summary>
-        /// Stores the custom handler delegate, if set by the test code.
-        /// </summary>
-        private DialogHandlerDelegate _handlerDelegate;
-        /// <summary>
-        /// Stores the current handled state.
-        /// </summary>
-        private DialogCurrentState _currentState = DialogCurrentState.NotActive;
-        /// <summary>
-        /// Semaphore used by the WaitUntilHandled function.
-        /// </summary>
-        private AutoResetEvent _autoEvent = new AutoResetEvent(false);
-        #endregion
- 
-        #region Private Constants
-        /// <summary>
-        /// The title of the dialog we want handled.
-        /// </summary>
-        private const string DIALOG_TITLE = "Downloads";
-        #endregion
- 
-        #region Properties
-        /// <summary>
-        /// Gets the Window object of the dialog being handled.
-        /// </summary>
-        public Window Window
-        {
-            get {return this._window; }
-        }
- 
-        /// <summary>
-        /// Gets/Sets the number of times the dialog has been successfully handled.
-        /// </summary>
-        public int HandleCount
-        {
-            get {return this._handleCount; }
-            set {this._handleCount = value; }
-        }
- 
-        /// <summary>
-        /// Gets/Sets the dialog custom handler.
-        /// </summary>
-        public DialogHandlerDelegate HandlerDelegate
-        {
-            get {return this._handlerDelegate; }
-            set {this._handlerDelegate = value; }
-        }
- 
-        /// <summary>
-        /// Gets/Sets the current handled state. Will be set automatically by
-        /// the DialogMonitor object so we don't need to worry about it in our
-        /// code.
-        /// </summary>
-        public DialogCurrentState CurrentState
-        {
-            get {return this._currentState; }
-            set {this._currentState = value; }
-        }
-        #endregion
-```
-```VB
-Public Class FFDownloadsDialog
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog
- 
-   #Region "Members"
-    ' <summary>
-    ' Private storage for the number of times this dialog has been successfully handled.
-    ' </summary>
-    Private _handleCount As Integer
-    ' <summary>
-    ' The number of times in a row the dialog has been found. This overcomes the problem
-    ' where the dialog is first put up and momentarily displays "Downloads" and is
-    ' quickly changed to "16% complete 1 file – Downloads".
-    ' </summary>
-    Private _foundCount As Integer = 0
-    ' <summary>
-    ' The download window found.
-    ' </summary>
-    Private _window As Window
-    ' <summary>
-    ' Stores the custom handler delegate, if set by the test code.
-    ' </summary>
-    Private _handlerDelegate As DialogHandlerDelegate
-    ' <summary>
-    ' Stores the current handled state.
-    ' </summary>
-    Private _currentState As DialogCurrentState = DialogCurrentState.NotActive
-    ' <summary>
-    ' Semaphore used by the WaitUntilHandled function.
-    ' </summary>
-    Private _autoEvent As AutoResetEvent = New AutoResetEvent(False)
-#End Region
- 
-#Region "Private Constants"
-    ' <summary>
-    ' The title of the dialog we want handled.
-    ' </summary>
-    Private Const DIALOG_TITLE As String = "Downloads"
-#End Region
- 
-#Region "Properties"
-    ' <summary>
-    ' Gets the Window object of the dialog being handled.
-    ' </summary>
-    ReadOnly Property Window() As Window _
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.Window
-        Get
-            Return Me._window
-        End Get
-    End Property
- 
-    ' <summary>
-    ' Gets/Sets the number of times the dialog has been successfully handled.
-    ' </summary>
-    Property HandleCount() As Integer _
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.HandleCount
-        Get
-            Return Me._handleCount
-        End Get
-        Set(ByVal value As Integer)
-            Me._handleCount = value
-        End Set
-    End Property
- 
-    ' <summary>
-    ' Gets/Sets the dialog custom handler.
-    ' </summary>
-    Property HandlerDelegate() As DialogHandlerDelegate _
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.HandlerDelegate
-        Get
-            Return Me._handlerDelegate
-        End Get
-        Set(ByVal value As DialogHandlerDelegate)
-            Me._handlerDelegate = value
-        End Set
-    End Property
- 
-    ' <summary>
-    ' Gets/Sets the current handled state. Will be set automatically by
-    ' the DialogMonitor object so we don't need to worry about it in our
-    ' code.
-    ' </summary>
-    Property CurrentState() As DialogCurrentState _
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.CurrentState
-        Get
-            Return Me._currentState
-        End Get
-        Set(ByVal value As DialogCurrentState)
-            Me._currentState = value
-        End Set
-    End Property
-#End Region
-```
-
-
-So far everything is very simple and straightforward. Now that the local variables and properties are complete, it's time to implement the constructor. Since all we're going to do to handle the dialog is close it, we don't require the Desktop or DialogButton parameter that standard Win32 dialog handlers require:
-
-```C#
-#region Constructor
-/// <summary>
-/// Create the dialog.
-/// </summary>
-public FFDownloadsDialog()
-{
-}
-#endregion
-```
-```VB
-#Region "Constructor"
-    ' <summary>
-    ' Create the dialog handler instance.
-    ' </summary>
-    Public Sub New()
-        MyBase.New()
-    End Sub
-#End Region
-```
-
-Since there's nothing to the constructor, we could optionally leave it out and let the default constructor take over. So let's start implementing the IDialog methods starting with IsDialogActive.
-
-```C#
-#region IDialog Members
-/// <summary>
-/// Check whether the dialog is present or not. This function is
-/// called by the DialogMonitor object.
-/// </summary>
-/// <param name="dialogs">This is a list of dialogs passed in
-/// by the DialogMonitor object. Because the window we need is
-/// of the "MozillaUIWindowClass" class instead of the "#32770"
-/// dialog class, it's never included in the dialogs list.
-/// Thus we deliberately ignore this input parameter</param>
-/// <returns>True/False whether this dialog is present.</returns>
-public bool IsDialogActive(ArtOfTest.WebAii.Win32.WindowCollection dialogs)
-{
-    // Ignore dialogs parameter. It only contains windows of the 'Dialog' class.
-    // The FireFox Downloads dialog is of the 'MozillaUIWindowClass' class
-    this._window = WindowManager.FindWindowRecursively((IntPtr)0, "Downloads", false, 0);
-    if (null == this._window ||
-        !this._window.Caption.Equals("Downloads") ||
-        !this._window.ClassName.Equals("MozillaUIWindowClass"))
-    {
-        this._foundCount = 0;
-        return false;
-    }
-    this._foundCount++;
-    if (this._foundCount < 4)
-    {
-        // Must find the dialog four times in a row to be considered real
-        // instead of transient. When the dialog is first displayed it
-        // reads "Downloads" but is quickly changed after initial display.
-        return false;
-    }
-    return true;
-}
-```
-```VB
-' <summary>
-' Check whether the dialog is present or not. This function is
-' called by the DialogMonitor object.
-' </summary>
-' <param name="dialogs">This is a list of dialogs passed in
-' by the DialogMonitor object. Because the window we need is
-' of the "MozillaUIWindowClass" class instead of the "#32770"
-' dialog class, it's never included in the dialogs list.
-' Thus we deliberately ignore this input parameter</param>
-' <returns>True/False whether this dialog is present.</returns>
-Public Function IsDialogActive(ByVal dialogs As ArtOfTest.WebAii.Win32.WindowCollection) As Boolean _
-    Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.IsDialogActive
-    ' Ignore dialogs parameter. It only contains windows of the 'Dialog' class.
-    ' The FireFox Downloads dialog is of the 'MozillaUIWindowClass' class
-    Me._window = WindowManager.FindWindowRecursively(CType(0, System.IntPtr), "Downloads", False, 0)
-    If IsNothing(Me._window) Or _
-          Not Me._window.Caption.Equals("Downloads") Or _
-          Not Me._window.ClassName.Equals("MozillaUIWindowClass") Then
-            Me._foundCount = 0
-            Return False
-        End If
-        Me._foundCount += 1
-        If (Me._foundCount < 4) Then
-            ' Must find the dialog four times in a row to be considered real
-            ' instead of transient. When the dialog is first displayed it
-            ' reads "Downloads" but is quickly changed after initial display.
-            Return False
-        End If
-    Return True
-End Function
-```
-
-Because the DialogMonitor object passes in a **WindowCollection** of windows that have a class name of "#**32770**" and the FireFox dialog has the class name "**MozillaUIWindowClass**" we have to ignore the passed in WindowCollection and perform our own FindWindowRecursively. Once a window with the right caption is found we still need to verify it has the right class name.
- 
-Detecting when the download manager has finished downloading files is a little bit tricky (and the only way to know this is through experience). When the dialog is first displayed the caption initially reads "Downloads" which is exactly the same thing it displays when all the downloads are complete. When it actually begins downloading a file, the dialog caption is changed to something like "11% of 1 file - Downloads". This change usually happens very quickly (in less than a second). But since it isn't instantaneous we need to monitor the caption for a short period of time to make sure it is quiescent before accepting that Firefox has finished all the downloads. This is accomplished in the code by verifying that the caption reads "Downloads" in 4 consecutive calls to IsDialogActive.
- 
-Now we need to implement the Handle function:
-
-```C#
-/// <summary>
-/// This is called by the DialogMonitor whenever IsDialogActive returns true.
-/// </summary>
-public void Handle()
-{
-    // If you are sharing this implementation with other
-    // developers, this allows them to override this method
-    // by setting the handler delegate. So if the
-    // delegate is not null, perform the built in handling logic
-    // otherwise call the custom handling logic.
-    if (this.HandlerDelegate != null)
-    {
-        this.HandlerDelegate(this);
-    }
-    else
-    {
-        try
-        {
-                   this.Window.Close();
-                   this.Window.WaitForVisibility(false, 500);
-                   this._autoEvent.Set();    // trigger the semaphore used by WaitUntilHandled
-        }
-        catch
-        {
-                   // Do any custom handling and return error.
-        }
-    }
-}
-```
-```VB
-' <summary>
-' This is called by the DialogMonitor whenever IsDialogActive returns true.
-' </summary>
-' <returns>True/False whether the dialog was handled.</returns>
-Public Sub Handle() _
-Implements ArtOfTest.WebAii.Win32.Dialogs.IDialog.Handle
-    ' If you are sharing this implementation with other
-    ' developers, this allows them to override this method
-    ' by setting the handler delegate. So if the
-    ' delegate is not null, perform the built in handling logic
-    ' otherwise call the custom handling logic.
-    If (Not IsNothing(Me.HandlerDelegate)) Then
-    Me.HandlerDelegate.Invoke(Me)
-    Else
-        Try
-             Me.Window.Close()
-             Me.Window.WaitForVisibility(False, 500)
-            Me._autoEvent.Set()        ' trigger the semaphore used by WaitUntilHandled
-         Catch
-             ' Do any custom handling and return error.
-         End Try
-     End If
-End Sub
-```
-
-The normal action we want our custom dialog handler to perform is to simply close the window. This is easily accomplished with this.Window.Close. Once the handler sends to the window the close command we wait up to 500 milliseconds for it to actually go away. We also trigger a semaphore so that the main test thread can be notified that the dialog has been handled.
- 
-Optionally our handler code will call a custom handler function if the delegate has been set by the calling program.
- 
-Lastly we need to implement the WaitUntilHandled function:
-
-```C#
-        /// <summary>
-///
-        /// May be called by test code. Waits up to the specific time out
-        /// period for the dialog to be handled. Optionally clears the
-        /// HandleCount property.
-        /// </summary>
-        /// <param name="timeout">The maximum number of milliseconds to
-        /// wait for the dialog to be handled. If the timeout expires
-        /// before the dialog is handled a timeout exception is thrown.</param>
-        /// <param name="resetCount">Set to true to reset the
-        /// HandleCount property to zero just prior to waiting.</param>
-        public void WaitUntilHandled(int timeout, bool resetCount)
-         {
-             if (resetCount)
-             {
-                this.HandleCount = 0;
-             }
-             if (false == this._autoEvent.WaitOne(timeout, false))
-             {
-                throw new System.TimeoutException("FFDownloadsDialog.WaitUntilHandled timed out.");
-            }
-         }
-     }
-}
-```
-```VB
-    ' <summary>
-' <summary>
-    ' May be called by test code. Waits up to the specific time out
-    ' period for the dialog to be handled. Optionally clears the
-    ' HandleCount property.
-    ' </summary>
-    ' <param name="timeout">The maximum number of milliseconds to
-    ' wait for the dialog to be handled. If the timeout expires
-    ' before the dialog is handled a timeout exception is thrown.</param>
-    ' <param name="resetCount">Set to true to reset the
-    ' HandleCount property to zero just prior to waiting.</param>
-    Public Sub WaitUntilHandled(ByVal timeout As Integer, ByVal resetCount As Boolean)
-         If (resetCount) Then
-             Me.HandleCount = 0
-         End If
-             If (False = Me._autoEvent.WaitOne(timeout, False)) Then
-             Throw New System.TimeoutException("FFDownloadsDialog.WaitUntilHandled timed out.")
-    End If
-End Sub
- 
-End Class
-```
-
-The only thing really happening in this code is to wait on the semaphore to be set. If the semaphore is not set within the timeout period it throws a System.TimeoutException exception. Optionally it will also reset the HandleCount property prior to waiting for the semaphore.
-
-[1]: /img/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs/fig1.png
-[2]: /img/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs/fig2.png
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
index 397b9af4..743b031e 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/html-popups.md
@@ -12,19 +12,19 @@ Given that these pop-ups are just like any other browser instance, the framework
  
 Given that HTML pop-up dialogs are launched through some actions on the page and not through an explicit call to Manager.LaunchNewBrowser(), the framework has no idea which new browser instances you want connected and added to the Manager.Browsers[] collection versus the ones you want ignored. Therefore, you need to notify the framework about the browser instances that you want to be tracked by enabling new browser tracking. You enable manager tracking by calling:
 
-```C#
+````C#
 Manager.SetNewBrowserTracking(true);
-```
-```VB
+````
+````VB
 Manager.SetNewBrowserTracking(true)
-```
+````
 
 When new browser tracking is enabled, any new browser instance launched on the machine is automatically added to the Manager.Browsers[] collection. In addition the Manager.ActiveBrowser instance is automatically set to the last launched browser instance. You then have full access to that pop-up instance with its full DOM and the ability to execute automation actions against it just like any other browser instance. When the pop-up is closed using Browser.Close(), the instance is removed from the Manager.Browsers[] collection and the ActiveBrowser instance is again automatically re-assigned to the last active Browser object in the Manager.Browsers[] collection.
  
 The sample below demonstrates this support. Let's start with the following HTML page that invokes a HTML pop-up:
 
 
-```HTML
+````HTML
 <html>
 <head>
     <title>HTMLPopups</title>
@@ -41,11 +41,11 @@ The sample below demonstrates this support. Let's start with the following HTML
     <a onclick="OpenWindow()">Invoke HTML Popup</a>
 </body>
 </html>
-```
+````
 
 The automation code that allows us to connect to that new instance looks like this:
 
-```C#
+````C#
 // Set new browser tracking to enabled.
 // This will make all new browser instances connect to
 // the Manager.
@@ -74,8 +74,8 @@ ActiveBrowser.Close();
 // the last launched active instance.
 Assert.IsTrue(Manager.Browsers.Count == 1);
 Assert.IsTrue(ActiveBrowser.Url.Contains("PAGE_NAME.com"));
-```
-```VB
+````
+````VB
 ' Set new browser tracking to enabled.
 ' This will make all new browser instances connect to
 ' the Manager.
@@ -104,14 +104,14 @@ ActiveBrowser.Close()
 ' the last launched active instance.
 Assert.IsTrue(Manager.Browsers.Count = 1)
 Assert.IsTrue(ActiveBrowser.Url.Contains("PAGE_NAME.com"))
-```
+````
 
 Sometimes you need to close the popup by clicking on a button instead of just closing the window. Telerik Testing Framework supports this functionality with an additional paramter to the HtmlControl.Click function. By passing in a 'true' the framework expects the window to close. The ActiveBrowser is also set to the browser window that was open prior to the popup opening.
 
-```C#
+````C#
 Find.ById<HtmlInputButton>("button1").Click(true);  // Here we tell the framework that this click causes the browser window to close
-```
-```VB
+````
+````VB
 Find.ById(Of HtmlInputButton)("button1").Click(True)    ' Here we tell the framework that this click causes the browser window to close
-```
+````
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
index 7cc141c5..1f1fa422 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs.md
@@ -4,7 +4,8 @@ page_title: Modal Dialogs
 description: "Handle a modal dialog in a coded step in Test Studio. Coded test to handle modal dialogs in Test Studio. Test Studio Testing Framework Download Modal Dialog handling.."
 position: 9
 ---
-#Handling IE Modal Dialogs#
+
+# Handling IE Modal Dialogs
 
 ![Modal Dialog][1]
 
@@ -12,7 +13,7 @@ The main difference between IE modal dialogs and the HTML Pop-ups is that the mo
  
 IE modal dialogs require special handling. They don't act like standard HTML pop-up windows, which means the standard approach does not work. Here is an example of how to code for the IE modal dialog special case:
 
-```C#
+````C#
 [TestMethod]
 [Description("How to access and handle IE's modal dialogs")]
 public void IEModalDialogsSupport()
@@ -47,8 +48,8 @@ public void IEModalDialogsSupport()
     // The ActiveBrowser is back to the main browser window.
      ActiveBrowser.NavigateTo("http://www.google.com");
 }
-```
-```VB
+````
+````VB
 <TestMethod(), _
 Description("How to access and handle IE's modal dialogs")> _
 Public Sub IEModalDialogsSupport()
@@ -87,7 +88,7 @@ Public Sub IEModalDialogsSupport()
      ActiveBrowser.NavigateTo("http://www.google.com")
   
 End Sub
-```
+````
 
 [1]: /img/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/modal-dialogs/fig1.png
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/prompt-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/prompt-dialogs.md
index d1bcd7e3..cba7a51c 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/prompt-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/prompt-dialogs.md
@@ -14,7 +14,7 @@ __Telerik Testing Framework__ includes native support for dialog handling (under
 ><br>
 > _using ArtOfTest.WebAii.Win32.Dialogs;_
 
-```C#
+````C#
 // Define the Prompt dialog and how it needs to be handled - choose between Ok and Cancel
 var promptDlg = new ArtOfTest.WebAii.Win32.Dialogs.PromptDialog(Manager.ActiveBrowser, DialogButton.OK, "message to type");
 
@@ -49,8 +49,8 @@ Manager.DialogMonitor.Stop();
 // especially if the elements to use are related to the action confirmed with the dialog handling
 //Manager.ActiveBrowser.RefreshDomTree();
 
-```
-```VB
+````
+````VB
 ' Define the Prompt dialog
 IDialog promptDlg = New ArtOfTest.WebAii.Win32.Dialogs.PromptDialog(Manager.ActiveBrowser, DialogButton.OK, "stringMsg")
 
@@ -77,4 +77,4 @@ promptDlg.Handle()
 Manager.DialogMonitor.RemoveDialog(promptDlg)
 Manager.DialogMonitor.Stop()
 
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
index a36c80ba..4a0ad1e0 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/win32-dialogs.md
@@ -4,11 +4,12 @@ page_title: Logon Dialogs
 description: "Handle a Logon dialog in a coded step in Test Studio. Coded test to handle Logon dialogs in Test Studio. Test Studio Testing Framework Logon Dialog handling."
 position: 5
 ---
-#Logon Dialogs#
+
+# Logon Dialogs
 
 With Logon dialogs, you need to pass in the username/password that you want used and how the dialog should be handled. Your options for the Logon dialog are: DialogButton.OK, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add a logon dialog support with username/password
 Manager.DialogMonitor.AddDialog(new LogonDialog(ActiveBrowser, "<username>", "<password>", DialogButton.OK));
 Manager.DialogMonitor.Start();
@@ -17,8 +18,8 @@ Manager.DialogMonitor.Start();
 ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>");
 
 // Dialog should be automatically handled
-```
-```VB
+````
+````VB
 ' Add a logon dialog support with username/password
 Manager.DialogMonitor.AddDialog(New LogonDialog(ActiveBrowser, "<username>", "<password>", DialogButton.OK))
 Manager.DialogMonitor.Start()
@@ -27,7 +28,7 @@ Manager.DialogMonitor.Start()
 ActiveBrowser.NavigateTo("<Place a Url to LogOn to here>")
 
 ' Dialog should be automatically handled
-```
+````
 
 
 > **To compile the above code include the following using:**
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/wpf-dialogs.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/wpf-dialogs.md
index 721825dc..c6e074fa 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/wpf-dialogs.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/wpf-dialogs.md
@@ -12,7 +12,7 @@ The dialogs to store a file locally or open a file in the WPF application also h
 
 With OpenFile dialog you need to pass in the full path to the file to open in the WPF application and how the dialog should be handled. The options for OpenFile dialog are: DialogButton.OPEN, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add OpenFile dialog
 ArtOfTest.WebAii.Win32.Dialogs.OpenFileDialog.CreateOpenFileDialog wpfOpenDialog = ArtOfTest.WebAii.Win32.Dialogs.OpenFileDialog.CreateOpenFileDialog(ActiveApplication, DialogButton.OPEN, @"d:\name");
 
@@ -32,13 +32,13 @@ wpfOpenDialog.WaitUntilHandled(15000);
 Manager.DialogMonitor.RemoveDialog(wpfOpenDialog);
   
 // Dialog should be automatically handled
-```
+````
 
 ## SaveAs Dialog Handler
 
 With SaveAs dialog, you need to pass in the full path and name for the file to save and how the dialog should be handled. The options for SaveAs dialog are: DialogButton.SAVE, DialogButton.CANCEL or DialogButton.CLOSE.
 
-```C#
+````C#
 // Add SaveAs dialog
 ArtOfTest.WebAii.Win32.Dialogs.SaveAsDialog.CreateSaveAsDialog wpfSaveAsDialog = ArtOfTest.WebAii.Win32.Dialogs.SaveAsDialog.CreateSaveAsDialog(ActiveApplication, DialogButton.SAVE, @"d:\name");
 
@@ -59,7 +59,7 @@ Manager.DialogMonitor.RemoveDialog(wpfSaveAsDialog);
   
 // Dialog should be automatically handled
 
-```
+````
 
 > **Note** To compile the above code include the following using:
 >
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/invoking-javascript.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
index 279e0583..513891bb 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/invoking-javascript.md
@@ -5,7 +5,8 @@ description: "Invoke JavaScript in a coded step in Test Studio. Coded test to in
 previous_url: /user-guide/write-tests-in-code/advanced-topics/javascript/invoking-javascript.aspx, /user-guide/write-tests-in-code/advanced-topics/javascript/invoking-javascript
 position: 1
 ---
-#Invoking Javascript#
+
+# Invoking Javascript
 
 Telerik Testing Framework supports directly invoking JavaScript functions from your .NET test code. One key advantage to this support is that you can use it to do your JavaScript unit testing without having to integrate yet another unit testing framework into your development environment. You can also avoid having to learn/support this additional framework. Abilities include:
 
@@ -19,11 +20,12 @@ Telerik Testing Framework supports directly invoking JavaScript functions from y
 
 * Perform logging/tracing of your JavaScript routines. The logging is done directly into the unified log you are using.
 
-##Invoking JavaScript Functions##
+
+## Invoking JavaScript Functions
 
 The Actions.InvokeScript() enables you to simply provide a JavaScript function name to invoke. For example:
 
-```C#
+````C#
 // Assume our page has JavaScript method Test1() & Test2() & Test3()
  
 // Call a JavaScript function.
@@ -39,8 +41,8 @@ string jsRetValue = Actions.InvokeScript("Test3();");
  
 // Call a JavaScript function that returns a value
 int val = Actions.InvokeScript<int>(@"Test3(""Bear"", ""Utah"")");
-```
-```VB
+````
+````VB
 ' Assume our page has JavaScript method Test1() & Test2() & Test3()
  
 ' Call a JavaScript function.
@@ -56,21 +58,21 @@ Dim jsRetValue As String = Actions.InvokeScript("Test3();")
  
 ' Call a JavaScript function that returns a value
 Dim val As Integer = Actions.InvokeScript(Of Integer)("Test3(""Bear"", ""Utah"")")
-```
+````
 
 
 Here is a code which calls an Angular function against input field:
 
-```C#
+````C#
 Actions.InvokeScript("angular.element(" + element.ClientSideLocator + ").val('" + text.Replace("'", "\\'") + "').triggerHandler('input')");
-```
+````
 
-##JavaScript Unit Testing Using NUnit or Visual Studio Team Test##
+## JavaScript Unit Testing Using NUnit or Visual Studio Team Test
 
 Below is an example of how you can define JavaScript unit tests that is consistent with the rest of your tests and manages their execution and reporting using the same unit testing infrastructure, whether it is NUnit or Visual Studio Team Test.
 
 
-```C#
+````C#
 [TestMethod]
 public void JsUnitTest1()
 {
@@ -78,16 +80,16 @@ public void JsUnitTest1()
     string strBool = Actions.InvokeScript("JsUnitTest1()");
     Assert.IsTrue(bool.Parse(strBool));
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub JsUnitTest1()
     ' return 'true' for pass or 'false' for fail.
     Dim strBool As String = Actions.InvokeScript("JsUnitTest1()")
     Assert.IsTrue(Boolean.Parse(strBool))
 End Sub
-```
+````
 
-###See also
+### See also
 
 * <a href="/advanced-topics/coded-samples/html/jQuery-events-do-not-fire" target="_blank">jQuery events do not fire</a>
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-events.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-events.md
index 75c4cb1d..c03c528d 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-events.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-events.md
@@ -4,13 +4,14 @@ page_title: JavaScript Events
 description: "Invoking JS events in a coded step in Test Studio. Coded test to Invoke JS events in Test Studio. Test Studio Testing Framework Invoking JS Events"
 position: 2
 ---
-#JavaScript Events#
 
-##Invoking JavaScript Events##
+# JavaScript Events
+
+## Invoking JavaScript Events
 
 Telerik Testing Framework allows you to invoke JavaScript events directly with or without event arguments. For example:
 
-```C#
+````C#
 // Invoke the OnFocus event
 HtmlButton b = Find.ById<HtmlButton>("b");
 b.InvokeEvent(ScriptEventType.OnFocus);
@@ -25,8 +26,8 @@ MouseEvent me = new MouseEvent();
 me.Type = "mouseover";
 me.SetRelatedTarget(body1);
 area1.InvokeEvent(me);
-```
-```VB
+````
+````VB
 ' Invoke the OnFocus event
 Dim b As HtmlButton = Find.ById(Of HtmlButton)("b")
 b.InvokeEvent(ScriptEventType.OnFocus)
@@ -41,13 +42,13 @@ Dim [me] As New MouseEvent()
 [me].Type = "mouseover"
 [me].SetRelatedTarget(body1)
 area1.InvokeEvent([me])
-```
+````
 
-##JavaScript Event Handlers##
+## JavaScript Event Handlers
 
 The framework gives you the ability to attach a .NET event handler to your JavaScript happening in the browser. Start by defining your event handler like this:
 
-```C#
+````C#
 private volatile bool _clickHandled;
 private System.Threading.AutoResetEvent _clickARE;
  
@@ -56,8 +57,8 @@ private void OnClick(object sender, JavascriptEventArgs e)
     _clickHandled = true;
     _clickARE.Set();
 }
-```
-```VB
+````
+````VB
 Private _clickHandled As Boolean
 _clickHandled
 Private _clickARE As System.Threading.AutoResetEvent
@@ -66,11 +67,11 @@ Private Sub OnClick(ByVal sender As Object, ByVal e As JavascriptEventArgs)
     _clickHandled = True
     _clickARE.[Set]()
 End Sub
-```
+````
 
 All that's left is to attach the event handler to an element on the DOM like this:
 
-```C#
+````C#
 [TestMethod]
 public void ClickHandler()
 {
@@ -90,8 +91,8 @@ public void ClickHandler()
  
     Assert.IsTrue(_clickHandled);
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub ClickHandler()
     _clickARE = New System.Threading.AutoResetEvent(False)
@@ -110,4 +111,4 @@ Public Sub ClickHandler()
  
     Assert.IsTrue(_clickHandled)
 End Sub
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-logging.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-logging.md
index debd94fb..07046d0d 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-logging.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-logging.md
@@ -4,13 +4,14 @@ page_title: Logging from JavaScript
 description: "Logging from JavaScript in a coded step in Test Studio. Coded test to include Logs from JavaScript in the Test Studio test logging. Test Studio Testing Framework logging from JavaScript into the test log."
 position: 3
 ---
-#Logging from JavaScript#
+
+# Logging from JavaScript
 
 Telerik Testing Framework also supports logging directly from JavaScript into the unified test log that your tests are using. Logging from JavaScript is not enabled by default and needs to be explicitly enabled globally by setting the **Settings.EnableScriptLogging = true** via the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/settings-class" target="_blank">Settings Class</a> or setting **enableScriptLogging="true"** in the application <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/app-config-file" target="_blank">.config</a> file. In addition each page that wants to perform logging needs to include the WebAii_Logging.js file. You will find this file installed in the %InstallDir%\Bin folder.
  
 Below is a sample to demonstrate how to perform logging from your JavaScript routines:
 
-```C#
+````C#
 // Settings.Current.EnableScriptLogging must be set to true before
 // LaunchNewBrowser. This was done in the Initialize section of
 // this test.
@@ -28,8 +29,8 @@ Settings.Current.EnableScriptLogging = false;
  
 // NOTE: Once script logging is disabled, any logging calls from
 // the script will be ignored and won't cause a script error.
-```
-```VB
+````
+````VB
 ' Settings.Current.EnableScriptLogging must be set to true before
 ' LaunchNewBrowser. This was done in the Initialize section of
 ' this test.
@@ -47,13 +48,13 @@ Settings.Current.EnableScriptLogging = False
  
 ' NOTE: Once script logging is disabled, any logging calls from
 ' the script will be ignored and won't cause a script error.
-```
+````
 
 The page script function Test5() can perform logging like this:
 
-```JavaScript
+````JavaScript
 function Test5()
 {
     WebAiiLog("Trace", "Test5: Log this message!");
 }
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/json-objects.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/json-objects.md
index b9f94834..b963db98 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/json-objects.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/json-objects.md
@@ -4,13 +4,14 @@ page_title: JSON Objects
 description: "Using JSON objects in a coded step in Test Studio. Coded test to handle JSON objects in Test Studio. Test Studio Testing Framework handle JSON objects in tests."
 position: 5
 ---
-#Handling JSON Objects#
+
+# Handling JSON Objects
 
 Your tests can understand JSON (<a href="http://www.json.org/" target="_blank" rel="nofollow">JavaScript Object Notation</a>) and can handle strongly typed objects returned from JavaScript. This might be a bit advanced for regular testers implementing test automation. However, if you are building mini-frameworks on top of Telerik Testing Framework, it is a great tool to help you get rid of having to parse complex strings returned by the InvokeScript function.
  
 This is a basic example of how to use JSON:
 
-```C#
+````C#
 [TestMethod]
 public void KeyValuePairs()
 {
@@ -23,8 +24,8 @@ public void KeyValuePairs()
     Assert.AreEqual<string>("value1", o["root"]["key1"]);
     Assert.AreEqual<string>("value2", o["root"]["key2"]);
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub KeyValuePairs()
     Manager.LaunchNewBrowser()
@@ -35,11 +36,11 @@ Public Sub KeyValuePairs()
     Assert.AreEqual(Of String)("value1", o("root")("key1"))
     Assert.AreEqual(Of String)("value2", o("root")("key2"))
 End Sub
-```
+````
 
 In this example we define our own object in a Data Contract:
 
-```C#
+````C#
 [DataContract]
 public class MyObject
 {
@@ -57,8 +58,8 @@ public void ReturnObject()
     Assert.AreEqual<int>(1, o.One);
     Assert.AreEqual<int>(15, o.Fifteen);
 }
-```
-```VB
+````
+````VB
 <DataContract()> _
 Public Class MyObject
     Private _One As Integer
@@ -90,11 +91,11 @@ Public Sub ReturnObject()
     Assert.AreEqual(Of Integer)(1, o.One)
     Assert.AreEqual(Of Integer)(15, o.Fifteen)
 End Sub
-```
+````
 
 In this example we'll access an array returned by InvokeScript, treat it as JSON, and parse it manually for its values.
 
-```C#
+````C#
 var actions = Manager.Current.ActiveBrowser.Actions;
 JsonObject result = actions.InvokeScript <JsonObject>("window.my_list=[1,2,3]");
 JsonArray arr = (JsonArray)result["root"];
@@ -103,8 +104,8 @@ for (int i = 0; i < 3; i++)
 double val = arr[i];
 Log.WriteLine(val.ToString());
 }
-```
-```VB
+````
+````VB
 Dim actions = Manager.Current.ActiveBrowser.Actions
 Dim result As JsonObject = actions.InvokeScript(Of JsonObject)("window.my_list=[1,2,3]")
 Dim arr As JsonArray = DirectCast(result("root"), JsonArray)
@@ -112,4 +113,4 @@ For i As Integer = 0 To 2
     Dim val As Double = arr(i)
     Log.WriteLine(val.ToString())
 Next
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/multi-browser-support.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/multi-browser-support.md
index 9f1da34f..227796b3 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/multi-browser-support.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/multi-browser-support.md
@@ -5,11 +5,11 @@ description: "Test Studio Testing framework support for multiple browser instanc
 previous_url: /user-guide/write-tests-in-code/advanced-topics/multi-browser-instance-support.aspx, /user-guide/write-tests-in-code/advanced-topics/multi-browser-instance-support
 position: 1
 ---
-#Multi-Browser Instance Support#
+# Multi-Browser Instance Support
 
 Throughout the Telerik Testing Framework tutorials, we've been focusing only on the single browser instance 'ActiveBrowser,' given that it is the most common usage in web automation. Multi-browser instance automation within one session of the Manager object is supported, however. Having different types of browsers being automated within the same session is also supported. For example, within one test case session, you can automate two Internet Explorer browser instances and one Firefox instance all running concurrently. Such types of automation might not be very common but might be useful for certain specialized scenarios. (i.e. you could use this feature to do bitmap comparison across different browser types by capturing browser images from one instance and comparing it to the captured image from another instance).
 
-##How It Works##
+## How It Works
 
 The 'Manager' object is the main object that keeps tracks of all active browser instances using the Manager.Browsers[] collection. Users can launch as many instances as they want by using the 'Manager.LaunchNewBrowser()' method. Each time a new browser is launched, the 'Manager' creates the new 'Browser' object corresponding to that browser instance and adds it to the Browsers[] collection. The 'ActiveBrowser' property exposed off the 'Manager' is actually the last launched browser and should be the last browser instance in the 'Browsers[]' collection.
 
@@ -17,7 +17,7 @@ The 'Manager' object is the main object that keeps tracks of all active browser
  
 The below sample demonstrates how you can leverage the multi-browser support to automate multiple instances of a browser within one test case. Such testing might be needed when performing concurrency testing in your web app.
 
-```C#
+````C#
 // Launch a new instance of IE
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, true);
   
@@ -55,8 +55,8 @@ ie.Window.SetFocus();
 // You can also choose to set a timeout as shown below to double check that the
 // browser has actually closed and its handle is no longer visible.
 ff.Close(40);
-```
-```VB
+````
+````VB
 ' Launch a new instance of IE
 Manager.LaunchNewBrowser(BrowserType.InternetExplorer, True)
   
@@ -94,4 +94,4 @@ ie.Window.SetFocus()
 ' You can also choose to set a timeout as shown below to double check that the
 ' browser has actually closed and its handle is no longer visible.
 ff.Close(40)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/Introduction.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/Introduction.md
index d8462369..cb2301dd 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/Introduction.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/Introduction.md
@@ -4,11 +4,11 @@ page_title: Introduction to TestRegions
 description: "Test Studio Testing Framework: Introducing TestRegions. What are TestRegions and how TestRegions can help in designing coded automation tests. "
 position: 1
 ---
-#Introduction to TestRegions#
+# Introduction to TestRegions
 
 Building testability and agility into your markup applications.
 
-##What Are TestRegions? (*)##
+## What Are TestRegions? (*)
 
 TestRegions are simple innovations that bring a new perspective to automated software testing by breaking the traditional silos between application authoring and testing. They pave the way to a better and more robust test automation while enhancing the agility of the overall development lifecycle. TestRegions are hopefully a first step that others can use and build upon to usher a new generation of tools and methodologies that bring new advancements in the art of software testing and quality assurance.
  
@@ -28,7 +28,7 @@ Some of the key benefits of TestRegions are:
  
 To help demonstrate these benefits, we will be using the following simple markup page as our sample application through out this tutorial.
 
-```HTML
+````HTML
 <html>
 <head>
    <title>Basic TestRegion's Usage</title>
@@ -40,7 +40,7 @@ To help demonstrate these benefits, we will be using the following simple markup
      <input type="text" id="yourname" />
      <input type="text" id="zipcode" />
      <!-- Italian restaurants in your zipcode -->
-     <table>
+     </table>
        <tr>
          <td>Name</td>
          <td>Address</td>
@@ -65,9 +65,9 @@ To help demonstrate these benefits, we will be using the following simple markup
    </div>
 </body>
 </html>
-```
+````
 
-##Current Automation Practices##
+## Current Automation Practices
 
 Before digging into TestRegions, let's first take a look at some of the current common automation approaches for markup applications and understand their characteristics, challenges and drawbacks.
  
@@ -92,25 +92,25 @@ To clarify this point more, let's take a simple example:
  
 With that being said, it is important to note that TestRegions DO NOT completely eradicate the need for ids/names but instead they augment the current use of ids/names and common automation practices to help address some of the issues mentioned above and add more structure and consistency to test automation.
 
-##Using TestRegions##
+## Using TestRegions
 
 Let's start by using TestRegions in the above sample to provide a structured approach to accessing this application from test automation. To do so, we need to inject TestRegions within our application markup. The TestRegions supported by Telerik Testing Framework Automation Infrastructure are:
 
-```HTML
+````HTML
 <testregion id="regionid">...region content...</testregion>
-```
+````
 
 Given that these are custom tags and are currently not handled as expected in latest browsers (for example, in Firefox, custom tags - even if they are Xhtml defined with extended dtd - are always included with the closing tag right after the open tag regardless of the tag content), the comment version of these tags is supported:
 
-```HTML
+````HTML
 <!--testregion id="regionid"-->...region content...<!--/testregion-->
-```
+````
 
 Using these tags as comments is a very unintrusive approach to the overall application and is completely compliant with markup standards like XHTML and XML.
 
 Let's start by defining two logical regions within our sample application above that we want to target in our automated testing. The page below shows the sample above with the following two logical regions defined: userinput, restaurantdata.
 
-```HTML
+````HTML
 <html>
 <head>
    <title>Basic TestRegion's Usage</title>
@@ -151,23 +151,23 @@ Let's start by defining two logical regions within our sample application above
    </div>
 </body>
 </html>
-```
+````
 
 With test regions defined, our test code can directly access these regions regardless of their nesting or positioning as follows:
 
-```C#
+````C#
 TestRegion userInput = Manager.ActiveBrowser.Regions["userinput"];
 TestRegion restaurantData = Manager.ActiveBrowser.Regions["restaurantdata"];
-```
-```VB
+````
+````VB
 Dim userInput As TestRegion = Manager.ActiveBrowser.Regions("userinput")
 Dim restaurantData As TestRegion = Manager.ActiveBrowser.Regions("restaurantdata")
-```
+````
 
 
 Each TestRegion above represents the part of the application as defined by the TestRegio's that are part of the application. It is worth noting here that the TestRegions collection accessor is case-insensitive to avoid test failures due to id casing mistakes.
 
-##Identifying Elements Using TestRegions##
+## Identifying Elements Using TestRegions
 
 Now that we know how to define test regions as part of an application under test and how to access them from our automated test code, our next step is to be able to access elements contained in these TestRegions to perform actions on or extract data from.
  
@@ -179,22 +179,22 @@ Each TestRegion object has two properties that provide access to the elements co
  
 For example, to locate the restaurants table in the above sample, you can write:
 
-```C#
+````C#
 TestRegion restaurantData = Manager.ActiveBrowser.Regions["restaurantdata"];
  
 // Given that the table is the first table within the 'restaurantdata' test region, it has an occurrence index of '0'
 Element restaurantTable = restaurantData.Find.ByTagIndex("table", 0);
-```
-```VB
+````
+````VB
 Dim restaurantData As TestRegion = Manager.ActiveBrowser.Regions("restaurantdata")
  
 ' Given that the table is the first table within the 'restaurantdata' test region, it has an occurrence index of '0'
 Dim restaurantTable As Element = restaurantData.Find.ByTagIndex("table", 0)
-```
+````
 
 Once you have access to the Element object, you can now use it to extract information from or execute actions on. For example:
 
-```C#
+````C#
 // access the userinput test region.
 TestRegion userInput = Manager.ActiveBrowser.Regions["userinput"];
  
@@ -203,8 +203,8 @@ Element zipCodeTextBox = userInput.Find.ByXPath("//input[2]");
  
 // Perform an action on the element.
 Manager.ActiveBrowser.Actions.SetText(zipCodeTextBox, "90210");
-```
-```VB
+````
+````VB
 ' access the userinput test region.
 Dim userInput As TestRegion = Manager.ActiveBrowser.Regions("userinput")
  
@@ -213,11 +213,11 @@ Dim zipCodeTextBox As Element = userInput.Find.ByXPath("/input[2]")
  
 ' Perform an action on the element.
 Manager.ActiveBrowser.Actions.SetText(zipCodeTextBox, "90210")
-```
+````
 
 In the first sample above, the test will not be impacted by any changes to the application regardless of how many 'table' tags get added before or after that testregion. You can even extract that testregion and embed it in a different portion of a different application and all tests that target that region will still work as expected. Same with the second sample.
 
-##Summary##
+## Summary
 
 The samples above introduce you to basic usage of TestRegions as part of the Telerik Testing Framework Automation Infrastructure. They also demonstrate how you can utilize this approach to build robust test automation code that exhibit low maintenance cost and is highly resilient to undesired test breaks. Moreover, they demonstrate how to use a consistent and structured approach to identify application segments to target for automation while making test code more legible and faster to learn and understand. TestRegions can enhance the agility of development teams and fits nicely within an agile development environment.
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
index 88c0b094..f111ad52 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/asp-net-tr-control.md
@@ -4,7 +4,7 @@ page_title: Asp.NET TR Control
 description: "Using TestRegions in Test Studio Testing Framework tests. Example of using TestRegions in coded tests. "
 position: 2
 ---
-#Using Asp.Net TestRegion Control#
+# Using Asp.Net TestRegion Control
 
 TestRegions can be a powerful tool to build testability into your web applications and enable your test automation teams to build highly resilient test beds that have low maintenance costs compared to the traditional automation methods like the HTTP record/replay approaches. TestRegions are ideal to be used with dynamic web frameworks like ASP.NET since they can take out some of the complexity that comes with the auto generated html. Given that TestRegions are injected in the source code of web pages, we wanted to provide Visual Studio and ASP.NET developers a richer experience at design time. Telerik Testing Framework includes an ASP.NET TestRegion Custom Control that can be used just like any other asp: control to define TestRegion's into your code. This control allows you to:
 
@@ -20,7 +20,7 @@ Below is a segment of the HTML persisted that is shown in design view above.
 
 **Note:** The samples shown above are included in full in the code samples installed with Telerik Testing Framework.
 
-##Adding ASP.NET TestRegion Control to Your Toolbox##
+## Adding ASP.NET TestRegion Control to Your Toolbox
 
 To be able to use this control as shown above, you simply need to add it first to your ToolBox. Visual Studio should handle all tag registrations once you drag-n-drop the control on your pages. To add the control to your toolbox:
 
diff --git a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/using-the-http-proxy.md b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/using-the-http-proxy.md
index 03518a28..3018344b 100644
--- a/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/using-the-http-proxy.md
+++ b/docs/testing-framework/write-tests-in-code/advanced-topics-wtc/using-the-http-proxy.md
@@ -4,7 +4,7 @@ page_title: Using the HTTP Proxy
 description: "Test Studio Testing Framework support for using HTTP proxy. "
 position: 1
 ---
-#Using the HTTP Proxy#
+# Using the HTTP Proxy
 
 Telerik Testing framework includes the ArtOfTest.WebAii.Messaging.Http namespace. With it you have the ability to intercept raw HTTP traffic under the cover. Using the HTTP proxy you can intercept an HTTP request originating from the browser before it is sent to the web server and/or intercept HTTP responses coming from the web server just before they reach the browser and are rendered by it. This functionality opens up the framework to be used in a wider range of automation scenarios like:
 
@@ -21,47 +21,61 @@ In this namespace you will find the following methods classes:
 	<th>Class</th><th>Description</th>
 </tr>
 <tr>
-	<td>**HttpProxyManager**</td>
+	<td>
+
+**HttpProxyManager**</td>
 	<td>Manages the HTTP proxy agent.</td>
 </tr>
 <tr>
-	<td>**HttpRequest**</td>
+	<td>
+
+**HttpRequest**</td>
 	<td>Used to create and manipulate an HTTP request.</td>
 </tr>
 <tr>
-	<td>**HttpRequestEventArgs**</td>
+	<td>
+
+**HttpRequestEventArgs**</td>
 	<td>EventArgs subclass that wraps an HTTP request, and possibly the related response.</td>
 </tr>
 <tr>
-	<td>**HttpResponse**</td>
+	<td>
+
+**HttpResponse**</td>
 	<td>Class wrapper of an HTTP response.</td>
 </tr>
 <tr>
-	<td>**HttpResponseEventArgs**</td>
+	<td>
+
+**HttpResponseEventArgs**</td>
 	<td>EventArgs subclass that wraps an HTTP response and the related request.</td>
 </tr>
 <tr>
-	<td>**RequestListenerInfo**</td>
+	<td>
+
+**RequestListenerInfo**</td>
 	<td>Wraps a listener for BeforeRequest events from the proxy.</td>
 </tr>
 <tr>
-	<td>**ResponseListenerInfo**</td>
+	<td>
+
+**ResponseListenerInfo**</td>
 	<td>Wraps a listener for BeforeResponse events from the proxy.</td>
 </tr>
-<table>
+</table>
 
 You must enable the HTTP proxy before you can start using it. This setting is turned off by default. This can be done either by adding the setting to your .config file or modifying the setting in the Settings object. To add the setting to your .config file add this to your .config file:
 
 
-```XML
+````XML
 <WebAii.Settings
     Manager.Settings.Web.UseHttpProxy="true"
 />
-```
+````
 
 To enable this setting in the Settings object, add code to your initialization section like this:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -72,8 +86,8 @@ settings.Web.UseHttpProxy = true;
  
 // Now call Initialize again with your updated settings object
 Initialize(settings, new TestContextWriteLine(this.TestContext.WriteLine));
-```
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -84,12 +98,12 @@ settings.UseHttpProxy = True
  
 ' Now call Initialize again with your updated settings object
 Initialize(settings, New TestContextWriteLine(AddressOf Me.TestContext.WriteLine))
-```
+````
 
 
 Now that we have the HTTP proxy turned on we can start using it. Here's an example of how we would detect that a response coming back from the web server is an image response.
 
-```C#
+````C#
 [TestMethod]
 public void ImageDetection()
 {
@@ -121,8 +135,8 @@ private void CheckTypeForImage(object sender, HttpResponseEventArgs e)
             e.Response.Headers["Content-Type"]));
     }
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub ImageDetection()
     ' Launch a new browser window
@@ -147,11 +161,11 @@ Private Sub CheckTypeForImage(ByVal sender As Object, ByVal e As HttpResponseEve
         Log.WriteLine([String].Format("Not an image; MIME type: {0}", e.Response.Headers("Content-Type")))
     End If
 End Sub
-```
+````
 
 Let's go one step further. Suppose we want to verify that all of the images on the web page were smaller than 40Kb. We can accomplish this using code like this:
 
-```C#
+````C#
 [TestMethod]
 public void CheckImageSize()
 {
@@ -177,8 +191,8 @@ private void Check(object sender, HttpResponseEventArgs e)
         _imageTooLarge = true;
     }
 }
-```
-```VB
+````
+````VB
 <TestMethod()> _
 Public Sub CheckImageSize()
     ' Add our HTTP response event handler
@@ -201,6 +215,6 @@ Private Sub Check(ByVal sender As Object, ByVal e As HttpResponseEventArgs)
         _imageTooLarge = True
     End If
 End Sub
-```
+````
 
 **Note:** If you are using **localhost** in the URL of the **NavigateTo** method it must contain a trailing '.' character like this: ActiveBrowser.NavigateTo("http://localhost./myTestPage") . This is an IE limitation where all URL's must contain a '.' character in them to be recognized properly when a proxy is in place.
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/Annotator.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/Annotator.md
index dc08da54..41fe9aa2 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/Annotator.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/Annotator.md
@@ -4,59 +4,59 @@ page_title: Annotator
 description: "Test Studio Testing Framework annotated coded tests runs. Use the Annotator to highlight the target element for each action from the coded test."
 position: 1
 ---
-#Annotator#
+# Annotator
 
 The annotator displays in the browser window the actions that Telerik Testing Framework is performing along with highlighting the UI element that it is acting upon. If the action does not involve a UI element (such as navigating to a URL or creating a cookie) the action is displayed at the top of the browsers window. Here is what the annotator looks like in action:
 
 ![Annotation][1]
 
-##Activating the Annotator via the Application .config File##
+## Activating the Annotator via the Application .config File
 
 There are 2 methods to activating Telerik Testing Framework's automatic annotator. The simplest method is to activate it via the application .config file. By setting "annotateExecution" to true, the framework turns on the annotator and begins annotating all actions in the browser
 
-```XML
+````XML
 <WebAii.Settings
   annotateExecution="true"
 />
-```
+````
 
-##Activating the Annotator Programmatically##
+## Activating the Annotator Programmatically
 
 The next method is to turn on the annotator programmatically in your application. This is accomplished by placing this simple line of code in your unit test:
 
-```C#
+````C#
 // Enable Annotated Execution.
 Manager.Settings.AnnotateExecution = true;
 // Disable Annotated Execution.
 Manager.Settings.AnnotateExecution = false;
-```
-```VB
+````
+````VB
 ' Enable Annotated Execution.
 Manager.Settings.AnnotateExecution = True
 ' Disable Annotated Execution.
 Manager.Settings.AnnotateExecution = False
-```
+````
 
-##Performing Your Own Annotation##
+## Performing Your Own Annotation
 
 You can also perform your own annotation programmatically using the Annotator class. First you must create an Annotator object passing into it which browser window to display annotation in. Once you have an Annotator object you can call one of the annotate functions. For example:
 
-```C#
+````C#
 Annotator myAnnotator = new Annotator(ActiveBrowser);
 myAnnotator.Annotate("This annotation message appears at the top of the browser document window");
 myAnnotator.Annotate("This annotation message appears at the top left corner of the browser document window",
      350, OffsetReference.TopLeftCorner);
 myAnnotator.Annotate(new Point(100, 300), "This annotation message appears under the point at 100,300 in the browser document window");
 myAnnotator.Annotate(Find.ById("btn1").GetRectangle(), "This annotation highlights the Color On button");
-```
-```VB
+````
+````VB
 Dim myAnnotator As Annotator = New Annotator(ActiveBrowser)
 myAnnotator.Annotate("This annotation message appears at the top of the browser document window")
 myAnnotator.Annotate("This annotation message appears at the top left corner of the browser document window", _
                       350, OffsetReference.TopLeftCorner)
 myAnnotator.Annotate(New Point(100, 300), "This annotation message appears under the point at 100,300 in the browser document window")
 myAnnotator.Annotate(Find.ById("btn1").GetRectangle(), "This annotation highlights the Color On button")
-```
+````
 
 [1]: /img/testing-framework/write-tests-in-code/intermediate-topics-wtc/annotator/fig1.png
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support.md
index bcc5dd8b..758610f7 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/ajax-support.md
@@ -4,7 +4,8 @@ page_title: Ajax Support
 description: "Test Studio Testing Framework support in coded tests for AJAX calls."
 position: 1
 ---
-#Ajax Support#
+
+# Ajax Support
 
 Ajax is one of the latest and fastest growing web development technologies that is fueling today's Web 2.0 era. The technology enables developers to build great and rich web content. However at the same time it adds great complexity to the testing methods required to validate the web applications that use it. To a certain extent, websites that rely heavily on Ajax can no longer rely on using the legacy HTTP record/replay methods to test the entire functionality given that major portions of the website logic are executed within the browser JavaScript engine and in some cases no HTTP requests are being made to the server at all!
 
@@ -26,23 +27,23 @@ Telerik Testing Framework has been built from the ground up with features like A
 
 * **Attach event handlers** directly to JavaScript events. This topic is covered in detail under <a href="/testing-framework/write-tests-in-code/advanced-topics-wtc/javascript-wtc/javascript-events" target="_blank">JavaScript Events</a>.
 
-##Waiting on DOM Changes: WaitForElement(s)##
+## Waiting on DOM Changes: WaitForElement(s)
 
 **WaitForElement**(s) is a great method to use when trying to suspend test execution until a certain element is present or has changed or a specific value of a certain attribute for an element has been set (or even a combination of values). This is a common scenario when automating Ajax applications. WaitForElement(s) requires a basic understanding of <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-objects" target="_blank">FindParams and how to define them</a>. Once you know how to craft FindParam's, you will be able to write custom and rich wait routines using a consistent pattern.
  
 Let's examine a couple of examples to illustrate how WaitForElement(s) is used. Assume that you are waiting for a table to be inserted in your DOM tree at a certain location and you want to wait until the whole table is built including the sixth row. The following is the DOM segment before the Ajax call is made:
 
-```HTML
+````HTML
 <!--testregion id="ajaxupdate"-->
 <div>
 </div>
 <!--/testregion-->
-```
+````
 
 Here is the DOM after the call has been made:
 
 
-```HTML
+````HTML
 <!--testregion id="ajaxupdate"-->
 <div>
   <table>
@@ -55,11 +56,11 @@ Here is the DOM after the call has been made:
    </table>
 </div>
 <!--/testregion-->
-```
+````
 
 The following code will perform this wait:
 
-```C#
+````C#
 // Get the ajaxupdate region.
 // Notice how using a testregion simplifies our identification and makes it
 // more isolated to the current DOM region being targeted and less prone
@@ -75,8 +76,8 @@ FindParam sixth_row = new FindParam("tr", 6);
 // perform the wait for both elements. WaitForElements() takes 1-N FindParam objects to
 // to wait for.
 ActiveBrowser.Actions.WaitForElements(500, ajaxupdate, false, table, sixth_row);
-```
-```VB
+````
+````VB
 ' Get the ajaxupdate region.
 ' Notice how using a testregion simplifies our identification and makes it
 ' more isolated to the current DOM region being targeted and less prone
@@ -92,13 +93,13 @@ Dim sixth_row As FindParam = New FindParam("tr", 6)
 ' perform the wait for both elements. WaitForElements() takes 1-N FindParam objects to
 ' to wait for.
 ActiveBrowser.Actions.WaitForElements(500, ajaxupdate, False, table, sixth_row)
-```
+````
 
 In the above code sample, we used <a href="/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/introduction" target="_blank">TestRegions</a> to make our automation simpler and targeted at the DOM region we are interested in. If you choose to not use TestRegions, you can simply use the WaitForElement(s) overload that takes in only the FindParam and the Timeout. In that case, all identification will be performed with reference to the root element of the DomTree.
  
 You can also use "Chained Identification" to wait for an element. For example if we have a DOM segment that looks like the sample below: 
 
-```HTML
+````HTML
 <spanid="myspan">
    <div>
      <table>
@@ -111,11 +112,11 @@ You can also use "Chained Identification" to wait for an element. For example if
      </table>
    </div>
  </span>
-```
+````
 
 ... and we want to wait until we have six rows available, then we can use chained identification as follows:
 
-```C#
+````C#
 // First find the span by id
 FindParam myspan = new FindParam("id=myspan");
   
@@ -124,8 +125,8 @@ FindParam sixth_row = new FindParam("tr", 5);
   
 // perform the wait for the row element.
 ActiveBrowser.Actions.WaitForElement(new FindParam[] { myspan, sixth_row }, 500);
-```
-```VB
+````
+````VB
 ' First find the span by id
 Dim myspan As FindParam = New FindParam("id=myspan")
   
@@ -134,21 +135,21 @@ Dim sixth_row As FindParam = New FindParam("tr", 5)
   
 ' perform the wait for the row element.
 ActiveBrowser.Actions.WaitForElement(New FindParam() {myspan, sixth_row}, 500)
-```
+````
 
 The above scenario is one of the most common when testing Ajax apps. Therefore, the WaitForElement provides an easy to use overload for these common scenarios where you need to first identify an element by id/name then validate a certain attribute list. This helps reduce the lines of code each time you need to identify an element. If you need a more complex identification, you can use chained identification as described above.
 
-##Retrieving Dynamic Property Values Directly From the DOM##
+## Retrieving Dynamic Property Values Directly From the DOM
 
 When using Ajax the application, in most scenarios, updates the document's DOM using JavaScript. The DOM tree provided to your test code by Telerik Testing Framework is automatically updated after each command gets executed against the browser if Browser.AutoDomRefresh property is set to "true," which is the default value. In most scenarios the DOM tree is the latest up-to-date DOM tree from the browser. In cases where the DOM tree is updated without using Telerik browser commands (for example, the page auto-refreshes based on an internal timer, or you are using Pure UI automation), you can always refresh the DOM by calling Browser.RefreshDomTree().
  
 In some scenarios that might not even be enough. For example, you want to retrieve a property value that doesn't usually get emitted into the DOM when serialized like the default or inherited values of an unset property or in Firefox the 'value' property of input tags.
  
-To help address this issue and potentially other issues, the Telerik infrastructure supports a generic and simple method of retrieving any property of any element directly from the live DOM hosted in the browser. Each Element object in the Telerik Testing Framework has a GetValue<T>() method that you can use to evaluate any custom or standard attribute of your Dom element at any point in your test code or application.
+To help address this issue and potentially other issues, the Telerik infrastructure supports a generic and simple method of retrieving any property of any element directly from the live DOM hosted in the browser. Each Element object in the Telerik Testing Framework has a `GetValue<T>()` method that you can use to evaluate any custom or standard attribute of your Dom element at any point in your test code or application.
  
 For example, if you want to retrieve the text set by a user in an input textbox in Firefox, you can simply do the following:
 
-```C#
+````C#
 // Get the element.
 Element input = ActiveBrowser.Find.ById("myinput");
   
@@ -160,8 +161,8 @@ string display = input.GetValue<string>("display");
   
 // Get its 'visibility' property from the DOM
 string visibility = input.GetValue<string>("visibility");
-```
-```VB
+````
+````VB
 ' Get the element.
 Dim input As Element = ActiveBrowser.Find.ById("myinput")
   
@@ -173,17 +174,17 @@ Dim display As String = input.GetValue(Of String)("display")
   
 ' Get its 'visibility' property from the DOM
 Dim visibility As String = input.GetValue(Of String)("visibility")
-```
+````
 
 **Note:** If you are retrieving property values of set attributes available in the serialized DOM string, you should use the GetAttribute() method to retrieve these attributes and their values.
 
-##Browser.WaitForAjax()##
+## Browser.WaitForAjax()
 
 This method will wait for any active AJAX requests to complete.
 
-```C#
+````C#
 Manager.ActiveBrowser.WaitForAjax(30000);
-```
-```VB
+````
+````VB
 Manager.ActiveBrowser.WaitForAjax(30000)
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/configure-browser-In-code.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/configure-browser-In-code.md
index d1aae884..bd35f193 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/configure-browser-In-code.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/configure-browser-In-code.md
@@ -4,11 +4,11 @@ page_title: Configure Browser In Code
 description: "Test Studio Testing Framework supports browser calibration in coded tests. Configure execution browser in code. "
 position: 1
 ---
-#Configure Browser In Code#
+# Configure Browser In Code
 
 Apart from manually configuring each of the browsers for test execution this could be also accomplished in code. 
 
-```C#
+````C#
 //declare string variable to write possible errors in 
 string error;
 // to configure FireFox
@@ -21,12 +21,12 @@ Manager.ConfigureBrowser(BrowserType.InternetExplorer, out error);
 Manager.ConfigureBrowser(BrowserType.Safari, out error);
 // to configure Edge
 Manager.ConfigureBrowser(BrowserType.MicrosoftEdge, out error);
-```
-```VB
+````
+````VB
 Dim error As String
 Manager.ConfigureBrowser(BrowserType.FireFox, error)
 Manager.ConfigureBrowser(BrowserType.Chrome, error)
 Manager.ConfigureBrowser(BrowserType.InternetExplorer, error)
 Manager.ConfigureBrowser(BrowserType.Safari, error)
 Manager.ConfigureBrowser(BrowserType.MicrosoftEdge, error)
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/cookie-support.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/cookie-support.md
index dde313cc..c6d01c9c 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/cookie-support.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/cookie-support.md
@@ -4,7 +4,7 @@ page_title: Cookie Support
 description: "Test Studio Testing Framework support for retrieving Cookies from browser using the CookieManager class. "
 position: 1
 ---
-#Cookie Support#
+# Cookie Support
 
 Using the CookieManager class you can:
 
@@ -16,71 +16,71 @@ Using the CookieManager class you can:
 
 * Delete a cookie in the browser
 
-##Retrieving Cookies##
+## Retrieving Cookies
 
 There are two functions that can be used to retrieve cookies from the browser:
 
 
-```C#
+````C#
 public CookieCollection GetCookies (string url)
 public CookieCollection GetCookies (Uri uri)
-```
-```VB
+````
+````VB
 Public Function GetCookies(ByVal url As String) As System.Net.CookieCollection
 Public Function GetCookies(ByVal uri As System.Uri) As System.Net.CookieCollection
-```
+````
 
 These functions retrieve all the cookies from the browser for the specified website. For example:
 
-```C#
+````C#
 // Query the cookie
 System.Net.CookieCollection siteCookies = ActiveBrowser.Cookies.GetCookies("http://www.telerik.com");
-```
-```VB
+````
+````VB
 ' Query the cookie
 Dim siteCookies As System.Net.CookieCollection = ActiveBrowser.Cookies.GetCookies("http://www.telerik.com")
-```
+````
 
-##Creating and Setting Cookies##
+## Creating and Setting Cookies
 
 Below is an example of how to create or set a cookie. If the cookie already exists, it will be overwritten. If it does not exist, a new cookie will be created in the browser:
 
-```C#
+````C#
 // Let's create a new cookie for a url.
 ActiveBrowser.Cookies.SetCookie(new System.Net.Cookie("WebAii", "Rocks", "/", "http://www.telerik.com"));
-```
-```VB
+````
+````VB
 ' Let's create a new cookie for a url.
 ActiveBrowser.Cookies.SetCookie(New System.Net.Cookie("WebAii", "Rocks", "/", "http://www.telerik.com"))
-```
+````
 
-##Deleting Cookies##
+## Deleting Cookies
 
 Here is an example of how to delete a cookie:
 
-```C#
+````C#
 // Now delete the cookie.
 ActiveBrowser.Cookies.DeleteCookie(siteCookies[0]);
-```
-```VB
+````
+````VB
 ' Now delete the cookie.
 ActiveBrowser.Cookies.DeleteCookie(siteCookies(0))
-```
+````
 
 A simple foreach loop can be used to delete all the cookies for a particular website:
 
-```C#
+````C#
 // Purge any cookies associated with this server
 System.Net.CookieCollection cookies = ActiveBrowser.Cookies.GetCookies(ActiveBrowser.Url);
 foreach (System.Net.Cookie cookie in cookies)
 {
     ActiveBrowser.Cookies.DeleteCookie(cookie);
 }
-```
-```VB
+````
+````VB
 ' Purge any cookies associated with this server
 Dim cookies As System.Net.CookieCollection = ActiveBrowser.Cookies.GetCookies(ActiveBrowser.Url)
 For Each cookie As System.Net.Cookie In cookies
      ActiveBrowser.Cookies.DeleteCookie(cookie)
 Next cookie
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/desktop-manager.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/desktop-manager.md
index 718128db..d0dd2811 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/desktop-manager.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/desktop-manager.md
@@ -5,7 +5,7 @@ description: "Test Studio Testing Framework support in coded tests for interacti
 position: 1
 ---
 
-#The Desktop Manager Class#
+# The Desktop Manager Class
 
 The Desktop manager class is used to control interaction between the Windows desktop and the browser. It also contains instances of the Keyboard and Mouse managers. It has the following properties:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/dom-navigation.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/dom-navigation.md
index 605b68ad..acf167c6 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/dom-navigation.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/dom-navigation.md
@@ -4,7 +4,7 @@ page_title: DOM Navigation
 description: "Test Studio Testing Framework DOM Navigation. Use an element from the DOM to navigate to other elements on the page in the coded steps and tests. Get Element parent in code. Get Element sibling in code. Get Element child or children nodes in code"
 position: 1
 ---
-#DOM Navigation#
+# DOM Navigation
 
 Once you have an element, you can navigate to other elements relative to this element. Navigation methods include:
 
@@ -20,7 +20,7 @@ Once you have an element, you can navigate to other elements relative to this el
 Suppose we have some HTML that looks like this:
 
 
-```HTML
+````HTML
 <div id="div1">
   DIV1 TEXT
        <div id="div2">
@@ -30,12 +30,12 @@ Suppose we have some HTML that looks like this:
                <span id="span3" class="style-span-3">SPAN3 TEXT</span>
        </div>
 </div>
-```
+````
 
 
 Here is how we can navigate around the DOM once we have a starting element:
 
-```C#
+````C#
 // Let's start with the span1 element.
 Element span1 = Find.ById("span1");
 Element span2 = span1.GetNextSibling();
@@ -66,8 +66,8 @@ span3 = parentDiv.Children[2];
 Assert.IsTrue(span1.IdAttributeValue.Equals("span1"), string.Format("Actual ID: {0}", span1.IdAttributeValue));
 Assert.IsTrue(span2.IdAttributeValue.Equals("span2"), string.Format("Actual ID: {0}", span2.IdAttributeValue));
 Assert.IsTrue(span3.IdAttributeValue.Equals("span3"), string.Format("Actual ID: {0}", span3.IdAttributeValue));
-```
-```VB
+````
+````VB
 ' Let's start with the span1 element.
 Dim span1 As Element = Find.ById("span1")
 Dim span2 As Element = span1.GetNextSibling()
@@ -98,4 +98,4 @@ span3 = parentDiv.Children(2)
 Assert.IsTrue(span1.IdAttributeValue.Equals("span1"), String.Format("Actual ID: {0}", span1.IdAttributeValue))
 Assert.IsTrue(span2.IdAttributeValue.Equals("span2"), String.Format("Actual ID: {0}", span2.IdAttributeValue))
 Assert.IsTrue(span3.IdAttributeValue.Equals("span3"), String.Format("Actual ID: {0}", span3.IdAttributeValue))
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-expressions.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-expressions.md
index ab881b19..2f3a8932 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-expressions.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-expressions.md
@@ -6,7 +6,7 @@ previous_url: /user-guide/write-tests-in-code/intermediate-topics/element-identi
 position: 1
 ---
 
-#HTML and XAML Find Expressions#
+# HTML and XAML Find Expressions
 
 FindExpression's are the replacement/evolution of FindParam's. We will be using FindExpression's as the base for all element searches in the DOM, HWnd, or control trees (including Translator Locators). The key design goal for FindExpressions is to enable a flexible, rich and extensible search definition pattern that can be used across all of our Telerik technologies. This will enable our customers to carry over their product experience as they move across our product stacks making the learning curve for customers moving from one technology to another minimal.ma
  
@@ -34,30 +34,30 @@ FindExpression's are the following:
 
 6.&nbsp; Can't easily be leveraged for searches within other technologies.
 
-##Basic Concept##
+## Basic Concept
 
 The key to understanding FindExpression's is to understand its basic component: the FindClause. A FindClause is a name/value pair with an optional comparison operator. A FindExpression consists of 1-n FindClauses. For example:
 
-###FindClauses Without Operators###
+### FindClauses Without Operators
 
-```
+````
 TagName=div
 id=bar
 innermarkup=hellothere
-```
+````
 
-###FindClauses With Operators###
+### FindClauses With Operators
 
-```
+````
 name=~bar [name attribute partially contains bar]
 automationid=^hat [the automation id of an element starts with hat]
-```
+````
 
 
 **Note:** The optional operator is ALWAYS the first character after the = in the expression. This special character can be escaped with a preceding ' character if it is meant to be interpreted as a literal character.
 
 
-###Supported Operators###
+### Supported Operators
 
 <table class="docs">
 <tr>
@@ -112,29 +112,29 @@ automationid=^hat [the automation id of an element starts with hat]
 
 The name portion of the clause can be a well known enumeration that a certain technology (i.e. HTML, XAML) recognizes as a certain search pattern. For example, in HTML:
 
-```
+````
 xpath=HTML[0]/div[1]
-```
+````
 
 is interpreted by the HTML search tree as a specific search that requires XPATH interpretation.
 
-```
+````
 automationid=?sam
-```
+````
 
-##Constructing FindExpressions##
+## Constructing FindExpressions
 
-Each technology (HTML, Silverlight, etc.) will define its own FindExpression that inherits from the base FindExpression object. All FindExpression's need only one constructor to define any type of search.
+Each technology (HTML, WPF, or Desktop) will define its own FindExpression that inherits from the base FindExpression object. All FindExpression's need only one constructor to define any type of search.
  
 For example:
  
 Find the HTML element with an id that ends with 'sam' and also has a class attribute that contains bar and also has a text content that does not contain foo.
 
-```C#
+````C#
 HtmlFindExpression expr = new HtmlFindExpression("id=bar","|","tagindex=td:0","|","tagname=img","src=~png");
-```
+````
 
-##Hierarchy Constraint##
+## Hierarchy Constraint
 
 You can also describe a certain hierarchal constraint to be applied against that FindExpression so that the decision on whether a specific element matches a specific translator or not is not solely based on the tag but also takes into consideration its hierarchical position. For example a tag that looks like ```HTML <div class='foo' />```might be part of a grid while at the same time other elements on the page could contain that tag. The only way to distinguish whether that tag is part of the grid is to inspect its parent or child hierarchy.
  
@@ -148,16 +148,16 @@ A hierarchy constraint contains two pieces of data:
  
 For example, suppose we have the following HTML code snippet to deal with:
 
-```HTML
+````HTML
 <div class="bar">
   <div id="foo1">
      <section id="foo2">
          <div class="bar">
-```
+````
 
 Now we want to match the div tag that has class='bar' and its parent's parent has an id='foo1':
 
-```C#
+````C#
 // This expression will locate both p tags at [0] & [3]
 HtmlFindExpression expression = new HtmlFindExpression("class=bar", "tagname=div");
   
@@ -168,8 +168,8 @@ HtmlFindExpression parentExpr = new HtmlFindExpression("id=foo1"); // matches [1
 // -2 signifies two parents up.
 // Note that HierarchyConstraints are [1] based. Zero signifies the target element or reference point.
 expression.AddHierarchyConstraint(new HierarchyConstraint(parentExpr, -2));
-```
-```VB
+````
+````VB
 ' This expression will locate both p tags at [0] & [3]
 Dim expression As New HtmlFindExpression("class=bar", "tagname=div")
   
@@ -180,14 +180,14 @@ Dim parentExpr As New HtmlFindExpression("id=foo1")
 ' -2 signifies two parents up.
 ' Note that HierarchyConstraints are [1] based. Zero signifies the target element or reference point.
 expression.AddHierarchyConstraint(New HierarchyConstraint(parentExpr, -2))
-```
+````
 
 
 The resulting expression now will match [3] ONLY.
  
 Here is a more involved scenario:
 
-```HTML
+````HTML
 <div class="bar">
   <p id="foo1">
     <span id="foo2" />
@@ -199,13 +199,14 @@ Here is a more involved scenario:
     </span>
   </p>
 </div>
-```
+````
 
 If we wish the constraint to match the first child of the parent's parent (i.e. [2]) and to be an 'span' instead, that is also doable.
  
 The path in that case is -2, 1 => Two parents up, one down at index 1. (Or -1, -1, 1, both are the same) and the second FindExpression will be "TagName=span" instead of "id=foo1".
 
-##HtmlFindExpression Types##
+
+## HtmlFindExpression Types
 
 The following is a list of the types that can appear on the left side of the expression in HtmlFindExpressions:
 
@@ -229,7 +230,8 @@ The following is a list of the types that can appear on the left side of the exp
 
 * XPath - search for an element at the specified XPath expression.
 
-##XamlFindExpression Types##
+
+## XamlFindExpression Types
 
 The following is a list of the types that can appear on the left side of the expression in XamlFindExpressions:
 
@@ -247,4 +249,3 @@ The following is a list of the types that can appear on the left side of the exp
 
 * XamlPath - Uses a XAML path expression like XamlPath=/radtabcontrol[automationid=Tabs]/grid[0]/raddockpanel[0]/layouttransformcontrol[name=HeaderDockedElement]
 
-* For more information on using XamlFindExpressions, see <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/locating-elements" target="_blank">Locating Elements</a>.
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-as-xml-data.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-as-xml-data.md
index dec9e998..57953c79 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-as-xml-data.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-as-xml-data.md
@@ -4,7 +4,8 @@ page_title: FindParam as XML Data
 description: "Test Studio Testing Framework FindParam Data Sources."
 position: 1
 ---
-#FindParams as External XML Data Sources#
+
+# FindParams as External XML Data Sources
 
 **Note:** This topics assumes a basic understanding of FindParam objects. It is recommended to read the <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements" target="_blank">Finding Page Elements</a> topic first before reading this topic.
  
@@ -18,12 +19,13 @@ By doing so we can:
 
 * Enable the same test logic/code to run against different versions of the same application that differ in UI layout or DOM structure. By versioning the external data sources per each different application version, we can configure our tests to consume different data source versions for each application being tested without having to duplicate test code and worry about maintaining multiple code bases. This approach can dramatically cut down maintenance and support costs especially for product teams that maintain and service multiple versions of the same application. It is also a great approach to take on if you are starting a new project and you think you will end up having to support multiple versions of that product in the future.
  
-##Building FindParam Data Sources##
+
+## Building FindParam Data Sources
 
 We currently don't offer any UI design tools that can help build these data sources directly from your application. Therefore, to build these data source we need to craft our FindParams manually and then using FindParam and FindParamCollection XML serialization methods, store the generated sources to our storage medium of choice (i.e. database, file system ...etc).
 The sample below shows an example of how to build an XML file that can be later consumed by your test code to identify elements to use in the automation logic.
 
-```C#
+````C#
 // First we build the list of FindParam objects we want serialized
 // and add them to a FindParamCollection object.
   
@@ -46,14 +48,14 @@ paramCol.Save(@"C:\AppParams.xml");
 // in your choice of storage medium.
 //
 // string serializedParams = paramCol.ToXml();
-```
+````
 
-##Consuming the Data Sources##
+## Consuming the Data Sources
 
 The are three different methods you can use to consume the data source generated above. We can deserialize the data back into a FindParamCollection object and then select one of these FindParams to locate a specific element on the page.
 
 
-```C#
+````C#
 // Given we already have a datasource of FindParam's stored on a different medium,
 // we can deserialize the data back into a FindParamCollection object and then
 // select one of these FindParam's to locate a specific element on the page
@@ -65,12 +67,12 @@ Element inputText = ActiveBrowser.Find.ByParam(paramCol["InputTextBox"]);
   
 // Perform your automation actions on the element.
 ActiveBrowser.Actions.SetText(inputText, "sometext");
-```
+````
 
 Alternatively we can can create a Dictionary lookup object from the external datasource.
 
 
-```C#
+````C#
 
 // FindParams can be completely extracted out of test code and stored in an external xml file. 
 // 
@@ -96,11 +98,11 @@ Assert.IsTrue(elements["ProgramsTable"].ElementType == ElementType.Table);
 // Note:
 // 1. If you have the XML string stored in a DataBase, you can use the Find.FromXml() 
 //    to find these elements directly from the string.
-```
+````
 
 Finally we can load the external datasource using a FindParamAttribute.
 
-```C#
+````C#
 // The SupportFiles\FindElementsFromFile.xml shows a sample xml file with two FindParams defined; one for
 // the MainTable and the other for ProgramsTable.
    
@@ -112,9 +114,9 @@ Find.All(true);
 Assert.IsTrue(Find.Elements.Count == 2);
 Assert.IsTrue(Find.Elements["MainTable"].ElementType == ElementType.Table);
 Assert.IsTrue(Find.Elements["ProgramsTable"].ElementType == ElementType.Table);
-```
+````
 
-##Managing and Organizing Data Sources for an Entire Application##
+## Managing and Organizing Data Sources for an Entire Application
 
 There are probably many ways you can think of to organize your external data sources for your an entire application. We though want to discuss three approaches you might want to consider. You can organize your external sources:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-objects.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-objects.md
index f027c0f5..6cc2914e 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-objects.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-objects.md
@@ -4,21 +4,22 @@ page_title: FindParam Objects
 description: "Test Studio Testing Framework FindParam Objects in coded tests. Use FindParam Objects to describe the searched element."
 position: 1
 ---
-#FindParam Objects#
+
+# FindParam Objects
 
 All the identification methods exposed by the 'Find' object described above use FindParam objects under the covers to describe the desired element within the DOM tree to Telerik's identification engine. The engine itself can only understand searches using FindParam's. You can directly invoke element searches against the identification engine using the Find.ByParam() or Find.AllByParam() methods. When FindParam's are used directly to define a search, they enable a richer, consistent and more flexible way to describe a certain element than just the Find.Byxx() which were designed to cater for the most common scenarios. For example, if you want to describe the second 'div' on a page with class=myclass. You can't directly do that using the Find.Byxx() methods unless you first find the second 'div' element then inspect its attributes to figure out if the class attribute is set 'myclass'. With FindParam objects, you can simply describe that search by:
 
-```C#
+````C#
 // The find object will only return an element if all conditions
 // exist. Else NULL.
 Element e = Find.ByParam(new FindParam("div", 1,"class=myclass"));
 Assert.IsNotNull(e);
-```
+````
 
 
 Here are some other examples:
 
-```C#
+````C#
 Element e;
   
 // Find.ById() is implemented as
@@ -36,10 +37,10 @@ FindParam p = new FindParam(FindType.Content, "p:Some Data", "title=~Div", "clas
 p.ContentType = FindContentType.InnerMarkup;
 e = Find.ByParam(p);
 Assert.IsNotNull(e);
-```
+````
 
 
-##Chained Identification##
+## Chained Identification
 
 Chained identification is simply using multiple FindParam objects (as in a chain) to identify an element. Chained identification is used to help simplify locating nested and complex markup elements and promote a more robust approach for element identification in these scenarios.
  
@@ -49,7 +50,7 @@ To help understand chained identification better, let's take a concrete example.
  
 Many times developers find themselves struggling with a markup nesting similar to the one below; particularly on rich content websites when heavy styling is applied or when using dynamic web development technologies like ASP.NET. In the sample below, the outer table contains an id attribute but the rest of the nested tables don't. Let's assume a test needs to access the inner most table to verify its content. Instead of looking up the overall 'table' occurrence index over an entire document which can easily become difficult on large complex pages, we would like to first identify the "table1" element by its id and then simply count two table occurrences from it (occurrence index 1) to locate the inner table.
 
-```HTML
+````HTML
 <table id="table1">
    <tr>
      <td>
@@ -75,11 +76,11 @@ Many times developers find themselves struggling with a markup nesting similar t
      </td>
    </tr>
 </table>
-```
+````
 
 Below is the chained identification code to accomplish that.
 
-```C#
+````C#
 // Generic chained identification
 FindParam idtable1 = new FindParam("id=table1");
   
@@ -90,8 +91,8 @@ FindParam innertable = new FindParam("table", 1);
 Element innerTable = Find.ByParam(new FindParam[] { idtable1, innertable });
 Assert.IsNotNull(innertable);
 Assert.AreEqual(3, innerTable.Children[0].Children.Count);
-```
+````
 
-##Defining FindParam Objects Outside Test Code (i.e. FindParam Serialization)##
+## Defining FindParam Objects Outside Test Code (i.e. FindParam Serialization)
 
 FindParam objects support serialization including the FindParamCollection. This support allows you to define your FindParam's outside your test code and consume them as data sources. This enables you to be more agile when changes are made to your application by simply updating the xml that defines your FindParam objects. This topic is covered in more detail under <a href="/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/find-param-as-xml-data" target="_blank">FindParams as External Xml DataSources</a>.
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements.md
index 9c9a7b90..7066ebb8 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/finding-page-elements.md
@@ -6,33 +6,7 @@ previous_url: /user-guide/write-tests-in-code/intermediate-topics/element-identi
 position: 1
 ---
 
-<style>
-table.docs {
-font-family: verdana,arial,sans-serif;
-font-size:11px;
-color:#333333;
-border: 1px solid #dbdbdb;
-border-collapse: collapse;
-table-layout: fixed;
-width: 900px;
-
-}
-table.docs th {
-color:#fff;
-background-color:#ed8200;
-border: 1px solid #dbdbdb;
-padding: 8px;
-}
-table.docs tr {
-background-color:#ffffff;
-}
-table.docs td {
-border: 1px solid #dbdbdb;
-padding: 8px;
-}
-</style>
-
-# Finding Page Elements #
+# Finding Page Elements 
 
 Telerik Testing Framework provides one of the richest markup identification infrastructures currently available on the market. It builds on top of commonly known element identification methods like 'getElementById', 'getElementByName' or 'XPath' and extends them to provide identification routines that cater more to application automation scenarios. In addition to maintaining a simple and easy to use set of APIs, Telerik Testing Framework introduces a consistent and extensible way to build identification and persist it using 'FindParam' objects.
 
@@ -40,7 +14,7 @@ All the Find.Byxxx methods now support LINQ queries.
 
 It is important to understand how Telerik's identification method works because that understanding will allow you to exploit the power of these identification methods to build robust automation quicker.
 
-##Element Identification Overview##
+## Element Identification Overview
 
 The following identification methods are supported:
 
@@ -49,56 +23,61 @@ The following identification methods are supported:
 	<th style="width:165px;">Methods</th><th style="width:200px;">Description</th><th>Example</th>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ById_System_String_" target="_blank">**Find.ById()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ById_System_String_" target="_blank">Find.ById()</a></td>
 	<td>Searches for an element contained in a markup document using its set 'id' attribute. When the desired 'id' matches an element's id, the element is returned - identical to getElementById</td>
 <td>
-```	
+
+````C#
 // Find element with id=input1
 Element e = Find.ById("input1");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByName_System_String_" target="_blank">**Find.ByName()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByName_System_String_" target="_blank">Find.ByName()</a></td>
 	<td>Searches for an element contained in a markup document using its set 'name' attribute. When the desired 'name' matches an element's name, the element is returned</td>
 <td>
-```	
+
+````C#
 // Find element with name=goButton
 Element e = Find.ByName("goButton")
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByImage_System_Drawing_Image_System_Double_System_Int32_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">**Find.ByImage()**</a><br>
-    <a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByImage_System_Drawing_Image_System_Double_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">**Find.AllByImage()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByImage_System_Drawing_Image_System_Double_System_Int32_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">Find.ByImage()</a><br>
+    <a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByImage_System_Drawing_Image_System_Double_System_Boolean_System_Drawing_Point_System_Int32_" target="_blank">Find.AllByImage()</a></td>
 	<td>Searches for an element or 'All' elements that look like a predefined image</td>
 <td>
-```
+
+````C#
 // Specify the predefined image on which the search will be based
 System.Drawing.Image img1 = System.Drawing.Image.FromFile(@"C:\sampleImg.png");
 // Find an element that looks like the predefind image
 var elementImg1 = Manager.ActiveBrowser.Find.ByImage(img1, 70); // the second argument is the threshold % to use, while searching for the image
 // Cast the found element to be able to use it. The type of located element needs to be specified.
 HtmlButton btn1 = elementImg1.As<HtmlButton>();
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByTagIndex_System_String_System_Int32_" target="_blank">**Find.ByTagIndex()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByTagIndex_System_String_System_Int32_" target="_blank">Find.ByTagIndex()</a></td>
 	<td>Searches for an element using its tag name occurrence index. Finds the element at the specified occurrence index and returns it. This method uses zero based indexing.</td>
 <td>
-```	
+
+````C#
 // Find the 3rd occurrence of table tag
 Element table = Find.ByTagIndex("table", 2);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByAttributes_System_String___" target="_blank">**Find.ByAttributes()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByAttributes_System_String___" target="_blank">**Find.AllByAttributes()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByAttributes_System_String___" target="_blank">Find.ByAttributes()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByAttributes_System_String___" target="_blank">Find.AllByAttributes()</a></td>
 	<td>Searches for an element or 'All' elements using an 'exact' or 'partial' list of attribute values (You can specify 1-N attribute/value pairs). When all attribute values match, the element or collection of elements is returned.</td>
 <td>
-```	
+
+````C#
 // Find the first element with attribute class=myclass
 Element e = Find.ByAttributes("class=myclass");
 // Find the first element with attribute class=myclass
@@ -106,15 +85,16 @@ Element e = Find.ByAttributes("class=myclass");
 Element e = Find.ByAttributes("class=myclass", "src=~foo.gif");
 // Find all elements with class=myclass and src has a partial foo.gif
 IList<Element> allbtns = Find.AllByAttributes("class=myclass", "src=~foo.gif");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByContent_System_String_" target="_blank">**Find.ByContent()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_AllByContent_System_String_" target="_blank">**Find.AllByContent()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByContent_System_String_" target="_blank">Find.ByContent()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_AllByContent_System_String_" target="_blank">Find.AllByContent()</a></td>
 	<td>Searches for an element or 'All' elements using 'exact', 'partial' or 'regex' of the element content. The element content can be: InnerText, InnerMarkup, OuterMarkup, TextContent (default), StartTagContent.</td>
 <td>
-```	
+
+````C#
 // Find element with TextContent has literal value: Education
 // l: signifies literal
 Element e = Find.ByContent("l:Education");
@@ -139,64 +119,68 @@ IList<Element> alle = Find.AllByContent("p:car")
 // TextContent of div1 : Text1 {non-recursive}
 //
 // Default for ByContent is TextContent which is the most common usage.
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">**Find.ByExpression()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">**Find.AllByExpression()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">Find.ByExpression()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByExpression_ArtOfTest_WebAii_Core_HtmlFindExpression_" target="_blank">Find.AllByExpression()</a></td>
 	<td>Searches for an element or 'All' elements matching an HtmlFindExpression. The HtmlFindExpression cannot use any type of hierarchical expressions including tag index path expressions, HTML path expressions, and XPath expressions.</td>
 <td>
-```	
+
+````C#
 // Create an HtmlFindExpression element
 HtmlFindExpression expr = new HtmlFindExpression("id=?sam","class=~bar","textcontent=!foo");
 // Return all elements matching HtmlFindExpression
 IList<Element> allSams = Find.AllByExpression(expr);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByXPath_System_String_" target="_blank">**Find.ByXPath()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByXPath_System_String_" target="_blank">**Find.AllByXPath()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByXPath_System_String_" target="_blank">Find.ByXPath()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByXPath_System_String_" target="_blank">Find.AllByXPath()</a></td>
 	<td>Searches for an element or 'All' elements using an XPath expression. WebAii supports the .NET Framework XPath implementation.</td>
 <td>
-```	
+
+````C#
 // Find the banner img element
 Element img = Find.ByXPath("//body[1]/table[1]/tbody[1]/tr[1]/td[1]/img[1]");
 // Find all times with id=div
 IList<Element> allDivs = Find.AllByXPath("/descendant::node()[starts-with(@id,'div')]");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCssSelector_System_String_" target="_blank">**Find.ByCssSelector()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCssSelector_System_String_" target="_blank">**Find.AllByCssSelector()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCssSelector_System_String_" target="_blank">Find.ByCssSelector()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCssSelector_System_String_" target="_blank">Find.AllByCssSelector()</a></td>
 	<td>Searches for an element or 'All' elements using a css selector query.</td>
 <td>
-```	
+
+````C#
 // Find the active link
 HtmlAnchor activeLink = Find.ByCssSelector<HtmlAnchor>("a:active");
 // Find all links
 IList<HtmlAnchor> allLinks = Find.AllByCssSelector<HtmlAnchor>("a"); 
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByTagName_System_String_" target="_blank">**Find.AllByTagName()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByTagName_System_String_" target="_blank">Find.AllByTagName()</a></td>
 	<td>Searches for 'All' elements with the specified tag name and returns it as a list of elements.</td>
 <td>
-```	
+
+````C#
 // Return all img elements
 IList<Element> allimg = Find.AllByTagName("img");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByNodeIndexPath_System_String_" target="_blank">**Find.ByNodeIndexPath()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByNodeIndexPath_System_String_" target="_blank">Find.ByNodeIndexPath()</a></td>
 	<td>Searches for an element using dom tree node index paths. This identification is done using an xpath like approach that simply describes the hierarchy path to a specific element using the node index within the hierarchy without having to specify the tag name at each level. This identification method can be chosen in cases where a segment of the DomTree hierarchy at a specific location is consistent but element type changes. For example, if an element you are trying to target is the direct child of another element that fluctuates between a span and div, you can choose this identification method to provide a consistent way to identify that element.</td>
 <td>
 
-```	
+````C#
 Given this DOM:
 
  <referenceElement>
@@ -218,25 +202,27 @@ Given this DOM:
 
 // We can find the <target></target> element by:
 Element target = Find.ByNodeIndexPath("0/2/0/1");
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_FromCollection_ArtOfTest_WebAii_ObjectModel_FindExpressionCollection_ArtOfTest_WebAii_Core_HtmlFindExpression__" target="_blank">**Find.FromCollection()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_FromCollection_ArtOfTest_WebAii_ObjectModel_FindExpressionCollection_ArtOfTest_WebAii_Core_HtmlFindExpression__" target="_blank">Find.FromCollection()</a></td>
 	<td>Finds all elements with the FindParams in the passed in collection.</td>
 <td>
-```	
+
+````C#
 FindParamCollection col = FindParamCollection.LoadFromXml(xml);
 return this.FromCollection(col);
-```
+````
 </td>
 </tr>
 <tr>
-	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">**Find.ByCustom()**</a><br>
-	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">**Find.AllByCustom()**</a></td>
+	<td><a href="/api/artoftest.webaii.core.find.html#collapsible-ArtOfTest_WebAii_Core_Find_ByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">Find.ByCustom()</a><br>
+	<a href="/api/artoftest.webaii.core.find.html#ArtOfTest_WebAii_Core_Find_AllByCustom_System_Predicate_ArtOfTest_WebAii_ObjectModel_Element__" target="_blank">Find.AllByCustom()</a></td>
 	<td>Searches for an element or 'All' elements using a custom predicate.</td>
 <td>
-```	
+
+````C#
 // Find the first input button having an ID of 'input1'
 HtmlInputButton btn = Find.ByCustom<HtmlInputButton>(
     delegate(HtmlInputButton e)
@@ -248,12 +234,12 @@ HtmlInputButton btn = Find.ByCustom<HtmlInputButton>(
     }
 );
 Assert.IsNotNull(btn);
-```
+````
 </td>
 </tr>
-<table>
+</table>
 
-##Identification Methods Usage##
+## Identification Methods Usage
 
 Telerik Testing Framework identification methods are accessible using the **Find** object that is exposed as a property off of the 'Browser' object : *Manager.ActiveBrowser.Find.Byxx(...)* and also as a property off of each TestRegion object : *TestRegion.Find.Byxx(...)*.
 
@@ -261,7 +247,7 @@ The difference between the Find object off of the Browser class (Root Base Ident
 
 With TestRegions, depending on the areas of the application that each automated test is targeting, you can use different Find objects to give each test a greater level of independence and shield it from product changes outside its target area. This topic is discussed in greater details in <a href="/testing-framework/write-tests-in-code/advanced-topics-wtc/test-regions-wtc/introduction" target="_blank">Introduction to TestRegions</a>.
 
-##Matching Syntax Used in Parameters##
+## Matching Syntax Used in Parameters
 
 The Byxxx functions that take a nameValuePairs parameter recognizes the following matching syntax:
 
@@ -281,11 +267,11 @@ The Byxxx functions that take a content string parameter recognizes the followin
 
 * Prefix the string parameter with 'x:' for regular expression matching. e.g. 'x:[*foo*]' will match any content containing the string 'foo' in the middle of it. For more information about regular expressions see <a href="http://msdn.microsoft.com/en-us/library/2k3te2cs.aspx" target="_blank">this MSDN article</a>.
 
-##Identification Sample##
+## Identification Sample
 
 To help illustrate the above identification methods, let's use the following sample application. Note that this application uses TestRegions excessively to allow it to demonstrate the different identification methods that can be performed using both **RBI** and **RGBI**:
 
-```HTML
+````HTML
 <!DOCTYPE html>
 <html>
 <head>
@@ -329,11 +315,11 @@ To help illustrate the above identification methods, let's use the following sam
 <!--/testregion-->
 </body>
 </html>
-```
+````
 
 The code below shows the different methods you can use in your test code to identify elements. Note in the sample below, we are using Visual Studio's Assert class to demonstrate how different objects can be identified differently and to illustrate how to scope the identification with TestRegions using RGBI and across the entire document DomTree using RBI.
 
-```C#
+````C#
 // Set the short-cuts to the main automation objects.
 Browser brwser = mgr.ActiveBrowser;
 Find rootFind = brwser.Find;
@@ -387,8 +373,8 @@ Assert.IsTrue(rootFind.ByNodeIndexPath("1/0/0").TagName.Equals("div", StringComp
   
 //*** Using name
 Assert.IsNull(r1.Find.ByName("bla"));
-```
-```VB
+````
+````VB
 ' Set the short-cuts to the main automation objects.
 Dim brwser As ArtOfTest.WebAii.Core.Browser = Manager.ActiveBrowser
 Dim rootFind As Find = brwser.Find
@@ -442,4 +428,4 @@ Assert.IsTrue(rootFind.ByNodeIndexPath("1/0/0").TagName.Equals("div", StringComp
   
 '*** Using name
 Assert.IsNull(r1.Find.ByName("bla"))
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/linq-queries.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/linq-queries.md
index b288095f..819aae8f 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/linq-queries.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/element-identification-wtc/linq-queries.md
@@ -5,8 +5,7 @@ description: "Test Studio Testing Framework LINQ Queries"
 position: 1
 ---
 
-
-#LINQ Queries#
+# LINQ Queries
 
 The Find.Byxxx methods now support Language-Integrated Query (LINQ) queries. Some of the Find functions are intended to be used by LINQ queries only. These include:
 
@@ -15,21 +14,39 @@ The Find.Byxxx methods now support Language-Integrated Query (LINQ) queries. Som
 	<th>Methods</th><th>Description</th><th>Example</th>
 </tr>
 <tr>
-	<td>**AllElements**</td>
-	<td>Gets a IEnumerable for all elements to be used for LINQ queries.</td>
-	<td>var inlineStyledElements = Find.AllElements().Where(element =><br>
-	element.ContainsAttribute("style"));</td>
+<td>
+
+**AllElements**</td>
+<td>
+
+Gets a `IEnumerable` for all elements to be used for LINQ queries.</td>
+<td>
+
+````C#
+var inlineStyledElements = Find.AllElements().Where(element =>
+element.ContainsAttribute("style"));
+````
+</td>
 </tr>
 <tr>
-	<td>**AllControls**</td>
-	<td>Gets an IEnumerable for TControl to be used for LINQ queries. This will return only elements that are convertible to TControl.</td>
-	<td>var images = Find.AllControls<HtmlImage>();</td>
+<td>
+
+**AllControls**</td>
+<td>
+
+Gets an `IEnumerable` for `TControl` to be used for LINQ queries. This will return only elements that are convertible to TControl.</td>
+<td>
+
+````C#
+var images = Find.AllControls<HtmlImage>();
+````
+</td>
 </tr>
-<table>
+</table>
 
 Using LINQ we can create strongly typed advanced queries with intellisense support that we couldn't before. The most basic LINQ example is something like this:
 
-```C#
+````C#
 // Find all images on a page.
 var images = Find.AllControls<HtmlImage>();
  
@@ -37,12 +54,12 @@ foreach (HtmlImage img in images)
 {
     // Do what you want with each img.
 }
-```
+````
 
 
 We can also use lambda expressions like this:
 
-```C#
+````C#
 // Find the first element that contains "Go Google"
 Element el = Find.ByCustom(e => e.TextContent.Contains("Go Google"));
   
@@ -66,4 +83,4 @@ Assert.IsTrue(rd.Count > 0);
 // Fetch a list of HTML anchor's that contain 'a' in the ID
 IList<Element> li = (from b in Find.AllElements() where b.IdAttributeValue.Contains("a") select b).ToArray();
 Assert.IsTrue(li.Count > 0);
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/custom-html-control.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/custom-html-control.md
index eb1b5595..becd5728 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/custom-html-control.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/custom-html-control.md
@@ -4,13 +4,14 @@ page_title: Custom HtmlControl
 description: "Test Studio Testing Framework Custom HtmlControl - design CustomControl class in coded test to interact with custom components on the tested application."
 position: 2
 ---
-#Creating Your Own Custom HtmlControls#
+
+# Creating Your Own Custom HtmlControls
 
 Let's suppose you're testing a web site that uses a third party or custom control. You can easily create your own custom HtmlControl class and then design tests that interact with the custom control via your custom HtmlControl class.
  
 As an example, let's create a custom HtmlControl that wraps the ASP.NET calendar control. We'll give it some methods for reading and controlling the date selection along with a custom ClientSideLocator just for an example. First here's our ASPX web page containing a calendar control that we want to test
 
-```
+````
 <% @ Page Language="C#" MasterPageFile="~/AppMaster.master" Title="Untitled Page" %>
 <% @ Import Namespace="System.Data" %>
 <% @ Register Assembly="ArtOfTest.WebAii.AspNet" Namespace="ArtOfTest.WebAii.AspNet.WebControls" TagPrefix="test" %>
@@ -146,12 +147,12 @@ As an example, let's create a custom HtmlControl that wraps the ASP.NET calendar
      </test:TestRegion>
      <!-- This Data Page Content -->
 </asp:Content>
-```
+````
 
 Let's put together our custom HtmlControl that we can use interact with an ASP.NET calendar control:
 
 
-```C#
+````C#
  public class AspNetCalendar : HtmlTable
        {
            /// <summary>
@@ -282,8 +283,8 @@ Let's put together our custom HtmlControl that we can use interact with an ASP.N
                return GetMonth();
            }
        }
-```
-```VB
+````
+````VB
    Public Class AspNetCalendar
         Inherits HtmlTable
         ''' <summary>
@@ -402,7 +403,7 @@ Let's put together our custom HtmlControl that we can use interact with an ASP.N
             Return GetMonth()
         End Function
     End Class
-```
+````
 
 
 Notice how we derive from an HtmlTable. That way we can take advantage of all the functionality already built into a standard table. We'll just add all the functions useful for our calendar control which include:
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/drag-and-drop.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/drag-and-drop.md
index 94788fde..682c8e02 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/drag-and-drop.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/drag-and-drop.md
@@ -4,11 +4,11 @@ page_title: Drag & Drop
 description: "Test Studio Testing Framework Drag&Drop  actions in coded tests. Use the DragTo() methods to define the desired action to drag an element and drop it on specific point."
 position: 2
 ---
-#How to Drag and Drop#
+# How to Drag and Drop
 
 The HTML element wrapper classes make mouse drag & drop operations significantly easier. There are 7 different drag methods defined:
 
-```C#
+````C#
 public virtual void DragTo(ArtOfTest.WebAii.Controls.HtmlControls.HtmlControl control)
 
 public virtual void DragTo(System.Drawing.Point absolutePoint)
@@ -23,11 +23,11 @@ public virtual void DragTo(ArtOfTest.Common.OffsetReference sourceOffsetReferenc
 public virtual void DragTo(ArtOfTest.Common.OffsetReference sourceOffsetReference, System.Drawing.Point sourceOffset, int destinationOffsetX, int destinationOffsetY)
 
 public virtual void DragTo(ArtOfTest.Common.OffsetReference sourceOffsetReference, int sourceOffsetX, int sourceOffsetY, bool sourcePixelDrag, ArtOfTest.WebAii.Controls.HtmlControls.HtmlControl destination, ArtOfTest.Common.OffsetReference destinationOffsetReference, int destinationOffsetX, int destinationOffsetY, bool destinationPixelDrop)
-```
+````
 
 Suppose we have a sales by area table that supports drag & drop between cells. We can easily drag & drop the contents of one cell to another cell like this:
 
-```C#
+````C#
 // Find the sales table
 HtmlTable salesTable = Find.ById<HtmlTable>("area_1_table");
   
@@ -40,8 +40,8 @@ salesTable.BodyRows[3].Cells[1].DragTo(ArtOfTest.Common.OffsetReference.Absolute
 // Verify the new row subtotals are correct
 Assert.AreEqual(salesTable.Rows[2].Cells[5].TextContent, "$3342.78");
 Assert.AreEqual(salesTable.Rows[3].Cells[5].TextContent, "$2175.17");
-```
-```VB
+````
+````VB
 ' Find the sales table
 Dim salesTable As HtmlTable = Find.ById(Of HtmlTable)("area_1_table")
   
@@ -51,4 +51,4 @@ salesTable.BodyRows(3).Cells(1).DragTo(salesTable.BodyRows(2).Cells(1))
 ' Verify the new row subtotals are correct
 Assert.AreEqual(salesTable.Rows(2).Cells(5).TextContent, "$3342.78")
 Assert.AreEqual(salesTable.Rows(3).Cells(5).TextContent, "$2175.17")
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/element-styles.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/element-styles.md
index 341cf561..6ac44d7a 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/element-styles.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/element-styles.md
@@ -4,7 +4,7 @@ page_title: Element Styles
 description: "Test Studio Testing Framework read and validate the styles of HTML elements in coded tests."
 position: 2
 ---
-#Element Styles and HtmlStyle, GetStyle, GetComputedStyle#
+# Element Styles and HtmlStyle, GetStyle, GetComputedStyle
 
 Telerik Testing Framework includes a good set of classes and methods for reading and validating the styles often attached to HTML controls. With this feature you can do things like:
 
@@ -24,7 +24,7 @@ Telerik Testing Framework includes a good set of classes and methods for reading
  
 Let's look at some code samples to see how this works:
 
-```C#
+````C#
 // Verify the color of the warning text is Red
 HtmlSpan warningSpan = Find.ById<HtmlSpan>("Warning");
 HtmlStyle warningColorStyle = warningSpan.GetStyle("color");
@@ -60,8 +60,8 @@ HtmlStyle warningMarginStyle = warningSpan.GetStyle("margin");
 Assert.IsTrue(warningMarginStyle.IsInt());
 int warningMargin = warningMarginStyle.ToInt();
 Assert.AreEqual(30, warningMargin);
-```
-```VB
+````
+````VB
 ' Verify the color of the warning text is Red
 Dim warningSpan As HtmlSpan = Find.ById(Of HtmlSpan)("Warning")
 Dim warningColorStyle As HtmlStyle = warningSpan.GetStyle("color")
@@ -95,13 +95,13 @@ Dim warningMarginStyle As HtmlStyle = warningSpan.GetStyle("margin")
 Assert.IsTrue(warningMarginStyle.IsInt())
 Dim warningMargin As Integer = warningMarginStyle.ToInt()
 Assert.AreEqual(30, warningMargin)
-```
+````
 
 The GetComputedStyle is especially powerful. It will follow the CSS chain up through all the parent elements until it finds the first matching style and returns the value picked up from that style. This is quite different from GetStyle which only returns an explicitly set style value on the specific element (i.e. it does not follow the CSS chain). If no explicit value has been set then GetStyle returns an empty string for the value. 
 
 Here's an example:
 
-```C#
+````C#
 // GetStyle returns the value of an explicit style applied to the element.
 // If the element does not have an explicit style applied, GetStyle returns an empty value.
 // Since our warning span does not have the padding style explicitly applied to it,
@@ -114,8 +114,8 @@ Assert.IsTrue(string.IsNullOrEmpty(paddingStyle.Value));
 // Therefore GetComputedStyle on the warning span will return the value set in the parent form tag.
 paddingStyle = warningSpan.GetComputedStyle("padding");
 Assert.IsFalse(string.IsNullOrEmpty(paddingStyle.Value));
-```
-```VB
+````
+````VB
 ' GetStyle returns the value of an explicit style applied to the element.
 ' If the element does not have an explicit style applied, GetStyle returns an empty value.
 ' Since our warning span does not have the padding style explicitly applied to it,
@@ -128,4 +128,4 @@ Assert.IsTrue(String.IsNullOrEmpty(paddingStyle.Value))
 ' Therefore GetComputedStyle on the warning span will return the value set in the parent form tag.
 paddingStyle = warningSpan.GetComputedStyle("padding")
 Assert.IsFalse(String.IsNullOrEmpty(paddingStyle.Value))
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/find-and-navigate-elements.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/find-and-navigate-elements.md
index 8a6ce10f..2c2e0e4e 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/find-and-navigate-elements.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/find-and-navigate-elements.md
@@ -4,11 +4,11 @@ page_title: Find and Navigate Elements
 description: "Test Studio Testing Framework finding elements in code and navigating through the DOM."
 position: 2
 ---
-#Finding and Navigating HTML Elements#
+# Finding and Navigating HTML Elements
 
 The example above used just two of the available find methods, the Find.ById<**TControl**> and the Find.AllByTagName<**TControl**> and did not take advantage of the powerful navigation features. Let's look at some other find examples:
 
-```C#
+````C#
 // Find the first table on the page.
 HtmlTable outertable = Find.ByTagIndex<HtmlTable>("table", 0);
   
@@ -38,8 +38,8 @@ Assert.AreEqual(1, imgCtrls.Count);
 // Find the <div> section containing the Eastern US Division sales report
 HtmlDiv EasternUSDivision = Find.ByContent<HtmlDiv>("Eastern US Division", FindContentType.TextContent);
 Assert.IsNotNull(EasternUSDivision);
-```
-```VB
+````
+````VB
 ' Find the first table on the page.
 Dim outertable As HtmlTable = Find.ByTagIndex(Of HtmlTable)("table", 0)
 Assert.AreEqual(3, outertable.Rows.Count)
@@ -70,12 +70,12 @@ Assert.AreEqual(1, imgCtrls.Count)
 ' Find the <div> section containing the Eastern US Division sales report
 Dim EasternUSDivision As HtmlDiv = Find.ByContent(Of HtmlDiv)("Eastern US Division", FindContentType.TextContent)
 Assert.IsNotNull(EasternUSDivision)
-```
+````
 
 
 The above example demonstrates how to use many of the more useful find methods. There are many more. It would take up too much space to try and document them all here. Refer to the API reference to learn about the others. Let's look at some HTML navigation functions:
 
-```C#
+````C#
 // Traverse the control tree upwards too. You can easily
 // Find the container control of a certain type from its children.
   
@@ -101,8 +101,8 @@ Assert.IsTrue(table2.ID.Equals(outertable.ID));
 // Find the form this table is contained in.
 HtmlForm form1 = table2.Parent<HtmlForm>();
 Assert.IsTrue(form1.ID.Equals("form1"));
-```
-```VB
+````
+````VB
 ' Traverse the control tree upwards too. You can easily
 ' Find the container control of a certain type from its children.
 
@@ -129,4 +129,4 @@ Assert.IsTrue(table2.ID.Equals(outertable.ID))
 ' Find the form this table is contained in.
 Dim form1 As HtmlForm = table2.Parent(Of HtmlForm)()
 Assert.IsTrue(form1.ID.Equals("form1"))
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/get-set-properties.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/get-set-properties.md
index dfabea7e..1ba97838 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/get-set-properties.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/get-set-properties.md
@@ -4,11 +4,11 @@ page_title: Get & Set Properties
 description: "Test Studio Testing Framework getting and setting properties of HTML elements in coded tests."
 position: 2
 ---
-#Getting and Setting Properties#
+# Getting and Setting Properties
 
 We can also get and set the current value of any property of the wrapped element:
 
-```C#
+````C#
 // Get whether a checkbox is enabled or disabled.
 HtmlInputCheckBox cks = Find.ById<HtmlInputCheckBox>("checkbox1");
 bool disabled = cks.GetValue<bool>("disabled");
@@ -32,8 +32,8 @@ string strColor = mySpan.GetStyleValue("color");
 // style.
 HtmlStyle styleMargin = mySpan.GetComputedStyle("margin");
 string strMargin = mySpan.GetComputedStyleValue("margin");
-```
-```VB
+````
+````VB
 ' Get whether a checkbox is enabled or disabled.
 Dim cks As HtmlInputCheckBox = Find.ById(Of HtmlInputCheckBox)("checkbox1")
 Dim disabled As Boolean = cks.GetValue(Of Boolean)("disabled")
@@ -51,4 +51,4 @@ Dim strColor As String = mySpan.GetStyleValue("color")
 ' style.
 Dim styleMargin As HtmlStyle = mySpan.GetComputedStyle("margin")
 Dim strMargin As String = mySpan.GetComputedStyleValue("margin")
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-actions.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-actions.md
index c0c1770b..9bae94a3 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-actions.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-actions.md
@@ -4,7 +4,7 @@ page_title: HTML Actions
 description: "Test Studio Testing Framework interact with an HTML element identified in the DOM in coded tests. HTML actions to perform on an element in coded tests."
 position: 2
 ---
-#Common HTML Control Actions#
+# Common HTML Control Actions
 
 What are some of the things we can do after finding the element we want to act upon? We can:
 
@@ -22,7 +22,7 @@ What are some of the things we can do after finding the element we want to act u
  
 Here are some examples:
 
-```C#
+````C#
 // All controls have a Click/MouseClick. The .Click invokes a click from the DOM,
 // the MouseClick(), moves the mouse to the control and clicks it.
   
@@ -113,8 +113,8 @@ Assert.IsTrue(link.BaseElement.TextContent.Trim().Equals("Link"));
   
 // Invoke any events on the control
 link.InvokeEvent(ScriptEventType.OnFocus);
-```
-```VB
+````
+````VB
 ' All controls have a Click/MouseClick. The .Click invokes a click from the DOM,
 ' the MouseClick(), moves the mouse to the control and clicks it.   
   
@@ -205,4 +205,4 @@ Assert.IsTrue(link.BaseElement.TextContent.Trim().Equals("Link"))
     
 ' Invoke any events on the control
 link.InvokeEvent(ScriptEventType.OnFocus)
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-asserts.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-asserts.md
index 8265e8e3..045c6198 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-asserts.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-asserts.md
@@ -4,7 +4,7 @@ page_title: HTML Asserts
 description: "Test Studio Testing Framework validate an HTML element identified in the DOM in coded tests. HTML asserts to perform on an element in coded tests."
 position: 2
 ---
-#HTML Asserts#
+# HTML Asserts
 
 Telerik Testing Framework has a set of Assert classes to make validation of your HTML controls easier. An 'Assert' basically says "Verify the specified property of the control has the specified value or setting. If it doesn't have that setting/value, then throw an error and stop the test." 
 
@@ -138,11 +138,11 @@ For example: AssertCheck.IsTrue() will verify the associated checkbox control is
 	<td>RowRange</td>
 	<td>Asserts if the number of rows is not inside or not outside of the specified range.</td>
 </tr>
-<table>
+</table>
 
 Now let's see how this works in action:
 
-```C#
+````C#
 // Attribute checks
 HtmlSpan span = Find.ById<HtmlSpan>("Warning");
 span.AssertAttribute().Exists("style");
@@ -198,8 +198,8 @@ table.AssertTable().RowCount(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.
 table.AssertTable().RowRange(ArtOfTest.Common.NumberRangeCompareType.OutsideRange, 1, 2);
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.Contains, "TD5");
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.NotContain, "TD37");
-```
-```VB
+````
+````VB
 ' Attribute checks
 Dim span As HtmlSpan = Find.ById(Of HtmlSpan)("Warning")
 span.AssertAttribute().Exists("style")
@@ -253,7 +253,7 @@ table.AssertTable().RowCount(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.
 table.AssertTable().RowRange(ArtOfTest.Common.NumberRangeCompareType.OutsideRange, 1, 2)
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.Contains, "TD5")
 table.AssertTable().Contains(ArtOfTest.WebAii.Controls.HtmlControls.HtmlAsserts.StringCompareType.NotContain, "TD37")
-```
+````
 
 
 There are many other possible assert verification combinations built into the framework that you can take advantage of. The above examples are just a small subset of what is possible to help you get started implementing them in your code and crafting the kinds of verification you need for your particular website. Consult the API reference manual to learn about the other combinations.
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-wait-class.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-wait-class.md
index c9a9472c..066414e8 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-wait-class.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/html-wait-class.md
@@ -4,7 +4,7 @@ page_title: HtmlWait Class
 description: "Test Studio Testing Framework HtmlWait Class used to wait for visibility state of an HTML element identified in the DOM in coded tests. Wait for an element's custom condition in coded tests."
 position: 2
 ---
-#How to Use the HtmlWait Class#
+# How to Use the HtmlWait Class
 
 The HtmlWait class extends and enhances the Element.Wait class with some powerful methods that are very useful with the HTML control suite. It adds:
 
@@ -17,7 +17,7 @@ The HtmlWait class extends and enhances the Element.Wait class with some powerfu
 The HtmlWait.ForVisible and HtmlWait.ForVisibleNot use the HtmlControl.IsVisible function to test whether or not the element is currently visible in the browser. Since IsVisible follows the CSS chain, we get a true reading of whether or not the element actually is visible. For example:
 
 
-```C#
+````C#
 HtmlDiv div = Find.ByTagIndex<HtmlDiv>("div", 0);
 HtmlWait waitObj = div.Wait;
   
@@ -32,8 +32,8 @@ waitObj.Timeout = 1200000;        // Override the default value
 waitObj.ForVisible();
 // Wait 120 seconds for the div to become invisible
 waitObj.ForVisibleNot();
-```
-```VB
+````
+````VB
 HtmlDiv div = Find.ByTagIndex<HtmlDiv>("div", 0);
 HtmlWait waitObj = div.Wait;
   
@@ -48,11 +48,11 @@ waitObj.Timeout = 1200000;        // Override the default value
 waitObj.ForVisible();
 // Wait 120 seconds for the div to become invisible
 waitObj.ForVisibleNot();
-```
+````
 
 Using the HtmlWait.ForStyles and HtmlWait.ForStylesNot methods you can wait for a particular style to be set or removed from the element. For example:
 
-```C#
+````C#
 HtmlSpan span = Find.ByTagIndex<HtmlSpan>("span", 0);
 HtmlWait spanWaitObj = div.Wait;
   
@@ -84,8 +84,8 @@ spanWaitObj.ForStylesNot("backgroundColor=red", "margin=30px");
 // Will continue to wait if either style is still set to the specified value.
 // Uses the default timeout value from Settings.Current.ExecuteCommandTimeout
 span.Wait.ForStylesNot("backgroundColor=red", "margin=30px");
-```
-```VB
+````
+````VB
 Dim span As HtmlSpan = Find.ByTagIndex(Of HtmlSpan)("span", 0)
 Dim spanWaitObj As HtmlWait = div.Wait
   
@@ -117,29 +117,29 @@ spanWaitObj.ForStylesNot("backgroundColor=red", "margin=30px")
 ' Will continue to wait if either style is still set to the specified value.
 ' Uses the default timeout value from Settings.Current.ExecuteCommandTimeout
 span.Wait.ForStylesNot("backgroundColor=red", "margin=30px")
-```
+````
 
 
 The HtmlWait.ForCondition is an advanced method that calls a user defined function to determine whether or not the wait condition has been satisfied. You, the test automation programmer, may code up any sort of wait condition you can imagine. The only requirement is that your function must return true to indicate that the condition has been satisfied or return false to indicate the condition has not been satisfied.
  
 The overloads of the HtmlWait.ForCondition are split into two virtually identical sets of three overloads. The first set operates on basic Element objects. The second set operates on Control objects, which all of the classes contained in the HTML control suite derive from. Except for this difference, they operate identically. The sample below shows only the Control version:
 
-```C#
+````C#
 HtmlTextArea textArea = Find.ByTagIndex<HtmlTextArea>("textarea", 0);
 HtmlWait textAreaWaitObj = textArea.Wait;
 // Wait 30 seconds for the HtmlTextArea element to contain the text "Now is the time"
 textArea.Wait.ForCondition(textAreaContainsStr, false, "Now is the time", 30000);
-```
-```VB
+````
+````VB
 Dim textArea As HtmlTextArea = Find.ByTagIndex(Of HtmlTextArea)("textarea", 0)
 Dim textAreaWaitObj As HtmlWait = textArea.Wait
 ' Wait 30 seconds for the HtmlTextArea element to contain the text "Now is the time"
 textArea.Wait.ForCondition(AddressOf textAreaContainsStr, False, "Now is the time", 30000)
-```
+````
 
 Now we need the definition of the condition function 'textAreaContainsStr':
 
-```C#
+````C#
 /// <summary>
 /// Tests whether or not the HtmlTextArea element contains the specified string.
 /// </summary>
@@ -161,8 +161,8 @@ public bool textAreaContainsStr(ArtOfTest.WebAii.Controls.Control ctl, Object ob
     HtmlTextArea textArea = (HtmlTextArea)ctl;
     return textArea.Text.Contains((string)obj);
 }
-```
-```VB
+````
+````VB
 ''' <summary>
 ''' Tests whether or not the HtmlTextArea element contains the specified string.
 ''' </summary>
@@ -183,4 +183,4 @@ Public Function textAreaContainsStr(ByVal ctl As ArtOfTest.WebAii.Controls.Contr
     Return textArea.Text.Contains(CType(obj, String))
   
 End Function
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/introduction.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/introduction.md
index b5cb2dbc..a4b3b798 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/introduction.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/introduction.md
@@ -5,15 +5,15 @@ description: "Test Studio Testing Framework introducing the HTML Control Suite -
 previous_url: /user-guide/write-tests-in-code/intermediate-topics/html-control-suite/introduction.aspx, /user-guide/write-tests-in-code/intermediate-topics/html-control-suite/introduction
 position: 1
 ---
-#Intro to Telerik Testing Framework's HTML Control Element Wrappers Suite#
+# Intro to Telerik Testing Framework's HTML Control Element Wrappers Suite
 
 Telerik Framework includes an extensive suite of strongly typed HTML element wrappers that abstracts out actions and verifications of the controls contained on the webpage. With the classes contained in the control suite you can do things like:
 
-**nextPageButton.Click()** instead of **Actions.Click(nextPageButton)**
+`nextPageButton.Click()` instead of `Actions.Click(nextPageButton)`
 
 or
 
-**Assert.IsTrue(textBox.Text.Equals("foo"))** instead of **Assert.IsTrue(element.GetAttribute("value").Equals("foo"))**
+`Assert.IsTrue(textBox.Text.Equals("foo"))` instead of `Assert.IsTrue(element.GetAttribute("value").Equals("foo"))`
 
 
 In addition there are many other features that make the abstraction even more powerful. Here is a list off all the wrapper classes currently available along with the properties and methods they expose:
@@ -23,7 +23,9 @@ In addition there are many other features that make the abstraction even more po
 	<th>HTML Control</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlAnchor**</td>
+	<td>
+
+**HtmlAnchor**</td>
 	<td>Wraps access to a HTML \<a> anchor element.</td>
 	<td>HRef<br>
 	Name<br>
@@ -33,7 +35,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlButton**</td>
+	<td>
+
+**HtmlButton**</td>
 	<td>Wraps access to a HTML \<button> element.</td>
 	<td>Disabled
 	Name<br>
@@ -43,14 +47,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionDescription**</td>
+	<td>
+
+**HtmlDefinitionDescription**</td>
 	<td>Wraps access to a HTML \<dd /> element . This control is used by the HtmlDefinitionList control.</td>
 	<td>Description</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionList**</td>
+	<td>
+
+**HtmlDefinitionList**</td>
 	<td>Wraps access to a HTML \<dl> element.</td>
 	<td>Descriptions<br>
 	Terms</td>
@@ -58,21 +66,27 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDefinitionTerm**</td>
+	<td>
+
+**HtmlDefinitionTerm**</td>
 	<td>Wraps access to a HTML \<dt> element. This control is used by the HtmlDefinitionList control.</td>
 	<td>Terms</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlDiv**</td>
+	<td>
+
+**HtmlDiv**</td>
 	<td>Wraps access to a HTML \<div> container element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlForm**</td>
+	<td>
+
+**HtmlForm**</td>
 	<td>Wraps access to a HTML \<form> element.</td>
 	<td>EncType<br>
 	Length<br>
@@ -82,7 +96,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlImage**</td>
+	<td>
+
+**HtmlImage**</td>
 	<td>Wraps access to a HTML \<image> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -94,7 +110,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputButton**</td>
+	<td>
+
+**HtmlInputButton**</td>
 	<td>Wraps access to a HTML \<input type=button> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -106,28 +124,36 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputCheckBox**</td>
+	<td>
+
+**HtmlInputCheckBox**</td>
 	<td>Wraps access to a HTML \<input type=checkbox> element.</td>
 	<td>Checked</td>
 	<td>Check</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputFile**</td>
+	<td>
+
+**HtmlInputFile**</td>
 	<td>Wraps access to a HTML \<input type=file> element.</td>
 	<td>FilePath</td>
 	<td>Upload</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputHidden**</td>
+	<td>
+
+**HtmlInputHidden**</td>
 	<td>Wraps access to a HTML \<input type=hidden> element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputImage**</td>
+	<td>
+
+**HtmlInputImage**</td>
 	<td>Wraps access to a HTML \<input type=image> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -139,7 +165,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputPassword**</td>
+	<td>
+
+**HtmlInputPassword**</td>
 	<td>Wraps access to a HTML \<input type=password> element.</td>
 	<td>Disabled
 	Size<br>
@@ -149,14 +177,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputRadioButton**</td>
+	<td>
+
+**HtmlInputRadioButton**</td>
 	<td>Wraps access to a HTML \<input type=radio> element.</td>
 	<td>Cheched</td>
 	<td>Check</td>
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputReset**</td>
+	<td>
+
+**HtmlInputReset**</td>
 	<td>Wraps access to a HTML \<input type=reset> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -168,7 +200,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputSubmit**</td>
+	<td>
+
+**HtmlInputSubmit**</td>
 	<td>Wraps access to a HTML \<input type=submit> element.</td>
 	<td>Align<br>
 	Alt<br>
@@ -180,7 +214,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlInputText**</td>
+	<td>
+
+**HtmlInputText**</td>
 	<td>Wraps access to a HTML \<input type=text> element.</td>
 	<td>Disabled<br>
 	Size<br>
@@ -190,14 +226,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlInputControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlListItem**</td>
+	<td>
+
+**HtmlListItem**</td>
 	<td>Wraps access to a HTML \<li> element. This control is used by the HtmlOrdererList control and the HtmlUnorderedList control.</td>
 	<td>GetItemOrder</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlOption**</td>
+	<td>
+
+**HtmlOption**</td>
 	<td>Wraps access to a HTML \<option> element which is a member of a select element.</td>
 	<td>Selected<br>
 	Text<br>
@@ -206,7 +246,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlOrderedList**</td>
+	<td>
+
+**HtmlOrderedList**</td>
 	<td>Wraps access to a HTML \<ol>.</td>
 	<td>AllItems<br>
 	Itemst</td>
@@ -214,7 +256,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlSelect**</td>
+	<td>
+
+**HtmlSelect**</td>
 	<td>Wraps access to a HTML \<select> list box or drop-down list element.</td>
 	<td>Options<br>
 	SelectedIndex<br>
@@ -231,14 +275,18 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlSpan**</td>
+	<td>
+
+**HtmlSpan**</td>
 	<td>Wraps access to a HTML \<span> inline text container element.</td>
 	<td></td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTable**</td>
+	<td>
+
+**HtmlTable**</td>
 	<td>Wraps access to a HTML \<table> table element containing rows and columns.</td>
 	<td>AllRows<br>
 	BodyRows<br>
@@ -256,7 +304,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTableCell**</td>
+	<td>
+
+**HtmlTableCell**</td>
 	<td>Wraps access to a HTML \<td> table cell element.</td>
 	<td>Align<br>
 	BgColor<br>
@@ -272,7 +322,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTableRow**</td>
+	<td>
+
+**HtmlTableRow**</td>
 	<td>Wraps access to a HTML \<tr> element.</td>
 	<td>Align<br>
 	BgColor<br>
@@ -285,7 +337,9 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlTextArea**</td>
+	<td>
+
+**HtmlTextArea**</td>
 	<td>Wraps access to a HTML \<textArea> text input element.</td>
 	<td>Cols<br>
 	Rows<br>
@@ -294,14 +348,16 @@ In addition there are many other features that make the abstraction even more po
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
 <tr>
-	<td>**HtmlUnorderedList**</td>
+	<td>
+
+**HtmlUnorderedList**</td>
 	<td>Wraps access to a HTML \<ul> element.</td>
 	<td>AllItems<br>
 	Items</td>
 	<td></td>
 	<td><a href="#base">HtmlContainerControl</a></td>
 </tr>
-<table>
+</table>
 *Table 1. List of HTML element control wrappers contained in Telerik Testing Framework's HTML control suite.*
 
 Here is a list of the base classes along with the properties and methods they expose:
@@ -311,7 +367,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<th>Base Class</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlContainerControl**</td>
+	<td>
+
+**HtmlContainerControl**</td>
 	<td>Base class for all wrapper controls that can contain other controls.</td>
 	<td>Find<br>
 	InnerText<br>	
@@ -320,7 +378,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>HtmlControl</td>
 </tr>
 <tr>
-	<td>**HtmlInputControl**</td>
+	<td>
+
+**HtmlInputControl**</td>
 	<td>Base class for all input wrapper controls.</td>
 	<td>Name<br>
 	Type<br>
@@ -329,7 +389,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>HtmlControl</td>
 </tr>
 <tr>
-	<td>**HtmlControl**</td>
+	<td>
+
+**HtmlControl**</td>
 	<td>Base class for the entire HTML wrapper control suite.</td>
 	<td>Attributes<br>
 	ChildNodes<br>
@@ -366,7 +428,9 @@ Here is a list of the base classes along with the properties and methods they ex
 	<td>Control</td>
 </tr>
 <tr>
-	<td>**Control**</td>
+	<td>
+
+**Control**</td>
 	<td>Root base class for all WebAii controls.</td>
 	<td>BaseElement<br>
 	IsRefresh<br>
@@ -380,7 +444,7 @@ Here is a list of the base classes along with the properties and methods they ex
 	Refresh</td>
 	<td><a href="#" target="_blank">HtmlContainerControl</a></td>
 </tr>
-<table>
+</table>
 *Table 2. List of base classes used by Telerik Testing Framework's HTML control suite.*
 
 Here is a list of the support classes that make it easier to use the rest of the HTML control suite:
@@ -390,7 +454,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<th>Base Class</th><th>Description</th><th>Properties</th><th>Methods</th><th>Base Class</th>
 </tr>
 <tr>
-	<td>**HtmlFind**</td>
+	<td>
+
+**HtmlFind**</td>
 	<td>An extended Find class that includes HTML specific find methods.</td>
 	<td>Table<br>
 	TableCell<br>
@@ -399,7 +465,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<td>Find</td>
 </tr>
 <tr>
-	<td>**HtmlStyle**</td>
+	<td>
+
+**HtmlStyle**</td>
 	<td>Represents a single HtmlStyle. This object can be used to help probe and do validation against Html styles. Has functionality to convert unit styles to int values and color styles to System.Drawing.Color.</td>
 	<td>Name<br>
 	Value</td>
@@ -412,7 +480,9 @@ Here is a list of the support classes that make it easier to use the rest of the
 	<td>Name<br>Value</td>
 </tr>
 <tr>
-	<td>**HtmlWait**</td>
+	<td>
+
+**HtmlWait**</td>
 	<td>An extended Wait class that includes HTML specific wait methods.</td>
 	<td></td>
 	<td>ForCondition<br>
@@ -423,14 +493,14 @@ Here is a list of the support classes that make it easier to use the rest of the
 	ForVisibleNot</td>
 	<td>Wait</td>
 </tr>
-<table>
+</table>
 *Table 3. List of HtmlControl support classes contained in Telerik Testing Framework's HTML control suite.*
 
-##Example of How to Fill Out a Web Form Using the HTML Element Wrapper Control Suite##
+## Example of How to Fill Out a Web Form Using the HTML Element Wrapper Control Suite
 
 Suppose we're automating a form to submit an auto classified ad. Here's how to write the code and take advantage of the HTML element wrapper suite:
 
-```C#
+````C#
 [TestClass]
 public class SubmitAdTestClass : BaseTest
 {
@@ -500,8 +570,8 @@ public class SubmitAdTestClass : BaseTest
         submit.Click();
     }
 }
-```
-```VB
+````
+````VB
 <TestClass()> _
  Public Class SubmitAdTestClass
     Inherits BaseTest
@@ -574,12 +644,12 @@ public class SubmitAdTestClass : BaseTest
     End Sub
    
 End Class
-```
+````
 
 
 By taking advantage of the object oriented nature of the HTML element wrapper classes, our test code that fills in the fields and clicks the submit button is much simpler, more descriptive and more intuitive in nature. Note how simple it was to enter text into all the input fields, as well as make all the drop down selections using intuitive methods included with Telerik's HTML element wrapper classes!
-Also notice how we're doing a nested find. The line **form.Find.AllByTagName<HtmlSelect>("select");** is returning all of the **\<select>** elements that are contained within the form "Form2" contained on the page, not the entire page itself which may contain other \<select> elements on the page, perhaps even on other forms contained on the same page.
+Also notice how we're doing a nested find. The line `form.Find.AllByTagName<HtmlSelect>("select");` is returning all of the `<select>` elements that are contained within the form "Form2" contained on the page, not the entire page itself which may contain other `<select>` elements on the page, perhaps even on other forms contained on the same page.
  
-One special feature to note about the **Find.AllByXXX<TControl>()** functions is that they filter on the type of the **TControl** such that the returned list only includes elements of type **TControl**. In the example above we're calling **Find.AllByTagName<HtmlInputText>("input")**. Due to the filtering being performed by the framework we only get back \<input type="text"> elements and not other input elements such as the \<input type="password"> element that is also on the form.
+One special feature to note about the `Find.AllByXXX<TControl>()` functions is that they filter on the type of the `TControl` such that the returned list only includes elements of type `TControl`. In the example above we're calling `Find.AllByTagName<HtmlInputText>("input")`. Due to the filtering being performed by the framework we only get back `<input type="text">` elements and not other input elements such as the `<input type="password">` element that is also on the form.
  
-By the same token all of the Fi**nd.ByXXX<TControl>()** functions also verify that the found element is of type **TControl**. If, for example, you call **Find.ByTagIndex<HtmlInputPassword>("input", 4)** and the 5th \<input> element is not type="password" then the framework will throw a System.ArgumentException.
+By the same token all of the `Find.ByXXX<TControl>()` functions also verify that the found element is of type `TControl`. If, for example, you call `Find.ByTagIndex<HtmlInputPassword>("input", 4)` and the 5th `<input>` element is not type="password" then the framework will throw a System.ArgumentException.
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files.md
deleted file mode 100644
index efbabec7..00000000
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Transfer Files
-page_title: Transfer Files
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 2
-publish: false
----
-#How to Transfer Files#
-
-We can even perform complete file uploads and downloads with Telerik Testing Framework automatically handling all of the popup dialogs that appear as part of the file upload/download:
-
-```C#
-// Initiate a file upload
-Find.ByTagIndex<HtmlInputFile>("input", 0).Upload(
-     Path.Combine(Globals.PATH_TO_PAGES, @"..\SupportFiles\EmptyTextFile.txt"), 5000);
-  
-// Initiate a file download. Download will not return until the download is complete.
-Find.ByTagIndex<HtmlAnchor>("a", 0).Download(false, DownloadOption.Save, saveLocation, 20000);
-```
-```VB
-' Initiate a file upload
-Find.ByTagIndex(Of HtmlInputFile)("input", 0).Upload( _
-     Path.Combine(Globals.PATH_TO_PAGES, "..\SupportFiles\EmptyTextFile.txt"), 5000)
-  
-' Initiate a file download. Download will not return until the download is complete.
-Find.ByTagIndex(Of HtmlAnchor)("a", 0).Download(False, DownloadOption.Save, saveLocation, 20000)
-```
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/keyboard-manager.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/keyboard-manager.md
index 6b71decb..5ab74711 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/keyboard-manager.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/keyboard-manager.md
@@ -5,7 +5,7 @@ description: "Test Studio Testing Framework support in coded tests for sending d
 position: 1
 ---
 
-#The KeyBoard Manager Class#
+# The KeyBoard Manager Class
 
 The KeyBoard manager class is used to simulate typing keys on the keyboard. It has the following methods:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/mouse-manager.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/mouse-manager.md
index 306b0817..85b154fb 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/mouse-manager.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/mouse-manager.md
@@ -4,7 +4,8 @@ page_title: Mouse Manager
 description: "Test Studio Testing Framework support in coded tests for using direct mouse actions through the Mouse Manager class."
 position: 1
 ---
-#Mouse Manager Class#
+
+# Mouse Manager Class
 
 The Mouse manager class is used to simulate moving the physical mouse and performing various types of mouse clicks. It has the following properties:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/app-config-file.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/app-config-file.md
deleted file mode 100644
index f24791a2..00000000
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/app-config-file.md
+++ /dev/null
@@ -1,73 +0,0 @@
----
-title: App .config file
-page_title: App .config file
-description: "Test Studio Testing Framework App .config file"
-previous_url: /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/using-application-config-file.aspx, /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/using-application-config-file
-position: 1
----
-#Using the Application's .config File#
-
-Instead of programmatically setting the configuration, the application or test program can use an application .config file to fetch the appropriate settings. The Telerik infrastructure has a built in .NET Config SectionHandler (under the 'ArtOfTest.Core' namespace) that can read the configuration settings from the .config file associated with the application or test. You place the settings in your .config file as follows:
-
-1.&nbsp; First add the following line to the 'configSections' section:
-
-```XML
-<configSections>                                     
-<section name="WebAii.Settings" type="ArtOfTest.WebAii.Core.SettingsConfigSectionHandler,ArtOfTest.WebAii"/>
-<section name="WebAii.Settings.Web" type="ArtOfTest.WebAii.Core.WebSettingsConfigSectionHandler,ArtOfTest.WebAii"/>
-<section type="ArtOfTest.WebAii.Core.WpfSettingsConfigSectionHandler,ArtOfTest.WebAii" name="WebAii.Settings.Wpf"/>  
-</configSections>
-```
-
-2.&nbsp; Then add the settings you need under the 'WebAii.Settings' section or WebAii.Settings.Web' section.
-
-	**Note:** It is not necessary to include all of Telerik's settings in your .config file. You only need to add settings for those you wish to override. The Telerik Testing Framework uses default values for any setting not explicitly set in the .config file. 
-
-	**Note:** The configuration setting names are case sensitive e.g.  **AnnotateExecution** will not be recognized and will cause an exception to be thrown while **annotateExecution** will be recognized and used.
-
-		
-```XML
-	<WebAii.Settings                                           
-                   logLocation="F:\Log\"
-                   executionTimeout="30000"
-                   clientReadyTimeout="20000"                    
-                   queryEventLogErrorsOnExit="false"                     
-                   executionDelay="0"
-                   annotateExecution="true"
-                   annotationMode="All"
-                   logAnnotations="false"                                              
-                   waitCheckInterval="633"      
-                   createLogFile="true">
-	</WebAii.Settings>
-	<WebAii.Settings.Web baseUrl="http://www.lava.com">           
-	</WebAii.Settings.Web>
-```
-
-Here is an example of a complete app.config file that contains all of Telerik's configuration settings:
-
-```XML
-<?xml version="1.0" encoding="UTF-8"?>
-<configuration>
- <configSections>
- <section type="ArtOfTest.WebAii.Core.SettingsConfigSectionHandler,ArtOfTest.WebAii" name="WebAii.Settings"/>
- <section type="ArtOfTest.WebAii.Core.WebSettingsConfigSectionHandler,ArtOfTest.WebAii" name="WebAii.Settings.Web"/>
-<section type="ArtOfTest.WebAii.Core.WpfSettingsConfigSectionHandler,ArtOfTest.WebAii" name="WebAii.Settings.Wpf"/>
- </configSections>
- <WebAii.Settings elementWaitTimeout="10000" xMultiMgr="false" unexpectedDialogAction="HandleAndFailTest" createLogFile="true" waitCheckInterval="500" logAnnotations="false" annotationMode="All" annotateExecution="true" executionDelay="0" queryEventLogErrorsOnExit="false" clientReadyTimeout="20000" executionTimeout="30000" logLocation="F:\Log\"></WebAii.Settings>
- <WebAii.Settings.Web verboseHttpProxy="false" enableSilverlight="true" useHttpProxy="false" enableUILessRequestViewing="false" aspNetDevServerPort="-1" webAppPhysicalPath="" localWebServer="None" silverlightApplicationPath="" silverlightConnectTimeout="30000" enableScriptLogging="false" defaultBrowser="InternetExplorer" killBrowserProcessOnClose="false" baseUrl="http://www.telerik.com"> </WebAii.Settings.Web>
-<WebAii.Settings.Wpf defaultApplicationPath="E:\Users\Dad\Documents\visual studio 2010\Projects\TelerikWpfApp1\TelerikWpfApp1\bin\Debug\TelerikWpfApp1.exe" />
-</configuration>
-```	
-In your test code initialization, you read these settings by simply setting the UseConfig flag to true when calling the Manager() constructor. If you use the BaseTest template (which is what the VsUnit, MbUnit, NUnit and xUnit templates do) this call is done for you by BaseTest during the Initialize call:
-
-```C#
-Manager mgr = new Manager(true);
-```
-```VB
-Dim myManager As Manager = New Manager(True)
-```
-
-**Note:** If you are using Telerik's BaseTest (which the Telerik VS item templates use), there is no need to for your test code to read from the app.config file as shown above. The base class already does that for you. Read the item template's comments for the initialization routine for more details.
-
-
-
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
index 2e14eb17..38341db3 100644
--- 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
@@ -5,7 +5,7 @@ description: "Test Studio Testing Framework Settings class. Use the Setting Clas
 previous_url: /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/settings-class.aspx, /user-guide/write-tests-in-code/intermediate-topics/settings-and-configuration/settings-class
 position: 1
 ---
-#Settings Class#
+# Settings Class
 
 How the Telerik Testing Framework behaves during a test run is controlled by the settings contained in the Settings object. There are many settings you can take advantage of to modify its behavior to better meet your testing requirements or testing environment. The complete list of settings is detailed in the table below. A few of the more commonly used settings include:
 
@@ -13,15 +13,14 @@ How the Telerik Testing Framework behaves during a test run is controlled by the
 
 * DefaultBrowser - Controls which browser will be started by the LaunchNewBrowser command.
 
-* EnableSilverlight - If you will be doing any Silverlight application settings, this must be set to True.
  
 There are a few methods of controlling the settings in the Settings object. Which method you use depends on when and how you want them set in your unit test.
 
-##Initializing the Settings Object Without Using a Telerik Test Template##
+## Initializing the Settings Object Without Using a Telerik Test Template
 
 If you're not using one of Telerik's test templates (VsUnit, NUnit, MbUnit, xUnit) to create your unit test, you'll need to create your own Settings object and then pass that object as a parameter to the constructor of your Manager object. For example:
 
-```C#
+````C#
 // Create my own Settings object and then modify the defaults
 Settings mySettings = new Settings();
 mySettings.DefaultBrowser = BrowserType.FireFox;
@@ -29,8 +28,8 @@ mySettings.ClientReadyTimeout = 60000;
   
 // Use my Settings object to construct my Manager object
 Manager myManager = new Manager(mySettings);
-``` 
-```VB
+````
+````VB
 ' Create my own Settings object and then modify the defaults
 Dim mySettings As New Settings()
 mySettings.DefaultBrowser = BrowserType.FireFox
@@ -38,13 +37,13 @@ mySettings.ClientReadyTimeout = 60000
   
 ' Use my Settings object to construct my Manager object
 Dim myManager As New Manager(mySettings)
-```
+````
 
-##Initializing the Settings Object When Using a Test Template##
+## Initializing the Settings Object When Using a Test Template
 
 If you're using one of Telerik's test templates (VsUnit, NUnit, MbUnit, xUnit) to create your unit test, you'll need to create your own Settings object in the TestInitialize section (or Setup section if you're using NUnit) and then pass that object as a parameter to the Initialize method of the base class. For example:
 
-```C#
+````C#
 // This will get a new Settings object. If a configuration
 // section exists, then settings from that section will be
 // loaded
@@ -55,8 +54,8 @@ settings.UseHttpProxy = true;
   
 // Now call Initialize again with your updated settings object
 Initialize(settings, new TestContextWriteLine(this.TestContext.WriteLine));
-```
-```VB
+````
+````VB
 ' This will get a new Settings object. If a configuration
 ' section exists, then settings from that section will be
 ' loaded
@@ -67,26 +66,26 @@ settings.UseHttpProxy = True
   
 ' Now call Initialize again with your updated settings object
 Initialize(settings, New TestContextWriteLine(AddressOf Me.TestContext.WriteLine))
-```
+````
 
 **Note:** Be sure to call Initialize only once. Calling Initialize a second time will simply be ignored and you'll be left wondering why your settings did not take effect.
 
-##Changing Settings On-The-Fly##
+## Changing Settings On-The-Fly
 
 Lastly you can modify most of the settings after your test is already initialized and under-way. Here's how you to do that:
 
-```C#
+````C#
 Manager.Settings.AnnotateExecution = true;
 Manager.Settings.DefaultBrowser = BrowserType.FireFox;
-```
-```VB
+````
+````VB
 Manager.Settings.AnnotateExecution = True
 Manager.Settings.DefaultBrowser = BrowserType.FireFox
-```
+````
 
 **Note:** The following settings can only be set during initialization: AspNetDevServerPort, CreateLogFile, EnableUILessRequestViewing, LocalWebServer, LogLocation, VerboseHttpProxy and WebAppPhysicalPath.
 
-##Using the RecycleBrowser Feature##
+## Using the RecycleBrowser Feature
 
 The RecycleBrowser feature was added in version 2.0. Using it can significantly speed up running an entire test suite, no more starting and shutting down of the browser for each individual unit test. It works by launching one browser window in the test fixture initialization of your test suite and then constantly reusing that same browser window for all unit tests contained in your test suite.
 
@@ -96,16 +95,16 @@ There are a just a couple of things you need to be aware of to properly use the
 
 2.&nbsp; You must call the base classes ShutDown() method in the test fixture teardown section to properly the browser window at the end of the test suite. If you miss this then browser windows will be left behind after your test suite has finished and exited.
 
-##Restoring Default Settings##
+## Restoring Default Settings
 
 If it ever becomes necessary you can restore all the settings (except for those that can only be set during initialization) back to their default values. Just use the Reset() method of the Settings object. For example:
 
-```C#
+````C#
 Manager.Settings.Reset();
-```
-```VB
+````
+````VB
 Manager.Settings.Reset()
-```
+````
 
 This table lists all of the WebAii framework settings that are available for you to use:
 
@@ -114,169 +113,162 @@ This table lists all of the WebAii framework settings that are available for you
 	<th>Name</th><th>Description</th><th>Possible Values</th><th>Default Value</th>
 </tr>
 <tr>
-	<td>**AnnotateExecution**</td>
-	<td>Controls whether or not to highlight/annotate the target elements that the requested action is being executed against. e.g. **Actions.Click(goButton)**;</td>
+	<td><strong>AnnotateExecution</strong></td>
+	<td>Controls whether or not to highlight/annotate the target elements that the requested action is being executed against. e.g. <strong>Actions.Click(goButton)</strong>;</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**AnnotationMode**</td>
+	<td><strong>AnnotationMode</strong></td>
 	<td>This read-only setting contains the full physical path to your local ASP.NET development web server (WebDev.WebServer.EXE). It is set by the framework when LocalWebServer is set to "AspNetDevelopmentServer". Otherwise it is an empty string.</td>
 	<td></td>
 	<td></td>
 </tr>
 <tr>
-	<td>**AspNetDevServerPort**</td>
+	<td><strong>AspNetDevServerPort</strong></td>
 	<td>Controls the AspNetDevServer (if used) port. If this is not set (-1) a random port will be generated each time the manager is created.</td>
 	<td>0 to int.MaxValue</td>
 	<td>Random value</td>
 </tr>
 <tr>
-	<td>**BaseUrl**</td>
+	<td><strong>BaseUrl</strong></td>
 	<td>Sets the base URL to use for all NavigateTo() commands. When set NavigateTo() should use a relative URL (e.g. "~/default.aspx").</td>
 	<td>Any valid URL</td>
 	<td>string.Empty</td>
 </tr>
 <tr>
-	<td>**ClientReadyTimeout**</td>
+	<td><strong>ClientReadyTimeout</strong></td>
 	<td>Timeout used to wait for a client (a browser) to be ready after it is first launched or after executing a command (in milliseconds). For example after launching the browser if the browser is not ready within this timeout the framework will throw a <a href="http://msdn2.microsoft.com/en-us/library/system.timeoutexception%28vs.80%29.aspx" target="_blank">TimeoutException</a>.</td>
 	<td>0 to int.MaxValue</td>
 	<td>30000</td>
 </tr>
 <tr>
-	<td>**CreateLogFile**</td>
+	<td><strong>CreateLogFile</strong></td>
 	<td>Gets or sets whether to create a log file on disk. This value is read once at initialization time. Changing this value during test execution has no effect.</td>
 	<td>true<br>
 	false</td>
 	<td>true</td>
 </tr>
 <tr>
-	<td>**DefaultBrowser**</td>
+	<td><strong>DefaultBrowser</strong></td>
 	<td>The default browser (i.e. Internet Explorer or Firefox or AspNetHost) to launch when calling Manager.LaunchNewBrowser().</td>
 	<td>"InternetExplorer"<br>
 	"FireFox"<br>
 	"AspNetHost"<br>
-	"Safari"h</td>
+	"Safari"</td>
 	<td>"InternetExplorer"</td>
 </tr>
 <tr>
-	<td>**EnableScriptLogging**</td>
+	<td><strong>EnableScriptLogging</strong></td>
 	<td>Globally enables or disables logging of JavaScript execution.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**EnableSilverlight**</td>
-	<td>Controls whether or not Silverlight test automation is enabled.</td>
-	<td>true<br>
-	false</td>
-	<td>false</td>
-</tr>
-<tr>
-	<td>**EnableUILessRequestViewing**</td>
+	<td><strong>EnableUILessRequestViewing</strong></td>
 	<td>Controls whether or not to allow debugging of UILess page requests using a UI browser like Internet Explorer.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**ExecuteCommandTimeout**</td>
+	<td><strong>ExecuteCommandTimeout</strong></td>
 	<td>The amount of time to wait for a response to be received from the browser (in milliseconds) after sending it a command request. For example: if there is no response from the browser within this amount of time after sending it a click request, the framework will throw a <a href="http://msdn2.microsoft.com/en-us/library/system.timeoutexception%28vs.80%29.aspx" target="_blank">TimeoutException</a>.</td>
 	<td>0 to int.MaxValue</td>
 	<td>20000</td>
 </tr>
 <tr>
-	<td>**ExecutionDelay**</td>
+	<td><strong>ExecutionDelay</strong></td>
 	<td>Sets the amount of execution delay (in milliseconds) between commands. This can help in observing test execution.</td>
 	<td>0 to int.MaxValue</td>
 	<td>0</td>
 </tr>
 <tr>
-	<td>**IsStressRecordingMode**</td>
+	<td><strong>IsStressRecordingMode</strong></td>
 	<td>Used internally by Automation Design Canvas only.</td>
 	<td></td>
 	<td></td>
 </tr>
 <tr>
-	<td>**IsUserInteractiveMode**</td>
+	<td><strong>IsUserInteractiveMode</strong></td>
 	<td>This read-only setting indicates whether or not the currently logged on user is an interactive user. Normally this will always be true unless you are logged in under a non-interactive account. For example, if you create another account on your machine and from your current account launch a process using that other account without interactively logging into that account. That is when this property will be set to false. This is a common scenario when performing continuous integration within a build system and running tests. Usually there is a machine that has an account that VisualStudio simply uses to logon the machine non-interactively, build a product and launch tests.</td>
 	<td>true<br>
 	false</td>
 	<td>Depends on run time environment.</td>
 </tr>
 <tr>
-	<td>**KillBrowserProcessOnClose**</td>
-	<td>Gets or sets whether to make sure the browser process is killed when closing the browser. **Note:** Firefox is a single process browser. If you are using multiple browser instances and this setting is on, it will kill all open instances of Firefox.</td>
+	<td><strong>KillBrowserProcessOnClose</strong></td>
+	<td>Gets or sets whether to make sure the browser process is killed when closing the browser. <strong>Note:</strong> Firefox is a single process browser. If you are using multiple browser instances and this setting is on, it will kill all open instances of Firefox.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**LocalWebServer**</td>
+	<td><strong>LocalWebServer</strong></td>
 	<td>Controls whether or not to use the local ASP.NET development server. When set to true, be sure to set WebAppPhysicalPath to the full physical path of the root of your ASP.NET development server.</td>
 	<td>None<br>
 	AspNetDevelopmentServer</td>
 	<td>None</td>
 </tr>
 <tr>
-	<td>**LogAnnotations**</td>
+	<td><strong>LogAnnotations</strong></td>
 	<td>Controls whether to log annotations to the log file.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**LogLocation**</td>
+	<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>**QueryEventLogErrorsOnExit**</td>
+	<td><strong>QueryEventLogErrorsOnExit</strong></td>
 	<td>Controls whether or not the Manager object will query Windows Application Event log on exit for any error logged from automation clients. Any errors will be logged to the test log.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**RecycleBrowser**</td>
+	<td><strong>RecycleBrowser</strong></td>
 	<td>When set to true, one instance of the browser will be launched and recycled through out the entire test class and tests until Manager.Dispose is called.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**SimulatedMouseMoveSpeed**</td>
+	<td><strong>SimulatedMouseMoveSpeed</strong></td>
 	<td>Sets the simulated mouse move speed for Desktop.Mouse.Move()/DragDrop() operations in pixels/millisecond. Typically values are between 0.1f - 0.5f.</td>
 	<td>0 to Single.MaxValue</td>
 	<td>0.3</td>
 </tr>
 <tr>
-	<td>**UseHttpProxy**</td>
-	<td>Gets/Sets whether to use the built-in http proxy during automation. **NOTE:** will be forced to true when EnableSilverlight is set to true.</td>
+	<td><strong>UseHttpProxy</strong></td>
+	<td>Gets/Sets whether to use the built-in http proxy during automation. <strong>NOTE:</strong> will be forced to true when EnableSilverlight is set to true.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**VerboseHttpProxy**</td>
+	<td><strong>VerboseHttpProxy</strong></td>
 	<td>Gets/Sets whether the HTTP proxy produces lots of tracing output.</td>
 	<td>true<br>
 	false</td>
 	<td>false</td>
 </tr>
 <tr>
-	<td>**WaitCheckInterval**</td>
+	<td><strong>WaitCheckInterval</strong></td>
 	<td>Controls the rate that the condition is tested by the HtmlWait class. This value specifies the number of milliseconds to wait between tests of the condition.</td>
 	<td>1 to int.MaxValue</td>
 	<td>500</td>
 </tr>
 <tr>
-	<td>**WebAppPhysicalPath**</td>
+	<td><strong>WebAppPhysicalPath</strong></td>
 	<td>This setting is used when LocalWebServer is set to 'AspNetDevelopmentServer'. It must be the full physical path to the web application root that you are testing or a path relative to the location of the .config file.</td>
 	<td>The full physical path to the web application root.</td>
 	<td>string.Empty</td>
 </tr>
-<table>
\ No newline at end of file
+</table>
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing.md
index f0859d74..c1c98df4 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/visual-capturing.md
@@ -4,44 +4,44 @@ page_title: Visual Capturing
 description: "Test Studio Testing Framework support in coded tests to capture the visual state of the current active application window."
 position: 1
 ---
-#Visual Capturing#
+# Visual Capturing
 
 
-##Visual Capturing of Browser States and Win32 Windows##
+## Visual Capturing of Browser States and Win32 Windows
 
 Each Telerik Testing Framework Window object provides functionality to capture the visual bitmaps of the actual window it represents. You can capture the entire window or a targeted portion of that window using the Window.GetBitmap() method. You can use this method for any Win32 window represented by the Window object. Lets take a quick example:
 
 
-```C#
+````C#
 // Get the current browser window bitmap.
 System.Drawing.Bitmap browserImage = ActiveBrowser.Window.GetBitmap();
-```
-```VB
+````
+````VB
 Dim browserImage As System.Drawing.Bitmap = ActiveBrowser.Window.GetBitmap()
-```
+````
 
 The Log uses the above method to capture the browser window when calling the Log.CaptureBrowser() method. The log also saves the captured bitmap to the 'LogLocation' as provided by your settings and a line is added to the log file that points to that bitmap file. The bitmaps are also added to the Log.CapturedBitmaps[] array. For example:
 
 
-```C#
+````C#
 // Capture the bitmap of my current ActiveBrowser and save it to the LogLocation
 // [LogLocation is set using the Settings object that is passed in to the Manager's constructor]
 Manager.Log.CaptureBrowser(Manager.ActiveBrowser);
   
 // Note: If you are automating multiple browser instances, you can simply
 // call the CaptureBrowser() passing in any instance from the Manager.Browser[] collection.
-```
-```VB
+````
+````VB
 Manager.Log.CaptureBrowser(Manager.ActiveBrowser)
-```
+````
 
-##Visual Capturing of Elements##
+## Visual Capturing of Elements
 
 In addition to capturing the entire window, you can also capture targeted portions of that window. Such functionality can be extremely useful when combined with the functionality provided by each DOM element in Telerik Testing Framework. For example, you can use the Element.GetRectangle() to get the coordinates of a specific element and pass that to the Window.GetBitmap(targetRectangle) to visually capture that element. You can then do bitmap comparisons of that element to a base line or even compare it across browsers.
  
 Let's take a simple example to demonstrate this functionality. Assume we have the following simple page:
 
-```HTML
+````HTML
 <html>
    <head>
     <title>Visual Capturing sample</title>
@@ -61,7 +61,7 @@ Let's take a simple example to demonstrate this functionality. Assume we have th
      </div>
    </body>
 </html>
-```
+````
 
 The above page renders as follows:
 
@@ -69,20 +69,20 @@ The above page renders as follows:
 
 The below code shows how we can get the visual capture of the second 'div' element:
 
-```C#
+````C#
 // Get the element
 Element myDiv = ActiveBrowser.Find.ById("mydiv");
   
 // Capture it visually as a bitmap
 System.Drawing.Bitmap divimage = ActiveBrowser.Window.GetBitmap(myDiv.GetRectangle());
-```
-```VB
+````
+````VB
 ' Get the element
 Dim myDiv As Element = ActiveBrowser.Find.ById("mydiv")
   
 ' Capture it visually as a bitmap
 Dim divimage As System.Drawing.Bitmap = ActiveBrowser.Window.GetBitmap(myDiv.GetRectangle())
-```
+````
 
 The divimage bitmap captured object is:
 
diff --git a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/win32-windows.md b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/win32-windows.md
index ab2f9e49..4559dd39 100644
--- a/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/win32-windows.md
+++ b/docs/testing-framework/write-tests-in-code/intermediate-topics-wtc/win32-windows.md
@@ -4,7 +4,7 @@ page_title: Win32 Windows
 description: "Test Studio Testing Framework support in coded tests for Win32 Windows through the WindowManager and Window classes"
 position: 1
 ---
-#Native Win32 Windows Handling#
+# Native Win32 Windows Handling
 
 Telerik Testing Framework provides generic support for Win32 Windows handling. Under the 'ArtOfTest.Common.Win32' namespace, Telerik Framework provides two key objects that you can use in your test code to generically manage Win32 Windows and Dialogs.
 
@@ -17,7 +17,7 @@ In addition to the functionality described above, the WindowManager exposes a st
 Let's take an example to illustrate how these two classes can help provide automation functionality for native Win32 windows:
 
 
-```C#
+````C#
 Window vsWindow = null;
   
 // Get all desktop Windows
@@ -39,8 +39,8 @@ foreach (Window win in winManager.Items)
 // Find the vsWindow recursively. Passing IntPtr.Zero will start from the desktop.
 Window vsWindowRecur = WindowManager.FindWindowRecursively(
      IntPtr.Zero, "Microsoft Visual Studio", true, 0);
-```
-```VB
+````
+````VB
 Dim vsWindow As Window = Nothing
   
 ' Get all desktop Windows
@@ -61,5 +61,5 @@ Next
 ' Find the vsWindow recursively. Passing IntPtr.Zero will start from the desktop.
 Dim vsWindowRecur As Window = WindowManager.FindWindowRecursively( _
      IntPtr.Zero, "Microsoft Visual Studio", True, 0)
-```
+````
 
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/element-validation.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/element-validation.md
deleted file mode 100644
index 6c1a11b8..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/element-validation.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Element Validation
-page_title: Element Validation
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 3
----
-#Validating Properties of Silverlight Elements#
-
-```C#
-Assert.IsTrue(guidanceOverlays.Count == 15);
-Assert.IsTrue(CompareUtils.NumberCompareRange(foundPatients.Count, 93, 105, NumberRangeCompareType.InRange);
-Assert.IsTrue(patientSearchItem.Find.ByName("Address").Visibility == Visibility.Collapsed);
-Assert.IsTrue(searchScroll.VerticalOffset == 2000);
-Assert.AreEqual<System.Drawing.Rectangle>(new System.Drawing.Rectangle(1700, 259, 813, 465), admin1.GetScreenRectangle());
-```
-```VB
-app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy
-Assert.IsTrue(CompareUtils.NumberCompareRange(foundPatients.Count, 93, 105, NumberRangeCompareType.InRange))
-Assert.IsTrue(patientSearchItem.Find.ByName("Address").Visibility = Visibility.Collapsed)
-Assert.AreEqual(2000, searchScroll.VerticalOffset)
-Assert.AreEqual(Of System.Drawing.Rectangle)(New System.Drawing.Rectangle(1700, 259, 813, 465), admin1.GetScreenRectangle())
-```
-
-
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object.md
deleted file mode 100644
index b7934ea2..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object.md
+++ /dev/null
@@ -1,252 +0,0 @@
----
-title: FrameworkElement Object
-page_title: FrameworkElement Object
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 3
----
-#FrameworkElement Object#
-
-The **FrameworkElement** object is analogous to the <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement(VS.95).aspx" target="_blank">FrameworkElement</a> in Silverlight and is the base object that all visual elements and controls inherit from in the **ArtOfTest.WebAii.Silverlight.UI** namespace. For customers interested in our extensibility model, the Silverlight Extension does not expose a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.95).aspx" target="_blank">UIElement</a> and therefore, our **FrameworkElement** can be viewed as the combination of Silverlight's **UIElement + FrameworkElement**.
- 
-The **FrameworkElement** and all objects that inherit from it get the following infrastructure properties:
-
-<table class="docs">
-<tr>
-	<th>Property</th><th>Description</th>
-</tr>
-<tr>
-	<td>**AbsoluteSiblingTagIndex**</td><td>Get the sibling tag index of this FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**AbsoluteTagIndex**</td><td>Get the absolute index of this XAML tag in the Visual Tree.</td>
-</tr>
-<tr>
-	<td>**ActualHeight**</td><td>Gets the rendered height of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**ActualWidth**</td><td>Gets the rendered width of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**Application**</td><td>Get the Application object that owns this element.</td>
-</tr>
-<tr>
-	<td>**AutomationId**</td><td>Gets the AutomationId set on this element if any.</td>
-</tr>
-<tr>
-	<td>**Children**</td><td>Gets the visual children of this element.</td>
-</tr>
-<tr>
-	<td>**Clip**</td><td>Gets or sets the <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.geometry(VS.96).aspx" target="_blank">Geometry</a> used to define the outline of the contents of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
-</tr>
-<tr>
-	<td>**Depth**</td><td>Get the depth of this element in the Visual Tree.</td>
-</tr>
-<tr>
-	<td>**EnableValidateMouseLocation**</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
-</tr>
-<tr>
-	<td>**Find**</td><td>Get the Find object used to search the visual children of this element.</td>
-</tr>
-<tr>
-	<td>**Height**</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**HorizontalAlignment**</td><td>Gets or sets the horizontal alignment characteristics applied to a FrameworkElement when it is composed within a layout parent, such as a panel or items control.</td>
-</tr>
-<tr>
-	<td>**Host**</td><td>Returns the SilverlightApp object owning this FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**IsHitTestVisible**</td><td>Gets or sets whether the contained area of this UIElement can return true values for hit testing.</td>
-</tr>
-<tr>
-	<td>**IsTestRegion**</td><td>Returns whether or not this FrameworkElement is contained inside a TestRegion (not supported in WebAii 2.0 Beta 2).</td>
-</tr>
-<tr>
-	<td>**Language**</td><td>Gets or sets localization/globalization language information that applies to a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**Margin**</td><td>Gets or sets the outer margin of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**MaxHeight**</td><td>Gets or sets the maximum height constraint of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**MaxWidth**</td><td>Gets or sets the maximum width constraint of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**MinHeight**</td><td>Gets or sets the minimum height constraint of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**MinWidth**</td><td>Gets or sets the minimum width constraint of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**Name**</td><td>Gets (or sets, but see Remarks) the identifying name of the object. The name provides a reference that is initially markup-compiled. After a XAML processor creates the object tree from markup, run-time code can refer to a markup element by this name.</td>
-</tr>
-<tr>
-	<td>**Opacity**</td><td>Gets or sets the degree of the object's opacity.</td>
-</tr>
-<tr>
-	<td>**OpacityMask**</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
-</tr>
-<tr>
-	<td>**Projection**</td><td>Gets or sets the perspective projection (3-D effect) to apply when rendering this <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
-</tr>
-<tr>
-	<td>**RenderSize**</td><td>Gets the final render size of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
-</tr>
-<tr>
-	<td>**RenderTransform**</td><td>Gets or sets transform information that affects the rendering position of a UIElement.</td>
-</tr>
-<tr>
-	<td>**RenderTransformOrigin**</td><td>Gets or sets the origin point of any possible render transform declared by <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement.rendertransform(VS.96).aspx" target="_blank">RenderTransform</a>, relative to the bounds of the <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
-</tr>
-<tr>
-	<td>**Resources**</td><td>Gets the locally defined resource dictionary. In XAML, you can establish resource items as child object elements of the <object.Resources> property element, through XAML implicit collection syntax.</td>
-</tr>
-<tr>
-	<td>**Style**</td><td>Gets or sets an instance <a href="http://msdn.microsoft.com/en-us/library/system.windows.style(VS.96).aspx" target="_blank">Style</a> that is applied for this object during rendering.</td>
-</tr>
-<tr>
-	<td>**TagNameIndex**</td><td>Gets the tag name index of the xaml tag name in the visual tree.</td>
-</tr>
-<tr>
-	<td>**TechnologyType**</td><td>Get the technology type of this element. Always returns TechnologyType.Silverlight for FrameworkElement objects.</td>
-</tr>
-<tr>
-	<td>**TextContent**</td><td>Gets the text content of this framework element if any.</td>
-</tr>
-<tr>
-	<td>**UseLayoutRounding**</td><td>Gets or sets a value that determines whether rendering for the object and its subtree should use rounding behavior that aligns rendering to whole pixels.</td>
-</tr>
-<tr>
-	<td>**User**</td><td>Gets the UI interaction object that allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
-</tr>
-<tr>
-	<td>**VerticalAlignment**</td><td>Gets or sets the vertical alignment characteristics applied to a FrameworkElement when it is composed within a parent object such as a panel or items control.</td>
-</tr>
-<tr>
-	<td>**Visibility**</td><td>Gets or sets the visibility of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>. A <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> that is not visible does not render and does not communicate its desired size to layout.</td>
-</tr>
-<tr>
-	<td>**Wait**</td><td>Gets a VisualWait object to be used on waiting for Visual elements in the VisualTree.</td>
-</tr>
-<tr>
-	<td>**Width**</td><td>Gets or sets the width of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**XamlTag**</td><td>Get the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
-</tr>
-<table>
-
-##The FrameworkElement Methods##
-
-Before describing all of the methods of the FrameworkElement object I'd like to point out the following special features:
-
-1. VisualTree navigation: All FrameworkElements enable you to navigate the visual tree up or down. The object exposes methods and properties like **Parent**, **Children**, **NextSibling**, **PreviousSibling**, **AnySibling<T>**. The navigation also supports control sensitive navigation. For example, if you would like to find the parent 'Grid' that a certain text is contained in you do the following:
-
-	
-	```C#
-	WpfApplication app = Manager.ActiveApplication;
-	Assert.IsNotNull(app);
-
-	Grid containerGrid = app.Find.ByText("SomeText").Parent("Grid").As<Grid>();
-
-	```
-
-	__OR__
-
-	If you are working with a custom control that doesn't have a strongly-typed object under **ArtOfTest.WebAii.Silverlight.UI**, the navigation methods all offer a non-generic version that can be used to search for a certain type. For example, let's say you are trying to find the custom control "Bar" that contains some text, then you can do the following:
-
-	```C#
-	WpfApplication app = Manager.ActiveApplication;
-	Assert.IsNotNull(app);
-
-	FrameworkElement barElement = app.Find.ByText("SomeText").Parent("Bar");
-	
-	```
-
-	**Parent**, **NextSibling**, **PreviousSibling & AnySibling** all offer a non-generic versions in addition to the generic one.
-
-2. **User Interaction object:**
-
-	The FrameworkElement object exposes a user interaction object. The object is exposed as a property named '**User**'. User then exposes all the real automation methods like moving the mouse to click an element, type a text, mouse enter, mouse leave…etc.
-
-	**Note:** One of the reasons why we moved these methods into their own object under 'User.xxx' is to help users differentiate between automation that is done by setting/getting properties vs. real automation that used the mouse or keyboard to invoke actions.
-
-3. **Element coordinates:** 
-
-
-	All FrameworkElements offer the ability to get both the relative coordinates of the element within the Silverlight application and the actual coordinates in screen coordinates. The two methods are **GetRectangle()**and **GetScreenRectangle()**.
-
-	**Note:** Given that WPF/Silverlight applications allow for rich transforms for visual elements (i.e. rotate, zoom….etc) and some elements like ellipses don't really conform to a rectangle per-say, our coordinate calculations will always return the largest rectangle that contains the actual element with its center right at the center of the element. For example, a GetRectangle on an ellipse will return this:
-
-	![SL app][1]
-
-	 *The highlighting above is using the FrameworkElement.Highlight() method.*
-
-4. **XML Representation**:
-
-
-	Every **FrameworkElement** has a **ToXml()** method on it that returns the VisualTree of that element as an XML formatted string. This is very useful when trying to understand the visual tree at a certain state. [Hint: You can get the entire visual tree of an app by calling **app.VisualTree.Root.ToXml()**]
-
-These are all of the FrameworkElement methods available for use by your automation code:
-
-<table class="docs">
-<tr>
-	<th>Method</th><th>Description</th>
-</tr>
-<tr>
-	<td>**AnySibling(T)**</td><td>Return any sibling of this control of type T. The framework first searches for a previous sibling having the specified type. If it finds one that sibling is returned. If it doesn't find one then it searches for the next sibling. If it find one that sibling is returned, otherwise null (Nothing in VB.NET) is returned.</td>
-</tr>
-<tr>
-	<td>**As(T)**</td><td>Return this framework element as a strongly-typed control of type T.</td>
-</tr>
-<tr>
-	<td>**CastAs(T)**</td><td>Returns this framework element as a strongly-typed control of type T without enforcing tag name to match the type it is being cast to. This functions gives you free casting abilities between types.</td>
-</tr>
-<tr>
-	<td>**Equals**</td><td>Determines whether this FrameworkElement is equal to another, by comparing their AutomationReferences.</td>
-</tr>
-<tr>
-	<td>**GetChildren**</td><td>Get the children of this framework element.</td>
-</tr>
-<tr>
-	<td>**GetNextSibling**</td><td>Get the next sibling of this FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**GetParent**</td><td>Get the Parent of this element.</td>
-</tr>
-<tr>
-	<td>**GetPrevSibling**</td><td>Get the previous sibling.</td>
-</tr>
-<tr>
-	<td>**GetRectangle**</td><td>Get the bounding rectangle of this FrameworkElement within the owning Silverlight application.</td>
-</tr>
-<tr>
-	<td>**GetScreenRectangle**</td><td>Return the actual coordinates of this element in absolute screen coordinates taking into account the location of the overall plug-in on the page.</td>
-</tr>
-<tr>
-	<td>**Highlight**</td><td>Highlight this element in the Silverlight application.</td>
-</tr>
-<tr>
-	<td>**NextSibling**</td><td>Get the next sibling control of a specific type.</td>
-</tr>
-<tr>
-	<td>**Parent**</td><td>Get the parent FrameworkElement of this element.</td>
-</tr>
-<tr>
-	<td>**PreviousSibling**</td><td>Get the previous sibling control of a specific type.</td>
-</tr>
-<tr>
-	<td>**Refresh**</td><td>Refresh this FrameworkElement within the VisualTree.</td>
-</tr>
-<tr>
-	<td>**ScrollToVisible**</td><td>Scrolls the web page so that this element is visible in the browser window.</td>
-</tr>
-<tr>
-	<td>**ToXml**</td><td>Gets an XML formatted string that represents this element and all its children This XML represents the VisualTree.</td>
-</tr>
-<table>
-
-[1]: /img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation/fig1.png
\ No newline at end of file
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
deleted file mode 100644
index 89d7aff4..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions.md
+++ /dev/null
@@ -1,224 +0,0 @@
----
-title: Invoking Actions
-page_title: Invoking Actions
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 3
----
-#Invoking Actions on Elements#
-
-Once you have found an element you can then interact with it. Many different types of interactions are supported like clicking, mouse hover over, mouse wheel-related actions, keyboard clicks etc.
-
-1.&nbsp; <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Clicking-On-an-Element">Clicking On an Element</a> - invoke a click on a FrameworkElement.
-
-2.&nbsp; <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Sending-Text-to-a-Control">Sending Text to a Control</a> - type text content into a FrameworkElement.
-
-3.&nbsp; <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Mouse-Actions">Mouse Actions</a> - invoking different mouse actions on FrameworkElement.
-
-4.&nbsp; <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Framework-Element-Properties-and-Actions">Framework Element Properties and Actions.</a>
-	* <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#UI-Element-Actions">UI Element Actions</a> - understanding wrappers.
-	* <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Telerik-Testing-Framework-Specific-Properties">Telerik Testing Framework Specific Properties</a> - commonly used Properties of Telerik's FrameworkElement.
-	* <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Telerik-Testing-Framework-Specific-Methods">Telerik Testing Framework Specific Methods</a> - commonly used Methods of Telerik's FrameworkElement.
-	* <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Getting-and-Setting-Properties-on-Elements">Getting and Setting Properties on Elements</a> - working with non-built in Properties.
-5. <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions#Invoking-Element-Methods">Invoking Element Methods</a> - invoke any method attached to an element.
-
-##Clicking On an Element##
-
-To invoke a UI action, use the User object that is attached to every UI element. For example, to click on an element such as a button, enter code like this:
-
-```C#
-//In this example app can be a Silverlight application or the MainWindow element of a WPF application 
-// Click the ShowGuide button.
-app.Find.ByName("guideButton").User.Click();
- 
-// Right click the ShowGuide button 5 pixels away from the center of the control
-app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick,
-     new System.Drawing.Point(5, 5), OffsetReference.AbsoluteCenter);
-```
-```VB
-'In this example app can be a Silverlight application or the MainWindow of a WPF application 
-' Click the ShowGuide button.
-app.Find.ByName("guideButton").User.Click()
- 
-' Right click the ShowGuide button 5 pixels away from the center of the control
-app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick, _
-                                       New System.Drawing.Point(5, 5), _
-                                        OffsetReference.AbsoluteCenter)
-```
-
-##Sending Text to a Control##
-
-To send text to the control use one of the following lines of code:
-
-```C#
-searchText.User.TypeText("Abe Lincoln", 100);
- 
-searchText.User.KeyPress(System.Windows.Forms.Keys.L, 100);
- 
-searchText.User.KeyDown(System.Windows.Forms.Keys.L);
-searchText.User.KeyUp(System.Windows.Forms.Keys.L);
-```
-```VB
-searchText.User.TypeText("Abe Lincoln", 100)
- 
-searchText.User.KeyPress(Windows.Forms.Keys.L, 100)
- 
-searchText.User.KeyDown(Windows.Forms.Keys.L)
-searchText.User.KeyUp(Windows.Forms.Keys.L)
-```
-
-##Mouse Actions##
-
-To perform one of the various possible mouse actions use one of the following lines of code:
-
-```C#
-admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"));
-admin1.User.HoverOver();
-admin1.User.MouseEnter(OffsetReference.LeftCenter);
-admin1.User.MouseLeave(OffsetReference.RightCenter);
-admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, false);
-```
-```VB
-admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"))
-admin1.User.HoverOver()
-admin1.User.MouseEnter(OffsetReference.LeftCenter)
-admin1.User.MouseLeave(OffsetReference.RightCenter)
-admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, False)
-```
-
-##Framework Element Properties and Actions##
-
-All of the Telerik Testing Framework UI controls derive from the FrameworkElement object. Our FrameworkElement object mirrors as closely as possible XAML's FrameworkElement as defined in MSDN <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement%28VS.96%29.aspx" target="_blank">here</a>. For customers interested in our extensibility model, the Silverlight Extension does not expose a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> and therefore, our FrameworkElement can be viewed as the combination of Silverlight/WPF's UIElement + FrameworkElement. These are just few examples of the many available properties of our FrameworkElement object:
-
-<table class="docs">
-<tr>
-	<th>Property</th><th>Description</th>
-</tr>
-<tr>
-	<td>**AutomationId**</td><td>Retrieves the Automation ID assigned to this element.</td>
-</tr>
-<tr>
-	<td>**Children**</td>Retrieves a list of elements that are children of this element in the visual tree.</td>
-</tr>
-<tr>
-	<td>**Clip**</td><td>Gets or sets the Geometry used to define the outline of the contents of a UI Element.</td>
-</tr>
-<tr>
-	<td>**Height**</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**Opacity**</td><td>Gets or sets the degree of the object's opacity.</td>
-</tr>
-<tr>
-	<td>**OpacityMask**</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
-</tr>
-<tr>
-	<td>**Width**</td><td>Gets or sets the suggested width of a FrameworkElement.</td>
-</tr>
-<table>
-
-##UI Element Actions##
-
-Each UI element wrapper class contained in Telerik Testing Framework has a set of properties used to access the properties appropriate for that UI element. For example: The Calendar control has a SelectedDate property that you can use to read and/or set the currently selected date of the control. It also has a SelectionMode property you can use to read and/or change the selection mode from a single date to a multi-range date selection. The CheckBox control has an IsChecked property you can use to read/set the checked state of the control and so on.
-
-##Telerik Testing Framework Specific Properties##
-
-We have implemented a few special properties in our FrameworkElement object to aid in automation. These include:
-
-<table class="docs">
-<tr>
-	<th>Property</th><th>Description</th>
-</tr>
-<tr>
-	<td>**AbsoluteSiblingTagIndex**</td><td>Returns the sibling tag index of this FrameworkElement relative to its other siblings within the Visual Tree.</td>
-</tr>
-<tr>
-	<td>**AbsoluteTagIndex**</td><td>Returns the absolute index of this XAML tag within the entire Visual Tree.</td>
-</tr>
-<tr>
-	<td>**Application**</td><td>Gets the Application object that owns this element.</td>
-</tr>
-<tr>
-	<td>**EnableValidateMouseLocation**</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
-</tr>
-<tr>
-	<td>**Find**</td><td>Gets the Find object that can be used to search the visual children of this element.</td>
-</tr>
-<tr>
-	<td>**TagNameIndex**</td><td>Gets the tag name index of the XAML tag name in the visual tree.</td>
-</tr>
-<tr>
-	<td>**User**</td><td>Gets the UI interaction object which allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
-</tr>
-<tr>
-	<td>**Wait**</td><td>Gets a VisualWait object you can use to wait for Visual elements in the Visual Tree.</td>
-</tr>
-<tr>
-	<td>**XamlTag**</td><td>Gets the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
-</tr>
-<table>
-
-##Telerik Testing Framework Specific Methods##
-
-The FrameworkElement class implements a number of methods just for purpose of test automation. Some of the most commonly used include:
-
-<table class="docs">
-<tr>
-	<th>Property</th><th>Description</th>
-</tr>
-<tr>
-	<td>**CastAs\<T>()**</td><td>Returns a FrameworkElement as a strongly-typed control. Does not enforce a tagname to match the type.</td>
-</tr>
-<tr>
-	<td>**GetChildren()**</td>Returns the child elements of the FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**GetNextSibling()**</td><td>Returns the next sibling of  the FrameworkElement.</td>
-</tr>
-<tr>
-	<td>**Parent()**</td><td>Returns the parent element of the current Framework Element</td>
-</tr>
-<tr>
-	<td>**ScrollToVisible()**</td><td>Scrolls the browser so that the Framework Element is visible.</td>
-</tr>
-<table>
-
-##Getting and Setting Properties on Elements##
-
-If the property of an element you want to get or set isn't available as a property in the UI element wrapper object, you can use the GetProperty and SetProperty from the FrameworkElement object to get/set it. This is especially useful if you start designing your own custom Silverlight UI controls or use a third party custom control. Let's suppose I have a UI element that represents an airline ticket. One of the many obvious properties such a control would need to have is flight number. To fetch this property from the control I can use code like this:
-
-```C#
-// Fetch the flight number from the ticket
-FrameworkElement ticket = app.FindName("airlineTicket");
-AutomationProperty flightNoProperty = new AutomationProperty("flightNo", typeof(string));
-string flightNo = (string)ticket.GetProperty(flightNoProperty);
- 
-// Update the flight number on the ticket
-ticket.SetProperty(flightNoProperty, "HX-1572");
-```
-```VB
-' Fetch the flight number from the ticket
-Dim ticket As FrameworkElement = app.FindName("airlineTicket")
-Dim flightNoProperty As New AutomationProperty("flightNo", GetType(String))
-Dim flightNo As String = DirectCast(ticket.GetProperty(flightNoProperty), String)
- 
-' Update the flight number on the ticket
-ticket.SetProperty(flightNoProperty, "HX-1572")
-```
-
-##Invoking Element Methods##
-
-Another advanced feature of the framework is the ability to invoke any method attached to an element. Here's how to invoke the ScrollToVerticalOffset method of a ScrollViewer element.
-
-```C#
-ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
-searchScroll = app.FindName().Find.ByType<>();
- 
-AutomationMethod scrollVert = new AutomationMethod("ScrollToVerticalOffset", null);
-searchScroll.InvokeMethod(scrollVert, 2000);
-```
-```VB
-Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
- 
-Dim scrollVert As New AutomationMethod("ScrollToVerticalOffset", Nothing)
-searchScroll.InvokeMethod(scrollVert, 2000)
-```
\ No newline at end of file
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
deleted file mode 100644
index b4929732..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/locating-elements.md
+++ /dev/null
@@ -1,144 +0,0 @@
----
-title: Locating Elements
-page_title: Locating Elements
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/locating-elements.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/locating-elements
-position: 3
----
-#Locating Elements in Silverlight and WPF applications 
-
-Before you can automate interaction with elements contained in a Silverlight/WPF application, you need to first locate the elements contained within the application. For complex applications, locating elements is probably going to be one of the more time consuming tasks. Testers will need to spend time understanding how to reliably find an element. Silverlight/WPF applications that we studied that rely heavily on control templates and data binding produce quite complex visual trees. Their elements are not easily searchable by **Find.ByName()** given the different <a href=http://msdn.microsoft.com/en-us/library/cc189026%28VS.95%29.aspx" target="_blank">Silverlight</a> and <a href="http://msdn.microsoft.com/en-us/library/ms746659.aspx" target="_blank">WPF</a> name scopes created, and the duplication of names within those templates.
-
-1. <a href="#the-find-strategy">The Find Strategy</a> - change the 'Strategy' property that controls how the method behaves when searching for an element.
-
-2. <a href="#finding-all-elements">Finding All Elements</a> - return a list of the elements contained in the application.
-
-3. <a href="#scoped-searches">Scoped Searches</a> - search for a specific element based on its parent.
-
-4. <a href="#finding-elements-by-xamlfindexpression">Finding Elements by XamlFindExpression</a> - search for an element using a FindExpression.
-
-The simplest method of searching is to use the **Find.ByName(String name)** method or the **Find.ByName\<TControl>(String name)** method. Both methods take a string parameter that specifies the name of the element to locate in the application. The first method returns a FrameworkElement object while the second method returns an object of type T having the specified name. If an element having the specified name does not exist or is not currently visible, or if the found element cannot be cast into type T, the functions will return null ('Nothing' in VB.NET). For example:
-
-```C#
-FrameworkElement zoomBox = app.FindName("zoomBox");
-TextBox searchText = app.FindName<TextBox>("searchText");
-```
-```VB
-Dim zoomBox As FrameworkElement = app.FindName("zoomBox")
-Dim searchText As TextBox = app.FindName(Of TextBox)("searchText")
-```
-
-You might be asking "How do I know what name to use to find the element I want?" There really are only a few ways to find out:
-
-1. Refer to the design document of the application. Hopefully the name has been specified.
-
-2. Ask the developer what the name of a particular element is.
-
-3. Examine the source code to find the name.
-
-4. If the above methods are not available to you, you will have to resort to some sort of Silverlight/WPF spy utility such as this one to discover the name.
- 
-The **Find** object offers a rich set of search methods that enable you to not only find elements using their names, but also by their text or type. Combined with type filtering, LINQ, FrameworkElement navigation, and the Find.AllByXXX routines, you get a rich set of routines that enables you to find any framework element in the tree.
- 
-All of the common methods for finding an element to operate on are:
-
-<table class="docs">
-<tr>
-	<th>Method</th><th>Description</th>
-</tr>
-<tr>
-	<td>**Find.ByName()/Find.ByName\<T>**</td><td>Returns the first element having the specified name.</td>
-</tr>
-<tr>
-	<td>**Find.ByText**</td><td>Returns the first TextBlock that matches the text provided.</td>
-</tr>
-<tr>
-	<td>**Find.ByAutomationId**</td><td>Returns an element having the automation ID you specify.</td>
-</tr>
-<tr>
-	<td>**Find.ByType**</td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
-</tr>
-<table>
-
-##The Find Strategy##
-
-The Find object has a 'Strategy' property that controls how the method behaves when searching for an element. To change the strategy simply change the Strategy property on the Find object. The following strategies can be set:
-
-<table class="docs">
-<tr>
-	<th>Strategy</th><th>Description</th>
-</tr>
-<tr>
-	<td>**AlwaysWaitForElementsVisible**</td><td>In this mode the Find object always waits for the element to exist and for its Visibility property to equal "Visible". The default amount of time it will wait is 5 seconds. This timeout can be changed by modifying the Find.Timeout property before using the Find object. This strategy is the default setting.</td>
-</tr>
-<tr>
-	<td>**WhenNotVisibleReturnElementProxy**</td><td>In this mode an 'Element Proxy' is returned if the element cannot be found right away. An 'Element Proxy' is a lightweight FrameworkElement object that only contains information on how to locate the desired element in the Visual Tree. This is useful when you want to use the SilverlightApp.Wait.ForExists method.</td>
-</tr>
-<tr>
-	<td>**WhenNotVisibleReturnNull**</td><td>In this mode null (Nothing in VB.NET) is returned if the element cannot be found right away.</td>
-</tr>
-<tr>
-	<td>**WhenNotVisibleThrowException**</td><td>In this mode a generic exception is thrown if the element cannot be found right away.</td>
-</tr>
-<table>
-
-##Finding All Elements##
-
-Sometimes you may need to fetch a list of the elements contained in the application. Suppose we want a list of all the DataGrids contained in the application. Either of the following lines of code will return this list:
-
-
-```C#
-IList<FrameworkElement> dataGrids1 = app.Find.AllByType("DataGrid");
-IList<DataGrid> dataGrids2 = app.Find.AllByType<DataGrid>();
-```
-```VB
-Dim dataGrids1 As IList(Of FrameworkElement) = app.Find.AllByType("DataGrid")
-Dim dataGrids2 As IList(Of DataGrid) = app.Find.AllByType(Of DataGrid)()
-```
-
-All of the Find.AllByxxx functions are:
-
-<table class="docs">
-<tr>
-	<th>Method</th><th>Description</th>
-</tr>
-<tr>
-	<td>**Find.AllByName()/Find.AllByName\<T>**</td><td>Find all elements that have a specific name. Allows filtering on a specific control type.</td>
-</tr>
-<tr>
-	<td>**Find.AllByText()**</td><td>Find all TextBlocks that contain a specific text. Use p:text to search for partial text.</td>
-</tr>
-<tr>
-	<td>**Find.AllByType()/Find.AllByType\<T>**</td><td>Find all elements of certain type. i.e Button, Grid..etc. Filtering on type is inherit here.</td>
-</tr>
-<tr>
-	<td>**Find.AllByAutomationID()/Find.AllByAutomationID\<T>**</td><td>Find all elements that have a specific automation ID. Allows filtering on a specific control type.</td>
-</tr>
-<table>
-
-##Scoped Searches##
-
-A more advanced feature is scoped searches. Suppose you need to find the ScrollBar attached to some other element. You would use code like this:
-
-
-```C#
-ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
-searchScroll = app.FindName().Find.ByType<>();
-```
-```VB
-Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
-searchScroll ScrollViewer = app.FindName().Find.ByType( ScrollViewer)()
-```
-
-The above code first locates the element named "patientSearchScroller" and then within that control finds the element of type "ScrollViewer". The search for "ScrollViewer" is considered a scoped search (aka chained search) because the search is limited to only those elements found underneath the "patientSearchScroller" element of the Visual Tree. The FrameworkElement base class has a Find property which allows scoped searches for all elements of an application.
-
-##Finding Elements by XamlFindExpression##
-
-Another advanced feature is to find the element using a XamlFindExpression. FindExpressions are the replacement/evolution of FindParams. Telerik Testing Framework uses FindExpressions as the basis for all element searches in the DOM, HWnd, or control trees (including Translator Locators). For example, the above scoped search to retrieve a ScrollViewer can be written using Find.ByExpression as follows:
-
-```C#
-ScrollViewer searchScroll = app.Find.ByExpression(new XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).As<ScrollViewer>();
-```
-```VB
-Dim searchScroll2 As ScrollViewer = app.Find.ByExpression(New XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).[As](Of ScrollViewer)()
-```
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
deleted file mode 100644
index c6f76c53..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation.md
+++ /dev/null
@@ -1,121 +0,0 @@
----
-title: Silverlight UI Automation
-page_title: Silverlight UI Automation
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/introduction.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/introduction
-position: 1
----
-#Getting Started with Silverlight UI Automation#
-
-When thinking about Silverlight applications and automated testing, there are a couple of different approaches that come to mind:
- 
-To get started, let's use a simple application and demo some basic automation scenarios like button click and set text. Then we will expand into more advanced topics and scenarios. Let's take the following simple Silverlight application that contains a button and a text box. When you click the button, it simply displays hello in a text block on the canvas. The application looks like this:
-
-![Silverlight app][1]
-
-To automate the application above to set the text, click the button and then verify the hello text in Telerik Testing Framework, we can simply write the following code using the Silverlight Extension (which resides under ArtOfTest.WebAii.Silverlight).
-
-```C#
-[TestMethod]
-public void SLDemo()
-{  
-	//Enable Silverlight
-	Settings.Current.Web.EnableSilverlight = true;
-	 
-	// Launch a browser instance
-	Manager.LaunchNewBrowser();
-	 
-	// Navigate to the page
-	ActiveBrowser.NavigateTo("http://localhost:5697/SilverlightApplication1Web/SilverlightApplication1TestPage.html");
-	 
-	// Get an instance of our Silverlight app.
-	SilverlightApp app = ActiveBrowser.SilverlightApps()[0];
-	 
-	// Set the text of the text box
-	app.FindName<TextBox>("myName").Text = "Telerik";
-	 
-	// Click the button
-	app.FindName<Button>("myBtn").User.Click();
-	 
-	// Verify the text
-	Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"));
-}
-```
-```VB
-<TestMethod> _
-Public Sub SampleWebAiiTest()
-    'Enable Silverlight
-    Settings.Current.Web.EnableSilverlight = True
- 
-    ' Launch a browser instance
-    Manager.LaunchNewBrowser()
- 
-    ' Navigate to the page
-    ActiveBrowser.NavigateTo("http://localhost:5697/SilverlightApplication1Web/SilverlightApplication1TestPage.html")
- 
-    ' Get an instance of our Silverlight app.
-    Dim app As SilverlightApp = ActiveBrowser.SilverlightApps()(0)
- 
-    ' Set the text of the text box
-    app.FindName(Of TextBox)("myName").Text = "Telerik"
- 
-    ' Click the button
-    app.FindName(Of Button)("myBtn").User.Click()
- 
-    ' Verify the text
-    Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"))
-End Sub
-```
-
-
-Let's take a closer look at the code above line by line:
-
-* Line 8-12
-
-	This is basic code that launches the browser and navigates to a specific page.
-
-* Line 14 (*SilverlightApp app = ActiveBrowser.SilverlightApps()[0];*)
-
-	As soon as you include the Silverlight extension namespace in your test, (**ArtOfTest.WebAii.Silverlight**), the '**SilverlightApps()**' extension method is added to the ActiveBrowser. The extension method offers you a list of all Silverlight applications found on that page. The extension method returns a list that has two accessors. An **index** accessor that takes an int (as shown above) and a string accessor that takes a hostid [The ID of the HTML element that contains the <object> tag for the plug-in]. You can pick and choose what works for you. In this sample, given that we only have one Silverlight plug-in on the page, we simply accessed the first and only one.
-
-* Line 17 (*app.FindName<TextBox>("myName").Text = "Telerik";*)
-
-	As soon as you have an instance of a **SilverlightApp**, you now have full access to the application including the entire **VisualTree**. The app offers a short-cut method '**FindName**', that can be used to search the application using an element name. In the above sample, given that the **TextBox** has a name associated with it, we can use FindName to locate it. The SilverlightApp object offers two versions of 'FindName': The first is a generic method that can return a strongly-typed object of the element (As shown above , i.e. a Button, a TextBox, a Grid, etc). The second is simpler and returns the base **FrameworkElement** object. We will discuss the strongly-typed object model offered in Silverlight Extension later.
- 
-	To go back to the line above, we are simply accessing the **TextBox** that has a name '**myName**' and then setting its Text property to "Telerik". Note that given we are accessing a property on the element, this is analogous to **SetText** on a DOM element in Telerik Testing Framework automation. You are not really typing the text in the textbox but rather setting the Text property inside the application to that text. Our extension enables you to access and set properties directly against any **FrameworkElement**. If we wanted to simulate real typing of the text we would have written code like this:
- 
- 
-	*app.FindName<TextBox>("myName").User.TypeText("Telerik", 50);*
-
-* 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.
-
-* Line 23 (*Assert.IsTrue(app.Find.ByTextContent("p:Hello").TextContent.Equals("Hello Telerik"));*) 
-
-	Now that the button is clicked, we need to verify that the message is correct. The difference here is that we can't really use **FindName** to locate the **TextBlock** because the TextBlock doesn't really have a name. The **SilverlightApp** object offers extensive search support within the **VisualTree** beyond FindName() by utilizing similar approach to the Find object off the ActiveBrowser (that is used for HTML DOM searches) but adapted to specific **XAML** search scenarios.
- 
-	In our code above, we are searching for a TextBlock (All Find.xxText() routines return TextBlocks) that partially contains '**Hello**', hence '**p:Hello**' (Similar to Find.ByContent in HTML search). Once we find the TextBlock, we then verify that the Text of that label is actually 'Hello Telerik' using the **Assert.IsTrue**.
-
-Now that we understand this sample, let's dig into some of the key objects available in the Silverlight Extension.
-
-> There is a new Setting.EnableSilverlight flag that needs to be set to enable WebAii to connect to Silverlight applications. By default this setting is not on. Setting this flag will activate the built-in proxy that we use to detect Silverlight applications.
-
-Limitations:
-
-1. On Vista, if you are automating an external website, then make sure to add the URL to your Trusted Websites list in IE.
-
-2. Our automation supports Silverlight 2.0 (and above). We do not support any previous versions.
-
-3. The automation only supports the **XAP** deployment method.
-EnableHtmlAccess needs to be set to 'True' on your application.
-
-4. There are known issues with Silverlight applications that attempt to perform web service calls within the application.
-
-5. EnableHtmlAccess needs to be set to 'True' on your application.
-
-6. The application needs to be running off http:// not C:\...
-
-7. When using localhost as your server name, it must end with a trailing '.' character e.g. http://localhost./.
-
-[1]: /img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation/fig1.png
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md b/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md
deleted file mode 100644
index 3ae79d91..00000000
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-namespace.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-title: Silverlight UI Namespace
-page_title: Silverlight UI Namespace
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 3
----
-#The ArtOfTest.WebAii.Silverlight.UI Namespace#
-
-The UI namespace includes all the strongly-typed controls like **Button**, **DataGrid**, **TextBox**, etc. and their properties/methods and enum's, mirroring as much as possible the set of controls available in Silverlight as documented <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement(VS.96).aspx" target="_blank">here</a>. The namespace also includes the types used by these properties like **Brush**, **SolidBrush**, etc.
- 
-The getting of simple primitive and complex properties is supported but only the setting of simple primitive properties and enum's and a few complex properties is also supported.
diff --git a/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object.md b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object.md
new file mode 100644
index 00000000..4c2c3e83
--- /dev/null
+++ b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object.md
@@ -0,0 +1,250 @@
+---
+title: FrameworkElement Object
+page_title: FrameworkElement Object
+description: "Learn about the FrameworkElement object in Test Studio's WPF automation. Explore its properties, methods, and usage for navigating and interacting with the visual tree in automated tests."
+position: 3
+---
+# FrameworkElement Object
+
+The **FrameworkElement** object is the base object that all visual elements and controls inherit from in the **ArtOfTest.WebAii.Silverlight.UI** namespace. 
+ 
+The **FrameworkElement** and all objects that inherit from it get the following infrastructure properties:
+
+<table class="docs">
+<tr>
+	<th>Property</th><th>Description</th>
+</tr>
+<tr>
+	<td>AbsoluteSiblingTagIndex</td><td>Get the sibling tag index of this FrameworkElement.</td>
+</tr>
+<tr>
+	<td>AbsoluteTagIndex</td><td>Get the absolute index of this XAML tag in the Visual Tree.</td>
+</tr>
+<tr>
+	<td>ActualHeight</td><td>Gets the rendered height of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>ActualWidth</td><td>Gets the rendered width of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>Application</td><td>Get the Application object that owns this element.</td>
+</tr>
+<tr>
+	<td>AutomationId</td><td>Gets the AutomationId set on this element if any.</td>
+</tr>
+<tr>
+	<td>Children</td><td>Gets the visual children of this element.</td>
+</tr>
+<tr>
+	<td>Clip</td><td>Gets or sets the <a href="http://msdn.microsoft.com/en-us/library/system.windows.media.geometry(VS.96).aspx" target="_blank">Geometry</a> used to define the outline of the contents of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+</tr>
+<tr>
+	<td>Depth</td><td>Get the depth of this element in the Visual Tree.</td>
+</tr>
+<tr>
+	<td>EnableValidateMouseLocation</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
+</tr>
+<tr>
+	<td>Find</td><td>Get the Find object used to search the visual children of this element.</td>
+</tr>
+<tr>
+	<td>Height</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>HorizontalAlignment</td><td>Gets or sets the horizontal alignment characteristics applied to a FrameworkElement when it is composed within a layout parent, such as a panel or items control.</td>
+</tr>
+<tr>
+	<td>Host</td><td>Returns the SilverlightApp object owning this FrameworkElement.</td>
+</tr>
+<tr>
+	<td>IsHitTestVisible</td><td>Gets or sets whether the contained area of this UIElement can return true values for hit testing.</td>
+</tr>
+<tr>
+	<td>IsTestRegion</td><td>Returns whether or not this FrameworkElement is contained inside a TestRegion (not supported in WebAii 2.0 Beta 2).</td>
+</tr>
+<tr>
+	<td>Language</td><td>Gets or sets localization/globalization language information that applies to a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>Margin</td><td>Gets or sets the outer margin of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>MaxHeight</td><td>Gets or sets the maximum height constraint of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>MaxWidth</td><td>Gets or sets the maximum width constraint of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>MinHeight</td><td>Gets or sets the minimum height constraint of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>MinWidth</td><td>Gets or sets the minimum width constraint of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>Name</td><td>Gets (or sets, but see Remarks) the identifying name of the object. The name provides a reference that is initially markup-compiled. After a XAML processor creates the object tree from markup, run-time code can refer to a markup element by this name.</td>
+</tr>
+<tr>
+	<td>Opacity</td><td>Gets or sets the degree of the object's opacity.</td>
+</tr>
+<tr>
+	<td>OpacityMask</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
+</tr>
+<tr>
+	<td>Projection</td><td>Gets or sets the perspective projection (3-D effect) to apply when rendering this <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+</tr>
+<tr>
+	<td>RenderSize</td><td>Gets the final render size of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+</tr>
+<tr>
+	<td>RenderTransform</td><td>Gets or sets transform information that affects the rendering position of a UIElement.</td>
+</tr>
+<tr>
+	<td>RenderTransformOrigin</td><td>Gets or sets the origin point of any possible render transform declared by <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement.rendertransform(VS.96).aspx" target="_blank">RenderTransform</a>, relative to the bounds of the <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>.</td>
+</tr>
+<tr>
+	<td>Resources</td><td>Gets the locally defined resource dictionary. In XAML, you can establish resource items as child object elements of the <code>&lt;object.Resources&gt;</code> property element, through XAML implicit collection syntax.</td>
+</tr>
+<tr>
+	<td>Style</td><td>Gets or sets an instance <a href="http://msdn.microsoft.com/en-us/library/system.windows.style(VS.96).aspx" target="_blank">Style</a> that is applied for this object during rendering.</td>
+</tr>
+<tr>
+	<td>TagNameIndex</td><td>Gets the tag name index of the xaml tag name in the visual tree.</td>
+</tr>
+<tr>
+	<td>TechnologyType</td><td>Get the technology type of this element. Always returns TechnologyType.Silverlight for FrameworkElement objects.</td>
+</tr>
+<tr>
+	<td>TextContent</td><td>Gets the text content of this framework element if any.</td>
+</tr>
+<tr>
+	<td>UseLayoutRounding</td><td>Gets or sets a value that determines whether rendering for the object and its subtree should use rounding behavior that aligns rendering to whole pixels.</td>
+</tr>
+<tr>
+	<td>User</td><td>Gets the UI interaction object that allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
+</tr>
+<tr>
+	<td>VerticalAlignment</td><td>Gets or sets the vertical alignment characteristics applied to a FrameworkElement when it is composed within a parent object such as a panel or items control.</td>
+</tr>
+<tr>
+	<td>Visibility</td><td>Gets or sets the visibility of a <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a>. A <a href="http://msdn.microsoft.com/en-us/library/system.windows.uielement(VS.96).aspx" target="_blank">UIElement</a> that is not visible does not render and does not communicate its desired size to layout.</td>
+</tr>
+<tr>
+	<td>Wait</td><td>Gets a VisualWait object to be used on waiting for Visual elements in the VisualTree.</td>
+</tr>
+<tr>
+	<td>Width</td><td>Gets or sets the width of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>XamlTag</td><td>Get the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
+</tr>
+</table>
+
+## The FrameworkElement Methods
+
+Before describing all of the methods of the FrameworkElement object I'd like to point out the following special features:
+
+1. VisualTree navigation: All FrameworkElements enable you to navigate the visual tree up or down. The object exposes methods and properties like `Parent`, `Children`, `NextSibling`, `PreviousSibling`, `AnySibling<T>`. The navigation also supports control sensitive navigation. For example, if you would like to find the parent 'Grid' that a certain text is contained in you do the following:
+
+	
+````C#
+WpfApplication app = Manager.ActiveApplication;
+Assert.IsNotNull(app);
+
+Grid containerGrid = app.Find.ByText("SomeText").Parent("Grid").As<Grid>();
+````
+
+__OR__
+
+If you are working with a custom control that doesn't have a strongly-typed object under **ArtOfTest.WebAii.Silverlight.UI**, the navigation methods all offer a non-generic version that can be used to search for a certain type. For example, let's say you are trying to find the custom control "Bar" that contains some text, then you can do the following:
+
+````C#
+WpfApplication app = Manager.ActiveApplication;
+Assert.IsNotNull(app);
+
+FrameworkElement barElement = app.Find.ByText("SomeText").Parent("Bar");
+````
+
+`Parent`, `NextSibling`, `PreviousSibling` & `AnySibling` all offer a non-generic versions in addition to the generic one.
+
+2. **User Interaction object:**
+
+The FrameworkElement object exposes a user interaction object. The object is exposed as a property named '**User**'. User then exposes all the real automation methods like moving the mouse to click an element, type a text, mouse enter, mouse leave…etc.
+
+**Note:** One of the reasons why we moved these methods into their own object under 'User.xxx' is to help users differentiate between automation that is done by setting/getting properties vs. real automation that used the mouse or keyboard to invoke actions.
+
+3. **Element coordinates:** 
+
+
+All FrameworkElements offer the ability to get both the relative coordinates of the element within the Silverlight application and the actual coordinates in screen coordinates. The two methods are `GetRectangle()`and `GetScreenRectangle()`.
+
+**Note:** Given that WPF/Silverlight applications allow for rich transforms for visual elements (i.e. rotate, zoom….etc) and some elements like ellipses don't really conform to a rectangle per-say, our coordinate calculations will always return the largest rectangle that contains the actual element with its center right at the center of the element. For example, a GetRectangle on an ellipse will return this:
+
+![SL app][1]
+
+*The highlighting above is using the FrameworkElement.Highlight() method.*
+
+4. **XML Representation**:
+
+
+Every **FrameworkElement** has a `ToXml()` method on it that returns the VisualTree of that element as an XML formatted string. This is very useful when trying to understand the visual tree at a certain state. [Hint: You can get the entire visual tree of an app by calling `app.VisualTree.Root.ToXml()`]
+
+These are all of the FrameworkElement methods available for use by your automation code:
+
+<table class="docs">
+<tr>
+	<th>Method</th><th>Description</th>
+</tr>
+<tr>
+	<td>AnySibling(T)</td><td>Return any sibling of this control of type T. The framework first searches for a previous sibling having the specified type. If it finds one that sibling is returned. If it doesn't find one then it searches for the next sibling. If it find one that sibling is returned, otherwise null (Nothing in VB.NET) is returned.</td>
+</tr>
+<tr>
+	<td>As(T)</td><td>Return this framework element as a strongly-typed control of type T.</td>
+</tr>
+<tr>
+	<td>CastAs(T)</td><td>Returns this framework element as a strongly-typed control of type T without enforcing tag name to match the type it is being cast to. This functions gives you free casting abilities between types.</td>
+</tr>
+<tr>
+	<td>Equals</td><td>Determines whether this FrameworkElement is equal to another, by comparing their AutomationReferences.</td>
+</tr>
+<tr>
+	<td>GetChildren</td><td>Get the children of this framework element.</td>
+</tr>
+<tr>
+	<td>GetNextSibling</td><td>Get the next sibling of this FrameworkElement.</td>
+</tr>
+<tr>
+	<td>GetParent</td><td>Get the Parent of this element.</td>
+</tr>
+<tr>
+	<td>GetPrevSibling</td><td>Get the previous sibling.</td>
+</tr>
+<tr>
+	<td>GetRectangle</td><td>Get the bounding rectangle of this FrameworkElement within the owning Silverlight application.</td>
+</tr>
+<tr>
+	<td>GetScreenRectangle</td><td>Return the actual coordinates of this element in absolute screen coordinates taking into account the location of the overall plug-in on the page.</td>
+</tr>
+<tr>
+	<td>Highlight</td><td>Highlight this element in the Silverlight application.</td>
+</tr>
+<tr>
+	<td>NextSibling</td><td>Get the next sibling control of a specific type.</td>
+</tr>
+<tr>
+	<td>Parent</td><td>Get the parent FrameworkElement of this element.</td>
+</tr>
+<tr>
+	<td>PreviousSibling</td><td>Get the previous sibling control of a specific type.</td>
+</tr>
+<tr>
+	<td>Refresh</td><td>Refresh this FrameworkElement within the VisualTree.</td>
+</tr>
+<tr>
+	<td>ScrollToVisible</td><td>Scrolls the web page so that this element is visible in the browser window.</td>
+</tr>
+<tr>
+	<td>ToXml</td><td>Gets an XML formatted string that represents this element and all its children This XML represents the VisualTree.</td>
+</tr>
+</table>
+
+[1]: /img/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation/fig1.png
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/invoking-actions.md b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/invoking-actions.md
new file mode 100644
index 00000000..6ed2bc0d
--- /dev/null
+++ b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/invoking-actions.md
@@ -0,0 +1,226 @@
+---
+title: Invoking Actions
+page_title: Invoking Actions
+description: "Learn how to interact with WPF application elements using Test Studio's automation framework. This article covers clicking, sending text, mouse actions, accessing properties, and invoking methods on UI elements for robust automated testing."
+position: 3
+---
+# Invoking Actions on Elements
+
+Once you have found an element you can then interact with it. Many different types of interactions are supported like clicking, mouse hover over, mouse wheel-related actions, keyboard clicks etc.
+
+1. [Clicking On an Element](#clicking-on-an-element) - invoke a click on a FrameworkElement
+
+2. [Sending Text to a Control](#sending-text-to-a-control) - type text content into a FrameworkElement
+
+3. [Mouse Actions](#mouse-actions) - invoking different mouse actions on FrameworkElement
+
+4. [Framework Element Properties and Actions](#framework-element-properties-and-actions)
+
+	* [UI Element Actions](#ui-element-action) - understanding wrappers.
+	* [Telerik Testing Framework Specific Properties](#telerik-testing-framework-specific-properties) - commonly used Properties of Telerik's FrameworkElement.
+	* [Telerik Testing Framework Specific Methods](#telerik-testing-framework-specific-methods) - commonly used Methods of Telerik's FrameworkElement.
+	* [Getting and Setting Properties on Elements](#getting-and-setting-properties-on-elements) - working with non-built in Properties.
+
+5. [Invoking Element Methods](#invoking-element-methods) - invoke any method attached to an element.
+
+## Clicking On an Element
+
+To invoke a UI action, use the User object that is attached to every UI element. For example, to click on an element such as a button, enter code like this:
+
+````C#
+//In this example app can be the MainWindow element of a WPF application 
+// Click the ShowGuide button.
+app.Find.ByName("guideButton").User.Click();
+ 
+// Right click the ShowGuide button 5 pixels away from the center of the control
+app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick,
+     new System.Drawing.Point(5, 5), OffsetReference.AbsoluteCenter);
+````
+````VB
+'In this example app can be the MainWindow of a WPF application 
+' Click the ShowGuide button.
+app.Find.ByName("guideButton").User.Click()
+ 
+' Right click the ShowGuide button 5 pixels away from the center of the control
+app.Find.ByName("guideButton").User.Click(MouseClickType.RightClick, _
+                                       New System.Drawing.Point(5, 5), _
+                                        OffsetReference.AbsoluteCenter)
+````
+
+## Sending Text to a Control
+
+To send text to the control use one of the following lines of code:
+
+````C#
+searchText.User.TypeText("Abe Lincoln", 100);
+ 
+searchText.User.KeyPress(System.Windows.Forms.Keys.L, 100);
+ 
+searchText.User.KeyDown(System.Windows.Forms.Keys.L);
+searchText.User.KeyUp(System.Windows.Forms.Keys.L);
+````
+````VB
+searchText.User.TypeText("Abe Lincoln", 100)
+ 
+searchText.User.KeyPress(Windows.Forms.Keys.L, 100)
+ 
+searchText.User.KeyDown(Windows.Forms.Keys.L)
+searchText.User.KeyUp(Windows.Forms.Keys.L)
+````
+
+## Mouse Actions
+
+To perform one of the various possible mouse actions use one of the following lines of code:
+
+````C#
+admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"));
+admin1.User.HoverOver();
+admin1.User.MouseEnter(OffsetReference.LeftCenter);
+admin1.User.MouseLeave(OffsetReference.RightCenter);
+admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, false);
+````
+````VB
+admin2.Find.ByType("Thumb").User.DragTo(admin3.Find.ByType("Thumb"))
+admin1.User.HoverOver()
+admin1.User.MouseEnter(OffsetReference.LeftCenter)
+admin1.User.MouseLeave(OffsetReference.RightCenter)
+admin1.User.TurnMouseWheel(5, MouseWheelTurnDirection.Backward, False)
+````
+
+## Framework Element Properties and Actions
+
+All of the Telerik Testing Framework UI controls derive from the FrameworkElement object. Our FrameworkElement object mirrors as closely as possible XAML's FrameworkElement as defined in MSDN <a href="http://msdn.microsoft.com/en-us/library/system.windows.frameworkelement%28VS.96%29.aspx" target="_blank">here</a>. These are just few examples of the many available properties of our FrameworkElement object:
+
+<table class="docs">
+<tr>
+	<th>Property</th><th>Description</th>
+</tr>
+<tr>
+	<td>AutomationId</td><td>Retrieves the Automation ID assigned to this element.</td>
+</tr>
+<tr>
+	<td>Children</td>Retrieves a list of elements that are children of this element in the visual tree.</td>
+</tr>
+<tr>
+	<td>Clip</td><td>Gets or sets the Geometry used to define the outline of the contents of a UI Element.</td>
+</tr>
+<tr>
+	<td>Height</td><td>Gets or sets the suggested height of a FrameworkElement.</td>
+</tr>
+<tr>
+	<td>Opacity</td><td>Gets or sets the degree of the object's opacity.</td>
+</tr>
+<tr>
+	<td>OpacityMask</td><td>Gets or sets the brush used to alter the opacity of regions of this object.</td>
+</tr>
+<tr>
+	<td>Width</td><td>Gets or sets the suggested width of a FrameworkElement.</td>
+</tr>
+</table>
+
+## UI Element Action
+
+Each UI element wrapper class contained in Telerik Testing Framework has a set of properties used to access the properties appropriate for that UI element. For example: The Calendar control has a SelectedDate property that you can use to read and/or set the currently selected date of the control. It also has a SelectionMode property you can use to read and/or change the selection mode from a single date to a multi-range date selection. The CheckBox control has an IsChecked property you can use to read/set the checked state of the control and so on.
+
+## Telerik Testing Framework Specific Properties
+
+We have implemented a few special properties in our FrameworkElement object to aid in automation. These include:
+
+<table class="docs">
+<tr>
+	<th>Property</th><th>Description</th>
+</tr>
+<tr>
+	<td>AbsoluteSiblingTagIndex</td><td>Returns the sibling tag index of this FrameworkElement relative to its other siblings within the Visual Tree.</td>
+</tr>
+<tr>
+	<td>AbsoluteTagIndex</td><td>Returns the absolute index of this XAML tag within the entire Visual Tree.</td>
+</tr>
+<tr>
+	<td>Application</td><td>Gets the Application object that owns this element.</td>
+</tr>
+<tr>
+	<td>EnableValidateMouseLocation</td><td>Enables or disables the validation of mouse click locations before performing mouse actions.</td>
+</tr>
+<tr>
+	<td>Find</td><td>Gets the Find object that can be used to search the visual children of this element.</td>
+</tr>
+<tr>
+	<td>TagNameIndex</td><td>Gets the tag name index of the XAML tag name in the visual tree.</td>
+</tr>
+<tr>
+	<td>User</td><td>Gets the UI interaction object which allows you to interact with this framework element directly using real mouse and keyboard interactions.</td>
+</tr>
+<tr>
+	<td>Wait</td><td>Gets a VisualWait object you can use to wait for Visual elements in the Visual Tree.</td>
+</tr>
+<tr>
+	<td>XamlTag</td><td>Gets the XAML tag name of this FrameworkElement. This is used for hierarchy matching and traversal.</td>
+</tr>
+</table>
+
+## Telerik Testing Framework Specific Methods
+
+The FrameworkElement class implements a number of methods just for purpose of test automation. Some of the most commonly used include:
+
+<table class="docs">
+<tr>
+	<th>Property</th><th>Description</th>
+</tr>
+<tr>
+	<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>GetChildren()</code></td>Returns the child elements of the FrameworkElement.</td>
+</tr>
+<tr>
+	<td><code>GetNextSibling()</code></td><td>Returns the next sibling of  the FrameworkElement.</td>
+</tr>
+<tr>
+	<td><code>Parent()</code></td><td>Returns the parent element of the current Framework Element</td>
+</tr>
+<tr>
+	<td><code>ScrollToVisible()</code></td><td>Scrolls the browser so that the Framework Element is visible.</td>
+</tr>
+</table>
+
+## Getting and Setting Properties on Elements
+
+If the property of an element you want to get or set isn't available as a property in the UI element wrapper object, you can use the GetProperty and SetProperty from the FrameworkElement object to get/set it. This is especially useful if you start designing your own custom UI controls or use a third party custom control. Let's suppose I have a UI element that represents an airline ticket. One of the many obvious properties such a control would need to have is flight number. To fetch this property from the control I can use code like this:
+
+````C#
+// Fetch the flight number from the ticket
+FrameworkElement ticket = app.FindName("airlineTicket");
+AutomationProperty flightNoProperty = new AutomationProperty("flightNo", typeof(string));
+string flightNo = (string)ticket.GetProperty(flightNoProperty);
+ 
+// Update the flight number on the ticket
+ticket.SetProperty(flightNoProperty, "HX-1572");
+````
+````VB
+' Fetch the flight number from the ticket
+Dim ticket As FrameworkElement = app.FindName("airlineTicket")
+Dim flightNoProperty As New AutomationProperty("flightNo", GetType(String))
+Dim flightNo As String = DirectCast(ticket.GetProperty(flightNoProperty), String)
+ 
+' Update the flight number on the ticket
+ticket.SetProperty(flightNoProperty, "HX-1572")
+````
+
+## Invoking Element Methods
+
+Another advanced feature of the framework is the ability to invoke any method attached to an element. Here's how to invoke the ScrollToVerticalOffset method of a ScrollViewer element.
+
+````C#
+ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
+searchScroll = app.FindName().Find.ByType<>();
+ 
+AutomationMethod scrollVert = new AutomationMethod("ScrollToVerticalOffset", null);
+searchScroll.InvokeMethod(scrollVert, 2000);
+````
+````VB
+Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
+ 
+Dim scrollVert As New AutomationMethod("ScrollToVerticalOffset", Nothing)
+searchScroll.InvokeMethod(scrollVert, 2000)
+````
\ No newline at end of file
diff --git a/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements.md b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements.md
new file mode 100644
index 00000000..c528c068
--- /dev/null
+++ b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements.md
@@ -0,0 +1,143 @@
+---
+title: Locating Elements
+page_title: Locating Elements
+description: "Discover effective strategies for locating and identifying elements in WPF applications using Test Studio. Learn about search methods, scoped searches, XamlFindExpressions, and best practices for reliable automated UI testing."
+position: 3
+---
+# Locating Elements in WPF applications 
+
+Before you can automate interaction with elements contained in a Silverlight/WPF application, you need to first locate the elements contained within the application. For complex applications, locating elements is probably going to be one of the more time consuming tasks. Testers will need to spend time understanding how to reliably find an element. Silverlight/WPF applications that we studied that rely heavily on control templates and data binding produce quite complex visual trees. Their elements are not easily searchable by `Find.ByName()` given the different <a href=http://msdn.microsoft.com/en-us/library/cc189026%28VS.95%29.aspx" target="_blank">Silverlight</a> and <a href="http://msdn.microsoft.com/en-us/library/ms746659.aspx" target="_blank">WPF</a> name scopes created, and the duplication of names within those templates.
+
+1. [The Find Strategy](#the-find-strategy) - change the 'Strategy' property that controls how the method behaves when searching for an element.
+
+2. [Finding All Elements](#finding-all-elements) - return a list of the elements contained in the application.
+
+3. [Scoped Searches](#scoped-searches) - search for a specific element based on its parent.
+
+4. [Finding Elements by XamlFindExpression](#finding-elements-by-xamlfindexpression) - search for an element using a FindExpression.
+
+The simplest method of searching is to use the `Find.ByName(String name)` method or the `Find.ByName<TControl>(String name)` method. Both methods take a string parameter that specifies the name of the element to locate in the application. The first method returns a FrameworkElement object while the second method returns an object of type T having the specified name. If an element having the specified name does not exist or is not currently visible, or if the found element cannot be cast into type T, the functions will return null ('Nothing' in VB.NET). For example:
+
+````C#
+FrameworkElement zoomBox = app.FindName("zoomBox");
+TextBox searchText = app.FindName<TextBox>("searchText");
+````
+````VB
+Dim zoomBox As FrameworkElement = app.FindName("zoomBox")
+Dim searchText As TextBox = app.FindName(Of TextBox)("searchText")
+````
+
+You might be asking "How do I know what name to use to find the element I want?" There really are only a few ways to find out:
+
+1. Refer to the design document of the application. Hopefully the name has been specified.
+
+2. Ask the developer what the name of a particular element is.
+
+3. Examine the source code to find the name.
+
+4. If the above methods are not available to you, you will have to resort to some sort of WPF spy utility such as this one to discover the name.
+ 
+The **Find** object offers a rich set of search methods that enable you to not only find elements using their names, but also by their text or type. Combined with type filtering, LINQ, FrameworkElement navigation, and the Find.AllByXXX routines, you get a rich set of routines that enables you to find any framework element in the tree.
+ 
+All of the common methods for finding an element to operate on are:
+
+<table class="docs">
+<tr>
+	<th>Method</th><th>Description</th>
+</tr>
+<tr>
+	<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>Find.ByText</code></td><td>Returns the first TextBlock that matches the text provided.</td>
+</tr>
+<tr>
+	<td><code>Find.ByAutomationId</code></td><td>Returns an element having the automation ID you specify.</td>
+</tr>
+<tr>
+	<td><code>Find.ByType</code></td><td>Returns the first element found of the specified type (e.g. Canvas, DataGrid, Calendar).</td>
+</tr>
+</table>
+
+## The Find Strategy
+
+The Find object has a 'Strategy' property that controls how the method behaves when searching for an element. To change the strategy simply change the Strategy property on the Find object. The following strategies can be set:
+
+<table class="docs">
+<tr>
+	<th>Strategy</th><th>Description</th>
+</tr>
+<tr>
+	<td>AlwaysWaitForElementsVisible</td><td>In this mode the Find object always waits for the element to exist and for its Visibility property to equal "Visible". The default amount of time it will wait is 5 seconds. This timeout can be changed by modifying the Find.Timeout property before using the Find object. This strategy is the default setting.</td>
+</tr>
+<tr>
+	<td>WhenNotVisibleReturnElementProxy</td><td>In this mode an 'Element Proxy' is returned if the element cannot be found right away. An 'Element Proxy' is a lightweight FrameworkElement object that only contains information on how to locate the desired element in the Visual Tree. This is useful when you want to use the SilverlightApp.Wait.ForExists method.</td>
+</tr>
+<tr>
+	<td>WhenNotVisibleReturnNull</td><td>In this mode null (Nothing in VB.NET) is returned if the element cannot be found right away.</td>
+</tr>
+<tr>
+	<td>WhenNotVisibleThrowException</td><td>In this mode a generic exception is thrown if the element cannot be found right away.</td>
+</tr>
+</table>
+
+## Finding All Elements
+
+Sometimes you may need to fetch a list of the elements contained in the application. Suppose we want a list of all the DataGrids contained in the application. Either of the following lines of code will return this list:
+
+
+````C#
+IList<FrameworkElement> dataGrids1 = app.Find.AllByType("DataGrid");
+IList<DataGrid> dataGrids2 = app.Find.AllByType<DataGrid>();
+````
+````VB
+Dim dataGrids1 As IList(Of FrameworkElement) = app.Find.AllByType("DataGrid")
+Dim dataGrids2 As IList(Of DataGrid) = app.Find.AllByType(Of DataGrid)()
+````
+
+All of the `Find.AllByxxx` functions are:
+
+<table class="docs">
+<tr>
+	<th>Method</th><th>Description</th>
+</tr>
+<tr>
+	<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>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>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>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>
+
+## Scoped Searches
+
+A more advanced feature is scoped searches. Suppose you need to find the ScrollBar attached to some other element. You would use code like this:
+
+
+````C#
+ScrollViewer searchScroll = app.FindName("patientSearchScroller").Find.ByType<ScrollViewer>();
+searchScroll = app.FindName().Find.ByType<>();
+````
+````VB
+Dim searchScroll As ScrollViewer = app.FindName("patientSearchScroller").Find.ByType(Of ScrollViewer)()
+searchScroll ScrollViewer = app.FindName().Find.ByType( ScrollViewer)()
+````
+
+The above code first locates the element named "patientSearchScroller" and then within that control finds the element of type "ScrollViewer". The search for "ScrollViewer" is considered a scoped search (aka chained search) because the search is limited to only those elements found underneath the "patientSearchScroller" element of the Visual Tree. The FrameworkElement base class has a Find property which allows scoped searches for all elements of an application.
+
+## Finding Elements by XamlFindExpression
+
+Another advanced feature is to find the element using a XamlFindExpression. FindExpressions are the replacement/evolution of FindParams. Telerik Testing Framework uses FindExpressions as the basis for all element searches in the DOM, HWnd, or control trees (including Translator Locators). For example, the above scoped search to retrieve a ScrollViewer can be written using `Find.ByExpression` as follows:
+
+````C#
+ScrollViewer searchScroll = app.Find.ByExpression(new XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).As<ScrollViewer>();
+````
+````VB
+Dim searchScroll2 As ScrollViewer = app.Find.ByExpression(New XamlFindExpression("Name=patientSearchScroller", "|", "XamlTag=ScrollViewer")).[As](Of ScrollViewer)()
+````
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/synchronization.md b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/synchronization.md
similarity index 59%
rename from docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/synchronization.md
rename to docs/testing-framework/write-tests-in-code/wpf-automation-wtc/synchronization.md
index 0314dc45..ecf1f7d2 100644
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/synchronization.md
+++ b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/synchronization.md
@@ -1,91 +1,99 @@
 ---
 title: Synchronization
 page_title: Synchronization
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, #framework-element-properties-and-actions, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
 position: 3
 ---
-#Synchronization#
+# Synchronization
 
-In the world of testing mostly static HTML pages synchronization was easy. Telerik Testing Framework was even able to automatically take care of synchronization for you (most of the time). All you had to do was click on a button and wait for the browser to be ready, which the framework does behind the scenes for most HTML UI actions.
- 
-In the world of Silverlight application testing, unlike testing static HTML web pages, you have to intelligently implement synchronization with the Silverlight application under test. This is because in the Silverlight world you're dealing with a real application that is running locally in the browser. The "browser is ready" indicator no longer applies since it only told you when the browser was finished loading the web page from the server.
- 
-The framework has many features implemented to aid you in synchronizing with your Silverlight application as it's being tested. There are six basic types of waits implemented in the framework that you can use for synchronization:
+The Test Studio Testing framework has many features implemented to aid you in synchronizing with your  application as it's being tested. There are six basic types of waits implemented in the framework that you can use for synchronization:
 
 <table class="docs">
 <tr>
 	<th>Wait Type</th><th>Description</th>
 </tr>
 <tr>
-	<td>**ForExists**</td><td>This method waits for the element to exist in the Visual Tree. It accepts an optional timeout parameter.</td>
+	<td>	
+
+**ForExists**</td><td>This method waits for the element to exist in the Visual Tree. It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForExistsNot**</td><td>This method waits for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter</td>
+	<td>
+
+**ForExistsNot**</td><td>This method waits for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter</td>
 </tr>
 <tr>
-	<td>**ForVisible**</td><td>This method waits for the element to both exist in the Visual Tree and its Visibility attribute to equal "Visible". It accepts an optional timeout parameter.</td>
+	<td>
+	
+**ForVisible**</td><td>This method waits for the element to both exist in the Visual Tree and its Visibility attribute to equal "Visible". It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForVisibleNot**</td><td>This method waits for the Visibility property of the element to not equal 'Visible' or for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter.</td>
+	<td>
+	
+**ForVisibleNot**</td><td>This method waits for the Visibility property of the element to not equal 'Visible' or for the element to no longer exist in the Visual Tree. It accepts an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**ForNoMotion**</td><td>This method waits for the element to stop moving on the drawing surface. It takes a check interval and an optional timeout parameter.</td>
+	<td>
+	
+**ForNoMotion**</td><td>This method waits for the element to stop moving on the drawing surface. It takes a check interval and an optional timeout parameter.</td>
 </tr>
 <tr>
-	<td>**For(Predicate)**</td><td>This method takes a custom predicate and waits for that predicate to return true. It accepts an optional error message and an optional timeout parameter.</td>
+	<td>
+	
+**For(Predicate)**</td><td>This method takes a custom predicate and waits for that predicate to return true. It accepts an optional error message and an optional timeout parameter.</td>
 </tr>
-<table>
+</table>
 
-##Waiting for an Element to Exist##
+## Waiting for an Element to Exist
 
 Before you can use the VisualWait.ForExists method to wait for an element to exist you need to create what is called an "Element Proxy". An element proxy is a lightweight FrameworkElement that doesn't actually represent a real element but contains information on how to find the desired element in the Visual Tree. To create an element proxy implement code like this:
 
-```C#
+````C#
 app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy;
 FrameworkElement myElementProxy = app.Find.ByName("MyElement");
-```
-```VB
+````
+````VB
 app.Find.Strategy = FindStrategy.WhenNotVisibleReturnElementProxy
 Dim myElementProxy As FrameworkElement = app.Find.ByName("MyElement")
-```
+````
 
 Now that you have an element proxy you use it to wait for the element to exist using this line of code:
 
-```C#
+````C#
 // Wait 15 seconds for the element to exist
 proxy.Wait.ForExists(15000);
-```
-```VB
+````
+````VB
 ' Wait 15 seconds for the element to exist
 proxy.Wait.ForExists(15000)
-```
+````
 
-##Using ForExistsNot, ForVisible, ForVisibleNot,  ForNoMotion##
+## Using ForExistsNot, ForVisible, ForVisibleNot,  ForNoMotion
 
 Using any of these functions is pretty straightforward. Just call the method with appropriate parameters, for example:
 
-```C#
+````C#
 FrameworkElement ticket = app.FindName("airlineTicket");
 ticket.Wait.ForExistsNot();         // Wait for the element to no longer exist
 ticket.Wait.ForVisible(3000);       // Wait up to 3 seconds for the element to become visible
 ticket.Wait.ForVisibleNot(2500);    // Wait up to 2.5 seconds for the element to no longer be visible
 ticket.Wait.ForNoMotion(250, 4500); // Wait up to 4.5 seconds for the element to stop moving. Check every 1/4 second.
-```
-```VB
+````
+````VB
 Dim ticket As FrameworkElement = app.FindName("airlineTicket")
 ticket.Wait.ForExistsNot()          ' Wait for the element to no longer exist
 ticket.Wait.ForVisible(3000)        ' Wait up to 3 seconds for the element to become visible
 ticket.Wait.ForVisibleNot(2500)     ' Wait up to 2.5 seconds for the element to no longer be visible
 ticket.Wait.ForNoMotion(250, 4500)  ' Wait up to 4.5 seconds for the element to stop moving. Check every 1/4 second.
-```
+````
 
-##Creating Your Own Wait Condition##
+## Creating Your Own Wait Condition
 
 If none of the built-in framework wait for methods meet your needs, the framework has the ability to use your own coded conditional predicate instead. This feature relieves you of the burden of having to fully implement your own custom wait loop.
  
 You can implement your conditional predicate in a function or a lambda expression. Here is a sample of how to implement and use your own conditional predicate in a function:
 
-```C#
+````C#
 FrameworkElement guideButton = app.FindName("guideButton");
 guideButton.Wait.For(myComparator);
  
@@ -93,25 +101,25 @@ public bool myComparator(FrameworkElement elem)
 {
     return elem.Visibility == ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible;
 }
-```
-```VB
+````
+````VB
 Dim guideButton As FrameworkElement = app.FindName("guideButton")
     guideButton.Wait.[For](AddressOf myComparator)
  
 Public Function myComparator(ByVal elem As FrameworkElement) As Boolean
     Return elem.Visibility = ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible
 End Function
-```
+````
 
 
 To do the same thing in a lambda expression would look like this:
 
 
-```C#
+````C#
 FrameworkElement guideButton = app.FindName("guideButton");
 guideButton.Wait.For(new System.Predicate<FrameworkElement>((fe) => fe.Visibility == ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible));
-```
-```VB
+````
+````VB
 Dim guideButton As FrameworkElement = app.FindName("guideButton")
 guideButton.Wait.[For](New System.Predicate(Of FrameworkElement)(Function(fe) fe.Visibility = ArtOfTest.WebAii.Silverlight.UI.Visibility.Visible))
-```
+````
diff --git a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation.md b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation.md
similarity index 77%
rename from docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation.md
rename to docs/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation.md
index 64b03c59..86cd167b 100644
--- a/docs/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation.md
+++ b/docs/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation.md
@@ -1,11 +1,10 @@
 ---
 title: WPF UI Automation
 page_title: WPF UI Automation
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation.aspx, /user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation
+description: "Learn how to automate WPF application UI testing with Test Studio. This article covers launching applications, interacting with UI elements, verifying results, and best practices for building robust automated tests using the WPF Extension."
 position: 2
 ---
-#Getting started with WPF UI Automation#
+# Getting started with WPF UI Automation
 
 To get started, let's use a simple application and demo some basic automation scenarios like button click and set text. Then we will expand into more advanced topics and scenarios. Let's take the following simple application that contains a button and a text box. When you click the button, it simply changes "Push the button" to "Hello world!" in the text box. The application looks like this:
 
@@ -13,7 +12,7 @@ To get started, let's use a simple application and demo some basic automation sc
 
 To automate the application above to set the text, click the button and then verify the hello text in **Telerik Testing Framework**, we can simply write the following code using the **WPF Extension** (which resides under **ArtOfTest.WebAii.Wpf**). The template for this method is based on a VsUnit test. However, the code itself can be reused in other type of Unit tests - it's just the template that will be different.
 
-```C#
+````C#
 [TestMethod]
 public void wpfDemo()
    {
@@ -36,8 +35,8 @@ public void wpfDemo()
     Assert.IsTrue(tb.Text.Equals("Hello World!"));
    
     }
-```
-```VB
+````
+````VB
 <TestMethod> _
   Public Sub wpfDemo()
    ' Launch the application instance from its location in file system
@@ -59,20 +58,20 @@ public void wpfDemo()
       Assert.IsTrue(tb.Text.Equals("Hello World!"))
    
   End Sub
-```
+````
 
 
 Let's take a closer look at the code above line by line:
 
-* Line 5 (*WpfApplication wpfApp = Manager.LaunchNewApplication(@"C:\Projects\WpfApplication2\bin\Debug\WpfApplication2.exe");*)
+* Line 5 (`WpfApplication wpfApp = Manager.LaunchNewApplication(@"C:\Projects\WpfApplication2\bin\Debug\WpfApplication2.exe");`)
 
 	This is basic code that launches the application from a location on the local machine and initializes it into a variable for us. As soon as you have an instance of a Wpf App,you now have full access to the application including the entire Logical Tree. 
 
-* Line 8 ( *Assert.IsTrue(wpfApp.MainWindow.Window.Caption.Equals("MainWindow"));*)
+* Line 8 ( `Assert.IsTrue(wpfApp.MainWindow.Window.Caption.Equals("MainWindow"));`)
 
 	We use the standard Assert class to check the name of the **MainWindow**. The MainWindow is a member of the generic WpfApplication class since every application has one and it holds its entire content.
 
-* Line 11 (*Button b = wpfApp.MainWindow.Find.ByName\<Button>("button1");*)
+* Line 11 (`Button b = wpfApp.MainWindow.Find.ByName<Button>("button1");`)
 
 	The **MainWindow** offers a short-cut member '**Find**' which contains search-related methods. In the above sample, given that the **Button** has a name associated with it, we can use **Find.ByName** to locate it. The MainWindow class offers two versions of **Find.ByName**:
 
@@ -82,18 +81,18 @@ Let's take a closer look at the code above line by line:
  
 	We'll be using the specific version.
 
-* Line 14 (*b.User.Click();*)
+* Line 14 (`b.User.Click();`)
 
 	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 WPF 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.
 
-* Line 17 (*TextBox tb = wpfApp.MainWindow.Find.ByName\<TextBox>("textBlock1");*)
+* Line 17 (`TextBox tb = wpfApp.MainWindow.Find.ByName<TextBox>("textBlock1");`)
 
 	Similarly to line 11 we initialize the Texbox from the app into a variable after locating it by name.
 
-* Line 20 (*Assert.IsTrue(tb.Text.Equals("Hello World!"));*)
+* Line 20 (`Assert.IsTrue(tb.Text.Equals("Hello World!"));`)
 
 	Now that the button is clicked, we need to verify that the message is correct.
  
 	Now that we understand this sample, let's dig into some of the key objects available in the WPF Extension.
 
-[1]: /img/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation/fig1.png
+[1]: /img/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation/fig1.png
diff --git a/docs/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value.md b/docs/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value.md
deleted file mode 100644
index 1bce1345..00000000
--- a/docs/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Change Text Input Value
-page_title: Change Text Input Value
-description: "Test Studio Testing Framework "
-position: 1
-publish: false
-
----
-# Change Text Input Value
-
-Given the following element:
-
-	<input type="text">
-
-If its value is changed, Firefox, Chrome, and Safari do not update the DOM and Test Studio's parsed elements do not recognize the changed value. If the input value is retrieved through JavaScript, then all browsers return the correct value.
-The correct result is returned if the following code is called for a text input element that has its value modified. This is because the value is retrieved by invoking JavaScript on the browser.
-
-	browser.Find.ByName<HtmlInputText>("oname").Value;
-
-If the code below is used instead, then only the initial value is retrieved. This is because Test Studio uses the parsed DOM elements and the DOM is incorrect.
-
-	string value = browser.Find.ByName("oname").GetAttributeValueOrEmpty("value");
-
-This problem only occurs with text input; it does not appear with button input, for example.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome.md b/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome.md
deleted file mode 100644
index 245a1759..00000000
--- a/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome.md
+++ /dev/null
@@ -1,45 +0,0 @@
----
-title: Progress Test Studio Extensions Disabled in Chrome
-page_title: Progress Test Studio Extensions Disabled in Chrome
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Chrome Extensions Disabled
-
-From Chrome version 35 and above due to security reasons, extensions can be installed only if they are hosted on the <a href="https://chrome.google.com/webstore/category/extensions" target="_blank">Chrome Web Store</a>. With this change, extensions that were previously  installed (ex. Test Studio Extensions) may be automatically disabled, and cannot be re-enabled or re-installed until they are hosted on the Chrome Web Store.
-
-For your convenience we are providing you the download links for the latest Chrome extensions below:
-
-**Test Studio 2017 R3 (v. 2017.3.1010) And Later**
-
-There is a single extension combining recording and execution: <a href="https://chrome.google.com/webstore/detail/progress-test-studio-exte/gegcllkonmciadpdldechnepmjildoan" target="_blank">**Progress Telerik Test Studio Extension**</a>.
-
-**Test Studio 2017 R2 SP1 (v. 2017.2.824) And Earlier**
-
-The extensions for Test Studio versions as of 2017 R2 SP1 (v. 2017.2.824) and earlier are divided into two separate extensions: <a href="https://chrome.google.com/webstore/detail/telerik-test-studio-chrom/fiahpmmidlchdfcdpckaclkancbnbgnl" target="_blank">**Progress Test Studio Chrome Recorder**</a> and <a href="https://chrome.google.com/webstore/detail/telerik-test-studio-chrom/pncoonbpgmlbbjnnmaindchmjckkjcdb" target="_blank">**Progress Test Studio Chrome Execution**</a>.
-
-<a href="https://chrome.google.com/webstore/detail/telerik-test-studio-chrom/fhemhbheldeocfphcgnliopkkaapnclg" target="_blank">**Telerik Test Studio Chrome Explore**</a> - the <a href="/features/testing-types/exploratory-testing/overview" target="_blank">exploratory extension</a> is not mandatory.
-
-## Extensions In Chrome Web Store
-
-The extensions comaptible both with Test Studio 2017 R2 SP 1 (v. 2017.2.824) and earlier and 2017 R3 (v. 2017.3.1010) and later are available for manual installation in the <a href="https://chrome.google.com/webstore/category/extensions" target="_blank">Chrome Web Store</a>. Make sure the **Extensions** node is selected. Type **Progress Test Studio** in the search bar and hit Enter.
-
-![Extensions][1]
-
-The displayed extension called **Progress Test Studio Extension** (highlighted) is the latest extension comapatible with **Test Studio 2017 R3 (v. 2017.3.1010) and later, and Chrome version 61 and later**. You can proceed installing it by clicking the **Add To Chrome** button.
-
-![Add Extensions New][2]
-
-The two Progress Test Studio Extensions separated for Recording and Execution (highlighted below) are compatible with **Test Studio version 2017 R2 SP1 (v. 2017.2.824) and previos, and Chrome with version prior 60**. You can proceed installing these by clicking the **Add To Chrome** button.
-
-![Add Extensions ][3]
-
-**Note:** If you are using **Test Studio 2014 R1 (v. 2014.1.410) or earlier** the respective extensions could be also found in the Store. 
-
-![Telerik Extensions][4]
-
-[1]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig1.png
-[2]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig2.png
-[3]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig3.png
-[4]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome/fig4.png
diff --git a/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff.md b/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff.md
deleted file mode 100644
index 7aa73664..00000000
--- a/docs/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff.md
+++ /dev/null
@@ -1,27 +0,0 @@
----
-title: Progress Test Studio Extensions Disabled in Firefox
-page_title: Progress Test Studio Extensions Disabled in Firefox
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Firefox Extensions Disabled
-
-**Test Studio 2017 R3 (v. 2017.3.1010) And Later**
-
-There is a single extension combining the recording and execution which could be downloaded from the Mozzila Extension Page. For your convenience here is a direct link to the <a href="https://addons.mozilla.org/en-US/firefox/addon/progress-test-studio-extension/" target="_blank">**Progress Telerik Test Studio Extension**</a>.
-
->If you face any troubles when installing or enabling the extension please expand the **Extension Install Procedure** section <a href="/getting-started/configure-your-browser/firefox#Extension_Install" target="_blank">in this article</a>.
-
-**Test Studio 2017 R2 SP1(v. 2017.2.824) And Earlier**
-
-The Firefox extensions are automatically installed with the Test Studio installation. Though in certain scenario it might be required to install these manually. Find below how to do that: 
-
-- Navigate to *C:\Program Files (x86)\Progress\Test Studio\Browser Extensions\Firefox4+* and drag the ***telerik_test_studio_automation-2015.2.918.0-fx-windows.xpi*** to an opened Firefox window.  
-- Navigate to *C:\Program Files (x86)\Progress\Test Studio\Bin\TestRecorderBrowserExtensions\Firefox* and drag the ***telerik_test_studio_recorder-2015.3.1228.0-fx-windows.xpi*** to an opened Firefox window.
-
-The extensions will now be available and enabled in Firefox.
-
-![Extensions][1]
-
-[1]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff/fig1.jpg
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/browser-inconsistencies-tg/html-button.md b/docs/troubleshooting-guide/browser-inconsistencies-tg/html-button.md
deleted file mode 100644
index f23e4f7d..00000000
--- a/docs/troubleshooting-guide/browser-inconsistencies-tg/html-button.md
+++ /dev/null
@@ -1,19 +0,0 @@
----
-title: HTML Button
-page_title: HTML Button
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# HTML Button
-
-You may receive different results when trying to get an HTML Button value between browsers. To get the value of an element, the Telerik Testing Framework injects JavaScript into the browser and the browser returns a value. Firefox and Chrome read the value of an attribute named "value", while IE returns the inner HTML of the button.
-
-For example, if we have a button defined as follows:
-
-	<button value="Value"> HTML </button>
-
-Internet Explorer will consider the value of the button to be "HTML", while Firefox and Chrome will consider it to be "Value".
-
-
-
diff --git a/docs/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure.md b/docs/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure.md
deleted file mode 100644
index cd7da59c..00000000
--- a/docs/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Package Load Failure
-page_title: Package Load Failure
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-# Package Load Failure
-
-## PROBLEM
-
-You receive a "Package Load Failure" error message while running Visual Studio after installing Test Studio. 
-
-![Load Failure][1]
-
-## SOLUTION
-
-The error may appear due to missing "Unit Testing Tools" package in Visual Studio. There is an option to uncheck those tools when installing Visual Studio 2008. Installing the tools back will resolve the problem. 
-
-To troubleshoot the error further, follow the steps from the MSDN blog post <a href="http://blogs.msdn.com/dr._ex/archive/2006/12/14/debugging-package-load-failures.aspx" target="_blank">here</a>.
-
-1.&nbsp; Open a command prompt and then change to the IDE subdirectory. Normally, for VS2012, the default is:
-
-  **C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE**
-
-2.&nbsp; Enter: *devenv /ResetSkipPkgs* at the command prompt. The purpose is to reset any Skip Package Load flags that were turned on during previous sessions. See if you still get the Package Load Failure dialog.
-
-3.&nbsp; If you do, then we're going to ask for you to create a log of VS2008 loading. To do that, exit VS2012, and at the command prompt enter:
-
-  *devenv /log*
-
-4.&nbsp; Let VS load and get the error, close the error dialog, and close VS. A log should have been created, but you may have to do a little hunting for it because it's created in your AppData folder. Typically this is:
-
-  **C:\Users\\\<username>\AppData\Roaming\Microsoft\VisualStudio\11.0**
-
-5.&nbsp; The file is called **ActivityLog.xml**. Please send us that file to study. Open a support ticket to attach files.
-
-[1]: /img/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure/fig1.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages.md b/docs/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages.md
deleted file mode 100644
index 66c54a14..00000000
--- a/docs/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages.md
+++ /dev/null
@@ -1,49 +0,0 @@
----
-title: Reset Skipped Packages
-page_title: Reset Skipped Packages
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-# Reset Skipped Packages
-
-
-## PROBLEM
-
-In most scenarios, after installing the Test Studio VS plugin, you should not have an issue with the installed software. If Test Studio states it installed successfully, then the full suite of software should be available so long as you are licensed to use it. It is possible, through changing settings and other means, to disable an extension in Visual Studio that is used by Test Studio. When this occurs, you will most likely receive a "Package Load Failure".
-
-
-## SOLUTION
-
-If you are directed by Telerik Support, or if you are troubleshooting on your own an issue with packages not loading properly, the below steps go through the basic process of Resetting Skipped Packages:
-
-1.&nbsp; Open a Command Prompt Console Window: 
-  
-  a. Click **Start > Run**.
-
-  b. In the prompt, type *cmd* and press **Enter**. 
-
-![cmd][1]
-
-2.&nbsp; Navigate to your Visual Studio IDE folder (the default location for the installation of Visual Studio). 
-
-![IDE][2]
-
-- **VS 2010**: Default Directory is **C:\Program Files\Microsoft Visual Studio 10.0\Common7\IDE\** 
-
-- **VS 2012**: Default Directory is **C:\Program Files\Microsoft Visual Studio 11.0\Common7\IDE\** 
-
-- **VS 2013**: Default Directory is **C:\Program Files\Microsoft Visual Studio 12.0\Common7\IDE\** 
-
-> Your directory may differ from the above. If it does, please use navigate to the directory that contains your devenv.exe file.
-
-3.&nbsp; Type in *devenv /ResetSkipPkgs* at the command prompt.
-
-![Reset][3]
-
-4.&nbsp; Press the **Enter** key.
-
-5.&nbsp; Allow Visual Studio some time to process the command. After it completes you should have access to your Telerik Tools once again. 
-
-[1]: /img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig1.png
-[2]: /img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig2.png
-[3]: /img/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages/fig3.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/installation-problems-tg/another-installation.md b/docs/troubleshooting-guide/installation-problems-tg/another-installation.md
index 1d6bcc9b..db7461d7 100644
--- a/docs/troubleshooting-guide/installation-problems-tg/another-installation.md
+++ b/docs/troubleshooting-guide/installation-problems-tg/another-installation.md
@@ -7,7 +7,7 @@ position: 1
 
 #"Another installation is in progress" error
 
-##Problem
+## Problem
 
 While installing Test Studio *Another installation is in progress* appears and it cannot continue:
 
@@ -15,7 +15,7 @@ The installer for Test Studio is a Windows .MSI install file. The above error me
 
 ![Error message][1]
 
-##Solution
+## Solution
 
 You should determine which installation is still in progress and finish it or abort it.
 
diff --git a/docs/troubleshooting-guide/installation-problems-tg/failed-internet-shortcut.md b/docs/troubleshooting-guide/installation-problems-tg/failed-internet-shortcut.md
deleted file mode 100644
index d06f3930..00000000
--- a/docs/troubleshooting-guide/installation-problems-tg/failed-internet-shortcut.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Failed Internet Shortcut
-page_title: Failed to Create Internet Shortcut
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Failed to Create Internet Shortcut
-
-
-## PROBLEM
-
- You may experience an installation problem that is caused when Internet shortcuts are created in the Start Menu. If this is the case, you'll see a message in the install log like this:
-
-
-*WixCreateInternetShortcuts: Creating IUniformResourceLocatorW shortcut 'C:\Documents and Settings\All Users\Start Menu\Programs\Telerik\Test Studio 20XX.X\Online Community Forums.url' target 'http://www.telerik.com/automated-testing-tools/community/forums.aspx'
-WixCreateInternetShortcuts: Error 0x80040154: failed to save shortcut 'C:\Documents and Settings\All Users\Start Menu\Programs\Telerik\Test Studio 20XX.X\Online Community Forums.url'
-WixCreateInternetShortcuts: Error 0x80040154: **failed to create Internet shortcut***
-
-## SOLUTION
-
-Run the installer from the command prompt that passes an argument to skip the Internet shortcut deployment. Here is the full command line:
-
-
-**msiexec /i [MsiPackagePath] DISABLE_INTERNET_SHORTCUTS=1**
diff --git a/docs/troubleshooting-guide/installation-problems-tg/vista-installer-error.md b/docs/troubleshooting-guide/installation-problems-tg/vista-installer-error.md
deleted file mode 100644
index 736efb50..00000000
--- a/docs/troubleshooting-guide/installation-problems-tg/vista-installer-error.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Vista Installer Error
-page_title: Vista Installer Problem
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
-
----
-# Vista Installer Problem
-
-## PROBLEM
-
- When I try to install on Windows Vista it says: 
-
-"*There is a problem with this Windows Installer package. A program required for this install to complete could not be run. Contact your support personnel or package vendor.*"
-
-
-## SOLUTION
-
-This is caused by trying to install as a regular user (default install mode) instead of as the administrator. Follow this procedure: 
-
-
-1.&nbsp; Copy the .msi to a folder on your machine.
-
-2.&nbsp; Start a command prompt with Admin privileges. [On the start menu, highlight the command prompt and right-click-> Run as admin]
-
-3.&nbsp; Navigate to the .msi and launch it from there.
-
diff --git a/docs/troubleshooting-guide/installation-problems-tg/vs-plugin-installation.md b/docs/troubleshooting-guide/installation-problems-tg/vs-plugin-installation.md
index 88661e5a..f6e63ddb 100644
--- a/docs/troubleshooting-guide/installation-problems-tg/vs-plugin-installation.md
+++ b/docs/troubleshooting-guide/installation-problems-tg/vs-plugin-installation.md
@@ -1,10 +1,10 @@
 ---
-title: Test Studio Project Not Available
-page_title: Test Studio Extensions Not Available in Visual Studio
+title: Test Studio Plugin Not Available in Visual Studio
+page_title: Test Studio Extensions in Visual Studio Not Available 
 description: "Test Studio plugin for Visual Studio is installed but I cannot create a project because the Test Studio project templates are not listed in Visual Studio. The Test Studio extensions in Visual Studio don't work. The Test Studio test is displayed as text in Visual Studio instead of showing the recorded steps."
 position: 0
 ---
-# Test Studio Plugin Not Available in Visual Studio
+# Test Studio Project Not Available in Visual Studio
 
 ## PROBLEM
 
@@ -14,7 +14,7 @@ I have installed Test Studio successfully along with the Visual Studio plugin. W
 
 In some occasions the extensions for Test Studio plugin, or some of them, do not get installed successfully during the overall product installation. Open the Visual Studio __Extensions->Manage Extensions__ menu to check what Test Studio extensions are listed.
 
-The below image demoes all Test Studio extensions when these are successfully added.
+The below image demos all Test Studio extensions when these are successfully added.
 
 ![Test Studio extensions in Visual Studio](/img/troubleshooting-guide/installation-problems-tg/vs-plugin-installation/vs2019-ts-extension2.png)
 
@@ -22,8 +22,12 @@ Depending on what extensions you see in your Visual Studio, you can proceed with
 
 1. Open a File Explorer and navigate to the Test Studio installation folder - __C:\Program Files (x86)\Progress\Test Studio__.
 1. Locate the subfolder with the version of Visual Studio you use - it contains the VSIX packages which install the Test Studio extensions for the respective Visual Studio version.
-1. Run these one by one in the order the files are listed - Common Package, Testing Framework, Test Adapter, Templates, TestStudioVSIP.<br>
-__Note:__ You can skip any of the packages if it is already available in the _Extensions->Manage Extensions_ list.
+1. Run these one by one in the order the files are listed - `Common Package`, `Testing Framework`, `Test Adapter`, `Templates`, `TestStudioVSIP`.<br>
+
+    > __Note:__ You can skip any of the packages if it is already available in the _Extensions->Manage Extensions_ list.
+
 1. Install the VSIX packages by double clicking each of them to trigger the VSIX installer UI and follow the wizard directions.<br>
-__Note:__ In case there is something to prevent the extension installation, you can see more details from the VSIX installer UI.
-1. If the installation for any package fails, collect the log from the failing VSIX Installer. It can be found under the _current user's %temp%_ folder and you can recognize it by its name - it is something like dd_VSIXInstaller_[GUID].log. Send the log to the product team for further analysis via a support ticket.
+    
+    > __Note:__ In case there is something to prevent the extension installation, you can see more details from the VSIX installer UI.
+
+1. If the installation for any package fails, collect the log from the failing VSIX Installer. It can be found under the _current user's %temp%_ folder and you can recognize it by its name - it is something like `dd_VSIXInstaller_[GUID].log`. Send the log to the product team for further analysis via a support ticket.
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/401-in-results.md b/docs/troubleshooting-guide/load-testing-problems-tg/401-in-results.md
index 952d0e4e..d15de4f8 100644
--- a/docs/troubleshooting-guide/load-testing-problems-tg/401-in-results.md
+++ b/docs/troubleshooting-guide/load-testing-problems-tg/401-in-results.md
@@ -1,11 +1,11 @@
 ---
-title: 401 in Results
-page_title: 401 in Results
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+title: 401 in Load Test Results
+page_title: 401 in Load Test Results
+description: "Discover how to troubleshoot 401 errors in Test Studio load test results. Learn about common causes, such as authentication challenges, and find solutions to ensure successful automated load testing workflows."
 position: 1
-publish: false
+published: false
 ---
-# Error 401 in Results
+# How to Address Error 401 in Load Test Results
 
 ## PROBLEM
 
@@ -13,13 +13,7 @@ When running a load test, the results include a number of 401 responses.
 
 ## SOLUTION
 
-This behavior can occur when you configure your load test to use Windows Authentication credentials. Test Studio opens a new connection each time it executes a user profile, which can result in a large number of 401 responses containing authentication challenges applicable to the requested resource. 
+This behavior occurs when the traffic recorded in the User Profile of the load test is not setup correctly. Thus the traffic sent towards the application server is not authorized to access it. 
 
-- If one or two 401 responses are followed by a 200-Okay response, this means that authentication was successful. 
+The approach for addressing these errors is to revise all requests in the User Profile, remove the unnecessary queries and parameterize the dynamic parts of the rest. Use the recommended steps in <a href="/troubleshooting-guide/load-testing-problems-tg/resolving-server-load-mismatch-telerik-load-tests" target="_blank">this KB article about adjusting the user profile in Test Studio load test</a>. 
 
-- If there are more than two 401 responses with no 200 response, this means that your load test is not providing valid credentials when they are required by the server. 
-
-- If the 401 responses are followed by a 403-Forbidden response, this means that the credentials your load test provided lacked the permissions required for the requested resource.
-
-
-For more information, see <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.4.2" target="_blank">Fielding et al. (June 1999), "Hypertext Transfer Protocol – HTTP/1.1", IETF, RFC 2616, Section 10.4.2</a>.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service.md b/docs/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service.md
deleted file mode 100644
index fe5e75ab..00000000
--- a/docs/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service.md
+++ /dev/null
@@ -1,21 +0,0 @@
----
-title: Can't Add Scheduling Service
-page_title: Can't Add Scheduling Service
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Cannot Add Scheduling Service
-
-## PROBLEM
-
- In the **Manage Virtual Users** dialog, the **Add Scheduling Service** button does not connect to a remote scheduling service.
-
-![Could not connect][1]
-
-## SOLUTION
-
-As of 2013.1.806, the Add Scheduling Service dialog only looks for Scheduling Servers that are listening on port 8009. If your scheduling service is listening on a different port, you will need to change it to 8009 before you can add it to the load test. 
-
-[1]: /img/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service/fig1.png
-
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/cannot-dispatch-load-test.md b/docs/troubleshooting-guide/load-testing-problems-tg/cannot-dispatch-load-test.md
deleted file mode 100644
index 8df57231..00000000
--- a/docs/troubleshooting-guide/load-testing-problems-tg/cannot-dispatch-load-test.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Cannot Dispatch Load Test
-page_title: Cannot Dispatch Load Test
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Cannot Dispatch Load Test
-
-## PROBLEM
-
-When attempting to run a load test, the test list fails. The test list results for the load test contain this error: "Cannot Dispatch Load Test."
-
-## SOLUTION
-
-This error can occur when a firewall is blocking the port that the load test requires. The more load tests you run, the more open ports your Execution Server may require. To resolve this behavior:
-
-- Ensure that any active firewall on the Execution Server(s) running the load test is not blocking the ports in the range 8030-8039.
-
-- If this does not resolve the behavior, try unblocking a larger range of ports in the range above 8039 (for example, ports 8039-8059).
-
-- If the behavior still occurs, try closing and re-opening the <a href="/features/scheduling-test-runs/overview" target="_blank">Test Studio Test Runner System Tray process</a>.
-
-
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/duplicate-dynamic-targets.md b/docs/troubleshooting-guide/load-testing-problems-tg/duplicate-dynamic-targets.md
deleted file mode 100644
index dd01ac02..00000000
--- a/docs/troubleshooting-guide/load-testing-problems-tg/duplicate-dynamic-targets.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Duplicate Dynamic Targets
-page_title: Duplicate Dynamic Targets
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Duplicate Dynamic Targets
-
-
-## PROBLEM
-
-Load test generates duplicate copies of the same dynamic variable with identical values.
-
-## SOLUTION
-
-There is currently no way to prevent this behavior. To work around this result, select the repeated variable in all steps it is used in.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/load-test-run-quits.md b/docs/troubleshooting-guide/load-testing-problems-tg/load-test-run-quits.md
deleted file mode 100644
index b40795fc..00000000
--- a/docs/troubleshooting-guide/load-testing-problems-tg/load-test-run-quits.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Load Test Run Quits
-page_title: Load Test Run Quits
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Load Test Run Quits
-
-
-##PROBLEM
-
-Load test execution does not complete successfully. 
-
-##SOLUTION
-
-This behavior may be caused by a 'File name too long' exception. This is because the load test project location file path length exceeds 255 characters. To address this, relocate or rename the load project files and folders to avoid exceeding the 255 character limit.
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/missing-dynamic-targets.md b/docs/troubleshooting-guide/load-testing-problems-tg/missing-dynamic-targets.md
deleted file mode 100644
index 28183f6a..00000000
--- a/docs/troubleshooting-guide/load-testing-problems-tg/missing-dynamic-targets.md
+++ /dev/null
@@ -1,17 +0,0 @@
----
-title: Missing Dynamic Targets
-page_title: Missing Dynamic Targets
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Missing Dynamic Targets
-
-## PROBLEM
-
-Test Studio Load Testing does not capture <a href="/features/testing-types/load-testing/dynamic-targets" target="_blank">Dynamic Targets</a> from your application.
-
-## SOLUTION
-
-In Test Studio versions 2013 R1 and earlier, Load Tests will not detect dynamic targets using <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec3.html#sec3.6.1" target="_blank">chunked transfer encoding</a>. Upgrading to 2013 R2 or later should resolve this behavior.
-
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/no-locahost-traffic.md b/docs/troubleshooting-guide/load-testing-problems-tg/no-locahost-traffic.md
index 1af85b1c..5d27f70f 100644
--- a/docs/troubleshooting-guide/load-testing-problems-tg/no-locahost-traffic.md
+++ b/docs/troubleshooting-guide/load-testing-problems-tg/no-locahost-traffic.md
@@ -4,7 +4,7 @@ page_title: No Locahost Traffic Captured in Load Test
 description: "Test Studio Load test doesn't capture traffic for localhost. How to workaround not capturing localhost in load user profile."
 position: 1
 ---
-# No Locahost Traffic
+# No Localhost Traffic
 
 ## PROBLEM
 
@@ -16,4 +16,4 @@ Replace _localhost_ with the machine name or IP address of the local machine.
 
 **See Also**
 
-- <a href="http://fiddler2.com/documentation/Observe-Traffic/Troubleshooting/NoTrafficToLocalhost" target="_blank">No Traffic to Localhost in Fiddler</a>
\ No newline at end of file
+- <a href="https://docs.telerik.com/fiddler/observe-traffic/troubleshooting/notraffictolocalhost" target="_blank">No Traffic to Localhost in Fiddler</a>
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/no-results-data.md b/docs/troubleshooting-guide/load-testing-problems-tg/no-results-data.md
index 6ab28b22..b6a84bf1 100644
--- a/docs/troubleshooting-guide/load-testing-problems-tg/no-results-data.md
+++ b/docs/troubleshooting-guide/load-testing-problems-tg/no-results-data.md
@@ -1,7 +1,7 @@
 ---
 title: No Results Data
 page_title: No Results Data
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Troubleshoot the issue of missing results data in Test Studio load tests. Learn why results may not appear, how sampling period settings affect data collection, and steps to resolve common load testing problems."
 position: 1
 ---
 # No Results Data
diff --git a/docs/troubleshooting-guide/load-testing-problems-tg/resolving-server-load-mismatch-telerik-load-tests.md b/docs/troubleshooting-guide/load-testing-problems-tg/resolving-server-load-mismatch-telerik-load-tests.md
new file mode 100644
index 00000000..6c78fb50
--- /dev/null
+++ b/docs/troubleshooting-guide/load-testing-problems-tg/resolving-server-load-mismatch-telerik-load-tests.md
@@ -0,0 +1,132 @@
+---
+title: Resolving Mismatch in Server Load During Telerik Test Studio Load Tests
+description: Troubleshooting server load mismatch during load tests in Telerik Test Studio, identifying dynamic targets, and adjusting settings for accurate simulation.
+type: how-to
+page_title: Fixing Server Traffic Discrepancy in Telerik Test Studio Load Tests
+meta_title: Fixing Server Traffic Discrepancy in Telerik Test Studio Load Tests
+slug: resolving-server-load-mismatch-telerik-load-tests
+tags: telerik test studio, load tests, dynamic targets, test studio settings, troubleshooting
+res_type: kb
+ticketid: 1683582
+---
+
+# How to Address Mismatch in Server Load During Load Test Runs
+
+## Description
+
+I designed a load test in Telerik Test Studio to simulate multiple users, but the server only receives a fraction of the intended traffic. Requests per second do not match the test design, even though CPU and memory usage on both the site server and the hosting virtual machine have sufficient capacity. I need to troubleshoot why the traffic isn't being generated correctly.
+
+This knowledge base article also answers the following questions:
+- How do I fix low server traffic during load tests in Telerik Test Studio?
+- How do I adjust user profiles and dynamic targets in Telerik Test Studio load tests?
+- How can I simulate accurate server load with multiple concurrent users in Test Studio?
+
+## Solution
+
+To ensure proper load simulation and address the discrepancy in server traffic, you need to adjust the load test user profile to handle all requests correctly. Follow each of these steps for this: 
+
+<!-- no toc -->
+- [Adjusting the User Profile](#adjusting-the-user-profile)
+- [Configuring Dynamic Targets](#configuring-dynamic-targets)
+- [Adding Think Times](#adding-think-times)
+- [Running the Load Test](#running-the-load-test)
+
+
+> __Note!__ 
+> <br>
+> All images listed in the article are for illustrative purposes and do not reflect any real life scenario. The required __adjustments are unique to the specific captured traffic__ in each user profile and need to be carefully determined!
+
+### Adjusting the User Profile
+
+1. Open the user profile created for the load test in Edit mode (double click the profile to work with it). This profile is based on the HTTP(S) traffic captured during the execution of the base web test scenario used to generate the user profile.
+   
+   ![Open Load test user profile](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/edit-profile.gif)
+
+2. Remove requests for visual resources such as JavaScript scripts, CSS files, images, fonts, and icons. These requests are unnecessary for load testing since load test doesn't use the application UI.
+
+   ![Example of requests loading visual resources](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/requests-loading-visual-resources.png)
+
+3. Retain only essential requests required for the actual interactions with the application server.
+
+   ![Example of non-essential requests from 3rd party services](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/remove-queries-to-3rd-party-services.png)
+
+### Configuring Dynamic Targets
+
+1. Review the captured traffic which remains after clearing the non-essential requests and drill down which are the dynamic session identifiers - such as cookies, headers, or query parameters - exchanged during the web test execution. These identifiers ensure the user session is accepted from the application server as a valid one so they need to be correctly handled during the load test execution. 
+
+    <table id="no-table">
+      <tr>
+        <td>
+          <img alt="Dynamic value in response" src="/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-response.png" loading="lazy" decoding="async">
+          <br>
+          <b>Dynamic value returned in response</b>
+        </td>
+        <td>
+          <img alt="Reused dynamic value in next request" src="/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/identify-dynamics-in-request.png" loading="lazy" decoding="async">
+          <br>
+          <b>Reused dynamic value in next request</b>
+        </td>
+      <tr>
+    </table>
+   
+2. Add dynamic targets to replace these identifiers for each virtual user:
+   
+   - Use the <a href="/automated-tests/load/designing-load-tests/dynamic-targets#source-section-properties" target="_blank">source step properties</a> to define the part of the response (e.g., body, headers, cookies).
+   - Use the <a href="/automated-tests/load/designing-load-tests/dynamic-targets#search-options" target="_blank">search options</a> to pinpoint specific dynamic values.
+   - Set up the <a href="/automated-tests/load/designing-load-tests/dynamic-targets#destination-section-properties" target="_blank">destination step properties</a> to reuse the dynamic value (e.g., as a header, query parameter, or cookie).
+
+   > __Tip__
+   ><br>
+   > The example shows setting a dynamic target to cover a redirect to specific URL generated during the current user session. 
+
+   ![Create custom dynamic target to cover the URL redirect](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/add-dynamic-target.png)
+
+   - After adding the custom dynamic target you can see it listed in the target step request field.  
+
+   ![See the custom added dynamic target listed in the target step request part](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/see-added-dynamic-target-in-target-step.png)
+
+3. Refer to this <a href="https://www.telerik.com/blogs/custom-dynamic-targets-in-load-tests" target="_blank">blog post about dynamic targets</a> for another detailed example of setting up a Request Verification token.
+4. Iterate through all requests in the captured traffic to __identify all necessary dynamic targets__. Usually in real life scenario more than one dynamic identifier needs to be transferred from one step's response to the following requests.
+   - __E.g.__: 
+   - A session identifier cookie returned in one request's response is then used in all following requests. So you need a dynamic target for each step. 
+   - Or, in one request's response you find a session identifier cookie and a verification token which are reused in the next step - these two need separate dynamic targets from one step to the other. 
+
+### Adding Think Times
+
+Include <a href="/automated-tests/load/designing-load-tests/modifying-tests#addremovechange-the-think-times" target="_blank">think times</a> in the user profile to simulate realistic user behavior. 
+
+Users typically need time to process the displayed information before interacting with the application, and the think times simulate delays between requests in your User Profile. That way executing the load test ensures accurate user behavior simulation.
+
+![Adding Think times](/img/troubleshooting-guide/load-testing-problems-tg/resolve-server-load-mismatch/think-times.png)
+
+The general recommendation is to insert a think time between every few requests which represent certain user action. You can refer to the following sample workflow: 
+
+- Load initial URL of the application; 
+- Insert think time - allow the user time to enter username and password, and to hit the Login button; 
+- Next few requests cover the authentication process and expected is that the user is now logged;
+- Insert think time - allow the user time to process the next action in scenario, e.g. to fulfill a form and submit it; 
+- Next few requests cover submitting the form and getting response from the application server; 
+- Etc. 
+
+
+### Running the Load Test
+
+1. <a href="/automated-tests/load/designing-load-tests/test-settings#available-users-and-time-settings" target="_blank">Set the test to run</a> with 1 virtual user for 1 minute to verify the setup and ensure all requests execute successfully.
+2. Once verified, increase the number of virtual users and test duration to simulate the desired load.
+3. When the User profile is validated and you are sure it covers the user workflow, you can use <a href="/automated-tests/load/running-load-test/best-practices" target="_blank">remote execution</a> to simulate high user concurrency effectively.
+
+## Additional Resources
+
+- [Getting Started with Load Testing in Test Studio](/automated-tests/load/designing-load-tests/getting-started)
+- [Dynamic Targets Overview](/automated-tests/load/designing-load-tests/dynamic-targets)
+- [Load Test Settings](/automated-tests/load/designing-load-tests/test-settings)
+- [Modifying User Profiles in Load Tests](/automated-tests/load/designing-load-tests/modifying-tests)
+- [Best Practices for Running Load Tests](/automated-tests/load/running-load-test/best-practices)
+- [Step-by-Step: Load Testing](https://www.telerik.com/blogs/test-studio-step-by-step-load-testing)
+- [Designing Load Tests with Test Studio and Fiddler Everywhere in 6 Easy Steps](https://www.telerik.com/blogs/designing-load-tests-test-studio-fiddler-6-easy-steps)
+
+## See Also
+
+- [Dynamic Targets Overview](/automated-tests/load/designing-load-tests/dynamic-targets)
+- [Load Test Settings](/automated-tests/load/designing-load-tests/test-settings)
+- [Modifying User Profiles in Load Tests](/automated-tests/load/designing-load-tests/modifying-tests) 
diff --git a/docs/troubleshooting-guide/network-related-problems-tg/missing-mapped-netword-drives.md b/docs/troubleshooting-guide/network-related-problems-tg/missing-mapped-netword-drives.md
index 8b8f44d2..1fbcdcbe 100644
--- a/docs/troubleshooting-guide/network-related-problems-tg/missing-mapped-netword-drives.md
+++ b/docs/troubleshooting-guide/network-related-problems-tg/missing-mapped-netword-drives.md
@@ -6,13 +6,13 @@ position: 1
 ---
 # Missing mapped network drives
 
-##Problem:
+## Problem:
 
 When open a new project in Test Studio the browser dialog may not show the mapped network drives:
 
 ![missing drives][1]
 
-##Solution:
+## Solution:
 
 You need to set the following registry option:
 
diff --git a/docs/troubleshooting-guide/recording-problems-tg/cannot-launch-exploratory.md b/docs/troubleshooting-guide/recording-problems-tg/cannot-launch-exploratory.md
deleted file mode 100644
index 257b7147..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/cannot-launch-exploratory.md
+++ /dev/null
@@ -1,32 +0,0 @@
----
-title: Can't Launch Exploratory Tool
-page_title: Can't Launch Exploratory Tool
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Cannot Launch Exploratory Tool
-
-## PROBLEM
-
-I receive one of the following errors when attempting to launch the <a href="/features/testing-types/exploratory-testing/Overview" target="_blank">Exploratory Testing</a> tool.
-
-- **Internet Explorer**: Feedback.Listener is not running!
-
-- **Firefox**: Cannot launch Telerik Exploratory Tool.
-
-- **Safari**: Telerik Exploratory Testing Extension NaN.
-
-- **Chrome**: Cannot launch Telerik Exploratory Tool.
-
-## SOLUTION
-
-Start the Feedback Listener process manually from the following location, then launch the tool again through the browser.
-
-- **C:\Program Files (x86)\Progress\Test Studio\Bin\Feedback\Telerik.TestStudio.Feedback.Listener.exe**
-
- The Exploratory Testing tool is currently unable to launch for users with non-administrator rights.
-
-- You may need to right click *Telerik.TestStudio.Feedback.Listener.exe* and select <a href="http://www.sevenforums.com/tutorials/11841-run-administrator.html" target="_blank">Run as Administrator</a>. Then launch the browser in the same fashion.
-
- 
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/recording-problems-tg/ie-fails-to-record-execute-test.md b/docs/troubleshooting-guide/recording-problems-tg/ie-fails-to-record-execute-test.md
deleted file mode 100644
index 3b3bc1f1..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/ie-fails-to-record-execute-test.md
+++ /dev/null
@@ -1,29 +0,0 @@
----
-title: Internet Explorer could not record/execute a test
-page_title: Internet Explorer could not record/execute a test
-description: "Internet Explorer could not record/execute a test in Test Studio. Is there a specific setting to adjust in order to use IE for recording and executing Test Studio test"
-position: 1
-publish: false
----
-# Internet Explorer 11 could not record/execute a test
-
-## PROBLEM
-
-Internet Explorer 11 is successfully calibrated by Test Studio and <a href="/getting-started/installation/configure-windows-server" target="_blank">IE Enhanced Security (Windows Server OS)</a> is turned off. Though when trying to execute a test in Internet Explorer once the browser is launched it stops on the "about:blank page" and the test times out. In the execution log the following exception is recorded:
-
-	System.TimeoutException: Wait for condition has timed out
-   	at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
-   	at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
-   	at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
-   	at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
-   	at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
-   	at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)
-   	at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)
-   	at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)
- 
-
-## SOLUTION
-
-Download and install <a href="https://www.microsoft.com/en-us/download/details.aspx?id=30656" target="_blank">Team Explorer</a>.  
-
-
diff --git a/docs/troubleshooting-guide/recording-problems-tg/java-flash-activex.md b/docs/troubleshooting-guide/recording-problems-tg/java-flash-activex.md
deleted file mode 100644
index 17b0c801..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/java-flash-activex.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Java Flash ActiveX
-page_title: Java Flash ActiveX
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Recording Java Plugins, Flash Objects, ActiveX Controls, and Chrome Frames
-
-
-## PROBLEM
-
-I am recording actions against a Java plugin, Flash object, ActiveX control, or Google Chrome Frame. No corresponding steps are recorded in Test Studio, however.
-
-## SOLUTION
-
-Test Studio sees Java plugins, Flash objects, ActiveX controls, and Google Chrome Frames as a single block \<object> or \<applet> element and cannot distinguish the individual components within it. It's basically a black box and the best alternative is to <a href="/troubleshooting-guide/test-execution-problems-tg/invoke-blind-mouse-click" target="_blank">Invoke Blind Mouse Clicks</a> and <a href="/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing" target="_blank">Blind Keyboard Typing</a> on it.
-
diff --git a/docs/troubleshooting-guide/recording-problems-tg/no-file-path-ie10.md b/docs/troubleshooting-guide/recording-problems-tg/no-file-path-ie10.md
deleted file mode 100644
index b29c53db..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/no-file-path-ie10.md
+++ /dev/null
@@ -1,23 +0,0 @@
----
-title: No File Path for Upload Step in IE 10
-page_title: No File Path for Upload Step in IE 10
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# No file path for IE 10 upload dialog
-
-## PROBLEM
-
-In Internet Explorer 10, recording against a file upload dialog may record a dialog handler step with no file path.
-
-![Steps][1]
-
-## SOLUTION
-
-In Windows 8, the default folder settings hide known file extensions, which prevents Test Studio file path recording. To fix this behavior, disable the 'Hide extensions for known file types' setting in the Folder Options View tab for the origin folder.
-
-![Folder Options][2]
-
-[1]: /img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig1.png
-[2]: /img/troubleshooting-guide/recording-problems-tg/no-file-path-ie10/fig2.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/recording-problems-tg/parsing-error.md b/docs/troubleshooting-guide/recording-problems-tg/parsing-error.md
index 9cb2bd58..f03a142d 100644
--- a/docs/troubleshooting-guide/recording-problems-tg/parsing-error.md
+++ b/docs/troubleshooting-guide/recording-problems-tg/parsing-error.md
@@ -1,7 +1,7 @@
 ---
 title: Parsing Error
 page_title: Resolving Errors Related to Invalid HTML Code
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to resolve parsing errors in Test Studio caused by invalid HTML code. This article explains common causes, troubleshooting steps, and best practices for ensuring your web pages are compatible with automated recording and testing."
 position: 1
 ---
 # Resolving Errors Related to Invalid HTML Code
diff --git a/docs/troubleshooting-guide/recording-problems-tg/recorder-attached.md b/docs/troubleshooting-guide/recording-problems-tg/recorder-attached.md
deleted file mode 100644
index 4b4979b0..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/recorder-attached.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Recorder Must Be Attached
-page_title: Silverlight Unable to Attach Recorder
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Silverlight: Unable to Attach Recorder
-
-## PROBLEM
-
-You receive the message below when attaching the Test Studio recorder to an existing browser instance with a Silverlight application loaded.
-
-![Refresh Page][1]
-
-## SOLUTION
-
-This is normal and expected behavior. The technical challenge is that Test Studio injects hooks into the Silverlight application as the browser is downloading the .XAP file. In this case the browser has already downloaded the .XAP file, so Test Studio cannot hook into the already running Silverlight application.
-
-There are two solutions:
-
-
-1.&nbsp; Click OK on the message above. After the recorder attaches to the browser, click Refresh in the Internet Explorer browser window (pause the recorder first so a "Refresh" step is not recorded). This forces the Silverlight application to reload so Test Studio can inject its hooks and properly record actions and verifications.
-
-2.&nbsp; Attach the recorder to the browser window *before* the Silverlight application is loaded. Pause recording until you reach the desired page so no unwanted steps are inadvertently recorded.
-
-
-[1]: /img/troubleshooting-guide/recording-problems-tg/recorder-attached/fig1.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/recording-problems-tg/recorder-blocks-wpf-popup.md b/docs/troubleshooting-guide/recording-problems-tg/recorder-blocks-wpf-popup.md
index a7c5ec41..08268084 100644
--- a/docs/troubleshooting-guide/recording-problems-tg/recorder-blocks-wpf-popup.md
+++ b/docs/troubleshooting-guide/recording-problems-tg/recorder-blocks-wpf-popup.md
@@ -1,7 +1,7 @@
 ---
 title: Recorder Blocks WPF Popup
 page_title: Recorder Blocks WPF Pop-up
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Resolve Recorder Blocks WPF Pop-up"
 position: 1
 ---
 # Recorder Blocks WPF Pop-up
diff --git a/docs/troubleshooting-guide/recording-problems-tg/refresh-dom.md b/docs/troubleshooting-guide/recording-problems-tg/refresh-dom.md
index aa9e36d3..1f2be225 100644
--- a/docs/troubleshooting-guide/recording-problems-tg/refresh-dom.md
+++ b/docs/troubleshooting-guide/recording-problems-tg/refresh-dom.md
@@ -17,9 +17,9 @@ Some elements in an application are loaded in the DOM dynamically during executi
 
 Very often in such situation refreshing the DOM after that particular action will allow the execution to go smoothly. There is no UI step for that though it could be easily obtained in <a href="/features/custom-steps/script-step" target="_blank">a coded step</a>. The only row of code you need to add is the following:
 
-```C#
+````C#
 Manager.ActiveBrowser.RefreshDomTree();
-```
-```VB
+````
+````VB
 Manager.ActiveBrowser.RefreshDomTree()
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/recording-problems-tg/silverlight-highlighting.md b/docs/troubleshooting-guide/recording-problems-tg/silverlight-highlighting.md
deleted file mode 100644
index 7cf0f79e..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/silverlight-highlighting.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Silverlight Highlighting
-page_title: Hover Over Highlighting Not Recognizing Individual Silverlight Elements
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Hover Over Highlighting Not Recognizing Individual Silverlight Elements
-
-## PROBLEM
-
-Hover over highlighting does not recognize individual Silverlight elements in your application. Although accessible through the DOM, the recording surface only detects the Silverlight components as one object.
-
-# SOLUTION
-
-Set the *windowless* parameter for your Silverlight application to true:
-
-	<object id="xamlHost0" width="900" height="412" type="application/x-silverlight">
-    <param value="transparent" name="background"/>
-    <param value="true" name="windowless"/>
-    <!-- other params go here -->
-	</object>
-
-Here is the technical problem that causes this behavior and why/how setting the *windowless* parameter to true helps:
-
-The default behavior is for IE to create a separate real Win32 window (with no border/chrome) and render the Silverlight application within this real window. This window is overlaid on top of the \<object> tag being rendered within the browser window such that they should lay directly on top of one another. For Test Studio to attach to and control the Silverlight application, it must locate the correct Win32 window and hook into it. Test Studio locates the correct window by asking the browser for the screen coordinates of the <object> tag and then hooking into the Win32 window that overlays that location.
-
-However, sometimes (we have yet to clearly understand when/why this happens) IE gives incorrect coordinates for where the \<object> tag is being rendered within the browser window. It says it is located at position X (an incorrect position), but the window is actually at position Y. As a result, Test Studio is unable to find the Silverlight application window so that it can hook into it. This causes the behavior described above where the windowless parameter is set to the default setting of false.
-
-By setting the windowless parameter to true, IE renders the Silverlight application directly in the browser window. Test Studio detects this property setting and injects its Silverlight hooks into the IE browser window when seen instead of looking for a separate Win32 window. Thus, even though IE may give incorrect coordinates for the \<object> tag, Test Studio is no longer sensitive to it.
-
-
-We don't know when/why IE sometimes gives incorrect screen coordinates for the <object> tag. When it does, setting the windowless parameter to true is the only solution. Different versions of IE may behave differently, and turning on/off Quirks mode may also change the behavior of IE in this area.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect-oob.md b/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect-oob.md
deleted file mode 100644
index 36c52791..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect-oob.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Unable to connect to Silverlight OOB 
-page_title: Unable to Connect to Silverlight OOB 
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Unable to Connect to Silverlight Out Of Browser Application 
-
-## PROBLEM
-
-I am not able to record my Silverlight out of browser application. It fails to attach with the following errors:
-
-
-Outer Exception Type: System.TimeoutException<br/>
-Message: Wait for condition has timed out<br/>
-HRESULT: 0x80131505 (Official ID (if app.) = COR_E_TIMEOUT, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5381)<br/>
-Call Stack:<br/>
-at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)<br/>
-at ArtOfTest.Common.WaitSync.For\[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
-at ArtOfTest.Common.WaitSync.For\[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
-
-at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
-
-at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
-
-at Telerik.TestStudio.Web.IERecorder.IERecorderManager.LaunchNewRecorder(Action`2 asyncCallback, FloatingUIMode mode, BrowserType browserType, String arguments)
-
-##Solution
-
-This behavior appears on systems which have the <a href="https://technet.microsoft.com/en-us/library/security/MS15-049">MS15-049</a> security fix (KB3058985) installed. It is included in Silverlight version 5.1.40416 and later.
-
-This security fix was addressed in Windows Updates on 12th of May, 2015. The patch prevents an elevation of privilege issue by restricting Silverlight applications running inside sllauncher.exe (the out-of-browser Silverlight container) to a **low integrity level**. 
-
-
-
-You may wish to uninstall KB3058985 security patch or downgrade Silverlight below version 5.1.40416 to allow recording the Silverlight OOB applications.
-
diff --git a/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect.md b/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect.md
deleted file mode 100644
index 488e11a0..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect.md
+++ /dev/null
@@ -1,104 +0,0 @@
----
-title: Silverlight Unable to Connect
-page_title: Unable to Connect to Silverlight Application 
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/troubleshooting_guide/recording-problems/unable-to-connect-to-silverlight-application.aspx, /user-guide/troubleshooting_guide/recording-problems/unable-to-connect-to-silverlight-application
-position: 1
-publish: false
----
-# Unable to Connect to Silverlight Application 
-
-## PROBLEM
-
- You cannot record your Silverlight application through Test Studio and receive an "Unable to connect" error message. 
-
-## KNOWN ISSUES
-
-- **The MIME Type for your XAP file is not properly registered on your web server. This is the most common cause for this type of issue.**
-
-- Automation only supports .XAP Silverlight app deployment (the .NET method). 
-
-> .XBAP or Javascript Silverlight deployment is not supported.
-
-## SOLUTION
-
-1.&nbsp; Make sure that you have registered the .XAP file extension within IIS. These instructions are also documented <a href="http://learn.iis.net/page.aspx/262/configuring-iis-for-silverlight-applications/" target="blank">**here**</a>.
-
-
- a. Click **Start** > **Run** (XP) or **Start** then click in the search field (Vista/Win7/Win8).
- b. Type *IIS* within the search/run field.
- c. Hit 'Enter' on your keyboard.
- d. Make sure you are targeting the "Default Web Site" in the left column.
- e. Double-click *MIME Types* in Features View.
- f. Click **Add** (right column).
- g. Set the file extension to **.XAP**.
- h. Set the MIME Type to *application/x-silverlight-app*
- i. Click OK.
-
-2.&nbsp; If the Web and Silverlight app is deployed locally, try adding a period ('.') after localhost, as in http://localhost.: 
-
-3.&nbsp; Delete the entire cache for the test playback browser: 
-
-
- a. In Interent Explorer, select: **Tools > Internet Options > General Tab > Delete (Within the browsing history section)**
-
- b. In Firefox, select: **Tools > Clear Recent History > Select Everything in the 'Time Range to Clear' drop-down menu > Choose Clear Now**
-
- c. In Safari, select: **Settings (the gear in the upper-right of the Safari window) > Reset Safari > Check only Empty the Cache > Click Reset**
-
- d. In Chrome, select: **Tools menu > Options > Click the Under the Hood tab > Click Clear browsing data...**
-
-
-4.&nbsp; <a href="http://support.microsoft.com/kb/923737" target="_blank">Reset Internet Explorer settings</a>.
-
-5.&nbsp; Try increasing the (Settings.) <a href="/features/project-settings/recording-options" target="_blank">Silverlight Connect Timeout</a> if the Silverlight app has a longer load time. 
-
-6.&nbsp; Try setting externalAccessfromCrossDomainCallers to script only your application's AppManifest.xaml file by doing the following in your html page and Silverlight manifest: 
-
- a. **Example for html page:**
-
-
-	<div id="silverlightControlHost" />
-	<object height="300" width="300" type="application/x-silverlight-2" data="data:application/x-silverlight-2," >
-	<param value="http://a-remote-domain.com/ClientBin/SilverlightClient.xap" name="source" />
-	<param value="white" name="background" />
-	<param value="3.0.40723.0" name="minRuntimeVersion" />
-	<param value="true" name="enableHtmlAccess" />
-	<param value="visOnly=true" name="initParams" />
-	<a style="text-decoration: none;" href="http://go.microsoft.com/fwlink/?LinkID=149156">
-	<img style="border-style: none; width: 400px; height: 200px;" alt="Install Microsoft Silverlight" src="http://storage.timheuer.com/sl4wp-ph.png"/></a></object>
-	<iframe style="border: 0px none ; visibility: hidden; height: 0pt; width: 0pt;" /></div>
-
- b. **Example for SL Manifest:** 
-
-
-	<Deployment xmlns="http://schemas.microsoft.com/client/2007/deployment" xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml" ExternalCallersFromCrossDomain="ScriptableOnly">
-	<Deployment.Parts>
-	</Deployment.Parts>
-	</Deployment>
-
-> See <a href="https://social.msdn.microsoft.com/Forums/silverlight/en-us/home?category=silverlight" target="_blank">this Microsoft forum thread</a> for more information
-
-7.&nbsp; Try setting the "windowless" property for your Silverlight app to "true":
-
-Example (similar to first example above):
-
-
-	<object id="xamlHost0" width="900" height="412" type="application/x-silverlight">
-	<param value="transparent" name="background"/>
-	<param value="true" name="windowless"/>
-	<!-- a bunch of other params go here -->
-	</object>
-
-8.&nbsp; Check the headers your server is sending for the Silverlight Page by: 
-
-
- a. Install/Run <a href="http://www.telerik.com/fiddler" target="_blank">Fiddler</a> and load your Silverlight page.
- 
- b. Click the response for the .xap file
- 
- c. Click **Inspectors > Headers**.
- 
- There should be an entry titled: Content:*application/x-silverlight-app*
- This must be in response in order for the Telerik Testing Framework or Test Studio to detect the Silverlight app.
-
diff --git a/docs/troubleshooting-guide/recording-problems-tg/ts-fails-to-start-msedge.md b/docs/troubleshooting-guide/recording-problems-tg/ts-fails-to-start-msedge.md
index eb979801..3d38aedb 100644
--- a/docs/troubleshooting-guide/recording-problems-tg/ts-fails-to-start-msedge.md
+++ b/docs/troubleshooting-guide/recording-problems-tg/ts-fails-to-start-msedge.md
@@ -3,7 +3,7 @@ title: Test Studio Fails to Start Edge Chromium
 page_title: Test Studio Fails to Start Microsoft Edge Browser
 description: "Telerik Test Studio cannot start Microsoft Edge Chromium browser in the mode without browser extension."
 position: 1
-publish: true
+published: true
 ---
 # Test Studio Fails to Start Microsoft Edge Browser
 
@@ -11,9 +11,9 @@ publish: true
 
 *Telerik Test Studio cannot start Edge browser without browser extension. While Test Studio tests work fine with Chrome.*
 
-```
+````
 System.TimeoutException: This request operation sent to net.pipe://localhost/Telerik/TestingFramework.Hosts.Manager did not receive a reply within the configured timeout (00:01:00). The time allotted to this operation may have been a portion of a longer timeout. This may be because the service is still processing the operation or because the service was unable to send a reply message. Please consider increasing the operation timeout (by casting the channel/proxy to IContextChannel and setting the OperationTimeout property) and ensure that the service is able to connect to the client.
-```
+````
 
 ## SOLUTION
 
diff --git a/docs/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder.md b/docs/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder.md
deleted file mode 100644
index 841abf3f..00000000
--- a/docs/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder.md
+++ /dev/null
@@ -1,90 +0,0 @@
----
-title: Unable to Launch Recorder
-page_title: Unable to Launch Recorder
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/troubleshooting_guide/recording-problems/unable-to-launch-recorder.aspx, /user-guide/troubleshooting_guide/recording-problems/unable-to-launch-recorder
-position: 1
-publish: false
----
-# Unable to Launch Recorder
-
-## PROBLEM
-
-Attempting to start the recorder from Test Studio's GUI results in an error. 
-
-![GUI][1]
-
-The most common errors are:
-
-- Unable to launch recorder.
-
-- Failed to launch the browser.
-
-- Connecting to recorder timed out.
-
-- Exception thrown attempting to launch Internet Explorer. Please make sure Internet Explorer is properly installed and you are able to launch it.
-
-
-## SOLUTION
-
-- **Run Visual Studio as Administrator**
-
-If you are using the VS plugin, ensure you run Visual Studio as Administrator. <a href="http://www.sevenforums.com/tutorials/11841-run-administrator.html" target="_blank">Here</a> are instructions.
-
-
-- **Reset Internet Explorer Settings**
-
-Go to **Tools > Internet Options > Advanced** tab. Click the **Reset** button and proceed with resetting IE to its default state. After, ensure you configure IE as mentioned in the next bullet point.
-
-![Reset][2]
-
-- **Configure IE**
-
-In order to optimize IE for recording and playback of tests you have to configure it as described <a href="/getting-started/configure-your-browser/internet-explorer" target="_blank">here</a>. Configuring IE correctly might resolve the issue. You can also try resetting IE to default settings before introducing the new configuration.
-
-- **Uninstall Test Studio and reinstall it**
-
-This might resolve the issue, particularly if you've previously upgraded Test Studio. Uninstalling and then installing again will not cause any data loss - all your projects and tests will still be there. You can download it from Telerik's site after logging into your account. After you download it, you'll need to activate it with your license again - this works the same way whether you're using a trial or paid license.  
-
-- **Ensure Test Studio is using x86 IE (Windows 7 or below)**
-
-If you are using a 64-bit version of Windows below Windows 8, please do the following:
-
-1.&nbsp; Load the project in Visual Studio.
-
-2.&nbsp; Right-click the test project that contains the test.
-
-3.&nbsp; Choose properties.
-
-4.&nbsp; Click the Build tab.
-
-5.&nbsp; Change the Platform Target from Any CPU to x86.
-
-6.&nbsp; Save the changes and re-test execution.
-
-
-This ensures the 64-bit version of IE is not launched (which Test Studio is not compatible with in Windows 7 or below).
-
-- **Uninstall older versions of Test Studio or Design Canvas (Test Studio's precursor)**
-
-It's possible to have different installations running in parallel. Remove all installations apart from the most recent one (i.e. the one you're planning to use).
-
-- **Temporarily disable all Internet Explorer Add-ons**
-
-Attach the recorder to an instance of IE with add-ons disabled. This is how to do it in Windows 7:
-
-  * Click *Start > All Programs > Accessories > System Tools > Internet Explorer (No Add-ons)*
-
-A new instance of instance of IE is started. Now open a Test Studio project. You'll notice there's an arrow below the Record button. Click on the arrow to open a drop-down menu with IE instances you can connect to. Choose the "Add-ons disabled" instance.
-
-![No addons][3]
-
-If recording works, then an IE add-on is the problem. Consider which IE add-ons could be causing the issue and uninstall them.
-
-- **Migrate Test Studio to a different machine**
-
-This problem is uncommon and hard to reproduce. In our experience, using a different machine to run Test Studio will almost certainly solve the issue. If this is possible for you and none of the other solutions worked - please consider it. Uninstall the current instance of Test Studio and reuse your license on a different instance.
-
-[1]: /img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig1.png
-[2]: /img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig2.png
-[3]: /img/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder/fig3.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely.md b/docs/troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely.md
index b2449557..561ee917 100644
--- a/docs/troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely.md
+++ b/docs/troubleshooting-guide/scheduling-issues-tg/project-runs-locally-not-remotely.md
@@ -3,24 +3,24 @@ title: My Project Runs Locally but Does Not Remotely
 page_title: My Project Runs Locally but Does Not Remotely
 description: "Possible issues if My Project Runs Locally but Does Not Remotely via Test Studio Scheduling setup"
 position: 1
-publish: true
+published: true
 ---
 
-# My Project Runs Locally but Does Not Remotely #
+# My Project Runs Locally but Does Not Remotely 
 
 *Apart from the communication issues that might occur in a remote setup there are few reasons related to some project specifics why a test list is successfully executed in local run but fails to be started and compiled in remote one. To easily determine whether the remote connections are successfully built create a test list with a basic web test, preferably in a sample plain project, and try to run it remotely. In case that execution is successful you might find a possible solution in the below listed scenarios.* 
 
 
-## Unstable Tests ##
+## Unstable Tests 
 
 Such a problem could be caused by an unstable test. If a test is created and ran exception free on one machine it is not given that the same test will pass on the remote machine. Basically, the reason for unstable behavior could be timing problem - the test fails when the action is performed against an element that is still not present on the page. To ensure stability of the test you could use an "<a href="/features/custom-steps/execution-delay" target="_blank">execution delay</a>" or "<a href="/features/recorder/verifications/wait" target="_blank">wait for exist</a>" steps against the element that will be targeted in the next step.
 
-## An Execution Extension is Implemented ##
+## An Execution Extension is Implemented 
 
 The <a href="/advanced-topics/coded-samples/general/execution-extensions" target="_blank">execution extension</a> library has to be available on each execution machine's *C:\Program Files (x86)\Progress\Test Studio\Bin\Plugins* folder. Using such library when executing remotely has some limitations by design though. The methods related to test lists will be executed only on the machine which hosts the scheduling server responsible for the test execution in the current setup. Those methods are *OnBeforeTestListStarted()* and *OnAfterTestListCompleted()*. The rest of the methods will be executed as expected on each execution machine.
 
 
-## The Project is in TFS Source Control and a Test List is Scheduled with "Get latest version of tests automatically from TFS" Enabled ##
+## The Project is in TFS Source Control and a Test List is Scheduled with "Get latest version of tests automatically from TFS" Enabled 
 
 Important note here is that both Scheduling and Execution servers require access to TFS - the Scheduling server loads the recent available test list from TFS to determine which tests to distribute to executors as part of the currently running job and loads these tests. On the other hand the Execution server requires the access to obtain the latest checked in test files since the local project copy may not be the recent one from TFS. 
 
@@ -28,7 +28,7 @@ An issue might appear if the required class library files for Test Studio to com
 
 **Note:** This library dependence problem is resolved in the product version 2017.2.824 or later.
 
-## One of the Tests in the Test List Has Very Long Name ##
+## One of the Tests in the Test List Has Very Long Name 
 
 This issue could appear in a local run as well. The name of a test file is interpreted along with its full path location on disk. Windows OS limits that string up to 260 symbols so if it gets longer it cannot be resolved and used. 
 
@@ -36,7 +36,7 @@ Even if a local execution is possible a remote one could fail due to that limita
 
 **Note:** If the issue is at least once encountered there might be corrupted values stored in the MongoDB storage. To get rid of these the DB collections should be maintained accordingly -  with the help of <a href=https://robomongo.org/download target="_blank">Robomongo</a> the corrupted test list could be located and deleted or alternatively the whole test list collection could be dropped. 
 
-## Getting Compilation Exceptions ##
+## Getting Compilation Exceptions 
 
 The most probable reason for the misbehavior in such scenario could be the cross test elements' definitions. Further details on the topic could be found <a     href="/troubleshooting-guide/scheduling-issues-tg/compilation-exceptions-when-execute-remotely" target="_blank">here</a> along with possible solutions.
 
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-serialization-exception.md b/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-serialization-exception.md
deleted file mode 100644
index 8cbe345e..00000000
--- a/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-serialization-exception.md
+++ /dev/null
@@ -1,41 +0,0 @@
----
-title: Run Failure With Serialization Exception
-page_title: Run failure with SerializationException
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Run failure with SerializationException
-
-In environments where Runtime version is installed only, there are "SerializationException" errors during start of remote run or after it ends and tries to report result to Storage Server:
-
-<pre>
-System.Runtime.Serialization.SerializationException was unhandled
-  Message=Type 'System.ServiceModel.Channels.ReceivedFault' in Assembly 'System.ServiceModel, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089' is not marked as serializable.
-  Source=mscorlib
-  StackTrace:
-       at System.Runtime.Serialization.FormatterServices.InternalGetSerializableMembers(RuntimeType type)
-       at System.Runtime.Serialization.FormatterServices.GetSerializableMembers(Type type, StreamingContext context)
-       at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitMemberInfo()
-       at System.Runtime.Serialization.Formatters.Binary.WriteObjectInfo.InitSerialize(Object obj, ISurrogateSelector surrogateSelector, StreamingContext context, SerObjectInfoInit serObjectInfoInit, IFormatterConverter converter, ObjectWriter objectWriter, SerializationBinder binder)
-       at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Write(WriteObjectInfo objectInfo, NameInfo memberNameInfo, NameInfo typeNameInfo)
-       at System.Runtime.Serialization.Formatters.Binary.ObjectWriter.Serialize(Object graph, Header[] inHeaders, __BinaryWriter serWriter, Boolean fCheck)
-       at System.Runtime.Serialization.Formatters.Binary.BinaryFormatter.Serialize(Stream serializationStream, Object graph, Header[] headers, Boolean fCheck)
-       at ArtOfTest.WebAii.Messaging.Process.PipeCommand.ToBinary()
-       at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.WriteCommandToPipe(PipeCommand command, PipeStream pipe, Boolean waitForDrain)
-       at ArtOfTest.WebAii.Design.Execution.RemoteRunner.OnTestComplete(ExecutionReturnValues retValues, Boolean displayResults)
-       at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.TestCompleted(IAsyncResult result)
-       at System.Runtime.Remoting.Messaging.AsyncResult.SyncProcessMessage(IMessage msg)
-       at System.Runtime.Remoting.Messaging.StackBuilderSink.AsyncProcessMessage(IMessage msg, IMessageSink replySink)
-       at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.DoAsyncCall()
-       at System.Runtime.Remoting.Proxies.AgileAsyncWorkerItem.ThreadPoolCallBack(Object o)
-       at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
-       at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean ignoreSyncCtx)
-       at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
-       at System.Threading.ThreadPoolWorkQueue.Dispatch()
-       at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()
-</pre>
-
-## SOLUTION
-
-Installing <a href="http://www.microsoft.com/en-us/download/details.aspx?id=40779" target="_blank">.NET 4.5.1</a> will fix the issue.
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500.md b/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500.md
deleted file mode 100644
index 5a217794..00000000
--- a/docs/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Run Failure with Status 500
-page_title: Run failure with status 500 (Windows XP)
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Run failure with status 500 (Windows XP Only)
-
-## PROBLEM
-
-Remote run fails with error status 500 and no test is run.
-
-## SOLUTION
-
-Disable FIPS and restart Telerik Storage Service:
-
-1.&nbps; Open administrative tools from the control panel
-
-![Administrative tools][1]
-
-2.&nbsp; **Disable System cryptography: Use FIPS compliant algorithms for encryption, hashing, and signing**
-
-![System cryptography][2]
-
-3.&nbsp; Stop Test Studio Test Runner
-
-4.&nbsp; Restart the Telerik Storage Service
-
-![Services][3]
-
-![Restart][4]
-
-[1]: /img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig1.png
-[2]: /img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig2.png
-[3]: /img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig3.png
-[4]: /img/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500/fig4.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/test-from-tfs-dont-run.md b/docs/troubleshooting-guide/scheduling-issues-tg/test-from-tfs-dont-run.md
deleted file mode 100644
index d027a95b..00000000
--- a/docs/troubleshooting-guide/scheduling-issues-tg/test-from-tfs-dont-run.md
+++ /dev/null
@@ -1,65 +0,0 @@
----
-title: Test from TFS Doesn't Run
-page_title: Test from TFS Doesn't Run
-description: "Scheduled test via Test Studio Scheduling setup and enabled to get latest from TFS connected project doesn't run on the remote machine. "
-position: 1
-publish: false
----
-# Test from TFS Doesn't Run
-
-
-## PROBLEM
-
-A scheduled test list with Get Latest from TFS enabled does not run. 
-
-## SOLUTION 1
-
-The first time a project is opened from TFS it is mapped to a local directory. A relative common scenario is to change the remote project location in TFS which will not be reflected in the local copy of the project. Thus when trying to execute a test list using 'Get Latest' option the project could not be found in the previous remote location. As a result no tests execution starts and the following exception is logged in the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-application-log" target="_blank">application log</a>:
-
-```
-[date time,Telerik.TestStudio.ExecutionManagerService.exe(6336:125),Execution] FileReaderWriterSync.ReadFileAsync() : EXCEPTION! (see below)
-     Outer Exception Type: System.IO.DirectoryNotFoundException
-     Message: Could not find a part of the path 'C:\Users\[User Name]\AppData\Local\Temp\Projects\[GUID]\TestLists\My Test List.aiilist'.
-     HRESULT: 0x80070003 (Official ID (if app.) = 2147942403, Error Bit = FAILED, Facility = FACILITY_WIN32, Code = ERROR_PATH_NOT_FOUND)
-     Call Stack:
-          at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
-          at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
-          at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share)
-          at Telerik.TestStudio.Shared.Storage.Local.FileReaderWriterSync.<ReadFileAsync>d__1.MoveNext()
-```
-
-The remote path in TFS for each source control enabled project is stored in the Settings.aiis file and could be changed only manually. The value of "RemotePath" setting in Test Studio project settings file (Settings.aiis) must be updated with the actual TFS project location. For your reference below is listed part of a sample Settings.aiis file showing the "RemotePath" setting:
-
-```
-    ...
-    "SourceControlRepository": {
-      "__type": "ArtOfTest.Common.TFSClient.TFSRepositoryInfo",
-      "__value": {
-        "RemotePath": "$/WebUI_Test_Studio/[Location]/[ProjectName]",
-        "ServerType": 1,
-        "ServerInfo": {
-          "__type": "ArtOfTest.Common.TFSClient.TFSServerInfo",
-          "__value": {
-            "ServerName": "http://tfsserver.samplecompany.it:portNumber/"
-          }
-        }
-      }
-    },
-    ...
-```
-
-
-## SOLUTION 2
-
-> Note! Since product version **R2 2017 SP1** such library dependency problem will not be present
-
--  If the execution machine does not have the necessary TFS components installed, Test Studio cannot log on to TFS to check out the test project. If this is the problem, the following error will appear in the Execution Server application log: 
-
-**Could not load file or assembly 'Microsoft.TeamFoundation.Client'**
-
-In this case you should install Team Explorer 2013 or earlier on the execution machine. It is accessible for download trough a MSDN account.
-
- To resolve this behavior, ensure that Team Foundation Client is installed on the Scheduling Server and Execution Server machines.
-
-- This behavior may also be caused by the Execution Server using a service account that cannot log on to the TFS repository. Ensure that the Execution Server is setup with the <a href="/features/scheduling-test-runs/change-service-account" target="_blank">correct service account</a>.
-
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/test-runner-stays-open.md b/docs/troubleshooting-guide/scheduling-issues-tg/test-runner-stays-open.md
index 8be9299f..695d6fff 100644
--- a/docs/troubleshooting-guide/scheduling-issues-tg/test-runner-stays-open.md
+++ b/docs/troubleshooting-guide/scheduling-issues-tg/test-runner-stays-open.md
@@ -1,7 +1,7 @@
 ---
 title: Test Runner Stays Open
 page_title: Test Runner Stays Open
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Understand why the Test Studio Test Runner process may remain open after closing Test Studio. Learn about the intended behavior, reasons for persistent processes, and how scheduled test execution affects Test Runner lifecycle."
 position: 1
 ---
 # Test Runner Stays Open
diff --git a/docs/troubleshooting-guide/scheduling-issues-tg/unscheduled-test-runs.md b/docs/troubleshooting-guide/scheduling-issues-tg/unscheduled-test-runs.md
index 17afd83b..b5f6b7a3 100644
--- a/docs/troubleshooting-guide/scheduling-issues-tg/unscheduled-test-runs.md
+++ b/docs/troubleshooting-guide/scheduling-issues-tg/unscheduled-test-runs.md
@@ -1,7 +1,7 @@
 ---
 title: Unscheduled Test Runs
 page_title: Unscheduled Test Runs
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Resolve issues with unscheduled or repeatedly running test lists in Test Studio. Learn how to clear scheduled jobs, restart the Scheduling service, and ensure accurate test execution and reporting."
 position: 1
 ---
 # Unscheduled Test Runs
diff --git a/docs/troubleshooting-guide/source-control-problems-tg/clearing-tfvc-cached-credentials-test-studio.md b/docs/troubleshooting-guide/source-control-problems-tg/clearing-tfvc-cached-credentials-test-studio.md
new file mode 100644
index 00000000..c2b7411c
--- /dev/null
+++ b/docs/troubleshooting-guide/source-control-problems-tg/clearing-tfvc-cached-credentials-test-studio.md
@@ -0,0 +1,36 @@
+---
+title: Changing Cached Credentials for TFVC Source Control in Telerik Test Studio
+description: Learn how to clear cached credentials for TFVC type source control repository associated with a Telerik Test Studio project.
+type: how-to
+page_title: Clearing TFVC Cached Credentials in Test Studio
+meta_title: Clearing TFVC Cached Credentials in Test Studio
+slug: clearing-tfvc-cached-credentials-test-studio
+tags: telerik test studio, tfvc, source control, credentials, perusersettings.json
+res_type: kb
+ticketid: 1503880
+---
+
+## Description
+
+I need to __update cached credentials for a TFVC source control repository__ associated with my Telerik Test Studio project. However, Test Studio doesn't prompt me for updated credentials even after attempting various steps like workspace removal, Credential Manager cleanup, and project disconnection.
+
+This knowledge base article also answers the following questions:
+- How to reset TFVC credentials in Telerik Test Studio?
+- How to enable credential prompts in Test Studio after changes?
+- Where are TFVC credentials stored for Test Studio projects?
+
+## Solution
+
+To refresh cached credentials for a TFVC repository, follow these steps:
+
+1. Locate the Test Studio internal settings file in the user folder: `C:\Users\<YourUsername>\AppData\Roaming\ArtOfTest`.
+2. Open the `PerUserSettings.json` file using a text editor like Notepad++.
+3. Find the setting `"TfsSkipAuth"` in the file.
+4. Change the value of `"TfsSkipAuth"` from `true` to `false`.
+5. Save the changes to the file.
+6. Delete the `WebUITestStudio.json` file in the same directory.
+7. Start Telerik Test Studio.
+8. Attempt to connect to the TFVC repository. Test Studio will prompt for credentials.
+
+
+  
diff --git a/docs/troubleshooting-guide/source-control-problems-tg/error-adding-files.md b/docs/troubleshooting-guide/source-control-problems-tg/error-adding-files.md
deleted file mode 100644
index c06ce87d..00000000
--- a/docs/troubleshooting-guide/source-control-problems-tg/error-adding-files.md
+++ /dev/null
@@ -1,38 +0,0 @@
----
-title: Error Adding Files
-page_title: Error Adding Files
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Error Adding Files
-
-## PROBLEM
-
-Test Studio attempts to check out a test from TFS every time Test Studio opens, even when that test has not been recently checked in to TFS. 
-
-An error like this appears in the application log:
-
-<pre>
-[02/04 14:33:22,Telerik.TestStudio.exe(2920:1),TeamFoundationServer] TFSServer._vcs_NonFatalError() : Non-fatal error handling TFS request: Failure instance 52192065
-  RequestType: None
-  Code: ItemExistsException
-  Severity: Error
-  Warnings: [0]
-  ComputerName:
-  IdentityName:
-  LocalItem:
-  Message: The item $/TestName.tstest already exists.
-
-  [ . . .]
-
- [02/04 14:33:22,Telerik.TestStudio.exe(2920:1),TeamFoundationServer] TFSServer.AddFiles() : Error adding files
-</pre>
-
-## SOLUTION
-
-This behavior may occur if you attempt to open a project on your local hard drive that was connected to a different TFS workspace. 
-
-
-Instead of copying the project from another machine, try <a href="/features/source-control/open-tfs-project" target="_blank">opening it from TFS</a>. This way, Test Studio can properly setup the TFS workspace on your local machine.
-
diff --git a/docs/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs.md b/docs/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs.md
deleted file mode 100644
index abacbf52..00000000
--- a/docs/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs.md
+++ /dev/null
@@ -1,31 +0,0 @@
----
-title: Error Connecting to TFS Server
-page_title: Error connecting to TFS server - Team Foundation services are not available from server [url]
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Error connecting to TFS server: Team Foundation services are not available from server [url]
-
-## PROBLEM
-
-Specific machines might fail to connect to Team Foundation Service with the error: "TF400813: Resource not available for anonymous access. Client authentication required".
-
-![Error][1]
-
-The error like this appears in the application log: 
-
-<pre>
-TFSServer.ConnectToServer() : EXCEPTION! (see below)
-     Situation: Exception connecting to TFS server
-     Outer Exception Type: Microsoft.TeamFoundation.TeamFoundationServiceUnavailableException
-     Message: Team Foundation services are not available from server [url].
-          Technical information (for administrator):
-          TF400813: Resource not available for anonymous access. Client authentication required.
-</pre>
-
-# SOLUTION
-
-You need to install <a href="https://visualstudiogallery.msdn.microsoft.com/f30e5cc7-036e-449c-a541-d522299445aa" target="_blank">Team Foundation Server 2012 Object Model Installer</a> and <a href="http://www.microsoft.com/en-us/download/details.aspx?id=29082" target="_blank">Visual Studio 2010 SP1 Team Foundation Server Compatibility GDR</a>.
-
-[1]: /img/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs/fig1.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio.md b/docs/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio.md
index eec51719..ab5e266f 100644
--- a/docs/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio.md
+++ b/docs/troubleshooting-guide/source-control-problems-tg/fix-git-source-control-lockout-issue-in-test-studio.md
@@ -8,6 +8,7 @@ slug: fix-git-source-control-lockout-issue-in-test-studio
 tags: git, source control, lockout, push commits, troubleshooting
 res_type: kb
 ---
+# Reset Git Credentials Used in Test Studio Project
 
 ## Description
 
@@ -15,14 +16,14 @@ When pushing commits to Git source control in Test Studio, you get to a state wh
 
 In the log you can see errors like this: 
 
-```txt
+````txt
 SourceControlFactory.GetControlInstance() : EXCEPTION! (see below)
      Situation: Error loading Git source control plugin.
      ...
 Inner Exception Type: LibGit2Sharp.LibGit2SharpException
      Message: too many redirects or authentication replaysInner Exception Type: LibGit2Sharp.LibGit2SharpException
      Message: too many redirects or authentication replays
-```
+````
 
 ## Solution
 To fix the Git source control lockout issue, follow these steps:
diff --git a/docs/troubleshooting-guide/source-control-problems-tg/unable-to-load-sc-plugin.md b/docs/troubleshooting-guide/source-control-problems-tg/unable-to-load-sc-plugin.md
deleted file mode 100644
index 0daf43db..00000000
--- a/docs/troubleshooting-guide/source-control-problems-tg/unable-to-load-sc-plugin.md
+++ /dev/null
@@ -1,25 +0,0 @@
----
-title: Unable to Load SC Plugin
-page_title: Unable to Load Source Control Plugin
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-
-# Unable to Load Source Control Plugin
-
-## PROBLEM
-
-You receive the following error when you attempt to integrate TFS in Test Studio Standalone version and you do not have Visual Studio installed:
-
-![Plugin Error][1]
-
-## SOLUTION
-
-Install the appropriate version of <a href="http://www.microsoft.com/en-us/download/details.aspx?id=40776" target="_blank">Visual Studio Team Explorer</a>. This is the client SKU that allows you to access the TFS functionality.
-
-> Even you have or you would install Visual Studio 2015 it does not include VS Team Explorer. In order to use our TFS integration, you need to install explicitly Team Explorer.
-
-[1]: /img/troubleshooting-guide/installation-problems-tg/unable-to-load-sc-plugin/fig1.png
-
-
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/artoftestconnector-error.md b/docs/troubleshooting-guide/test-execution-problems-tg/artoftestconnector-error.md
index 19ad182e..150bef7f 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/artoftestconnector-error.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/artoftestconnector-error.md
@@ -10,10 +10,10 @@ position: 1
 
 I need to automate a 64-bit WPF application. When I try to configure a WPF test in Test Studio or run an existing one, I get a message that a dll is missing. If I check the listed directory I can see the file listed in it, but no test starts for the automated WPF application.
 
-```
+````
 There was a problem starting C:\Program Files (x86)\Progress\Test Studio\Bin\ArtOfTest.Connector_64.dll. 
 The specified module could not be found.
-```
+````
 
 ## Solution
 
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime.md b/docs/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime.md
index 5b2db1d3..a8e29f24 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime.md
@@ -1,8 +1,7 @@
 ---
 title: Built by Newer Runtime
 page_title: This Assembly Is Built by a Runtime Newer than the Currently Loaded Runtime
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/troubleshooting_guide/test-execution-problems/assembly-built-by-newer-runtime.aspx, /user-guide/troubleshooting_guide/test-execution-problems/assembly-built-by-newer-runtime
+description: "Learn how to resolve the 'assembly built by a newer runtime' error in Test Studio. This article explains the cause, provides troubleshooting steps, and details the correct way to run ArtOfTest.Runner.exe for successful test execution."
 position: 1
 ---
 # This Assembly Is Built by a Runtime Newer than the Currently Loaded Runtime
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execute-test.md b/docs/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execute-test.md
deleted file mode 100644
index e21bca74..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execute-test.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: Cannot Execute Test
-page_title: Tests Will Not Run in Google Chrome
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-previous_url: /user-guide/troubleshooting_guide/test-execution-problems/chrome/cannot-execute-in-chrome.aspx, /user-guide/troubleshooting_guide/test-execution-problems/chrome/cannot-execute-in-chrome
-position: 1
-publish: false
----
-# Tests Will Not Run in Google Chrome
-
-## PROBLEM
-
-When executing a test in Chrome, the browser opens and navigates to http://localhost:XXXX/WebUI?XXXXXX, but test execution does not continue.
-
-## SOLUTION
-
-Please refer to <a href="/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome" target="_blank">this article</a> for more information.
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig1.png
-[2]: /img/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execite-test/fig2.png
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/dialog-handling-fails.md b/docs/troubleshooting-guide/test-execution-problems-tg/dialog-handling-fails.md
deleted file mode 100644
index 51fef213..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/dialog-handling-fails.md
+++ /dev/null
@@ -1,16 +0,0 @@
----
-title: Dialog Handling Fails
-page_title: Dialog Handling Fails
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Dialog Handling Fails
-
-## PROBLEM
-
-In multiple browsers, dialog handling fails to enter dialog field text or click dialog buttons accurately.
-
-## SOLUTION
-
-Conflicts with automatic form completion software can cause this behavior in dialog handler execution. Specifically, <a href="http://www.roboform.com/" target="_blank">RoboForm</a> can conflict with Test Studio dialog handling in this manner. Uninstalling RoboForm can resolve this behavior.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied.md b/docs/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied.md
index 6060ec28..78ca4a1b 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied.md
@@ -12,7 +12,7 @@ position: 1
 A web test with 'Handle Download dialog' or 'Handle Upload dialog' step fails with the following error message in the execution log. 
 A WPF test with 'Handle OpenFile dialog' or 'Handle SaveFile dialog' step fails with the following error message in the execution log. 
 
-```txt
+````txt
 Failure Information: 
 
 The current user does not have access to this folder C:\workingStation\temp\noPermissionsFolder\myw3schoolsimage.jpg. 
@@ -27,7 +27,7 @@ System.UnauthorizedAccessException: The current user does not have access to thi
 You can use the %USERPROFILE%\Downloads\myw3schoolsimage.jpg folder instead or grant access to the folder on all executing machines. 
 
 For more information: https://docs.telerik.com/teststudio/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied
-```
+````
 
 ![Failure details for upload or download dialog not handled](/img/troubleshooting-guide/test-execution-problems-tg/download-dialog-access-denied/failure-message.png)
 
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery-event-not-triggered.md b/docs/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery-event-not-triggered.md
index ba3b16b9..6bd8f058 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery-event-not-triggered.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/drop-down-menu-jquery-event-not-triggered.md
@@ -1,7 +1,7 @@
 ---
 title: Drop-down menu jQuery Event Not Triggered
 page_title: Drop-down menu jQuery Event Not Triggered
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Find solutions for jQuery events not triggering on HTML drop-down menus during Test Studio test execution. Learn about the TriggerjQueryEvent property and how to ensure automated tests handle drop-down interactions correctly."
 position: 1
 ---
 # Drop-down menu jQuery Event Not Triggered
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed.md b/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed.md
deleted file mode 100644
index 3b287b16..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed.md
+++ /dev/null
@@ -1,81 +0,0 @@
----
-title: Extension Not Installed
-page_title: Firefox Extension Not Installed
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Firefox Extension Not Installed
-
-## PROBLEM
-
-I cannot execute a test in Firefox. I receive the following error in the test log:
-
-*System.TimeoutException: Wait for condition has timed out<br>
-   at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo)<br>
-   at ArtOfTest.Common.WaitSync.For\[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)<br>
-   at ArtOfTest.Common.WaitSync.For\[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)<br>
-   at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)<br>
-   at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)<br>
-   at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)<br>
-   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)<br>
-   at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)*
-
-And the following displays in the Firefox URL field:
-
-*about:blank?!!AOT2.0!Pipe.ArtOfTest.WebAii.BrowserProvisioner_##########*
-
-## SOLUTION
-
-**Test Studio 2017 R3 (v. 2017.3.1010) And Later**
-
-There is a single extension combining the recording and execution which could be downloaded from the Mozzila Extension Page. For your convenience here is a direct link to the <a href="https://addons.mozilla.org/en-US/firefox/addon/progress-test-studio-extension/" target="_blank">**Progress Test Studio Extension**</a>.
-
->If you face any troubles when installing or enabling the extension please expand the **Extension Install Procedure** section <a href="/getting-started/configure-your-browser/firefox#Extension_Install" target="_blank">in this article</a>.
-
-**Test Studio 2017 R2 SP1(v. 2017.2.824) And Earlier**
-
-1.&nbsp; Check the Progress Testing Framework extension in Add-ons Manager. Click **Tools > Add-ons** (or Ctrl+Shift+A). Ensure __Progress Test Studio Firefox Execution__ is enabled. If they are not enabled please check <a href="/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff" target="_blank">this article</a>.
-
-![Add-ons][1]
-
-2.&nbsp; If that is correct and it still doesn't work, there may be a conflicting Add-on. Try disabling all non-Telerik Add-ons and try again. If it succeeds, re-enable those Add-ons one at a time until you identify the culprit.
-
-> Restart Firefox after making changes in the Add-ons Manager.
-
-3.&nbsp; If the issue persist, try to reinstall Firefox first and then Test Studio.
-
-4.&nbsp; As a last resort you can perform manual installation of the extensions by following these steps:
-
-- Verify that in the *C:\Program Files (x86)\Progress\Test Studio\Browser Extensions\Firefox4+* folder you can see the following files:
-
-![FF4][2]
-
-- Open the Windows registry.
-
-- Navigate to the following path in the registry:
-
- - For 64bit version: **HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Mozilla\Firefox\Extensions\**
-
- - For 32bit version: **HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Firefox\Extensions\**
-
-- You need to have the registry shown in the following screenshot:
-
-![Edit String][3]
-
-- If it doesn't look like the one in the screenshot, you need to create a new 'String Value' with:
-
-Key: ** webaii21_FF4@telerik.com**  
-Value: **C:\Program Files\Telerik\Test Studio\Browser Extensions\Firefox4+\**
-
--  Once this is done, open Firefox and go to your Firefox Extensions. Now you should be able to see the "Telerik Testing Framework - Firefox Http Client" extension. Simply enable it and you should be good to go.
-
-> If you're using Symantec Antivirus Protection, its <a href="http://www.symantec.com/business/support/index?page=content&id=TECH95347" target="_blank">Intrusion Prevention System</a> may be interfering with the Test Studio Firefox extension.
-> 
-- Disable Symantec Intrusion Prevention.
-- Load Firefox and enable the Telerik Testing Framework extension in Add-ons Manager.
-
-
-[1]: /img/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff/fig1.jpg
-[2]: /img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig2.png
-[3]: /img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed/fig3.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy.md b/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy.md
deleted file mode 100644
index a03e4813..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy.md
+++ /dev/null
@@ -1,64 +0,0 @@
----
-title: HTTPS with Custom Proxy
-page_title: Firefox HTTPS Error with Custom Proxy
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Firefox HTTPS Error with Custom Proxy
-
-## PROBLEM
-
-I receive the following error when executing a test against an HTTPS site using Firefox configured with a custom proxy:
-
-*This Connection is Untrusted.<br>
-You have asked Firefox to connect securely to www.domain.com, but we can't confirm that your connection is secure.*
-
-
-![Untrusted][1]
-
-## SOLUTION
-
-1.&nbsp; Register the certificate for HTTPS Connection.
-
-a. Follow the instructions <a href="/knowledge-base/project-configuration-kb/register-certificate" target="_blank">here</a>.
-
-2.&nbsp; Export the Fiddler Root Certificate.
-
- a. Open <a href="http://www.telerik.com/download/fiddler" target="_blank">Fiddler</a>.
-
- b. Click **Tools > Fiddler Options**.
- 
- c. Select the **HTTPS** tab.
-
- d. Click the **Export Root Certificate to Desktop** button.
-
-![Export][2]
-
-3.&nbsp; Configure Firefox to trust the Fiddler Root Certificate.
-
- a. Open Firefox.
-
- b. Click **Tools > Options**.
-
- c. Click **Advanced**.
-
- d. Click the **Encryption** tab.
-
- e. Click **View Certificates**.
-
- f. Click the **Authorities** tab.
-
- g. Click **Import**.
-
- h. Select *FiddlerRoot.cer* from the Desktop.
-
- i. Check **Trust this CA to identify websites**.
-
-![Download Cert][3]
-
- j. Click **OK**.
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig1.png
-[2]: /img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig2.png
-[3]: /img/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy/fig3.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/mcafee-siteadvisor.md b/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/mcafee-siteadvisor.md
deleted file mode 100644
index 99cbb198..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/firefox-tg/mcafee-siteadvisor.md
+++ /dev/null
@@ -1,30 +0,0 @@
----
-title: McAfee SiteAdvisor blocks execution 
-page_title: McAfee SiteAdvisor blocks execution
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# McAfee SiteAdvisor blocks execution
-
-## PROBLEM
-
-I cannot execute a test in Firefox. I receive the following error in the test log:
-
-*Outer Exception Type: System.TimeoutException
-     Message: Wait for condition has timed out
-     HRESULT: 0x80131505 (Official ID (if app.) = COR_E_TIMEOUT, Error Bit = FAILED, Facility = FACILITY_URT, Code = 5381)
-     Call Stack:
-          at ArtOfTest.Common.WaitSync.CheckResult(WaitSync wait, String extraExceptionInfo, Object target)
-          at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout, WaitResultType errorResultType)
-          at ArtOfTest.Common.WaitSync.For[T](Predicate`1 predicate, T target, Boolean invertCondition, Int32 timeout)
-          at ArtOfTest.WebAii.Core.Manager.WaitForBrowserToConnect(Int32 browserIndexToWaitFor)
-          at ArtOfTest.WebAii.Core.Manager.LaunchNewBrowser(BrowserType browserToLaunch, Boolean waitForBrowserToConnect, ProcessWindowStyle windowStyle, String arguments)
-          at ArtOfTest.WebAii.Design.Execution.ExecutionEngine.InitializeWeb(ExecutionEngineCreateParams initParams)
-          at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.CreateAndInitializeEngine(Test test, ExecutionEngineCreateParams cp)
-          at ArtOfTest.WebAii.Design.Execution.TestExecuteProxy.ExecuteTest(ExecuteTestCommand command)*
-
-## SOLUTION
-
-In some cases **McAfee SiteAdvisor** could block the test execution in **FireFox**. Disable it or uninstall it in order to prove whether the antivirus software causes the execution problems.
-
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing.md b/docs/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing.md
index 737845af..4e090e95 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/invoke-blind-keyboard-typing.md
@@ -18,21 +18,21 @@ The "blind" typing actions itself could be implemented in a <a href="/features/c
 
 Here's a line of sample code that types "*This is a sample*":
 
-```C#
+````C#
     Manager.Desktop.KeyBoard.TypeText("This is a sample", 200);
-```
-```VB
+````
+````VB
     Manager.Desktop.KeyBoard.TypeText("This is a sample", 200)
-```
+````
 
 Here's a line of sample code that presses the ENTER key: 
 
-```C#
+````C#
     Manager.Desktop.KeyBoard.KeyPress(Keys.Enter, 200);
-```
-```VB
+````
+````VB
     Manager.Desktop.KeyBoard.KeyPress(Keys.Enter, 200)
-```
+````
 
 
 **Manager.Desktop.KeyBoard** contains many additional methods you might also find useful:
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/missing-api-assembly-files.md b/docs/troubleshooting-guide/test-execution-problems-tg/missing-api-assembly-files.md
index e86cc941..f2711cb8 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/missing-api-assembly-files.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/missing-api-assembly-files.md
@@ -10,9 +10,9 @@ position: 1
 
 If you have an embedded <a href="/features/execute-apitest/add-api-test-as-step" target="_blank">API test as step</a>, which has a code behind file, you might encounter similar error after updating Test Studio:
 
-```
+````
 Could not load file or assembly 'Telerik.ApiTesting.Framework, Version=xxxx.x.xxx.xxxx, Culture=neutral, PublicKeyToken=xxx' or one of its dependencies. The system cannot find the file specified.
-```
+````
 
 This means that the API embeded project was built with the previous version of APITesting Framework and the *dll* files were generated with that version. 
 
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/pages-not-defined.md b/docs/troubleshooting-guide/test-execution-problems-tg/pages-not-defined.md
index 9da5d9fe..6a44b18e 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/pages-not-defined.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/pages-not-defined.md
@@ -19,7 +19,7 @@ The coded files need to use the namespace as the one set on project level in the
 
 The code-behind file for a test in project with name TestProj2 looks like this: 
 
-```C#
+````C#
 
 // Starting with a list of using statements which may vary 
 // and therefore are not listed here
@@ -59,7 +59,7 @@ namespace TestProj2 // This is the namespace set in the project settings
 	}
 
 }
-```
+````
 
 ## Solution
 
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed.md b/docs/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed.md
deleted file mode 100644
index 422f9a2e..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed.md
+++ /dev/null
@@ -1,47 +0,0 @@
----
-title: Extension Not Installed
-page_title: Safari Extension Not Installed
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Safari Extension Not Installed
-
-## PROBLEM
-
-I cannot execute a test in Safari. I receive the following message:
-
-*Safari automation extension has not yet been installed. Please click 'Install' when
-prompted to install the WebUI automation extension and close the Safari window
-once the extension has been installed.*
-
-![Not installed][1]
-
-## SOLUTION
-
-If things go as expected, clicking OK on the above message should load Safari and display the prompt below. Click **Install** to proceed. Once finished, your test should execute in Safari. 
-
-![Install][2]
-
-If the test does not execute, or you never receive the second prompt, install the Safari extension manually:
-
-1.&nbsp; Locate the following file:
-
- - **C:\Program Files (x86)\Progress\Test Studio\Browser Extensions\Safari\WebUI.safariextz**
-
-2.&nbsp; Right click the file and select **Open with**.
-
-![Open With][3]
-
- 
-
-3.&nbsp; Open the file with Safari to install the extension. 
-
-![Safari][4]
-
-4.&nbsp; Retest Safari execution in Test Studio.
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig1.png
-[2]: /img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig2.png
-[3]: /img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig3.png
-[4]: /img/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed/fig4.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/find-element-timeout.md b/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/find-element-timeout.md
deleted file mode 100644
index 89040915..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/find-element-timeout.md
+++ /dev/null
@@ -1,18 +0,0 @@
----
-title: Find Element Timeout
-page_title: Find Element Timeout
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Find Element Timeout
-
-
-## Problem
-
-When navigating to a Silverlight application, the navigate step succeeds, but while the Silverlight app is loading, the second step fails. The error log displays an 'Unable to locate element' error for the target element.
-
-## SOLUTION
-
-This issue is caused by the Silverlight plugin not loading before the second step navigates. The solution is to enable the 'Use StepWaitOnElementsTimeout' test step property for the failing step after the navigate, and increase the 'WaitOnElementsTimeout' test step property to allow the plugin to load (for example, to 30000 ms). 
-
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/target-host-error.md b/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/target-host-error.md
deleted file mode 100644
index f3c85328..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/target-host-error.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Target Host Error
-page_title: Unable to Find the Target Host
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Unable to Find the Target Host
-
-## PROBLEM
-
-I'm trying to run a Silverlight test from Quick Execution, as part of a test list, or through the Telerik Testing Framework. The test fails with the Unable to find the target host error at the initial stages.
-
-## SOLUTION
-
-This is likely related to the test settings. This errors frequently shows up when you add a coded step that performs actions against Silverlight elements in your test. There are a few things you need to check:
-
-- If you're running the test from Quick Execution in the Standalone version, go to the Project tab and check whether the test's *SilverlightEnabled* <a href="/features/test-maintenance/test-properties-standalone" target="_blank">Test Property</a> is set to True.
-
-- If you're running the test as part of a test list (applicable for the Standalone version and VS plugin), check whether the SilverlightEnabled property is set to True on the Web tab of <a href="/getting-started/test-execution/test-list-settings" target="_blank">Test List Settings</a>.
-
-- Increase the Silverlight Connect Timeout in Project Settings > <a href="/features/project-settings/recording-options" target="_blank">Recording Options</a>.
-
-- If running the test as part of a test list, increase the Silverlight Connect Timeout on the Web tab of <a href="/getting-started/test-execution/test-list-settings" target="_blank">Test List Settings</a>..
-
-- If you're using the Telerik Testing Framework, ensure your test includes the code below as the first line of your test. This is seen in <a href="/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation" target="_blank">this example</a>.
-
-	
-
-	Settings.Current.Web.EnableSilverlight = true;
-
-> These solutions apply only for execution-related problems with Silverlight (i.e. you were able to record a test successfully). If you're unable to connect the recorder to your Silverlight application to record a test, see <a href="/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect" target="_blank">this article</a>.
-
-<br>
-> If you receive this error for a non-Silverlight test that contains frames, see the bottom of <a href="/getting-started/test-recording/Frames" target="_blank">this page</a>.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match.md b/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match.md
deleted file mode 100644
index 5d3d37d8..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Window Partial Match
-page_title: How to Indicate a Partial Match for WPF Window Name
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# How to Indicate a Partial Match for WPF Window Name
-
-## PROBLEM
-
-I have a dynamic window title in my application. Elements in the window cannot be located during execution because the title differs from when it was recorded.
-
-## SOLUTION
-
-Edit the **Caption** property for the Window node in the Elements Explorer. Use a leading tilde (~) character to indicate a partial match and remove the dynamic portion.
-
-<table id="no-table">
-<tr>
-<td>![fig1][1]<br>![fig2][2]<br>**Original Window Caption**</td>
-<td>![fig3][3]<br>![fig4][4]<br>**Edited for Partial Match**</td>
-</tr>
-<table>
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig1.png
-[2]: /img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig2.png
-[3]: /img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig3.png
-[4]: /img/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match/fig4.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/single-coded-step.md b/docs/troubleshooting-guide/test-execution-problems-tg/single-coded-step.md
index 78bdfbb2..df4961d0 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/single-coded-step.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/single-coded-step.md
@@ -21,10 +21,10 @@ This happens because a single coded step is not set to automatically call refres
 
 Add a statement to refresh the DOM tree as first row in the coded step.
 
-```C# 
+````C# 
 // Use Manager.ActiveBrowser for a web application 
 Manager.ActiveBrowser.RefreshDomTree();
 
 // Use Manager.ActiveApplication for a wpf application 
 Manager.ActiveApplication.MainWindow.RefreshVisualTrees();
-```
+````
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md b/docs/troubleshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md
index 83e099e4..d05c9ae8 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/steps-not-shown-ts-versions-diff.md
@@ -1,7 +1,7 @@
 ---
 title: Test Steps Not Showing in Step Panel
 page_title: Test Steps Not Showing in Step Panel
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Resolve the issue of missing test steps in the step panel when opening projects in an older version of Test Studio. Learn why this happens and how to update your installation for full compatibility."
 position: 1
 ---
 # Test Steps Not Showing in Step Panel
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/test-list-does-not-complete.md b/docs/troubleshooting-guide/test-execution-problems-tg/test-list-does-not-complete.md
index 3634c464..9002adfe 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/test-list-does-not-complete.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/test-list-does-not-complete.md
@@ -1,7 +1,7 @@
 ---
 title: Test List Does Not Complete
 page_title: Test List Does Not Complete
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Troubleshoot issues where a test list execution does not complete in Test Studio. Learn about common causes, such as the RecycleBrowser setting, and how to resolve incomplete test runs for reliable automation."
 position: 1
 ---
 # Test List Does Not Complete
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/tests-not-executed-in-chrome-or-firefox.md b/docs/troubleshooting-guide/test-execution-problems-tg/tests-not-executed-in-chrome-or-firefox.md
deleted file mode 100644
index 78ef069d..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/tests-not-executed-in-chrome-or-firefox.md
+++ /dev/null
@@ -1,24 +0,0 @@
----
-title: Tests Not Executed in Chrome or Firefox
-page_title: Tests Not Executed in Chrome or Firefox
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
----
-# Tests Not Executed in Chrome or Firefox
-
-## Problem
-
-Test Studio <a href="/getting-started/configure-your-browser/Chrome" target="_blank">Chrome</a> or <a href="/getting-started/configure-your-browser/Firefox" target="_blank">Firefox</a> browser latest extensions have been installed and browsers properly <a href="/features/project-settings/browsers" target="_blank">calibrated</a>. But it's still not possible to execute/record a test using those browsers and the following exception appears in the <a href="/troubleshooting-guide/troubleshooting-tools-tg/using-the-execution-log" target="_blank">execution log</a>.
-
-```
-[Date, Time] - Error attempting to exit runner. Error: System.IO.IOException: Pipe is broken.
-   at System.IO.Pipes.PipeStream.WinIOError(Int32 errorCode)
-   at System.IO.Pipes.PipeStream.WriteCore(Byte[] buffer, Int32 offset, Int32 count)
-   at System.IO.Pipes.PipeStream.Write(Byte[] buffer, Int32 offset, Int32 count)
-   at ArtOfTest.WebAii.Messaging.Process.PipeCommunication.WriteCommandToPipe(PipeCommand command, PipeStream pipe, Boolean waitForDrain)
-   at ArtOfTest.WebAii.Design.Execution.RunnerController.Exit()
-```
-
-## Solution
-
-The exception indicates that the communication between the product and the browser extension has been broken and no further test recording or execution is possible. Such problem is most probably caused by an active firewall or anti-virus software on the testing machine. Try to stop or deactivate that software to resolve the problem.
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-add-reference.md b/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-add-reference.md
index 6e9aa7b2..43992242 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-add-reference.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-add-reference.md
@@ -1,7 +1,7 @@
 ---
 title: Unable to Add Reference
 page_title: Unable to Add Reference
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to resolve errors when adding assembly references in Test Studio projects. This article explains common causes, such as referencing DLLs in hidden folders, and provides steps to fix reference and compilation issues."
 position: 1
 ---
 # Unable to Add Reference
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element.md b/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element.md
index b70ffca2..1af9a033 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-locate-element.md
@@ -88,7 +88,7 @@ Start by using the same steps to determine if the test is on the right page. Loo
 
 Let's take the second failure list above as an example. The find logic is saying find an element that has the id "*rpbNavigator_i3_rtvROOFER*" then find the third \<li> element (because it's zero based) underneath it. Here's what the DOM looked like when the test failed:
 
-```
+````
 <div id="rpbNavigator_i3_rtvROOFER" >
 	<div id="rpbNavigator_i3_rtvROOFER_RadTreeViewContextMenuROOFER" >
 		<div id="rpbNavigator_i3_rtvROOFER_RadTreeViewContextMenuROOFER_detached" >
@@ -99,7 +99,7 @@ Let's take the second failure list above as an example. The find logic is saying
 	</div>
 	<input id="rpbNavigator_i3_rtvROOFER_ClientState" >
 </div>
-```
+````
 
 Notice that there are no \<li> elements contained in the unordered list (the \<ul> element). Here's a case where the dropdown combobox doesn't get populated until you actually open the combobox. Opening the combobox initiates an AJAX postback which returns the list of items to populate in the combobox. The solution was to add a test step to open the combobox before our failing step.
 
@@ -113,7 +113,7 @@ If you use XPath or TagIndex to locate the element and the structure of the page
 
 Make sure the name/IDF didn't change after recording the test. You can compare the find expression for the particular element and the DOM tree of the application:
 
-```
+````
 <html>
 <head>
 </head>
@@ -123,7 +123,7 @@ Make sure the name/IDF didn't change after recording the test. You can compare t
     </div>
 </body>
 </html>
-```
+````
 
 *DOM tree of our application which shows us the ID of the DIV.*
 
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data.md b/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data.md
deleted file mode 100644
index 8b7c9a19..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data.md
+++ /dev/null
@@ -1,28 +0,0 @@
----
-title: Unable to Show Data Tables In Excel Data Source
-page_title: Unable to Show Data Data Tables in Excel Data Source
-description: "Test Studio data driven test throws an error Test Studio data bound test cannot bind excel file cannot select the sheets from the bound excel file error: The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine"
-position: 1
-publish: false
----
-# Unable to Show Data Tables in Excel Data Source
-
-> The scenario is applicable for Test Studio versions before release 2024 Q1 (2024.1.220).
-
-If running a data driven test on remote machine you get your test failed and the following exception could be found in the log:
-
-```
-The 'Microsoft.ACE.OLEDB.12.0' provider is not registered on the local machine
-```
-
-> This could happen on machines with no Microsoft Office or Data Connectivity Component installed or if the Microsoft Office package is 64-bit version.
-
-Another option to face the same error in the application log is to bind an Excel file to a test, and try to select a sheet - the list is empty. 
-
-![No sheets][1]
-
-## Solution
-
-Download and install the **32-bit version** of <a href="https://www.microsoft.com/en-us/download/details.aspx?id=13255" target="_blank">Microsoft Access Database Engine 2010</a>. It will install the required drivers for communication between Test Studio and the Microsoft Office files for all of the above cases.
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data/fig1.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out.md b/docs/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out.md
deleted file mode 100644
index 340eee24..00000000
--- a/docs/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out.md
+++ /dev/null
@@ -1,33 +0,0 @@
----
-title: Wait for Condition Timed Out
-page_title: Wait for Condition Timed Out
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Wait for Condition Timed Out
-
-## PROBLEM
-
-You may encounter the *Wait for condition* has timed out error after your test performs a click action.
-
-__Failure Information:__
-
-```
-Wait for condition has timed out
-InnerException:
-System.TimeoutException: Wait for condition has timed out
-at ArtOfTest.WebAii.Core.Browser.WaitUntilReady()
-```
-
-This indicates the test timed out waiting for the browser to return to a "ready" state after the click command was sent to it.
-
-## SOLUTION
-
-This can be often overcome by setting the applicable step's **SimulateRealClick** property to True. Find it under the Behavior heading in the Properties pane.
-
-![SimulaterRealClick][1]
-
-When set to **True**, Test Studio will not wait for the browser to return to a "ready" state. Also, it will not automatically refresh its local copy of the DOM. Instead it sends the click command to the browser (as a live user would) and immediately moves on to the next test step.
-
-[1]: /img/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out/fig1.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/why-find-by-content.md b/docs/troubleshooting-guide/test-execution-problems-tg/why-find-by-content.md
index def4bb3f..8b779243 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/why-find-by-content.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/why-find-by-content.md
@@ -1,7 +1,7 @@
 ---
 title: Why Find.By.Content May Return Null
 page_title: Why Find.By.Content May Return Null
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Understand why Find.ByContent may return null in Test Studio. This article explains common pitfalls, error scenarios, and provides solutions for locating elements by content in automated tests."
 position: 1
 ---
 # Why Find.By.Content May Return Null
@@ -24,27 +24,27 @@ If we run the test against this html source:
 
 The following find expression will return NullReferenceException:
 
-```C#
+````C#
 HtmlAnchor elementName = ActiveBrowser.Find.ByContent<HtmlAnchor>("Test");
-```
-```VB
+````
+````VB
 Dim elementName As HtmlAnchor = ActiveBrowser.Find.ByContent(Of HtmlAnchor)("Test")
-```
+````
 
 The solution is to use either the correct element type:
 
-```C#
+````C#
 HtmlDiv elementName = ActiveBrowser.Find.ByContent<HtmlDiv>("Test");
-```
-```VB
+````
+````VB
 Dim elementName As HtmlDiv = ActiveBrowser.Find.ByContent(Of HtmlDiv)("Test")
-```
+````
 
 or call the method without specifying element type: 
 
-```C#
+````C#
  Element a = ActiveBrowser.Find.ByContent("Test");
-```
-```VB
+````
+````VB
 Dim a As Element = ActiveBrowser.Find.ByContent("Test")
-```
\ No newline at end of file
+````
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/window-partial-match.md b/docs/troubleshooting-guide/test-execution-problems-tg/window-partial-match.md
new file mode 100644
index 00000000..395a9c2b
--- /dev/null
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/window-partial-match.md
@@ -0,0 +1,31 @@
+---
+title: Window Partial Match
+page_title: How to Indicate a Partial Match for WPF Window Name
+description: "Learn how to handle dynamic WPF window titles in Test Studio by using partial match techniques. This article explains how to edit the Caption property for reliable element identification during automated test execution."
+position: 1
+---
+# How to Indicate a Partial Match for WPF Window Name
+
+## PROBLEM
+
+I have a dynamic window title in my application. Elements in the window cannot be located during execution because the title differs from when it was recorded.
+
+## SOLUTION
+
+Edit the **Caption** property for the Window node in the Elements Explorer. Use a leading tilde (~) character to indicate a partial match and remove the dynamic portion.
+
+<table id="no-table" style="border:none;">
+<tr style="text-align: center; background-color: transparent; border:none;">
+<td>
+
+![fig1][1]<br>![fig2][2]<br>**Original Window Caption**</td>
+<td>
+
+![fig3][3]<br>![fig4][4]<br>**Edited for Partial Match**</td>
+</tr>
+</table>
+
+[1]: /img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig1.png
+[2]: /img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig2.png
+[3]: /img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig3.png
+[4]: /img/troubleshooting-guide/test-execution-problems-tg/wpf-tg/window-partial-match/fig4.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog.md b/docs/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog.md
index bd419e34..9e771a24 100644
--- a/docs/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog.md
+++ b/docs/troubleshooting-guide/test-execution-problems-tg/windows-security-dialog.md
@@ -25,7 +25,7 @@ If the tested application uses similar dialog and fails to be automated the Wind
 For example the username and password might be stored and only the Ok button needs to be hit. If it is the active one and pressing Enter will confirm the dialog then only this part of the code is required after the URL is entered.  
 
 
-```C#
+````C#
         [CodedStep(@"New Coded Step")]
         public void WindowsSecurityDialog_CodedStep()
 		{
@@ -42,8 +42,8 @@ For example the username and password might be stored and only the Ok button nee
 			Manager.Desktop.KeyBoard.KeyPress(Keys.Tab); //switch the focus to the OK button
 			Manager.Desktop.KeyBoard.KeyPress(Keys.Enter); //confirm the OK button 
 		}
-```
-```VB
+````
+````VB
 <CodedStep("New Coded Step")> _
 	Public Sub WindowsSecurityDialog_CodedStep()
 		Manager.Desktop.KeyBoard.KeyPress(Keys.F6) 'pressing F6 makes the address bar of each browser active
@@ -65,7 +65,7 @@ For example the username and password might be stored and only the Ok button nee
 		Manager.Desktop.KeyBoard.KeyPress(Keys.Enter)	'confirm the OK button 
 
 	End Sub
-```
+````
 
 >To be able to use the code above the assembly **System.Windows.Forms.dll** needs to be <a href="/features/coded-steps/add-assembly-reference" target="_blank">referenced</a> in the Project settings.<br>
 
diff --git a/docs/troubleshooting-guide/visual-studio-tg/cannot-add-open-test.md b/docs/troubleshooting-guide/visual-studio-tg/cannot-add-open-test.md
index 9fa9292b..c321a89a 100644
--- a/docs/troubleshooting-guide/visual-studio-tg/cannot-add-open-test.md
+++ b/docs/troubleshooting-guide/visual-studio-tg/cannot-add-open-test.md
@@ -1,7 +1,7 @@
 ---
 title: Cannot Add Open Test
 page_title: Cannot Add Open Test
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to resolve issues when adding or opening tests in Visual Studio with the Test Studio plugin. This article covers common error messages, troubleshooting steps, and best practices for managing test files and projects."
 position: 1
 ---
 # Cannot Add Open Test
diff --git a/docs/troubleshooting-guide/visual-studio-tg/cannot-build-project.md b/docs/troubleshooting-guide/visual-studio-tg/cannot-build-project.md
deleted file mode 100644
index 69634c48..00000000
--- a/docs/troubleshooting-guide/visual-studio-tg/cannot-build-project.md
+++ /dev/null
@@ -1,37 +0,0 @@
----
-title: Cannot Build Project After version 2015.3.1202 
-page_title: Cannot Build Project After version 2015.3.1202 
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# Cannot build projects in Visual Studio after upgrading to 2015.3.1202 version and higher
-
-## PROBLEM
-
- The problem occurs after upgrading the <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> Visual Studio plugin to 2015.3.1202 version. In Visual Studio your test projects will no longer build. 
-
-![Erros][1]
-
-# SOLUTION
-
-As of version **2015.3.1202** Test Studio has migrated to **.NET 4.5**. If your test project was created in .NET 4.0 the above issue will occur after upgrading the Test Studio Visual Studio plugin to version 2015.3.1202 and above.
-
-You have to upgrade your Visual Studio projects to **.NET Framework 4.5** as the target framework from the properties of the Test Project.
-
-1.&nbsp; Right click on the test project and click **Properties**.
-
-![Properties][2]
-
-2.&nbsp; Under the Application tab select **.NET Framework 4.5** as the target framework.
-
-![Target framework][3]
-
-3.&nbsp; Confirm the target framework change. 
-
-![Confirm the changes][4]
-
-[1]: /img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig1.png
-[2]: /img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig2.png
-[3]: /img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig3.png
-[4]: /img/troubleshooting-guide/visual-studio-tg/cannot-build-project/fig4.png
diff --git a/docs/troubleshooting-guide/visual-studio-tg/coded-steps-disappear-vs.md b/docs/troubleshooting-guide/visual-studio-tg/coded-steps-disappear-vs.md
index 93a99b72..91c963a6 100644
--- a/docs/troubleshooting-guide/visual-studio-tg/coded-steps-disappear-vs.md
+++ b/docs/troubleshooting-guide/visual-studio-tg/coded-steps-disappear-vs.md
@@ -1,7 +1,7 @@
 ---
 title: Coded Steps Disappear in Visual Studio
 page_title: Coded Steps Disappear in Visual Studio
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Find out why coded steps may disappear in Visual Studio when using the Test Studio plugin. This article explains the cause, related to custom base classes, and provides steps to restore coded step visibility in your projects."
 position: 1
 ---
 # Coded steps disappear in Visual Studio plugin when user double click on Coded Step for specific project
@@ -21,7 +21,7 @@ In order to fix this problem so you are able to see your coded steps again, you
 
 2. Generate in the project an independant class that defines the inheritance of your custom base class from Test Studio 'BaseWebAiiTest', i.e.:
 
-```C#
+````C#
 using ArtOfTest.WebAii.Design;
 using System;
 using System.Collections.Generic;
@@ -34,5 +34,5 @@ public class CustomWebAiiTest : BaseWebAiiTest
 {
 }
 }
-```
+````
 
diff --git a/docs/troubleshooting-guide/visual-studio-tg/enable-deployment.md b/docs/troubleshooting-guide/visual-studio-tg/enable-deployment.md
deleted file mode 100644
index 9b2c95b7..00000000
--- a/docs/troubleshooting-guide/visual-studio-tg/enable-deployment.md
+++ /dev/null
@@ -1,35 +0,0 @@
----
-title: Enable Deployment
-page_title: How to Enable Deployment
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
-position: 1
-publish: false
----
-# How to Enable Deployment
-
-## PROBLEM
-
-Deployment is the process of copying test assemblies, dependencies, and any other specified files to an "Out Directory." By default, the AppBase is the "Out Directory." If you try to use a Project/Solution that has not had the necessary data copied over, you will receive a similar error to below (this is a common reason for an error starting with System.IO.FileNotFoundException).
-
-By enabling Deployment, you are telling Visual Studio to copy all files for the project to the Out Directory. When it is disabled, everything runs out of the root folder for the project/solution.
-
-## SOLUTION
-
-1.&nbsp; Open the project. 
-
-2.&nbsp; Double-click the Test Settings file in use by the Project/Solution in the Solution Explorer. 
-
-![Test Settings][1]
-
-3.&nbsp; Click **Deployment** in the left column. 
-
-4.&nbsp; Check **Enable Deployment**. 
-
-![Enable Deployment][2]
-
-5.&nbsp; Click **Apply**. 
-
-> It will likely be necessary to Rebuild your project before running the test again.
-
-[1]: /img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig1.png
-[2]: /img/troubleshooting-guide/visual-studio-tg/enable-deployment/fig2.png
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/visual-studio-tg/fail-search-varify-step-vs-dpi.md b/docs/troubleshooting-guide/visual-studio-tg/fail-search-varify-step-vs-dpi.md
index d043448f..9d4ed502 100644
--- a/docs/troubleshooting-guide/visual-studio-tg/fail-search-varify-step-vs-dpi.md
+++ b/docs/troubleshooting-guide/visual-studio-tg/fail-search-varify-step-vs-dpi.md
@@ -1,7 +1,7 @@
 ---
 title: Fail Search or Verify Step in Visual Studio
 page_title: Fail Search or Verify Step in Visual Studio
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to resolve element search or verification failures in Visual Studio Test Explorer with Test Studio. This article explains DPI scaling issues, their impact on test execution, and provides step-by-step solutions."
 position: 1
 ---
 # Fail Search or Verify Step in Visual Studio
diff --git a/docs/troubleshooting-guide/visual-studio-tg/license-prompts-full-ts-version-activation.md b/docs/troubleshooting-guide/visual-studio-tg/license-prompts-full-ts-version-activation.md
new file mode 100644
index 00000000..460fba5d
--- /dev/null
+++ b/docs/troubleshooting-guide/visual-studio-tg/license-prompts-full-ts-version-activation.md
@@ -0,0 +1,35 @@
+---
+title: Wrong License Activation Prompt in Test Studio Dev Edition
+page_title: Test Studio Dev Edition Wrongly Prompts Activating Trial License
+description: "Learn how to resolve the wrong license activation prompt in Test Studio Dev Edition after upgrading the Visual Studio plugin. This guide provides a solution to address issues with unexpected trial license activation prompts."
+position: 1
+---
+# Wrong License Activation Prompt in Test Studio Dev Edition
+
+## PROBLEM
+
+After upgrading __Test Studio Dev Edition plugin in Visual Studio from release Q1 2025 (v. 2025.1.226)__ it prompts for license activation but the wizard suggests activating Test Studio Ultimate trial version only. 
+
+## SOLUTION
+
+
+To resolve the wrong license activation prompt in Test Studio Dev Edition, you can try one of the following options:
+
+### Option 1: Repair the Test Studio Dev Edition Installation
+
+1. Exit **Visual Studio** to ensure no conflicts during the repair process.
+1. Open the **Windows Control Panel**.
+2. Navigate to **Programs and Features**.
+3. Locate the **Test Studio Dev Edition** in the list of installed applications.
+4. Select the application and click **Repair**.
+5. Follow the on-screen instructions to complete the repair process.
+
+### Option 2: Perform a Fresh Install of Test Studio Dev Edition
+
+1. Exit **Visual Studio** to ensure no conflicts during the installation process.
+2. Open the **Windows Control Panel** and navigate to **Programs and Features**.
+3. Locate and uninstall the **Test Studio Dev Edition** application.
+4. Download the latest available version of **Test Studio Dev Edition** from the official website.
+5. Run the installation file and follow the on-screen instructions to complete the setup.
+
+After completing either of these steps, restart Visual Studio and verify that the license activation prompt now lets you choose your available Test Studio Dev Edition license.
\ No newline at end of file
diff --git a/docs/troubleshooting-guide/visual-studio-tg/missing-assembly-references.md b/docs/troubleshooting-guide/visual-studio-tg/missing-assembly-references.md
index 986ac779..d034b926 100644
--- a/docs/troubleshooting-guide/visual-studio-tg/missing-assembly-references.md
+++ b/docs/troubleshooting-guide/visual-studio-tg/missing-assembly-references.md
@@ -1,7 +1,7 @@
 ---
 title: Missing Assembly References in Test Studio Project
 page_title: Missing Assembly References in Test Studio Project
-description: "Test Studio is an innovative and easy-to-use automated web, WPF and load testing solution. Test Studio tests support essential technologies like ASP.NET AJAX, Silverlight, PHP and MVC. HTML5, Testing framework, functional testing, performance testing, load testing, exploratory testing, manual testing."
+description: "Learn how to fix missing assembly reference errors in Test Studio projects after updating the Visual Studio plugin. This article explains why references break and provides step-by-step solutions for restoring project builds."
 position: 1
 ---
 # Missing Assembly References in Visual Studio (Typically After Updating Test Studio Plugin)
@@ -40,7 +40,7 @@ Check the **Specific Version** property. Change it to False. The yellow warning
 
 You must select all the unresolved references at once or repeat these steps for every unresolved reference. Once you're done, there should be no warning icons and your project should build successfully.
 
-Also ensure you select **.NET Framework 4.5** as the target framework from the properties of the Test Project.
+Also ensure you select **.NET Framework 4.7.2** as the target framework from the properties of the Test Project.
 
 ![Target Framework][4]
 
diff --git a/docs/urlrewriter.config b/docs/urlrewriter.config
index 194cb071..1fd19472 100644
--- a/docs/urlrewriter.config
+++ b/docs/urlrewriter.config
@@ -816,7 +816,6 @@
 <redirect url="/teststudio/user-guide/data-driven-testing.aspx" to="/teststudio/automated-tests/data-drive-test/what-is-ddt"/>
 <redirect url="/teststudio/user-guide/data-driven-testing" to="/teststudio/automated-tests/data-drive-test/what-is-ddt"/>
 <redirect url="/teststudio/features/data-driven-testing/overview" to="/teststudio/automated-tests/data-drive-test/what-is-ddt"/>
-
 <redirect url="/teststudio/user-guide/add-custom-step/test-as-step.aspx" to="/teststudio/features/custom-steps/test-as-step"/>
 <redirect url="/teststudio/user-guide/add-custom-step/script-step.aspx" to="/teststudio/features/custom-steps/script-step"/>
 <redirect url="/teststudio/user-guide/modifying-tests/properties-pane.aspx" to="/teststudio/features/test-maintenance/test-properties-standalone"/>
@@ -902,8 +901,7 @@
 <redirect url="/teststudio/user-guide/scheduling-test-runs/schedule-test-execution.aspx" to="/teststudio/automated-tests/scheduling/schedule-execution"/>
 <redirect url="/teststudio/user-guide/scheduling-test-runs/schedule-test-execution" to="/teststudio/automated-tests/scheduling/schedule-execution"/>
 <redirect url="/teststudio/testing-framework/write-tests-in-code/intermediate-topics-wtc/html-control-suite-wtc/transfer-files" to="/teststudio/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers"/>
-<redirect url="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value" to="https://docs.telerik.com/teststudio/automated-tests/recording/overview#how-to-add-steps-in-the-test"/>
-<redirect url="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome" to="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-chrome"/>
+<redirect url="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/change-text-input-value" to="/teststudio/automated-tests/recording/overview#how-to-add-steps-in-the-test"/>
 <redirect url="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/extensions-disabled-in-ff" to="/teststudio/prerequisites/configure-your-browser/firefox"/>
 <redirect url="/teststudio/troubleshooting-guide/browser-inconsistencies-tg/html-button" to="/teststudio/features/recorder/highlighting-menu/quick-steps/quick-verification"/>
 <!-- previous_url: /user-guide/troubleshooting_guide/recording-problems/hover-over-highlighting-is-misaligned.aspx -->
@@ -938,7 +936,6 @@
 <redirect url="/teststudio/user-guide/command-line-test-execution/continuous-integration/teamcity.aspx" to="/teststudio/advanced-topics/build-server/team-city-builds"/>
 <redirect url="/teststudio/user-guide/command-line-test-execution/continuous-integration/teamcity" to="/teststudio/advanced-topics/build-server/team-city-builds"/>
 <redirect url="/teststudio/knowledge-base/scheduling-kb/non-domain-environment" to="https://testdocs.telerik.com/teststudio/automated-tests/scheduling/overview"/>
-
 <redirect url="/teststudio/knowledge-base/silverlight-kb/automate-in-tfs-builds" to="/teststudio/welcome"/>
 <redirect url="/teststudio/knowledge-base/silverlight-kb/codeless-scrolling-in-virtualized-panel" to="/teststudio/welcome"/>
 <redirect url="/teststudio/knowledge-base/verification-kb/verify-silverlight-combobox-items" to="/teststudio/welcome"/>
@@ -951,6 +948,190 @@
 <redirect url="/teststudio/troubleshooting-guide/scheduling-issues-tg/no-change-button" to="/teststudio/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"/>
 <redirect url="/teststudio/troubleshooting-guide/scheduling-issues-tg/scheduling-service-shuts-down" to="/teststudio/automated-tests/scheduling/multiple-machines-scheduling-setup/create-scheduling-server"/>
 <redirect url="/teststudio/automated-tests/load/advanced-topics/manage-windows-auth" to="/teststudio/automated-tests/load/configuring-load-tests-quick-guide"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/change-find-strategy" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/select-listbox-item-by-text" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/verify-colors-in-silverlight" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/verify-sort-order" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/verify-text-in-rich-textbox" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/combobox-automation/verify-all-text" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/combobox-automation/verify-specific-text" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/radgridview-automation/scrolling-paging" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/radgridview-automation/total-rows-count" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/radgridview-automation/verify-specific-column" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/silverlight/radgridview-automation/go-through-all-grid-cells" to="/teststudio/welcome"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-automation" to="/teststudio/welcome"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/silverlight-ui-namespace" to="/teststudio/welcome"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/element-validation" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/recorder-attached" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/silverlight-highlighting" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/silverlight-unable-connect-oob" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/find-element-timeout" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/target-host-error" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/safari-tg/extension-not-installed" to="/teststudio/welcome"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/firefox-tg/mcafee-siteadvisor" to="/teststudio/welcome"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/wpf-ui-automation" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/framework-element-object" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/framework-element-object"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/invoking-actions" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/invoking-actions"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/locating-elements" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/silverlight-wpf-automation-wtc/synchronization" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/synchronization"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/silverlight-wpf-tg/window-partial-match" to="/teststudio/troubleshooting-guide/test-execution-problems-tg/window-partial-match"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/firefox-tg/extension-not-installed" to="/teststudio/prerequisites/configure-your-browser/firefox"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/firefox-tg/https-with-custom-proxy" to="/teststudio/knowledge-base/project-configuration-kb/register-certificate"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/chrome-tg/cannot-execute-test" to="/teststudio/prerequisites/configure-your-browser/chrome"/>
+<!-- previous_url: /user-guide/code-samples/general/data-driven-find-expressions.aspx, /user-guide/code-samples/general/data-driven-find-expressions -->
+<redirect url="/teststudio/user-guide/code-samples/general/data-driven-find-expressions.aspx" to="/teststudio/advanced-topics/coded-samples/general/data-driven-find-expressions"/>
+<redirect url="/teststudio/user-guide/code-samples/general/data-driven-find-expressions" to="/teststudio/advanced-topics/coded-samples/general/data-driven-find-expressions"/>
+<redirect url="/teststudio/knowledge-base/browsers-kb/custom-chrome-profile" to="/teststudio/prerequisites/configure-your-browser/chrome"/>
+<redirect url="/teststudio/knowledge-base/browsers-kb/custom-chrome-path" to="/teststudio/prerequisites/configure-your-browser/chrome"/>
+<redirect url="/teststudio/knowledge-base/browsers-kb/custom-edge-chromium-profile" to="/teststudio/prerequisites/configure-your-browser/edge-chromium"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/tests-not-executed-in-chrome-or-firefox" to="/teststudio/prerequisites/configure-your-browser/firefox"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/unable-to-show-data" to="/teststudio/automated-tests/data-drive-test/what-is-ddt"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/wait-for-condition-timed-out" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/knowledge-base/test-recording-kb/kendoui-duplicate-elements" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/unable-to-launch-recorder" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/no-file-path-ie10" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/java-flash-activex" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/ie-fails-to-record-execute-test" to="/teststudio/getting-started/first-test"/>
+<redirect url="/teststudio/troubleshooting-guide/recording-problems-tg/cannot-launch-exploratory" to="/teststudio/getting-started/first-test"/>
+<!-- previous_url: /user-guide/code-samples/html/tagframe.aspx, /user-guide/code-samples/html/tagframe -->
+<redirect url="/teststudio/user-guide/code-samples/html/tagframe.aspx" to="/teststudio/advanced-topics/coded-samples/html/add-tag-to-iframe"/>
+<redirect url="/teststudio/user-guide/code-samples/html/tagframe" to="/teststudio/advanced-topics/coded-samples/html/add-tag-to-iframe"/>
+<!-- previous_url: /user-guide/code-samples/html/handling-radasynchdialog.aspx, /user-guide/code-samples/html/handling-radasynchdialog -->
+<redirect url="/user-guide/code-samples/html/handling-radasynchdialog.aspx" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/user-guide/code-samples/html/handling-radasynchdialog" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/html/async-upload-dialog" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<!-- previous_url: /user-guide/code-samples/html/ajax-calendar-random-date-selection.aspx, /user-guide/code-samples/html/ajax-calendar-random-date-selection -->
+<redirect url="/teststudio/user-guide/code-samples/html/ajax-calendar-random-date-selection.aspx" to="/teststudio/advanced-topics/coded-samples/html/ajax-calendar-random-date"/>
+<redirect url="/teststudio/user-guide/code-samples/html/ajax-calendar-random-date-selection" to="/teststudio/advanced-topics/coded-samples/html/ajax-calendar-random-date"/>
+<!-- previous_url: /user-guide/code-samples/html/common-find-expressions.aspx, /user-guide/code-samples/html/common-find-expressions -->
+<redirect url="/teststudio/user-guide/code-samples/html/common-find-expressions.aspx" to="/teststudio/advanced-topics/coded-samples/html/common-find-expressions"/>
+<redirect url="/teststudio/user-guide/code-samples/html/common-find-expressions" to="/teststudio/advanced-topics/coded-samples/html/common-find-expressions"/>
+<!-- previous_url: /user-guide/code-samples/html/conditional-dialog-handling.aspx, /user-guide/code-samples/html/conditional-dialog-handling -->
+<redirect url="/teststudio/user-guide/code-samples/html/conditional-dialog-handling" to="/teststudio/advanced-topics/coded-samples/html/conditional-dialog-handling"/>
+<redirect url="/teststudio/user-guide/code-samples/html/conditional-dialog-handling.aspx" to="/teststudio/advanced-topics/coded-samples/html/conditional-dialog-handling"/>
+<!-- previous_url: /user-guide/code-samples/html/extract-an-attribute.aspx, /user-guide/code-samples/html/extract-an-attribute -->
+<redirect url="/teststudio/user-guide/code-samples/html/extract-an-attribute.aspx" to="/teststudio/advanced-topics/coded-samples/html/extract-an-attribute"/>
+<redirect url="/teststudio/user-guide/code-samples/html/extract-an-attribute" to="/teststudio/advanced-topics/coded-samples/html/extract-an-attribute"/>
+<!-- previous_url: /user-guide/code-samples/html/jquery-events-do-not-fire.aspx, /user-guide/code-samples/html/jquery-events-do-not-fire -->
+<redirect url="/teststudio/user-guide/code-samples/html/jquery-events-do-not-fire.aspx" to="/teststudio/welcome"/>
+<redirect url="/teststudio/user-guide/code-samples/html/jquery-events-do-not-fire.aspx" to="/teststudio/welcome"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/html/jquery-events-do-not-fire" to="/teststudio/welcome"/>
+<!-- previous_url: /user-guide/code-samples/html/verify-dialog-text.aspx, /user-guide/code-samples/html/verify-dialog-text -->
+<redirect url="/teststudio/user-guide/code-samples/html/verify-dialog-text.aspx" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/user-guide/code-samples/html/verify-dialog-text" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/html/verify-dialog-text" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/html/verify-dialog-text-chrome" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/troubleshooting-guide/visual-studio-tg/cannot-build-project" to="/teststudio/automated-tests/vs-plugin/project-vs-plugin"/>
+<redirect url="/teststudio/troubleshooting-guide/visual-studio-tg/enable-deployment" to="/teststudio/automated-tests/vs-plugin/project-vs-plugin"/>
+<redirect url="/teststudio/troubleshooting-guide/test-execution-problems-tg/dialog-handling-fails" to="/teststudio/automated-tests/recording/recording-dialogs"/>
+<redirect url="/teststudio/troubleshooting-guide/source-control-problems-tg/unable-to-load-sc-plugin" to="/teststudio/automated-tests/source-control/tfs/overview-tfs"/>
+<redirect url="/teststudio/troubleshooting-guide/source-control-problems-tg/error-connecting-tfs" to="/teststudio/automated-tests/source-control/tfs/overview-tfs"/>
+<redirect url="/teststudio/troubleshooting-guide/source-control-problems-tg/error-adding-files" to="/teststudio/automated-tests/source-control/tfs/overview-tfs"/>
+<redirect url="/teststudio/troubleshooting-guide/scheduling-issues-tg/test-from-tfs-dont-run" to="/teststudio/automated-tests/scheduling/schedule-execution"/>
+<redirect url="/teststudio/troubleshooting-guide/scheduling-issues-tg/run-failure-status-500" to="/teststudio/automated-tests/scheduling/schedule-execution"/>
+<redirect url="/teststudio/troubleshooting-guide/scheduling-issues-tg/run-failure-serialization-exception" to="/teststudio/automated-tests/scheduling/schedule-execution"/>
+<redirect url="/teststudio/troubleshooting-guide/load-testing-problems-tg/missing-dynamic-targets" to="/teststudio/automated-tests/load/designing-load-tests/dynamic-targets"/>
+<redirect url="/teststudio/troubleshooting-guide/load-testing-problems-tg/load-test-run-quits" to="/teststudio/automated-tests/load/running-load-test/best-practices"/>
+<redirect url="/teststudio/troubleshooting-guide/load-testing-problems-tg/duplicate-dynamic-targets" to="/teststudio/automated-tests/load/designing-load-tests/dynamic-targets"/>
+<redirect url="/teststudio/troubleshooting-guide/load-testing-problems-tg/cannot-dispatch-load-test" to="/teststudio/automated-tests/load/running-load-test/best-practices"/>
+<redirect url="/teststudio/troubleshooting-guide/load-testing-problems-tg/cannot-add-scheduling-service" to="/teststudio/automated-tests/load/designing-load-tests/managing-vu"/>
+<redirect url="/teststudio/troubleshooting-guide/installation-problems-tg/vista-installer-error" to="/teststudio/prerequisites/installation/installation-consideration"/>
+<redirect url="/teststudio/troubleshooting-guide/installation-problems-tg/failed-internet-shortcut" to="/teststudio/prerequisites/installation/install-procedure"/>
+<redirect url="/teststudio/troubleshooting-guide/cannot-launch-test-studio-tg/reset-skipped-packages" to="/teststudio/prerequisites/installation/install-procedure"/>
+<redirect url="/teststudio/troubleshooting-guide/cannot-launch-test-studio-tg/package-load-failure" to="/teststudio/prerequisites/installation/install-procedure"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/intermediate-topics-wtc/settings-and-configuration-wtc/app-config-file" to="/teststudio/features/test-runners/artoftest-runner#option-to-use-custom-settings-for-the-execution"/>
+<redirect url="/teststudio/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/firefox-dialogs" to="/teststudio/testing-framework/write-tests-in-code/advanced-topics-wtc/html-popups-and-dialogs-wtc/built-in-handlers"/>
+<redirect url="/teststudio/prerequisites/installation/vs2017-compatibility" to="/teststudio/prerequisites/installation/installation-consideration"/>
+<redirect url="/teststudio/prerequisites/installation/configure-windows-server" to="/teststudio/prerequisites/installation/installation-consideration"/>
+<redirect url="/teststudio/features/test-runners/mstest" to="/teststudio/features/test-runners/artoftest-runner"/>
+<redirect url="/teststudio/features/test-runners/manual-runner" to="/teststudio/features/test-runners/artoftest-runner"/>
+<redirect url="/teststudio/automated-tests/test-lists/test-lists-type-standalone" to="/teststudio/automated-tests/test-lists/test-lists-standalone"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/general/load-testing-extensions" to="/teststudio/automated-tests/load/overview"/>
+<redirect url="/teststudio/automated-tests/load/designing-load-tests/dynamic-targets-custom" to="/teststudio/automated-tests/load/designing-load-tests/dynamic-targets"/>
+<redirect url="/teststudio/automated-tests/data-drive-test/help-file-for-docs" to="/teststudio/automated-tests/data-drive-test/what-is-ddt"/>
+<redirect url="/teststudio/automated-tests/customize-project/built-in-help-tools/guided-tutorials" to="/teststudio/automated-tests/customize-project/built-in-help-tools/in-product-guides"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/general/access-performance-data" to="/teststudio/automated-tests/performance/overview"/>
+<redirect url="/teststudio/advanced-topics/build-server/azure-devops" to="/teststudio/advanced-topics/build-server/azdo/self-hosted-agent-classic-pipeline"/>
+<redirect url="/teststudio/advanced-topics/build-server/microsoft-hosted-agent-testing" to="/teststudio/advanced-topics/build-server/azdo/ms-hosted-agent-classic-pipeline"/>
+<redirect url="/teststudio/user-guide/code-samples/general/access-sql-database" to="/teststudio/advanced-topics/coded-samples/general/access-sql-database"/>
+<redirect url="/teststudio/user-guide/code-samples/general/access-sql-database.aspx" to="/teststudio/advanced-topics/coded-samples/general/access-sql-database"/>
+<redirect url="/teststudio/user-guide/code-samples/general/attach-columns-to-input-values-in-code.aspx" to="/teststudio/advanced-topics/coded-samples/general/attach-data-columns"/>
+<redirect url="/teststudio/user-guide/code-samples/general/execution-extensions.aspx" to="/teststudio/advanced-topics/coded-samples/general/execution-extensions"/>
+<redirect url="/teststudio/user-guide/code-samples/general/execution-extensions" to="/teststudio/advanced-topics/coded-samples/general/execution-extensions"/>
+<redirect url="/teststudio/user-guide/code-samples/general/random-number-input.aspx" to="/teststudio/advanced-topics/coded-samples/general/generate-random-number"/>
+<redirect url="/teststudio/user-guide/code-samples/general/random-number-input" to="/teststudio/advanced-topics/coded-samples/general/generate-random-number"/>
+<redirect url="/teststudio/user-guide/code-samples/general/generate-random-text.aspx" to="/teststudio/advanced-topics/coded-samples/general/generate-random-text"/>
+<redirect url="/teststudio/user-guide/code-samples/general/generate-random-text" to="/teststudio/advanced-topics/coded-samples/general/generate-random-text"/>
+<redirect url="/teststudio/user-guide/code-samples/general/invoke-web-service-call.aspx" to="/teststudio/automated-tests/execute-apitest/add-api-test-as-step"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/general/invoke-web-service-call" to="/teststudio/automated-tests/execute-apitest/add-api-test-as-step"/>
+<redirect url="/teststudio/user-guide/code-samples/general/non-iterative-data-driven-testing.aspx" to="/teststudio/advanced-topics/coded-samples/general/non-iterative-data-driving"/>
+<redirect url="/teststudio/user-guide/code-samples/general/non-iterative-data-driven-testing" to="/teststudio/advanced-topics/coded-samples/general/non-iterative-data-driving"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/general/override-app-config" to="/teststudio/features/test-runners/artoftest-runner#option-to-use-custom-settings-for-the-execution"/>
+<redirect url="/teststudio/advanced-topics/coded-samples/general/mouse-wheel-scroll" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/user-guide/code-samples/general/random-row.aspx" to="/teststudio/advanced-topics/coded-samples/general/random-row"/>
+<redirect url="/user-guide/code-samples/general/random-row" to="/teststudio/advanced-topics/coded-samples/general/random-row"/>
+<redirect url="/teststudio/user-guide/code-samples/general/send-keystrokes.aspx" to="/teststudio/advanced-topics/coded-samples/general/send-keystrokes"/>
+<redirect url="/teststudio/user-guide/code-samples/general/send-keystrokes" to="/teststudio/advanced-topics/coded-samples/general/send-keystrokes"/>
+<redirect url="/teststudio/user-guide/code-samples/general/wait-for-element-to-exist-in-code.aspx" to="/teststudio/advanced-topics/coded-samples/general/wait-for-element-in-code"/>
+<redirect url="/teststudio/user-guide/code-samples/general/wait-for-element-to-exist-in-code" to="/teststudio/advanced-topics/coded-samples/general/wait-for-element-in-code"/>
+<redirect url="/teststudio/user-guide/code-samples/general/utility-in-standalone.aspx" to="/teststudio/advanced-topics/coded-samples/general/utility-class-in-standalone"/>
+<redirect url="/teststudio/user-guide/code-samples/general/utility-in-standalone" to="/teststudio/advanced-topics/coded-samples/general/utility-class-in-standalone"/>
+<redirect url="/teststudio/user-guide/code-samples/general/using_the_http_proxy.aspx" to="/teststudio/advanced-topics/coded-samples/general/using-the-http-proxy"/>
+<redirect url="/teststudio/user-guide/code-samples/general/using_the_http_proxy" to="/teststudio/advanced-topics/coded-samples/general/using-the-http-proxy"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/connect-to-running-wpf-app.aspx" to="/teststudio/advanced-topics/coded-samples/wpf/connect-to-running-app"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/connect-to-running-wpf-app" to="/teststudio/advanced-topics/coded-samples/wpf/connect-to-running-app"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/go-through-cells.aspx" to="/teststudio/advanced-topics/coded-samples/wpf/go-through-grid-cells"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/go-through-cells" to="/teststudio/advanced-topics/coded-samples/wpf/go-through-grid-cells"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/go-through-radtreeview.aspx" to="/teststudio/advanced-topics/coded-samples/wpf/go-through-radtreeview"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/go-through-radtreeview" to="/teststudio/advanced-topics/coded-samples/wpf/go-through-radtreeview"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/parameterize-wpf-app-location.aspx" to="/teststudio/advanced-topics/coded-samples/wpf/parameterize-wpf-app"/>
+<redirect url="/teststudio/user-guide/code-samples/wpf/parameterize-wpf-app-location" to="/teststudio/advanced-topics/coded-samples/wpf/parameterize-wpf-app"/>
+<redirect url="/teststudio/user-guide/exploratory-testing.aspx" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/user-guide/exploratory-testing" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/features/testing-types/exploratory-testing/overview" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/user-guide/exploratory-testing/launch-tool.aspx" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio//user-guide/exploratory-testing/launch-tool" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/features/testing-types/exploratory-testing/launch-tool" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/user-guide/exploratory-testing/provide-feedback.aspx" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio//user-guide/exploratory-testing/provide-feedback" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/features/testing-types/exploratory-testing/provide-feedback" to="/teststudio/automated-tests/recording/overview"/>
+<redirect url="/teststudio/user-guide/manual-testing/convert-to-automated.aspx" to="/teststudio/features/testing-types/manual-testing/convert-automated"/>
+<redirect url="/teststudio/user-guide/manual-testing/convert-to-automated" to="/teststudio/features/testing-types/manual-testing/convert-automated"/>
+<redirect url="/teststudio/user-guide/manual-testing/fast-forward-test.aspx" to="/teststudio/features/testing-types/manual-testing/fast-forward"/>
+<redirect url="/teststudio/user-guide/manual-testing/fast-forward-test" to="/teststudio/features/testing-types/manual-testing/fast-forward"/>
+<redirect url="/teststudio/user-guide/manual-testing/import_and_export_excel.aspx" to="/teststudio/features/testing-types/manual-testing/import-export"/>
+<redirect url="/teststudio/user-guide/manual-testing/import_and_export_excel" to="/teststudio/features/testing-types/manual-testing/import-export"/>
+<redirect url="/teststudio/user-guide/manual-testing.aspx" to="/teststudio/features/testing-types/manual-testing/overview"/>
+<redirect url="/teststudio/user-guide/manual-testing" to="/teststudio/features/testing-types/manual-testing/overview"/>
+<redirect url="/teststudio/user-guide/manual-testing/start-a-manual-test.aspx" to="/teststudio/features/testing-types/manual-testing/start-test"/>
+<redirect url="/teststudio/user-guide/manual-testing/start-a-manual-test" to="/teststudio/features/testing-types/manual-testing/start-test"/>
+<redirect url="/teststudio/user-guide/write-tests-in-code/silverlight-test-automation/locating-elements.aspx" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements"/>
+<redirect url="/teststudio/user-guide/write-tests-in-code/silverlight-test-automation/locating-elements" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/locating-elements"/>
+<redirect url="/teststudio/user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation.aspx" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation"/>
+<redirect url="/teststudio/user-guide/write-tests-in-code/silverlight-test-automation/wpf-test-automation" to="/teststudio/testing-framework/write-tests-in-code/wpf-automation-wtc/wpf-ui-automation"/>
+<redirect url="/teststudio/user-guide/troubleshooting_guide/test-execution-problems/assembly-built-by-newer-runtime.aspx" to="/teststudio/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime"/>
+<redirect url="/teststudio/user-guide/troubleshooting_guide/test-execution-problems/assembly-built-by-newer-runtime" to="/teststudio/troubleshooting-guide/test-execution-problems-tg/built-by-newer-runtime"/>
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
+<!-- <redirect url="" to=""/> -->
 <!-- <redirect url="" to=""/> -->
 <!-- <redirect url="" to=""/> -->
 <!-- <redirect url="" to=""/> -->
@@ -961,7 +1142,5 @@
 <!-- <redirect url="" to=""/> -->
 <!-- <redirect url="" to=""/> -->
 <!-- <redirect url="" to=""/> -->
-
-<!-- previous_url:  -->
 <!-- <redirect url="" to=""/> -->
 </rewriter>
\ No newline at end of file
diff --git a/docs/welcome.md b/docs/welcome.md
index 1ac77dd8..547def0d 100644
--- a/docs/welcome.md
+++ b/docs/welcome.md
@@ -14,7 +14,7 @@ You’ve been always looking for a test automation tool that really works and yo
 <a href="http://www.telerik.com/teststudio" target="_blank">Test Studio</a> is an easy to use tool for functional UI, load/performance and API testing for web and WPF desktop applications. Whether you decide to go codeless or choose to use Test Studio’s code-based automation capabilities, you’ll always ensure optimal app quality and deliver outstanding results. Test Studio provides <a href="https://www.telerik.com/teststudio/test-automation-solutions-for-the-entire-team" target="_blank">test automation solutions for the entire team</a>, empowering everyone—from junior testers to senior developers, product managers and QA leads—to achieve maximum productivity in agile software delivery environments.
 
 {% if site.has_cta_panels == true %}
-{% include cta-panel-teststudio-introduction.html %}
+{% include cta-panel-introduction.html %}
 {% endif %}
 
 ## Who is Test Studio Designed For?
@@ -51,6 +51,11 @@ Test Studio also supports load and performance testing by allowing you to conver
 
 * __Validating PDFs__ – add <a href="/automated-tests/recording/pdf-validation" target="_blank">PDF validation</a> steps during test recording or whenever you need to during automation.
 
+> __Feature Deprecation Notice__
+> <br>
+> <br>
+> Performance Testing is scheduled for deprecation in the Test Studio 2026 Q1 release.
+
 <table id=no-table>
 <tr>
 <td valign=top>
@@ -110,4 +115,4 @@ Test Studio also supports load and performance testing by allowing you to conver
 
 </td>
 </tr>
-<table>
+</table>
diff --git a/images/pdf-cover.png b/images/pdf-cover.png
new file mode 100644
index 00000000..ce9967ef
Binary files /dev/null and b/images/pdf-cover.png differ