Update README for workload name and paths

Author: incredere

training/a4/llama3-1-70b/nemo-pretraining-gke/8node-bf16-seq8192-gbs256/README.md

@@ -71,7 +71,7 @@ Clone the `gpu-recipes` repository and set a reference to the recipe folder.
 git clone https://github.com/ai-hypercomputer/gpu-recipes.git
 cd gpu-recipes
 export REPO_ROOT=`git rev-parse --show-toplevel`
-export RECIPE_ROOT=$REPO_ROOT/training/a4/llama3-1-70b/nemo-pretraining-gke/8_nodes
+export RECIPE_ROOT=$REPO_ROOT/training/a4/llama3-1-70b/nemo-pretraining-gke/8node-bf16-seq8192-gbs256
 cd $RECIPE_ROOT
 ```
 
@@ -89,7 +89,7 @@ your client:
 
     ```bash
     cd $RECIPE_ROOT
-    export WORKLOAD_NAME=$USER-a4-llama3-1-70b-8node
+    export WORKLOAD_NAME=$USER-a4-llama3-1-70b
     helm install $WORKLOAD_NAME . -f values.yaml \
     --set-file workload_launcher=launcher.sh \
     --set-file workload_config=llama3-1-70b-bf16-seq8192-gbs256-gpus64.py \
@@ -107,7 +107,7 @@ your client:
 
     ```bash
     cd $RECIPE_ROOT
-    export WORKLOAD_NAME=$USER-a4-llama3-1-70b-8node
+    export WORKLOAD_NAME=$USER-a4-llama3-1-70b
     helm install $WORKLOAD_NAME . -f values.yaml \
     --set-file workload_launcher=launcher.sh \
     --set-file workload_config=llama3-1-70b-bf16-seq8192-gbs256-gpus64.py \
@@ -124,12 +124,12 @@ your client:
 To check the status of pods in your job, run the following command:
 
 ```
-kubectl get pods | grep $USER-a4-llama3-1-70b-8node
+kubectl get pods | grep $USER-a4-llama3-1-70b
 ```
 
 Replace the following:
 
-- JOB_NAME_PREFIX - your job name prefix. For example $USER-a4-llama3-1-70b-8node.
+- JOB_NAME_PREFIX - your job name prefix. For example $USER-a4-llama3-1-70b
 
 To get the logs for one of the pods, run the following command:
 
@@ -141,13 +141,13 @@ Information about the training job's progress, including crucial details such as
 loss, step count, and step time, is generated by the rank 0 process.
 This process runs on the pod whose name begins with
 `JOB_NAME_PREFIX-workload-0-0`.
-For example: `$USER-a4-llama3-1-70b-8node-workload-0-0-s9zrv`.
+For example: `$USER-a4-llama3-1-70b-workload-0-0-s9zrv`.
 
 ### Uninstall the Helm release
 
 You can delete the job and other resources created by the Helm chart. To
 uninstall Helm, run the following command from your client:
 
 ```bash
-helm uninstall $USER-a4-llama3-1-70b-8node
-```
+helm uninstall $USER-a4-llama3-1-70b
+```