From 3904b8feaca1d6f6853a0437e996ff3136654fde Mon Sep 17 00:00:00 2001
From: Andreas Haas <liu.gam3@gmail.com>
Date: Tue, 16 May 2017 19:53:38 +0200
Subject: [PATCH] InputEvent tutorial: Recommend Input instead of MainLoop for
 parsing events.

(cherry picked from commit 0ca7e06f36934dd2fb97f468f7072fe93cb7348b)
---
 learning/features/inputs/inputevent.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/learning/features/inputs/inputevent.rst b/learning/features/inputs/inputevent.rst
index e4bb66af9..c7d7cd878 100644
--- a/learning/features/inputs/inputevent.rst
+++ b/learning/features/inputs/inputevent.rst
@@ -135,8 +135,8 @@ Any event has the methods :ref:`InputEvent.is_action() <class_InputEvent_is_acti
 
 Alternatively, it may be desired to supply the game back with an action
 from the game code (a good example of this is detecting gestures).
-SceneTree (derived from MainLoop) has a method for this:
-:ref:`MainLoop.input_event() <class_MainLoop_input_event>`. You would normally use it like this:
+The Input singleton has a method for this:
+:ref:`Input.parse_input_event() <class_input_parse_input_event>`. You would normally use it like this:
 
 ::
 
@@ -145,7 +145,7 @@ SceneTree (derived from MainLoop) has a method for this:
     # set as move_left, pressed
     ev.set_as_action("move_left", true) 
     # feedback
-    get_tree().input_event(ev)
+    Input.parse_input_event(ev)
 
 InputMap
 --------