diff --git a/DEPLOYMENT.md b/DEPLOYMENT.md
index 79acd087..2a8e1e3c 100644
--- a/DEPLOYMENT.md
+++ b/DEPLOYMENT.md
@@ -140,7 +140,7 @@ Once the release is defined, create a pull request from the `release/X.Y(.Z)` br
     - deployments: folder with general info of the contracts deployed in several networks.
         - <network_id>.json : info on the current state of the contracts deployed on the network
         - multisigs.json: info on the admin multisigs on each network
-        - relayers.json: info on the (usually) priviledged EOAs needed. Tipically OZ Defender relayers.
+        - relayers.json: info on the (usually) privileged EOAs needed. Tipically OZ Defender relayers.
 ```
 
 # Config files for pre-defined tasks
@@ -152,7 +152,7 @@ These json files hold the info that the tasks will use to interact with the cont
 To make the config files less error prone, there are some parameter substitutions allowed:
 - `deployment.<contract-key>`: address of a deployed contract/proxy found in `/releases/deployments/<network>.json`. Example `deployment.access-manager`. This could reference contracts being deployed in the same release, as long as they precede this reference in the config file (previous entries).
 - `deployment.multisig`: admin multisig address for the network as defined in `/releases/deployments/multisigs.json`.
-- `deployment.relayer`: priviledged EOAs (usually OZ Defender Relayers) for the network as defined in `/releases/deployments/relayers.json`.
+- `deployment.relayer`: privileged EOAs (usually OZ Defender Relayers) for the network as defined in `/releases/deployments/relayers.json`.
 - `roles.<IDENTIFIER_ROLE>`: keccack256 hash of the identifier of a role, as defined in `Roles.sol` or the Forta token contracts.
 - **NOTE:** All parameters must be strings, numbers included, to not trigger overflow errors on BigNumber conversion.
 
diff --git a/contracts/components/_old/scanners/ScannerRegistry_0_1_3.sol b/contracts/components/_old/scanners/ScannerRegistry_0_1_3.sol
index 54572af7..ccd2de1a 100644
--- a/contracts/components/_old/scanners/ScannerRegistry_0_1_3.sol
+++ b/contracts/components/_old/scanners/ScannerRegistry_0_1_3.sol
@@ -1402,7 +1402,7 @@ abstract contract ForwardedContext is ContextUpgradeable {
     /// @custom:oz-upgrades-unsafe-allow constructor
     constructor(address trustedForwarder) {
         // WARNING: do not set this address to other than a deployed Forwarder instance.
-        // Forwarder is critical infrastructure with priviledged address, it is safe for the limited
+        // Forwarder is critical infrastructure with privileged address, it is safe for the limited
         // functionality of the Forwarder contract, any other EOA or contract could be a security issue.
         _trustedForwarder = trustedForwarder;
     }
diff --git a/contracts/components/utils/ForwardedContext.sol b/contracts/components/utils/ForwardedContext.sol
index baec0839..a7993860 100644
--- a/contracts/components/utils/ForwardedContext.sol
+++ b/contracts/components/utils/ForwardedContext.sol
@@ -13,7 +13,7 @@ abstract contract ForwardedContext is ContextUpgradeable {
     /// @custom:oz-upgrades-unsafe-allow constructor
     constructor(address trustedForwarder) {
         // WARNING: do not set this address to other than a deployed Forwarder instance.
-        // Forwarder is critical infrastructure with priviledged address, it is safe for the limited
+        // Forwarder is critical infrastructure with privileged address, it is safe for the limited
         // functionality of the Forwarder contract, any other EOA or contract could be a security issue.
         _trustedForwarder = trustedForwarder;
     }
diff --git a/subgraph/README.md b/subgraph/README.md
index 1f0f6534..3f206fd6 100644
--- a/subgraph/README.md
+++ b/subgraph/README.md
@@ -1,5 +1,5 @@
 # Forta Subgraph 
-The Forta subgraph is currently hosted on chainstack (both dev and production enviornments) and provides visibility to on-chain events around the forta protocol such as staking, rewards, node pools, etc.
+The Forta subgraph is currently hosted on chainstack (both dev and production environments) and provides visibility to on-chain events around the forta protocol such as staking, rewards, node pools, etc.
 
 ## Deployment