Spelling fixes

Co-authored-by: Furkat Gofurov <[email protected]>

Author: Danil-Grigorev

docs/book/src/03_topics/02_configuration/01_air-gapped-environtment.md

@@ -67,7 +67,7 @@ When working with metadata and component files within OCI artifacts, the files s
   - Typed: `fmt.Sprintf("%s-components.yaml", p.GetType())`, Example: `infrastructure-components.yaml`
   - Versioned: `fmt.Sprintf("%s-%s-%s-components.yaml", p.GetType(), p.GetName(), p.GetSpec().Version)`, Example: `infrastructure-azure-v1.9.3-components.yaml`
 
-Versioned files allow to use single image for hosting multiple provider manifests and versions simulaniously, without overlapping each other.
+Versioned files allow to use single image for hosting multiple provider manifests and versions simultaneously, without overlapping each other.
 
 Typed allow to store multiple provider types inside single image, which is needed for example for `bootstrap` and `control-plane` providers.
 

docs/book/src/03_topics/03_plugin/02_preload_subcommand.md

@@ -2,7 +2,7 @@
 
 ## Overview
 
-The `preload` subcommand allows users to preload provider `ConfigMaps` into a management cluster from an OCI (Open Container Initiative) artifact, known provider source, or URL override. User can supply any number of provider stings or discover and use existing provider manifests from the cluster.
+The `preload` subcommand allows users to preload provider `ConfigMaps` into a management cluster from an OCI (Open Container Initiative) artifact, known provider source, or URL override. Users can supply any number of provider stings or discover and use existing provider manifests from the cluster.
 
 ## Command Syntax
 The basic syntax for using the `preload` command is: