fix(docs): update document paths to use dataset directory

Author: esolitos

examples/operations/multinode-HA/README.md

@@ -463,7 +463,7 @@ Notes:
 ## Test feed and query endpoints
 Feed 5 documents, using the document-API endpoint in the _feed_ container cluster, here mapped to 8080/8081:
 <pre data-test="exec">
-$ i=0; (for doc in $(ls ../../../album-recommendation/ext/*.json); \
+$ i=0; (for doc in $(ls ../../../album-recommendation/dataset/*.json); \
   do \
     curl -H Content-Type:application/json -d @$doc \
     http://localhost:8080/document/v1/mynamespace/music/docid/$i; \
@@ -745,7 +745,7 @@ export VESPA_CLI_DATA_PLANE_KEY_FILE=pki/client/client.key
 ```
 Feed documents:
 ```
-vespa feed -t https://localhost:8443 ../../../album-recommendation/ext/documents.jsonl
+vespa feed -t https://localhost:8443 ../../../album-recommendation/dataset/documents.jsonl
 ```
 Visit documents:
 ```
@@ -762,7 +762,7 @@ Note that the _feed_ and _query_ container cluster nodes are mapped to 8443 and
 ## Test feed and query endpoints using curl
 Feed 5 documents, using the document-API endpoint in the _feed_ container cluster, here mapped to 8080/8081:
 <pre data-test="exec">
-$ i=0; (for doc in $(ls ../../../album-recommendation/ext/*.json); do \
+$ i=0; (for doc in $(ls ../../../album-recommendation/dataset/*.json); do \
     curl -s --key pki/client/client.key --cert pki/client/client.pem --cacert pki/vespa/ca-vespa.pem \
       -H Content-Type:application/json -d @$doc \
       https://localhost:8443/document/v1/mynamespace/music/docid/$i; \

examples/operations/multinode-HA/gke/README.md

@@ -48,7 +48,7 @@ gcloud container clusters create vespa \
   --num-nodes=3 \
   --machine-type=n1-standard-2 \
   --disk-size=20
-  
+
 gcloud container clusters get-credentials vespa
 ```
 This is a minimum-configuration to start the multinode-HA application on GKE.
@@ -207,7 +207,7 @@ Feed data to the feed endpoint:
 kubectl port-forward svc/vespa-feed 8080
 ```
 ```
-i=0; (for doc in $(ls ../../../../album-recommendation/ext/*.json); \
+i=0; (for doc in $(ls ../../../../album-recommendation/dataset/*.json); \
   do \
     curl -H Content-Type:application/json -d @$doc \
     http://localhost:8080/document/v1/mynamespace/music/docid/$i; \

examples/operations/multinode/README.md

@@ -148,9 +148,9 @@ Check that this works:
 $ curl http://localhost:19050/clustercontroller-status/v1/music
 </pre>
 Then open these in a browser:
-* http://localhost:19050/clustercontroller-status/v1/music 
-* http://localhost:19051/clustercontroller-status/v1/music 
-* http://localhost:19052/clustercontroller-status/v1/music 
+* http://localhost:19050/clustercontroller-status/v1/music
+* http://localhost:19051/clustercontroller-status/v1/music
+* http://localhost:19052/clustercontroller-status/v1/music
 
 0 is normally master, 1 is next (and hence has an overview table), 2 is cold.
 
@@ -246,7 +246,7 @@ see [troubleshooting](/examples/operations/README.md#troubleshooting).
 ## Feed data, check distribution
 Make sure the three nodes are started and up - then feed 5 documents:
 <pre data-test="exec" data-test-wait-for="id:mynamespace:music::4">
-$ i=0; (for doc in $(ls ../../../album-recommendation/ext/*.json); \
+$ i=0; (for doc in $(ls ../../../album-recommendation/dataset/*.json); \
     do \
       curl -H Content-Type:application/json -d @$doc \
       http://localhost:8080/document/v1/mynamespace/music/docid/$i; \