fix the bullet list not showing up correctly

docs/bitbucket-installation.md

@@ -26,14 +26,14 @@ description: Install gitStream to your Bitbucket workspace.
 
     1. **Webhook Event Handling by gitStream**
        When Bitbucket triggers a webhook event (e.g., a pull request opened), gitStream may need to make follow-up API calls to Bitbucket. This can include fetching additional metadata, posting comments to the PR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your Bitbucket allowlist to ensure proper operation.
-
     2. **Outbound Requests from Your CI Runner**
        When your pipeline runs gitStream, that runner might also make outbound calls to Bitbucket—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address.
 
     If you encounter errors due to blocked IPs during your CI runs, it's likely that the runner is using an IP that is not part of the configured allowlist.
 
     **Recommended Solution**
     To ensure reliability:
+
     - Add LinearB/gitStream service IPs to your Bitbucket allowlist (listed above).
     - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly.
 

docs/github-installation.md

@@ -17,14 +17,14 @@ description: Install gitStream to your GitHub organization.
 
     1. **Webhook Event Handling by gitStream**
        When GitHub triggers a webhook event (e.g., a pull request opened), gitStream may need to make follow-up API calls to GitHub. This can include fetching additional metadata, posting comments to the PR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your GitHub allowlist to ensure proper operation.
-
     2. **Outbound Requests from Your CI Runner**
        When your pipeline runs gitStream (e.g., via a GitHub Action), that runner might also make outbound calls to GitHub—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address.
 
     If you encounter errors due to blocked IPs during your CI runs, it's likely that the runner is using an IP that is not part of the configured allowlist. This is a common issue with GitHub-hosted runners, as their IPs can be dynamic and change frequently.
 
     **Recommended Solution**
     To ensure reliability:
+
     - Add LinearB/gitStream service IPs to your GitHub allowlist (listed above).
     - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly.
 

docs/gitlab-installation.md

@@ -20,14 +20,14 @@ description: Install gitStream to your GitLab organization.
 
     1. **Webhook Event Handling by gitStream**
        When GitLab triggers a webhook event (e.g., a merge request opened), gitStream may need to make follow-up API calls to GitLab. This can include fetching additional metadata, posting comments to the MR, or performing other actions. These calls are made from the LinearB/gitStream service, which uses a fixed set of IP addresses. These IPs must be added to your GitLab allowlist to ensure proper operation.
-
     2. **Outbound Requests from Your CI Runner**
        When your pipeline runs gitStream, that runner might also make outbound calls to GitLab—for example, to clone a repository or retrieve commit history. These requests will originate from the runner's IP address.
 
     If you encounter errors due to blocked IPs during your CI runs, it's likely that the runner is using an IP that is not part of the configured allowlist.
 
     **Recommended Solution**
     To ensure reliability:
+
     - Add LinearB/gitStream service IPs to your GitLab allowlist (listed above).
     - Use self-hosted runners or runners with static IPs so you can manage and allowlist their addresses explicitly.