From 173be31af89a0c9e3788cc45fc9e7014a42eb408 Mon Sep 17 00:00:00 2001
From: zacryol <60046681+zacryol@users.noreply.github.com>
Date: Sat, 22 Jan 2022 12:36:21 -0700
Subject: [PATCH] Reverse parenting order of Sprite and AnimationPlayer in
 tutorial

The docs had a sprite as the child of the player, then *immediately* after
says to not do that. Why mislead the reader at all and not just do it
the better way from the start? There nothing really gained from the
sprite being a child here, not even simplicity.

(cherry picked from commit f2ac9f8ab8dc21e54173024e00e7bebbe52967c4)
---
 tutorials/animation/introduction.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/tutorials/animation/introduction.rst b/tutorials/animation/introduction.rst
index 9be4286f4..b9e4aff5b 100644
--- a/tutorials/animation/introduction.rst
+++ b/tutorials/animation/introduction.rst
@@ -105,8 +105,8 @@ Tutorial: Creating a simple animation
 Scene setup
 ~~~~~~~~~~~
 
-For this tutorial, we'll create an AnimationPlayer node and a sprite node as its
-child.
+For this tutorial, we'll create a Sprite node with an AnimationPlayer as
+its child. We will animate the sprite to move between two points on the screen.
 
 .. figure:: img/animation_animation_player_tree.png
    :alt: Our scene setup