Browse Source

Merge pull request #2514 from Meriipu/patch-1

Tutorial text: try and -> try to
Nathan Lovato 6 years ago
parent
commit
6ff4f00e57

+ 1 - 1
tutorials/inputs/input_examples.rst

@@ -91,7 +91,7 @@ It inherits from the following classes:
         with events so you can check the event type's available properties and
         with events so you can check the event type's available properties and
         methods.
         methods.
 
 
-You can encounter errors if you try and access a property on an input type that
+You can encounter errors if you try to access a property on an input type that
 doesn't contain it - calling ``position`` on ``InputEventKey`` for example. To
 doesn't contain it - calling ``position`` on ``InputEventKey`` for example. To
 avoid this, make sure to test the event type first:
 avoid this, make sure to test the event type first:
 
 

+ 1 - 1
tutorials/misc/instancing_with_signals.rst

@@ -68,7 +68,7 @@ You could do this by adding the bullet to the main scene directly:
     Node bulletInstance = Bullet.Instance();
     Node bulletInstance = Bullet.Instance();
     GetParent().AddChild(bulletInstance);
     GetParent().AddChild(bulletInstance);
 
 
-However, this will lead to a different problem. Now if you try and test your
+However, this will lead to a different problem. Now if you try to test your
 "Player" scene independently, it will crash on shooting, because there is no
 "Player" scene independently, it will crash on shooting, because there is no
 parent node to access. This makes it a lot harder to test your player code
 parent node to access. This makes it a lot harder to test your player code
 independently and also means that if you decide to change your main scene's
 independently and also means that if you decide to change your main scene's