983104: Updated

Author: Ashwini-SF5049

blazor/file-upload/chunk-upload.md

@@ -196,8 +196,6 @@ To modify chunk upload behavior, the following options can be used.
 
 The following sample sets the chunk upload delay to 3000 milliseconds and the retry count to 5. The failure event triggers because an incorrect saveUrl is used.
 
-`SaveUrl` and `RemoveUrl` actions are explained in this [link](./chunk-upload/#save-and-remove-action-for-blazor-aspnet-core-hosted-application).
-
 ```cshtml
 @using Syncfusion.Blazor.Inputs
 
@@ -213,8 +211,6 @@ Chunk upload allows resuming an interrupted upload after a network failure or a
 
 N> The pause and resume features are available only when chunk upload is enabled.
 
-`SaveUrl` and `RemoveUrl` actions are explained in this [link](./chunk-upload/#save-and-remove-action-for-blazor-aspnet-core-hosted-application).
-
 ```cshtml
 @using Syncfusion.Blazor.Inputs
 

blazor/file-upload/http-client.md

@@ -14,7 +14,7 @@ The File Upload component supports configuring a custom HTTP pipeline for its ne
 The following example illustrates how to configure the File Upload component to use a specific HttpClient instance for SaveUrl and RemoveUrl requests in a Blazor application. This approach applies to Blazor Server and Blazor Web App (Server/Auto). In Blazor WebAssembly, an HttpClient is available by default; register headers either via DI (for a scoped client) or on a per-request basis.
 
 N> - Ensure the API configured in SaveUrl/RemoveUrl permits cross-origin requests if it runs on a different domain (CORS).
-- Prefer standard Authorization headers (for example, Bearer tokens) and avoid hardcoding secrets.
+- Prefer standard Authorization headers (for example, Bearer tokens) and avoid hard coding secrets.
 - Consider IHttpClientFactory or named clients for production scenarios to manage handlers, retries, and resilience.
 - To append additional form data for each file (for example, metadata), use Uploader events such as Uploading/BeforeUpload; headers should be used for auth and routing concerns.
 - Handle failures using Uploader events (for example, OnFailure/Success) to surface authorization or validation errors returned by the API.