Updating docs to reflect full path requirement for ssh key (#1370)

docs/firstWorkload/README.md

@@ -174,7 +174,12 @@ Update the value for `resource_group_name` to be a variant of this, like `myname
 
 Update the `gitops_ssh_url` to your GitOps resource manifest repo, using the `ssh` url format available when you clone the repo from Azure DevOps. For example: `git@ssh.dev.azure.com:v3/myOrganization/myProject/app-cluster-manifests`.
 
-Set the `gitops_ssh_key` to the GitOps private key we created previously. If you followed those steps, you can set this value to `~/cluster-deployment/keys/gitops-ssh-key`.
+Set the `gitops_ssh_key` to the full path to the GitOps private key we created previously. If you followed those steps, you can find the full path by running:
+```
+$ cd ~/cluster-deployment
+$ echo $(pwd)/keys/gitops-ssh-key
+/Users/demo/cluster-deployment/keys/gitops-ssh-key
+```
 
 In multi-cluster scenarios, we will often keep all of the resource manifests for all of our clusters in the same repo, but in this simple case, we are only managing one cluster, so we are going to use the root of our GitOps repo as our root for our in-cluster resource manifests.