Updated docs

Author: oiadebayo

docs/build-your-software-catalog/sync-data-to-catalog/git/bitbucket/bitbucket-cloud/installation.md

@@ -35,16 +35,16 @@ This page details how to install Port's Bitbucket Cloud integration (powered by
 
 :::tip Use of dedicated accounts and tokens
 
-We recommend using workspace tokens from accounts dedicated to the integration, as this will provide a more secure and scalable solution.
+We recommend using multiple workspace tokens for the integration, as this will provide a more secure and scalable solution. Using multiple workspace tokens helps distribute the load and avoid rate limiting issues. You can provide multiple workspace tokens as a comma-separated string in the configuration.
 
-Different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization. Using dedicated workspace tokens helps manage rate limits more effectively.
+If you are using the username and app password, we recommend using a dedicated account for the integration, as different credentials from the same Bitbucket account share the same rate limits, which can cause issues when using the integration in a large organization.
 :::
 
 The integration requires either a workspace token or an app password with username to authenticate with your Bitbucket Cloud account.  You can create a workspace token by following the steps [here](https://support.atlassian.com/bitbucket-cloud/docs/workspace-access-tokens/) or an app password by following [these steps](https://support.atlassian.com/bitbucket-cloud/docs/app-passwords/).  
 
 The token or app password should have `read` permission scope for each of the supported resources you want to ingest into Port and a `read` and `write` permission scope for the webhooks.
 
-We recommend using workspace tokens when possible, as they provide better security and are easier to manage than app passwords.
+We recommend using multiple workspace tokens when possible, as they provide better security, are easier to manage than app passwords, and help avoid rate limiting issues by distributing requests across different tokens.
 
 ## Deploy the integration
 
@@ -180,7 +180,7 @@ This table summarizes the available parameters for the installation.
 | `integration.config.bitbucketUsername`      | The username of the Bitbucket Cloud account                                                  | ✅        |
 | `integration.config.bitbucketWorkspace`     | The workspace of the Bitbucket Cloud account             | ✅        |
 | `integration.config.bitbucketAppPassword`   | The app password of the Bitbucket Cloud account             | ✅        |
-| `integration.config.bitbucketWorkspaceToken`| The workspace token of the Bitbucket Cloud account             | ✅        |
+| `integration.config.bitbucketWorkspaceToken`| The workspace token (or comma seperated string of multiple tokens) of the Bitbucket Cloud account             | ✅        |
 | `integration.config.webhookSecret`          | The secret used to verify the webhook requests             | ❌        |
 | `scheduledResyncInterval`        | The number of minutes between each resync                                                                                           | ❌        |
 | `initializePortResources`        | Default true, When set to true the integration will create default blueprints and the port App config Mapping                       | ❌        |