diff --git a/README.md b/README.md
index 6a9452c3d..f9d0a629c 100644
--- a/README.md
+++ b/README.md
@@ -53,7 +53,7 @@ The two suggested workflows are:
   When you link to an image, the path and filename are case-sensitive. The convention is `kebab-case`. `import` should be used to help detect broken images and placed near the top of the document for easier maintenance.
 
   > Example code for adding an image in markdown file:
-  ```
+  ```markdown
   import ButtonGroup from '/img/button-group.png';
   <img className="screenshot-full" src={ButtonGroup} alt="Button group" />
   ```
@@ -68,13 +68,13 @@ The two suggested workflows are:
 
 ### Setup
 
-```
+```bash
 npm install
 ```
 
 ### Starting 
 
-```
+```bash
 npx docusaurus start
 npx docusaurus start --locale zh-Hans
 npx docusaurus start --locale ru
diff --git a/docs/basics/data/data-binding/index.md b/docs/basics/data/data-binding/index.md
index 0edfdeef1..9d9976e7a 100644
--- a/docs/basics/data/data-binding/index.md
+++ b/docs/basics/data/data-binding/index.md
@@ -30,7 +30,7 @@ If the user edits the text in the text box, then the `FirstName` property of the
 
 Bindings can be unidirectional: where changes in the properties of a bound application object are reflected in the control, but the user cannot change the control. An example of this would be the text block control, which is read-only.
 
-```
+```xml
 <TextBlock Text="{Binding StatusMessage}" />
 ```
 
diff --git a/docs/basics/user-interface/styling/styles.md b/docs/basics/user-interface/styling/styles.md
index 421fbd4fc..60add48fa 100644
--- a/docs/basics/user-interface/styling/styles.md
+++ b/docs/basics/user-interface/styling/styles.md
@@ -29,7 +29,7 @@ When a match is located by the selection step, then the matched control's proper
 
 The XAML for a style has two parts: a selector attribute, and one or more setter elements. The selector value contains a string that uses the _Avalonia UI_ **style selector syntax**. Each setter element identifies the property that will be changed by name, and the new value that will be substituted. The pattern is like this:
 
-```
+```xml
 <Style Selector="selector syntax">
      <Setter Property="property name" Value="new value"/>
      ...
diff --git a/docs/concepts/reactiveui/binding-to-sorted-filtered-list.md b/docs/concepts/reactiveui/binding-to-sorted-filtered-list.md
index 6fa1ce063..f70a867f4 100644
--- a/docs/concepts/reactiveui/binding-to-sorted-filtered-list.md
+++ b/docs/concepts/reactiveui/binding-to-sorted-filtered-list.md
@@ -19,7 +19,7 @@ Then the `_sourceCache` can be populated through the `AddOrUpdate` method
 
 ## Creating Sorted Or Filtered Views
 
-Next the `ReadOnlyObservableCollection<T>` can be bound to the filtered or sorted `_sourceCache`. The sorting/filtering is done similarly to linq.
+Next the `ReadOnlyObservableCollection<T>` can be bound to the filtered or sorted `_sourceCache`. The sorting/filtering is done similarly to Linq.
 
 ```csharp
 private readonly ReadOnlyObservableCollection<TestViewModel> _testViewModels;
diff --git a/docs/concepts/reactiveui/reactive-command.md b/docs/concepts/reactiveui/reactive-command.md
index 90056baa7..e49f638c1 100644
--- a/docs/concepts/reactiveui/reactive-command.md
+++ b/docs/concepts/reactiveui/reactive-command.md
@@ -65,7 +65,7 @@ When you use _ReactiveUI_ to implement revealed functionality, you create an obs
 
 For example, you can add this code to the above view model constructor (`public MainWindowViewModel()`) to create an observable object to validate the view model:
 
