Language fixes to building blocks page. (#237)

docs/en/manuals/building-blocks.md

@@ -55,7 +55,7 @@ Game objects are simple objects that each have a separate lifespan during the ex
 go.animate("can", "position.x", go.PLAYBACK_LOOP_PINGPONG, 100, go.EASING_LINEAR, 1.0)
 ```
 
-Game objects can be used empty (as position markers, for instance) but are usually used equipped with various components, like sprites, sounds, scripts, models, factories and more. Game objects are either created in the editor, placed in collection files, or dynamically spawned at run-time through _factory_ components.
+Game objects can be used empty (as position markers, for instance) but are usually equipped with various components, like sprites, sounds, scripts, models, factories and more. Game objects are either created in the editor, placed in collection files, or dynamically spawned at run-time through _factory_ components.
 
 Game objects are either added in-place in a collection, or added to a collection as a reference to a game object file:
 
@@ -80,7 +80,7 @@ You can see what file an object instance is based on in the outline view. The fi
 
 ![Instance](images/building_blocks/instance.png){srcset="images/building_blocks/[email protected] 2x"}
 
-The benefit of creating prototype files becomes apparent when you have multiple instances of a game object or collection and wishes to change all of them:
+The benefit of creating prototype files becomes apparent when you have multiple instances of a game object or collection and wish to change all of them:
 
 ![GO instances](images/building_blocks/go_instance.png){srcset="images/building_blocks/[email protected] 2x"}
 
@@ -94,7 +94,7 @@ Here the sprite image of the prototype file is changed and immediately all insta
 
 ## Childing game objects
 
-In a collection file, you can build hierarchies of game objects so that one or more game objects are children to a single parent game object. By simply <kbd>dragging</kbd> one game object and <kbd>dropping</kbd> it onto another the dragged game object is childed under the target:
+In a collection file, you can build hierarchies of game objects so that one or more game objects are children to a single parent game object. By simply <kbd>dragging</kbd> one game object and <kbd>dropping</kbd> it onto another, the dragged game object is childed under the target:
 
 ![Childing game objects](images/building_blocks/childing.png){srcset="images/building_blocks/[email protected] 2x"}
 
@@ -112,5 +112,5 @@ msg.post("child_bean", "set_parent", { parent_id = parent })
 ```
 
 ::: important
-A common misunderstanding is that a game object's place in the collection hierarchy changes when it becomes part of a parent-child hierarchy. However, these are two very different things. Parent-child hierarchies dynamically alters the scene graph which allows objects to be visually attached to each other. The only thing that dictates a game object's address is its place in the collection hierarchy. The address is static throughout the lifetime of the object.
+A common misunderstanding is that a game object's place in the collection hierarchy changes when it becomes part of a parent-child hierarchy. However, these are two very different things. Parent-child hierarchies dynamically alter the scene graph, which allows objects to be visually attached to each other. The only thing that dictates a game object's address is its place in the collection hierarchy. The address is static throughout the lifetime of the object.
 :::