Update standard steps with new output

python/skewer/standardsteps.yaml

@@ -105,6 +105,7 @@ install_skupper_in_your_namespaces:
     ~~~ console
     $ skupper init
     Waiting for LoadBalancer IP or hostname...
+    Waiting for status...
     Skupper is now installed in namespace '<namespace>'.  Use 'skupper status' to get more information.
     ~~~
 check_the_status_of_your_namespaces:
@@ -147,8 +148,9 @@ link_your_namespaces:
     link.
   commands:
     "0":
-      - output: Token written to ~/secret.token
-        run: skupper token create ~/secret.token
+      - run: skupper token create ~/secret.token
+        output: |
+          Token written to ~/secret.token
     "1":
       - run: skupper link create ~/secret.token
         output: |
@@ -158,8 +160,8 @@ link_your_namespaces:
         apply: test
   postamble: |
     If your console sessions are on different machines, you may need
-    to use `sftp` or a similar tool to transfer the token securely.
-    By default, tokens expire after a single use or 15 minutes after
+    to use `scp` or a similar tool to transfer the token securely.  By
+    default, tokens expire after a single use or 15 minutes after
     creation.
 test_the_application:
   title: Test the application
@@ -201,13 +203,13 @@ accessing_the_web_console:
   commands:
     "0":
       - run: skupper status
-        apply: readme
         output: |
           Skupper is enabled for namespace "@namespace@". It is connected to 1 other site. It has 1 exposed service.
           The site console url is: <console-url>
           The credentials for internal console-auth mode are held in secret: 'skupper-console-users'
       - run: kubectl get secret/skupper-console-users -o jsonpath={.data.admin} | base64 -d
-        output: <password>
+        output: |
+          <password>
       - await_console_ok:
   postamble: |
     Navigate to `<console-url>` in your browser.  When prompted, log