README.md in google_sign_in-1.0.2 vs README.md in google_sign_in-1.1.0

@@ -121,24 +121,28 @@
 For security reasons, the `proceed_to` URL you provide to `google_sign_in_button` is required to reside on the same
 origin as your application. This means it must have the same protocol, host, and port as the page where
 `google_sign_in_button` is used. We enforce this before redirecting to the `proceed_to` URL to guard against
 [open redirects](https://www.owasp.org/index.php/Unvalidated_Redirects_and_Forwards_Cheat_Sheet).
 
+### `GoogleSignIn::Identity`
+
 The `GoogleSignIn::Identity` class decodes and verifies the integrity of a Google ID token. It exposes the profile
 information contained in the token via the following instance methods:
 
 * `name`
 
 * `email_address`
 
-* `user_id`: A value that uniquely identifies a single Google user. Use this, not `email_address`, to associate a
+* `user_id`: A string that uniquely identifies a single Google user. Use this, not `email_address`, to associate a
   Google user with an application user. A Google user’s email address may change, but their `user_id` will remain constant.
 
 * `email_verified?`
 
 * `avatar_url`
 
 * `locale`
+
+* `hosted_domain`: The user’s hosted G Suite domain, provided only if they belong to a G Suite.
 
 
 ## Security
 
 For information on our security response procedure, see [SECURITY.md](SECURITY.md).