Fix typos

bridges/modules/parachains/src/lib.rs

@@ -1470,7 +1470,7 @@ pub(crate) mod tests {
 			);
 
 			// then if someone is pretending to provide updated head#10 of parachain#1 at relay
-			// block#30, and actualy provides it
+			// block#30, and actually provides it
 			//
 			// => we'll update value
 			proceed(30, state_root_10_at_30);

docs/contributor/STYLE_GUIDE.md

@@ -161,4 +161,4 @@ See the config file for the exact rules.
 You may find useful
 
 - [Taplo VSCode extension](https://marketplace.visualstudio.com/items?itemName=tamasfe.even-better-toml)
-- For NeoVim, [taplo is avaliable with Mason](https://github.com/williamboman/mason-lspconfig.nvim#available-lsp-servers)
+- For NeoVim, [taplo is available with Mason](https://github.com/williamboman/mason-lspconfig.nvim#available-lsp-servers)

docs/sdk/src/meta_contributing.rs

@@ -43,7 +43,7 @@
 //! The following guidelines are meant to be the guiding torch of those who contribute to this
 //! crate.
 //!
-//! 1. 🔺 Ground Up: Information should be layed out in the most ground-up fashion. The lowest level
+//! 1. 🔺 Ground Up: Information should be laid out in the most ground-up fashion. The lowest level
 //!    (i.e. "ground") is Rust-docs. The highest level (i.e. "up") is "outside of this crate". In
 //!    between lies [`reference_docs`] and [`guides`], from low to high. The point of this principle
 //!    is to document as much of the information as possible in the lower level media, as it is

docs/sdk/src/reference_docs/extrinsic_encoding.rs

@@ -172,7 +172,7 @@
 //! }
 //! ```
 //!
-//! The bytes representing `call_data` and `signed_extensions_extra` can be obtained as descibed
+//! The bytes representing `call_data` and `signed_extensions_extra` can be obtained as described
 //! above. `signed_extensions_additional` is constructed by SCALE encoding the
 //! ["additional signed" data][sp_runtime::traits::SignedExtension::AdditionalSigned] for each
 //! signed extension that the chain is using, in order.