extend validation requirements (hyperledger-archives#2221)

contrib-notes/release-process/runtime-validation.md

@@ -70,7 +70,20 @@ Verification Stage (basic)
 
 Verification Stage (adv)
  - Use the Ionic App to drive the vehicle lifecycle
+ -- From the ionic app, define the car order and then select 'build'
+ -- From the manufcturing page, commence manufacture
+ -- From the VDA page, observe the chains being generated as the order progresses
  - Log into Playground and inspect transactions via Historian, and all items in the registry
 
 Points to note:
  - If you get lost, or don't know what to do, ask
+
+ ## K8 Scripts
+ This task requires obtaining and running of the K8 scripts, targetting a deploy environment, however, prior to this:
+  - The K8 scripts will need to be modified to target unstable images of all composer items
+
+Only after modifying the tags should you proceed with the script run.
+
+Once the scripts have run, log onto Playground and ensure that:
+ - You have access
+ - You can generate and share ID cards

contrib-notes/release-process/weekly-qa-validation.md

@@ -59,4 +59,4 @@ Consequently a major version bump in Composer *requires* Composer-tools to suppo
 VLC builds from static files, that define the connection profile, IDCard that enables connection, deployed base network etc. Any breaking API changes in the runtime must be accounted for in the build files that generate the specification, otherwise it simply will not work and we will be very sad.
 
 #K8s
-Alike the VLC demo, the K8s sripts are based from the build of static files ... API changes must also be refelcted here.
+Alike the VLC demo, the K8s sripts are based from the build of static files ... API changes must also be reflected here.