edits

Author: dlepow

articles/container-instances/container-instances-liveness-probe.md

@@ -57,14 +57,14 @@ az container create --resource-group myResourceGroup --name livenesstest -f live
 
 ### Start command
 
-The deployment includes a `command` property that defines a starting command that runs when the container first starts running. This property accepts an array of strings. In this example, it starts a bash session and creates a file called `healthy` within the `/tmp` directory by passing this command:
+The deployment includes a `command` property defining a starting command that runs when the container first starts running. This property accepts an array of strings. This command simulates the container entering an unhealthy state.
+
+First, it starts a bash session and creates a file called `healthy` within the `/tmp` directory. It then sleeps for 30 seconds before deleting the file, then enters a 10-minute sleep:
 
 ```bash
 /bin/sh -c "touch /tmp/healthy; sleep 30; rm -rf /tmp/healthy; sleep 600"
 ```
 
- It then sleeps for 30 seconds before deleting the file, then enters a 10-minute sleep.
-
 ### Liveness command
 
 This deployment defines a `livenessProbe` that supports an `exec` liveness command that acts as the liveness check. If this command exits with a non-zero value, the container is killed and restarted, signaling the `healthy` file could not be found. If this command exits successfully with exit code 0, no action is taken.

articles/container-instances/container-instances-readiness-probe.md

@@ -58,7 +58,9 @@ type: Microsoft.ContainerInstance/containerGroups
 
 ### Start command
 
-The deployment includes a `command` property that defines a starting command that runs when the container first starts running. This property accepts an array of strings. This command simulates a time when the web app runs but the container isn't ready. First, it starts a shell session and runs a `node` command to start the web app. It also starts a command to sleep for 240 seconds, after which it creates a file called `ready` within the `/tmp` directory:
+The deployment includes a `command` property defining a starting command that runs when the container first starts running. This property accepts an array of strings. This command simulates a time when the web app runs but the container isn't ready. 
+
+First, it starts a shell session and runs a `node` command to start the web app. It also starts a command to sleep for 240 seconds, after which it creates a file called `ready` within the `/tmp` directory:
 
 ```console
 node /usr/src/app/index.js & (sleep 240; touch /tmp/ready); wait