Updated information for R3 2016

installation-and-deployment/installing-on-your-computer.md

@@ -12,9 +12,11 @@ position: 1
 
 Telerik Document Processing is part of several Telerik bundles and is installed following the steps for installing the suite with which you've obtained the product.
 
-Starting from Q1 2016, the Document Processing Libraries are built separately from any other component that comes with the different suites. Thus, they have their own version, which may differ with the version of the other assemblies in the particular suite. 
-
-This change is synced between the controls that have a dependency on Telerik Document Processing and while the referenced files are from the same release, they should work as expected regardless of the version distinction. 
+>Starting from Q1 2016, the Document Processing assemblies have an assembly version which may differ from the assembly version of the other assemblies in the particular suite. 
+>
+>Starting from R3 2016, only assemblies with a version number ending with .40 suffix are distributed. The libraries don't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+>
+>The changes are synced between the controls that have a dependency on Telerik Document Processing and while the referenced files are from the same release, they should work as expected regardless of the version distinction. 
 
 
 ## UI for ASP.NET AJAX

installation-and-deployment/upgrade-instructions.md

@@ -12,9 +12,12 @@ position: 2
 
 Telerik Document Processing is part of several Telerik bundles and could be upgraded following the steps for upgrading the other assemblies from the suite with which you've obtained the product.
 
-Starting from Q1 2016, the Document Processing Libraries are built separately from any other component that comes with the different suites. Thus, they have their own version, which may differ with the version of the other assemblies in the particular suite. 
+>Starting from Q1 2016, the Document Processing assemblies have an assembly version which may differ from the assembly version of the other assemblies in the particular suite. 
+>
+>Starting from R3 2016, only assemblies with a version number ending with .40 suffix are distributed. The libraries don't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+>
+>The changes are synced between the controls that have a dependency on Telerik Document Processing and while the referenced files are from the same release, they should work as expected regardless of the version distinction. 
 
-This change is synced between the controls that have a dependency on Telerik Document Processing and while the referenced files are from the same release, they should work as expected regardless of the version distinction. 
 
 
 ## UI for ASP.NET AJAX

libraries/radpdfprocessing/changes-and-backward-compatibility/backward-compatibility.md

@@ -14,6 +14,23 @@ position: 1
 
 This article lists the breaking changes and how they can be fixed when upgrading from a specific version of the controls to another.
 
+## What's Different in 2016 R3  
+
+
+### Changed
+
+Assemblies with a version number ending with .45 suffix are **not** distributed.
+
+### What to do now
+
+Use the assemblies with a version number ending with .40 suffix. The library doesn't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+
+
+### Changed
+
+Telerik.Windows.Documents.Fixed.Model.RadFixedDocument::Merge() doesn't remove the content from the source document after appending it to the targeted one.
+
+
 ## What's Different in 2015 Q1      
 
 

libraries/radpdfprocessing/model/radfixeddocument.md

