diff --git a/content/collections/stickiness/en/stickiness-interpret.md b/content/collections/stickiness/en/stickiness-interpret.md
index 797272a7b..73ab04361 100644
--- a/content/collections/stickiness/en/stickiness-interpret.md
+++ b/content/collections/stickiness/en/stickiness-interpret.md
@@ -6,8 +6,8 @@ source: 'https://help.amplitude.com/hc/en-us/articles/360053681271-Interpret-you
 this_article_will_help_you:
   - 'Draw conclusions about user behavior from your Stickiness chart'
   - 'Set up a behavioral cohort from your stickiness analysis'
-updated_by: 0c3a318b-936a-4cbd-8fdf-771a90c297f0
-updated_at: 1717104143
+updated_by: 5817a4fa-a771-417a-aa94-a0b1e7f55eae
+updated_at: 1726784017
 landing: true
 landing_blurb: 'Draw conclusions about user behavior from your Stickiness chart'
 ---
@@ -23,8 +23,6 @@ If you haven't done so already, be sure to read our article on [building a Stick
 
 In Amplitude, Stickiness can be measured in one of two ways: **cumulatively** or **non-cumulatively**. You can change this setting at the top of the Metrics Module at any time during your analysis.
 
-### interpret stickiness 1.png
-
 ### Non-cumulative stickiness
 
 The non-cumulative Stickiness chart shows you the percentage of users who triggered the event at least once on the **exact number of days** listed on the X-axis. For example, users in the *2 days* bucket have triggered the event on **exactly two days** over the course of a week (or month) in the time frame of your analysis, while those in the *3 days* bucket have done it on **exactly three days** in a week.
diff --git a/content/trees/collections/stickiness.yaml b/content/trees/collections/en/stickiness.yaml
similarity index 100%
rename from content/trees/collections/stickiness.yaml
rename to content/trees/collections/en/stickiness.yaml