turn on some better compiler warnings.

[gregoa/bti.git] / README

diff --git a/README b/README
index caf348ff92ce50003fb8bed6f0c3bb8d195abf22..1c5022ffdba8ed1f2f7788c62c8ebddc1a42be72 100644 (file)
--- a/README
+++ b/README
@@ -21,11 +21,12 @@ and browsed at:
 
 About OAuth configuration
 
 
 About OAuth configuration
 

-If you want to use an OAuth-enabled service (like twitter), you should configure bti to use the
-consumer key and secret shipped with the source code (check the oath.keys file).
+If you want to use an OAuth-enabled service (like twitter), you should
+configure bti to use the consumer key and secret shipped with the source
+code (check the oath.keys file).

 
 

-For example, you should add the following two lines to your ~/.bti configuration
-file:
+For example, you should add the following two lines to your ~/.bti
+configuration file:

 
 ---8<-------------------
 # Consumer key
 
 ---8<-------------------
 # Consumer key


@@ -35,8 +36,8 @@ consumer_key=cZy8DdioswAfu3LJYg6E2w
 consumer_secret=fnIGGU0T12mMWKjmThUdSeKN32NLWfmnwapwubVQ
 ---8<-------------------
 
 consumer_secret=fnIGGU0T12mMWKjmThUdSeKN32NLWfmnwapwubVQ
 ---8<-------------------
 

-The next time that you run bti, you will be told to visit an URL that will
-provide you a PIN number. You should then input that number in the bti prompt,
-and you will be given two new configuration values
+The next time that you run bti, you will be told to visit an URL that
+will provide you a PIN number. You should then input that number in the
+bti prompt, and you will be given two new configuration values

 (access_token_secret and access_token_key) that you need to add to your
 bti configuration file to authenticate requests from bti.
 (access_token_secret and access_token_key) that you need to add to your
 bti configuration file to authenticate requests from bti.