From 56748cd38ea15c2f54b1b0b3e8d48a878ccec7d6 Mon Sep 17 00:00:00 2001
From: ANANDHU S <71482562+anandhu-eng@users.noreply.github.com>
Date: Tue, 29 Oct 2024 10:24:12 +0530
Subject: [PATCH 1/3] corrected hyperlinks

---
 docs/getting-started.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/getting-started.md b/docs/getting-started.md
index f1c337ce3..18fdba09c 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -192,7 +192,7 @@ Such architecture makes it possible to easily chain existing user scripts and to
 instead of substituting or rewriting them.
 
 It is possible to chain CM scripts using simple 
-[`deps` list](https://github.com/mlcommons/ck/blob/master/cm-mlops/script/app-image-classification-onnx-py/_cm.yaml#L21) 
+[`deps` list](https://github.com/mlcommons/ck/blob/master/cm-mlops/script/app-image-classification-onnx-py/_cm.yaml#L23) 
 in a meta description of a given script:
 
 <sup>
@@ -262,7 +262,7 @@ cmr "python app image-classification onnx _cpu" --input=computer_mouse.jpg -j
  variables at the host. However, CM allows you to do that 
  by explicitly specifying which environment variables and state keys
  will be updated at the host using `new_env_keys` and `new_state_keys`
- in the meta of a given script as shown [here](https://github.com/mlcommons/ck/blob/master/cm-mlops/script/app-image-classification-onnx-py/_cm.yaml#L83).
+ in the meta of a given script as shown [here](https://github.com/mlcommons/ck/blob/master/cm-mlops/script/app-image-classification-onnx-py/_cm.yaml#L88).
  This helped us make behavior of complex CM workflows more deterministic
  and reproducible.*
 
@@ -294,7 +294,7 @@ detect or install Python and PIP packages, download and preprocess data sets and
 
 ## How to add new CM scripts?
 
-One the main requirement for CM was to provide a very light-weight connectors 
+One of the main requirement for CM was to provide a very light-weight connectors 
 between existing automation scripts and tools rather than substituting them.
 
 You can add your own scripts and tools to CM using the following command

From aec10d178e528e11c192a6ee2184f65e6ade7f1e Mon Sep 17 00:00:00 2001
From: ANANDHU S <71482562+anandhu-eng@users.noreply.github.com>
Date: Tue, 29 Oct 2024 10:57:05 +0530
Subject: [PATCH 2/3] Update getting-started.md

---
 docs/getting-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started.md b/docs/getting-started.md
index 18fdba09c..f23592680 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -314,7 +314,7 @@ You can also run it from python as follows:
 import cmind
 output=cmind.access({'action':'run', 
                      'automation':'script', 
-                     'tags':'my,script})
+                     'tags':'my,script'})
 if output['return']==0: print (output)
 ```
 

From c9adefe3b4f196a55a6741708a32594b555a4332 Mon Sep 17 00:00:00 2001
From: ANANDHU S <71482562+anandhu-eng@users.noreply.github.com>
Date: Tue, 29 Oct 2024 14:36:15 +0530
Subject: [PATCH 3/3] Fix in cm through virtual env

---
 docs/getting-started.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/getting-started.md b/docs/getting-started.md
index f23592680..d9effbf65 100644
--- a/docs/getting-started.md
+++ b/docs/getting-started.md
@@ -412,7 +412,7 @@ export CM_SCRIPT_EXTRA_CMD="--adr.python.name=mlperf"
 
 If you now run our image classification automation recipe, 
 it will reuse model and dataset from the cache, but will
-use 
+use the newly created virtual environment `mlperf` for running the script.
 
 
 ## How to debug CM scripts?