Merge pull request #726 from BrainCrumbz/patch-2

Typos: 'is case', 'biding', 'droped in'

Author: Urigo

.docs/angular-meteor/client/content/tutorials/angular1/steps/tutorial.step_15.md

@@ -52,7 +52,7 @@ So let's use `ng-if` to hide the outstanding invitations from a party, if the pa
 
 # Assigning a function
 
-Now lets hide the 'Users to invite' inside `party-details.ng.html` is case the user is not logged in or can't invite to the party:
+Now lets hide the 'Users to invite' inside `party-details.ng.html` in case the user is not logged in or can't invite to the party:
 
 To do that we will create a scope function that returns a boolean and associate it with `ng-show`:
 

.docs/angular-meteor/client/content/tutorials/angular1/steps/tutorial.step_16.md

@@ -18,7 +18,7 @@ Now let's add a map the `party-details.ng.html` , first add this HTML snippet to
 
 {{> DiffBox tutorialName="angular-meteor" step="16.2"}}
 
-Here we created the google-map directive with attributes for biding the center, handling events and zoom of the map.
+Here we created the google-map directive with attributes for binding the center, handling events and zoom of the map.
 So let's define those variables in our scope. Go to `partyDetails.js`.
 
 Inside we will create the $scope.map variable to hold the properties on the map:
@@ -56,7 +56,7 @@ What happened here:
 * We added the click event to the map. Every time the user clicks the map, we take the location from the click event's params and save it as the party's new location.
 Notice that in the end we call $scope.$apply();  this is because that event comes outside of Angular and we need to let Angular know that something has change so it will run another $digest cycle.
 * We defined the options object under the marker to specify the marker is draggable.
-* We handled the dragend event that happens when the marker is droped in a new location. We take the location from the event's params and save it as the party's new location.
+* We handled the dragend event that happens when the marker is dropped to a new location. We take the location from the event's params and save it as the party's new location.
 
 Again, with the great Meteor platform there is no need for sync or save function. We just set it and it syncs in all other clients.
 
@@ -77,7 +77,7 @@ You can see that the difference between the directive we used in `party-details.
 The attributes we use:
 
 * models - the scope array that the markers represent.
-* coords - the property the holds the location.
+* coords - the property that holds the location.
 * click - handler for the click event on a marker
 * fit - a boolean to automatically zoom the map to fit all the markers inside
 * idKey - the property that holds the unique id of the array