Merge branch 'main' into patch-7

content/md/en/docs/deploy/keys-and-network-operations.md

@@ -36,12 +36,12 @@ Session keys are private online keys that are used by validators to sign consens
 Session keys must be available online to enable the validator to perform certain network operations.
 
 These keys aren't used to control funds and they should only be used for their intended purpose.
-They can be changed regularly
+They can be changed regularly.
 To create session keys, a validator node operator must use a controller account too generate a certificate signed with the session's public key.
 The certificate attests that the key acts on behalf of the validator's staking account and nominators.
 After creating the session key, the validator node operator informs the chain that this key represents the controller key by
 publishing the session certificate in a transaction on the chain.
-In most cases, node operators use the [Session](https://paritytech.github.io/substrate/master/pallet_session/index.html)) pallet to manage their session keys.
+In most cases, node operators use the [Session](https://paritytech.github.io/substrate/master/pallet_session/index.html) pallet to manage their session keys.
 
 The [`SessionKeys`](https://paritytech.github.io/substrate/master/sp_session/index.html)
 trait is a generic, indexable type and you can declare any number of session keys in the runtime.

content/md/en/docs/maintain/runtime-upgrades.md

@@ -19,7 +19,7 @@ If a runtime upgrade requires changes to the existing state, it is likely to req
 
 In [Build process](/main-docs/build/build-process/), you learned that compiling a node generated both a platform-native binary and a WebAssembly binary and that selecting which binary to use at different points in the block production process can be controlled by execution strategy command-line options.
 The component that selects the runtime execution environment to communicate with is called the **executor**.
-Although you can override the default execution strategies for custom scenarios, in most cases, or the executor select the appropriate binary to use by evaluating the following information for both the native and WebAssembly runtime binaries:
+Although you can override the default execution strategies for custom scenarios, in most cases the executor select the appropriate binary to use by evaluating the following information for both the native and WebAssembly runtime binaries:
 
 - `spec_name`
 - `spec_version`