telerik
diff --git a/‎.gitignore
+6-6 b/‎.gitignore
+6-6
diff --git a/‎_config.yml
+6-6 b/‎_config.yml
+6-6
diff --git a/‎_templates/radajax/common-errors.md
+19-17 b/‎_templates/radajax/common-errors.md
+19-17
diff --git a/‎controls/ajaxmanager/accessibility-and-internationalization/wai-aria-support.md
-34 b/‎controls/ajaxmanager/accessibility-and-internationalization/wai-aria-support.md
-34
diff --git a/‎controls/ajaxmanager/advantages.md
+83 b/‎controls/ajaxmanager/advantages.md
+83
diff --git a/‎controls/ajaxmanager/appearance-and-styling/render-modes.md
-107 b/‎controls/ajaxmanager/appearance-and-styling/render-modes.md
-107
@@ -1,7 +1,7 @@
 
+.DS_Store
 .asset-cache/
 .dockerignore
-.DS_Store
 .editorconfig
 .jekyll-metadata
 .ruby-version
@@ -19,24 +19,24 @@
 /favicon.ico
 /fonts/
 /styles/
+CODEOWNERS
+Dockerfile
+Gemfile
+Gemfile.lock
+SlugLog.log
 _excludefile.yml
 _site
 _tempconfig.yml
 bs-config.js
 build-docs.sh
-CODEOWNERS
 copy_content.sh
 copy_local.sh
-Dockerfile
 exclude.txt
-Gemfile
-Gemfile.lock
 install-npm.sh
 knowledge-base.html
 modify-config.sh
 robots.txt
 search.html
-SlugLog.log
 start-docs.sh
 temp_exclude_result.tmp
 to_delete.md
 
@@ -167,6 +167,12 @@ navigation:
     "controls/ajaxmanager":
         title: "AjaxManager"
         position: 1
+    "controls/ajaxmanager/client-side-programming":
+        title: "Client-Side API"
+        position: 70
+    "controls/ajaxmanager/server-side-programming":
+        title: "Server-Side API"
+        position: 80
     "controls/ajaxloadingpanel":
         title: "AjaxLoadingPanel"
         position: 1
@@ -544,12 +550,6 @@ navigation:
 
 
 ## List control specific directory names and order here, like this:
-    "*ajaxmanager/radajaxmanagerproxy":
-        title: "RadAjaxManagerProxy"
-        position: 6
-    "*ajaxmanager/performance":
-        title: "Performance"
-        position: 8
     "*autocompletebox/client-side-programming/objects":
         title: "Objects"
         position: 4
 
@@ -1,39 +1,41 @@
 #known-errors
 
-This help article describes common reasons for error messages and their solutions.
+This article lists the common error messages which may occur when working with Telerik UI for ASP.NET AJAX, and their causes and solutions.
 
-* **`SyntaxError`** (for IE) or **`Uncaught SyntaxError: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule'`** (for Chrome), or **`SyntaxError: An invalid or illegal string was specified`** (for FireFox).
+* The `SyntaxError` in Internet Explorer, `Uncaught SyntaxError: Failed to execute 'insertRule' on 'CSSStyleSheet': Failed to parse the rule'` in Chrome, or `SyntaxError: An invalid or illegal string was specified` in FireFox occur.
 
-	This error is caused by having commented CSS rules (e.g., `/* .someClass { display: none; } */`) in the `<head>` of your page.
+	The cause for this error is the commented CSS rules in the `<head>` of your page, for example, `/* .someClass { display: none; } */`.
 
-	RadAjax controls update the `<head>` of the page to let controls register stylesheets and scripts during an AJAX request and such commented rules cannot be parsed by the engine.
+	The AjaxManager and Ajaxpanel update the `<head>` of the page to enable controls to register stylesheets and scripts during an AJAX request. Such commented rules cannot be parsed by the engine.
 
-	There are three solutions:
+	To solve this issue, use any of the following approaches:
 
-	* Set the `EnablePageHeadUpdate` property of the RadAjax control to `false`.
+	* Set the `EnablePageHeadUpdate` property of the Ajax control to `false`.
 
 	* Remove the commented CSS rule or move it to a separate stylesheet file.
 
