formatting

Author: taylorotwell

UPGRADE.md

@@ -18,19 +18,19 @@ PR: https://github.com/laravel/passport/pull/1145
 
 Client secrets may now be stored using a Bcrypt hash. However, before enabling this functionality, please consider the following. First, there is no way to reverse the hashing process once you have migrated your existing tokens. Secondly, when hashing client secrets, you will only have one opportunity to display the plain-text value to the user before it is hashed and stored in the database.
 
-#### Personal Access Client
+#### Personal Access Clients
 
-Before you continue, there's a special case for personal access clients. You should set your personal access client ID and unhashed secret in your `.env` file:
+Before you continue, you should set your personal access client ID and unhashed secret in your `.env` file:
 
-    PASSPORT_PERSONAL_ACCESS_CLIENT_ID=
-    PASSPORT_PERSONAL_ACCESS_CLIENT_SECRET=
+    PASSPORT_PERSONAL_ACCESS_CLIENT_ID=client-id-value
+    PASSPORT_PERSONAL_ACCESS_CLIENT_SECRET=unhashed-client-secret-value
 
-After this, you should set register them with the `Passport` instance by playing the following calls within the `boot` method of your `AppServiceProvider`:
+Next, you should set register these values by placing the following calls within the `boot` method of your `AppServiceProvider`:
 
     Passport::personalAccessClientId(config('passport.personal_access_token.id'));
     Passport::personalAccessClientSecret(config('passport.personal_access_token.secret'));
 
-Make sure to do this before hashing your secrets using the step below, otherwise they'll be lost forever.
+> Make sure you follow the instructions above before hashing your secrets. Otherwise, irreversible data loss may occur.
 
 #### Hashing Existing Secrets
 

config/passport.php

@@ -35,9 +35,9 @@
     | Personal Access Client
     |--------------------------------------------------------------------------
     |
-    | If you enable client hashing, you should set the personal access
-    | client id and secret in your config file. This way they will be
-    | used when you issue access tokens to your users.
+    | If you enable client hashing, you should set the personal access client
+    | ID and unhashed secret within your environment file. The values will
+    | get used while issuing fresh personal access tokens to your users.
     |
     */