diff --git a/website/blog/2023-04-22-monorepos-are-great/item.md b/website/blog/2023-04-22-monorepos-are-great/item.md
index e90e95d2d..301ade96d 100644
--- a/website/blog/2023-04-22-monorepos-are-great/item.md
+++ b/website/blog/2023-04-22-monorepos-are-great/item.md
@@ -98,7 +98,7 @@ The challenges for multi-repos are basically the inverse of the advantages of a
 
 We are still a small company here at Authentik Security, moving fast to grow our product’s feature set and leap-frog our competitors, while staying true to our open source origins. We want to innovate, release, and at this stage, tilt towards rapid development. Our engineers and infrastructure team have the ability and desire to collaborate closely and learn from one another; this culture is important going forward, and using a monorepo works as a compelling incentive for team transparency and support across the projects.
 
-The history of authenik provides some additional insight into our use of a monorepo; as the single maintainer for many years, a monorepo was simply easier for me to manage, and even as our wonderful community grew and contributions increased and sponsors appeared, the benefits of a monorepo remain.
+The history of authentik provides some additional insight into our use of a monorepo; as the single maintainer for many years, a monorepo was simply easier for me to manage, and even as our wonderful community grew and contributions increased and sponsors appeared, the benefits of a monorepo remain.
 
 So for us, at this stage, we benefit greatly from using a monorepo for the vast majority of our code base (and documentation). Using a monorepo means that as a team, we closely integrate our work: coding, documentation, test suites, refactoring efforts, common dependencies and tooling.
 
diff --git a/website/integrations/services/rocketchat/index.md b/website/integrations/services/rocketchat/index.md
index 55df4bccc..5b4dbbc64 100644
--- a/website/integrations/services/rocketchat/index.md
+++ b/website/integrations/services/rocketchat/index.md
@@ -76,7 +76,7 @@ In Rocket.chat, follow the procedure below:
 
 3. In the top right corner, click _Add custom oauth_
 
-4. Give your new oauth the name of _Authenik_, then click _Send_
+4. Give your new oauth the name of _Authentik_, then click _Send_
 
 ![](./rocketchat6.png)
 
diff --git a/website/integrations/sources/google/index.md b/website/integrations/sources/google/index.md
index ba9d69f7f..188e95ef4 100644
--- a/website/integrations/sources/google/index.md
+++ b/website/integrations/sources/google/index.md
@@ -56,7 +56,7 @@ _I'm only going to list the mandatory/important fields to complete._
 
 21. **Application Type:** Web Application
 22. **Name:** Choose a name
-23. **Authorized redirect URIs:** `https://authenik.company/source/oauth/callback/google/`
+23. **Authorized redirect URIs:** `https://authentik.company/source/oauth/callback/google/`
 
 ![](googledeveloper6.png)
 
diff --git a/website/integrations/sources/twitter/index.md b/website/integrations/sources/twitter/index.md
index 8d436c021..8adca1344 100644
--- a/website/integrations/sources/twitter/index.md
+++ b/website/integrations/sources/twitter/index.md
@@ -26,7 +26,7 @@ You will need to create a new project, and OAuth credentials in the Twitter Deve
 
 6. Enable **OAuth 2.0**
 7. Set **Type of App** to _Web_
-8. Set **Callback URI / Redirect URL** to `https://authenik.company/source/oauth/callback/twitter/`
+8. Set **Callback URI / Redirect URL** to `https://authentik.company/source/oauth/callback/twitter/`
 9. Set **Website URL** to `https://authentik.company`
 
 ![](./twitter2.png)