-	* Place the styles settings in external css files.
+	* Place the styles settings in external CSS files.
 
 
-* **Receiving `Sys.WebForms.PageRequestManagerParserErrorException`.** You may receive this error if you have used **RadAjaxPanel** and **RadAjaxManager** to AJAX-enable the same control at the same time. You can read more about the problem in the [Controls Wrapped in AjaxPanel and Added to AjaxManager Settings]({%slug ajaxmanager/troubleshooting/controls-wrapped-in-ajaxpanel-and-added-to-ajaxmanager-settings%}) help article.
+* `Sys.WebForms.PageRequestManagerParserErrorException` occurs.
 
+	A possible cause for this error is the usage of the AjaxPanel and AjaxManager to AJAX-enable the same control at the same time. For more information on the issue, refer to the article on [using controls wrapped in an AjaxPanel and added to the AjaxManager settings]({%slug ajaxmanager/troubleshooting/controls-wrapped-in-ajaxpanel-and-added-to-ajaxmanager-settings%}).
 
-* **The state information is invalid for this page and might be corrupted.** Firefox 1.5 and up uses in-memory caching for entire web pages, including their JavaScript states, for a single browser session. Going backward and forward between visited pages requires no page loading and the JavaScript states are preserved. This feature, referred to by some as bfcache (for "Back-Forward Cache"), makes page navigation very fast. This caching state is preserved until the user closes the browser.Please refer to the [Ajax, ViewState and Firefox]({%slug ajaxpanel/troubleshooting/firefox-specifics%}) help article for more information and a workaround.
 
-* Dialog with the following error: **`Unexpected AJAX response was received from the server`**. This may be caused by one of the following reasons:
+* `The state information is invalid for this page and might be corrupted` error occurs. 
 
-	* `Server.Transfer()`.
-	* Custom HTTP handler.
-	* Incorrect loading of an AJAX-enabled user control.
+	Firefox version 1.5 and later use in-memory caching for entire web pages, including their JavaScript states, for a single browser session. Going backward and forward between visited pages requires no page loading and the JavaScript states are preserved. This feature, referred to by some as bfcache (for "Back-Forward Cache"), makes page navigation very fast. The caching state is preserved until the user closes the browser. For more information and a workaround, refer to the article on [using Ajax, ViewState, and Firefox]({%slug ajaxpanel/troubleshooting/firefox-specifics%}).
 
-	**Verify that you don't get a server-side exception or any other undesired behavior, by setting the `EnableAJAX` property to `false`**.
+* `Unexpected AJAX response was received from the server` error occurs in a dialog. 
 
-	Most often people see this error when using the `Server.Transfer` method. Note that some controls may use this method internally (like the `asp:LoginView` control). In order to redirect to another page in an AJAX-enabled application, you should use the approaches mentioned in the [Redirecting to another page] ({%slug ajaxpanel/how-to/redirecting-to-another-page%}) help article. In most cases, `Response.Redirect` does the trick. You can also try using the `Redirect` method of the `RadAjax` control you use.
+	The possible causes for this issue may be any of the following:
 
-	Another reason you might see this error is because the application improperly loads user controls. The [Loading user controls]({%slug ajaxpanel/how-to/load-user-controls%}) help topic will help you fix the error in your code.
+	* Using `Server.Transfer()`&mdash;Some controls may use this method internally, for example, the `asp:LoginView` control. To redirect to another page in an AJAX-enabled application, use the approaches from the article on [redirecting to another page]({%slug ajaxpanel/how-to/redirecting-to-another-page%}). To solve this issue, utilize `Response.Redirect`. You can also try using the `Redirect` method of the Ajax control you use.
 
-	Additionally, if the suggestions above do not help, you could disable AJAX as suggested in the error message. This will help you verify whether the error is related to using AJAX and if it is not, to fix any server-side errors if any are thrown.
+	* Using a custom HTTP handler
+	
+	* Incorrect loading of an AJAX-enabled user control. To solve the issue, refer to the article on [loading user controls]({%slug ajaxpanel/how-to/load-user-controls%}).
+
+	If the suggested solutions do not fix the issue, disable AJAX as suggested in the error message. Verify that you don't get a server-side exception or any other undesired behavior by setting the `EnableAJAX` property to `false`. This approach will help you verify whether the error is related to using AJAX and, if not, to fix any server-side errors if any are thrown.
 
 #end
