syncfusion-content · MathanKumarVaradhaRajaPerumal · Jul 23, 2026 · Jul 23, 2026 · Jul 23, 2026 · Jul 23, 2026
diff --git a/.../Word/Conversions/Word-To-Image/NET/Convert-Word-Document-to-Image-in-Blazor.md b/.../Word/Conversions/Word-To-Image/NET/Convert-Word-Document-to-Image-in-Blazor.md
@@ -737,12 +737,6 @@ Step 2: Install the following **Nuget packages** in application from [Nuget.org]
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-image/net/nuget-packages-required-word-to-image#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart Visual Studio to ensure proper integration of the tools.
-
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 
 Add the following namespaces in the file:
@@ -926,11 +920,7 @@ Step 2: To **convert a Word document to Image in Blazor WASM Standalone app**, i
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-image/net/nuget-packages-required-word-to-image#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart Visual Studio Code to ensure proper integration of the tools.
+
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 
@@ -1134,11 +1124,6 @@ Step 2: Install the NuGet package from [NuGet.org](https://www.nuget.org/).
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-image/net/nuget-packages-required-word-to-image#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart JetBrains Rider to ensure proper integration of the tools.
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 

diff --git a/...-Processing/Word/Conversions/Word-To-PDF/NET/Assemblies-required-word-to-pdf.md b/...-Processing/Word/Conversions/Word-To-PDF/NET/Assemblies-required-word-to-pdf.md
@@ -43,6 +43,8 @@ T> 1. If you encounter issues while using the .NET Word library in ASP.NET Core,
 T> 2. Switch to NuGet packages for a seamless experience:
 T>    * Get frequent bug fixes every week.
 T>    * Upgrade quickly with no manual effort.
+
+
 N> To avoid a trial watermark when using NuGet packages, it is recommended to register a license key in the application. Please refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in your application to use our components.
 N>
 N> Refer [here](https://help.syncfusion.com/document-processing/word/conversions/word-to-pdf/net/nuget-packages-required-word-to-pdf) to know more about NuGet packages required.

diff --git a/...ns/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Azure-App-Service-Windows.md b/...ns/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Azure-App-Service-Windows.md
@@ -224,7 +224,7 @@ An online sample link to [convert Word document to PDF](https://document.syncfus
 
 ## See Also
 
-- [Convert Word to PDF in Azure App Service on Linux](convert-word-document-to-pdf-in-azure-app-service-linux.md)
+- [Convert Word to PDF in Azure App Service on Linux](convert-word-document-to-pdf-in-azure-app-service-linux)
 - [Convert Word to PDF in Azure App Service Windows (Console / SDK sample)](https://github.com/SyncfusionExamples/DocIO-Examples/tree/main/Word-to-PDF-Conversion/Convert-Word-document-to-PDF/Azure/Azure_App_Service)
 - [Syncfusion<sup>&reg;</sup> licensing overview](https://help.syncfusion.com/common/essential-studio/licensing/overview)
-- [DocIO NuGet packages required for Word to PDF conversion](nuget-packages-required-word-to-pdf.md)
+- [DocIO NuGet packages required for Word to PDF conversion](nuget-packages-required-word-to-pdf)
diff --git a/...nversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Azure-Functions-v4.md b/...nversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Azure-Functions-v4.md
@@ -21,7 +21,7 @@ Step 2: Create a project name and select the location.
 Step 3: Configure the project's additional information (Storage account, Authorization level).
 ![Select function worker](Azure-Images/Functions-v4/Additional-Information-WordtoPDF.png)
 
-Step 4: Install the [Syncfusion.DocIO.Net.Core](https://www.nuget.org/packages/Syncfusion.DocIO.Net.Core) and [Syncfusion.DocIORenderer.Net.Core](https://www.nuget.org/packages/Syncfusion.DocIORenderer.Net.Core) NuGet packages in your project from [NuGet.org](https://www.nuget.org/).
+Step 4: Install the [Syncfusion.DocIORenderer.Net.Core](https://www.nuget.org/packages/Syncfusion.DocIORenderer.Net.Core) NuGet package in your project from [NuGet.org](https://www.nuget.org/).
 ![Install Syncfusion.DocIO.Net.Core and DocIORenderer.Net.Core NuGet packages](Azure-Images/Functions-v4/Nuget-Package-WordtoPDF.png)
 
 N> Starting with v16.2.0.x, if you reference Syncfusion<sup>&reg;</sup> assemblies from trial setup or from the NuGet feed, you also have to add the "Syncfusion.Licensing" assembly reference and include a license key in your projects. Please refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering the Syncfusion<sup>&reg;</sup> license key in your application to use our components.

diff --git a/...sing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Blazor.md b/...sing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Blazor.md
@@ -45,7 +45,7 @@ N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are refe
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder, which is located inside the `Components` folder (`Components/Pages/DocIO.razor`).
 
-> **Note:** The `@rendermode InteractiveServer` directive requires that the `<Routes>` component in `App.razor` be updated to `<Routes @rendermode="InteractiveServer" />` so the interactive rendering mode is available to pages.
+N> The `@rendermode InteractiveServer` directive requires that the `<Routes>` component in `App.razor` be updated to `<Routes @rendermode="InteractiveServer" />` so the interactive rendering mode is available to pages.
 
 Include the following namespaces in the file:
 
@@ -102,11 +102,6 @@ Include the following code in `WordService.cs`. This adds the required `using` d
 {% tabs %}
 
 {% highlight c# tabtitle="C#" %}
-using Syncfusion.DocIO;
-using Syncfusion.DocIO.DLS;
-using Syncfusion.DocIORenderer;
-using Syncfusion.Pdf;
-using System.IO;
 
 namespace Convert_Word_Document_to_PDF.Data
 {
@@ -162,7 +157,6 @@ Create a new class file named `FileUtils.cs` at the project root and add the fol
 {% tabs %}
 
 {% highlight c# tabtitle="C#" %}
-using Microsoft.JSInterop;
 
 namespace Convert_Word_Document_to_PDF
 {
@@ -338,11 +332,6 @@ Include the following code in `WordService.cs`. This adds the required `using` d
 {% tabs %}
 
 {% highlight c# tabtitle="C#" %}
-using System.IO;
-using Syncfusion.DocIO;
-using Syncfusion.DocIO.DLS;
-using Syncfusion.DocIORenderer;
-using Syncfusion.Pdf;
 
 namespace Convert_Word_Document_to_PDF.Data
 {
@@ -594,11 +583,6 @@ Include the following code in `WordService.cs`. This adds the required `using` d
 {% tabs %}
 
 {% highlight c# tabtitle="C#" %}
-using Syncfusion.DocIO;
-using Syncfusion.DocIO.DLS;
-using Syncfusion.DocIORenderer;
-using Syncfusion.Pdf;
-using System.IO;
 
 namespace Convert_Word_Document_to_PDF.Data
 {
@@ -768,11 +752,7 @@ Step 2: Install the following **NuGet packages** in the application from [NuGet.
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-pdf/net/nuget-packages-required-word-to-pdf#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart Visual Studio to ensure proper integration of the tools.
+
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 
@@ -973,11 +953,7 @@ Step 2: To **convert a Word document to PDF in the Blazor WebAssembly Standalone
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-pdf/net/nuget-packages-required-word-to-pdf#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart Visual Studio Code to ensure proper integration of the tools.
+
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 
@@ -1196,11 +1172,6 @@ Step 2: Install the NuGet packages from [NuGet.org](https://www.nuget.org/).
 
 N> 1. If deploying the application in a Linux environment, refer to the [documentation](https://help.syncfusion.com/document-processing/word/conversions/word-to-pdf/net/nuget-packages-required-word-to-pdf#additional-nuget-packages-required-for-linux) for the required additional NuGet packages.
 N> 2. Starting with v16.2.0.x, if Syncfusion<sup>&reg;</sup> assemblies are referenced from trial setup or from the NuGet feed, the "Syncfusion.Licensing" assembly reference must also be added and a license key included in projects. Refer to this [link](https://help.syncfusion.com/common/essential-studio/licensing/overview) to know about registering Syncfusion<sup>&reg;</sup> license key in an application to use Syncfusion components.
-N> 3. If you face issues related to SkiaSharp during runtime, install the necessary WebAssembly tools by running the following commands in the terminal:
-N> ```
-N> dotnet workload install wasm-tools
-N> ```
-N> After completing the installation, restart JetBrains Rider to ensure proper integration of the tools.
 
 Step 3: Create a Razor file named `DocIO.razor` in the `Pages` folder.
 

diff --git a/...ssing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-WinUI.md b/...ssing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-WinUI.md
@@ -12,7 +12,7 @@ Syncfusion<sup>&reg;</sup> DocIO is a [.NET Word library](https://www.syncfusion
 
 ## Prerequisites
 - Install the Windows App SDK extension for Visual Studio. For more details, refer [here](https://learn.microsoft.com/en-us/windows/apps/windows-app-sdk/set-up-your-development-environment?tabs=cs-vs-community%2Ccpp-vs-community%2Cvs-2022-17-1-a%2Cvs-2022-17-1-b).
-- Supported environment: Visual Studio 2022 (17.x) with the Windows App SDK 1.x workload on Windows 10 (build 17763 or later) or Windows 11.
+- Supported environment: **Visual Studio 2022 or later** with the **Windows App SDK** workload on Windows 10 (build 17763 or later) or Windows 11.
 
 ## WinUI Desktop app
 
@@ -24,7 +24,7 @@ Step 2: Enter the project name and click **Create** button.
 
 ![Create a project name for your new project](WinUI_Images/Project-Name-WinUI-WordtoPDF.png)
 
-Step 3: Install [Syncfusion.DocIORenderer.NET](https://www.nuget.org/packages/Syncfusion.DocIORenderer.NET) and [Syncfusion.DocIO.NET](https://www.nuget.org/packages/Syncfusion.DocIO.NET) NuGet packages as references to your WinUI Desktop application from the [NuGet.org](https://www.nuget.org/).
+Step 3: Install [Syncfusion.DocIORenderer.NET](https://www.nuget.org/packages/Syncfusion.DocIORenderer.NET) NuGet package as references to your WinUI Desktop application from the [NuGet.org](https://www.nuget.org/).
 
 ![Syncfusion.DocIORenderer.NET NuGet package](WinUI_Images/Nuget-Package-WordtoPDF.png)
 

diff --git a/...ing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Xamarin.md b/...ing/Word/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-PDF-in-Xamarin.md
@@ -10,7 +10,7 @@ documentation: UG
 
 Syncfusion<sup>&reg;</sup> DocIO is a [.NET Word library](https://www.syncfusion.com/document-sdk/net-word-library) used to create, read, edit, and **convert Word documents** programmatically without **Microsoft Word** or **interop** dependencies. Using this library, you can **convert a Word document to PDF in Xamarin**.
 
-N> **Platform status:** Xamarin and Xamarin.Forms are in maintenance mode. Microsoft recommends migrating to [.NET MAUI](https://learn.microsoft.com/en-us/dotnet/maui/) for new development. For an equivalent guide for .NET MAUI, refer to [Convert Word Document to PDF in .NET MAUI](convert-word-document-to-pdf-in-maui.md).
+N> **Platform status:** Xamarin and Xamarin.Forms are in maintenance mode. Microsoft recommends migrating to [.NET MAUI](https://learn.microsoft.com/en-us/dotnet/maui/) for new development. For an equivalent guide for .NET MAUI, refer to [Convert Word Document to PDF in .NET MAUI](convert-word-document-to-pdf-in-maui).
 
 ## Prerequisites
 

diff --git a/...ord/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-Pdf-in-Window-Forms.md b/...ord/Conversions/Word-To-PDF/NET/Convert-Word-Document-to-Pdf-in-Window-Forms.md
@@ -180,10 +180,10 @@ Step 3: Include the following namespaces in the **Form1.cs** (or **Form1.Designe
 using System;
 using System.IO;
 using System.Windows.Forms;
-using Syncfusion.DocIO.DLS;     // Provides WordDocument and FormatType.
-using Syncfusion.DocIO;          // Core DocIO namespace.
-using Syncfusion.DocToPDFConverter; // Provides the DocToPDFConverter.
-using Syncfusion.Pdf;            // Provides PdfDocument.
+using Syncfusion.DocIO.DLS;
+using Syncfusion.DocIO;
+using Syncfusion.DocToPDFConverter;
+using Syncfusion.Pdf;
 
 {% endhighlight %}
 
@@ -253,7 +253,7 @@ using (WordDocument document = new WordDocument(Path.GetFullPath(inputPath), For
 
 {% endtabs %}
 
-N> **Troubleshooting tip:** If the sample throws `FileNotFoundException` for `Input.docx`, confirm the file is present in the `Data` folder and that **Copy to Output Directory** is set to **Copy always**. For advanced conversion options, see [Word to PDF settings](word-to-pdf-settings.md).
+N> **Troubleshooting tip:** If the sample throws `FileNotFoundException` for `Input.docx`, confirm the file is present in the `Data` folder and that **Copy to Output Directory** is set to **Copy always**. For advanced conversion options, see [Word to PDF settings](./word-to-pdf-settings).
 
 Step 6: Build the project.
 

diff --git a/Document-Processing/Word/Conversions/Word-To-PDF/NET/Fallback-fonts-word-to-pdf.md b/Document-Processing/Word/Conversions/Word-To-PDF/NET/Fallback-fonts-word-to-pdf.md
@@ -20,7 +20,7 @@ N> DocIO internally uses the specified fallback fonts for Unicode characters dur
 
 ## Prerequisites
 
-To use fallback fonts during Word to PDF conversion, install the required Syncfusion NuGet packages. For more information on NuGet packages and assemblies, refer to the [NuGet packages required for Word to PDF](Nuget-packages-required-word-to-pdf.md) and [Assemblies required for Word to PDF](Assemblies-required-word-to-pdf.md) documentation.
+To use fallback fonts during Word to PDF conversion, install the required Syncfusion NuGet packages. For more information on NuGet packages and assemblies, refer to the [NuGet packages required for Word to PDF](Nuget-packages-required-word-to-pdf) and [Assemblies required for Word to PDF](./Assemblies-required-word-to-pdf) documentation.
 
 The following namespaces are used in the code examples throughout this document:
 
@@ -829,8 +829,8 @@ N> The Unicode ranges in the table are inclusive on both ends. A character belon
 
 ## See also
 
-* [Font substitution in Word to PDF conversion](Font-substituion-word-to-pdf.md)
-* [NuGet packages required for Word to PDF conversion](Nuget-packages-required-word-to-pdf.md)
-* [Assemblies required for Word to PDF conversion](Assemblies-required-word-to-pdf.md)
-* [Word to PDF conversion settings](Word-to-pdf-settings.md)
-* [Frequently asked questions about Word to PDF conversion](Faqs-word-to-pdf.md)
+* [Font substitution in Word to PDF conversion](Font-substituion-word-to-pdf)
+* [NuGet packages required for Word to PDF conversion](Nuget-packages-required-word-to-pdf)
+* [Assemblies required for Word to PDF conversion](Assemblies-required-word-to-pdf)
+* [Word to PDF conversion settings](Word-to-pdf-settings)
+* [Frequently asked questions about Word to PDF conversion](Faqs-word-to-pdf)
diff --git a/...ent-Processing/Word/Conversions/Word-To-PDF/NET/Font-substituion-word-to-pdf.md b/...ent-Processing/Word/Conversions/Word-To-PDF/NET/Font-substituion-word-to-pdf.md
@@ -16,7 +16,7 @@ The library supports the following font substitution approaches during Word to P
 
 * **Use an alternate font from installed fonts** – substitute with a font that is already installed on the production machine.
 * **Use an alternate font without installing** – load the replacement font from a file stream without installing it on the machine.
-* **Embed fonts** – embed the required TrueType font glyphs directly into the converted PDF. For more details, see [Embedding fonts in Word to PDF conversion](./Word-to-pdf-settings.md#embedding-fonts).
+* **Embed fonts** – embed the required TrueType font glyphs directly into the converted PDF. For more details, see [Embedding fonts in Word to PDF conversion](./Word-to-pdf-settings#embedding-fonts).
 
 ## Use an alternate font from installed fonts
 

diff --git a/...Processing/Word/Conversions/Word-To-PDF/NET/Unsupported-elements-word-to-pdf.md b/...Processing/Word/Conversions/Word-To-PDF/NET/Unsupported-elements-word-to-pdf.md
@@ -261,7 +261,7 @@ During Word-to-PDF and Word-to-Image conversions, Syncfusion Word Library uses f
 
 ## Show Warning for Unsupported Elements
 
-> **Prerequisites:** Refer to the [NuGet packages required for Word to PDF conversion](nuget-packages-required-word-to-pdf.md) and ensure the required assemblies are referenced in your project.
+> **Prerequisites:** Refer to the [NuGet packages required for Word to PDF conversion](nuget-packages-required-word-to-pdf) and ensure the required assemblies are referenced in your project.
 
 When converting a Word document to a PDF, the presence of unsupported elements in the input Word document can lead to preservation issues in the converted PDF. The .NET Word library (DocIO) provides the [Warning](https://help.syncfusion.com/cr/document-processing/Syncfusion.DocToPDFConverter.DocToPDFConverterSettings.html#Syncfusion_DocToPDFConverter_DocToPDFConverterSettings_Warning) API (and the equivalent [DocIORenderer.Settings.Warning](https://help.syncfusion.com/cr/document-processing/Syncfusion.DocIORenderer.DocIORendererSettings.html#Syncfusion_DocIORenderer_DocIORendererSettings_Warning) for cross-platform scenarios), which helps to detect and handle these unsupported elements during the conversion process. This API holds the information of unsupported elements found in the input Word document.