From 42ebb7aa11c3c0d50a3a21e8e498405ebfc0fe8f Mon Sep 17 00:00:00 2001
From: Kai Hendry <hendry@webconverger.com>
Date: Fri, 17 Jan 2014 13:08:21 +0800
Subject: [PATCH] Better instructions :)

---
 README.md | 32 ++++++++++++++++++++------------
 1 file changed, 20 insertions(+), 12 deletions(-)

diff --git a/README.md b/README.md
index e5db39c..8fd1f73 100644
--- a/README.md
+++ b/README.md
@@ -27,16 +27,24 @@ Last 4 tweets:
 
 # Getting a Bearer Token
 
-When you clone and attempt to run this project you will notice that you are missing a `secrets.php` 
-file, this file contains one setting `$bearer`. To 
-[create a bearer token](https://dev.twitter.com/docs/auth/application-only-auth):
+When you clone and attempt to run this project you will notice that you are
+missing a `secret.php` file, this file contains one setting `$bearer_token`.
+To [create a bearer
+token](https://dev.twitter.com/docs/auth/application-only-auth):
+
+1. [Create a new Twitter app](https://dev.twitter.com/apps/new)
+1. Under OAuth settings, make a note of the **Consumer key** and **Consumer secret**
+1. Now retrieve the bearer token by building a request with curl:
+
+	curl -X POST --verbose "https://api.twitter.com/oauth2/token" -d "grant_type=client_credentials" -u consumerKey:consumerSecret
+
+The response should end like:
+
+	{"access_token":"SECRETEXAMPLESTRING","token_type":"bearer"}
+
+Save that SECRETEXAMPLESTRING to secret.php:
+
+	<?php
+	$bearer_token = 'SECRETEXAMPLESTRING';
+	?>
 
-1. [Create a new Twitter app.](https://dev.twitter.com/apps/new)
-1. Base64 encode your key and secret separated by a colon, eg: key:secret => a2V5OnNlY3JldA==
-1. Add the result to the Authorization header:
-<pre>
-    wget --post-data=grant_type=client_credentials \
-        --header='Authorization: Basic **BASE64HERE**' \
-        --header='Content-Type: application/x-www-form-urlencoded;charset=UTF-8' \
-        https://api.twitter.com/oauth2/token
-</pre>