chore: fix typos in new rs net articles (#1917)

dnikolov-prg · web-flow · commit d5c0cbbb5962 · 2025-11-11T18:34:11.000+02:00
* Update how-to-use-with-report-server-net.md

* Update how-to-use-with-report-server-net.md

* Update how-to-use-with-report-server-net.md

* Update how-to-use-with-report-server-net.md
diff --git a/embedding-reports/display-reports-in-applications/web-application/angular-report-viewer/how-to-use-with-report-server-net.md b/embedding-reports/display-reports-in-applications/web-application/angular-report-viewer/how-to-use-with-report-server-net.md
@@ -30,7 +30,7 @@ The user account that will authenticate with the Report Server may be any User,
 npm install @progress/telerik-angular-report-viewer
 ````
 
-	>If you receive a *403 Forbidden Error*, you need to register and login at [npmjs.com](https://www.npmjs.com/) before performing this step.
+	>If you receive a *403 Forbidden Error*, you need to register and log in at [npmjs.com](https://www.npmjs.com/) before performing this step.
 	>
 	>````powershell
 npm login --registry=https://registry.npmjs.org --scope=@progress
@@ -58,7 +58,7 @@ import { TelerikReportingModule } from '@progress/telerik-angular-report-viewer'
 <link href="https://kendo.cdn.telerik.com/themes/10.2.0/default/default-ocean-blue.css" rel="stylesheet" />
 ````
 
-	>To get the Sass-based Kendo UI themes, you can use either the pre-build CSS files or the NPM packages ([Getting the Sass-Based Themes](https://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes/overview#getting-the-themes)).
+	>To get the Sass-based Kendo UI themes, you can use either the pre-built CSS files or the NPM packages ([Getting the Sass-Based Themes](https://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes/overview#getting-the-themes)).
 
 	If you use the __styleUrls__ attribute to reference the CSS, it is required to set the view encapsulation to __None__:
 
@@ -83,7 +83,7 @@ export class AppComponent {
 ````
 
 
-1. In the same component class, define a `reportSource` object property specifying the category and the name of the report that will be displaued. For example, if the category is **Samples** and the report is **Dashboard**, the syntax will look as follows:
+1. In the same component class, define a `reportSource` object property specifying the category and the name of the report that will be displayed. For example, if the category is **Samples** and the report is **Dashboard**, the syntax will look as follows:
 
 	````TypeScript
 reportSource = {
@@ -93,7 +93,7 @@ reportSource = {
 ````
 
 
-1. In the same component class, define a `reportServer` object property with a `url` string pointing to the Report Server for .NET, and `getPersonalAccessToken` callback, which will be executed when the the report viewer request from the server to render the report.
+1. In the same component class, define a `reportServer` object property with a `url` string pointing to the Report Server for .NET, and a `getPersonalAccessToken` callback, which will be executed when the report viewer requests from the server to render the report.
 
 	````JS
 reportServer = { 
@@ -107,7 +107,7 @@ reportServer = {
 	This is the **recommended** approach, but if an endpoint cannot be exposed, the token can be hardcoded in the callback: `getPersonalAccessToken: () => Promise.resolve('TOKEN_STRING')`
 
 
-1. In the HTML template of the component, define the `<tr-viewer>` element, and pass the defined properties to their corresponding properties of the Angular Wrapper Report Viewer::
+1. In the HTML template of the component, define the `<tr-viewer>` element, and pass the defined properties to their corresponding properties of the Angular Wrapper Report Viewer:
 
 	````HTML
 <tr-viewer
diff --git a/embedding-reports/display-reports-in-applications/web-application/native-angular-report-viewer/how-to-use-with-report-server-net.md b/embedding-reports/display-reports-in-applications/web-application/native-angular-report-viewer/how-to-use-with-report-server-net.md
@@ -92,7 +92,7 @@ reportSource = {
 ````
 
 
-1. In the same component class, define a `reportServer` object property with a `url` string pointing to the Report Server for .NET, and `getPersonalAccessToken` callback, which will be executed when the report viewer requests from the server to render the report.
+1. In the same component class, define a `reportServer` object property with a `url` string pointing to the Report Server for .NET, and a `getPersonalAccessToken` callback, which will be executed when the report viewer requests from the server to render the report.
 
 	````JS
 reportServer = { 
diff --git a/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-with-report-server-net.md b/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-with-report-server-net.md
@@ -67,7 +67,7 @@ The user account that will authenticate with the Report Server may be any User,
 ````
 
 
-1. Set up an endpoint on the server that will securily return the token used by the Report Server for .NET to authorize. For example, creaate an environment variable in `launchSettins.json`**named 'RS_NET_TOKEN**, and store the token in it. Then, the endpoint can be configured to read and return the value of the environment variable:
+1. Set up an endpoint on the server that will securely return the token used by the Report Server for .NET to authorize. For example, create an environment variable in the `launchSettins.json` file named **'RS_NET_TOKEN**, and store the token in it. Then, the endpoint can be configured to read and return the value of the environment variable:
 
 	````C#
 app.MapGet("/rs-token", () =>
@@ -79,14 +79,14 @@ app.MapGet("/rs-token", () =>
 
 	For Blazor Web Assembly applications where the server is not available, the token can be injected on the `.RAZOR` page at build-time. Use `appsettings.{Environment}.json` files (they are bundled at build time), and read the token from the configuration.
 
-1. Configure an `HttpClient` in the `Program.cs` file that will be ibjected on the `.RAZOR` page on the next step when we make a HTTP request to get the token from the server.
+1. Configure an `HttpClient` in the `Program.cs` file that will be injected on the `.RAZOR` page on the next step when we make an HTTP request to get the token from the server.
 
 	````C#
 builder.Services.AddHttpClient();
 ````
 
 
-1. Create a method in the `RAZOR` or `RAZOR.CS` file of the Blazor component that return a `Task<string>` with the retrieved from the server token:
+1. Create a method in the `RAZOR` or `RAZOR.CS` file of the Blazor component that returns a `Task<string>` with the token retrieved from the Report Server:
 
 	````C#
 @inject HttpClient Http
@@ -150,4 +150,4 @@ builder.Services.AddHttpClient();
 ## See Also
 
 * [Integration with Telerik Reporting](https://docs.telerik.com/blazor-ui/integrations/reporting)
-* [Native Blazor Report Viewer Overview]({%slug telerikreporting/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/overview%})
+* [Native Blazor Report Viewer Overview]({%slug telerikreporting/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/overview%})
diff --git a/embedding-reports/display-reports-in-applications/web-application/react-report-viewer/how-to-use-with-report-server-net.md b/embedding-reports/display-reports-in-applications/web-application/react-report-viewer/how-to-use-with-report-server-net.md
@@ -41,9 +41,9 @@ npm install @progress/telerik-react-report-viewer
 <link href="https://kendo.cdn.telerik.com/themes/10.2.0/default/default-ocean-blue.css" rel="stylesheet" />
 ````
 
-	>note To get the Sass-based Kendo UI themes, you can use either the pre-build CSS files, the Kendo UI CDN, or the NPM packages ([Getting the Sass-Based Themes](https://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes/installation)).
+	>note To get the Sass-based Kendo UI themes, you can use either the pre-built CSS files, the Kendo UI CDN, or the NPM packages ([Getting the Sass-Based Themes](https://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes/installation)).
 
-1. In the `.JSX` file where the report viewer will be used, create a `reportSource` object specifying the category and the name of the report that will be displaued. For example, if the category is **Samples** and the report is **Dashboard**, the syntax will look as follows:
+1. In the `.JSX` file where the report viewer will be used, create a `reportSource` object specifying the category and the name of the report that will be displayed. For example, if the category is **Samples** and the report is **Dashboard**, the syntax will look as follows:
 
 	````JS
 const reportSource = {
@@ -63,7 +63,7 @@ const viewerContainerStyle = {
 ````
 
 
-1. In the same file, define a `reportServer` object with a `url` string pointing to the Report Server for .NET, and `getPersonalAccessToken` callback, which will be executed when the the report viewer request from the server to render the report.
+1. In the same file, define a `reportServer` object with a `url` string pointing to the Report Server for .NET, and a `getPersonalAccessToken` callback, which will be executed when the report viewer requests from the server to render the report.
 
 	````JS
 const reportServer = { 
