991876: Resolved CI failures

Author: SF4524LogeshKumar

Document-Processing/PDF/PDF-Viewer/angular/how-to/load-document-after-resources-loaded.md

@@ -14,7 +14,7 @@ In Standalone mode, the Angular PDF Viewer downloads its PDFium runtime assets (
 
 ## When does resourcesLoaded trigger?
 
-The `resourcesLoaded` event fires once the viewer finishes loading all required PDFium assets. At this point, it is safe to call the [`load`](https://ej2.syncfusion.com/angular/documentation/api/pdfviewer/#load) method to open a document (by URL or Base64).
+The `resourcesLoaded` event fires once the viewer finishes loading all required PDFium assets. At this point, it is safe to call the [`load`](https://ej2.syncfusion.com/angular/documentation/api/pdfviewer#load) method to open a document (by URL or Base64).
 
 ## How to Load Document after resourcesLoaded
 
@@ -90,11 +90,11 @@ export class AppComponent {
 
 - Always set a valid `resourceUrl` when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside `resourcesLoaded`. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call `load` again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call `load` again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in Angular PDF Viewer](../events/#resourcesloaded)
+- [Events in Angular PDF Viewer](../events#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/asp-net-core/how-to/load-document-after-resources-loaded.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: Load document after resources Loaded ASP.NET Core PDF Viewer | Syncfusion
+title: Load document after resources Loaded Core PDF Viewer | Syncfusion
 description: Learn here how to load a PDF only after assets are ready in the Syncfusion ASP.NET Core PDF Viewer (Standalone) using the resourcesLoaded event.
 platform: document-processing
 control: PDF Viewer 
@@ -67,11 +67,11 @@ The resourcesLoaded event fires once the viewer finishes loading all required PD
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in ASP.NET Core PDF Viewer](../event/#resourcesloaded)
+- [Events in ASP.NET Core PDF Viewer](../event#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/asp-net-mvc/how-to/load-document-after-resources-loaded.md

@@ -1,6 +1,6 @@
 ---
 layout: post
-title: Load document after resources Loaded ASP.NET MVC PDF Viewer | Syncfusion
+title: Load document after resources Loaded MVC PDF Viewer | Syncfusion
 description: Learn here how to load a PDF only after assets are ready in the Syncfusion ASP.NET Core PDF Viewer (Standalone) using the resourcesLoaded event.
 platform: document-processing
 control: PDF Viewer 
@@ -60,11 +60,11 @@ The resourcesLoaded event fires once the viewer finishes loading all required PD
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in ASP.NET MVC PDF Viewer](../event/#resourcesloaded)
+- [Events in ASP.NET MVC PDF Viewer](../event#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/javascript-es5/how-to/load-document-after-resources-loaded.md

@@ -53,11 +53,11 @@ function onResourcesLoaded() {
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in JavaScript PDF Viewer](../event/#resourcesloaded)
+- [Events in JavaScript PDF Viewer](../event#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/javascript-es6/how-to/load-document-after-resources-loaded.md

@@ -56,11 +56,11 @@ viewer.appendTo('#PdfViewer');
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in JavaScript PDF Viewer](../event/#resourcesloaded)
+- [Events in JavaScript PDF Viewer](../event#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/react/how-to/load-document-after-resources-loaded.md

@@ -105,11 +105,11 @@ root.render(<App />);
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in React PDF Viewer](../events/#resourcesloaded)
+- [Events in React PDF Viewer](../events#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)

Document-Processing/PDF/PDF-Viewer/vue/how-to/load-document-after-resources-loaded.md

@@ -101,11 +101,11 @@ export default {
 
 - Always set a valid resourceUrl when using the Standalone PDF Viewer. If the path is incorrect or blocked by the network, the event cannot fire.
 - Load documents inside resourcesLoaded. This guarantees the PDFium runtime is ready and prevents intermittent errors on slower networks.
-- The event fires for the viewer’s asset load lifecycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
+- The event fires for the viewer’s asset load life cycle, not for every document load. After it fires once, you can safely call load again later (for example, in response to user actions) without waiting for the event.
 
 ## See also
 
-- [Events in Vue PDF Viewer](../event/#resourcesloaded)
+- [Events in Vue PDF Viewer](../event#resourcesloaded)
 - [Open PDF files](../open-pdf-files)
 - [Save PDF files](../save-pdf-files)
 - [Getting started](../getting-started)