diff --git a/website/docs/integrations/services/proxmox-ve/index.md b/website/docs/integrations/services/proxmox-ve/index.md
index f0615b874..d3bf50281 100644
--- a/website/docs/integrations/services/proxmox-ve/index.md
+++ b/website/docs/integrations/services/proxmox-ve/index.md
@@ -47,10 +47,10 @@ Another way is to use the CLI. SSH into any Proxmox cluster node, and issue the
 
 `pveum realm add authentik --type openid --issuer-url https://authentik.company/application/o/proxmox/ --client-id xxx --client-key xxx --username-claim username --autocreate 1`
 
-You can find the Issuer URL on the Provider Metadata tab in Authentik. You can find the Client ID and Key on the Provider Edit dialog in Authentik.
+You can find the Issuer URL on the Provider Metadata tab in authentik. You can find the Client ID and Key on the Provider Edit dialog in authentik.
 
 After configuring the source in Proxmox, any user that logs in to Proxmox for the first time automatically gets an user named `<authentik username>@<pve realm name>`. In this example,
-Authentik user `bob` will get an user named `bob@authentik` in Proxmox. You can then assign Permissions as normally in Proxmox. You can also pre-create the users in Proxmox if you want
+authentik user `bob` will get an user named `bob@authentik` in Proxmox. You can then assign Permissions as normally in Proxmox. You can also pre-create the users in Proxmox if you want
 the user to be able to perform actions immediately after first login.
 
 There is no way to directly trigger an OpenID Connect login in Proxmox, but if you set the source as 'default', it will be automatically selected on the Proxmox login screen.
diff --git a/website/docs/user-group/user.md b/website/docs/user-group/user.md
index 8c347b706..82f77b936 100644
--- a/website/docs/user-group/user.md
+++ b/website/docs/user-group/user.md
@@ -26,7 +26,7 @@ See [Troubleshooting access problems](../troubleshooting/access.md), when set, t
 This field is only used by the Proxy Provider.
 :::
 
-Some applications can be configured to create new users using header information forwarded from Authentik. You can forward additional header information by adding each header
+Some applications can be configured to create new users using header information forwarded from authentik. You can forward additional header information by adding each header
 underneath `additionalHeaders`:
 
 #### Example:
@@ -38,7 +38,7 @@ additionalHeaders:
   REMOTE-NAME: Joseph
 ```
 
-These headers will now be passed to the application when the user logs in. Most applications will need to be configured to accept these headers. Some examples of applications that can accept additional headers from an Authentik Proxy Provider are [Grafana](https://grafana.com/docs/grafana/latest/auth/auth-proxy/) and [Tandoor Recipes](https://docs.tandoor.dev/features/authentication/).
+These headers will now be passed to the application when the user logs in. Most applications will need to be configured to accept these headers. Some examples of applications that can accept additional headers from an authentik Proxy Provider are [Grafana](https://grafana.com/docs/grafana/latest/auth/auth-proxy/) and [Tandoor Recipes](https://docs.tandoor.dev/features/authentication/).
 
 ## Object attributes