Added missed trademark symbol in WPF UG common files.

Author: YuvarajMasilamani

wpf/Add-Syncfusion-Controls.md

@@ -160,7 +160,7 @@ Syncfusion<sup>&reg;</sup> provides the Visual Studio Project Templates for the
 
 I> The Syncfusion<sup>&reg;</sup> WPF templates are available from v16.1.0.24. 
 
-### Create Syncfusion WPF project 
+### Create Syncfusion<sup>&reg;</sup> WPF project 
 
 The following steps direct you to create the Syncfusion<sup>&reg;</sup> WPF project using the Visual Studio Project Template. 
 
@@ -200,6 +200,6 @@ N> Minimum target Framework is 4.0 for Syncfusion<sup>&reg;</sup> WPF project te
 
 ![Shows project folder for added control](Add-Syncfusion-Control_images\Syncfusion-Project-Template-Gallery-8.png)
 
-5. Then, Syncfusion<sup>&reg;</sup> licensing registration required message box will be shown as follows, if you have installed the trial setup or NuGet packages since Syncfusion introduced the licensing system with the 2018 Volume 2 (v16.2.0.41) Essential Studio release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion<sup>&reg;</sup> license key for your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio.
+5. Then, Syncfusion<sup>&reg;</sup> licensing registration required message box will be shown as follows, if you have installed the trial setup or NuGet packages since Syncfusion introduced the licensing system with the 2018 Volume 2 (v16.2.0.41) Essential Studio<sup>&reg;</sup> release. Please navigate to the [help topic](https://help.syncfusion.com/common/essential-studio/licensing/license-key#how-to-generate-syncfusion-license-key), which is shown in the licensing message box to generate and register the Syncfusion<sup>&reg;</sup> license key for your project. Refer to this [blog](https://blog.syncfusion.com/post/Whats-New-in-2018-Volume-2-Licensing-Changes-in-the-1620x-Version-of-Essential-Studio.aspx) post for understanding the licensing changes introduced in Essential Studio<sup>&reg;</sup>.
 
 ![Shows syncfusion license registration message](Add-Syncfusion-Control_images\Syncfusion-Project-Template-Gallery-9.png)

wpf/Pattern-and-Practices.md

@@ -10,7 +10,7 @@ documentation: ug
 
 ## Getting Started with MVVM
 
-Essential WPF controls are suitable for MVVM Pattern. Since, the controls are provided with built-in commands. 
+Essential<sup>&reg;</sup> WPF controls are suitable for MVVM Pattern. Since, the controls are provided with built-in commands. 
 
 The `DataContext` property specifies the default source for Data Binding in MVVM pattern.
 

wpf/Themes/Skin-Manager.md

@@ -866,7 +866,7 @@ private void Window_Closed(object sender, EventArgs e)
 <tr><td>Window</td><td>WPFWindowStyle</td></tr>
 </table>
 
-### Syncfusion Controls
+### Syncfusion<sup>&reg;</sup> Controls
 
 <table>
 <tr><th>Control Name</th><th>Key Name</th></tr>

wpf/VPAT.md

@@ -9,7 +9,7 @@ documentation: ug
 
 # Section 508 Compliance - Voluntary Product Accessibility Template
 
-The following Voluntary Product Accessibility information refers to Syncfusion Essential Studio for WPF.
+The following Voluntary Product Accessibility information refers to Syncfusion<sup>&reg;</sup> Essential Studio<sup>&reg;</sup> for WPF.
 
 <table>
 <tr>
@@ -187,5 +187,5 @@ Essential Studio WPF controls are accessible<br/><br/></td></tr>
 Supported.<br/><br/></td><td>
 Online support <a href="https://www.syncfusion.com/support/directtrac/incidents">Incidents</a> and <a href="https://www.syncfusion.com/support/directtrac/forums">Forums</a> are available.<br/><br/></td></tr>
 </table>
-Syncfusion does not promise that the information provided in this document will be error-free, or that any errors will be corrected, or that your use of the information will provide specific results. The document and its content are delivered on an “as-is” basis. All information provided is subject to change without notice. Syncfusion disclaims all warranties, express or implied, including any warranties of accuracy, non-infringement, merchantability and fitness for a particular purpose.
+Syncfusion<sup>&reg;</sup> does not promise that the information provided in this document will be error-free, or that any errors will be corrected, or that your use of the information will provide specific results. The document and its content are delivered on an “as-is” basis. All information provided is subject to change without notice. Syncfusion<sup>&reg;</sup> disclaims all warranties, express or implied, including any warranties of accuracy, non-infringement, merchantability and fitness for a particular purpose.
 

wpf/dotnet-core-compatibility.md

@@ -11,7 +11,7 @@ documentation: ug
 
 Syncfusion<sup>&reg;</sup> Essential Studio<sup>&reg;</sup> for WPF ships .NET Core assemblies for building WPF .NET Core applications using Syncfusion<sup>&reg;</sup> Controls. This section explains how to create the project in .NET Core application and using syncfusion<sup>&reg;</sup> WPF controls.
 
-N> All Syncfusion WPF controls supports .NET Core except the controls labeled as `classic`.
+N> All Syncfusion<sup>&reg;</sup> WPF controls supports .NET Core except the controls labeled as `classic`.
 
 ## Version Compatibility