Updated information about the version of the assemblies from TDP

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

@@ -17,6 +17,15 @@ This article lists the breaking changes and how they can be fixed when upgrading
 ## 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.

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/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