@@ -76,16 +76,24 @@ __Example 3__ creates a page and adds it to the document created in [__Example 1
     document.Pages.Add(page);
 {{endregion}}
 
+**Example 4** shows you how you could obtain a copy of a RadFixedDocument.
 
-Since Q2 2015 you can merge PDF documents out-of-the-box with the Merge() method of __RadFixedDocument__. This method appends the source document to the current instance of __RadFixedDocument__.
+#### __[C#] Example 4: Clone a document__
 
-#### __[C#] Example 4: Merge documents__
+{{region radpdfprocessing-model-radfixeddocument_5}}
+	RadFixedDocument clonedDocument = originalDocument.Clone();
+{{endregion}}
 
-{{region radpdfprocessing-model-radfixeddocument_3}}
+
+You can merge PDF documents out-of-the-box with the Merge() method of __RadFixedDocument__. This method clones the source document and appends it to the current instance of __RadFixedDocument__.
+
+#### __[C#] Example 5: Merge documents__
+
+{{region radpdfprocessing-model-radfixeddocument_4}}
 	document.Merge(source);
 {{endregion}}
 
-The code from __Example 4__ will merge the document created in [__Example 1__](#example1) with another __RadFixedDocument__.
+The code from __Example 5__ merges the document created in [__Example 1__](#example1) with another __RadFixedDocument__.
 
 ## Document Information
 
@@ -95,7 +103,7 @@ __RadFixedDocument__ exposes a __DocumentInfo__ property of type __RadFixedDocum
 * __Title__: The title of the document.
 * __Description__: Text that describes the content of the document.
 
-#### __[C#] Example 5: Set DocumentInfo__
+#### __[C#] Example 6: Set DocumentInfo__
 
 {{region radpdfprocessing-model-radfixeddocument_3}}
 	document.DocumentInfo.Author = "Jane Doe";

libraries/radspreadprocessing/changes-and-backward-compatibility/backwards-compatibility.md → libraries/radspreadprocessing/changes-and-backward-compatibility/backward-compatibility.md

@@ -3,17 +3,29 @@ title: Backwards Compatibility
 page_title: Backwards Compatibility
 description: Backwards Compatibility
 slug: radspreadprocessing-backwards-compatibility
-tags: backwards,compatibility
+tags: backward,compatibility
 published: True
 position: 1
 ---
 
-# Backwards Compatibility
+# Backward Compatibility
 
 
 
 This article will list the breaking changes and how they can be fixed when upgrading from a specific version of the controls to the next one.
 
+## What's Different in 2016 R3  
+
+
+### Changed
+
+Assemblies with a version number ending with .45 suffix are **not** distributed.
+
+### What to do now
+
+Use the assemblies with a version number ending with .40 suffix. The library doesn't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+
+
 ## What's Different in 2016 Q1
 
 ### Changed

libraries/radspreadstreamprocessing/changes-and-backward-compatibility/backward-compatibility.md

@@ -0,0 +1,26 @@
+---
+title: Backward Compatibility
+page_title: Backward Compatibility
+description: Backward Compatibility
+slug: radspreadstreamprocessing-backward-compatibility
+tags: backward,compatibility
+published: True
+position: 1
+---
+
+# Backward Compatibility
+
+
+
+This article lists the breaking changes and how they can be fixed when upgrading from a specific version of the controls to the next one.
+
+## What's Different in 2016 R3  
+
+
+### Changed
+
+Assemblies with a version number ending with .45 suffix are **not** distributed.
+
+### What to do now
+
+Use the assemblies with a version number ending with .40 suffix. The library doesn't contain code specific for .NET Framework 4.5, thus an additional version is not needed.

libraries/radwordsprocessing/changes-and-backward-compatibility/backward-compatibility.md

@@ -0,0 +1,26 @@
+---
+title: Backward Compatibility
+page_title: Backward Compatibility
+description: Backward Compatibility
+slug: radwordsprocessing-backward-compatibility
+tags: backward,compatibility
+published: True
+position: 1
+---
+
+# Backward Compatibility
+
+
+
+This article lists the breaking changes and how they can be fixed when upgrading from a specific version of the controls to the next one.
+
+## What's Different in 2016 R3  
+
+
+### Changed
+
+Assemblies with a version number ending with .45 suffix are **not** distributed.
+
+### What to do now
+
+Use the assemblies with a version number ending with .40 suffix. The library doesn't contain code specific for .NET Framework 4.5, thus an additional version is not needed.

libraries/radwordsprocessing/formats-and-conversion/html/settings.md

@@ -132,6 +132,9 @@ Specifies whether the exported document should be indented (formatted with space
 This property is used to control how images are exported. The available options are as external file or as embedded images.
 
 > When an image with Uri source is imported, the ImageSource property of the Image contains object of type UriImageSource. Hence, the image is always exported with URI and the __ImagesExportMode__ property is not respected. If you need this property to be respected, you could convert the **UriImageSource** object to __ImageSource__.
+
+<p>
+>When working with relative URI, the import/export functionalities only preserve the path to the image and do not modify it.
 
 ### ImagesFolderPath
 

libraries/radziplibrary/changes-and-backwards-compatibility/backward-compatibility.md

@@ -14,6 +14,18 @@ position: 1
 
 This article lists the breaking changes and how they can be fixed when upgrading from a specific version of the controls to the next one.
 
+## What's Different in 2016 R3  
+
+
+### Changed
+
+Assemblies with a version number ending with .45 suffix are **not** distributed.
+
+### What to do now
+
+Use the assemblies with a version number ending with .40 suffix. The library doesn't contain code specific for .NET Framework 4.5, thus an additional version is not needed.
+
+
 ## What's Different in 2015 Q1 - 2015.1.0225