addressed Yoan's feedback

Author: dessyordanova

getting-started/Installation/nuget-packages.md

@@ -82,3 +82,4 @@ The following list represents the available NuGet packages for the Document Proc
 
  * [Restoring NuGet Packages in Your CI Workflow]({%slug using-nuget-keys%})
  * [How to Obtain Telerik Document Processing Libraries for .NET Framework, .NET Standard, .NET Core, .NET 6/.NET 8/.NET 9]({%slug distribute-telerik-document-processing-libraries-net-versions%})
+ * [Resolving Namespace Conflicts in Telerik Document Processing Libraries]({%slug radspreadprocessing-resolving-namespace-conflicts%})

knowledge-base/resolving-namespace-conflicts.md

@@ -1,10 +1,10 @@
 ---
 title: Resolving Namespace Conflicts in Telerik Document Processing Libraries
-description: This article demonstrates how to resolve namespace conflicts when using Telerik Document Processing in a .NET Core project with both .NET Standard and .NET Framework versions installed.
+description: This article demonstrates how to resolve namespace conflicts when using Telerik Document Processing in a .NET Core project with both .NET Standard and .NET Framework packages/assemblies referenced.
 type: how-to
 page_title: How to Fix Namespace Conflicts in RadSpreadProcessing for Document Processing
 slug: radspreadprocessing-resolving-namespace-conflicts
-tags: radspreadprocessing, document processing, namespace, extern alias, .net core, .net standard
+tags: spreadprocessing, document, processing, namespace, extern, alias, net, core, standard
 res_type: kb
 ticketid: 1673450
 ---
@@ -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 accordinglyt. 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 .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:
 
 1. **Assign Alias to NuGet Packages**
    - For the `Telerik.Documents.Spreadsheet` NuGet package, set its alias to `StandardHelper` (or any preferred alias).

troubleshooting/telerik-nuget.md

@@ -99,4 +99,8 @@ Another common problem is that your machine (PC, GitHub Actions runner or Azure
 
 * https://nuget.telerik.com/nuget/Search()?$filter=IsAbsoluteLatestVersion&searchTerm=%27WPF%27&includePrerelease=true&$skip=0&$top=100&semVerLevel=2.0.0. 
 
-After you enter your telerik.com username and password, you should see an XML search result containing a list of all the Telerik.UI.for.WPF packages available with your license.
+After you enter your telerik.com username and password, you should see an XML search result containing a list of all the Telerik.UI.for.WPF packages available with your license.
+
+## See Also
+
+ * [Resolving Namespace Conflicts in Telerik Document Processing Libraries]({%slug radspreadprocessing-resolving-namespace-conflicts%})