diff --git a/docs/developer-guide/architecture/authz-authn.md b/docs/developer-guide/architecture/authz-authn.md
index af32a9176eec9..921b744f2ea8a 100644
--- a/docs/developer-guide/architecture/authz-authn.md
+++ b/docs/developer-guide/architecture/authz-authn.md
@@ -7,7 +7,7 @@ enforced.
 
 ## Logical layers
 
-The diagram bellow suggests 4 different logical layers (represented by
+The diagram below suggests 4 different logical layers (represented by
 4 boxes: HTTP, gRPC, AuthN and AuthZ) inside Argo CD API server that
 collaborate to provide authentication and authorization. 
 
diff --git a/docs/developer-guide/extensions/proxy-extensions.md b/docs/developer-guide/extensions/proxy-extensions.md
index 1511b199c2063..f1360576b213e 100644
--- a/docs/developer-guide/extensions/proxy-extensions.md
+++ b/docs/developer-guide/extensions/proxy-extensions.md
@@ -63,7 +63,7 @@ data:
             server: https://some-cluster
 ```
 
-Note: There is no need to restart Argo CD Server after modifiying the
+Note: There is no need to restart Argo CD Server after modifying the
 `extension.config` entry in Argo CD configmap. Changes will be
 automatically applied. A new proxy registry will be built making
 all new incoming extensions requests (`<argocd-host>/extensions/*`) to