diff --git a/docs/user/dashboard/lens.asciidoc b/docs/user/dashboard/lens.asciidoc
index 7cafeca52bdb3c..fb6696d3d8129b 100644
--- a/docs/user/dashboard/lens.asciidoc
+++ b/docs/user/dashboard/lens.asciidoc
@@ -315,8 +315,8 @@ Pagination in a data table is unsupported in *Lens*. However, the <<types-of-vis
 *Lens* lets you pick, for each Y dimension, up to two distinct axis: *left* and *right*. Each axis can have a different scale.
 
 [float]
-[[why-my-value-is-not-of-the-right-color-using-value-based-coloring]]
-===== Why mt value is not of the right color when using value-based coloring?
+[[why-is-my-value-with-the-right-color-using-value-based-coloring]]
+===== Why is my value with the incorrect color when using value-based coloring?
 
 There could be various reasons for a specific value in the table to have a different color than expected.
 
@@ -325,10 +325,10 @@ Here's a short list of few different aspects to check:
 
 * Make sure you have the right value precision setup: value formatters could round the numeric values up or down.
 
-* Make sure the right color continuity option is selected: if the number is below the first color stop value a continuity of type `Below` or `Above and below range` is required
+* Make sure the right color continuity option is selected: if the number is below the first color stop value, a continuity of type `Below` or `Above and below range` is required.
 
 * The default values set by the Value type are based on the current data range displayed on the data table.
 
 ** If a custom `Number` configuration is used, check that the color stop values are covering the current data range.
 
-** If a `Percent` configuration is used, when the data range changes this has an effect on colors displayed.
+** If a `Percent` configuration is used, and the data range changes, the colors displayed are affected.