Clarify SceneTree.current_scene functionality

[AttackButton]

Improving the current_scene description, which was always very succinct. Now it clearly expresses the possibility of quickly getting the top node of the currently running scene.

This change is compatible with 3.x. (Bugsquad edit, needs modifications for the names of the methods for changing scene)

[YuriSizov]

Thanks for opening a PR! Why does your edit basically repeat the same thing twice?

[AttackButton]

I wanted to emphasize the fact of getting the top node quickly, something not as simple as it seems. Even using owner or get_parent (successively until null is returned). I will rewrite the note in another way.

[YuriSizov]

Notes should be used for important but tangential mentions. Here you can just continue the paragraph with an extra tip.

[AttackButton]

It's ok now.

[AThousandShips]

You should rebase instead of merging into your branch, you will need to clean up your branch

[AThousandShips]

See here, do not merge like this

[AThousandShips]

What you need to do is:

• Run git rebase -i master (assuming you've updated master, otherwise if you've added the upstream remote you can use upstream/master)
• replace "pick" for all the commits that aren't yours with "drop"
• replace "pick" of all your own commits save for your first one with "fixup"
• Run git push -f (this is important)

[AThousandShips]

Please squash your commits into a single commit as described above

[AttackButton]

I fixed it. Need to squash, I think.

[AThousandShips]

Are you using git push -f? Because you keep making merge commits for some reason

[AttackButton]

I believe it is fixed now. Thanks.

[YuriSizov]

I believe it is fixed now. Thanks.

Unfortunately, not exactly. You had your branch name as your commit message. I fixed it and pushed on your behalf, so it should be good now.

[akien-mga]

Thanks! And congrats for your first merged Godot contribution 🎉