Updated references and fixed sentry images

Author: danciaclara

self-hosting/govern/integrations/sentry.mdx

@@ -43,8 +43,6 @@ A custom integration (also called a public integration) connects your Sentry org
     Replace `[YOUR_DOMAIN]` with your actual Plane instance domain. For example, if your Plane instance is at `plane.company.com`, your Webhook URL would be `https://plane.company.com/silo/api/sentry/sentry-webhook/`
     </Note>
 
-    ![Public integration](/images/sentry/public-integration.webp)
-
 **Field explanations:**
 
 **Webhook URL**  
@@ -238,8 +236,6 @@ Configure these permissions to allow Sentry to interact with Plane appropriately
 | **Member** | Read | Access member details for assignee functionality |
 | **Alerts** | Read | Enable alert rule actions for automatic issue creation |
 
-![Sentry integration permissions](/images/sentry/sentry-permissions.webp)
-
 ### Enable webhooks
 
 Webhooks keep Plane and Sentry synchronized. When issues change in Sentry, Plane receives notifications and updates accordingly.
@@ -254,8 +250,6 @@ Enable the **issue** webhook with these events:
 | **archived** | Reflect archived status in Plane |
 | **unresolved** | Update Plane when resolved issues reopen |
 
-![Sentry webhook configuration](/images/sentry/sentry-webhook-config.webp)
-
 ### Save and retrieve credentials
 
 After saving your integration, Sentry generates OAuth credentials:

self-hosting/govern/ldap.mdx

@@ -127,41 +127,6 @@ You'll need:
 7. Users will see **Sign in with LDAP** on Plane's login page and can use their directory credentials to sign in.
     ![Sign in using LDAP](/images/ldap/sign-in-ldap.webp)
 
-## Configuration examples
-
-### Active Directory
-```
-Server URI:          ldaps://ad.company.com:636
-Bind DN:             cn=PlaneService,ou=Service Accounts,dc=company,dc=com
-Bind Password:       ********
-User Search Base:    ou=Employees,dc=company,dc=com
-User Search Filter:  (sAMAccountName={username})
-User Attributes:     mail,cn,givenName,sn,userPrincipalName
-Provider Name:       Company Directory
-```
-
-### OpenLDAP
-```
-Server URI:          ldap://ldap.example.com:389
-Bind DN:             cn=readonly,dc=example,dc=com
-Bind Password:       ********
-User Search Base:    ou=users,dc=example,dc=com
-User Search Filter:  (uid={username})
-User Attributes:     mail,cn,givenName,sn
-Provider Name:       LDAP
-```
-
-### FreeIPA
-```
-Server URI:          ldaps://ipa.example.com:636
-Bind DN:             uid=plane-svc,cn=users,cn=accounts,dc=example,dc=com
-Bind Password:       ********
-User Search Base:    cn=users,cn=accounts,dc=example,dc=com
-User Search Filter:  (uid={username})
-User Attributes:     mail,cn,givenName,sn
-Provider Name:       FreeIPA
-```
-
 ## How LDAP authentication works
 
 LDAP authentication in Plane works through a two-phase process. First, Plane locates the user in your directory, then it verifies their credentials. This separation is fundamental to how LDAP works and explains why you need both a service account (Bind DN) and the user's own credentials.

self-hosting/manage/manage-licenses/activate-enterprise.mdx

@@ -5,18 +5,15 @@ sidebarTitle: Activate Enterprise
 
 Enterprise plan licenses are activated at the instance level through God Mode, not through individual workspace settings. This gives instance administrators centralized control over Enterprise features across all workspaces.
 
