diff --git a/explore/chart-types/chart-library.mdx b/explore/chart-types/chart-library.mdx
index 5fc8973e..74f97e31 100644
--- a/explore/chart-types/chart-library.mdx
+++ b/explore/chart-types/chart-library.mdx
@@ -1,7 +1,7 @@
 ---
 title: "Install chart types from the chart library"
 sidebarTitle: "Chart library"
-description: "Browse ready-made chart types built by Lightdash and install them into a project so anyone can use them like a built-in chart type"
+description: "Browse and install ready-made Lightdash chart types for everyone in your project"
 icon: "books"
 doc-type: "reference"
 ---
diff --git a/explore/configure-charts.mdx b/explore/configure-charts.mdx
index d2eceb72..fa4e7645 100644
--- a/explore/configure-charts.mdx
+++ b/explore/configure-charts.mdx
@@ -34,6 +34,17 @@ The options available in here will depend on the data in your chart. But, in her
 - Show value labels or group totals on data points
 - Hide a series from your chart
 
+### Value label colors
+
+When you show value labels on bar, line, area, or pie charts, Lightdash chooses a label color automatically:
+
+- Labels on lines and areas, labels outside bars, and labels outside pie slices use the series or slice color.
+- Labels inside bars and pie slices use black or white, depending on which has better contrast with the fill color.
+
+To use a fixed color instead, select the color next to **Value labels** for a cartesian series. On pie charts, use **Label color** to set one color for the whole chart, or expand an individual slice in the **Series** section to override it. Select **Use automatic color** to return to the contrast-aware default.
+
+Value label color overrides are saved with the chart and included in chart-as-code downloads.
+
 ### Custom colors (conditional formatting)
 
 On bar charts, toggle **Apply custom colors** in the Series tab to recolor bars based on rules you define. Each rule targets a specific metric via the **Target metric** picker and only recolors that metric's bars — other metrics keep their default colors, even where their values match the same condition.
diff --git a/workflow/cli/install.mdx b/workflow/cli/install.mdx
index 0754917a..101e0415 100644
--- a/workflow/cli/install.mdx
+++ b/workflow/cli/install.mdx
@@ -1,7 +1,7 @@
 ---
 title: "How to install the Lightdash CLI"
 sidebarTitle: "Install the CLI"
-description: Install the Lightdash CLI with Homebrew on macOS, Linux, or Windows (WSL), or download the binary directly
+description: Install the Lightdash CLI with Homebrew or download the binary directly
 doc-type: tutorial
 ---
 
@@ -95,9 +95,7 @@ The Lightdash CLI doesn't ship a native Windows binary. Install it inside [WSL (
   Once WSL is set up, every other guide in these docs — [authenticating your CLI](/workflow/cli/authenticate), [`lightdash preview`](/workflow/preview-projects), [`lightdash deploy`](/workflow/cli/deploy) — works exactly as written for macOS/Linux. Just run the commands in your Ubuntu terminal.
 </Tip>
 
-<Info>
-  On locked-down corporate laptops (Zscaler / Netskope / SSL inspection) you may hit TLS errors on `lightdash login` and `lightdash deploy`. See [Windows troubleshooting](#windows-troubleshooting).
-</Info>
+On locked-down corporate laptops (Zscaler / Netskope / SSL inspection) you may hit TLS errors on `lightdash login` and `lightdash deploy`. See [Windows troubleshooting](#windows-troubleshooting).
 
 ## Download binary directly
 
@@ -150,9 +148,7 @@ npm install -g @lightdash/cli
 lightdash --version
 ```
 
-<Info>
-  If you get an `npm ERR! code EACCES` error, [follow this guide](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally) to resolve it. On native Windows, if `lightdash` isn't found after install, close and reopen PowerShell so it picks up the updated `PATH`; if PowerShell blocks the script, run `Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned`.
-</Info>
+If you get an `npm ERR! code EACCES` error, [follow this guide](https://docs.npmjs.com/resolving-eacces-permissions-errors-when-installing-packages-globally) to resolve it. On native Windows, if `lightdash` isn't found after install, close and reopen PowerShell so it picks up the updated `PATH`; if PowerShell blocks the script, run `Set-ExecutionPolicy -Scope CurrentUser -ExecutionPolicy RemoteSigned`.
 
 <Warning>
   Native Windows (PowerShell) via npm is less well-tested than WSL. If you hit issues with dbt, file paths, or Node globals, switch to [WSL](#install-on-windows-wsl).