@progress/kendo-theme-classic 4.43.1-dev.0 → 4.43.1-dev.4

package/README.md

@@ -36,9 +36,7 @@ and then import it in your project styles:
 
 For more information on how to implement the Classic theme in your project, refer to the following articles:
 
-* [Using the Classic Theme in Angular Projects](https://www.telerik.com/kendo-angular-ui/components/styling/theme-classic/)
-* [Using the Classic Theme in React Projects](https://www.telerik.com/kendo-react-ui/components/styling/theme-classic/)
-* [Using the Classic Theme in jQuery Projects](http://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes)
+* [Using the Classic Theme in jQuery Projects](https://docs.telerik.com/kendo-ui/styles-and-layout/sass-themes)
 
 ## Customizing
 
@@ -46,7 +44,7 @@ You can customize Kendo UI Classic Theme both in terms of what gets compiled and
 
 ### Importing
 
-In your custom csss file, you can import the entirety of the theme, by importing `dist/all.scss` or pick just the styles for the components you need. The files for individual components are in `scss/` folder:
+In your custom scss file, you can import the entirety of the theme, by importing `dist/all.scss` or pick just the styles for the components you need. The files for individual components are in `scss/` folder:
 
 ```scss
 // Import only PanelBar and Grid styles
@@ -56,9 +54,9 @@ In your custom csss file, you can import the entirety of the theme, by importing
 
 ### SCSS Variables
 
-Kendo UI Classic Theme provides many variables for customization. There are variables that control globally used theme colors like `$primary`, `$secondary`, `$success`, `$error` etc.; variables for all components such as `$component-text`, `$component-bg`; as well as variables for individual components such as `$grid-bg`, `$combobox-text`, `$tabstrip-font-size` and so on.
+Kendo UI Classic Theme provides many variables for customization. There are variables that control globally used theme colors like `$primary`, `$secondary`, `$success`, `$error` etc.; variables for all components such as `$component-text`, `$component-bg`; as well as variables for individual components such as `$grid-bg`, `$tabstrip-font-size` and so on.
 
-Most component variables link to higher abstracted generic variables. For instance, the background of the grid component can be customized both from `$component-bg` and `$grid-bg`, with the latter ferrencing the former.
+Most component variables link to higher abstracted generic variables. For instance, the background of the grid component can be customized both from `$component-bg` and `$grid-bg`, with the latter referencing the former.
 
 We have more than 2000 variables, so it's hard to list them all. We've tried to make variable names as coherent as possible. For instance, all variables ending in `-bg` control background color; all variables ending in `-text` control text color.
 
@@ -68,9 +66,6 @@ Here is a quick example on how to customize:
 // Make all inputs components with a different background color
 $input-bg: #f0f0f0;
 
-// Change just the autocomplete to have white background
-$autocomplete-bg: #ffffff;
-
 // Make the border of the grid black and slightly ticker
 $grid-border-width: 2px;
 $grid-border: #000000;
@@ -91,7 +86,7 @@ CSS can be complicated due to cascades (that's what C stands for). If there are
 
 To avoid that, we've prefixed all our class names with `k-` e.g. `k-grid`, `k-hidden` etc., with the exception of handling for `hidden` attribute, which will hide the element that has it.
 
-Some frameworks, like Bootstrap and Tailwind, touch global styles to establish a sort of baseline -- we call that normalizing. One such styles is the following bit, which makes dimenssions (width and height) behave in a specific way:
+Some frameworks, like Bootstrap and Tailwind, touch global styles to establish a sort of baseline -- we call that normalizing. One such styles is the following bit, which makes dimensions (width and height) behave in a specific way:
 
 ```css
 *, ::after, ::before {
@@ -114,18 +109,16 @@ Have a bug or a feature request? Please first search for existing and closed iss
 
 ## Versioning
 
-To ensure version predictability, we use [Semantic Versioning](https://semver.org/): we try to add only feaures for minor versions and bugfixes (or smaller features) for patch version.
+To ensure version predictability, we use [Semantic Versioning](https://semver.org/): we try to add only features for minor versions and bugfixes (or smaller features) for patch version.
 ## License
 
 This package is part of the following suites:
 
-* [Kendo UI for Angular](http://www.telerik.com/kendo-angular-ui/)
-* [KendoReact](http://www.telerik.com/kendo-react-ui/)
-* [Kendo UI for jQuery](http://www.telerik.com/kendo-ui)
-* [UI for ASP.NET MVC](http://www.telerik.com/aspnet-mvc)
-* [UI for ASP.NET Core](http://www.telerik.com/aspnet-core-ui)
+* [Kendo UI for jQuery](https://www.telerik.com/kendo-ui)
+* [Telerik UI for ASP.NET MVC](https://www.telerik.com/aspnet-mvc)
+* [Telerik UI for ASP.NET Core](https://www.telerik.com/aspnet-core-ui)
 
-All available Kendo UI commercial licenses may be obtained at http://www.telerik.com/purchase/kendo-ui.
+Visit the [Kendo UI Pricing page](https://www.telerik.com/purchase/kendo-ui) to review Kendo UI commercial licensing and pricing.
 
 If you do not own a commercial license, the usage of this software shall be governed by the [Apache License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0).