Light copy edit to README

Author: kevinthecheung

auth/README.md

@@ -6,9 +6,9 @@ customizable UI bindings on top of the core
 code and promote best practices (both user experience and security) for
 authentication.
 
-A simple API is provided for drop-in user authentication which handles
-the flow of signing in users with Email/Password,
-Google Sign-In, and Facebook Login. It is built on top of the
+A simple API is provided for drop-in user authentication which handles the flow
+of signing in users with email addresses and passwords, and federated identity
+providers such as Google Sign-In, and Facebook Login. It is built on top of
 [Firebase Auth](https://firebase.google.com/docs/auth).
 
 The best practices embodied in FirebaseUI aim to maximize sign-in
@@ -67,7 +67,7 @@ these authentication methods are first configured in the Firebase console.
 FirebaseUI client-side configuration for Google sign-in is then provided
 automatically by the
 [google-services gradle plugin](https://developers.google.com/android/guides/google-services-plugin).
-If support for Facebook Sign-in is also required, define the
+If support for Facebook Login is also required, define the
 resource string `facebook_application_id` to match the application ID in
 the [Facebook developer dashboard](https://developers.facebook.com):
 
@@ -81,15 +81,15 @@ the [Facebook developer dashboard](https://developers.facebook.com):
 ```
 
 If support for Twitter Sign-in is also required, define the resource strings
-twitter_consumer_key and twitter_consumer_secret to match the values of your Twitter app as
-reported by the [Twitter application manager](https://dev.twitter.com/apps).
+`twitter_consumer_key` and `twitter_consumer_secret` to match the values of your
+Twitter app as reported by the
+[Twitter application manager](https://dev.twitter.com/apps).
 
 ```
 <resources>
   <string name="twitter_consumer_key" translatable="false">YOURCONSUMERKEY</string>
   <string name="twitter_consumer_secret" translatable="false">YOURCONSUMERSECRET</string>
 </resources>
-
 ```
 
 ## Using FirebaseUI for Authentication
@@ -112,13 +112,14 @@ The entry point to the authentication flow is the
 If your application uses the default `FirebaseApp` instance, an AuthUI
 instance can be retrieved simply by calling `AuthUI.getInstance()`.
 If an alternative app instance is required, call
-`AuthUI.getInstance(app)` instead, passing the appropriate FirebaseApp instance.
+`AuthUI.getInstance(app)` instead, passing the appropriate `FirebaseApp`
+instance.
 
 ### Sign in
 
 If a user is not currently signed in, as can be determined by checking
-`auth.getCurrentUser() != null`, where auth is the FirebaseAuth instance
-associated with your FirebaseApp, then the sign-in process can be started by
+`auth.getCurrentUser() != null` (where `auth` is the `FirebaseAuth` instance
+associated with your `FirebaseApp`), then the sign-in process can be started by
 creating a sign-in intent using `AuthUI.SignInIntentBuilder`. A builder instance
 can be retrieved by calling `createSignInIntentBuilder()` on the retrieved
 AuthUI instance.
@@ -129,9 +130,8 @@ The builder provides the following customization options for the authentication
 - The terms of service URL for your app can be specified, which is included as
   a link in the small-print of the account creation step for new users. If no
   terms of service URL is provided, the associated small-print is omitted.
-
 - A custom theme can be specified for the flow, which is applied to all the
-  activities in the flow for consistent customization of colors and typography.
+  activities in the flow for consistent colors and typography.
 
 #### Sign-in examples
 
@@ -175,8 +175,8 @@ startActivityForResult(
 
 By default, FirebaseUI uses [Smart Lock for Passwords](https://developers.google.com/identity/smartlock-passwords/android/)
 to store the user's credentials and automatically sign users into your app on subsequent attempts.
-Using SmartLock is recommended to provide the best user experience, but in some cases you may want
-to disable SmartLock for testing or development.  To disable SmartLock, you can use the 
+Using Smart Lock is recommended to provide the best user experience, but in some cases you may want
+to disable Smart Lock for testing or development.  To disable Smart Lock, you can use the
 `setIsSmartLockEnabled` method when building your sign-in Intent:
 
 ```java
@@ -188,8 +188,8 @@ startActivityForResult(
     RC_SIGN_IN);
 ```
 
-It is often desirable to disable SmartLock in development but enable it in production. To achieve
-this, you can use the `BuildConfig.DEBUG` flag to control SmartLock:
+It is often desirable to disable Smart Lock in development but enable it in production. To achieve
+this, you can use the `BuildConfig.DEBUG` flag to control Smart Lock:
 
 ```java
 startActivityForResult(
@@ -208,7 +208,7 @@ The authentication flow only provides three response codes:
 sign in failed, and `ResultCodes.RESULT_NO_NETWORK` if sign in failed due to a lack of network connectivity.
 No further information on failure is provided as it is not
 typically useful; the only recourse for most apps if sign in fails is to ask
-the user to sign in again later, or proceed with an anonymous account if
+the user to sign in again later, or proceed with anonymous sign-in if
 supported.
 
 ```java
@@ -221,7 +221,7 @@ protected void onActivityResult(int requestCode, int resultCode, Intent data) {
         return;
     }
 
-    // Sign in cancelled
+    // Sign in canceled
     if (resultCode == RESULT_CANCELED) {
         showSnackbar(R.string.sign_in_cancelled);
         return;
@@ -232,7 +232,7 @@ protected void onActivityResult(int requestCode, int resultCode, Intent data) {
         showSnackbar(R.string.no_internet_connection);
         return;
     }
-    
+
     // User is not signed in. Maybe just wait for the user to press
     // "sign in" again, or show a message.
  }
@@ -300,9 +300,9 @@ if (v.getId() == R.id.sign_out) {
 With the integrations provided by FirebaseUI Auth, deleting a user is a multi-stage process:
 
 1. The user must be deleted from Firebase Auth.
-2. SmartLock for Passwords must be told to delete any existing Credentials for the user, so
+2. Smart Lock for Passwords must be told to delete any existing Credentials for the user, so
    that they are not automatically prompted to sign in with a saved credential in the future.
-   
+
 This process is encapsulated by the `AuthUI.delete()` method, which returns a `Task` representing
 the entire operation:
 
@@ -387,7 +387,7 @@ redefine a string to change it, for example:
 ### OAuth Scope Customization
 
 #### Google
-By default, FirebaseUI requests the `email` and `profile` scopes when using Google Sign In. If you
+By default, FirebaseUI requests the `email` and `profile` scopes when using Google Sign-In. If you
 would like to request additional scopes from the user, call `setPermissions` on the
 `AuthUI.IdpConfig.Builder` when initializing FirebaseUI.