Replacing Telerik UI for ASP.NET AJAX with Telerik® UI for ASP.NET Ajax

Author: pepinho24

README.md

@@ -1,15 +1,15 @@
 ---
-title: Telerik UI for ASP.NET AJAX Documentation Repo
+title: Telerik® UI for ASP.NET Ajax Documentation Repo
 publish: false
 ---
 
-# Telerik UI for ASP.NET AJAX Documentation
+# Telerik® UI for ASP.NET Ajax Documentation
 
-Welcome to the GitHub repo for [UI for ASP.NET AJAX](http://www.telerik.com/products/aspnet-ajax.aspx) documentation. This repository contains the source content — written in Markdown — that we use to power Telerik UI for ASP.NET AJAX Documentation at [http://docs.telerik.com/devtools/aspnet-ajax/introduction](http://docs.telerik.com/devtools/aspnet-ajax/introduction). If you've arrived here wanting to search and peruse our docs, you'd be better served heading over to [http://docs.telerik.com/devtools/aspnet-ajax/introduction](http://docs.telerik.com/devtools/aspnet-ajax/introduction) where our content is prettified and searchable.
+Welcome to the GitHub repo for [UI for ASP.NET AJAX](http://www.telerik.com/products/aspnet-ajax.aspx) documentation. This repository contains the source content — written in Markdown — that we use to power Telerik® UI for ASP.NET Ajax Documentation at [http://docs.telerik.com/devtools/aspnet-ajax/introduction](http://docs.telerik.com/devtools/aspnet-ajax/introduction). If you've arrived here wanting to search and peruse our docs, you'd be better served heading over to [http://docs.telerik.com/devtools/aspnet-ajax/introduction](http://docs.telerik.com/devtools/aspnet-ajax/introduction) where our content is prettified and searchable.
 
 ## Running Locally
 
-You can generate a static web site from the Telerik UI for ASP.NET AJAX documentation and browse it locally.
+You can generate a static web site from the Telerik® UI for ASP.NET Ajax documentation and browse it locally.
 
 1. Clone the repository `git clone git@github.com:telerik/ajax-docs.git`
 2. Run `bundle install` (you must have ruby and bundler installed beforehand)
@@ -19,7 +19,7 @@ You can generate a static web site from the Telerik UI for ASP.NET AJAX document
 
 ## License
 
-The Telerik UI for ASP.NET AJAX Documentation is licensed under an MIT license. This license applies to the markdown (.md) files in this site **ONLY**, and does not convey, override or modify any existing licenses covering the runtime source and components of Telerik UI for ASP.NET AJAX. For information about available licenses for the Telerik UI for ASP.NET AJAX click [here](http://www.telerik.com/purchase/license-agreement/aspnet-ajax).
+The Telerik® UI for ASP.NET Ajax Documentation is licensed under an MIT license. This license applies to the markdown (.md) files in this site **ONLY**, and does not convey, override or modify any existing licenses covering the runtime source and components of Telerik® UI for ASP.NET Ajax. For information about available licenses for the Telerik® UI for ASP.NET Ajax click [here](http://www.telerik.com/purchase/license-agreement/aspnet-ajax).
 
 ### MIT License
 

_templates/button/distorted-appearance.md

@@ -13,7 +13,7 @@ The appearance of **@{control}** may be distorted (**Figure 1**) when the contro
 #cause-resolve
 ## Cause of the Problem
 
-Generally, controls from the Telerik UI for ASP.NET AJAX suite that use the same styles support only a single type of `RenderMode` per page. This also includes instances from user controls and master pages.
+Generally, controls from the Telerik® UI for ASP.NET Ajax suite that use the same styles support only a single type of `RenderMode` per page. This also includes instances from user controls and master pages.
 
 **RadButton**, **@{control}** and controls that utilize them, however, share similar resources. Since **@{control}** supports only a `Lightweight` `RenderMode`, its styles may interfere with the styles of the `Classic` **RadButton**. The improper appearance is shown in **Figure 1** and the code that creates it shown in **Example 1**.
 

_templates/common/additional-libraries-path.md

@@ -1,5 +1,5 @@
 #additional-libraries-path
-You can find @{assemblies} in the **AdditionalLibraries** folder in the **Telerik UI for ASP.NET AJAX** installation (automated and manual) and in the internal builds archive. @{support} .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the @{isplural} from the *Bin40* or *Bin45* folder respectively.
+You can find @{assemblies} in the **AdditionalLibraries** folder in the **Telerik® UI for ASP.NET Ajax** installation (automated and manual) and in the internal builds archive. @{support} .NET 4 and .NET 4.5, so depending on the target framework of your project, you need to take the @{isplural} from the *Bin40* or *Bin45* folder respectively.
 #end
 
 

_templates/common/render-mode.md

@@ -1,5 +1,5 @@
 #do-not-mix-modes
->important @{control}, as well as the other controls included in the Telerik UI for ASP.NET AJAX suite that utilize render modes, support only one type of render mode per page. This includes mode being set for a standalone @{control}. All such controls must have the same RenderMode on a given page.This also includes instances from user controls and master pages.
+>important @{control}, as well as the other controls included in the Telerik® UI for ASP.NET Ajax suite that utilize render modes, support only one type of render mode per page. This includes mode being set for a standalone @{control}. All such controls must have the same RenderMode on a given page.This also includes instances from user controls and master pages.
 #end
 
 

api/server/Telerik.Web.UI/RadGrid.md

@@ -957,7 +957,7 @@ Gets or sets the name of the Skin that Telerik RadGrid will use.
 
 #### Remarks
 There are three possible scenarios for using this property:Leave this property unset or set it to "Default" - the default skin,
-                    common for the Telerik UI for ASP.NET AJAX suite will be usedSet the name of the embedded grid skin - the skin will be appliedSet the name of the custom grid skin along with the EnableEmbeddedSkins="false" 
+                    common for the Telerik® UI for ASP.NET Ajax suite will be usedSet the name of the embedded grid skin - the skin will be appliedSet the name of the custom grid skin along with the EnableEmbeddedSkins="false" 
             (see 'Creating a custom skin' Fundamentals article)Set this property to "" - no skin will be applied.
                     Only the default grid images (for Expand/Collapse, Sort, Edit, etc) will be
                     used. Use this option if you have own appearance customizations for prevous

controls/button/appearance-and-styling/creating-a-custom-lightweight-skin.md

@@ -13,7 +13,7 @@ position: 4
 
 ## RadButton Custom Skin with LightWeight RenderMode
 
-Each of the controls included in the **Telerik UI for ASP.NET AJAX** suite is styled with two CSS files that are loaded in acertain order. The first one – **[ControlName].css** , also called base stylesheet, contains CSS properties and values that are commonfor all skins, i.e it is layout-specific, not skin-specific. These are CSS float, padding, margin, font-size, font-family, etc. In the general case, when creating	a custom skin for a control this file should not be edited, unless the custom skin needs different sizes, padding and / or margins.
+Each of the controls included in the **Telerik® UI for ASP.NET Ajax** suite is styled with two CSS files that are loaded in acertain order. The first one – **[ControlName].css** , also called base stylesheet, contains CSS properties and values that are commonfor all skins, i.e it is layout-specific, not skin-specific. These are CSS float, padding, margin, font-size, font-family, etc. In the general case, when creating	a custom skin for a control this file should not be edited, unless the custom skin needs different sizes, padding and / or margins.
 
 The second file represents the actual skin of the control, and its name consists of the control name plus the skin name, e.g. - **Button.Default.css**.Upon creating a custom skin for the control, one should edit that particular file, as it contains skin-specific CSS properties, and references to images, colors,borders and backgrounds.
 

controls/button/appearance-and-styling/creating-a-custom-skin.md

@@ -14,7 +14,7 @@ position: 4
 
 ## Creating RadButton Custom Skin
 
-Each of the controls included in the Telerik UI for ASP.NET AJAX suite is styled by two CSS files that are loaded in a certain order.The first one - ControlName.css, also called the base stylesheet contains CSS properties and values that are common for all skins, i.e., it is layout-specific, not skin-specific. These are CSS float, padding, margin, font-size, font-family, etc.In the general case, when creating a custom skin for a control this file should not be edited, unless the custom skin needs different sizes, paddings or margins.The second file represents the actual skin of the control, and its name consists of the control name plus the skin name, i.e. Button.Default.css. Upon creating a custom skin for the control,one should edit that particular file, as it contains skin-specific CSS properties, and references to images, colors, borders and backgrounds.
+Each of the controls included in the Telerik® UI for ASP.NET Ajax suite is styled by two CSS files that are loaded in a certain order.The first one - ControlName.css, also called the base stylesheet contains CSS properties and values that are common for all skins, i.e., it is layout-specific, not skin-specific. These are CSS float, padding, margin, font-size, font-family, etc.In the general case, when creating a custom skin for a control this file should not be edited, unless the custom skin needs different sizes, paddings or margins.The second file represents the actual skin of the control, and its name consists of the control name plus the skin name, i.e. Button.Default.css. Upon creating a custom skin for the control,one should edit that particular file, as it contains skin-specific CSS properties, and references to images, colors, borders and backgrounds.
 
 ## Creating a Custom Skin for RadButton for ASP.NET AJAX from an Existing One
 

controls/captcha/accessibility-and-internationalization/localization.md

@@ -12,7 +12,7 @@ position: 2
 
 The **RadCaptcha** provides a mechanism for quick and easy localization based on the native ASP.NET localization. The ErrorMessage, the Label telling the user to enter the code and the button labels are obtained from the resource files located in the App_LocalReources directory, so that the language of the **RadCaptcha** is automatically switched to the culture and UI culture of the Web page.
 
->note You can inspect these files by navigating to your Telerik UI for ASP.NET AJAX installation folder, then under **Live Demos** locate the **Captcha\Examples\Localization** directory as it also contains example audio codes.
+>note You can inspect these files by navigating to your Telerik® UI for ASP.NET Ajax installation folder, then under **Live Demos** locate the **Captcha\Examples\Localization** directory as it also contains example audio codes.
 
 Each of the localization strings can also be modified at runtime using the respective server-side properties: **ErrorMessage, CaptchaTextBoxLabel, CaptchaAudioLinkButtonText, and CaptchaLinkButtonText**. This eliminates the need to create a new localization file to change a single string. For example:
 

controls/captcha/changes-and-backward-compatibility/memory-consumption-increase.md

@@ -12,14 +12,14 @@ position: 1
 
 ## What has changed
 
-Since the Q2 2013 release of Telerik UI for ASP.NET AJAX we have introduced a CachingProvider that is responsible for storing the generated CapchaImage to the RadCaptcha control. This was done because previously the CapchaImage was incorrectly removed on each request, thus only single instance was preserved, and every subsequent request that is not a postback made the previous codes invalid.
-
+Since the Q2 2013 release of Telerik® UI for ASP.NET Ajax we have introduced a CachingProvider that is responsible for storing the generated CapchaImage to the RadCaptcha control. This was done because previously the CapchaImage was incorrectly removed on each request, thus only single instance was preserved, and every subsequent request that is not a postback made the previous codes invalid.
+
 With the applied fix, the control is expected to increase its memory consumption because now it is keeping CaptchaImage objects alive for specified time controlled by the property **CaptchaMaxTimeout** (default value is 20 minutes) utilizing application's Cache.
 
 ## How to decrease memory consumption
 
 The memory consumption of RadCaptcha can be reduced by one of the following approaches:
-
-* Decreasing the value of the **CaptchaMaxTimeout** property so that the lifetime of cached objects is shorter and the memory usage depends on the stream of application users;
+
+* Decreasing the value of the **CaptchaMaxTimeout** property so that the lifetime of cached objects is shorter and the memory usage depends on the stream of application users;
 
 * Implementing custom CachingProvider that utilizes different type of storage for the generated CaptchaImage objects. This approach is described in the help article [Caching Provider]({%slug captcha/functionality/caching-provider%});

controls/captcha/functionality/caching-provider.md

@@ -10,7 +10,7 @@ position: 0
 
 # Caching Provider
 
-Since the Q2 2013 SP1 release of Telerik UI for ASP.NET AJAX, the RadCaptcha makes it possible to create a custom caching provider that allows specifying a storage for the captcha code different than the cache and the session.
+Since the Q2 2013 SP1 release of Telerik® UI for ASP.NET Ajax, the RadCaptcha makes it possible to create a custom caching provider that allows specifying a storage for the captcha code different than the cache and the session.
 
 The following example demonstrates how to utilize a MS SQL database for this purpose: