fix: formatting

Author: sriramveeraghanta

docs/self-hosting/govern/environment-variables.md

@@ -11,9 +11,10 @@ This guide provides a comprehensive overview of all environment variables used i
 ## Where to find the .env file
 
 The environment file for Plane Commercial Edition is located at:
-`bash
-    /opt/plane/plane.env
-    `
+
+```bash
+/opt/plane/plane.env
+```
 
 This is where you'll make all configuration changes. Remember to restart the instance after making changes to ensure they take effect.
 
@@ -164,9 +165,10 @@ This guide provides a comprehensive overview of all environment variables availa
 ## Where to find the environment file
 
 The environment configuration file is located at:
-`bash
-    plane-selfhost/plane-app/plane.env
-    `
+
+```bash
+plane-selfhost/plane-app/plane.env
+```
 
 ## Environment Variables
 

docs/self-hosting/govern/integrations/gitlab.md

@@ -72,37 +72,37 @@ After creating and configuring the GitLab application and configuring the instan
 3. From the dropdown menu that appears, select **Edit profile**.
 4. Look for and select the **Applications** option within this menu.
 5. On the Applications page, click **Add new application** to begin configuring your OAuth application.
-  
-  Fill in the application details with the following configuration:
 
-  - **Name**
-    Enter a descriptive name for your application (e.g., `Plane Local Dev` or `Plane Integration`).
+Fill in the application details with the following configuration:
 
-  - **Redirect URI**
-    The redirect URI depends on your Plane deployment:
+- **Name**
+  Enter a descriptive name for your application (e.g., `Plane Local Dev` or `Plane Integration`).
 
-    **For Plane Cloud:**
-    
-    `https://silo.plane.so/api/oauth/gitlab-enterprise/auth/callback`
+- **Redirect URI**
+  The redirect URI depends on your Plane deployment:
 
-    **For Plane Self-Hosted:**
-    
-    `https://<your-domain>/silo/api/oauth/gitlab-enterprise/auth/callback`
+  **For Plane Cloud:**
 
-  Replace `<your-domain>` with your actual Plane instance domain.
+  `https://silo.plane.so/api/oauth/gitlab-enterprise/auth/callback`
 
-  - **Confidential**
-    Keep the **Confidential** checkbox enabled. This ensures the application uses a client secret for secure authentication.
+  **For Plane Self-Hosted:**
 
-  - **Scopes**
-    Select the following scopes to grant Plane the necessary permissions:
+  `https://<your-domain>/silo/api/oauth/gitlab-enterprise/auth/callback`
 
-  - **api** - Grants complete read/write access to the API, including all groups and projects
-  - **read_api** - Grants read access to the API, including all groups and projects
-  - **read_user** - Grants read-only access to your profile information
-  - **read_repository** - Grants read-only access to repositories on private projects
-  - **profile** - Grants read-only access to the user's profile data using OpenID Connect
-  - **email** - Grants read-only access to the user's primary email address using OpenID Connect
+Replace `<your-domain>` with your actual Plane instance domain.
+
+- **Confidential**
+  Keep the **Confidential** checkbox enabled. This ensures the application uses a client secret for secure authentication.
+
+- **Scopes**
+  Select the following scopes to grant Plane the necessary permissions:
+
+- **api** - Grants complete read/write access to the API, including all groups and projects
+- **read_api** - Grants read access to the API, including all groups and projects
+- **read_user** - Grants read-only access to your profile information
+- **read_repository** - Grants read-only access to repositories on private projects
+- **profile** - Grants read-only access to the user's profile data using OpenID Connect
+- **email** - Grants read-only access to the user's primary email address using OpenID Connect
 
 6. Click **Save application** to create the OAuth application.
 

docs/self-hosting/manage/migrate-plane.md

@@ -23,14 +23,14 @@ 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](/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.
+    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 ↓:
+    Create a backup of your Plane instance with ↓:
 
-  ```bash
-  prime-cli backup
-  ```
+```bash
+prime-cli backup
+```
 
 This command will generate a backup file in the path: `/opt/plane/backups`.
 
@@ -39,21 +39,21 @@ This command will generate a backup file in the path: `/opt/plane/backups`.
 :::
 
 3.  **Set up Plane on the new server**  
-  Follow the [installation guide](/self-hosting/methods/docker-compose#install-plane) to deploy Plane on the new instance.
+    Follow the [installation guide](/self-hosting/methods/docker-compose#install-plane) to deploy Plane on the new instance.
 
 4.  **Transfer backup files**  
-  Copy the `backups` folder from the old server, created in step 2, to the new server. Place the backup in the folder `/opt/plane`.
+    Copy the `backups` folder from the old server, created in step 2, to the new server. Place the backup in the folder `/opt/plane`.
 
 5.  **Restore data**  
-  On the new server, restore your data with ↓:
+    On the new server, restore your data with ↓:
 
-  ```bash
-  prime-cli restore
-  ```
+```bash
+prime-cli restore
+```
 
 Follow the prompts during the restore process to make sure everything is set up correctly.
 
 6.  **Reactivate license**  
-  Finally, [reactivate your license keys](/self-hosting/manage/manage-licenses/activate-pro-and-business#activate-your-license) 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.

docs/self-hosting/upgrade-from-community.md

@@ -86,27 +86,28 @@ This upgrade path is for installations using external or managed database and ob
     1. Find the `DATABASE_URL` environment variable.
     2. Verify it points to your external database:
 
-        ```ini
-        DATABASE_URL=postgresql://user:password@your-db-host:5432/plane
-        ```
-
-        If you need to change it, update the value with your managed database connection string. 
-    3. Configure object storage 
-        1. Find the `#DATASTORE SETTINGS` section in `plane.env` 
-        2. Update these environment variables for your external storage:
-
-        ```ini
-        USE_MINIO=0
-        AWS_REGION=us-east-1
-        AWS_ACCESS_KEY_ID=<your-access-key>
-        AWS_SECRET_ACCESS_KEY=<your-secret-key>
-        AWS_S3_ENDPOINT_URL=https://s3.amazonaws.com
-        AWS_S3_BUCKET_NAME=plane-uploads
-        ```
-
-        :::info
-        Setting `USE_MINIO=0` disables the local MinIO service and enables external object storage (S3 or S3-compatible services).
-        :::
+       ```ini
+       DATABASE_URL=postgresql://user:password@your-db-host:5432/plane
+       ```
+
+       If you need to change it, update the value with your managed database connection string.
+
+    3. Configure object storage
+       1. Find the `#DATASTORE SETTINGS` section in `plane.env`
+       2. Update these environment variables for your external storage:
+
+       ```ini
+       USE_MINIO=0
+       AWS_REGION=us-east-1
+       AWS_ACCESS_KEY_ID=<your-access-key>
+       AWS_SECRET_ACCESS_KEY=<your-secret-key>
+       AWS_S3_ENDPOINT_URL=https://s3.amazonaws.com
+       AWS_S3_BUCKET_NAME=plane-uploads
+       ```
+
+       :::info
+       Setting `USE_MINIO=0` disables the local MinIO service and enables external object storage (S3 or S3-compatible services).
+       :::
 
 3.  Restart Plane services to apply the configuration:
     ```bash