From 12c59bbf4c7bd1abd15aac3d4f799a803427e6f7 Mon Sep 17 00:00:00 2001
From: "Morales Quispe, Marcela" <marcela.morales.quispe@intel.com>
Date: Wed, 16 Oct 2019 17:35:12 -0500
Subject: [PATCH] Add execution entries at debugging report phase example to
 avoid confusion.

Signed-off-by: Morales Quispe, Marcela <marcela.morales.quispe@intel.com>
---
 metrics/report/README.md | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/metrics/report/README.md b/metrics/report/README.md
index d320cad..6f8349c 100644
--- a/metrics/report/README.md
+++ b/metrics/report/README.md
@@ -64,11 +64,15 @@ shell within the running `Dockerfile` image used to generate the report, whilst
 mapping your host side `R` scripts from the `report_dockerfile` subdirectory into the
 container, thus facilitating a 'live' edit/reload/run development cycle.
 From there you can examine the Docker image environment, and execute the generation scripts.
+
 E.g., to test the `tidy_scaling.R` script, you can execute:
 
 ```bash
-$ makereport.sh -d
-# R
+$ ./makereport.sh -d
+...
+Successfully built eea7d6ac6fa7
+Successfully tagged metrics-report:latest
+root@<hostname>:/# R
 > source('/inputdir/Env.R')
 > source('/scripts/tidy_scaling.R')
 ## Edit script on host, and re-load/run...