Update use-blazor-report-viewer-with-rs-net.md (#1910)

* Update use-blazor-report-viewer-with-rs-net.md

* Update html5-report-viewer-with-report-server-net.md

Author: todorarabadzhiev

embedding-reports/display-reports-in-applications/web-application/blazor-report-viewer/use-blazor-report-viewer-with-rs-net.md

@@ -1,5 +1,5 @@
 ---
-title: Using the Blazor Report Viewer with Report Server for .NET
+title: Using with Report Server for .NET
 page_title: Connect the Telerik Reporting Blazor Report Viewer with Report Server for .NET
 description: "Learn how the Telerik Reporting Blazor HTML5 Report Viewer can work with the Report Server for .NET."
 slug: use-blazor-report-viewer-with-rs-net
@@ -122,7 +122,7 @@ app.MapGet("/rs-token", (HttpContext context) =>
 
 ### Username and Password Authentication
 
->tip We recommend avoiding this approach for security reasons.
+>caution Avoid this approach for security reasons.
 
 If you prefer to use hardcoded credentials, use the following snippet to place the viewer component in a Razor page like `Pages/Index.razor`.
 

embedding-reports/display-reports-in-applications/web-application/html5-report-viewer/html5-report-viewer-with-report-server-net.md

@@ -39,7 +39,9 @@ reportServer: {
 
 	Substitute the `https://yourReportServerUrl:port` with the actual url of your Report Server for .NET instance, along with the port if needed.
 
-	(__recommended__) The `reportServer.getPersonalAccessToken` option should be set to a function returning the Token of the user who is logging in to the Report Server for .NET wrapped in a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise). Here is a sample implementation that relies on a dedicated secure endpoint '/rs-token' to return the token:
+	To authenticate against the Report Server for .NET you have the following options:
+
+	* (__recommended__) The `reportServer.getPersonalAccessToken` option should be set to a function returning the Token of the user who is logging in to the Report Server for .NET wrapped in a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise). Here is a sample implementation that relies on a dedicated secure endpoint '/rs-token' to return the token:
 
 	````JavaScript
 reportServer: {
@@ -62,7 +64,7 @@ app.MapGet("/rs-token", (HttpContext context) =>
 ````
 
 
-	(_not recommended_) Alternatively, you may use a hardcoded username and password instead of Token authentication. We do not recommend this for security reasons:
+	* (_not recommended_) Alternatively, you may use a hardcoded _username_ and _password_ instead of Token authentication. We do not recommend this for security reasons:
 
 	````JavaScript
 reportServer: {