@@ -0,0 +1,83 @@
+---
+title: Advantages
+page_title: AjaxManager Advantages
+description: "Learn more about the advantages of using the Telerik UI for ASP.NET AjaxManager."
+slug: ajaxmanager/getting-started/radajax-advantages
+previous_url: ajax/getting-started/radajax-advantages
+tags: telerik, aspnet, ajax, ajaxmanager, advantages
+published: True
+position: 1
+---
+
+# AjaxManager Advantages
+
+Using the AjaxManager control provides a number of benefits.
+
+Among the many advantages for using the AjaxManager is that you don't need to make any changes to your existing applications, nor build new ones in some specific way so that they can be AJAX-enabled. 
+
+The AjaxManager uses the Microsoft ASP.NET AJAX engine to Ajaxify applications but eliminates the need of using numerous UpdatePanels, triggers, and so on.
+
+The click-and-Go™ technology of the AjaxManager allows you to AJAX-enable any ASP.NET application without making any modification or writing a single line of code. For more information, refer to the article on [AJAX and Telerik AJAX]({% slug ajaxmanager/getting-started/what-is-ajax %}). 
+
+## Existing Applications
+
+To AJAX-enable an existing application:
+
+1. Add Microsoft ASP.NET AJAX to your project.
+
+1. Drop an [AjaxManager]({%slug ajaxmanager/overview %}) to your form.
+
+1. Define the AJAX relations by using a single dialogue in Visual Studio.
+
+1. Press `F5` to run.
+
+## New Applications 
+
+To AJAX-enable new applications, you don't have to follow any specific guidelines. Build a regular postback-based application the way you are used to and use the [AjaxManager]({%slug ajaxmanager/overview%}) to AJAX-enable it at the end.
+
+
+## AJAX-Enabling without the AjaxManager
+
+When using Microsoft ASP.NET AJAX, the standard approach to AJAX-enable an application will require you to place `UpdatePanels` around each area that needs to be updated. This may introduce some challenges with preserving the application layout, that is, you need to figure out how to group the various elements. 
+
+Consider the following example: it begins as an ASP.NET web page that has a calendar, an email list, and a message body control. When the user selects a date from the calendar, the e-mails that are received that day are shown in the grid. Once an e-mail is selected, its content is displayed in the message body.
+
+>caption Add three UpdatePanels to AJAX-enable a page with Microsoft ASP.NET AJAX
+
+![UpdatePanels usage](images/Manager1_UpdatePanels.png)
+
+In simple scenarios like the demonstrated one, placing `UpdatePanels` may not be very difficult. However, in real-life applications with dozens of UI controls that need to start working with AJAX, placing more than 20 `UpdatePanels` and figuring which element will go in the respective panel, may be a challenge even for the most advanced developers.
+
+## AJAX-Enabling with the AjaxManager
+
+The AjaxManager offers a fundamentally different approach for enabling AJAX on existing applications by dragging and dropping the control on your form and, then, setting the relations in a codeless way. 
+
+>caption The AjaxManager designer when the Smart Tag is clicked
+
+![Ajax results](images/Manager1_Form.png)
+
+Once the AjaxManager is placed on the form, you need to use its configuration dialog to define the which controls will initiate AJAX requests and which controls will be updated by each respective AJAX request, for example:
+
+* "Message Body" UpdatePanel - Trigger 1: The needs to be updated when an **e-mail item** is clicked.
+
+* "Message Body" UpdatePanel - Trigger 2: The needs to be updated when the **calendar** is clicked.
+
+* "E-mail list" UpdatePanel - Trigger 1: The needs to be updated when the **calendar** is clicked.
+
+The combination of these three relation triggers defines the two AJAX relations on the page, which are:
+
+1. When the **calendar** is clicked, the **e-mail list** and the **message body** need to be updated.
+
+1. When an **e-mail message** is clicked, only the **message body** needs to be updated.
+
+As you can see, it is not very easy to figure out what will be the effect of the combination of triggers, especially when you have complex real-life application. Moreover, setting several triggers that facilitate each AJAX relation will need serious planning and something like a "Trigger diagram". 
+
+In contrast, the AjaxManager offers a centralized place where you can define and modify the AJAX relations on the page through the single configuration dialog in the Visual Studio .Net design-mode.
+
+![Buld RadAjax Settings](images/Centralized_Management_of_AJAX_Relations_Pick2.png)
+
+The logic for setting AJAX relations in the AjaxManager dialog brings about another benefit: the AJAX relations are defined in the same sequence in which users interact with the interface of the application.
+
+## See Also
+
+* [Adding the AjaxSettings Programmatically]({%slug ajaxmanager/how-to/add-ajaxsettings-programmatically%})