gitkraken · jjsilva4 · Mar 24, 2026
diff --git a/gitlens/GL-Cloud-Patches.md b/gitlens/GL-Cloud-Patches.md
@@ -1,23 +1,27 @@
 ---
 title: GitLens Cloud Patches
 description: Use GitLens Cloud Patches to securely share work-in-progress changes across GitKraken tools for early collaboration.
+product: GitLens
+feature: Cloud Patches
+content_type: how-to
+audience: developer
+plan_required: Pro
+status: GA
+last_verified: 2026-03
 taxonomy:
     category: gitlens
 
 ---
 
-<kbd>Last updated: August 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
 ## What Are Cloud Patches?
 
-A **Cloud Patch** is a Git patch securely stored by GitKraken so it can be easily shared across **GitLens**, **GitKraken Desktop**, and the **GitKraken CLI**.  
-The patch is transferred directly from your machine into secure storage.
-
-Cloud Patches let you collaborate with your team **before creating a pull request**. You can share work in progress, gather feedback early, and minimize delays in pull request reviews.
+GitLens Cloud Patches let GitLens users securely share uncommitted or in-progress changes across **GitLens**, **GitKraken Desktop**, and the **GitKraken CLI** before opening a pull request. Use this feature when you need early feedback on work in progress and have a GitKraken account with Cloud Patch access.
 
 ---
 
-## Set Up Cloud Patches
+## How to Set Up GitLens Cloud Patches
 
 To enable or disable Cloud Patches per client:
 
@@ -31,7 +35,7 @@ To enable or disable Cloud Patches per client:
 
 ---
 
-## Create and Share Cloud Patches
+## How to Create and Share a Cloud Patch
 
 You can manage Cloud Patches from the **Cloud Patches view** in the GitLens sidebar.
 
@@ -52,6 +56,12 @@ A Cloud Patch can be created from **Working Changes, Commits, Stashes, or Compar
 ### Sharing Options
 When creating a Cloud Patch, choose one of the following:
 
+| Sharing option | Requires account | Best for | Limitation |
+|---|---|---|---|
+| Anyone with the link | No | Fast sharing outside your organization | Anyone with the link can access it |
+| Anyone in my org | Yes | Broad sharing within a GitKraken organization | Limited to organization members |
+| Only collaborators | Yes | Restricted review with named teammates | Requires selecting collaborators |
+
 - **Anyone with the link**: Public access for anyone with the link.  
 - **Anyone in my org**: Accessible to members of your GitKraken Organization (authentication required).  
 - **Only collaborators**: Restricted to selected GitKraken Organization members (authentication required). Use **Invite** to select members.  
@@ -65,7 +75,7 @@ Cloud Patches shared with you appear under **Shared with Me** in the Cloud Patch
 
 ---
 
-## Apply and Manage Cloud Patches
+## How to Apply or Delete a Cloud Patch
 
 - Open a Cloud Patch from a shared URL to view it in GitLens.  
 - Apply it to your **working tree** or to a **new/existing branch** by following the prompts in GitLens.  
