From 98e1e5ce1ddca9b4dcf08b75822ccb935658db62 Mon Sep 17 00:00:00 2001
From: 2044smile <2044smile@naver.com>
Date: Sun, 13 Sep 2020 15:12:39 +0900
Subject: [PATCH 1/3] fix: tutorial-introduce typo fix

---
 docs/tutorials/01-introduction.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/tutorials/01-introduction.md b/docs/tutorials/01-introduction.md
index 8cb0b5433c..6a8262cf63 100644
--- a/docs/tutorials/01-introduction.md
+++ b/docs/tutorials/01-introduction.md
@@ -90,11 +90,11 @@ If you don't see the event-source and sensor pod in `argo-events` namespace,
   4. Look for any error in event-source or sensor pod.
   5. Inspect the event-source,
 
-        kubectl -n argo-events event-source-object-name -o yaml
+        kubectl -n argo-events get pod event-source-object-name -o yaml
 
      Inspect the sensor,
 
-        kubectl -n argo-events sensor-object-name -o yaml
+        kubectl -n argo-events get pod sensor-object-name -o yaml
 
      and look for any errors within the `Status`.
  

From 7d25a6a837bbb728e1652294478a02867779842a Mon Sep 17 00:00:00 2001
From: 2044smile <2044smile@naver.com>
Date: Sun, 13 Sep 2020 16:57:39 +0900
Subject: [PATCH 2/3] fix: Troubleshoot msg

---
 docs/tutorials/01-introduction.md | 11 ++++-------
 1 file changed, 4 insertions(+), 7 deletions(-)

diff --git a/docs/tutorials/01-introduction.md b/docs/tutorials/01-introduction.md
index 6a8262cf63..02c3fbe446 100644
--- a/docs/tutorials/01-introduction.md
+++ b/docs/tutorials/01-introduction.md
@@ -81,20 +81,17 @@ from event context or data and pass it to the workflow as arguments.
 
 If you don't see the event-source and sensor pod in `argo-events` namespace,
 
-  1. Make sure the correct Role and RoleBindings are applied to the service account
+  1. Inspect the event-source
+  2. Make sure the correct Role and RoleBindings are applied to the service account
      and there are no errors in both event-source and sensor controller.
-  2. Make sure the sensor controller configmap has `namespace` set to 
-     `argo-events`.
   3. Check the logs of event-source and sensor controller. Make sure the controllers
      have processed the event-source and sensor objects and there are no errors.
-  4. Look for any error in event-source or sensor pod.
-  5. Inspect the event-source,
 
-        kubectl -n argo-events get pod event-source-object-name -o yaml
+        kubectl -n argo-events get eventsource event-source-object-name -o yaml
 
      Inspect the sensor,
 
-        kubectl -n argo-events get pod sensor-object-name -o yaml
+        kubectl -n argo-events get sensor sensor-object-name -o yaml
 
      and look for any errors within the `Status`.
  

From 61c8e9716e9adc0fd289d6b4f98dd566e209efd8 Mon Sep 17 00:00:00 2001
From: 2044smile <2044smile@naver.com>
Date: Mon, 14 Sep 2020 09:29:52 +0900
Subject: [PATCH 3/3] fix: minor

---
 docs/tutorials/01-introduction.md | 13 ++++++-------
 1 file changed, 6 insertions(+), 7 deletions(-)

diff --git a/docs/tutorials/01-introduction.md b/docs/tutorials/01-introduction.md
index 02c3fbe446..9edaff5dae 100644
--- a/docs/tutorials/01-introduction.md
+++ b/docs/tutorials/01-introduction.md
@@ -82,11 +82,7 @@ from event context or data and pass it to the workflow as arguments.
 If you don't see the event-source and sensor pod in `argo-events` namespace,
 
   1. Inspect the event-source
-  2. Make sure the correct Role and RoleBindings are applied to the service account
-     and there are no errors in both event-source and sensor controller.
-  3. Check the logs of event-source and sensor controller. Make sure the controllers
-     have processed the event-source and sensor objects and there are no errors.
-
+    
         kubectl -n argo-events get eventsource event-source-object-name -o yaml
 
      Inspect the sensor,
@@ -94,5 +90,8 @@ If you don't see the event-source and sensor pod in `argo-events` namespace,
         kubectl -n argo-events get sensor sensor-object-name -o yaml
 
      and look for any errors within the `Status`.
- 
- 6. Raise an issue on GitHub or post a question on `argo-events` slack channel.
+  2. Make sure the correct Role and RoleBindings are applied to the service account
+     and there are no errors in both event-source and sensor controller.
+  3. Check the logs of event-source and sensor controller. Make sure the controllers
+     have processed the event-source and sensor objects and there are no errors.
+  4. Raise an issue on GitHub or post a question on `argo-events` slack channel.