docs: fix spelling issues (#18799)

Fix typos in docs.

docs/content/concepts/sui-architecture/epochs.mdx

@@ -20,7 +20,7 @@ Reconfiguration is a critical process occurring at the end of each epoch. It inv
     - **Synchronous moment:** This is the only fully synchronous event in the network, crucial for maintaining consistency.
 1. **Distribution of gas rewards**
     - Computation gas fees are distributed to the validator staking reward pool, from which stakers can withdraw.
-    - Storage fees are allocated to a storage fund, playing a vital role in the Sui tokenomics, as explaiend in [Tokenomics](../tokenomics.mdx).
+    - Storage fees are allocated to a storage fund, playing a vital role in the Sui tokenomics, as explained in [Tokenomics](../tokenomics.mdx).
 1. **Validator set change**
     - Any pending staking and unstaking requests during the epoch are finalized and reflected in validators stake distribution.
     - Any pending validator change requests are also processed, including adding new validators and removing existing validators. This is the sole opportunity for altering the validator set and stake distribution.

docs/content/concepts/sui-architecture/sui-security.mdx

@@ -35,7 +35,7 @@ A private signature key also corresponds to a public address on the Sui network
 
 ### Smart contracts define asset types and their logic {#smart-contracts}
 
-All assets have a type that is defined within a Sui Smart Contract. Sui provides a few system contracts, such as these used to manage the SUI native token, yet also allows anyone to write and submit custom smart contracts. A transaction on an asset type can call operations defined in only the smart contract that defined the asset type, and is constrained by the logic in the contract.
+All assets have a type that is defined within a Sui Smart Contract. Sui provides a few system contracts, such as those used to manage the SUI native token, yet also allows anyone to write and submit custom smart contracts. A transaction on an asset type can call operations defined in only the smart contract that defined the asset type, and is constrained by the logic in the contract.
 
 For this reason, users are encouraged to operate on their assets using smart contracts they trust, that they or others they trust have audited, and understand the logic they define for operations on their assets. Sui smart contracts are defined as immutable assets to allow third parties to audit them and also prevent their modification to increase assurance.
 

docs/content/concepts/sui-move-concepts/packages/automated-address-management.mdx

@@ -24,7 +24,7 @@ Previously a `published-at` entry was **mandatory** in the `Move.toml` file, whi
                         --latest-id 'LATEST-ADDRESS' \
                         --version-number 'VERSION-NUMBER'
       ```
-      - `ORIGINAL-ADDRESS` should be the address your package was first published at. If you never upgraded your package, this the same address as your `published-at` address in the `Move.toml`
+      - `ORIGINAL-ADDRESS` should be the address your package was first published at. If you never upgraded your package, this is the same address as your `published-at` address in the `Move.toml`
       - `LATEST-ADDRESS` should be the latest package address. If you never upgraded your package, it is the same as `ORIGINAL-ADDRESS`. If you upgraded your package, this is the same address as your current `published-at` address in the `Move.toml`.
       - `VERSION-NUMBER` is `1` if you never upgraded your package. Otherwise, it is a number greater than `1` depending on how many times you upgraded your package. In this case, look up the package at `LATEST-ADDRESS` to determine the version number.
 1. Delete the `published-at` line in your `Move.toml`.