diff --git a/src/components/announcement-banner/AnnouncementBannerProvider.jsx b/src/components/announcement-banner/AnnouncementBannerProvider.jsx
index 9233eebf..94a860cf 100644
--- a/src/components/announcement-banner/AnnouncementBannerProvider.jsx
+++ b/src/components/announcement-banner/AnnouncementBannerProvider.jsx
@@ -13,8 +13,8 @@ const BANNER_ENABLED = true
 
 export const announcement = {
   tag: 'New',
-  text: 'Embedded Identity Provider with DEX for Self-Hosted Installations',
-  link: '/selfhosted/identity-providers#local-user-management',
+  text: 'Simplified IdP Integration',
+  link: '/selfhosted/identity-providers',
   linkText: 'Learn More',
   linkAlt: 'Learn more about the embedded Identity Provider powered by DEX for self-hosted installations',
   isExternal: false,
diff --git a/src/pages/selfhosted/identity-providers/index.mdx b/src/pages/selfhosted/identity-providers/index.mdx
index d90b5fad..17f3a7af 100644
--- a/src/pages/selfhosted/identity-providers/index.mdx
+++ b/src/pages/selfhosted/identity-providers/index.mdx
@@ -20,7 +20,7 @@ verify the user's identity and grant access.
 By default, NetBird does not require an external identity provider. New installations include a built-in authentication
 system that lets you create and manage users directly through the Dashboard using local username and password authentication.
 External identity providers are entirely optional. Add them when you need SSO integration with Google, Microsoft, Okta, or
-self-hosted identity providers like Keycloak or Authentik.
+self-hosted identity providers like Keycloak or Authentik, and more.
 
 ## Local User Management
 
@@ -30,7 +30,7 @@ authentication.
 ## External Identity Providers
 
 NetBird supports connecting **multiple external identity providers** [alongside local user management](/selfhosted/identity-providers/local).
-This allows users to sign in with their existing accounts from services like Google, Microsoft, or your corporate identity
+This allows users to sign in with their existing accounts from services like Google, Microsoft and your corporate or self-hosted identity
 provider, while still maintaining the option for local username/password authentication.
 
 NetBird supports any OIDC-compliant identity providers. Here are some popular providers and their setup instructions:
@@ -44,7 +44,7 @@ NetBird supports any OIDC-compliant identity providers. Here are some popular pr
 | [**Zitadel**](/selfhosted/identity-providers/zitadel) | `zitadel` | Open-source IAM with multi-tenancy and passwordless auth |
 | [**Keycloak**](/selfhosted/identity-providers/keycloak) | `keycloak` |  Popular open source IAM with extensive enterprise features |
 | [**Authentik**](/selfhosted/identity-providers/authentik) | `authentik` | Flexible open source IdP with SSO, MFA, and policy engine |
-| [**PocketID**](/selfhosted/identity-providers/pocketid) | `pocketid` | Lightweight OIDC provider with passkey authentication |
+| [**Pocket ID**](/selfhosted/identity-providers/pocketid) | `pocketid` | Lightweight OIDC provider with passkey authentication |
 
 <Note>
     Any identity provider that supports OpenID Connect can be integrated with NetBird. If your provider isn't listed above,
@@ -171,7 +171,7 @@ This allows you to support different authentication methods for different user g
 
 - Check Management service logs for errors
 - Verify the token contains required claims (email, name)
-- Ensure the user's email domain is not blocked by any policies
+- Ensure the user's email domain is not blocked by any policies in your IdP. Some providers like Pocket ID block all users by default unless you unrestrict groups in the OIDC client configuration.
 
 #### External connector not working
 
diff --git a/src/pages/selfhosted/selfhosted-quickstart.mdx b/src/pages/selfhosted/selfhosted-quickstart.mdx
index 801388b9..b92478b3 100644
--- a/src/pages/selfhosted/selfhosted-quickstart.mdx
+++ b/src/pages/selfhosted/selfhosted-quickstart.mdx
@@ -160,17 +160,6 @@ To upgrade NetBird to the latest version:
 For upgrades from older versions (pre-v0.26.0), see the [Legacy upgrade notes](#legacy-self-hosting-with-zitadel-idp).
 </Note>
 
-### Support browser clients
-If you deployed NetBird before version **0.59.0** and want to use browser clients, you need to update your Signal, Management, Dashboard and Relay services, see [Upgrade](#upgrade), then you need to edit the `Caddyfile` file to enable support for browser clients by adding the following lines to the `Caddyfile`:
-```
-    reverse_proxy /ws-proxy/management* management:80
-    reverse_proxy /ws-proxy/signal* signal:80
-```
-Then restart the Caddy service to apply the changes:
-```bash
-docker compose restart caddy
-```
-
 ### Remove
 To remove the NetBird installation and all related data from your server, run these commands from the folder where you installed NetBird:
 ```bash
@@ -264,7 +253,7 @@ See the [Migration Guide](/selfhosted/identity-providers#migration-guide) for de
 ### Upgrade (Legacy)
 
 <Note>
-If upgrading from management version < [v0.15.3](https://github.com/netbirdio/netbird/releases/tag/v0.15.3), 
+If upgrading from management version < [v0.15.3](https://github.com/netbirdio/netbird/releases/tag/v0.15.3),
 first upgrade to [v0.25.9](https://github.com/netbirdio/netbird/releases/tag/v0.25.9), 
 run management to migrate rules to policies, then upgrade to **0.26.0+**.
 </Note>