Merge pull request #946 from watson-developer-cloud/SirSpidey-patch-vr-iam

Update info about Visual Recognition

Author: lpatino10

README.md

@@ -15,6 +15,7 @@ Java client library to use the [Watson APIs][wdc].
     * [Gradle](#gradle)
   * [Usage](#usage)
   * [Running in IBM Cloud](#running-in-ibm-cloud)
+  * [Visual Recognition](#visual-recognition)
   * [Authentication](#authentication)
     * [Username and Password](#username-and-password)
     * [API Key](#api-key)
@@ -126,6 +127,13 @@ credentials; the library will get them for you by looking at the [`VCAP_SERVICES
 When running in IBM Cloud (or other platforms based on Cloud Foundry), the library will automatically get the credentials from [`VCAP_SERVICES`][vcap_services].
 If you have more than one plan, you can use `CredentialUtils` to get the service credentials for an specific plan.
 
+## Visual Recognition
+
+The process for authenticating with Visual Recognition has changed:
+
+- For new service instances, authenticate by using IAM. See [Using IAM](#using-iam). Also set the service URL by calling the `setEndpoint()` method of the service instance. 
+- For service instances created before May 23, 2018, authenticate by providing the API Key for the service instance. See [API Key](#api-key).
+
 ## Authentication
 
 There are three ways to authenticate with IBM Cloud through the SDK: using a `username` and `password`, using an `api_key`, and with IAM.
@@ -155,7 +163,7 @@ service.setUsernameAndPassword("<username>", "<password>");
 
 ### API Key
 
-_Note: This version of instantiation only works with Visual Recognition, as it's the only service that uses an API key rather than a username and password._
+_Important: Instantiation with API key works only with Visual Recognition service instances created before May 23, 2018. Visual Recognition instances created after May 22 use IAM._
 
 ```java
 // in the constructor