-## Get your license key
+## Activate license key
 
 1. Sign in to the [Prime portal](https://prime.plane.so/licenses) with the email address you used to purchase your Enterprise plan.
 2. Navigate to **Manage licenses**.
 3. Copy the license key for your Enterprise plan.
-
-### Activate in God Mode
-
-1. Sign in to your Plane instance in [God Mode](/self-hosting/govern/instance-admin).
-2. Select **Billing** from the left pane.
-3. Paste your license key in the **Activate Enterprise license** field.
-6. Click **Activate**.
+4. Sign in to your Plane instance in [God Mode](/self-hosting/govern/instance-admin).
+5. Select **Billing** from the left pane.
+6. Paste your license key in the **Activate Enterprise license** field.
+7. Click **Activate**.
 
    ![Activate Enterprise license](/images/activate-license/activate-enterprise-plan.webp)
 

self-hosting/manage/migrate-plane.mdx

@@ -18,7 +18,7 @@ If you need to change your domain during migration, contact our support team for
 
 ## Steps
 1. **Delink licenses**  
-Log in to Plane on your current server. Head to each paid workspace like Pro or Business and [delink the licenses](https://docs.plane.so/workspaces-and-users/upgrade-plan#delink-license-key). This will free up the licenses for activation on your new server. Ideally, you have just one paid workspace.
+Log in to Plane on your current server. Head to each paid workspace like Pro or Business and [delink the licenses](/self-hosting/manage/manage-licenses/activate-pro-and-business#delink-license-key). This will free up the licenses for activation on your new server. Ideally, you have just one paid workspace.
 
 2. **Backup data**  
 Create a backup of your Plane instance with ↓:
@@ -45,6 +45,6 @@ On the new server, restore your data with ↓:
     Follow the prompts during the restore process to make sure everything is set up correctly.
 
 6. **Reactivate license**  
-Finally, [reactivate your license keys](https://docs.plane.so/workspaces-and-users/upgrade-plan#self-hosted-only) on the new instance.
+Finally, [reactivate your license keys](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) on the new instance.
 
 This should get your Plane instance up and running on the new server.

self-hosting/methods/coolify.mdx

@@ -45,4 +45,4 @@ This guide shows you the steps to deploy a self-hosted instance of Plane using C
 8. Deploy to launch your Plane instance.
     Once the deployment is complete, your Plane instance should be accessible on the configured domain.
 
-9. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+9. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.

self-hosting/methods/docker-aio.mdx

@@ -96,7 +96,7 @@ The following ports are exposed:
 
 3. Once it's running, you can access the Plane application on the domain you provided during the deployment.
 
-4. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+4. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.
 
 ## Volume mounts
 

self-hosting/methods/docker-compose.mdx

@@ -40,7 +40,7 @@ Ensure you're using the **latest version of Docker Compose**. Check your Docker
       When self-hosting Plane for production use, it is strongly recommended to configure [external database and storage](/self-hosting/govern/database-and-storage). This ensures that your data remains secure and accessible even if the local machine crashes or encounters hardware issues. Relying solely on local storage for these components increases the risk of data loss and service disruption.
       </Warning>
    6. The installation will take a few minutes to complete and you will see the message **Plane has successfully installed**. You can access the Plane application on the domain you provided during the installation. 
-   7. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+   7. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.
 
 
 <Accordion title="Install Community Edition ">

self-hosting/methods/docker-swarm.mdx

@@ -58,4 +58,4 @@ This guide shows you the steps to deploy a self-hosted instance of the Plane Com
 
     That's it! This will deploy Plane as a Swarm stack, and your instance should be accessible on your configured domain.
 
-5. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+5. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.

self-hosting/methods/kubernetes.mdx

@@ -103,7 +103,7 @@ Ensure you use use the latest Helm chart version.
                     --wait \
                     --wait-for-jobs 
             ```
-    5. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+    5. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.
 
 ### Configuration settings
 

self-hosting/methods/podman-quadlets.mdx

@@ -97,7 +97,7 @@ Note that you should run these commands without `sudo`.
 
     The startup sequence is important: network first, then dependencies, followed by backend services, and finally frontend services.
 
-6. If you've purchased a paid plan, [activate your license key](https://docs.plane.so/workspaces-and-users/manage-licenses#activate-license) to unlock premium features.
+6. If you've purchased a paid plan, [activate your license key](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) to unlock premium features.
 
 ### Verify service status
 Check that all services are running correctly: