From da86a42aabe210cb9bbc4e4515102107a323c490 Mon Sep 17 00:00:00 2001
From: kurbycchua <50901466+kurbycchua@users.noreply.github.com>
Date: Fri, 10 May 2024 11:53:17 +0800
Subject: [PATCH] Update lookup-tables.md

---
 pages/docs/data-structure/lookup-tables.md | 9 +++++++--
 1 file changed, 7 insertions(+), 2 deletions(-)

diff --git a/pages/docs/data-structure/lookup-tables.md b/pages/docs/data-structure/lookup-tables.md
index 7475847365..a3ba397941 100644
--- a/pages/docs/data-structure/lookup-tables.md
+++ b/pages/docs/data-structure/lookup-tables.md
@@ -53,7 +53,11 @@ If you have a B2B product, you likely have some key entities that are specific t
 In general, it is still best to have metadata that don't change over time and you analyse often to be tracked as event or user properties. Do refer to the FAQ section on [When shouldn't I use Lookup Tables?](/docs/data-structure/lookup-tables#when-shouldnt-i-use-lookup-tables)
 
 ## How do I upload a Lookup Table?
-Lookup Tables are accessible via Lexicon. Go to **Lexicon > Import > Lookup Table**, and upload a CSV in the format of the example below, and map it to an event or user profile property which is the ID (eg song_id) that the Lookup Table should join with. Mixpanel will assume the first column of the CSV is the ID and will join it with that property.
+Lookup Tables are accessible via Lexicon. Go to **Lexicon > Import > Lookup Table** to upload a CSV file or manage existing lookup tables.
+
+![image](/lexicon-lookup-table.png "Lexicon Lookup Tables")
+
+Here's an example of what a CSV file should look like:
 
 ```
 song_id,artist,genre,is_platinum,name,release_date
@@ -62,7 +66,8 @@ d8d949,Gipsy Kings,Flamenco,False,Bamboleo,1987-07-12T05:00:00Z
 a43fb8,Daft Punk,House,False,Aerodynamic,2001-03-12T07:30:00Z
 ```
 
-![image](/lexicon-lookup-table.png "Lexicon Lookup Tables")
+Once you have uploaded the CSV file for the lookup table map it to an event or user profile property which is the ID (eg song_id) that the Lookup Table should join with. Mixpanel will assume the first column of the CSV is the ID and will join it with that property.
+
 ![image](/lexicon-import-lookup-table.png "Lexicon Import Lookup Table Modal")
 
 You can also upload Lookup Tables straight from your reports. Lookup Tables uploaded directly in reports create a local (or temporary) mapping that can only be used while you are in the report. This mapping is not global, and can't be used in other reports. This feature can be useful if you need to have the lookup table mapping only for a specific report or if you wish to override an existing globally mapped lookup table for a property within a report.