README.md in unsplash-1.0.0.pre.rc.1 vs README.md in unsplash-1.0.0.pre.rc.2

@@ -50,15 +50,15 @@
 
 ```ruby
 search_results = Unsplash::Photo.search("cats")
 ```
 
-For a complete list of available actions, see our [documentation details]().
+For a complete list of available actions, see our [documentation details](http://www.rubydoc.info/github/CrewLabs/unsplash_rb).
 
 ### User Authorization
 
-For non-public actions, you'll have to get your user's permission to access their data.
+For non-public actions, you'll have to get the user's permission to access their data.
 Direct them to the Unsplash authorization URL:
 
 ```ruby
 requested_scopes = ["public", "read_user", "something_else_you_are_asking_for"]
 auth_url = Unsplash::Client.connection.authorization_url(requested_scopes)
@@ -71,9 +71,15 @@
 Unsplash::Client.connection.authorize!("the authentication code")
 ```
 
 And that's it. The API actions will be available to you according to whichever
 permission scopes you requested and the user authorized.
+
+### Hotlinking
+
+Hotlinking the Unsplash image files is encouraged: https://unsplash.com/documentation#hotlinking
+
+Unlike most APIs, Unsplash prefers for the image URLs returned by the API to be directly used or embedded in your applications (generally referred to as hotlinking). By using the CDN and embedding the photo URLs in your application, Unsplash can better track photo views and pass those stats on to the photographer, providing them with context for how popular their photo is and how it's being used.
 
 ## Development
 
 After checking out the repo, run `bin/setup` to install dependencies. Then, run `rake rspec` to run the tests. You can also run `bin/console` for an interactive prompt that will allow you to experiment.