@@ -94,4 +104,4 @@ For configuration instructions, see [Self-Hosted Documentation](/gk-dev/gk-dev-h
 
 <div class='callout callout--basic'>
   <p>Note: If you belong to multiple organizations, you can switch between them from the GitKraken Account view.</p>
-</div>
+</div>
diff --git a/gitlens/GL-Code-Suggest.md b/gitlens/GL-Code-Suggest.md
@@ -1,19 +1,29 @@
 ---
 title: GitLens Code Suggest
 description: Use GitLens Code Suggest to propose edits and code review suggestions across entire projects in GitHub repositories.
+product: GitLens
+feature: Code Suggest
+content_type: how-to
+audience: developer
+plan_required: Pro
+status: GA
+last_verified: 2026-03
 taxonomy:
     category: gitlens
 
 ---
 
-<kbd>Last updated: August 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
 ## What Is Code Suggest?
 
-**GitLens Code Suggest** simplifies code review by allowing you to make suggestions and edits across the entire project, not just on changed lines.  
-Suggestions can be created within **GitLens**, **GitKraken Desktop**, or **gitkraken.dev** and attached to pull requests.  
+GitLens Code Suggest lets GitLens users propose project-wide edits and review suggestions for GitHub pull requests from **GitLens**, **GitKraken Desktop**, or **gitkraken.dev**. Use it when review feedback spans files beyond changed-line comments and your repository supports Code Suggest workflows.
 
-Reviewers can then view, accept, and apply these suggestions directly to the pull request branch.
+**Requirements:**
+- **Supported host:** GitHub.com repositories
+- **Requires:** An open pull request on the branch you are reviewing
+- **Review surfaces:** GitLens, GitKraken Desktop, or gitkraken.dev
+- **Best for:** Multi-file or project-wide pull request suggestions
 
 <figure>
   <img src="/wp-content/uploads/gl-code-suggest.png" class="help-center-img img-bordered" alt="GitLens Code Suggest view showing suggestion options" />
@@ -22,7 +32,7 @@ Reviewers can then view, accept, and apply these suggestions directly to the pul
 
 ---
 
-## Start a Code Suggestion
+## How to Start a Code Suggestion
 
 1. Open the [GitLens Inspect Overview](/gitlens/side-bar/#overview) for your repository.  
 2. Check out a branch with an open pull request.  
@@ -46,7 +56,7 @@ This action adds a comment on the pull request with two options:
 
 ---
 
-## Review and Apply Suggestions Locally
+## How to Review and Apply Suggestions Locally
 
 1. Select **Locally on your machine**.  
 2. Open the suggestion in GitLens or [GitKraken Desktop](/gitkraken-client/pull-requests/#review-code-and-suggest-changes).  
@@ -60,7 +70,7 @@ This action adds a comment on the pull request with two options:
 
 ---
 
-## Review and Commit Suggestions in gitkraken.dev
+## How to Review and Commit Suggestions in gitkraken.dev
 
 1. Select **Code Suggestion for #PR** to open the suggestion in **gitkraken.dev**.  
 2. Review each file and its proposed changes.  
@@ -79,4 +89,4 @@ This creates a new commit on the remote branch (shown under **COMMIT SUGGESTIONS
 
 <div class='callout callout--basic'>
   <p><strong>Note:</strong> Code Suggest is currently supported only for repositories on <strong>GitHub.com</strong>.</p>
-</div>
+</div>
diff --git a/gitlens/GL-Commit-Graph.md b/gitlens/GL-Commit-Graph.md
@@ -1,16 +1,29 @@
 ---
 title: GitLens Commit Graph
-description: Visualize your repository history, branches, and collaborators with the GitLens Commit Graph in VS Code.
+description: Visualize your repository history, branches, and collaborators with GitLens Commit Graph across supported GitLens IDEs.
+product: GitLens
+feature: Commit Graph
+content_type: reference
+audience: developer
+plan_required: Pro
+status: GA
+last_verified: 2026-03
 taxonomy:
     category: gitlens
 
 ---
 
-<kbd>Last updated: August 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
 ## Commit Graph <code>PRO</code>
 
-The GitLens Commit Graph provides an interactive view of your repository history. It shows commits, branches, and collaborators in one place, helping you understand contributions and make faster decisions.
+GitLens Commit Graph gives GitLens users an interactive repository history view for branches, commits, and collaborators. Use it when you need branch-level context or commit relationships that are harder to see in file history, line history, or the standard Source Control view.
+
+| View | Best for | Scope | Access |
+|---|---|---|---|
+| Commit Graph | Branch relationships, rebases, and repository-wide history | Entire repository | Public and local repos for all users; private repos require paid access |
+| Visual File History | Understanding how one file evolved | Single file | Available in GitLens |
+| Line History / Inline Blame | Tracing one line or code region | Single line or selection | Available in GitLens |
 
 <figure>
   <img src="/wp-content/uploads/commit-graph.png" class="help-center-img img-bordered" alt="Commit Graph in GitLens showing branches and commits" />
@@ -19,7 +32,7 @@ The GitLens Commit Graph provides an interactive view of your repository history
 
 ---
 
-### Open the Commit Graph
+### How to Open the Commit Graph
 
 1. Open the Command Palette:
    - macOS: <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>
@@ -35,7 +48,7 @@ The Commit Graph opens in a new tab, where you can scroll through history and re
 
 ---
 
-### Repository Information
+### How to Read Repository Information
 
 At the top of the Commit Graph, you’ll see:
 
@@ -62,7 +75,7 @@ At the top of the Commit Graph, you’ll see:
 We’d love your input! Share ideas and feedback in the [GitLens Commit Graph discussion on GitHub](https://github.com/gitkraken/vscode-gitlens/discussions/2158).
 
 
-### Configuration and Layout
+### How to Configure the Commit Graph Layout
 
 You can configure the Commit Graph to control what information is shown and how it is displayed.
 
@@ -115,7 +128,7 @@ Use scroll markers to quickly jump to important points such as `HEAD` or refs. Y
 
 ---
 
-### Settings
+### How to Open Commit Graph Settings
 
 Adjust Commit Graph settings from the Command Palette:
 - macOS: <kbd>Cmd</kbd> + <kbd>Shift</kbd> + <kbd>P</kbd>
@@ -130,7 +143,7 @@ Search for **GitLens: Open Settings**.
 
 ---
 
-### Rich Commit Search
+### How to Search Commits in the Commit Graph
 
 The Commit Graph supports rich search across your entire repository. You can search by commit, message, author, file, or even specific code changes.
 
@@ -261,4 +274,4 @@ The Minimap provides a high-level overview of repository activity. It shows comm
 
 <div class='callout callout--basic'>
   <p>Note: We’d love your feedback on the Minimap. Please share it on the <a href='https://github.com/gitkraken/vscode-gitlens/discussions/2477#discussion-4807133' target='_blank'>GitHub Discussion board</a>.</p>
-</div>
+</div>
diff --git a/gitlens/GL-GK-AI.md b/gitlens/GL-GK-AI.md
@@ -1,13 +1,19 @@
 ---
-
 title: GitKraken AI Features in GitLens
-description: Learn more about the use of Gitkraken AI in Gitlens!
+description: Learn how to use GitKraken AI features in GitLens.
+product: GitLens
+feature: GitKraken AI
+content_type: reference
+audience: developer
+plan_required: all
+status: GA
+last_verified: 2026-03
 taxonomy:
     category: gitlens
 
 ---
 
-Merge cutting-edge AI capabilities with your Git workflow to save time, increase clarity, and enhance collaboration. GitLens' AI features transform how you create, understand, and document code changes.
+This page explains GitLens AI features for Visual Studio Code users, including commit generation, explanations, changelog creation, and pull request workflows. Use it to identify which GitLens AI features are available on your plan and which provider settings or token limits apply before enabling them.
 
 ---
 

diff --git a/gitlens/GL-GK-Account.md b/gitlens/GL-GK-Account.md
@@ -1,13 +1,20 @@
 ---
 title: GitKraken Account – GitLens
 description: Learn how to create and manage your GitKraken account for GitLens features.
+product: GitLens
+feature: GitKraken Account
+content_type: how-to
+audience: developer
+plan_required: all
+status: GA
+last_verified: 2026-03
 taxonomy:
   category: gitlens
 ---
 
-<kbd>Last updated: July 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
-Your GitKraken account is your key to unlocking the most personal experience across GitKraken products.
+This page explains how GitLens users create, sign in to, personalize, and delete a GitKraken account for GitLens features that require authentication. Use it when GitLens prompts for a GitKraken account or when you need to update account settings used across GitKraken products.
 
 <figure class='callout callout--basic'>
   <p><strong>Note:</strong> GitKraken accounts are not compatible with <a href="/git-integration-for-jira-cloud/git-integration-for-jira-home-gij-cloud/">Git Integration for Jira</a>.</p>
@@ -73,4 +80,3 @@ To delete your GitKraken account:
 > Important: If you're a non-admin member of a GitKraken organization, you must ask an admin to remove your account before you can delete it. Organization admins have control over employee accounts.
 
 GitKraken complies with GDPR. Once deleted, your account cannot be restored. This action permanently removes your subscriptions, Cloud Workspaces, Insights data, and organizations.
-
diff --git a/gitlens/GL-Integrations.md b/gitlens/GL-Integrations.md
@@ -1,13 +1,22 @@
 ---
 title: GitLens Integrations
 description: Explore GitLens integrations with remote providers
+product: GitLens
+feature: Integrations
+content_type: integration
+audience: developer
+plan_required: all
+status: GA
+last_verified: 2026-03
 taxonomy:
     category: gitlens
 ---
 
-<kbd>Last updated: July 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
-GitLens supports a wide range of remote providers to enhance your Git workflow inside Visual Studio Code. Supported platforms include:
+This page explains which remote services GitLens integrates with across supported GitLens IDEs, what each integration enables, and how to connect supported providers. Use it when you need pull request, issue, repository, or Launchpad features that depend on an authenticated Git host or Jira connection.
+
+Supported platforms include:
 
 - GitHub (including GitHub Enterprise)
 - GitLab
@@ -162,7 +171,7 @@ GitLens Pro supports integration with Jira Cloud via your GitKraken Account. Thi
 </figure>
 
 <div class='callout callout--warning'>
-  <p>This feature is only available for Pro subscription tiers or higher.</p>
+  <p>This feature is available on Pro, Advanced, Business, and Enterprise plans.</p>
 </div>
 
 ### Connect the Jira Integration

diff --git a/gitlens/GL-Interactive-Code-History.md b/gitlens/GL-Interactive-Code-History.md
@@ -1,22 +1,43 @@
 ---
 title: GitLens Interactive Code History
 description: Learn how GitLens helps you explore and understand your repository’s commit history.
+product: GitLens
+feature: Interactive Code History
+content_type: concept
+audience: developer
+plan_required: all
+status: GA
+last_verified: 2026-03
 taxonomy:
   category: gitlens
 ---
 
-<kbd>Last updated: July 2025</kbd>
+<kbd>Last updated: March 2026</kbd>
 
 <figure class='embed-container embed-container--16-9'>
   <iframe width='560' height='315' src='https://www.youtube.com/embed/uSc7aQV8uMs?si=7bGXpqRI0lv7k-A0' frameborder='0' allowfullscreen title="GitLens Interactive Code History video overview"></iframe>
 </figure>
 
 &nbsp;
 
-Understanding code history in large repositories can be challenging, especially with multiple branches and contributors. GitLens helps simplify this process by providing tools that surface meaningful context:
+GitLens helps users understand code history through Commit Graph, GitLens Inspect, inline blame, and hovers across supported GitLens IDEs. Use this overview when you need to choose the right GitLens history view before investigating authorship, prior changes, or repository context.
+
+Understanding code history in large repositories can be challenging, especially with multiple branches and contributors. GitLens provides tools that surface meaningful context:
 
 - **Commit Graph** – Visualize the structure of your repository.
 - **GitLens Inspect** – Drill into file and line-level history.
 - **Inline Blame and Hovers** – Quickly see who changed what and when.
 
 These features make it easier to navigate your repository, understand changes, and make informed decisions about your code.
+
+## When to Use Commit Graph
+
+Use Commit Graph when you need repository-wide history, branch relationships, merge context, or a visual view of how work diverged over time.
+
+## When to Use GitLens Inspect
+
+Use GitLens Inspect when you want commit, file, or line details for the code currently in front of you without switching to a repository-wide history view.
+
+## When Inline Blame and Hovers Are Enough
+
+Use Inline Blame and hovers when you only need quick authorship, timing, or commit context for the current line before deciding whether to open a deeper history view.