diff --git a/docs/administrator.md b/docs/administrator.md
index 7bb30cd3a..9bff446c3 100644
--- a/docs/administrator.md
+++ b/docs/administrator.md
@@ -763,7 +763,7 @@ in 5.):
 7. WAL and logical backup settings from operator config
 
 The `envFrom` section is treated separately and allows for a very flexible
-local configuration referecing a config map or secret.
+local configuration referencing a ConfigMap or a Secret.
 
 ### Via ConfigMap
 
diff --git a/docs/index.md b/docs/index.md
index 6a3a5cc44..40626e25b 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -47,8 +47,8 @@ flexibility to complement it with other tools like [ZMON](https://opensource.zal
 Here is a diagram, that summarizes what would be created by the operator, when a
 new Postgres cluster CRD is submitted:
 
-![Features](docs/diagrams/neutral_operator_dark.png#gh-dark-mode-only)
-![Features](docs/diagrams/neutral_operator_light.png#gh-light-mode-only)
+![Features](diagrams/neutral_operator_dark.png#gh-dark-mode-only)
+![Features](diagrams/neutral_operator_light.png#gh-light-mode-only)
 
 ## Status
 
diff --git a/docs/migrate.md b/docs/migrate.md
index 35756cd12..33aa847c6 100644
--- a/docs/migrate.md
+++ b/docs/migrate.md
@@ -6,7 +6,7 @@ Version 2.0 changes some default settings and removes deprecated fields. Please
 
 The new operator will default password encryption to `scram-sha-256`. Unless you configure `password_encryption: md5` in the manifest under `spec.postgresql.parameters` the operator will encrypt existing passwords in the secrets with `scram-sha-256` and alter the database passwords. Make sure that your used clients and drivers support `scram-sha-256` as pods will get rotated in rolling fashion after updating to Postgres Operator v2.
 
-The default Spilo image (`spilo-18:4.1-p2`) still configures the pg_hba.conf file to allow `md5` passwords but Postgres will validate `scram-sha-256` passwords correctly. Passwords of users that are not managed by the operator and are still `md5` enrypted need be altered before the next tagged Spilo image which will drop `md5` completely.
+The default Spilo image (`spilo-18:4.1-p2`) still configures the pg_hba.conf file to allow `md5` passwords but Postgres will validate `scram-sha-256` passwords correctly. Passwords of users that are not managed by the operator and are still `md5` encrypted need be altered before the next tagged Spilo image which will drop `md5` completely.
 
 ## K8s Endpoints are deprecated