-```
+```csharp
 IObservable<bool> isInputValid = this.WhenAnyValue(
                 x => x.UserName,
                 x => !string.IsNullOrWhiteSpace(x) && x.Length > 7
diff --git a/docs/concepts/services/insets-manager.md b/docs/concepts/services/insets-manager.md
index afd19b364..b24f13eb7 100644
--- a/docs/concepts/services/insets-manager.md
+++ b/docs/concepts/services/insets-manager.md
@@ -67,7 +67,7 @@ SafeAreaChangedArgs is a class that provides data for the SafeAreaChanged event.
 ### SafeAreaPadding
 Gets the new safe area padding.
 
-```
+```csharp
 public Thickness SafeAreaPadding { get; }
 ```
 
diff --git a/docs/concepts/view-locator.md b/docs/concepts/view-locator.md
index dfb427d99..199a3da8b 100644
--- a/docs/concepts/view-locator.md
+++ b/docs/concepts/view-locator.md
@@ -56,7 +56,7 @@ You can customize the View Locator to use different conventions. For example, yo
 
 By default, the View Locator is referenced in App.axaml as a DataTemplate, in the content of the `Application.DataTemplates` XAML tag. Ensure that its appropriate 'using' statement is in the `xmlns:local` property of the Application root tag.
 
-```xaml
+```xml
 <Application xmlns="https://github.com/avaloniaui"
              xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
              x:Class="LearningAvalonia.App"
diff --git a/docs/deployment/debian-ubuntu.md b/docs/deployment/debian-ubuntu.md
index c639a5b20..b49740613 100644
--- a/docs/deployment/debian-ubuntu.md
+++ b/docs/deployment/debian-ubuntu.md
@@ -75,7 +75,7 @@ Overall, all .NET and Avalonia dependencies are required, plus any others specif
 
 Below is a simple example of a `control` file.
 
-```
+```yaml
 Package: myprogram
 Version: 3.1.0
 Section: devel
@@ -112,7 +112,7 @@ The desktop shortcut file follows the [freedesktop specification](https://specif
 
 Below is an example of a desktop shortcut file.
 
-```
+```conf
 [Desktop Entry]
 Name=MyProgram
 Comment=MyProgram, great for doing X
diff --git a/docs/deployment/macOS.md b/docs/deployment/macOS.md
index 15e46c04a..39129c0c3 100644
--- a/docs/deployment/macOS.md
+++ b/docs/deployment/macOS.md
@@ -7,7 +7,7 @@ macOS applications are typically distributed in a `.app` [application bundle](ht
 
 With Avalonia, you'll have a `.app` folder structure that looks like this:
 
-```csharp
+```
 MyProgram.app
 |
 ----Contents\
diff --git a/docs/get-started/install.md b/docs/get-started/install.md
index 7d2e982b6..6cef3660d 100644
--- a/docs/get-started/install.md
+++ b/docs/get-started/install.md
@@ -64,7 +64,7 @@ The project templates will also allow for project creation from your IDE.
 
 ### Ensure .NET SDK is installed
 
-```
+```bash
 dotnet --list-sdks
 
 8.0.202 [C:\Program Files\dotnet\sdk] <-- Your version may vary
@@ -79,7 +79,7 @@ associated with the terminal. On Windows, this involves checking environment var
 If while installing the project templates, you receive an error stating the `Avalonia.Templates` package cannot be found, 
 then ensure NuGet is correctly setup with .NET's standard global package source.
 
-```
+```bash
 dotnet nuget list source
 
 Registered Sources:
@@ -89,7 +89,7 @@ Registered Sources:
 
 If this source is not listed, add it:
 
-```
+```bash
 dotnet nuget add source https://api.nuget.org/v3/index.json -n nuget.org
 ```
 
diff --git a/docs/get-started/test-drive/add-some-layout.mdx b/docs/get-started/test-drive/add-some-layout.mdx
index 8daae947e..b23407d43 100644
--- a/docs/get-started/test-drive/add-some-layout.mdx
+++ b/docs/get-started/test-drive/add-some-layout.mdx
@@ -70,7 +70,7 @@ To take the example forward, add a `StackPanel` as follows (include the preexist
 ```
 
 <ThemedImage
-        alt="Tempature StackPanel"
+        alt="Temperature StackPanel"
         className="center"
         sources={{
             light: useBaseUrl('/img/get-started/test-drive/temperature-stackpanel-light.png'),
diff --git a/docs/get-started/test-drive/input-controls.md b/docs/get-started/test-drive/input-controls.md
index bddc930b6..f605e5238 100644
--- a/docs/get-started/test-drive/input-controls.md
+++ b/docs/get-started/test-drive/input-controls.md
@@ -13,7 +13,7 @@ The following picture shows the finished application at runtime with the gridlin
 these are invisible on a production UI.
 
 <ThemedImage
-        alt="Tempature StackPanel"
+        alt="Temperature StackPanel"
         className="center"
         sources={{
             light: useBaseUrl('/img/get-started/test-drive/input-controls-light.png'),
diff --git a/docs/get-started/wpf/comparison-of-avalonia-with-wpf-and-uwp.md b/docs/get-started/wpf/comparison-of-avalonia-with-wpf-and-uwp.md
index 3166e5296..38fe13d8e 100644
--- a/docs/get-started/wpf/comparison-of-avalonia-with-wpf-and-uwp.md
+++ b/docs/get-started/wpf/comparison-of-avalonia-with-wpf-and-uwp.md
@@ -47,7 +47,7 @@ Legend:
 | Item                                                                | Avalonia | WPF | UWP | Notes                                                                                                                                                                                                                                                                                                                                                                                                     |
 | ------------------------------------------------------------------- | :------: | :-: | :-: | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | DataTriggers / PropertyTrigger / EventTrigger within Style.Triggers |     ✖    |  ✔  |  ✖  |                                                                                                                                                                                                                                                                                                                                                                                                           |
-| VisualStateManager                                                  |     ✖    |  ⚡  |  ✔  | A different concept from WPF that takes the place of DataTriggers, this is very verbose and more often than not increases complexity compared to data triggers. @Felix-Dev VisualStateManager does exist in WPF (it was added in .NET Framework 4.0). It's not as elegant as in UWP though, i.e. it has no VisuaStateManager.Setters property. That means you have to use Storyboards to set your values. |
+| VisualStateManager                                                  |     ✖    |  ⚡  |  ✔  | A different concept from WPF that takes the place of DataTriggers, this is very verbose and more often than not increases complexity compared to data triggers. @Felix-Dev VisualStateManager does exist in WPF (it was added in .NET Framework 4.0). It's not as elegant as in UWP though, i.e. it has no VisualStateManager.Setters property. That means you have to use Storyboards to set your values. |
 | Implicit DataTemplate                                               |     ✔    |  ✔  |  ✖  | Set the DataType property of the DataTemplate to the corresponding type and the template is then applied automatically to all instances of that particular type                                                                                                                                                                                                                                           |
 | Binding in Style setter                                             |     ✔    |  ✔  |  ✖  | Any other than TemplateBinding isn't support in a template/style within UWP                                                                                                                                                                                                                                                                                                                               |
 | BasedOn default Style                                               |     ✔    |  ✔  |  ⚡  | `BasedOn={StaticResource {x:Type TextBlock}` isn't supported in UWP but works in WPF. Instead, BasedOn requires the use of a key which is a problem as not all default styles define one. This is a specific example of the missing x:Type markup extension in UWP.                                                                                                                                       |
@@ -57,7 +57,7 @@ Legend:
 | Item                                                          | Avalonia | WPF | UWP | Notes                                                                                                                                                                                                                                                                                                                                                                                                                                                |
 | ------------------------------------------------------------- | :------: | :-: | :-: | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
 | Coercion                                                      |     ✔    |  ✔  |  ✖  | Coercion of Dependency Properties is not supported in UWP.                                                                                                                                                                                                                                                                                                                                                                                           |
-| Data (Input) Validation                                       |     ✔    |  ✔  |  ✖  | The entire WPF data validation system including the classes/inferfaces: ValidationRule (and all standard implementations), Binding.ValidationRules, IDataErrorInfo, INotifyDataErrorInfo, Binding.ValidatesOnNotifyDataErrors, etc. is not implemented in UWP. This will be added in WinUI 3.0 but the story for using this within the UWP app model with WinUI 3.0 is less clear.                                                                   |
+| Data (Input) Validation                                       |     ✔    |  ✔  |  ✖  | The entire WPF data validation system including the classes/interfaces: ValidationRule (and all standard implementations), Binding.ValidationRules, IDataErrorInfo, INotifyDataErrorInfo, Binding.ValidatesOnNotifyDataErrors, etc. is not implemented in UWP. This will be added in WinUI 3.0 but the story for using this within the UWP app model with WinUI 3.0 is less clear.                                                                   |
 | x:TypeArguments directive                                     |     ✔    |  ✔  |  ✖  | The TypeArguments directive isn't implemented in UWP which causes problems with generics. Missing this requires some work-arounds with classes and creating a non-generic class to use in XAML from a generic one.                                                                                                                                                                                                                                   |
 | UIElement.IsVisible / IsVisibleChanged                        |     ✔    |  ✔  |  ✖  | UWP has no way of tracking which controls are actually visible on the display. WPF has the UIElement.IsVisible property and the IsVisibleChanged event. This hinders the ability to optimize controls for performance.                                                                                                                                                                                                                               |
 | UIElement.Visibility / Visibility.Hidden                      |     ⚡    |  ✔  |  ⚡  | UWP does not include the Visibility.Hidden enum value used for UIElement.Visibility. Hidden in WPF allowed a control to still be used in measure/layout but appear invisible when rendered for display.                                                                                                                                                                                                                                              |
@@ -67,8 +67,8 @@ Legend:
 | VisualBrush / DrawingBrush                                    |     ✔    |  ✔  |  ✖  | VisualBrush is not a XAML brush in UWP. Instead, must fall back to composition brushes which are not 1:1 equivalent. DrawingBrush is not supported at all in UWP.                                                                                                                                                                                                                                                                                    |
 | Supplemental Shapes: Arrow, Callout, Star, etc                |     ✔    |  ✔  |  ✖  | Several shapes present in WPF are missing in UWP.                                                                                                                                                                                                                                                                                                                                                                                                    |
 | Adorner                                                       |     ✔    |  ✔  |  ✖  | [Adorners overview](https://docs.microsoft.com/en-us/dotnet/framework/wpf/controls/adorners-overview)                                                                                                                                                                                                                                                                                                                                                |
-| Thickness                                                     |     ✔    |  ✔  |  ⚡  | The Thickness struct exposes fields for Top, Bottom, Left and Right instead of dependency properties as in WPF. This means you cannot Bind or asign resources to an individual thickness parameter.                                                                                                                                                                                                                                                  |
-| Size / Rect / Point                                           |     ✔    |  ✔  |  ✔  | Size, Rect and Point are fully supported in both WPF and UWP. However, UWP uses single-precision float types for properties instead of double in WPF. This creates an incompatiblity when porting code.                                                                                                                                                                                                                                              |
+| Thickness                                                     |     ✔    |  ✔  |  ⚡  | The Thickness struct exposes fields for Top, Bottom, Left and Right instead of dependency properties as in WPF. This means you cannot Bind or assign resources to an individual thickness parameter.                                                                                                                                                                                                                                                  |
+| Size / Rect / Point                                           |     ✔    |  ✔  |  ✔  | Size, Rect and Point are fully supported in both WPF and UWP. However, UWP uses single-precision float types for properties instead of double in WPF. This creates an incompatibility when porting code.                                                                                                                                                                                                                                              |
 | ItemsControl.AlternationIndex / ItemsControl.AlternationCount |     ✖    |  ✔  |  ✖  | WPF has an easy way to change the style of items in a list using ItemsControl.AlternationIndex and ItemsControl.AlternationCount. This allows, for example, to change the background color of a listed item for even/odd entries. UWP doesn't support this at all in any controls. The partial work-around in UWP is to create a new control deriving from the framework's implementation and override the PrepareContainerForItemOverride() method. |
 | Custom Cursor at runtime                                      |     ✔    |  ✔  |  ✖  |                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
 | Sub-pixel anti-aliasing                                       |     ✔    |  ✔  |  ✖  | Anti-aliasing in UWP along with rendering in general is poor compared to WPF. It's assumed this is for performance reasons on mobile devices and the web (Silverlight).                                                                                                                                                                                                                                                                              |
@@ -193,7 +193,7 @@ This section describes the differences in controls in vanilla WPF and UWP (with
 * Several UWP controls have reentrancy issues. For example, changing the selected item while in a ComboBox SelectionChanged event is largely not possible and will result in a crash. This makes validation directly in the event handler nearly impossible.
 * UWP controls are generally not as powerful as the WPF counterparts. For example, for several years the ComboBox in UWP was not editable. The UWP DatePicker also does not allow typing in a specific date.
 * UWP has no support for data (input) validation. This is a large issue for line-of-business apps migrating from WPF to UWP that heavily use this feature in view models or binding.
-* The UWP styling system is different enough from WPF to require extra effort during porting. UWP uses the VistualStateManger instead of concepts like DataTriggers or EventTriggers from WPF. Styling/Templating are one of the main differences.
+* The UWP styling system is different enough from WPF to require extra effort during porting. UWP uses the VisualStateManger instead of concepts like DataTriggers or EventTriggers from WPF. Styling/Templating are one of the main differences.
 * The ResourceDictionary XAML markup in UWP supports far fewer features than in WPF.
 * UWP seems to follow only the XAML/2006 spec instead of [XAML/2009](https://docs.microsoft.com/en-us/dotnet/desktop/xaml-services/xaml-2009-language-features) supported by WPF
 * Several UWP controls are sealed and new controls cannot derive from them
diff --git a/docs/guides/custom-controls/defining-properties.md b/docs/guides/custom-controls/defining-properties.md
index 6e1ce5074..6d5ce05f1 100644
--- a/docs/guides/custom-controls/defining-properties.md
+++ b/docs/guides/custom-controls/defining-properties.md
@@ -24,13 +24,13 @@ You register a styled property by defining a static read-only field and using th
 
 There is a convention for the name of a property. It must follow the pattern:
 
-```
+```csharp
 [AttributeName]Property
 ```
 
 This means that _Avalonia UI_ will look for an attribute in the XAML, like this:
 
-```
+```xml
 <MyCustomControl AttributeName="value" ... >
 ```
 
diff --git a/docs/guides/data-binding/binding-classes.md b/docs/guides/data-binding/binding-classes.md
index d56d16dfa..b16321a31 100644
--- a/docs/guides/data-binding/binding-classes.md
+++ b/docs/guides/data-binding/binding-classes.md
@@ -13,7 +13,7 @@ To do this, you will need some classes defined in a `<Styles>` collection that t
 
 You can then conditionally apply the classes to a control using special classes syntax and a data binding. The syntax is like this:
 
-```
+```xml title='XAML'
 <SomeControl Classes.class1="{Binding IsClass1Active}">
 ```
 
diff --git a/docs/guides/data-binding/how-to-bind-to-a-command-with-reactiveui.md b/docs/guides/data-binding/how-to-bind-to-a-command-with-reactiveui.md
index 38d93d3bf..4ecc56920 100644
--- a/docs/guides/data-binding/how-to-bind-to-a-command-with-reactiveui.md
+++ b/docs/guides/data-binding/how-to-bind-to-a-command-with-reactiveui.md
@@ -9,7 +9,7 @@ import BindReactiveCommandScreenshot from '/img/guides/data-binding/bind-reactiv
 
 This guide shows you how to bind a view model method (that performs an action) to a control that can initiate an action in response to user interaction (for example, a button). This binding is defined in XAML using the `Command` attribute, for example:
 
-```csharp
+```xml
 <Window xmlns="https://github.com/avaloniaui">
     ...
   <StackPanel Margin="20">
diff --git a/docs/guides/data-binding/how-to-bind-to-a-command-without-reactiveui.md b/docs/guides/data-binding/how-to-bind-to-a-command-without-reactiveui.md
index cf2bc9edf..79a80c02d 100644
--- a/docs/guides/data-binding/how-to-bind-to-a-command-without-reactiveui.md
+++ b/docs/guides/data-binding/how-to-bind-to-a-command-without-reactiveui.md
@@ -50,7 +50,7 @@ namespace AvaloniaGuides.ViewModels
 
 _Avalonia UI_ data binding provides a simple way of implementing a 'can execute?' feature using a naming convention.
 
-If you need to have execution dependent on the value of a command parameter or a view model property, then you can write a second Boolean method to check if the action m,ethod can execute.
+If you need to have execution dependent on the value of a command parameter or a view model property, then you can write a second Boolean method to check if the action method can execute.
 
 To make this work, _Avalonia UI_ uses the naming convention that the Boolean method has the same root name as the action method, but with the added prefix 'Can'.
 
diff --git a/docs/guides/data-binding/how-to-create-a-custom-data-binding-converter.md b/docs/guides/data-binding/how-to-create-a-custom-data-binding-converter.md
index dbb8deac2..168f0d946 100644
--- a/docs/guides/data-binding/how-to-create-a-custom-data-binding-converter.md
+++ b/docs/guides/data-binding/how-to-create-a-custom-data-binding-converter.md
@@ -85,7 +85,7 @@ public class TextCaseConverter : IValueConverter
 
 ## Target Property Type
 
-You may want to write a a custom converter that can switch the output type depending on what the target property requires. You can achieve this becuase the `Convert` method receives a `targetType` argument that you can test with the `IsAssignableTo` function.
+You may want to write a a custom converter that can switch the output type depending on what the target property requires. You can achieve this because the `Convert` method receives a `targetType` argument that you can test with the `IsAssignableTo` function.
 
 In this example, the `animalConverter` can find an image, or a text name for a bound `Animal` class object:  
 
diff --git a/docs/guides/graphics-and-animation/keyframe-animations.md b/docs/guides/graphics-and-animation/keyframe-animations.md
index 7ac5f9a78..2373f35e9 100644
--- a/docs/guides/graphics-and-animation/keyframe-animations.md
+++ b/docs/guides/graphics-and-animation/keyframe-animations.md
@@ -43,7 +43,7 @@ Follow this procedure to define a simple color fade animation using XAML:
 
 The finished code will look like this: 
 
-```
+```xml
 <Window xmlns="https://github.com/avaloniaui">
     <Window.Styles>
         <Style Selector="Rectangle.red">
diff --git a/docs/guides/implementation-guides/how-to-use-design-time-data.md b/docs/guides/implementation-guides/how-to-use-design-time-data.md
index 42eb319d4..b573be280 100644
--- a/docs/guides/implementation-guides/how-to-use-design-time-data.md
+++ b/docs/guides/implementation-guides/how-to-use-design-time-data.md
@@ -67,7 +67,7 @@ As of Avalonia version 11, the default sample app is set to use Compiled binding
 1. Import the ViewModels namespace: this is done from the line **xmlns:vm** is to include the ViewModel namespace. In this example the project name is **AvaloniaApplication1**.
 2. Declare the ViewModel class, so that the design time environment can do a type check on the class properties. This is done through the line **x:DataType**
    
-```
+```xml
 <UserControl xmlns="https://github.com/avaloniaui"
              xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
              xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
diff --git a/docs/guides/implementation-guides/ide-support.md b/docs/guides/implementation-guides/ide-support.md
index 9196de7cf..482617838 100644
--- a/docs/guides/implementation-guides/ide-support.md
+++ b/docs/guides/implementation-guides/ide-support.md
@@ -29,7 +29,7 @@ In some cases, due to bugs/limitations in Visual Studio, the Avalonia XAML desig
 
 There are a number of properties that can be applied to your controls which will take effect only at design-time. To use these you must add a namespace to your XAML file:
 
-```csharp
+```xml
 xmlns:d="http://schemas.microsoft.com/expression/blend/2008"
 ```
 
diff --git a/docs/guides/platforms/android/setting-up-your-developer-environment-for-android.md b/docs/guides/platforms/android/setting-up-your-developer-environment-for-android.md
index e8d2a769d..4ceede5b1 100644
--- a/docs/guides/platforms/android/setting-up-your-developer-environment-for-android.md
+++ b/docs/guides/platforms/android/setting-up-your-developer-environment-for-android.md
@@ -42,12 +42,12 @@ If you use _JetBrains Rider_ then follow the guide [here](https://www.jetbrains.
 Alternatively you can install the _Android_ command line tools from [here](https://developer.android.com/studio#command-tools).
 
 This toolset has a command line based SDK manager that can be used to install the SDK. On successfully installing the Android SDK, add the path to the sdk to your PATH environment variable, directly in bash or in your profile's .bashrc file on Linux.
-```
+```bash
 export ANDROID_HOME=/path/to/sdk
 export PATH=$PATH:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools
 ```
 You can also directly specify the Android SDK location in the `dotnet` commands when you build, run or deploy the dotnet Android project, by setting the `AndroidSdkDirectory` variable in the command:
-```
+```bash
 dotnet build ... /p:AndroidSdkDirectory=/path/to/sdk
 ```
 Ensure you've installed the JDK 11 or above using your platform's package manager. This is already done if set up using Visual Studio or JetBrains Rider as stated above.
diff --git a/docs/guides/platforms/ios/build-and-run-your-application-on-a-simulator.md b/docs/guides/platforms/ios/build-and-run-your-application-on-a-simulator.md
index acadbc947..7aeaf715b 100644
--- a/docs/guides/platforms/ios/build-and-run-your-application-on-a-simulator.md
+++ b/docs/guides/platforms/ios/build-and-run-your-application-on-a-simulator.md
@@ -28,7 +28,7 @@ dotnet run
 If you use `JetBrains Rider` or `Visual Studio for Mac` you can open the solution and run, build and debug your program inside the simulator.
 
 :::info
-`Dependent on the .NET version and the iOS Simulator version it may require Rosetta 2 to be installed on Apple Slicon Macs. To install Rosetta 2, you can use the following command in the terminal:`
+`Dependent on the .NET version and the iOS Simulator version it may require Rosetta 2 to be installed on Apple Silicon Macs. To install Rosetta 2, you can use the following command in the terminal:`
 
 ```bash
 /usr/sbin/softwareupdate --install-rosetta
diff --git a/docs/guides/platforms/rpi/running-on-raspbian-lite-via-drm.md b/docs/guides/platforms/rpi/running-on-raspbian-lite-via-drm.md
index 732abbdab..723750aba 100644
--- a/docs/guides/platforms/rpi/running-on-raspbian-lite-via-drm.md
+++ b/docs/guides/platforms/rpi/running-on-raspbian-lite-via-drm.md
@@ -42,7 +42,7 @@ To prepare the EMMC memory for mounting follow these [steps](https://www.raspber
 * Review your selections and click 'Flash!' to begin writing data. Once flashing is complete, create a new empty file named **ssh** (with no extension, e.q with `touch ssh`) in the boot drive of the Raspberry. This will ensure that the SSH daemon is enabled once the Raspberry Pi has started and you can logon over the network.
 * _**Only for Cm4** add the following to `/boot/config.txt` to enable the Usb 2.0 ports_
 
-```
+```conf
 dtoverlay=dwc2,dr_mode=host
 ```
 
diff --git a/docs/guides/platforms/rpi/running-your-app-on-a-raspberry-pi.md b/docs/guides/platforms/rpi/running-your-app-on-a-raspberry-pi.md
index 59ef517c9..0ef7ec7bd 100644
--- a/docs/guides/platforms/rpi/running-your-app-on-a-raspberry-pi.md
+++ b/docs/guides/platforms/rpi/running-your-app-on-a-raspberry-pi.md
@@ -7,7 +7,7 @@ title: Running on Raspberry Pi
 
 ### Step 1
 
-Flash 8GB SD Card with Raspbian Stretch (2018-11-13). `BelenaEtcher` is a nice tool for that.
+Flash 8GB SD Card with Raspbian Stretch (2018-11-13). `balenaEtcher` is a nice tool for that.
 
 Plug in the card and start the `Raspberry Pi`.
 
diff --git a/docs/guides/styles-and-resources/property-setters.md b/docs/guides/styles-and-resources/property-setters.md
index 8cfe5cd91..a5d2a9f29 100644
--- a/docs/guides/styles-and-resources/property-setters.md
+++ b/docs/guides/styles-and-resources/property-setters.md
@@ -42,9 +42,9 @@ There are two rules that govern which property setter has precedence when a sele
 For example, firstly this means that styles defined at window level will override those defined at application level. Secondly, this means that where the selected style collections are at the same level, then the later definition (as written in the file) has priority.
 
 :::warning
-If you were comparing style classes to CSS you must note that: **unlike CSS**, the list sequence of class names in the `Classes` attribute has no effect on setter priority in _Avalonia UI_. That is, if both these style classes set the colour, then either way of listing the classes has the same result:
+If you were comparing style classes to CSS you must note that: **unlike CSS**, the list sequence of class names in the `Classes` attribute has no effect on setter priority in _Avalonia UI_. That is, if both these style classes set the color, then either way of listing the classes has the same result:
 
-```
+```xml
 <Button Classes="h1 blue"/>
 <Button Classes="blue h1"/>
 ```
diff --git a/docs/guides/styles-and-resources/resources.md b/docs/guides/styles-and-resources/resources.md
index b4d42625e..6f6c05b59 100644
--- a/docs/guides/styles-and-resources/resources.md
+++ b/docs/guides/styles-and-resources/resources.md
@@ -274,12 +274,12 @@ Avalonia provides different options to access Resources from code.
 
 :::note
 
-`ResourceNode` in the below samples can be any node that supports `Resource`, like `Appliction.Current`, `Window`, `UserControl`, ... 
+`ResourceNode` in the below samples can be any node that supports `Resource`, like `Application.Current`, `Window`, `UserControl`, ... 
 
 :::
 
 - **ResourceNode.Resources["TheKey"]**: <br/>
-  This will directly access the underlaying `Dictionary`. Be aware: Merged Dictionaries and parents will not be scanned. 
+  This will directly access the underlying `Dictionary`. Be aware: Merged Dictionaries and parents will not be scanned. 
 - **ResourceNode.TryGetResource**: <br/>
   This function will try to get a specific resource and return `true` if successful, otherwise `false`. Merged dictionaries will be scanned, but it will not follow the logical tree. 
 - **ResourceNode.TryFindResource**:  <br/>
@@ -304,10 +304,10 @@ public MainWindow()
     // found2 = true | result2 = "Hello World" 
     var found2 = this.TryFindResource("TheKey", this.ActualThemeVariant, out var result2);
 
-    // Dound the resource to a TextBlock from code behind
+    // Bind the resource to a TextBlock from code behind
     myTextBlock.Bind(TextBlock.TextProperty, Resources.GetResourceObservable("TheKey"));
 
-    // this will update myTextBlock.Text via the bound observable
+    // This will update myTextBlock.Text via the bound observable
     this.Resources["TheKey"] = "Hello from code behind"; 
 }
 ```
diff --git a/docs/reference/controls/buttons/radiobutton.md b/docs/reference/controls/buttons/radiobutton.md
index a15cf10dd..e5ce6508e 100644
--- a/docs/reference/controls/buttons/radiobutton.md
+++ b/docs/reference/controls/buttons/radiobutton.md
@@ -23,7 +23,7 @@ You will probably use these properties most often:
 
 This example shows two groups of radio buttons working independently:
 
-```
+```xml
 <StackPanel Margin="20">
   <TextBlock Margin="0 10 0 5">First Group</TextBlock>
     <RadioButton GroupName="First Group"
diff --git a/docs/reference/controls/buttons/repeatbutton.md b/docs/reference/controls/buttons/repeatbutton.md
index 4627f3858..bc990b9a7 100644
--- a/docs/reference/controls/buttons/repeatbutton.md
+++ b/docs/reference/controls/buttons/repeatbutton.md
@@ -22,7 +22,7 @@ You will probably use these properties most often:
 
 This example shows a repeat button generating click events with the default interval and delay.
 
-```
+```xml
 <Grid Margin="20" RowDefinitions="50,*">
   <RepeatButton Grid.Row="0" Click="ClickHandler">Press and hold down</RepeatButton>
   <ScrollViewer Grid.Row="1">
diff --git a/docs/reference/controls/menu.md b/docs/reference/controls/menu.md
index 476883ea9..13cfec9f0 100644
--- a/docs/reference/controls/menu.md
+++ b/docs/reference/controls/menu.md
@@ -153,6 +153,7 @@ A menu icon can be displayed by placing an image or a path icon in the `<MenuIte
      <MenuItem.Icon>
         <PathIcon Data="{StaticResource clipboard_paste_regular}"/>
      </MenuItem.Icon>
+  </MenuItem>
 </MenuItem>
 ```
 
diff --git a/docs/reference/controls/treedatagrid/creating-a-flat-treedatagrid.md b/docs/reference/controls/treedatagrid/creating-a-flat-treedatagrid.md
index e6b9c7bde..96e911fdd 100644
--- a/docs/reference/controls/treedatagrid/creating-a-flat-treedatagrid.md
+++ b/docs/reference/controls/treedatagrid/creating-a-flat-treedatagrid.md
@@ -10,7 +10,7 @@ import FlatTreeDataGridSourceScreenshot from '/img/reference/controls/treedatagr
 
 In this example the view model contains an observable collection that is filled with data and then used to create a `FlatTreeDataGridSource` property to bind to the source of the tree data grid. The items of the grid are class `Person`.
 
-```
+```xml
 <TreeDataGrid Source="{Binding PersonSource}"/>
 ```
 
diff --git a/docs/reference/controls/treedatagrid/creating-a-hierarchical-treedatagrid.md b/docs/reference/controls/treedatagrid/creating-a-hierarchical-treedatagrid.md
index ce7bf6bf2..367244c7e 100644
--- a/docs/reference/controls/treedatagrid/creating-a-hierarchical-treedatagrid.md
+++ b/docs/reference/controls/treedatagrid/creating-a-hierarchical-treedatagrid.md
@@ -10,7 +10,7 @@ import HierarchicalTreeDataGridSourceScreenshot from '/img/reference/controls/tr
 
 In this example the view model contains an observable collection that is filled with data and then used to create a `HierarchicalTreeDataGridSource` property to bind on to the source of the tree data grid. The items of the grid are class `Person`.
 
-```
+```xml
 <TreeDataGrid Source="{Binding PersonSource}"/>
 ```
 
diff --git a/docs/reference/controls/wrappanel.md b/docs/reference/controls/wrappanel.md
index 82e5f01be..44d5e8a86 100644
--- a/docs/reference/controls/wrappanel.md
+++ b/docs/reference/controls/wrappanel.md
@@ -20,7 +20,7 @@ You will probably use these properties most often:
 
 ## Examples
 
-```
+```xml
 <WrapPanel>
     <Rectangle Fill="Navy" Width="100" Height="100" Margin="20"/>
     <Rectangle Fill="Yellow" Width="100" Height="100" Margin="20"/>
diff --git a/docs/reference/gestures/pinchgesturerecognizer.md b/docs/reference/gestures/pinchgesturerecognizer.md
index b1bc22673..1d33cfd81 100644
--- a/docs/reference/gestures/pinchgesturerecognizer.md
+++ b/docs/reference/gestures/pinchgesturerecognizer.md
@@ -23,7 +23,7 @@ A PinchGestureRecognizer can be attached to a control using the control's `Gestu
 image.GestureRecognizers.Add(new PinchGestureRecognizer());
 ```
 
-The PinchGestureRegonizer raises a `Gestures.PinchEvent` when it detects the start of a pull gesture. When the pull ends, from the pointer being released or another gesture start, it raises a `Gestures.PinchEndedEvent`.
+The PinchGestureRecognizer raises a `Gestures.PinchEvent` when it detects the start of a pull gesture. When the pull ends, from the pointer being released or another gesture start, it raises a `Gestures.PinchEndedEvent`.
 The `Scale` property in the args passed to the `Gestures.PinchEvent` event handler contains the relative size of the pinch since it started.
 
 ## Binding Events
diff --git a/docs/reference/gestures/pullgesturerecognizer.md b/docs/reference/gestures/pullgesturerecognizer.md
index 352e356d9..567dd0026 100644
--- a/docs/reference/gestures/pullgesturerecognizer.md
+++ b/docs/reference/gestures/pullgesturerecognizer.md
@@ -30,7 +30,7 @@ The PullGestureRecognizer raises a `Gestures.PullGestureEvent` when it detects t
 
 ### PullDirection
 This defines the direction of the pull. There are 4 available values;
-* `PullDirection.TopToBottom` : Pull starts from the top edge and moves towards the buttom
+* `PullDirection.TopToBottom` : Pull starts from the top edge and moves towards the bottom
 * `PullDirection.BottomToTop` : Pull starts from the bottom edge and moves towards the top
 * `PullDirection.LeftToRight` : Pull starts from the left edge and moves towards the right
 * `PullDirection.RightToLeft` : Pull starts from the right edge and moves towards the left
diff --git a/docs/reference/styles/style-selector-syntax.md b/docs/reference/styles/style-selector-syntax.md
index aba677aa2..f9bd293cb 100644
--- a/docs/reference/styles/style-selector-syntax.md
+++ b/docs/reference/styles/style-selector-syntax.md
@@ -123,7 +123,7 @@ This is very similar to the style class selector except it also matches derived
 Technical detail: during the matching process, _Avalonia UI_ determines the type of a control by examining its `StyleKey` property.
 :::
 
-INterestingly, this allows you to write very general class-based selectors. As controls are all derived from the class `Control`, a selector that only selects on the style class `margin2` can be written:
+Interestingly, this allows you to write very general class-based selectors. As controls are all derived from the class `Control`, a selector that only selects on the style class `margin2` can be written:
 
 
 
@@ -163,13 +163,13 @@ For the concept behind the logical controls tree, see [here](../../concepts/cont
 
 For example, applying the above selector to this XAML:
 
-```
+```xml
 <StackPanel>
    <Button>Save</Button>
    <DockPanel Width="300" Height="300">
        <Button DockPanel.Dock="Top">Top</Button>
        <TextBlock>Some text</TextBlock>
-   </DockPanel
+   </DockPanel>
 </StackPanel>
 ```
 
@@ -211,7 +211,7 @@ new Style(x => x.OfType<Button>().PropertyEquals(Button.IsDefaultProperty, true)
 
 You can refine a selector so that it includes the value of a property. The property=value pair is defined inside square brackets. This matches any control that has the specified property set to the specified value.
 
-```
+```xml
 <StackPanel Orientation="Horizontal">
    <Button IsDefault="True">Save</Button>
    <Button>Cancel</Button>   
@@ -346,12 +346,12 @@ new Style(x => x.OfType<TextBlock>().NthChild(0, 3));
 
 You can also use a keyword notation in place of the formula: `odd` or `even`. So these are selectors are equivalent:
 
-```
+```xml
 <Style Selector="TextBlock:nth-child(2n)">
 <Style Selector="TextBlock:nth-child(even)">
 ```
 
-```
+```xml
 <Style Selector="TextBlock:nth-child(2n+1)">
 <Style Selector="TextBlock:nth-child(odd)">
 ```
diff --git a/docs/stay-up-to-date/release-notes.md b/docs/stay-up-to-date/release-notes.md
index 8d256babb..f46bea61d 100644
--- a/docs/stay-up-to-date/release-notes.md
+++ b/docs/stay-up-to-date/release-notes.md
@@ -113,7 +113,7 @@ https://www.nuget.org/packages/Avalonia/11.0.6
 * Fixed passing current_folder to DBus for save file dialog by @HermanKirshin in https://github.com/AvaloniaUI/Avalonia/pull/13491
 * Fix issue #11006 by correcting SelectionChanged event to be fired AFTER (not before) raising Prop. by @lnxon in https://github.com/AvaloniaUI/Avalonia/pull/13503
 * Fix ImageBrush crash when source bitmap gets disposed by @kekekeks in https://github.com/AvaloniaUI/Avalonia/pull/13506
-* fix: Navigation when CanExecute is fasle by @workgroupengineering in https://github.com/AvaloniaUI/Avalonia/pull/13507
+* fix: Navigation when CanExecute is false by @workgroupengineering in https://github.com/AvaloniaUI/Avalonia/pull/13507
 * DataGrid inertial scroll support (#13502) by @stogle in https://github.com/AvaloniaUI/Avalonia/pull/13511
 * Fix for issue #13493 by @laolarou726 in https://github.com/AvaloniaUI/Avalonia/pull/13518
 * fix: Potential TransformGroup memory leak by @workgroupengineering in https://github.com/AvaloniaUI/Avalonia/pull/13529
diff --git a/docs/tutorials/music-store-app/add-items-to-users-collection.md b/docs/tutorials/music-store-app/add-items-to-users-collection.md
index 54b3cfa16..ec6570118 100644
--- a/docs/tutorials/music-store-app/add-items-to-users-collection.md
+++ b/docs/tutorials/music-store-app/add-items-to-users-collection.md
@@ -49,7 +49,7 @@ To add the items control and its data template, follow this procedure:
 - Locate and open the **MainWindow.axaml** file.
 - Add the following namespace declaration to the `<Window>` element:
 
-```
+```xml
 xmlns:views="clr-namespace:Avalonia.MusicStore.Views"
 ```
 
diff --git a/docs/tutorials/music-store-app/album-view.md b/docs/tutorials/music-store-app/album-view.md
index a197022dc..1ab1c9b6e 100644
--- a/docs/tutorials/music-store-app/album-view.md
+++ b/docs/tutorials/music-store-app/album-view.md
@@ -66,7 +66,7 @@ As you saw on the last page, at this point the album list currently just shows t
 
 In this step you will be using the view locator class (**ViewLocator.cs** file) that was added to the project by the solution template. This class was registered (by the solution template) as a data template at the highest level in the app in the **App.axaml** file. The data template registration looks like this:
 
-```
+```xml
 <Application ...
              xmlns:local="using:Avalonia.MusicStore"
              ... >
diff --git a/docs/tutorials/music-store-app/button-command.md b/docs/tutorials/music-store-app/button-command.md
index da6bc2dd9..3316824f0 100644
--- a/docs/tutorials/music-store-app/button-command.md
+++ b/docs/tutorials/music-store-app/button-command.md
@@ -50,7 +50,7 @@ To add the button data binding, follow this procedure:
 - Locate and open the **MainWindow.axaml** file.
 - Find the XAML for the button and add the command attribute and binding, as shown:
 
-```
+```xml
 <Button HorizontalAlignment="Right" VerticalAlignment="Top"
         Command="{Binding BuyMusicCommand}">
    <PathIcon Data="{StaticResource store_microsoft_regular}"/>
diff --git a/docs/tutorials/music-store-app/opening-a-dialog.md b/docs/tutorials/music-store-app/opening-a-dialog.md
index 2fa3a63cf..7a03a2663 100644
--- a/docs/tutorials/music-store-app/opening-a-dialog.md
+++ b/docs/tutorials/music-store-app/opening-a-dialog.md
@@ -208,7 +208,7 @@ Follow this procedure:
 - Add attributes for the width and height of the dialog, set at 1000 and 550 respectively.
 - Add the start-up position attribute set to `CenterOwner`, as shown:
 
-```
+```xml
 <Window ...
     Width="1000" Height="550"
     WindowStartupLocation="CenterOwner">
diff --git a/docs/tutorials/samples.md b/docs/tutorials/samples.md
index f6145b964..cf6cb0c04 100644
--- a/docs/tutorials/samples.md
+++ b/docs/tutorials/samples.md
@@ -159,7 +159,7 @@ import SampleCardsGrid from '@site/src/components/SampleCardsGrid';
   samples={[    
   {
       title: 'Clipboard Operations',
-      description: 'This sample demonstrates how to interat with the devices clipboard and copy and paste text.',
+      description: 'This sample demonstrates how to interact with the devices clipboard and copy and paste text.',
       tags: ['XAML', 'C#', 'Clipboard'],
       url: 'https://github.com/AvaloniaUI/AvaloniaUI.QuickGuides/tree/main/ClipboardOps'
     },  
diff --git a/i18n/ru/docusaurus-plugin-content-docs/current/guides/styles-and-resources/resources.md b/i18n/ru/docusaurus-plugin-content-docs/current/guides/styles-and-resources/resources.md
index 03231ebae..1739d090b 100644
--- a/i18n/ru/docusaurus-plugin-content-docs/current/guides/styles-and-resources/resources.md
+++ b/i18n/ru/docusaurus-plugin-content-docs/current/guides/styles-and-resources/resources.md
@@ -259,7 +259,7 @@ Avalonia provides different options to access Resources from code.
 :::
 
 - **ResourceNode.Resources["TheKey"]**: <br/>
-  This will directly access the underlaying `Dictionary`. Be aware: Merged Dictionaries and parents will not be scanned. 
+  This will directly access the underlying `Dictionary`. Be aware: Merged Dictionaries and parents will not be scanned. 
 - **ResourceNode.TryGetResource**: <br/>
   This function will try to get a specific resource and return `true` if successful, otherwise `false`. Merged dictionaries will be scanned, but it will not follow the logical tree. 
 - **ResourceNode.TryFindResource**:  <br/>
diff --git a/versioned_docs/version-0.10.x/animations/keyframe-animations.md b/versioned_docs/version-0.10.x/animations/keyframe-animations.md
index 5ef0d04be..137baa6f0 100644
--- a/versioned_docs/version-0.10.x/animations/keyframe-animations.md
+++ b/versioned_docs/version-0.10.x/animations/keyframe-animations.md
@@ -37,7 +37,7 @@ The example above animates the target `Control` as defined by its [selector](../
 
 ## Triggering Animations
 
-Unlike WPF's `Triggers`, Animations defined in XAML rely on [selectors](../styling/selectors) for their triggering behavior. Selectors can always apply to a control, or they can conditionally apply \(for example if the control has a style class appled\).
+Unlike WPF's `Triggers`, Animations defined in XAML rely on [selectors](../styling/selectors) for their triggering behavior. Selectors can always apply to a control, or they can conditionally apply \(for example if the control has a style class applied\).
 
 If the selector isn't conditional then the animation will be triggered when a matching `Control` is spawned into the visual tree. Otherwise, the animations will run whenever its selector is activated. When the selector no longer matches, the currently running animation will be canceled.
 
diff --git a/versioned_docs/version-0.10.x/distribution-publishing/macos.md b/versioned_docs/version-0.10.x/distribution-publishing/macos.md
index 4db28ce68..6c2003938 100644
--- a/versioned_docs/version-0.10.x/distribution-publishing/macos.md
+++ b/versioned_docs/version-0.10.x/distribution-publishing/macos.md
@@ -7,7 +7,7 @@ macOS applications are typically distributed in a `.app` [application bundle](ht
 
 With Avalonia, you'll have a `.app` folder structure that looks like this:
 
-```csharp
+```
 MyProgram.app
 |
 ----Contents\
diff --git a/versioned_docs/version-0.10.x/guides/deep-dives/running-on-raspbian-lite-via-drm.md b/versioned_docs/version-0.10.x/guides/deep-dives/running-on-raspbian-lite-via-drm.md
index c7810282d..5136713c6 100644
--- a/versioned_docs/version-0.10.x/guides/deep-dives/running-on-raspbian-lite-via-drm.md
+++ b/versioned_docs/version-0.10.x/guides/deep-dives/running-on-raspbian-lite-via-drm.md
@@ -47,7 +47,7 @@ these [steps](https://www.raspberrypi.com/documentation/computers/compute-module
   named **ssh** (with no extension, e.q with `touch ssh`) in the boot drive of the Raspberry. This will ensure that the SSH daemon is enabled
   once the Raspberry Pi has started and you can logon over the network.
 - ***Only for Cm4** add the following to `/boot/config.txt` to enable the Usb 2.0 ports*
-```text
+```conf
 dtoverlay=dwc2,dr_mode=host
 ```
 - Start up your Raspberry and login.  
diff --git a/versioned_docs/version-0.10.x/guides/deep-dives/running-your-app-on-a-raspberry-pi.md b/versioned_docs/version-0.10.x/guides/deep-dives/running-your-app-on-a-raspberry-pi.md
index 5b9506b7c..5eb05a8e1 100644
--- a/versioned_docs/version-0.10.x/guides/deep-dives/running-your-app-on-a-raspberry-pi.md
+++ b/versioned_docs/version-0.10.x/guides/deep-dives/running-your-app-on-a-raspberry-pi.md
@@ -5,7 +5,7 @@ title: Running your app on a Raspberry Pi
 
 ### Step 1
 
-Flash 8GB SD Card with Raspbian Stretch \(2018-11-13\). `BelenaEtcher` is a nice tool for that.
+Flash 8GB SD Card with Raspbian Stretch \(2018-11-13\). `balenaEtcher` is a nice tool for that.
 
 Plug in the card and start the `Raspberry Pi`.
 
diff --git a/versioned_docs/version-0.10.x/guides/developer-guides/comparison-of-avalonia-with-wpf-and-uwp.md b/versioned_docs/version-0.10.x/guides/developer-guides/comparison-of-avalonia-with-wpf-and-uwp.md
index d78d4441c..f844750aa 100644
--- a/versioned_docs/version-0.10.x/guides/developer-guides/comparison-of-avalonia-with-wpf-and-uwp.md
+++ b/versioned_docs/version-0.10.x/guides/developer-guides/comparison-of-avalonia-with-wpf-and-uwp.md
@@ -42,7 +42,7 @@ Legend:
 | Item | Avalonia | WPF | UWP | Notes |
 | :--- | :---: | :---: | :---: | :--- |
 | DataTriggers / PropertyTrigger / EventTrigger within Style.Triggers | ✖ | ✔ | ✖ |  |
-| VisualStateManager | ✖ | ⚡ | ✔ | A different concept from WPF that takes the place of DataTriggers, this is very verbose and more often than not increases complexity compared to data triggers. @Felix-Dev VisualStateManager does exist in WPF \(it was added in .NET Framework 4.0\). It's not as elegant as in UWP though, i.e. it has no VisuaStateManager.Setters property. That means you have to use Storyboards to set your values. |
+| VisualStateManager | ✖ | ⚡ | ✔ | A different concept from WPF that takes the place of DataTriggers, this is very verbose and more often than not increases complexity compared to data triggers. @Felix-Dev VisualStateManager does exist in WPF \(it was added in .NET Framework 4.0\). It's not as elegant as in UWP though, i.e. it has no VisualStateManager.Setters property. That means you have to use Storyboards to set your values. |
 | Implicit DataTemplate | ✔ | ✔ | ✖ | Set the DataType property of the DataTemplate to the corresponding type and the template is then applied automatically to all instances of that particular type |
 | Binding in Style setter | ✔ | ✔ | ✖ | Any other than TemplateBinding isn't support in a template/style within UWP |
 | BasedOn default Style | ✖ | ✔ | ⚡ | `BasedOn={StaticResource {x:Type TextBlock}` isn't supported in UWP but works in WPF. Instead, BasedOn requires the use of a key which is a problem as not all default styles define one. This is a specific example of the missing x:Type markup extension in UWP. |
@@ -52,7 +52,7 @@ Legend:
 | Item | Avalonia | WPF | UWP | Notes |
 | :--- | :---: | :---: | :---: | :--- |
 | Coercion | ✔ | ✔ | ✖ | Coercion of Dependency Properties is not supported in UWP. |
-| Data \(Input\) Validation | ✔ | ✔ | ✖ | The entire WPF data validation system including the classes/inferfaces: ValidationRule \(and all standard implementations\), Binding.ValidationRules, IDataErrorInfo, INotifyDataErrorInfo, Binding.ValidatesOnNotifyDataErrors, etc. is not implemented in UWP. This will be added in WinUI 3.0 but the story for using this within the UWP app model with WinUI 3.0 is less clear. |
+| Data \(Input\) Validation | ✔ | ✔ | ✖ | The entire WPF data validation system including the classes/interfaces: ValidationRule \(and all standard implementations\), Binding.ValidationRules, IDataErrorInfo, INotifyDataErrorInfo, Binding.ValidatesOnNotifyDataErrors, etc. is not implemented in UWP. This will be added in WinUI 3.0 but the story for using this within the UWP app model with WinUI 3.0 is less clear. |
 | x:TypeArguments directive | ✔ | ✔ | ✖ | The TypeArguments directive isn't implemented in UWP which causes problems with generics. Missing this requires some work-arounds with classes and creating a non-generic class to use in XAML from a generic one. |
 | UIElement.IsVisible / IsVisibleChanged | ✔ | ✔ | ✖ | UWP has no way of tracking which controls are actually visible on the display. WPF has the UIElement.IsVisible property and the IsVisibleChanged event. This hinders the ability to optimize controls for performance. |
 | UIElement.Visibility / Visibility.Hidden | ⚡ | ✔ | ⚡ | UWP does not include the Visibility.Hidden enum value used for UIElement.Visibility. Hidden in WPF allowed a control to still be used in measure/layout but appear invisible when rendered for display. |
@@ -62,8 +62,8 @@ Legend:
 | VisualBrush / DrawingBrush | ✔ | ✔ | ✖ | VisualBrush is not a XAML brush in UWP. Instead, must fall back to composition brushes which are not 1:1 equivalent. DrawingBrush is not supported at all in UWP. |
 | Supplemental Shapes: Arrow, Callout, Star, etc | ✔ | ✔ | ✖ | Several shapes present in WPF are missing in UWP. |
 | Adorner | ✔ | ✔ | ✖ | [Adorners overview](https://docs.microsoft.com/en-us/dotnet/framework/wpf/controls/adorners-overview) |
-| Thickness | ✔ | ✔ | ⚡ | The Thickness struct exposes fields for Top, Bottom, Left and Right instead of dependency properties as in WPF. This means you cannot Bind or asign resources to an individual thickness parameter. |
-| Size / Rect / Point | ✔ | ✔ | ✔ | Size, Rect and Point are fully supported in both WPF and UWP. However, UWP uses single-precision float types for properties instead of double in WPF. This creates an incompatiblity when porting code. |
+| Thickness | ✔ | ✔ | ⚡ | The Thickness struct exposes fields for Top, Bottom, Left and Right instead of dependency properties as in WPF. This means you cannot Bind or assign resources to an individual thickness parameter. |
+| Size / Rect / Point | ✔ | ✔ | ✔ | Size, Rect and Point are fully supported in both WPF and UWP. However, UWP uses single-precision float types for properties instead of double in WPF. This creates an incompatibility when porting code. |
 | ItemsControl.AlternationIndex / ItemsControl.AlternationCount | ✖ | ✔ | ✖ | WPF has an easy way to change the style of items in a list using ItemsControl.AlternationIndex and ItemsControl.AlternationCount. This allows, for example, to change the background color of a listed item for even/odd entries. UWP doesn't support this at all in any controls. The partial work-around in UWP is to create a new control deriving from the framework's implementation and override the PrepareContainerForItemOverride\(\) method. |
 | Custom Cursor at runtime | ✔ | ✔ | ✖ |  |
 | Sub-pixel anti-aliasing | ✔ | ✔ | ✖ | Anti-aliasing in UWP along with rendering in general is poor compared to WPF. It's assumed this is for performance reasons on mobile devices and the web \(Silverlight\). |
@@ -121,7 +121,7 @@ This section describes the differences in controls in vanilla WPF and UWP \(with
 | ItemsControl | ✖ | ItemsControl |  |
 | ItemsPresenter | ✖ | ItemsPresenter |  |
 | ItemsRepeater | ✖ | ItemsRepeater | First introduced in the Windows UI Library |
-| Label | Label | ✖ | For compatiblity with Windows Forms |
+| Label | Label | ✖ | For compatibility with Windows Forms |
 | ListBox | ListBox | ListBox |  |
 | ✖ | ListView | ListView |  |
 | ✖ | ✖ | MapControl |  |
@@ -184,7 +184,7 @@ This section describes the differences in controls in vanilla WPF and UWP \(with
 * Several UWP controls have reentrancy issues. For example, changing the selected item while in a ComboBox SelectionChanged event is largely not possible and will result in a crash. This makes validation directly in the event handler nearly impossible.
 * UWP controls are generally not as powerful as the WPF counterparts. For example, for several years the ComboBox in UWP was not editable. The UWP DatePicker also does not allow typing in a specific date.
 * UWP has no support for data \(input\) validation. This is a large issue for line-of-business apps migrating from WPF to UWP that heavily use this feature in view models or binding.
-* The UWP styling system is different enough from WPF to require extra effort during porting. UWP uses the VistualStateManger instead of concepts like DataTriggers or EventTriggers from WPF. Styling/Templating are one of the main differences.
+* The UWP styling system is different enough from WPF to require extra effort during porting. UWP uses the VisualStateManger instead of concepts like DataTriggers or EventTriggers from WPF. Styling/Templating are one of the main differences.
 * The ResourceDictionary XAML markup in UWP supports far fewer features than in WPF.
 * UWP seems to follow only the XAML/2006 spec instead of [XAML/2009](https://docs.microsoft.com/en-us/dotnet/desktop/xaml-services/xaml-2009-language-features) supported by WPF
 * Several UWP controls are sealed and new controls cannot derive from them
diff --git a/versioned_docs/version-0.10.x/tutorials/music-store-app/add-content-to-dialog.md b/versioned_docs/version-0.10.x/tutorials/music-store-app/add-content-to-dialog.md
index 7a6170b92..365eb6a08 100644
--- a/versioned_docs/version-0.10.x/tutorials/music-store-app/add-content-to-dialog.md
+++ b/versioned_docs/version-0.10.x/tutorials/music-store-app/add-content-to-dialog.md
@@ -87,7 +87,7 @@ namespace Avalonia.MusicStore.ViewModels
 
 Here we can see that we have a normal getter which returns the field, and we have a Setter that calls a method.
 
-This calls `RaiseAndSetIfChanged` this method checks to see if `value` is different from the current `_seachText` field and if so, it changes it to the new value, and then raises an event to notify the `View` that it has changed.
+This calls `RaiseAndSetIfChanged` this method checks to see if `value` is different from the current `_searchText` field and if so, it changes it to the new value, and then raises an event to notify the `View` that it has changed.
 
 Any View that has a `{Binding SearchText}` expression will automatically update, and stay in sync with this property.
 
@@ -219,7 +219,7 @@ This ViewLocator is a special `DataTemplate` that will take the typename, in thi
 
 If the ListBox finds one, it will display whatever `xaml` that `View` describes inside the `ListBox`, otherwise it will just show the typename inside the `ListBox` as a string.
 
-Lets test this by adding a contructor on the `MusicStoreViewModel.cs`.
+Lets test this by adding a constructor on the `MusicStoreViewModel.cs`.
 
 ```csharp
 public MusicStoreViewModel()
@@ -234,7 +234,7 @@ Before we can run this we need to add our `MusicStoreView` to our `MusicStoreWin
 
 At the top of `MusicStoreWindow.axaml` you will find some lines that begin `xmlns:x` etc.. add a line:
 
-```markup
+```xml
 xmlns:local="using:Avalonia.MusicStore.Views"
 ```
 
@@ -316,7 +316,7 @@ This shows a `StackPanel` to contain the controls. They are:
 
 A border with a `Corner` radius set, and `ClipToBounds` set to `True`, this means that the content will be clipped with rounded corners.
 
-The border contains a `Panel` with a `Background` set, using a hexadecimal colour code.
+The border contains a `Panel` with a `Background` set, using a hexadecimal color code.
 
 This `Panel` contains an `Image` and a `PathIcon` in front of it. Add the source for the Icon to `Icons.axaml`:
 
diff --git a/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-a-modern-looking-window.md b/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-a-modern-looking-window.md
index 78b9f1a28..ad647c698 100644
--- a/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-a-modern-looking-window.md
+++ b/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-a-modern-looking-window.md
@@ -18,8 +18,8 @@ Let's try and make this look a little more modern by applying `Dark` mode and so
 ```xml
 <Application xmlns="https://github.com/avaloniaui"
              xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
-             x:Class="Avolonia.MusicStore.App"
-             xmlns:local="using:Avolonia.MusicStore"
+             x:Class="Avalonia.MusicStore.App"
+             xmlns:local="using:Avalonia.MusicStore"
              RequestedThemeVariant="Dark">
              <!-- "Default" ThemeVariant follows system theme variant. "Dark" or "Light" are other available options. -->
 ```
diff --git a/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-the-project.md b/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-the-project.md
index 92d67f8fe..40bb9d28d 100644
--- a/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-the-project.md
+++ b/versioned_docs/version-0.10.x/tutorials/music-store-app/creating-the-project.md
@@ -40,7 +40,7 @@ Some of the important files are:
 | MainWindow.axaml | This is the `xaml` UI code that describes how the `MainWindow` looks and its contents. |
 | App.axaml | This is a `xaml` file that sets up the application, it chooses the theme the UI will use and declares the `ViewLocator` `DataTemplate`. |
 | Program.cs | `Main` method where the program starts and `Avalonia` is configured and started. |
-| ViewLocator.cs | `ViewLocator` is a special `DataTemplate`. When some `Data` appears in the UI, it quickly looks to see if a `View` exists for it. This is done by naming convention. If the datas `Type` is `MyDataViewModel` then the `ViewLocator` will use the `View` named `MyDataView` \(if it exists\) in that part of the UI. This is very powerful for list based controls \(`ItemsControl`, `ListBox`, etc\) and `ContentControl`. |
+| ViewLocator.cs | `ViewLocator` is a special `DataTemplate`. When some `Data` appears in the UI, it quickly looks to see if a `View` exists for it. This is done by naming convention. If the data's `Type` is `MyDataViewModel` then the `ViewLocator` will use the `View` named `MyDataView` \(if it exists\) in that part of the UI. This is very powerful for list based controls \(`ItemsControl`, `ListBox`, etc\) and `ContentControl`. |
 
 ### Compiling and Running the Project
 
diff --git a/versioned_docs/version-0.10.x/tutorials/running-in-the-browser.md b/versioned_docs/version-0.10.x/tutorials/running-in-the-browser.md
index c0c18966e..48930e8de 100644
--- a/versioned_docs/version-0.10.x/tutorials/running-in-the-browser.md
+++ b/versioned_docs/version-0.10.x/tutorials/running-in-the-browser.md
@@ -46,7 +46,7 @@ Avalonia app is compatible with standard **[JSImport]/[JSExport]** interop from
 ## Legacy Blazor backend
 
 Starting from Avalonia 11.0 [Avalonia.Web](https://www.nuget.org/packages/Avalonia.Web/) package relies on build-in .NET interop with better stability and performance.
-Legacy Blazor backend is still available for compatability and can be referenced using [Avalonia.Web.Blazor](https://www.nuget.org/packages/Avalonia.Web.Blazor/) package.
+Legacy Blazor backend is still available for compatibility and can be referenced using [Avalonia.Web.Blazor](https://www.nuget.org/packages/Avalonia.Web.Blazor/) package.
 
 
 ## Troubleshooting
diff --git a/versioned_docs/version-0.10.x/wpf-developer-tips/index.md b/versioned_docs/version-0.10.x/wpf-developer-tips/index.md
index 65c700f41..d76af132b 100644
--- a/versioned_docs/version-0.10.x/wpf-developer-tips/index.md
+++ b/versioned_docs/version-0.10.x/wpf-developer-tips/index.md
@@ -24,24 +24,24 @@ Avalonia is in general very similar to WPF, but you will find differences. Here
 If you use `Application.Current.Dispatcher`, you should use `Dispatcher.UIThread` instead which provide similar facilities.
 
 **WPF**
-```
+```csharp
 Application.Current.Dispatcher.InvokeAsync(handler, DispatcherPriority.Background);
 ```
 
 **Avalonia**
-```
+```csharp
 Dispatcher.UIThread.InvokeAsync(handler, DispatcherPriority.Background);
 ```
 
 If you previously access dispatcher on the control itself, you should use global static instance `Dispatcher.UIThread` too.
 
 **WPF**
-```
+```csharp
 this.Dispatcher.InvokeAsync(handler, DispatcherPriority.Background);
 ```
 
 **Avalonia**
-```
+```csharp
 Dispatcher.UIThread.InvokeAsync(handler, DispatcherPriority.Background);
 ```
 
@@ -54,21 +54,21 @@ WPF has uses `Visibility` property which can be `Collapsed`, `Hidden` or `Visibl
 # Binding
 
 **WPF**
-```
+```xml
 <TextBox Name="MyTextbox" Text="{Binding ElementName=searchTextBox, Path=Text}"" />
 ```
 
 **Avalonia**
-```
+```xml
 <TextBox Name="MyTextbox" Text="{Binding #searchTextBox.Text}" />
 ```
 
 # Handling attachment to visual tree
 
-There no events like `Loaded`/`Unloaded` in Avalonia, but you can override `OnAttachedToVisualTree`/`OnDetachedFromVisualTree` on the control, to know when control attached to virtual tree, or detatched from it. Alternatively you can use `TemplateApplied` instead of `Loaded` event.
+There no events like `Loaded`/`Unloaded` in Avalonia, but you can override `OnAttachedToVisualTree`/`OnDetachedFromVisualTree` on the control, to know when control attached to virtual tree, or detached from it. Alternatively you can use `TemplateApplied` instead of `Loaded` event.
 
 **WPF**
-```
+```csharp
 Unloaded += OnControl_Unloaded;
 Loaded += OnControl_Loaded;
 
@@ -84,7 +84,7 @@ private void OnControl_Unloaded(object sender, RoutedEventArgs e)
 ```
 
 **Avalonia**
-```
+```csharp
 TemplateApplied += OnControl_Loaded;
 private void OnControl_Loaded(object sender, RoutedEventArgs e)
 {
diff --git a/xpf/advanced/customizing-init.md b/xpf/advanced/customizing-init.md
index b0d353b5a..be8a03869 100644
--- a/xpf/advanced/customizing-init.md
+++ b/xpf/advanced/customizing-init.md
@@ -56,7 +56,7 @@ In the above example `App` is your XPF `Application` class defined in `App.xaml.
 
 Configure your project to use the new `Main` method by adding the following to your `.csproj`:
 
-```
+```xml
  <PropertyGroup>
      <StartupObject>MyXpfApp.Program</StartupObject>
  </PropertyGroup>
@@ -92,7 +92,7 @@ public class MyAvaloniaApp : Application
 }
 ```
 
-```csharp title="MyAvaloniaApp.axaml"
+```xml title="MyAvaloniaApp.axaml"
 <Application xmlns="https://github.com/avaloniaui"
              xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
              x:Class="MyXpfApp.MyAvaloniaApp">
diff --git a/xpf/advanced/key-mapping.md b/xpf/advanced/key-mapping.md
index 8107c098c..de3a94871 100644
--- a/xpf/advanced/key-mapping.md
+++ b/xpf/advanced/key-mapping.md
@@ -62,9 +62,9 @@ private void OnMapKey(object? sender, XpfMapKeyEventArgs e)
 
 Modifier keys can be mapped in one of two ways:
 
-The first option is to handle the initial modifier key press. An example of this would be receiving `e.Key == System.Windows.Input.Key.LeftCtrl` and setting `e.MappedKey = System.Windows.Input.Key.LeftAlt` in response. In this case, the application will receive a `KeyDown`/`KeyUp` event pair for `LeftAlt`; and `Keyboard.Modifiers` will be set to `Alt` for the duration of the key press. `e.MappedModifers` does not need to be touched in this case.
+The first option is to handle the initial modifier key press. An example of this would be receiving `e.Key == System.Windows.Input.Key.LeftCtrl` and setting `e.MappedKey = System.Windows.Input.Key.LeftAlt` in response. In this case, the application will receive a `KeyDown`/`KeyUp` event pair for `LeftAlt`; and `Keyboard.Modifiers` will be set to `Alt` for the duration of the key press. `e.MappedModifiers` does not need to be touched in this case.
 
-The problem with this technique is that often it's not known what the modifier should be mapped to until the second key is pressed. In this case, one should wait for the second key press and set `e.MappedModifiers`. Bear in mind when using this technique that the raised `KeyDown` events will not match the current `Keyboard.Modifiers` value. That is, no "fake" `KeyDown` events will be raised for the modifier key, the mapping will only be reflected by `Keyboard.Modifers` and `Keyboard.IsKeyDown`.
+The problem with this technique is that often it's not known what the modifier should be mapped to until the second key is pressed. In this case, one should wait for the second key press and set `e.MappedModifiers`. Bear in mind when using this technique that the raised `KeyDown` events will not match the current `Keyboard.Modifiers` value. That is, no "fake" `KeyDown` events will be raised for the modifier key, the mapping will only be reflected by `Keyboard.Modifiers` and `Keyboard.IsKeyDown`.
 
 ## Conditional Mapping
 
diff --git a/xpf/advanced/window-handles.md b/xpf/advanced/window-handles.md
index 938588afa..8a14a65cc 100644
--- a/xpf/advanced/window-handles.md
+++ b/xpf/advanced/window-handles.md
@@ -20,5 +20,5 @@ if (XpfWpfAbstraction.GetAvaloniaWindowForWindow(xpfWindow) is { } avaloniaWindo
 ```
 
 :::note
-The type of the handle retreived in this manner will be different depending on the OS platform and cannot be passed to the win32 API emulation layer. For example, on Windows it will be a `HWND` but on macOS it will be an `NSWindow` pointer. The type of the handle can be retreived by using the `IPlatformHandle.HandleDescriptor` property.
-:::
\ No newline at end of file
+The type of the handle retrieved in this manner will be different depending on the OS platform and cannot be passed to the win32 API emulation layer. For example, on Windows it will be a `HWND` but on macOS it will be an `NSWindow` pointer. The type of the handle can be retrieved by using the `IPlatformHandle.HandleDescriptor` property.
+:::
diff --git a/xpf/embedding/avalonia-in-xpf/adding-style-to-avalonia-control-in-xpf.md b/xpf/embedding/avalonia-in-xpf/adding-style-to-avalonia-control-in-xpf.md
index ca193eda6..18f4eb34f 100644
--- a/xpf/embedding/avalonia-in-xpf/adding-style-to-avalonia-control-in-xpf.md
+++ b/xpf/embedding/avalonia-in-xpf/adding-style-to-avalonia-control-in-xpf.md
@@ -5,7 +5,7 @@ title: Adding style to Avalonia control in XPF
 
 # Adding Style to the Avalonia control in XPF
 
-In XPF you can add Style to the Avalonia control only with the code-behind. Plese consider the sample below.
+In XPF you can add Style to the Avalonia control only with the code-behind. Please consider the sample below.
 
 ## XAML Code
 
diff --git a/xpf/platforms/linux.md b/xpf/platforms/linux.md
index f95ce8ba9..6ee07d937 100644
--- a/xpf/platforms/linux.md
+++ b/xpf/platforms/linux.md
@@ -40,7 +40,7 @@ If you have installed .NET from your distribution's package repository, you must
 
 The following dependencies are required to run XPF: `libice6 libsm6 libfontconfig1 libgdiplus`
 
-On a [Debian-based distibution](https://en.wikipedia.org/wiki/Category:Debian-based_distributions) run the following command to install these dependencies:
+On a [Debian-based distribution](https://en.wikipedia.org/wiki/Category:Debian-based_distributions) run the following command to install these dependencies:
 
 ```bash
 sudo apt install libice6 libsm6 libfontconfig1 libgdiplus
diff --git a/xpf/troubleshooting.md b/xpf/troubleshooting.md
index f4904cbbb..9ad072f8a 100644
--- a/xpf/troubleshooting.md
+++ b/xpf/troubleshooting.md
@@ -34,7 +34,7 @@ If you are unable to login with your license key, it may have expired. Ask suppo
 
 Run the following commands from the command-line:
 
-```
+```bash
 dotnet nuget locals http-cache --clear
 dotnet restore
 ```
@@ -53,7 +53,7 @@ Typically, there are two possible ways to listen for Avalonia logs
 
 ### .LogToTrace in a custom Avalonia initialization
 
-1. Follow [instructions](./customizing-init) on how to setup custom Avalonia intiialization.
+1. Follow [instructions](./customizing-init) on how to setup custom Avalonia initialization.
 2. Then you will be able to call `.LogToTrace()` with optional severity parameter in the AppBuilder chain, like this:
 ```diff
         AppBuilder.Configure<AvaloniaUI.Xpf.Helpers.DefaultXpfAvaloniaApplication>()
@@ -66,7 +66,7 @@ This will redirect all Avalonia logs to the .NET Trace listener. Which can be re
 
 ### Override Logger.Sink
 
-Static property `Logger.Sink` has a public setter and can be overriden by custom implementation.
+Static property `Logger.Sink` has a public setter and can be overridden by custom implementation.
 ```csharp
 public void Initialize()
 {