replace .net core to use the placeholders

dessyordanova · dessyordanova · commit b7e4c54ccc26 · 2025-04-30T17:28:34.000+03:00
diff --git a/getting-started/Installation/nuget-packages.md b/getting-started/Installation/nuget-packages.md
@@ -18,7 +18,7 @@ If your workflow relies on NuGet for package management, you can take advantage
 
 #### This article contains the following sections:
 
-* [NuGet packages for .NET Framework and .NET Core for Windows](#packages-for-net-framework-and-net-core-for-windows)
+* [NuGet packages for .NET Framework and {{site.dotnetversions}} for Windows](#packages-for-net-framework-and-net-core-for-windows)
 * [Packages for .NET Standard 2.0 (Support for {{site.dotnetversions}})](#packages-for-net-standard-20-net-core-net-6-net-8)
 * [Get the NuGet Packages](#get-the-nuget-packages)
 
@@ -37,9 +37,9 @@ If your workflow relies on NuGet for package management, you can take advantage
 
 >important The .NET Standard packages are compatible with any .NET version (e.g .NET 9), even if there are no packages explicitly available for the specific versions. The same applies to the .NET Framework packages.
 
-## Packages for .NET Framework and .NET Core for Windows
+## Packages for .NET Framework and {{site.dotnetversions}} for Windows
 
-The following list represents the available NuGet packages for the Document Processing libraries that you can use with the .NET Framework or .NET Core for Windows. Although we offer them as an addition to the Telerik UI components, you can use them without any UI components:
+The following list represents the available NuGet packages for the Document Processing libraries that you can use with the .NET Framework or {{site.dotnetversions}} for Windows. Although we offer them as an addition to the Telerik UI components, you can use them without any UI components:
 
 * __Telerik.Windows.Documents.Core:__ The main NuGet package for the Telerik Document Processing libraries. Required when you plan to use the library.
 * __Telerik.Windows.Documents.Fixed:__ The package is required when processing `PDF` documents.
diff --git a/knowledge-base/distribute-telerik-document-processing-libraries-net-versions.md b/knowledge-base/distribute-telerik-document-processing-libraries-net-versions.md
@@ -1,8 +1,8 @@
 ---
 title: What Versions of Document Processing Libraries are Distributed with the Telerik Products
-description: Learn how to obtain Telerik Document Processing libraries suitable for .NET Framework, .NET Standard, .NET Core, .NET 6, and newer versions.
+description: Learn how to obtain Telerik Document Processing libraries suitable for .NET Framework, .NET Standard, {{site.dotnetversions}} and newer versions.
 type: how-to
-page_title: How to Obtain Telerik Document Processing Libraries for .NET Framework, .NET Standard, .NET Core, .NET 6, and newer versions
+page_title: How to Obtain Telerik Document Processing Libraries for .NET Framework, .NET Standard, {{site.dotnetversions}} and newer versions
 slug: distribute-telerik-document-processing-libraries-net-versions
 tags: telerik, document, processing, net, core, nuget, packages, framework, windows, distribute, libraries, standard
 res_type: kb
@@ -42,7 +42,7 @@ Depending on the product suite you are using (Telerik UI for WinForms, WPF, ASP.
 
 As the above screenshots shows, the respective NuGet package indicates the exact target frameworks version considering the application's Target framework and Target OS. All versions are available as [NuGet packages]({%slug installation-nuget-packages%}). The assemblies/packages for .NET Standard do not contain the word *Windows* in their name.
 
->note There are no implementation/functionality differences between the Document Processing versions for .NET Framework and .NET Core/.NET 6 (or newer). However, the .NET Standard version comes with some limitations. More information about the limitations can be found in the [Cross-Platform Support]({%slug radpdfprocessing-cross-platform%}) article.
+>note There are no implementation/functionality differences between the Document Processing versions for .NET Framework and {{site.dotnetversions}} (or newer). However, the .NET Standard version comes with some limitations. More information about the limitations can be found in the [Cross-Platform Support]({%slug radpdfprocessing-cross-platform%}) article.
 
 ### Download the Libraries
 
diff --git a/knowledge-base/handle-no-nuget-packages-found-message.md b/knowledge-base/handle-no-nuget-packages-found-message.md
@@ -1,8 +1,8 @@
 ---
-title: Handling the 'No packages found" Message when Using the Telerik NuGet Server
-description: Learn how to handle the 'No packages found" message when using the Telerik NuGet Server
+title: Handling the 'No packages found' Message when Using the Telerik NuGet Server
+description: Learn how to handle the 'No packages found' message when using the Telerik NuGet Server
 type: how-to
-page_title: How to handle the 'No packages found" message when using the Telerik NuGet Server
+page_title: How to handle the 'No packages found' message when using the Telerik NuGet Server
 slug: handle-no-nuget-packages-found-message
 tags: telerik, nuget, server, package, dpl, document, processing
 res_type: kb
diff --git a/knowledge-base/resolving-namespace-conflicts.md b/knowledge-base/resolving-namespace-conflicts.md
@@ -32,7 +32,7 @@ This knowledge base article also answers the following questions:
 
 ## Solution
 
-Depending on the target framework of your project (NET Framework, .NET Standard .NET Core, .NET 6, etc.), you should install the library version accordingly. However, if you need to install both versions for any reason, to resolve the compile-time error caused by the conflicting `Workbook` type in both assemblies, utilize the C# [extern alias](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/extern-alias) feature. This approach allows you to differentiate between assemblies and use types from both without conflict. Follow the steps below:
+Depending on the target framework of your project (NET Framework, .NET Standard, {{site.dotnetversions}}, etc.), you should install the library version accordingly. However, if you need to install both versions for any reason, to resolve the compile-time error caused by the conflicting `Workbook` type in both assemblies, utilize the C# [extern alias](https://learn.microsoft.com/en-us/dotnet/csharp/language-reference/keywords/extern-alias) feature. This approach allows you to differentiate between assemblies and use types from both without conflict. Follow the steps below:
 
 1. **Assign Alias to NuGet Packages**
    - For the `Telerik.Documents.Spreadsheet` NuGet package, set its alias to `StandardHelper` (or any preferred alias).
diff --git a/libraries/radpdfprocessing/cross-platform/overview.md b/libraries/radpdfprocessing/cross-platform/overview.md
@@ -28,7 +28,7 @@ To export images different than Jpeg and Jpeg2000 or ImageQuality different than
 * **Telerik.Documents.ImageUtils.dll**
 <br><sub>_This assembly is not available in UI for Xamarin._</sub>
 
-> Note that for .NET Framework & .NET Core with Windows Compatibility Pack projects, the references contain "Windows" in their names (e.g. **Telerik.Windows.Documents.Core.dll**)
+> Note that for .NET Framework, {{site.dotnetversions}} with Windows Compatibility Pack projects, the references contain "Windows" in their names (e.g. **Telerik.Windows.Documents.Core.dll**)
 
 ## Fonts and Images
 
diff --git a/libraries/radspreadprocessing/cross-platform-support/cross-platform.md b/libraries/radspreadprocessing/cross-platform-support/cross-platform.md
@@ -33,7 +33,7 @@ To use the model of **RadSpreadProcessing** in your cross-platform project, you
 
 >note The **Telerik.Documents.ImageUtils.dll** assembly depends on **SkiaSharp**. In order to use this assembly, you will need to add a reference to [SkiaSharp](https://www.nuget.org/packages/SkiaSharp/). With the [R2 2023 changes](https://docs.telerik.com/devtools/document-processing/libraries/radpdfprocessing/changes-and-backward-compatibility/backward-compatibility#whats-different-in-2023-r2) SkiaSharp replaced ImageSharp as the required dependency.
 
-> Note that for .NET Framework & .NET Core with Windows Compatibility Pack projects, the references contain "Windows" in their names (e.g. **Telerik.Windows.Documents.Core.dll**)
+> Note that for .NET Framework, {{site.dotnetversions}} with Windows Compatibility Pack projects, the references contain "Windows" in their names (e.g. **Telerik.Windows.Documents.Core.dll**)
 
 ## What's Different Between .NET Framework and .NET Standard versions of SpreadProcessing
 
diff --git a/libraries/radspreadstreamprocessing/getting-started.md b/libraries/radspreadstreamprocessing/getting-started.md
@@ -58,7 +58,7 @@ In order to use **RadSpreadStreamProcessing** in your project, you will need to
 </tbody>
 </table>
 
->note The binaries compatible with .NET Standard are distributed with the packages targeting .NET Standard and .NET Core. For the full list of suites including Telerik Document Processing, check the [Installing on Your Computer]({%slug installation-installing-on-your-computer%}) help topic. There are **NuGet** packages as well that you can access if you have a license for one of the above mentioned suites.
+>note The binaries compatible with .NET Standard are distributed with the packages targeting .NET Standard and {{site.dotnetversions}}. For the full list of suites including Telerik Document Processing, check the [Installing on Your Computer]({%slug installation-installing-on-your-computer%}) help topic. There are **NuGet** packages as well that you can access if you have a license for one of the above mentioned suites.
 
 ## Create a Spreadsheet Document
 
