From ab75f0f197847c7fccd8cb5136016aadfdd4e4db Mon Sep 17 00:00:00 2001 From: Daniel Helfand Date: Tue, 26 May 2020 12:03:50 -0400 Subject: [PATCH] correct output alignment, column name, and minor typo in eventing getting started (#2507) --- docs/eventing/getting-started.md | 11 +++++------ 1 file changed, 5 insertions(+), 6 deletions(-) diff --git a/docs/eventing/getting-started.md b/docs/eventing/getting-started.md index 8af6a358c..bb8cdc24b 100644 --- a/docs/eventing/getting-started.md +++ b/docs/eventing/getting-started.md @@ -228,13 +228,12 @@ Your event consumers receive the events sent by event producers. In this step, y This lists the `hello-display` and `goodbye-display` consumers that you deployed: ```sh - NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE - hello-display 1 1 1 1 26s - NAME DESIRED CURRENT UP-TO-DATE AVAILABLE AGE - goodbye-display 1 1 1 1 16s + NAME READY UP-TO-DATE AVAILABLE AGE + hello-display 1/1 1 1 26s + goodbye-display 1/1 1 1 16s ``` - The number of replicas in your **DESIRED** column should match the number of replicas in your **AVAILABLE** column, which might take a few minutes. If after two minutes the numbers do not match, then see the [Debugging Guide](./debugging/README.md) to help troubleshoot the issue. + The number of replicas in your **READY** column should match the number of replicas in your **AVAILABLE** column, which might take a few minutes. If after two minutes the numbers do not match, then see the [Debugging Guide](./debugging/README.md) to help troubleshoot the issue. ### Creating `Triggers` @@ -344,7 +343,7 @@ Now that you've created the Pod, you can create an event by sending an HTTP requ kubectl --namespace event-example attach curl -it ``` - You have sshed into the Pod, and can now make a HTTP request. A prompt similar to the one below will appear: + You have sshed into the Pod, and can now make an HTTP request. A prompt similar to the one below will appear: ```sh Defaulting container name to curl.