Sync with Kendo UI Professional

Author: kendo-bot

docs-aspnet/backwards-compatibility/2024-backwards-compatibility.md

@@ -355,9 +355,7 @@ As of the Q1 2024 release, the following APIs will be deprecated.
         )
     ```
 
-* `ChartSeriesLineSettingsBuilder.Width(string)`, `ChartSeriesLineSettingsBuilder.Style(ChartAreaStyle)`,
-`ChartSeriesLineSettingsBuilder.Style(ChartPolarAreaStyle)`,
-`ChartSeriesLineSettingsBuilder.Style(ChartRadarAreaStyle)`
+* `ChartSeriesLineSettingsBuilder.Width(string)`, `ChartSeriesLineSettingsBuilder.Style(ChartAreaStyle)`, `ChartSeriesLineSettingsBuilder.Style(ChartPolarAreaStyle)`, `ChartSeriesLineSettingsBuilder.Style(ChartRadarAreaStyle)`
 
     ```Deprecated
         .Series(series => series

docs-aspnet/cloud-integration/amazon-web-services/s3-storage.md

@@ -22,7 +22,7 @@ Refer to [Creating an AWS Account and a User]({% slug aws_getting_started_aspnet
 
 ## Creating and Configuring a New Bucket
 
-Data in Amazon S3 is stored in buckets. Before you can upload a file to Amazon S3, you need to create a bucket by using the AWS Management Console. You can learn how to do that in the [Creating a Bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html) article. 
+Data in Amazon S3 is stored in buckets. Before you can upload a file to Amazon S3, you need to create a bucket by using the AWS Management Console. You can learn how to do that in the [Creating a Bucket](https://docs.aws.amazon.com/AmazonS3/latest/userguide/creating-bucket.html) article.
 
 >The example in this article uses the AWS Signature Version 2 (V2) signing process. This means that the bucket you will be uploading to must support Signature Version 2. In the bucket creation steps, you are prompted to specify the region the bucket resides in. The region determines whether V2 of the signing process is supported. See the list of regions that support V2 in the [Signature Version 2](https://docs.aws.amazon.com/general/latest/gr/signature-version-2.html) article.
 
@@ -53,40 +53,40 @@ The configuration is in JSON format:
 ]
 ```
 
-The `"http://localhost:62500"` address shown above is exemplary. Use the actual address of your application. Setting `"*"` as value of `AllowedOrigins` will allow any origin. 
+The `"http://localhost:62500"` address shown above is exemplary. Use the actual address of your application. Setting `"*"` as value of `AllowedOrigins` will allow any origin.
 
 ## User Permissions
 
 >If the purpose of the user is only to upload to the S3 storage, we recommend that you create a user with restricted permissions. In this case, the users policy only needs to allow two actions on the destination bucket: `PutObject` and `PutObjectAcl`. In the `Permissions` settings of the user, you can create a policy that includes only these two actions and apply the policy to the user.
 
-	Allow the PutObject and PutObjectAcl actions in the Visual Editor:
+Allow the PutObject and PutObjectAcl actions in the Visual Editor:
 
-	![{{ site.product_short }} Amazon S3 configure restricted permissions](../images/aws-permissions-restricted.png)
+![{{ site.product_short }} Amazon S3 configure restricted permissions](../images/aws-permissions-restricted.png)
 
-    The permissions configuration of the restricted user can be reviewed as JSON and should look like this: 
+The permissions configuration of the restricted user can be reviewed as JSON and should look like this:
 
-    ```js
-    {
-        "Version": "2012-10-17",
-        "Statement": [
-            {
-                "Sid": "VisualEditor0",
-                "Effect": "Allow",
-                "Action": [
-                    "s3:PutObject",
-                    "s3:PutObjectAcl"
-                ],
-                "Resource": "arn:aws:s3:::mybucketname/*"
-            }
-        ]
-    }
-    ```
+```js
+{
+    "Version": "2012-10-17",
+    "Statement": [
+        {
+            "Sid": "VisualEditor0",
+            "Effect": "Allow",
+            "Action": [
+                "s3:PutObject",
+                "s3:PutObjectAcl"
+            ],
+            "Resource": "arn:aws:s3:::mybucketname/*"
+        }
+    ]
+}
+```
 
-## Configuring the Application 
+## Configuring the Application
 
 ### Upload Authorization
 
-In your application, create a model and set up the S3 authorization as demonstrated below. 
+In your application, create a model and set up the S3 authorization as demonstrated below.
 
 The following server-side logic authorizes uploads by creating and signing temporary policies for each client:
 

docs-aspnet/cloud-integration/google-cloud/google-cloud-big-query.md

@@ -23,7 +23,7 @@ Refer to [Creating a Google Cloud Account and Project]({% slug google_cloud_gett
 
 ## Creating New DataSet and Table in BigQuery
 
-For more information on how to create new datasets and tables, refer to the articles about [creating and using datasets](https://cloud.google.com/bigquery/docs/tables) and [creating and using tables](https://cloud.google.com/bigquery/docs/tables) from the official BigQuery documentation. 
+For more information on how to create new datasets and tables, refer to the articles about [creating and using datasets](https://cloud.google.com/bigquery/docs/tables) and [creating and using tables](https://cloud.google.com/bigquery/docs/tables) from the official BigQuery documentation.
 
 1. Navigate to **BigQuery** from the Google Cloud Platform navigation menu.
 
@@ -54,7 +54,7 @@ To start using the Google APIs Client library for .NET:
 
 1. Follow the steps from the [Setting up Authentication](https://cloud.google.com/bigquery/docs/reference/libraries#setting_up_authentication) guide.
 
-One of the steps for setting up authentication consists of downloading a JSON key file that holds the credentials information to your computer. Provide the credentials to your application code by setting the environment variable GOOGLE_APPLICATION_CREDENTIALS. To set the variable, use the approach described in the [Setting up Authentication](https://cloud.google.com/bigquery/docs/reference/libraries#setting_up_authentication) guide. 
+One of the steps for setting up authentication consists of downloading a JSON key file that holds the credentials information to your computer. Provide the credentials to your application code by setting the environment variable GOOGLE_APPLICATION_CREDENTIALS. To set the variable, use the approach described in the [Setting up Authentication](https://cloud.google.com/bigquery/docs/reference/libraries#setting_up_authentication) guide.
 
 If you experience issues with accessing the environment variable, make sure the JSON file is present in an accessible location, for example, `C:\Program Files (x86)\IIS Express\myproject-name-191225-5f6ddc8dc2f6.json`. Try setting the GOOGLE_APPLICATION_CREDENTIALS environment variable in the application:
 
@@ -69,7 +69,7 @@ public ActionResult Index()
 
 ## Configuring the Grid to Consume and Manipulate Available BigQuery Data
 
-Configure the Grid for remote binding and implement the actions the Grid will call to perform CRUD operations. 
+Configure the Grid for remote binding and implement the actions the Grid will call to perform CRUD operations.
 
 1. Configure the Grid.
 
@@ -141,8 +141,8 @@ Configure the Grid for remote binding and implement the actions the Grid will ca
     ```csharp
     using Google.Cloud.BigQuery.V2;
     ```
-    
-    This exemplary implementation shows how you can use a SELECT statement, to get the data and then return it back to the client, for the Grid to visualize it. 
+
+    This exemplary implementation shows how you can use a SELECT statement, to get the data and then return it back to the client, for the Grid to visualize it.
 
     ```Controller
         public ActionResult Products_Read([DataSourceRequest]DataSourceRequest request)
@@ -167,7 +167,7 @@ Configure the Grid for remote binding and implement the actions the Grid will ca
 
 1. Implement the Update, Create and Destroy actions.
 
-    This snippet shows an exemplary implementation of the action responsible for the Update operations. 
+    This snippet shows an exemplary implementation of the action responsible for the Update operations.
 
     ```Controller
         [AcceptVerbs(HttpVerbs.Post)]

docs-aspnet/deployment/overview.md

@@ -40,7 +40,7 @@ The {{ site.product }} components consist of:
 * assembly - it is distributed through [NuGet]({%slug nuget_install_aspnetmvc6_aspnetmvc%}). You could find the list with the packages related to UI for ASP.NET Core [here]({% slug nuget_install_aspnetmvc6_aspnetmvc%}#list-of-provided-packages)
 * [client-side resources]({%slug copyclientresources_aspnetmvc6_aspnetmvc%}) - the required JavaScript and CSS files needed to run the components
 
->important The machine that performs the publish build must be able to properly restore the referenced Telerik NuGet packages. See the [CI, CD, Build Server]({%slug deployment-ci-cd-build-pc%}) article for more details on setting automation up.
+>important The machine that performs the publish build must be able to properly restore the referenced Telerik NuGet packages. See the [CI, CD, Build Server]({%slug deployment_ci_cd_build%}) article for more details on setting automation up.
 
 
 ## Next Steps and Troubleshooting