Fix minor typos

src/activity-streams/activities.md

@@ -67,7 +67,7 @@ The view, defined in `resources/views/activities.blade.php`, already has some fu
 
 ### User Visited
 
-Whenever the `/activities` endpoint (`getIndex()` action) is access a `user-visit` event is triggered on the `activities` channel. 
+Whenever the `/activities` endpoint (`getIndex()` action) is accessed, a `user-visit` event is triggered on the `activities` channel. 
 
 <i class="fa fa-rocket fa-2"></i> If you haven't already done so, navigate to http://localhost:8000/activities endpoint in the browser and make sure the event is triggered by checking the Pusher Debug Console.
 

src/activity-streams/learned.md

@@ -2,7 +2,7 @@
 
 In this chapter we've:
 
-* Created a super-simple authentication mechanism tso we can give our events some user context
+* Created a super-simple authentication mechanism so we can give our events some user context
 * How we can trigger events with different names on the same channel in order to provide more context to events
 * How events simplify our client-side application logic by separating out event handlers
 

src/activity-streams/simple-auth.md

@@ -53,7 +53,7 @@ In order to use GitHub social login your application needs to be registered with
 1. Login to [GitHub](https://github.com)
 2. Go to your settings (top-right drop-down -> Settings)
 3. Select **Applications** from the menu
-4. Select the **Developer applications** tab
+4. Select the **OAuth applications** tab
 5. Click **Register new application**
 6. Enter a name, If using `localhost:8000`:
   * Use `http://localhost:8000` as the home page

src/getting-started/setting-env-vars.md

@@ -2,7 +2,7 @@
 
 When the Laravel application was created a `.env` file will also have been created in the root of the app.
 
-<i class="fa fa-rocket fa-2"></i> Take the Pusher credentials we noted down earlier (`app_id`, `key` and `secret`) - or you may even have a browser tap still open on the *App Keys* section of your app in the Pusher dashboard - and add them to the `.env` file:
+<i class="fa fa-rocket fa-2"></i> Take the Pusher credentials we noted down earlier (`app_id`, `key` and `secret`) - or you may even have a browser tab still open on the *App Keys* section of your app in the Pusher dashboard - and add them to the `.env` file:
 
 ```php
 PUSHER_APP_ID=YOUR_APP_ID

src/notifications/ui.md

@@ -20,7 +20,7 @@ channel.bind('event-name', function(data) {
 
 ## Showing the Notifications
 
-The Pusher JavaScript library and the toastr notification library has already been included in the [template](../assets/laravel_app/notifiation.blade.php) we copied earlier. So, all we need to do is subscribe to the `notifications` channel, bind to the `new-notification` event and use the toastr library to show the notification.
+The Pusher JavaScript library and the toastr notification library have already been included in the [template](../assets/laravel_app/notifiation.blade.php) we copied earlier. So, all we need to do is subscribe to the `notifications` channel, bind to the `new-notification` event and use the toastr library to show the notification.
 
 <i class="fa fa-rocket fa-2"></i> Use the following code outline to implement the notification functionality: