update again

_episodes/01-prep.md

@@ -34,32 +34,32 @@ You will be using SSH to sign into your virtual machine. If you run into challen
 
 1. SSH to the [AWS bastion host](https://aws.amazon.com/blogs/security/tag/bastion-host/) by typing the following command:
 
-``` bash
-ssh training@ssh.comanage.incommon.training
+``` console
+$ ssh training@ssh.comanage.incommon.training
 ```
 
 You will use the training session password when requested. As a reminder, you can find the password on the Workshop Reference Document.
 
 2. Once on the bastion host, SSH into the virtual machine that you will be using for the workshop. Refer to the Workshop Reference Document to see the name of your virtual host. You will replace the letter 'N' in the command below, with the number for your virtual machine.
 
-``` bash
-ssh registryN-private
+``` console
+$ ssh registryN-private
 ```
 
 3. The docker files are already available to you, so you can run a few docker commands to check them. 
 
 First we'll see what docker nodes are available:
 
 ``` console
-docker node ls
+[training@registry1-private ~]$ docker node ls
 ID                            HOSTNAME                                       STATUS              AVAILABILITY        MANAGER STATUS      ENGINE VERSION
 8tuwrbfdci97tfn9nqoinic0o *   registry1-private.comanage.incommon.training   Ready               Active              Leader              19.03.4
 ```
 
 You can also see the list of containers that are available by running the docker ps command. (NOTE, there shouldn't be any Docker containers because we haven't set them up yet. This command will confirm that this is true.)
 
 ``` console
-docker ps
+[training@registry1-private ~]$ docker ps
 CONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES
 ```