update tutorial with newer image & args

Signed-off-by: Ian Billett <ibillett@redhat.com>

tutorials/katacoda/thanos/7-multi-tenancy/step2.md

@@ -46,12 +46,11 @@ So why not we start something like this in front of our "Tomato" Querier?
 ```
 docker run -d --net=host --rm \
     --name prom-label-proxy \
-    quay.io/thanos/prom-label-proxy:v0.3.0-rc.0-ext1 \
+    quay.io/prometheuscommunity/prom-label-proxy:v0.3.0 \
     -label tenant \
     -upstream http://127.0.0.1:29090 \
     -insecure-listen-address 0.0.0.0:39090 \
-    -non-api-path-passthrough \
-    -enable-label-apis && echo "Started prom-label-proxy"
+    -enable-label-apis 
 ```{{execute}}
 
 ### Laveraging prom-label-proxy
@@ -97,8 +96,21 @@ At the end we should have setup as on following diagram:
 
 Let's check if our read isolation works:
 
-* [Query for Fruit Team through Caddy 39091 port](https://[[HOST_SUBDOMAIN]]-39091-[[KATACODA_HOST]].environments.katacoda.com/)
-* [Query for Veggie Team through Caddy 39092 port](https://[[HOST_SUBDOMAIN]]-39092-[[KATACODA_HOST]].environments.katacoda.com/)
+#### Team Fruit
+
+Firstly for `Team Fruit`, let's make a query for some data:
+```
+curl -g 'http://127.0.0.1:39091/api/v1/query?query=up'
+```{{execute}}
+Inspecting the output we should only see metrics with `"tenant":"team-fruit"`.
+
+#### Team Veggie
+
+Secondly for `Team Veggie`, let's make the same query to the other port:
+```
+curl -g 'http://127.0.0.1:39091/api/v1/query?query=up'
+```{{execute}}
+ Inspecting the output we should only see metrics with `"tenant":"team-veggie"`.
 
 Feel free to play around, you will see that we can only see Fruit or Veggie data depends where we go!