user-guide: reword notes about creds and toekn sharing safety in gdrive guide

per #926 (review)

Author: jorgeorpinel

public/static/docs/user-guide/setup-google-drive-remote.md

@@ -40,10 +40,10 @@ Drive API connections, and its
 6. The newly generated **client ID** and **client secret** should be shown to
    you now, and you can always come back to **Credentials** to fetch them.
 
-⚠️ It's safe to share **client ID** and **client secret** among your team. These
-credentials are used to
-[authorize](https://developers.google.com/drive/api/v2/about-auth) DVC to use
-your Google Drive.
+⚠️ It should be safe to share **client ID** and **client secret** among your
+team. These credentials are only used to generate the
+[authorization](#authorization) DVC will later need in order to connect to the
+Google Drive.
 
 > Note that Google Drive API has usage limits/quotas per credentials in a
 > _project_ (which you can review in the
@@ -103,12 +103,13 @@ $ dvc remote modify mygdfolder gdrive_client_secret <client secret>
 
 On the first usage of a GDrive [DVC remote](/doc/command-reference/remote),
 you'll be prompted to visit a web page to generate an access token, which will
-require you to sign into the corresponding Google account. The sign-in process
-will guide you through granting the necessary access permissions. On success,
-the token data will be cached in a Git-ignored directory located in
+require you to sign into the corresponding Google account. The
+[sign-in process](https://developers.google.com/drive/api/v2/about-auth) will
+guide you through granting the necessary access permissions. On success, the
+token data will be cached in a Git-ignored directory located in
 `.dvc/tmp/gdrive-user-credentials.json`.
 
-⚠️ In order to prevent unauthenticated access to your Google Drive, do not share
-access token data with others. Each team member should have
-[separate access](https://support.google.com/drive/answer/7166529) to Google
-Drive, and generate their own token.
+⚠️ In order to prevent unauthenticated access to your Google Drive, **do not
+share access token data with others**. Each team member should have [separate
+access](https://support.google.com/drive/answer/7166529) to the appropriate
+Google Drive resources, and generate their own tokens.