Some minor typo fixes

Author: TimoSalomaki

components/button/overview.md

@@ -164,7 +164,7 @@ The button renders a `<button type="submit">` element by default, as this is the
 You can control the `type` attribute through the `ButtonType` property of the component which can accept the following values:
 
 * `Submit` - Renders a `type="submit"` attribute. Can submit the form and trigger validation. The default value.
-* `Button` - Renders a `type="button"` attribute. Does not invokce form validation and submission.
+* `Button` - Renders a `type="button"` attribute. Does not invoke form validation and submission.
 * `Reset` - Renders a `type="reset"` attribute. Can reset the current form.
 
 ````CSHTML

components/calendar/navigation.md

@@ -52,7 +52,7 @@ The user can click on an item in the current view to go to the more detailed vie
 
 You can control the initial view by setting the `View` property to a member of the `Telerik.Blazor.CalendarView` enum as listed above.
 
-You can control how much detail the user can go into by setting the `BottomView` property to the same enum. Once the user reaches this bottom view, clicking the items selects them and does not navigate to a mode detailed view.
+You can control how much detail the user can go into by setting the `BottomView` property to the same enum. Once the user reaches this bottom view, clicking the items selects them and does not navigate to a more detailed view.
 
 >caption Control current view and how deep the user can go
 

components/chart/overview.md

@@ -74,7 +74,7 @@ To use a Telerik chart for Blazor:
 
 ![](images/overview-chart.png)
 
->tip When configuring nested properties and child elements in your chart, the inner tags will contain their parent tag name and add specifics to its end. You can see an example of this in the `TelerikChartSeries` > `TelerikChartSeriesLabels` tags above example.
+>tip When configuring nested properties and child elements in your chart, the inner tags will contain their parent tag name and add specifics to its end. You can see an example of this with the `TelerikChartSeries` > `TelerikChartSeriesLabels` tags in the above example.
 
 
 >caption Component namespace and reference

components/chart/types/bar.md

@@ -18,7 +18,7 @@ A **Bar** chart displays data as horizontal bars whose lengths vary according to
 
 @[template](/_contentTemplates/chart/link-to-basics.md#understand-basics-and-databinding-first)
 
-To create an bar chart:
+To create a bar chart:
 
 1. add a `TelerikChartSeries` to the `TelerikChartSeriesItems` collection
 2. set its `Type` property to `ChartSeriesType.Bar`

components/chart/types/column.md

@@ -18,7 +18,7 @@ A **Column** chart displays data as vertical bars whose heights vary according t
 
 @[template](/_contentTemplates/chart/link-to-basics.md#understand-basics-and-databinding-first)
 
-To create an bar chart:
+To create a column chart:
 
 1. add a `TelerikChartSeries` to the `TelerikChartSeriesItems` collection
 2. set its `Type` property to `ChartSeriesType.Column`

components/chart/types/donut.md

@@ -18,7 +18,7 @@ The **Donut** chart displays the data as sectors from a two-dimensional circle a
 
 @[template](/_contentTemplates/chart/link-to-basics.md#understand-basics-and-databinding-first)
 
-To create an donut chart:
+To create a donut chart:
 
 1. add a `TelerikChartSeries` to the `TelerikChartSeriesItems` collection
 2. set its `Type` property to `ChartSeriesType.Donut`

components/chart/types/pie.md

@@ -18,7 +18,7 @@ The **Pie** chart displays the data as sectors from a two-dimensional circle and
 
 @[template](/_contentTemplates/chart/link-to-basics.md#understand-basics-and-databinding-first)
 
-To create an bar chart:
+To create a pie chart:
 
 1. add a `TelerikChartSeries` to the `TelerikChartSeriesItems` collection
 2. set its `Type` property to `ChartSeriesType.Pie`