docs: fix 55 defects found by proofread + source revalidation

docs/ai/agent-skills/sdk/cordova/SKILL.md

@@ -83,7 +83,7 @@ document.addEventListener('deviceready', function() {
 
 > Replace the tokens with values from your Bugsee dashboard.
 
-> iOS/iPadOS: Since v7.0.0 the Bugsee iOS SDK supports the simulator; crash capture is excluded. For full functionality, use a real device.
+> iOS/iPadOS: Since v6.0.0 the Bugsee iOS SDK supports the simulator; crash capture is excluded. For full functionality, use a real device.
 
 ---
 

docs/ai/agent-skills/sdk/kmp/SKILL.md

@@ -79,7 +79,7 @@ kotlin {
 
     sourceSets {
         commonMain.dependencies {
-            implementation("com.bugsee:bugsee-kotlin-multiplatform:+")
+            implementation("com.bugsee:bugsee-kotlin-multiplatform:0.1.1")
         }
     }
 }

docs/ai/plugins/claude-code.md

@@ -18,7 +18,7 @@ Add the Bugsee marketplace, then install the plugin:
 /plugin install bugsee@bugsee-plugin-marketplace
 ```
 
-That's it — Claude Code now has the Bugsee SDK-setup and workflow skills, and the read-only Bugsee MCP server (`https://api.bugsee.com/mcp`) is configured.
+That's it — Claude Code now has the Bugsee SDK-setup and workflow skills, and the Bugsee MCP server (`https://api.bugsee.com/mcp`) is configured with the read-only `mcp:read` scope.
 
 ## Connect the MCP server
 
@@ -37,6 +37,6 @@ Ask Claude Code in natural language:
 
 - **SDK setup skills** for every supported platform.
 - **Workflow skills**: `bugsee-fix-issues` (triage and root-cause crashes, errors, and bug reports through the MCP server), `bugsee-build-insights` (build size, regressions, and dependency vulnerabilities through the MCP server), and `bugsee-upload-symbols` (dSYMs, JavaScript source maps, Android mapping files).
-- **MCP server** access to your Bugsee applications and issues (read-only).
+- **MCP server** access to your Bugsee applications and issues (read-only by default — the `mcp:read` scope).
 
 See [Plugins](/ai/plugins) for the full list, or browse the source at [github.com/bugsee/bugsee-for-ai](https://github.com/bugsee/bugsee-for-ai).

docs/ai/plugins/codex.md

@@ -23,7 +23,7 @@ Repeat for any platform you need, or point Codex at the [bugsee-for-ai](https://
 
 ## Connect the MCP server
 
-Add the read-only Bugsee MCP server to your Codex configuration (`~/.codex/config.toml`) so the assistant can read your issues. Use the OAuth URL `https://api.bugsee.com/mcp`, or the personal-token URL `https://api.bugsee.com/mcp/<token>` for unattended setups. See [MCP configuration](/mcp/configuration) for how to generate a token and the security model.
+Add the Bugsee MCP server to your Codex configuration (`~/.codex/config.toml`) so the assistant can read your issues. Use the OAuth URL `https://api.bugsee.com/mcp`, or the personal-token URL `https://api.bugsee.com/mcp/<token>` for unattended setups. See [MCP configuration](/mcp/configuration) for how to generate a token and the security model.
 
 ## Use it
 

docs/ai/plugins/other-agents.md

@@ -25,7 +25,7 @@ curl -o .claude/skills/bugsee-android-sdk/SKILL.md \
 
 ## Any MCP-capable client
 
-Connect the read-only Bugsee MCP server (`https://api.bugsee.com/mcp`) to read your applications and issues. [MCP configuration](/mcp/configuration) has per-client setup for Claude Desktop, Cursor, Windsurf, VS Code, Cline, Zencoder, and Antigravity, plus the OAuth and personal-token flows for anything else.
+Connect the Bugsee MCP server (`https://api.bugsee.com/mcp`) to read your applications and issues; the default `mcp:read` scope is read-only. [MCP configuration](/mcp/configuration) has per-client setup for Claude Desktop, Cursor, Windsurf, VS Code, Cline, Zencoder, and Antigravity, plus the OAuth and personal-token flows for anything else.
 
 ## What you get
 

docs/dashboard/accounts/2fa.md

@@ -28,8 +28,8 @@ Now, when you have configured your authentication application, it's time to chec
 
 ![](2fa-step-4.png)
 
-If you have properly configured your authentication application and verification was passed successfully, 2FA will be enabled for your account and you will be provided with backup codes. Please, store them somewhere to later obtain access to your account if you will not be able to access your authentication application anymore.
+If you have properly configured your authentication application and verification was passed successfully, 2FA will be enabled for your account and you will be provided with backup codes. Please store them somewhere to later obtain access to your account if you will not be able to access your authentication application anymore.
 
 ![](2fa-step-5.png)
 
-Finally, click _"Complete"_ to close the wizard. Two-Factor authentication is now activated for your account.
+Finally, click _"Complete"_ to close the wizard. Two-factor authentication is now activated for your account.

docs/dashboard/accounts/sso/index.md

@@ -11,8 +11,8 @@ Bugsee provides a generic auth provider for SAML2 based authentication, which al
 
 Bugsee supports the following SAML services:
 
-Identity and Service Provider initiated SSO
-Identity Provider initiated SLO (Single Logout)
+- Identity and Service Provider initiated SSO
+- Identity Provider initiated SLO (Single Logout)
 
 ### 1. Register Bugsee with IdP
 

docs/dashboard/accounts/sso/instructions/config-gsuite.md

@@ -27,11 +27,11 @@ On the next step, fill the _"Application name"_, _"Description"_ and _"Logo"_.
 
 ![](gsuite-step-5.png)
 
-Now, on _"Service Provider Details"_ step, you need to fill information available in _"SSO setup"_ wizard in Bugsee. Please, follow the instructions shown in the screenshot below.
+Now, on _"Service Provider Details"_ step, you need to fill information available in _"SSO setup"_ wizard in Bugsee. Please follow the instructions shown in the screenshot below.
 
 ![](gsuite-step-6.png)
 
-Finally, on the _"Attribute Mapping"_ step, you need to list attributes that will be available to Bugsee (as Service Provider). Please, follow the instructions shown in the screenshot below. Copy the attribute names. You must provide the same names in the Bugsee SSO setup wizard dialog when prompted.
+Finally, on the _"Attribute Mapping"_ step, you need to list attributes that will be available to Bugsee (as Service Provider). Please follow the instructions shown in the screenshot below. Copy the attribute names. You must provide the same names in the Bugsee SSO setup wizard dialog when prompted.
 
 :::info
 Note that Bugsee is using single field to store user name, while Google Workspace does not provide similar one by default. In this tutorial, we use "Last name" as the target value for the "name" attribute.

docs/integrations/index.md

@@ -19,12 +19,12 @@ If you don't find your tool among the available integrations, please contact <a
 * [Asana](providers/asana/)
 * [Azure DevOps](providers/azure-devops/)
 * [Basecamp](providers/basecamp/)
-* [BitBucket](providers/bitbucket/)
+* [Bitbucket](providers/bitbucket/)
 * [BugHerd](providers/bugherd/)
 * [Bugzilla](providers/bugzilla/)
 * [ClickUp](providers/clickup/)
-* [Github](providers/github/)
-* [Gitlab](providers/gitlab/)
+* [GitHub](providers/github/)
+* [GitLab](providers/gitlab/)
 * [Hubspot](providers/hubspot/)
 * [Jira](providers/jira/)
 * [Linear](providers/linear/)

docs/integrations/providers/bitbucket/index.md

@@ -5,12 +5,18 @@ sidebar_position: 3
 slug: "/integrations/providers/bitbucket"
 ---
 
+:::warning[This integration is retired]
+Bitbucket Cloud removed its native issue tracker and the Issues REST APIs on **20 August 2026**. Bugsee can no longer create or update Bitbucket issues, and attempting to push to an existing Bitbucket integration returns an error.
+
+Existing configurations are left in place so historical links keep resolving, but no new issues will be delivered. Migrate issue tracking to [Jira](/integrations/providers/jira/) or another supported provider.
+:::
+
 To push issues from Bugsee to Bitbucket you must have properly configured issue trackers in all target repositories. Follow the steps below to validate your configuration.
 
 
 ## Prepare
 
-Navigate to your [Bitbucket account](https://www.bitbucket.com) and open the repository you want to check.
+Navigate to your [Bitbucket account](https://bitbucket.org) and open the repository you want to check.
 
 ![Open repo](open_repo.png)
 

docs/integrations/providers/clickup/index.md

@@ -50,7 +50,7 @@ You will be presented with the following window asking you to select workspaces
 We describe here only specific configuration steps for ClickUp. Generic steps are described in [configuration](/integrations/configuration/) section. Refer to it for more details.
 :::
 
-ClickUp has the following structure: _"Team"_ -> _"Space"_ -> _"Folder"_ -> _"List"_ -> _"Task"_. So, we provide one more step in integration setup wizard that asks you to pick the _"Team"_ and _"Space"_ pair to fetch folders and lists from. Please, pick one and click _"Next"_ to proceed.
+ClickUp has the following structure: _"Team"_ -> _"Space"_ -> _"Folder"_ -> _"List"_ -> _"Task"_. So, we provide one more step in integration setup wizard that asks you to pick the _"Team"_ and _"Space"_ pair to fetch folders and lists from. Please pick one and click _"Next"_ to proceed.
 
 ![Choose workspace](workspace.png)
 
@@ -70,8 +70,9 @@ function create(context) {
     return {
     	// ...
     	custom: {
-    		// for some tasks this is 'open', for some others it's 'open'
-    		status: 'open'
+    		// Bugsee maps its own 'open' state to ClickUp's 'to do' by default;
+    		// your space or list may use 'open', 'backlog' or a custom name instead.
+    		status: 'to do'
     	}
     };
 }

docs/integrations/providers/github/index.md

@@ -68,11 +68,11 @@ For custom fields you can use in [custom recipes](/integrations/recipes/recipes/
 
 ## Custom recipes
 
-Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with Github. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
+Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with GitHub. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
 
 ### Setting labels field
 
-By default Bugsee creates and updates Github issues with Bugsee issue _labels_. But _labels_ list can be overridden inside your custom recipe. For example you can add some new _label_ to existing ones:
+By default Bugsee creates and updates GitHub issues with Bugsee issue _labels_. But _labels_ list can be overridden inside your custom recipe. For example you can add some new _label_ to existing ones:
 
 ```javascript
 function create(context) {

docs/integrations/providers/gitlab/index.md

@@ -60,11 +60,11 @@ There are no specific configuration steps for GitLab. Refer to <a href="/integra
 
 ## Custom recipes
 
-Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with Gitlab. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
+Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with GitLab. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
 
 ### Setting labels field
 
-By default Bugsee creates and updates Gitlab issues with Bugsee issue _labels_. But _labels_ list can be overridden inside your custom recipe. For example you can add some new _label_ to existing ones:
+By default Bugsee creates and updates GitLab issues with Bugsee issue _labels_. But _labels_ list can be overridden inside your custom recipe. For example you can add some new _label_ to existing ones:
 
 ```javascript
 function create(context) {

docs/integrations/providers/itop/index.md

@@ -13,7 +13,7 @@ slug: "/integrations/providers/itop"
 - [Personal token](#personal-token)
 
 
-## Basic authentication
+### Basic authentication
 
 :::info
 No custom configuration required in iTop for this type of authentication. The iTop user account you use must have sufficient permissions to create tickets via the REST API.

docs/integrations/providers/jira/index.md

@@ -1,5 +1,5 @@
 ---
-title: "JIRA integration"
+title: "Jira integration"
 description: "Connect Bugsee to Jira using a personal token or OAuth, with extensive custom recipe examples for labels, components, priorities, and custom fields."
 sidebar_position: 14
 slug: "/integrations/providers/jira"
@@ -31,9 +31,9 @@ Your API token is now generated. Store it somewhere as it will not visible to yo
 
 ![Copy token](wz_step4_token.png)
 
-Now, as we have obtained the API token, it's time to setup JIRA integration in Bugsee.
+Now, as we have obtained the API token, it's time to setup Jira integration in Bugsee.
 
-Bring up the JIRA integration wizard. Select _"Personal token"_ in the first step of integration wizard. Click _"Next"_.
+Bring up the Jira integration wizard. Select _"Personal token"_ in the first step of integration wizard. Click _"Next"_.
 
 ![Select personal token authentication](wz_step5_token.png)
 
@@ -44,7 +44,7 @@ Provide username and personal token obtained in steps above.
 
 ### OAuth 
 
-Before we can start configuring integration in Bugsee, your JIRA instance need to be tuned a bit.
+Before we can start configuring integration in Bugsee, your Jira instance need to be tuned a bit.
 
 Click the _"Cog"_ icon to bring up the settings pane:
 
@@ -74,7 +74,7 @@ Click _"Continue"_:
 
 ![Configure application URL](app_link_url_2.png)
 
-Ignore the warning and click "Continue". JIRA will bring you next dialog:
+Ignore the warning and click "Continue". Jira will bring you next dialog:
 
 ![Link applications](app_link_name_2.png)
 
@@ -95,17 +95,17 @@ VLy6zImCFbJfPz1qbwIDAQAB
 -----END PUBLIC KEY-----
 ```
 
-Now, when you've prepared your JIRA instance, let's configure integration in Bugsee.
+Now, when you've prepared your Jira instance, let's configure integration in Bugsee.
 
 Start Bugsee integration wizard and select "OAuth" in the first step of integration wizard. Click _Next_.
 
 ![Select OAuth](wz_step1_oauth.png)
 
-Skip instructional steps. Provide valid URL to your JIRA (if you're using JIRA Cloud, then it will be ```https://<domain>.atlassian.net```) and click _"Next"_.
+Skip instructional steps. Provide valid URL to your Jira (if you're using Jira Cloud, then it will be ```https://<domain>.atlassian.net```) and click _"Next"_.
 
 ![Select OAuth](wz_step2_oauth.png)
 
-You will be presented with dialog asking you to grant Bugsee permissions. Click _Allow_ to allow Bugsee access your JIRA.
+You will be presented with dialog asking you to grant Bugsee permissions. Click _Allow_ to allow Bugsee access your Jira.
 
 ![OAuth Grant](oauth_grant.png)
 
@@ -120,12 +120,12 @@ Paste the code you copied in previous step. Click _"Next"_.
 
 ## Configuration
 
-There are no specific configuration steps for JIRA. Refer to <a href="/integrations/configuration/">configuration</a> section for description about generic steps.
+There are no specific configuration steps for Jira. Refer to <a href="/integrations/configuration/">configuration</a> section for description about generic steps.
 
 
 ## Custom recipes
 
-JIRA is very customizable, fields can be made mandatory, new fields can be added, issue types, priorities and other default types can be changed. Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with JIRA. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
+Jira is very customizable, fields can be made mandatory, new fields can be added, issue types, priorities and other default types can be changed. Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with Jira. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
 
 Some fields in sent to Jira, require specifying _accountId_ field. You can find it by navigating to your Jira's _People_ section: ```https://<your-sub-domain>.atlassian.net/people```. From there, select the user you want to get accountId for and URL in browser will change to something like: ```https://<your-sub-domain>.atlassian.net/people/123456:44448ae7-90ce-4e62-bfda-e88abcde5555```. The last segment of URL, after "people/" is accountId, which in this particular case is ```123456:44448ae7-90ce-4e62-bfda-e88abcde5555```.
 
@@ -278,15 +278,15 @@ function create(context) {
     return {
     	// ...
     	custom: {
-    		// We use default JIRA versions field, which is an array of available version in JIRA.
-    		// Important: This assumes the version with that name is already created in JIRA prior to first issue
+    		// We use default Jira versions field, which is an array of available version in Jira.
+    		// Important: This assumes the version with that name is already created in Jira prior to first issue
     		// being reported, otherwise integration will break.
             versions : [ 
                 {
                     name : app.version
                 }
             ],
-            // To store the build number, we have a custom field created in JIRA, so lets store it there
+            // To store the build number, we have a custom field created in Jira, so lets store it there
             customfield_10308 : app.build
     	}
     };

docs/integrations/providers/notion/index.md

@@ -11,7 +11,7 @@ Bugsee requires the "Projects and tasks" template to be present in the workspace
 
 During the authentication process you will be asked to grant Bugsee the access to your workspace in Notion. Make sure you select both "Projects" and "Tasks" databases.
 
-Once authenticated, you will need to add the "Description" field to the task template. You can do that by creating the dummy task, opening it and clicking on "Add a property" button below the task fields (not, that this button may be collapsed under the "# more property" toggle).
+Once authenticated, you will need to add the "Description" field to the task template. You can do that by creating the dummy task, opening it and clicking on "Add a property" button below the task fields (note that this button may be collapsed under the "# more property" toggle).
 
 ![Add description field](add_description_field.png)
 

docs/integrations/providers/pivotal/index.md

@@ -5,6 +5,12 @@ sidebar_position: 21
 slug: "/integrations/providers/pivotal"
 ---
 
+:::warning[This integration is retired]
+Pivotal Tracker was discontinued on **30 April 2025**. Bugsee can no longer create or update stories, and attempting to push to an existing Pivotal Tracker integration returns an error.
+
+Existing configurations are left in place so historical links keep resolving, but no new stories will be delivered. Migrate to another supported provider from the [integrations list](/integrations/).
+:::
+
 ## Authentication
 
 ### Supported authentication methods

docs/integrations/providers/redmine/index.md

@@ -15,7 +15,7 @@ To let Bugsee integrate with your Redmine, you should enable REST API access. En
 - [Personal token](#personal-token)
 
 
-## Basic authentication
+### Basic authentication
 
 :::info
 No custom configuration required in Redmine for this type of authentication.

docs/integrations/providers/splunk/index.md

@@ -124,8 +124,6 @@ In case, if you want to push data to some other _"index"_ and/or change the _"so
 ```
 
 
-## Custom recipes
-
 Bugsee can accommodate all these customizations with the help of [custom recipes](/integrations/recipes/recipes/). This section provides a few examples of using custom recipes specifically with Splunk. For basic introduction, refer to custom recipe [documentation](/integrations/recipes/recipes/).
 
 ### Setting labels field

docs/integrations/providers/wrike/index.md

@@ -13,7 +13,7 @@ slug: "/integrations/providers/wrike"
 
 ### OAuth
 
-Start Bugsee integration wizard and select  "OAuth" at the first step. Click _"Next"_.
+Start Bugsee integration wizard and select "OAuth" at the first step. Click _"Next"_.
 
 ![Select OAuth](wz_step1_oauth.png)